TS 123 082 - V3.5.0 - Digital cellular telecommunications ... · ETSI 3GPP TS 23.082 version 3.5.0...

ETSI TS 123 082 V3.5.0 (2000-12)Technical Specification

Digital cellular telecommunications system (Phase 2+) (GSM);Universal Mobile Telecommunications System (UMTS);Call Forwarding (CF) supplementary services - Stage 2

(3GPP TS 23.082 version 3.5.0 Release 1999)

GLOBAL SYSTEM FORMOBILE COMMUNICATIONS

R

1

ETSI

ETSI TS 123 082 V3.5.0 (2000-12)3GPP TS 23.082 version 3.5.0 Release 1999

ReferenceRTS/TSGN-0423082UR4

KeywordsGSM, UMTS

ETSI

650 Route des LuciolesF-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 CAssociation à but non lucratif enregistrée à laSous-Préfecture de Grasse (06) N° 7803/88

Important notice

Individual copies of the present document can be downloaded from:http://www.etsi.org

The present document may be made available in more than one electronic version or in print. In any case of existing orperceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).

In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drivewithin ETSI Secretariat.

Users of the present document should be aware that the document may be subject to revision or change of status.Information on the current status of this and other ETSI documents is available at http://www.etsi.org/tb/status/

If you find errors in the present document, send your comment to:[email protected]

Copyright Notification

No part may be reproduced except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2000.

All rights reserved.

http://www.etsi.org/

http://www.etsi.org/tb/status

[email protected]

2

ETSI


Intellectual Property RightsIPRs essential or potentially essential to the present document may have been declared to ETSI. The informationpertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be foundin ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI inrespect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Webserver (http://www.etsi.org/ipr).

Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guaranteecan be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Webserver) which are, or may be, or may become, essential to the present document.

ForewordThis Technical Specification (TS) has been produced by the ETSI 3rd Generation Partnership Project (3GPP).

The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities orGSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.

The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under www.etsi.org/key .

http://www.etsi.org/ipr

http://www.etsi.org/key

ETSI


Contents

Foreword ............................................................................................................................................................6

0 Scope ........................................................................................................................................................70.1 References................................................................................................................................................................70.2 Abbreviations...........................................................................................................................................................80.3 The forwarded-to number ........................................................................................................................................80.4 Cross phase compatibility ........................................................................................................................................80.5 Support of Long Forwarded-to Numbers .................................................................................................................80.6 Data stored in the HLR for all call forwarding services...........................................................................................8

1 Call forwarding unconditional (CFU) ......................................................................................................91.1 Handling of call forwarding unconditional ..............................................................................................................91.1.1 Registration ........................................................................................................................................................91.1.2 Erasure..............................................................................................................................................................121.1.3 Activation.........................................................................................................................................................141.1.4 Deactivation .....................................................................................................................................................161.1.5 Interrogation.....................................................................................................................................................181.2 Functions and information flows ...........................................................................................................................181.3 Information stored in the HLR...............................................................................................................................201.4 State transition model ............................................................................................................................................211.5 Transfer of information from HLR to VLR ...........................................................................................................221.6 Information stored in the VLR...............................................................................................................................221.7 Handover................................................................................................................................................................221.8 Cross phase compatibility ......................................................................................................................................221.8.1 MS, MSC, VLR or HLR only support Phase 1 control of SS by the subscriber ..............................................221.8.2 HLR only supports Phase 1 updating of subscriber information......................................................................231.8.3 VLR only supports Phase 1 updating of subscriber information......................................................................231.8.4 GMSC only supports Phase 1 call handling .....................................................................................................231.8.5 GMSC does not support CAMEL or supports CAMEL Phase 1 only .............................................................231.9 Contents of Messages.............................................................................................................................................231.9.1 Messages on the C interface (MSC-HLR)........................................................................................................231.9.1.4 Send Routing Info ............................................................................................................................................231.9.1.2 Send Routing Info ack......................................................................................................................................241.9.2 Messages on the Um, B and D interfaces (MS – network)...............................................................................241.9.2.1 RegisterSS ........................................................................................................................................................241.9.2.2 ActivateSS........................................................................................................................................................241.9.2.3 InterrogateSS....................................................................................................................................................241.9.3 Information flows on the J interface (HLR – gsmSCF) ...................................................................................241.9.3.1 Any Time Subscription Interrogation...............................................................................................................241.9.3.2 Any Time Subscription Interrogation ack ........................................................................................................251.9.3.3 Any Time Modification....................................................................................................................................251.9.3.4 Any Time Modification ack .............................................................................................................................251.10 Exceptional Procedures ....................................................................................................................................251.10.1 MS does not support Long Forwarded-to Numbers .........................................................................................251.10.2 HLR does not support Long Forwarded-to Numbers .......................................................................................251.10.3 GMSC does not support Long Forwarded-to Numbers....................................................................................26

2 Call forwarding on mobile subscriber busy ...........................................................................................262.1 Handling of call forwarding on mobile subscriber busy ........................................................................................262.1.1 Registration ......................................................................................................................................................262.1.2 Erasure..............................................................................................................................................................282.1.3 Activation.........................................................................................................................................................302.1.4 Deactivation .....................................................................................................................................................322.1.5 Interrogation.....................................................................................................................................................342.2 Functions and information flows ...........................................................................................................................342.3 Information stored in the HLR...............................................................................................................................392.4 State transition model ............................................................................................................................................402.5 Transfer of information from HLR to VLR ...........................................................................................................41

ETSI


2.6 Information stored in the VLR...............................................................................................................................412.7 Handover................................................................................................................................................................412.8 Cross phase compatibility ......................................................................................................................................422.8.1 MS, MSC, VLR or HLR only support Phase 1 control of SS by the subscriber ..............................................422.8.2 HLR only supports Phase 1 updating of subscriber information......................................................................422.8.3 VLR only supports Phase 1 updating of subscriber information......................................................................422.8.4 VLR only supports Phase 1 call handling ........................................................................................................422.8.5 VLR does not support CAMEL or supports CAMEL Phase 1 only.................................................................422.9 Contents of messages .............................................................................................................................................432.9.1 Messages on the B interface (MSC-VLR)........................................................................................................432.9.1.1 Send Info For Incoming Call ack .....................................................................................................................432.9.2 Messages on the D interface (VLR-HLR)........................................................................................................432.9.2.1 Insert Subscriber Data ......................................................................................................................................432.9.2.2 Update Location ...............................................................................................................................................432.9.2.3 Provide Roaming Number................................................................................................................................442.9.3 Messages on the E interface (VMSC-GMSC)..................................................................................................442.9.3.1 Resume Call Handling......................................................................................................................................442.9.4 Messages on the MSC internal interface ..........................................................................................................442.9.4.1 Perform Call Forwarding..................................................................................................................................442.9.4.2 Perform Call Forwarding ack ...........................................................................................................................442.10 Support of Long Forwarded-to Numbers .........................................................................................................442.10.1 MS does not support Long Forwarded-to Numbers .........................................................................................442.10.2 HLR does not support Long Forwarded-to Numbers .......................................................................................452.10.3 GMSC does not support Long Forwarded-to Numbers....................................................................................452.10.4 MSC/VLR does not support Long Forwarded-to Numbers..............................................................................45

3 Call forwarding on no reply ...................................................................................................................453.1 Handling of call forwarding on no reply................................................................................................................453.1.1 Registration ......................................................................................................................................................453.1.2 Erasure..............................................................................................................................................................483.1.3 Activation.........................................................................................................................................................503.1.4 Deactivation .....................................................................................................................................................523.1.5 Interrogation.....................................................................................................................................................543.2 Functions and information flows ...........................................................................................................................543.3 Information stored in the HLR...............................................................................................................................583.4 State transition model ............................................................................................................................................583.5 Transfer of information from HLR to VLR ...........................................................................................................593.6 Information stored in the VLR...............................................................................................................................593.7 Handover................................................................................................................................................................603.8 Cross phase compatibility ......................................................................................................................................603.8.1 MS, MSC, VLR or HLR only support Phase 1 control of SS by the subscriber ..............................................603.8.2 HLR only supports Phase 1 updating of subscriber information......................................................................603.8.3 VLR only supports Phase 1 updating of subscriber information......................................................................603.8.4 VLR only supports Phase 1 call handling ........................................................................................................603.8.5 VLR does not support CAMEL or supports CAMEL Phase 1 only.................................................................613.9 Contents of messages .............................................................................................................................................613.10 Support of Long Forwarded-to Numbers .........................................................................................................61

4 Call forwarding on mobile subscriber not reachable..............................................................................614.1 Handling of call forwarding on mobile subscriber not reachable ..........................................................................614.1.1 Registration ......................................................................................................................................................614.1.2 Erasure..............................................................................................................................................................644.1.3 Activation.........................................................................................................................................................664.1.4 Deactivation .....................................................................................................................................................684.1.5 Interrogation.....................................................................................................................................................704.2 Functions and information flows ...........................................................................................................................704.2.1 Call re-routed from VLR..................................................................................................................................704.2.2 Call re-routed from HLR..................................................................................................................................704.2.3 Call re-routed from HLR for Pre-Paging..........................................................................................................814.3 Information stored in the HLR...............................................................................................................................844.4 State transition model ............................................................................................................................................854.5 Transfer of information from HLR to VLR ...........................................................................................................86

ETSI


4.6 Information stored in the VLR...............................................................................................................................864.7 Handover................................................................................................................................................................864.8 Cross phase compatibility ......................................................................................................................................874.8.1 MS, MSC, VLR or HLR only support Phase 1 control of SS by the subscriber ..............................................874.8.2 HLR only supports Phase 1 updating of subscriber information......................................................................874.8.3 VLR only supports Phase 1 updating of subscriber information......................................................................874.8.4 GMSC only supports Phase 1 call handling .....................................................................................................874.8.5 VLR only supports Phase 1 call handling ........................................................................................................874.8.6 VLR does not support CAMEL or supports CAMEL Phase 1 only.................................................................884.8.7 GMSC does not support CAMEL or supports CAMEL Phase 1 only .............................................................884.9 Contents of messages .............................................................................................................................................884.10 Support of Long Forwarded-to Numbers .........................................................................................................88

Annex A (informative): Change history .......................................................................................................89

ETSI


ForewordThis Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP).

The present document defines the stage 2 of the Call Forwarding (CF) supplementary services for the 3GPP system.

The contents of the present document are subject to continuing work within the TSG and may change following formalTSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with anidentifying change of release date and an increase in version number as follows:

Version x.y.z

where:

x the first digit:

1 presented to TSG for information;

2 presented to TSG for approval;

3 or greater indicates TSG approved document under change control.

y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,updates, etc.

z the third digit is incremented when editorial only changes have been incorporated in the document.

ETSI


0 ScopeThe present document gives the stage 2 description of the call forwarding supplementary services.

The group of supplementary services call offering supplementary services is divided into 4 different supplementaryservices:

- Call forwarding unconditional (CFU) (clause 1);

- Call forwarding on mobile subscriber busy (CFB) (clause 2);

- Call forwarding on no reply (CFNRy) (clause 3);

- Call forwarding on mobile subscriber not reachable (CFNRc) (clause 4).

0.1 ReferencesThe following documents contain provisions which, through reference in this text, constitute provisions of the presentdocument.

• References are either specific (identified by date of publication, edition number, version number, etc.) ornon-specific.

• For a specific reference, subsequent revisions do not apply.

• For a non-specific reference, the latest version applies.

[1] 3G TR 21.905: "3G Vocabulary".

[2] 3G TS 22.004: "General on supplementary services".

[3] 3G TS 22.082: "Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF)Supplementary Services - Stage 1".

[4] 3G TS 23.011: "Technical realization of supplementary services".

[5] 3G TS 23.015: "Technical realization of operator determined barring".

[6] 3G TS 22.078: "Customised Applications for Mobile network Enhanced Logic (CAMEL); Servicedescription, Stage 1".

[7] 3G TS 23.018: "Basic Call Handling; Technical Realization".

[8] 3G TS 23.078: "Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 3– Stage 2".

[9] 3G TS 23.079: "Support of Optional Routeing (SOR); Technical realisation".

[10] 3G TS 29.002: "Mobile Application part (MAP) specification".

ETSI


0.2 AbbreviationsFor the purposes of the present document, the abbreviations listed in 3G TR 21.905 apply.

0.3 The forwarded-to numberAs indicated in 3G TS 22.082 the forwarded-to numbers are stored in the international format.

If according to 3G TS 22.082 the served subscriber is provided with a Translation Information Flag (TIF-CSI) then theHPLMN shall treat the forwarded-to number transparently at the time of registration, i.e. not perform any checks ortranslations. In this case the forwarded-to number shall be stored in the format as it was received from the MS.

Therefore, if transferred, the forwarded-to number is transferred from the HLR to other network entities and stored inthe VLR always in the format as stored in the HLR..

0.4 Cross phase compatibilityFor the following supplementary services, a number of changes exist between the present document and the Phase 1specification:

- Call forwarding unconditional;

- Call forwarding on mobile subscriber busy;

- Call forwarding on no reply;

- Call forwarding on mobile subscriber not reachable.

The main body of the present document assumes that all network entities comply with this version of the service. Ineach case an additional subclause (subclause x.6) defines the additional requirements for when one or more networkentities or the MS complies with the Phase 1 specifications for the supplementary service procedures.

0.5 Support of Long Forwarded-to NumbersFor the following supplementary services, it shall be possible to register a long forwarded-to number which was notpossible in previous versions of the services:

- Call forwarding unconditional;

- Call forwarding on mobile subscriber busy;

- Call forwarding on no reply;

- Call forwarding on mobile subscriber not reachable.

The main body of the present document assumes that all network entities comply with this version of the service. Ineach case an additional subclause (subclause x.10) defines the additional requirements when one or more networkentities and/or the mobile station does not support Long Forwarded-to Numbers.

0.6 Data stored in the HLR for all call forwarding servicesThe following data are stored in the HLR in common for all call forwarding services:

- The “notification to CSE flag”. This flag applies for all call forwarding services. When the data for any CallForwarding are changed, the HLR checks this flag. If the flag is set, the change is reported to the gsmSCF(s)defined by the gsmSCF address list. See 3G TS 23.078.

- The “gsmSCF address list”, which is a list of gsmSCF addresses to which Notification on Change of SubscriberData is to be sent. This list applies to all call forwarding services. See 3G TS 23.078.

ETSI


1 Call forwarding unconditional (CFU)

1.1 Handling of call forwarding unconditional

1.1.1 Registration

At the beginning of registration subscription to the basic service, provision of the supplementary service and sufficiencyof registration information has to be checked (see figure 1.2).

The following information has to be registered in the network:

1) the forwarded-to number (possibly including a sub-address);

2) information as to whether all calls or all calls of a specific basic service group should be forwarded.

The basic service group code

If the registration request received by the HLR does not contain any basic service group code, the registration shall beperformed for all subscribed basic service groups for which CFU is provided, see figure 1.2.

The forwarded-to number

If the forwarded-to number is a number in the HPLMN country, it may be entered by the served mobile subscriber inthree different formats, independent of his actual location, according to the schemes:

1) national (significant) number;

2) (trunk) prefix plus national (significant) number;

3) international prefix, country code, national (significant) number.

The received number may have to be converted to an international number before further processing.

The network may also validate the forwarded-to number before accepting the call forwarding registration request.

If a served mobile subscriber is provided with the Translation Information Flag (TIF-CSI) as part of the CAMELsubscriber data (refer to TS 23.078), the network shall accept and store the forwarded-to number transparently at thetime of registration. In this case the network shall neither convert nor validate the received number. Therefore theforwarded-to number may not comply with the schemes indicated above.

For further details related to the handling of the forwarded-to number refer to figure 1.2.

Supplementary Service interaction

Possible interaction situations between CFU and other call forwarding and barring supplementary services must then bechecked. This is described in figure 1.2. Also see technical specifications 3G TS 22.004 and 3G TS 22.082. Forinteraction between CFU and other supplementary services (ie not call barring or call forwarding services), the reader isreferred to the respective technical specification for those supplementary services.

Interaction with CAMEL Phase 2 or higher

Possible interaction between CFU and CAMEL Phase 2 or higher is described in figure 1.2. If CAMEL Phase 2 orhigher is not supported in the HLR, processing continues from the "No" exit of the test "Result=Pass".

Notifications to the subscriber

When the mobile subscriber registers CFU, the network shall attempt to register and activate the service. The networkwill return notification of acceptance of the request. This notification will include the forwarded-to number and possiblythe basic service group code to which CFU is registered.

If the system cannot accept a registration request, the network sends a notification that CFU registration was notsuccessful to the served mobile subscriber.

The information flow for registration of CFU is shown in figure 1.1.

ETSI


MS MSC VLR HLR FFFFF FFFFF FFFFF FFFFF

G G G G G G G G

G G 5HJLVWHU &)8 G G G G G G

G G��!G G G G G G

G G G G5HJLVWHU &)8G G G G

G G G G��!G G G G

G G G G G G5HJLVWHU &)8G G

G G G G G G��!G G

G G G G G G G&)8�G G G G G G G $FNQRZOHGJHG G

G G G G G G��G G

G G G G $FNQRZOHGJHG G G G

G G G G��G G G G

G G5HOHDVH FRPSOHWHG G G G G G

G G��G G G G G G

G G ?)DFLOLW\ G G G G G G

Figure 1.1: Registration of call forwarding unconditional

ETSI


Process CFU1 382_12(1)

BS: Basic Service group. ftn: forwarded-to number. CCF: "Conditional" Call Forwarding. BAOC: Barring of All Outgoing Calls. BOIC: Barring of Outgoing International Calls. BOIC-exHC: Barring of Outgoing International Calls - except those directed to HPLMN Country. BAIC: Barring of All Incoming Calls. BIC-Roam: Barring of Incoming Calls when Roaming outside the home PLMN country.

idle

registerCFU

BSincluded in

request

set BS =all BS

CFUprovided

subset ofrequired BS

provided

BAICactive

BAOCactive

CAMEL_Check_CF_Interaction

See GSM 03.78

Result =PASS

validftn

Not, e.g.: - special service number; - own number.

numbertype

convert tointernational

(from HPLMN)

12 3

2

seterror

acknowledge

idle

1

BOIC/BOIC-exHC

activeftn

in HPLMNcountry

make any operativeBIC-Roam and CCFservices quiescent

setresult

3

no

yes

yes

no

no

No

yes

national

international

no

yes

yes

yes

no

no

yes

yes

yes

no

no

Figure 1.2: CFU1 Call forwarding unconditional registration process

ETSI


1.1.2 Erasure

A previous registration can be erased in either of the following three ways:

- the subscriber can specifically erase a previous registration (to a basic service group) with an appropriate controlprocedure;

- the subscriber can register information for CFU (to a basic service group), thus causing previous registrations ofCFU to be overridden (in the network this shall be handled as an erasure immediately followed by aregistration);

- all information is erased as a result of withdrawal of the supplementary service (administrative handling).

The basic service group code

If the erasure request received by the HLR does not contain any basic service group code, the erasure request applies forall basic service groups for which CFU is registered. See figure 1.4.

Supplementary Service interaction

Possible interaction situations between CFU and other supplementary services must then be checked. This is shown infigure 1.4. Also see technical specifications 3G TS 22.004 and 3G TS 22.082. For interaction between CFU and othersupplementary services (ie not call barring or call forwarding services), the reader is referred to the respective technicalspecification for those supplementary services.

Notifications to the subscriber

When the mobile subscriber erases CFU, the network shall attempt to erase (and thus deactivate) the service. Thenetwork shall send an indication of acceptance or rejection of the erasure request to the served mobile station.

The information flow for erasure of CFU is shown in figure 1.3.


G G (UDVH &)8 G G G G G G

G G��!G G (UDVH &)8 G G G G

G G G G��!G G (UDVH &)8 G G


G G G G G G G&)8�G G G G G G G $FNQRZOHGJHG G

G G5HOHDVH FRPSOHWHG G $FNQRZOHGJHG G��G G

G G��G G��G G G G


G G G G G G G G

Figure 1.3: Erasure of call forwarding unconditional

ETSI


Process CFU2 382_14(1) BS: Basic Service group. CCF: "Conditional" Call Forwarding. BIC-Roam: Barring of Incoming Calls when Roaming outside the home PLMN country.

idle

eraseCFU

BS includedin request

set BS =all BS

CFUprovided

make any quiescentBIC-Roam and CCFservices operative

setresult

acknowledge

idle

seterror

no

yes

no

yes

Figure 1.4: CFU2 Call forwarding unconditional erasure process

ETSI


1.1.3 Activation

The network initially checks subscription to the basic service and registration status of the supplementary service, seefigure 1.6.

Possible interaction situations between CFU and other supplementary services must then be checked. The SDLdiagrams in figure 1.6 shows the function to be performed in the HLR in order to deal with the interactions betweenCFU and the call restriction and conditional call forwarding services. Also see 3G TS 22.004 and 3G TS 22.082. Forinteraction between CFU and other supplementary services (ie not call barring or call forwarding services), the reader isreferred to the respective technical specification for those supplementary services.

The Basic Service Group Code

If the activation request received by the HLR doesn't contain any basic service group code, the activation request shallapply to all subscribed basic service groups against which a CFU forwarded-to number is registered. If a forwarded-tonumber is not registered against even a subset of the required basic service group, the request will be rejected.

Note that according to 3G TS 22.004, a request for activation shall still be accepted although the CFU supplementaryservice was already active for all basic service groups.

Notification to the subscriber

The network will return notification of acceptance, partial acceptance or rejection of the request to the mobile station.

The information flow for activation of CFU is shown in figure 1.5.

MS MSC VLR HLRFFF FFFF FFFF FFFFF

G G $FWLYDWH &)8 G G G G G G

G G��!G G $FWLYDWH &)8 G G G G

G G G G��!G G $FWLYDWH &)8 G G


G G G G G G G&)8�GG G G G G G $FNQRZOHGJH G G


G G G G $FNQRZOHGJH G G G G





G G G G G G G G

Figure 1.5: Activation of call forwarding unconditional

ETSI


Process CFU3 382_16(1) CCF: "Conditional" Call Forwarding. BS: Basic Service group. ftn: forwarded-to number. BAIC: Barring of All Incoming Calls. BAOC: Barring of All Outgoing Calls. BOIC: Barring of Outgoing International Calls. BOIC-exHC: Barring of Outgoing International Calls - except those directed to HPLMN Country.

idle

activateCFU

CFU registeredfor required BS

BAICactive

BAOCactive

BOIC/BOIC-exHC

active

ftn inHPLMN country

make any operativeBIC-Roam and CCF services

quiescent

setresult

acknowledge

idle

seterror

seterror

yes

no

no

yes

yes

no

no

yes

yes

no

Figure 1.6: CFU3 Call forwarding unconditional activation process

ETSI


1.1.4 Deactivation

The previous activation can be deactivated in either of the following three ways:

- the subscriber can specifically deactivate a previous activation (to a basic service group) with an appropriatecontrol procedure;

- the subscriber can register information for CFU (to a basic service group), thus causing previous registrationsand activations of CFU to be overridden (this shall be handled in the same way as an erasure (implyingdeactivation) immediately followed by a registration (implying activation));

- the service is deactivated as a result of withdrawal of the supplementary service (administrative handling).

Possible interaction situations between CFU and other supplementary services must be checked. The SDL diagram infigure 1.8 shows the function to be performed in the HLR in order to deal with the possible interactions between CFUand the conditional call forwarding services.

The Basic Service Group Code

The CFU deactivation request may specify a basic service group for which deactivation is required. If the deactivationrequest received by the HLR doesn't contain any basic service group code, the deactivation request shall apply to allbasic services for which CFU is active, see figure 1.8.

If the deactivation request received by the HLR contains a basic service group code, only information related to thespecified basic service group(s) is affected. Note that according to 3G TS 22.004, a request for deactivation shall still beaccepted even if the CFU supplementary service was already deactive for all basic service groups.

The user shall receive a notification of acceptance or rejection of the CFU deactivation request.

The information flow for deactivation of call forwarding unconditional is shown in figure 1.7.


G G'HDFWLYDWH &)8 G G G G G G

G G��!G G'HDFWLYDWH &)8 G G G G

G G G G��!G G'HDFWLYDWH &)8G G


G G G G G G G&)8�GG G G G G G $FNQRZOHGJH G G

G G G G $FNQRZOHGJH G G��G G

G G5HOHDVH FRPSOHWHG G��G G G G



Figure 1.7: Deactivation of call forwarding unconditional

ETSI


Process CFU4 382_18(1)

BS: Basic Service group. BIC-Roam: Barring of Incoming Calls when Roaming outside the home PLMN country.

idle

deactivateCFU

BSincluded

in request

set BS =all BS

CFUactive forsubset BS

BIC-Roam orconditional forwarding

quiescent

make quiescentservicesoperative

setresult

acknowledge

idle

seterror

no

yes

yes

no

no

yes

Figure 1.8: CFU4 Call forwarding unconditional deactivation process

ETSI


1.1.5 Interrogation

Data request

The data request procedure enables the mobile subscriber to obtain information about the data stored in the PLMN.Interrogation of CFU is handled by the HLR which returns the required information or error to the MS, see figure 1.9.

MS MSC VLR HLRFFF FFFF FFFF FFFF

G G,QWHUURJDWH &)8 G G G G G G


G G G G,QWHUURJDWH &)8G G G G


G G G G G G,QWHUURJDWH &)8G G


G G G G G G G G

G G G G G G $FNQRZOHGJH G G







G G G G G G G G

Figure 1.9: Interrogation of call forwarding unconditional

1.2 Functions and information flowsThe following Mobile Additional Function has been identified for the PLMN:

MAF007

Call forwarding unconditional authorizations examination

The ability of a PLMN component to determine the authorizations relating to CFU.

See figure 1.10.

Location: HLR.

The information flow for call forwarding unconditional is shown in figure 1.11.

ETSI


Process MAF007 382_1A(1)

BS : Basic Service group.

idle

initiatehandlingof CFU

activefor this

BS

numberof forwardings

reached

increment counterget forwarded-to number

set forwarding cause=CFU

notification tocalling subscriber

set indicator ='notify callingsubscriber'

served subscribersMSISDN can be

presented

set redirectingpresentation =

restricted

continuecallhandling

idle


allowed

seterror

set indicator ='set up

normal call'

yes

no

yes

no

yes

no

yes

no

Figure 1.10: MAF007 Call forwarding unconditional authorisations examination (HLR)

ETSI


MSa/TEa GMSC HLRb MSCb LEc ßFFFFFFF FFFFFFF FFFFFFF FFFFF FFFFFFF

G G G G G G G G G G

G G 6HW�XS G G G G G G G G

G G��!G G ,QIR UHTXHVW G G G G G G

G G G G��!G G G G G G

G G G G G G G G G G

G G G G ,QIR DFN G0$)��G G G G G

G G G G��G G G G G G

G G G G G G G G G G

G G G G 6HW�XS G G G G G G

G G G25��1 G��!G G G G

G G G G G G G G G G


G G G25��< G��!G G

G G G G G G G G G G

G G 1RWLILFDWLRQ G G G G G G G G

G G��G25��< G G G G G G G

G G G G G G G G G G

MSa/TEa GMSC HLRb MSCb HLRc SCcßFFFFF FFFFFFF FFFFFFF FFF FFF FFF

G G G G G G G G G G G G

G G 6HW�XS G G G G G G G G G G

G G��!G G ,QIR UHTXHVW G G G G G G G G

G G G G��!G G G G G G G G


G G G G ,QIR DFN G0$)��G G G G G G G

G G G G��G G G G G G G G


G G G G 6HW�XS G G G G G G G G

G G G25��1 G��!G G G G G G


G G G G ,QIRUPDWLRQ UHTXHVW G G G G G G

G G G25��< G��!G G G G


G G G G ,QIRUPDWLRQ DFNQRZOHGJH G G G G G G




G G G G��!G G

G G 1RWLILFDWLRQ G G G G G G G G G G

G G��G25��< G G G G G G G G G


NOTE: info: information Y: Yesreq: request N: Noack: acknowledgeOR1: Forwarding requestedOR2: Notification to calling subscriber required

Figure 1.11: Information flow for call forwarding unconditional

1.3 Information stored in the HLRThe following logical states are applicable for CFU (refer to 3G TS 23.011 for an explanation of the notation):

Provisioning State Registration State Activation State HLR Induction State

(Not Provisioned, Not Registered, Not Active, Not Induced)

(Provisioned, Not Registered, Not Active, Not Induced)

(Provisioned, Registered, Not Active, Not Induced)

(Provisioned, Registered, Active and Quiescent, Not Induced)

(Provisioned, Registered, Active and Operative, Not Induced)

The registration and activation state may be different for each applicable elementary basic service group.

The provisioning state shall be on a per subscriber basis, and hence the same for all basic service groups.

ETSI


The HLR shall store:

- the state of CFU (which shall be one of the valid states listed above) for each applicable elementary basic servicegroup;

- the subscription option "notification to the calling party" on a per subscriber basis;

This subscription option takes one of the following values:

- no notification;

- notification.

- the subscription option "MSISDN of the served subscriber can be presented to the forwarded-to subscriber" on aper subscriber basis;


- presentation restricted;

- presentation allowed.

- the registration parameter "forwarded-to number" (possibly including a forwarded-to sub-address) for eachapplicable elementary basic service group.

- the default forwarded-to number (containing less than 16 digits) for each applicable elementary basic servicegroup.

Note that the value "Active and Quiescent" of the activation state is required in case of interaction with OperatorDetermined Barring (see 3G TS 23.015).

1.4 State transition modelThe following figure shows the successful cases of transition between the applicable logical states of CFU. The statechanges are either caused by actions of the service provider, the mobile user or the network.

Note that error cases are not shown in the diagram as they normally do not cause a state change. Additionally, somesuccessful requests may not cause a state change. Hence, they are not shown in the diagram.

The diagram only shows operations on an elementary basic service group.

ETSI


(N ot P rov is ioned ,N o t R egis tered,

N o t A ctive ,N o t Induced)

(P rov is ioned ,N o t R egis te red,

N ot A ctive ,N o t Induced)

(P rovis ioned ,R eg is tered ,

A ctive and Q uiescen t,N ot Induced)

P rovis ion

(P rov is ioned,R eg iste red ,N o t A ctive ,

N o t Induced)

(P rov is ioned,R egiste red,

A ctive and O pera tive ,N o t Induced)

D eactiva tion

A ctiva tion

D eactiva tion

E rasure

R eg is trationE rasureE rasure S S In te rac tion s tarted

S S In te rac tion ended

W ithdraw al

W ithdraw alW ithd rawa lW ithd raw al

Figure 1.12: State transition model for CFU

1.5 Transfer of information from HLR to VLRIf the provisioning state for CFU is "Provisioned" then, when the subscriber registers on a VLR, the HLR shall send thatVLR information about the logical state of CFU for all relevant elementary basic service groups.

If the logical state of CFU is changed while a subscriber is registered on a VLR then for the affected basic servicegroups, the HLR shall inform the VLR of the new logical state of CFU.

1.6 Information stored in the VLRFor CFU the VLR shall store the service state information received from the HLR for all relevant elementary basicservice groups.

1.7 HandoverHandover will have no impact on the control procedure and the operation of the service.

1.8 Cross phase compatibility

1.8.1 MS, MSC, VLR or HLR only support Phase 1 control of SS by thesubscriber

In response to a CFU interrogation request, if the MS or any network element involved is of Phase 1, only informationconcerning basic service groups for which the activation state has the value "Active and Operative" will be returned.

ETSI


This means, for example, that the subscriber will not be aware that the forwarded to number is registered if CFU isdeactivated. A subaddress (if registered) will not be included in the response.

Note that if any network element involved is of Phase 1, CFU Registration requests which use a subaddress and all CFUActivation and Deactivation requests will be rejected, as these are not specified in Phase 1.

1.8.2 HLR only supports Phase 1 updating of subscriber information

The VLR shall ignore the subscription option "notification to the calling party" and the registration parameter"forwarded to number" when received from a Phase 1 HLR.

If the VLR receives the SS-Status parameter from a Phase 1 HLR it shall act if it has received the SS-Status parameterwith the values shown in the following:

1) Activated => A bit = 1, Q bit = 0;

2) Deactivated => A bit = 0, Q bit = 0 or 1

1.8.3 VLR only supports Phase 1 updating of subscriber information

When passing CFU information to a Phase 1 VLR, the HLR shall send the service state information in a form which theVLR can accept, based on the logical state held in the HLR, as follows:

1) (Provisioned, Not Registered, Not Active, Not Induced)

=> Erased, Deactivated;

2) (Provisioned, Registered, Not Active, Not Induced)

=> Registered, Deactivated;

3) (Provisioned, Registered, Active and Operative, Not Induced)

=> Registered, Activated;

4) (Provisioned, Registered, Active and Quiescent, Not Induced)

=> Registered, Deactivated.

The HLR shall not pass a subaddress to a Phase 1 VLR.

1.8.4 GMSC only supports Phase 1 call handling

When a call is forwarded unconditionally, the HLR shall not pass the subaddress to a Phase 1 GMSC. Calls shall beforwarded without the subaddress.

1.8.5 GMSC does not support CAMEL or supports CAMEL Phase 1 only

If the activation state of CFU is "Active and Operative" and if the forwarded-to number is registered in a format otherthan international and if the GMSC does not support CAMEL or supports CAMEL Phase 1 only, then when a requestfor routeing information for a mobile terminated call is received in the HLR, CFU shall not be invoked, i.e. the mobileterminated call establishment will be continued towards the served mobile subscriber.

1.9 Contents of Messages

1.9.1 Messages on the C interface (MSC-HLR)

1.9.1.4 Send Routing Info

This message is specified in 3G TS 23.018.

ETSI


Send Routing Info contains the following IE specific to Long Forwarded-to Numbers:

Information element name Required DescriptionLong FTN supported C Shall be present if the GMSC supports Long Forwarded-to

Numbers; otherwise shall be absent.

1.9.1.2 Send Routing Info ack


Send Routing Info ack contains the following amendment to the Forwarded-to number IE and an additional IE specificto Long Forwarded-to Numbers:

Information element name Required DescriptionForwarded-to number C E.164 number of the C subscriber. Shall be present if the HLR has

determined that the call is to be forwarded and at least one of theHLR and GMSC does not support Long Forwarded-to Numbers;otherwise shall be absent.

Long forwarded-to number C Number of the C subscriber. Shall be present if the HLR hasdetermined that the call is to be forwarded and Long Forwarded-toNumbers are supported by the HLR and the GMSC; otherwiseshall be absent.

1.9.2 Messages on the Um, B and D interfaces (MS – network)

1.9.2.1 RegisterSS

This message corresponds to the MAP_REGISTER_SS service specified in 3G TS 29.002.

Information element name Required DescriptionLong FTN supported C Shall be present if the MS supports Long Forwarded-to Numbers;

otherwise shall be absent.

1.9.2.2 ActivateSS

This message corresponds to the MAP_ACTIVATE_SS service specified in 3G TS 29.002.



1.9.2.3 InterrogateSS

This message corresponds to the MAP_INTERROGATE_SS service specified in 3G TS 29.002.



1.9.3 Information flows on the J interface (HLR – gsmSCF)

1.9.3.1 Any Time Subscription Interrogation

This IF is specified in 3G TS 23.078.

Any Time Subscription Interrogation contains the following IE specific to Long Forwarded-to Numbers:

ETSI


Information element name Required DescriptionLong FTN supported C Shall be present if the gsmSCF supports Long Forwarded-to


1.9.3.2 Any Time Subscription Interrogation ack


The Call forwarding SS data IE within the Any Time Subscription Interrogation ack IF contains the followingamendment to the Forwarded-to number IE and an additional IE specific to Long Forwarded-to Numbers:

Information element name Required DescriptionForwarded-to number C Shall be present if at least one of the HLR and the gsmSCF does

not support Long Forwarded-to Numbers; otherwise shall beabsent.

Long forwarded-to number C Shall be present if the HLR and the gsmSCF support LongForwarded-to Numbers; otherwise shall be absent.

1.9.3.3 Any Time Modification


Any Time Modification contains the following IE specific to Long Forwarded-to Numbers:

Information element name Required DescriptionLong FTN supported C Shall be present if the gsmSCF supports Long Forwarded-to


1.9.3.4 Any Time Modification ack


The Call forwarding SS data IE within the Any Time Modification ack IF contains the following amendment to theForwarded-to number IE and an additional IE specific to Long Forwarded-to Numbers.

Information element name Required DescriptionForwarded-to number C Shall be present if at least one of the HLR and the gsmSCF does

not support Long Forwarded-to Numbers; otherwise shall beabsent.

Long forwarded-to number C Shall be present if the HLR and the gsmSCF support LongForwarded-to Numbers; otherwise shall be absent.

1.10 Exceptional Procedures

1.10.1 MS does not support Long Forwarded-to Numbers

The MS shall indicate whether it supports Long Forwarded-to Numbers in the RegisterSS, ActivateSS andInterrogateSS messages.

If the MS does not support Long Forwarded-to Numbers, and a long forwarded-to number is registered, theacknowledgement message shall contain a truncated version of the registered long forwarded-to number (i.e. the leading15 digits of the registered long forwarded-to number).

1.10.2 HLR does not support Long Forwarded-to Numbers

The HLR shall not allow a subscriber to register a long forwarded-to number.

ETSI


1.10.3 GMSC does not support Long Forwarded-to Numbers

The HLR can determine from the Send Routing Info message whether the GMSC supports Long Forwarded-toNumbers.

If the GMSC does not support Long Forwarded-to Numbers and the HLR identifies that CFU should be invoked, then:

- If the registered forwarded-to number contains a maximum of 15 digits then the HLR shall populate theForwarded-to number parameter in the Send Routing Info ack message with the registered forwarded-tonumber.

- If the registered forwarded-to number contains more than 15 digits then, as a network option, the HLR can:

- Populate the Forwarded-to number parameter in the Send Routing Info ack message with an alternativeforwarded-to number (containing a maximum of 15 digits), or

- Allow the call to continue without invoking CFU, or

- Release the call.

2 Call forwarding on mobile subscriber busy

2.1 Handling of call forwarding on mobile subscriber busy

2.1.1 Registration

The same rules apply for the registration of Call Forwarding on Mobile Subscriber Busy as were described for CallForwarding Unconditional in subclause 1.1.1 above, with the exception of the checking of interaction with othersupplementary services. Basic registration of information is illustrated in figure 2.2.

Supplementary Service Interaction

Possible interaction situations between CFB and other supplementary services must then be checked. This is describedin figure 2.2. Also see 3G TS 22.004 and 3G TS 22.082. For interaction between CFB and other supplementary services(ie not call barring or call forwarding services), the reader is referred to the respective technical specification for thosesupplementary services.


Possible interaction between CFB and CAMEL Phase 2 or higher is described in figure 2.2. If CAMEL Phase 2 orhigher is not supported in the HLR, processing continues from the "No" exit of the test "Result=Pass".

The information flow for registration of CFB is shown in figure 2.1.


G G G G G G G G

G G 5HJLVWHU &)% G G G G G G


G G G G5HJLVWHU &)%G G G G


G G G G G G5HJLVWHU &)%G G


G G G G G G G&)%�G G G G G G G $FNQRZOHGJHG G







G G G G G G G G

Figure 2.1: Registration of call forwarding on mobile subscriber busy

ETSI


Process CFB1 382_22(1)

BS: Basic Service group. ftn: forwarded-to number. BAOC: Barring of All Outgoing Calls. BOIC: Barring of Outgoing International Calls. BOIC-exHC: Barring of Outgoing International Calls except those directed to HPLMN Country. BAIC: Barring of All Incoming Calls. BIC-Roam: Barring of Incoming Calls when Roaming outside the home PLMN country.

idle

registerCFB


set BS =all BS

CFBprovided


provided

BAICactive

BAOCactive


See GSM 03.78

Result =Pass?

validftn


numbertype


(from HPLMN)

12 3

1

BOICactive

BOIC-exHCactive

ftn in VPLMNcountry

ftn in HPLMNcountry

BIC-Roamactive

roamingoutside HPLMN

country

CFUactive

seterror

acknowledge

idle

setresult

seterror

ftn in VPLMNcountry

3

2

no

yes

yes

no

no

no

yes

national

international

no

yes

yes

yes

no

no

yes

no

yes

no

yes

yes

no

yes

no

yesno

no

yes no

yes

yes

no

Figure 2.2: CFB1 Call forwarding on mobile subscriber busy registration process

ETSI


2.1.2 Erasure

The same rules apply for the erasure of CFB as were described for CFU in subclause 1.1.2 above. However, no checksfor interaction with other supplementary services are required for erasure of CFB, see figure 2.4.

The information flow for registration of CFB is shown in figure 2.3.


G G G G G G G G

G G (UDVH &)% G G G G G G


G G G G (UDVH &)% G G G G


G G G G G G (UDVH &)% G G


G G G G G G G&)%�G G G G G G G $FNQRZOHGJHG G







G G G G G G G G

Figure 2.3: Erasure of call forwarding on mobile subscriber busy

ETSI



BS: Basic Service group.idle

eraseCFB

BSincluded

in request

set BS =all BS

CFBprovided

seterror

acknowledge

idle

setresult

no

no

yes

yes

Figure 2.4: CFB2 Call forwarding on mobile subscriber busy erasure process

ETSI


2.1.3 Activation

The same rules apply for the activation of CFB as were described for CFU in subclause 1.1.3 above, with the exceptionof the checking of interaction with other supplementary services. Basic activation of CFNRc is illustrated in figure 2.6.


Possible interaction situations between CFB and other supplementary services must then be checked. This is describedin figure 2.6. Also see 3G TS 22.004 and 3G TS 22.082. For interaction between CFB and other supplementary services(ie not call barring or call forwarding services), the reader is referred to the respective technical specification for thosesupplementary services.

The information flow for activation of call forwarding on MS busy is shown in figure 2.5.


G G $FWLYDWH &)% G G G G G G

G G��!G G $FWLYDWH &)% G G G G

G G G G��!G G $FWLYDWH &)% G G


G G G G G G G&)%�GG G G G G G $FNQRZOHGJH G G





G G G G G G G G

Figure 2.5: Activation of call forwarding on MS busy

ETSI


Process CFB3 382_26(1) BS: Basic Service group. ftn: forwarded-to number. BAOC: Barring of All Outgoing Calls. BOIC: Barring of Outgoing International Calls. BOIC-exHC: Barring of Outgoing International Calls - except those directed to HPLMN Country. BAIC: Barring of All Incoming Calls.

idle

activateCFB

CFB registeredfor required BS

BAICactive

BIC-Roamactive


country

BAOCactive

BOICactive

BOIC-exHCactive

ftn in VPLMNcountry

ftn in HPLMNcountry

CFUactive

setresult

acknowledge

idle

seterror

seterror

ftn in VPLMNcountry

seterror

seterror

yes

no

yes

no

no

no

yes

no

yes

no

yesno

yes no

yes

yes no

yesyes

no

yes

no

Figure 2.6: CFB3 Call forwarding on mobile subscriber busy activation process

ETSI


2.1.4 Deactivation

The same rules apply for the deactivation of CFB as were described for CFU in subclause 1.1.4 above, see figure 2.8.

The information flow for deactivation of call forwarding on mobile subscriber busy is shown in figure 2.7.


G G'HDFWLYDWH &)% G G G G G G

G G��!G G'HDFWLYDWH &)% G G G G

G G G G��!G G'HDFWLYDWH &)%G G


G G G G G G G&)%�GG G G G G G $FNQRZOHGJH G G







G G G G G G G G

Figure 2.7: Deactivation of call forwarding on mobile subscriber busy

ETSI




deactivateCFB


set BS =all BS

CFB active forsubset BS

seterror

acknowledge

idle

setresult

no

no

yes

yes

Figure 2.8: CFB4 Call forwarding on mobile subscriber busy deactivation process

ETSI


2.1.5 Interrogation

Data request

The data request procedure enables the mobile subscriber to obtain information about the data stored in the PLMN.Interrogation of CFB is handled by the VLR which returns the required information or error to the MS, see figure 2.9.

MS MSC VLR HLRFFF FFFF FFFF FFFF

G G G G G G G G

G G,QWHUURJDWH &)% G G G G G G


G G G G,QWHUURJDWH &)%G G G G


G G G G G G G G






G G G G G G G G

Figure 2.9: Interrogation of call forwarding on mobile subscriber busy


MAF008

Call forwarding on mobile subscriber busy authorizations examination

The ability of a PLMN component to determine the authorizations relating to call forwarding on mobilesubscriber busy. See figure 2.10.

Location: VLR.

The information flows for forwarding to fixed terminal and to mobile station are shown in figures 2.11 & 2.12 and 2.13& 2.14 respectively.

ETSI



NDUB: Network Determined User Busy. UDUB: User Determined User Busy. BS: Basic Serice group.

idle

initiatehandlingof CFB

activefor this BS


reached


set forwarding cause=CFB

UDUB orNDUB

notificationto forwarding

subscriberset indicator =

'notify forwardingsubscriber'

notificationto calling

subscriberset indicator ='notify callingsubscriber'


presented


restricted


idle


allowedset error

set indicator ='normal call

busy'

yes

no

NDUB

yes

yes

no

yes

no

no

UDUB

yes

no

Figure 2.10: MAF008 Call forwarding on mobile subscriber busy authorisations examination (VLR)

ETSI


MSa/TEa GMSC HLRb VLRb MSCb MSb LEcFFFF FFFFF FFFFF FFFFFFF FFFFFF FFFFF FFFFF

G G G G G G G G G G G G G G

G G 6HW�XS G G G G G G G G G G G G

G G��!G G,QIR UHT G G G G G G G G G G

G G G G��!G G G G G G G G G G


G G G G,QIR DFN G G G G G G G G G G

G G G G��G G G G G G G G G G





G G G G G G G G ,QIR UHTXHVW G G G G G G

G G G G G G G G��G G G G G G


G G G G G G G G 3DJH 06 G G G G G G

G G G G G G G G��!G G G G G G

G G G G G G G G G1'8% G G G G G

G G G G G G G G%XV\ VXEVFULEHU G G G G G G


G G G G G G G G �1'8%� G G G G G G

G G G G G G G0$)��G G G G G G G


G G G G G G G25��1 G ,PSRVVLEOH FDOOG G G G G G

G G G G G G G G FRPSOHWLRQ G G G G G G


G G G G 5HOHDVH G G G G G G

G G 5HOHDVH G G��G G G G G G

G G��G G G G G G G G G G G G


G G G G G G G25��< G&RQQHFW WR IRO� G G G G G G

G G G G G G G GORZLQJ DGGUHVV G G G G G G

G G G G G G G G��!G G 6HW�XS G G

G G G G G G G G G G��!G G


G G G G G G G G G G 1RWLI G G G G

G G G G G G G G G25��<G��!G G G G



G G G G 1RWLILFDWLRQ G25��<G G G G G

G G1RWLILFDWLRQG G��G G G G G G



NOTE: NDUB: Network Determined User Busyinfo: information Y: Yesreq: request N: Noack: acknowledgenotif: notificationOR1: Call to be forwardedOR2: Notification to forwarding subscriber requiredOR3: Notification to calling subscriber required

Figure 2.11: Information flow for call forwarding on mobile subscriber busy(to fixed terminal) (NDUB)

ETSI


MSa/TEa GMSC HLRb VLRb MSCb MSb LEcFFFF FFFFF FFFFF FFFFFFF FFFFFF FFFFFF FFFF






G G G G,QIR DFN G G G G G G G G G G






G G G G G G G G ,QIR UHTXHVW G G G G G G




G G G G G G G G��!G G6HW�XS G G G G

G G G G G G G G G G��!G G G G

G G G G G G G G G G G8'8% G G G

G G G G G G G G G G 8'8% G G G G

G G G G G G G G%XV\ VXEVFULEHU G G��G G G G


G G G G G G G G �8'8%� G G G G G G



G G G G G G G25��1 G,PSRVVLEOH FDOO G G G G G G




G G 5HOHDVH G G��G G G G G G



G G G G G G G25��< G&RQQHFW WR IRO� G G G G G G

G G G G G G G GORZLQJ DGGUHVV G G G G G G





G G1RWLILFDWLRQG G��G G G G G G



NOTE: UDUB: User Determined User Busyinfo: information Y: Yesreq: request N: Noack: acknowledgenotif: notificationOR1: Call to be forwardedOR2: Notification to calling subscriber required

Figure 2.12: Information flow for call forwarding on mobile subscriber busy(to fixed terminal) (UDUB)

ETSI


MSa/TEa GMSC HLRb VLRb MSCb MSb HLRc MSCcFFFF FFFF FFFF FFFFFFF FFFFFF FFFFF FFFFF FFFF

G G G G G G G G G G G G G G G G

G G6HW�XS G G G G G G G G G G G G G G

G G��!G G,QIR UHTG G G G G G G G G G G G

G G G G��!G G G G G G G G G G G G


G G G G,QIR DFNG G G G G G G G G G G G

G G G G��G G G G G G G G G G G G





G G G G G G G G ,QIR UHTXHVW G G G G G G G G

G G G G G G G G��G G G G G G G G


G G G G G G G G 3DJH 06 G G G G G G G G

G G G G G G G G��!G G G G G G G G

G G G G G G G G G1'8% G G G G G G G

G G G G G G G G%XV\ VXEVFULEHU G G G G G G G G


G G G G G G G0$)��G �1'8%� G G G G G G G G


G G G G G G G25��1 G,PSRVVLEOH FDOO G G G G G G G G

G G G G G G G G FRPSOHWLRQ G G G G G G G G


G G G G 5HOHDVH G G G G G G G G

G G5HOHDVHG G��G G G G G G G G

G G��G G G G G G G G G G G G G G


G G G G G G G25��< G&RQQHFW WR IRO� G G G G G G G G

G G G G G G G G ORZLQJ DGGUHVV G G G G G G G G

G G G G G G G G��!G G,QIRUPDWLRQ UHT G G G G



G G G G G G G G G G,QIRUPDWLRQ DFN G G G G

G G G G G G G G G G��G G G G


G G G G G G G G G G 6HW�XS G G



G G G G G G G G G G1RWLIG G G G G G

G G G G G G G G G25��<G��!G G G G G G


G G G G 1RWLILFDWLRQ G25��<G G G G G G G

G G 1RWLI G G��G G G G G G G G



NOTE: NDUB: Network Determined User Busyinfo: information Y: Yesreq: request N: Noack: acknowledgenotif: notificationOR1: Call to be forwardedOR2: Notification to forwarding subscriber requiredOR3: Notification to calling subscriber required

Figure 2.13: Information flow for call forwarding on mobile subscriber busy(to mobile station) (NDUB)

ETSI


MSa/TEa GMSC HLRb VLRb MSCb MSb HLRc MSCcFFFF FFFF FFFF FFFFFFF FFFFFF FFFFF FFFF FFFF



G G��!G G,QIR UHT G G G G G G G G G G G G



G G G G,QIR DFN G G G G G G G G G G G G






G G G G G G G G ,QIR UHTXHVW G G G G G G G G




G G G G G G G G��!G G 6HW�XSG G G G G G

G G G G G G G G G G��!G G G G G G

G G G G G G G G G G G8'8%G G G G G

G G G G G G G G G G 8'8% G G G G G G

G G G G G G G G%XV\ VXEVFULEHUG G��G G G G G G


G G G G G G G0$)��G �8'8%� G G G G G G G G


G G G G G G G25��1 G,PSRVVLEOH FDOOG G G G G G G G







G G G G G G G25��< G&RQQHFW WR IRO�G G G G G G G G

G G G G G G G GORZLQJ DGGUHVV G G G G G G G G

G G G G G G G G��!G G ,QIRUPDWLRQ UHT G G G G



G G G G G G G G G G ,QIRUPDWLRQ DFN G G G G





G G G G 1RWLILFDWLRQ G25��<G G G G G G G




NOTE: UDUB: User Determined User Busyinfo: information Y: Yesreq: request N: Noack: acknowledgenotif: notificationOR1: Call to be forwardedOR2: Notification to calling subscriber required

Figure 2.14: Information flow for call forwarding on mobile subscriber busy(to mobile station) (UDUB)

2.3 Information stored in the HLRThe following logical states are applicable for CFB (refer to 3G TS 23.011 for an explanation of the notation):







ETSI





- the state of CFB (which shall be one of the valid states listed above) for each applicable elementary basic servicegroup;



- no notification;

- notification.

- the subscription option "notification to the forwarding party" on a per subscriber basis;


- no notification;

- notification.

the subscription option " MSISDN of the served subscriber can be presented to the forwarded-to subscriber" on a persubscriber basis;





2.4 State transition modelThe following figure shows the successful cases of transition between the applicable logical states of CFB. The statechanges are either caused by actions of the service provider, the mobile user or the network.

Note that error cases are not shown in the diagram as they normally do not cause a state change. Additionally, somesuccessful requests may not cause a state change. Hence, they are not shown in the diagram. The diagram only showsoperations on an elementary basic service group.

ETSI








P rovis ion


N o t Induced)



D eactiva tion

A ctiva tion

D eactiva tion

E rasure



W ithdraw al


Figure 2.15: State transition model for CFB

2.5 Transfer of information from HLR to VLRIf the provisioning state for CFB is "Provisioned" then, when the subscriber registers on a VLR, the HLR shall send thatVLR information about the logical state of CFB for all relevant elementary basic service groups.

If the registration state for CFB is "Registered" then, when the subscriber registers on a VLR, the HLR shall send thatVLR the registration parameter "forwarded-to number" for all relevant elementary basic service groups and informationabout the subscription options "notification to the calling party", "notification to the forwarding party" and "MSISDNof the served subscriber can be presented to the forwarded-to subscriber".

If the logical state or the registration parameter "forwarded-to number" of CFB is changed while a subscriber isregistered on a VLR then for the affected basic service groups, the HLR shall inform the VLR respectively of the newlogical state or the new registration parameter of CFB.

If information about the subscription options "notification to the calling party" and "notification to the forwardingparty" of CFB is changed while a subscriber is registered on a VLR and the registration state of CFB is "Registered"then the HLR shall inform the VLR of the new information about the subscription options of CFB.

2.6 Information stored in the VLRFor CFB the VLR shall store the service state information, the registration parameter "forward-to number" and thesubscription options received from the HLR.


ETSI




In response to a CFB interrogation request, if the MS or any network element involved is of Phase 1, only informationconcerning basic service groups for which the activation state has the value "Active and Operative" will be returned.This means that the subscriber will not be aware that the forwarded to number is registered if CFB is deactivated oractive (quiescent). A subaddress (if registered) will not be included.

Note that if any network element involved is of Phase 1, CFB Registration requests which use a subaddress and all CFBActivation and Deactivation requests will be rejected, as these are not specified in Phase 1.



1) Registered, Activated => P bit =1, R bit = 1, A bit = 1, Q bit = 0;

2) Registered, Deactivated => P bit =1, R bit = 1, A bit = 0, Q bit = 0 or 1;

3) Erased => P bit =1, R bit = 0, A bit = 0, Q bit = 0 or 1.


When passing CFB information to a Phase 1 VLR, the HLR shall send the service state information in a form which theVLR can accept, based on the logical state held in the HLR, as follows:










2.8.4 VLR only supports Phase 1 call handling

When a call is forwarded on busy, as the HLR does not pass the subaddress to the VLR, calls shall be forwardedwithout the subaddress.

2.8.5 VLR does not support CAMEL or supports CAMEL Phase 1 only

When passing CFB information to a VLR not supporting CAMEL or supporting CAMEL Phase 1 only, the HLR shallsend the registration parameter "forwarded-to number" only if it is registered in a format which the VLR can accept, i.e.international format.

If the registration state for CFB is "Registered" and the forwarded-to number is registered in a format other thaninternational, then when updating a VLR not supporting CAMEL or supporting CAMEL Phase 1 only the HLR shallmodify the service state information of CFB as follows.

ETSI



=> (Provisioned, Not Registered, Not Active, Not Induced)





According to the definitions in subclause 2.5 no forwarded-to number will be passed to the VLR in these cases. Themodification of the service state information sent to the VLR shall have no impact on the service state informationstored in the HLR.

If the VLR supports Phase 1 updating of subscriber information only, a further translation of the service stateinformation as defined in subclause 2.8.3 shall be performed by the HLR.

2.9 Contents of messagesThe same additions apply for CFB as for CFU, see subclause 1.9. The following additions are specific to CFB.

2.9.1 Messages on the B interface (MSC-VLR)

2.9.1.1 Send Info For Incoming Call ack


Send Info For Incoming Call ack contains the following amendment to the Forwarded-to number IE, specific to LongForwarded-to Numbers:

Information element name Required DescriptionForwarded-to number M Number of the C subscriber.

2.9.2 Messages on the D interface (VLR-HLR)

2.9.2.1 Insert Subscriber Data

This message corresponds to the MAP-INSERT-SUBSCRIBER-DATA service specified in 3G TS 29.002.

Insert Subscriber Data contains the following IE specific to Long Forwarded-to Numbers:

Information element name Required DescriptionLong forwarded-to number C Shall be present if the subscriber has a long forwarded-to number

registered; otherwise shall be absent.

2.9.2.2 Update Location

This message corresponds to theMAP_UPDATE_LOCATION service specified in 3G TS 29.002.

Update Location contains the following IE specific to Long Forwarded-to Numbers:

Information element name Required DescriptionLong FTN supported C Shall be present if the VLR supports Long Forwarded-to Numbers;


ETSI


2.9.2.3 Provide Roaming Number


Provide Roaming Number contains the following IE specific to Long Forwarded-to Numbers:

Information element name Required DescriptionLong FTN supported C Shall be present if the GMSC and the HLR both support Long

Forwarded-to Numbers; otherwise shall be absent.

2.9.3 Messages on the E interface (VMSC-GMSC)

2.9.3.1 Resume Call Handling


Resume Call Handling contains the following amendment to the Forwarded-to number IE and an additional IE specificto Long Forwarded-to Numbers:

Information element name Required DescriptionForwarded-to number C E.164 number of the C subscriber. Shall be present if the VMSC

does not support Long Forwarded-to Numbers; otherwise shall beabsent.

Long forwarded-to number C Number of the C subscriber. Shall be present if the VMSCsupports Long Forwarded-to Numbers; otherwise shall be absent.

2.9.4 Messages on the MSC internal interface

2.9.4.1 Perform Call Forwarding


Perform Call Forwarding contains the following amendment to the Forwarded-to number IE specific to LongForwarded-to Numbers:


2.9.4.2 Perform Call Forwarding ack


Perform Call Forwarding ack contains the following amendment to the Forwarded-to number IE specific to LongForwarded-to Numbers:


NOTE:This number may be different from the Forwarded-tonumber received in the Perform Call Forwarding, as a result ofCAMEL handling.

2.10 Support of Long Forwarded-to Numbers

2.10.1 MS does not support Long Forwarded-to Numbers

The handling for CFB is the same as that for CFU, see subclause 1.10.1.

ETSI


2.10.2 HLR does not support Long Forwarded-to Numbers

The handling for CFB is the same as that for CFU, see subclause 1.10.2.

2.10.3 GMSC does not support Long Forwarded-to Numbers

The MSC/VLR can determine from the PRN whether the GMSC supports Long Forwarded-to Numbers. If the GMSCdoes not support Long Forwarded-to Numbers and a long forwarded-to number is registered for CFB, then oninvocation of CFB, ORLCF shall not be invoked.

2.10.4 MSC/VLR does not support Long Forwarded-to Numbers

The VLR shall indicate whether it supports Long Forwarded-to Numbers in the Update Location message to the HLR.If the VLR does not support Long Forwarded-to Numbers and a Long Forwarded-to Number is registered for CFB,then:

- If a default forwarded-to number (containing a maximum of 15 digits) is stored in the HLR, the HLR shall send tothe VLR an Insert Subscriber Data message containing the default forwarded-to number in the Forwarded-tonumber parameter.

- Otherwise, the HLR shall send the VLR the following service state information:


For an MT call, if the following conditions are met then the HLR shall include the Forwarding interrogation requiredparameter in the first Send Routing Info ack:

- The GMSC supports Optimal Routeing and Long Forwarded-to Numbers, and

- The MSC/VLR does not support Long Forwarded-to Numbers,and

- CFB is active and operative, and

- A long forwarded-to number is registered for CFB.

According to the rules of Optimal Routeing, when the GMSC receives a Resume Call Handling message from theMSC/VLR, it shall send a second Send Routing Info message to the HLR allowing the HLR to insert the correct longforwarded-to number.

3 Call forwarding on no reply

3.1 Handling of call forwarding on no reply

3.1.1 Registration

The same rules apply for the registration of Call Forwarding on No Reply as were described for Call ForwardingUnconditional in subclause 1.1.1 above, with the exceptions described below. Basic registration of information isillustrated in figure 3.2.

The No Reply Condition Timer

If a value for the no reply condition timer is not included in the registration request received from the MS, then theprevious value set by the mobile user or the network operator applies.


Possible interaction situations between CFNRy and other supplementary services must then be checked. This isdescribed in figure 3.2. Also see 3G TS 22.004 and 3G TS 22.082. For interaction between CFNRy and othersupplementary services (ie not call barring or call forwarding services), the reader is referred to the respective technicalspecification for those supplementary services.

ETSI



Possible interaction between CFNRy and CAMEL Phase 2 or higher is described in figure 3.2. If CAMEL Phase 2 orhigher is not supported in the HLR, processing continues from the "No" exit of the test "Result=Pass".

The information flow for registration of call forwarding on no reply is shown in figure 3.1.

MS MSC VLR HLRFFFF FFFF FFFF FFFFFFF

G G G G G G G G

G G5HJLVWHU &)15\ G G G G G G


G G G G5HJLVWHU &)15\G G G G


G G G G G G5HJLVWHU &)15\G G


G G G G G G G&)15\�GG G G G G G $FNQRZOHGJH G G







G G G G G G G G

Figure 3.1: Registration of call forwarding on no reply

ETSI


Process CFNRy1 382_32(1)


idle

registerCNRy


set BS =all BS

CFNRyprovided


provided

BAICactive

BAOCactive


See GSM 03.78

Result=Pass?

3

validftn


numbertype


(from HPLMN)

12

1

BOICactive

BOIC-exHCactive

ftn in VPLMNcountry

ftn in HPLMNcountry

BIC-Roamactive


country

CFUactive

seterror

acknowledge

idle

setresult

seterror

ftn in VPLMNcountry

3

no

yes

yes

no

no

yes

no

yes

national

international

no

yes

yes

no

no

yes

no

yes

no

yes

yes

no

yes

no

yes

no

no

yes no

yes

yes

no

Figure 3.2: CFNRy1 Call forwarding on no reply registration process

ETSI


3.1.2 Erasure

The same rules apply for the erasure of Call Forwarding on No Reply as were described for Call ForwardingUnconditional in subclause 1.1.2 above. However, no checks for interaction with other supplementary services arerequired for erasure of CFNRy, see figures 3.3 and 3.4.

MS MSC VLR HLR FFFF FFFF FFFFF FFFFFFF

G G G G G G G G

G G (UDVH &)15\ G G G G G G


G G G G(UDVH &)15\ G G G G


G G G G G G(UDVH &)15\ G G


G G G G G G G&)15\�G G G G G G G $FNQRZOHGJHG G







G G G G G G G G

Figure 3.3: Erasure of call forwarding on no reply

ETSI



BS: Basic Service group.

idle

eraseCFNRy


set BS =all BS

CFNRyprovided

seterror

acknowledge

idle

setresult

no

no

yes

yes

Figure 3.4: CFNRy2 Call forwarding on no reply erasure process

ETSI


3.1.3 Activation

The same rules apply for the activation of Call Forwarding on No Reply as were described for Call ForwardingUnconditional in subclause 1.1.3 above, with the exception of the checking of interaction with other supplementaryservices. Basic activation of CFNRy is illustrated in figure 3.6.


Possible interaction situations between CFNRy and other supplementary services must then be checked. This isdescribed in figure 3.6. Also see 3G TS 22.004 and 3G TS 22.082. For interaction between CFNRy and othersupplementary services (ie not call barring or call forwarding services), the reader is referred to the respective technicalspecification for those supplementary services.

The information flow for activation of CFNRy is shown in figure 3.5.

MS MSC VLR HLRFFF FFF FFFF FFFFFFF

G G $FWLYDWH &)15\ G G G G G G

G G��!G G$FWLYDWH &)15\G G G G

G G G G��!G G$FWLYDWH &)15\G G







G G G G G G G G

Figure 3.5: Activation of call forwarding on no reply

ETSI


Process CFNRy3 382_36(1) BS: Basic Service group. ftn: forwarded-to number. BAOC: Barring of All Outgoing Calls. BOIC: Barring of Outgoing International Calls. BOIC-exHC: Barring of Outgoing International Calls except those directed to HPLMN Country. BAIC: Barring of All Incoming Calls.

idle

activateCFNRy

CFNRy registeredfor required BS

BAICactive

BIC-Roamactive


country

BAOCactive

BOICactive

ftn in VPLMNcountry

CFUactive

setresult

acknowledge

idle

seterror

seterror

BOIC-exHCactive

ftn in VPLMNcountry

ftn in HPLMNcountry

seterror

seterror

yes

no

yes

no

no

yes

yes

no

yes

nono

yes

no

yes

no

yes no

yes yes

no

yes

no

Figure 3.6: CFNRy3 Call forwarding on no reply activation process

ETSI


3.1.4 Deactivation

The same rules apply for the deactivation of CFNRy as were described for CFU in subclause 1.1.4 above, see figure 3.7and 3.8.

MS MSC VLR HLRFFF FFF FFF FFFFFFF

G G'HDFWLYDWH &)15\G G G G G G

G G��!G G'HDFWLYDWH &)15\G G G G

G G G G��!G G'HDFWLYDWH&)15\G G









G G G G G G G G

Figure 3.7: Deactivation of call forwarding on no reply

ETSI




idle

deactivateCFNRy


set BS =all BS

CFNRy active forsubset BS

seterror

acknowledge

idle

setresult

no

no

yes

yes

Figure 3.8: CFNRy4 Call forwarding on no reply deactivation process

ETSI


3.1.5 Interrogation

Data request

The data request procedure enables the mobile subscriber to obtain information about the data stored in the PLMN.Interrogation of CFNRy is handled by the VLR which returns the required information or error to the MS, see figure3.9.

MS MSC VLR HLRFFF FFF FFF FFF

G G,QWHUURJDWH &)15\G G G G G G


G G G G,QWHUURJDWH &)15\G G G G


G G G G G G G G



G G5HOHDVH FRPSOHWH G G G G G G



G G G G G G G G

Figure 3.9: Interrogation of call forwarding on no reply


MAF009

Call forwarding on no reply authorizations examination

The ability of a PLMN component to determine the authorizations relating to call forwarding on no reply. Seefigure 3.10.

Location: VLR.

The information flows for forwarding to fixed terminal and to mobile station are shown in figures 3.11 and 3.12respectively.

ETSI




idle

initiatehandlingof CFNRy

activefor this

BS


reached


set forwarding cause=CFNRyset no reply condition timer

notificationto forwarding

subscriberset indicator =

'notify forwardingsubscriber'



servedsubscribers MSISDN

can be presented


restricted


idle


allowed

seterror

set indicator ='set up

normal call'

yes

no

yes

yes

no

yes

no

yes

no

Figure 3.10: MAF009 Call forwarding on no reply authorisations examination (VLR)

ETSI


MSa/TEa GMSC HLRb VLRb MSCb MSb LEcFFFFF FFFFF FFFFF FFFFFFF FFFFFFFF FFFFF FFFFF



G G��!G G,QIR UHTG G G G G G G G G G



G G G G,QIR DFNG G G G G G G G G G






G G G G G G G G ,QIR UHT G G G G G G



G G G G G G G G ,QIR DFN G G 6HW�XS G G G G

G G G G G G G G��!G G��!G G G G


G G G G G G G G G G&DOO FRQIG G G G

G G G G G G G G G VWDUW G��G G G G

G G G G G G G G G WLPHU G G G G G


G G G G G G G G G WLPHU G G G G G

G G G G G G G G ,QIR UHT GH[SLUHVG G G G G



G G G G G G G G,PSRVVLEOHG G G G G G

G G G G G G G G FDOO G G G G G G

G G G G G G G GFRPSOHWLRQG G G G G G

G G G G G G G25��1 G��!G G G G G G



G G5HOHDVH G G��G G G G G G



G G G G G G G G&RQQHFW WRG G G G G G

G G G G G G G G IROORZLQJG G G G G G

G G G G G G G G DGGUHVV G G G G G G

G G G G G G G25��< G��!G G 6HW�XS G G



G G G G G G G G G G 1RWLI G G G G

G G G G G G G G G 25��< G��!G G G G


G G G G 1RWLILFDWLRQ G 25��< G G G G G

G G 1RWLI G G��G G G G G G



NOTE: info: information Y: Yesreq: request N: Noack: acknowledgenotif: notificationconf: confirmationOR1: Call to be forwardedOR2: Notification to forwarding subscriber requiredOR3: Notification to calling subscriber required

Figure 3.11: Information flow for call forwarding on no reply(to fixed terminal)

ETSI


MSa/TEa GMSC HLRb VLRb MSCb MSb HLRc MSCcFFF FFFF FFFF FFFFFFF FFFFFFFF FFFF FFFF FFFF

G G 6HW�XS G G G G G G G G G G G G G G




G G G G,QIR DFNG G G G G G G G G G G G






G G G G G G G G ,QIR UHT G G G G G G G G


G G G G G G G0$)��G G G G G G G G G

G G G G G G G G ,QIR DFN G G G G G G G G

G G G G G G G G��!G G 6HW�XS G G G G G G



G G G G G G G G G G&DOO FRQIG G G G G G

G G G G G G G G G VWDUW G��G G G G G G

G G G G G G G G G WLPHU G G G G G G G


G G G G G G G G ,QIR UHT G WLPHU G G G G G G G

G G G G G G G G��GH[SLUHVG G G G G G G


G G G G G G G GLPSRVVLEOHG G G G G G G G

G G G G G G G G FDOO G G G G G G G G

G G G G G G G GFRPSOHWLRQG G G G G G G G

G G G G G G G25��1 G��!G G G G G G G G



G G5HOHDVH G G��G G G G G G G G



G G G G G G G G&RQQHFW WRG G G G G G G G

G G G G G G G GIROORZLQJ G G G G G G G G

G G G G G G G G DGGUHVV G G G G G G G G

G G G G G G G25��< G��!G G ,QIR UHTXHVW G G G G



G G G G G G G G G G ,QIR DFNQRZOHGJH G G G G






G G G G G G G G G G 1RWLI G G G G G G

G G G G G G G G G 25��< G��!G G G G G G


G G G G 1RWLILFDWLRQ G 25��< G G G G G G G



NOTE: info: information Y: Yesreq: request N: noack: acknowledgenotif: notificationconf: confirmationOR1: Call to be forwardedOR2: Notification to forwarding subscriber requiredOR3: Notification to calling subscriber required

Figure 3.12: Information flow for call forwarding on no reply(to mobile station)

ETSI


3.3 Information stored in the HLRThe following logical states are applicable for CFNRy (refer to 3G TS 23.011 for an explanation of the notation):










- the state of CFNRy (which shall be one of the valid states listed above) for each applicable elementary basicservice group;



- no notification;

- notification.

- the subscription option "notification to the forwarding party" on a per subscriber basis;


- no notification;

- notification.

- the subscription option "MSISDN of the served subscriber can be presented to the forwarded-to subscriber" on aper subscriber basis;




- the registration parameter "forwarded-to number" (possibly including a forwarded-to sub-address) foreach applicable elementary basic service group;

- the registration parameter "no reply condition timer" for each applicable elementary basic service group.

This parameter may take values in the range 5 - 30 seconds in steps of 5 seconds.


3.4 State transition model The following figure shows the successful cases of transition between the applicable logical states of CFNRy. The statechanges are either caused by actions of the service provider, the mobile user or the network.

ETSI


Note that error cases are not shown in the diagram as they normally do not cause a state change. Additionally, somesuccessful requests may not cause a state change. Hence, they are not shown in the diagram. The diagram only showsoperations on an elementary basic service group.







P rovis ion


N o t Induced)



D eactiva tion

A ctiva tion

D eactiva tion

E rasure



W ithdraw al


Figure 3.13: State transition model for CFNRy

3.5 Transfer of information from HLR to VLR If the provisioning state for CFNRy is "Provisioned" then, when the subscriber registers on a VLR, the HLR shall sendthat VLR information about the logical state of CFNRy for all relevant elementary basic service groups.

If the registration state for CFNRy is "Registered" then, when the subscriber registers on a VLR, the HLR shall sendthat VLR the registration parameter "forwarded-to number" and "no reply condition timer" for all relevant elementarybasic service groups and information about the subscription options "notification to the calling party", "notification tothe forwarding party" and "MSISDN of the served subscriber can be presented to the forwarded-to subscriber".

If the logical state, the registration parameter "forwarded-to number" or the registration parameter "no reply conditiontimer" of CFNRy is changed while a subscriber is registered on a VLR then for the affected basic service groups, theHLR shall inform the VLR respectively of the new logical state or the new registration parameter of CFNRy.

If information about the subscription options "notification to the calling party" and "notification to the forwardingparty" of CFNRy is changed while a subscriber is registered on a VLR and the registration state of CFNRy is"Registered" then the HLR shall inform the VLR of the new information about the subscription options of CFNRy.

3.6 Information stored in the VLR For CFNRy the VLR shall store the service state information, the registration parameter "forward-to number", theregistration parameter "no reply condition timer" and the subscription options received from the HLR.

ETSI


3.7 Handover Handover will have no impact on the control procedure and the operation of the service.



In response to a CFNRy interrogation request, if the MS or any network element involved is of Phase 1, onlyinformation concerning basic service groups for which the activation state has the value "Active and Operative" will bereturned. This means that the subscriber will not be aware that the forwarded to number is registered if CFNRy isdeactivated or active (quiescent). A subaddress (if registered) will not be included.

Note that if any network element involved is of Phase 1, CFNRy Registration requests which use a subaddress and allCFNRy Activation and Deactivation requests will be rejected, as these are not specified in Phase 1.





3) Erased=> P bit =1, R bit = 0, A bit = 0, Q bit = 0 or 1.


When passing CFNRy information to a Phase 1 VLR, the HLR shall send the service state information in a form whichthe VLR can accept, based on the logical state held in the HLR, as follows:











When a call is forwarded on no reply, as the HLR does not pass the subaddress to the VLR, calls shall be forwardedwithout the subaddress.

ETSI



When passing CFNRy information to a VLR not supporting CAMEL or supporting CAMEL Phase 1 only, the HLRshall send the registration parameter "forwarded-to number" only if it is registered in a format which the VLR canaccept, i.e. international format.

If the registration state for CFNRy is "Registered" and the forwarded-to number is registered in a format other thaninternational, then when updating a VLR not supporting CAMEL or supporting CAMEL Phase 1 only the HLR shallmodify the service state information of CFNRy as follows.









3.9 Contents of messages The same additions apply for CFNRy as for CFB, see subclause 2.9.

3.10 Support of Long Forwarded-to Numbers The handling for early CFNRc is the same as that for CFU, see section 1.10.

The handling for late CFNRy is the same as that for CFB, see subclause 2.10.

4 Call forwarding on mobile subscriber not reachable

4.1 Handling of call forwarding on mobile subscriber notreachable

4.1.1 Registration

The same rules apply for the registration of Call Forwarding on Mobile Subscriber Not Reachable as were described forCall Forwarding Unconditional in subclause 1.1.1 above, with the exception of the checking of interaction with othersupplementary services. Basic registration of information is illustrated in figure 4.2.


Possible interaction situations between CFNRc and other supplementary services must then be checked. This isdescribed in figure 4.2. Also see 3G TS 22.004 and 3G TS 22.082. For interaction between CFNRc and othersupplementary services (ie not call barring or call forwarding services), the reader is referred to the respective technicalspecification for those supplementary services.


ETSI


Possible interaction between CFNRc and CAMEL Phase 2 or higher is described in figure 4.2. If CAMEL Phase 2 orhigher is not supported in the HLR, processing continues from the "No" exit of the test "Result=Pass".

The information flow for registration of call forwarding on mobile subscriber not reachable is shown in figure 4.1.


G G G G G G G G

G G 5HJLVWHU &)15F G G G G G G


G G G G5HJLVWHU &)15FG G G G


G G G G G G5HJLVWHU &)15FG G


G G G G G G G&)15F�GG G G G G G $FNQRZOHGJH G G







G G G G G G G G

Figure 4.1: Registration of call forwarding on mobile subscriber not reachable

ETSI


Process CFNRc1 382_42(1)


idle

registerCFNRc

BSincluded in

request

set BS =all BS

CFNRcprovided


provided

BAICactive

BAOCactive


See GSM 03.78

Result =Pass?

3

validftn


numbertype

covert tointernational

(from HPLMN)

12

1

BOICactive

BOIC-exHCactive

ftn in VPLMNcountry

ftn in HPLMNcountry

BIC-Roamactive


country

CFUactive

seterror

acknowledge

idle

setresult

seterror

ftn in VPLMNcountry

3

no

yes

yes

no

no

yes

no

yes

national

international

no

yes

yes

no

no

yes

no

yes

no

yes

yes

no

yes

no

yes

no

no

yes no

yes

yes

no

Figure 4.2: CFNRc1 Call forwarding on mobile subscriber not reachable registration process

ETSI


4.1.2 Erasure

The same rules apply for the erasure of CFNRc as were described for CFU in subclause 1.1.2 above. However, nochecks for interaction with other supplementary services are required for erasure of CFNRc, see figure 4.4.

The information flow for registration of CFNRc is shown in figure 4.3.

MS MSC VLR HLR FFFFF FFFFF FFFFF FFFFFFF

G G G G G G G G

G G (UDVH &)15F G G G G G G


G G G G(UDVH &)15FG G G G


G G G G G G(UDVH &)15FG G


G G G G G G G&)15F�G G G G G G G$FNQRZOHGJHG G


G G G G$FNQRZOHGJHG G G G





G G G G G G G G

Figure 4.3: Erasure of call forwarding on mobile subscriber not reachable

ETSI




eraseCFNRc

BSincluded

in request

set BS =all BS

CFNRcprovided

seterror

acknowledge

idle

setresult

no

no

yes

yes

Figure 4.4: CFNRc2 Call forwarding on mobile subscriber not reachable erasure process

ETSI


4.1.3 Activation

The same rules apply for the activation of CFNRc as were described for CFU in subclause 1.1.3 above, with theexception of the checking of interaction with other supplementary services. Basic activation of CFNRc is illustrated infigure 4.6.


Possible interaction situations between CFNRc and other supplementary services must then be checked. This isdescribed in figure 4.6. Also see 3G TS 22.004 and 3G TS 22.082. For interaction between CFNRc and othersupplementary services (i.e. not call barring or call forwarding services), the reader is referred to the respectivetechnical specification for those supplementary services.

The information flow for activation of call forwarding on MS not reachable is shown in figure 4.5.


G G $FWLYDWH &)15F G G G G G G

G G��!G G$FWLYDWH &)15FG G G G

G G G G��!G G$FWLYDWH &)15FG G







G G G G G G G G

Figure 4.5: Activation of call forwarding on MS not reachable

ETSI



BS: Basic Service group. ftn: forwarded-to number. BAOC: Barring of All Outgoing Calls. BOIC: Barring of Outgoing International Calls. BOIC-exHC: Barring of Outgoing International Calls - except those directed to HPLMN Country. BAIC: Barring of All Incoming Calls.

idle

activateCFNRc

CFNRc registeredfor required BS

BAICactive

BIC-Roamactive


country

BAOCactive

BOICactive

ftn in VPLMNcountry

CFUactive

setresult

acknowledge

idle

seterror

seterror

BOIC-exHCactive

ftn in VPLMNcountry

ftn in HPLMNcountry

seterror

seterror

yes

no

yes

no

no

yes

yes

no

yes

nono

yes

no

yes

no

yes no

yes yes

no

yes

no

Figure 4.6: CFNRc3 Call forwarding on mobile subscriber not reachable activation process

ETSI


4.1.4 Deactivation

The same rules apply for the deactivation of CFNRc as were described for CFU in subclause 1.1.4 above, see figure 4.8.

The information flow for deactivation of call forwarding on mobile subscriber not reachable is shown in figure 4.7.

MS MSC VLR HLRFFF FFF FFF FFFFFFF

G G'HDFWLYDWH &)15FG G G G G G

G G��!G G'HDFWLYDWH &)15FG G G G

G G G G��!G G'HDFWLYDWH &)15FG G









G G G G G G G G

Figure 4.7: Deactivation of call forwarding on mobile subscriber not reachable

ETSI




idle

deactivateCFNRc


set BS =all BS

CFNRcactive forsubset BS

seterror

acknowledge

idle

setresult

no

no

yes

yes

Figure 4.8: CFNRc4 Call forwarding on mobile subscriber not reachable deactivation process

ETSI


4.1.5 Interrogation

Data request

The data request procedure enables the mobile subscriber to obtain information about the data stored in the PLMN.Interrogation of CFNRc is handled by the VLR which returns the required information or error to the MS, see figure4.9.

MS MSC VLR HLRFFFF FFFF FFFF FFFF

G G G G G G G G

G G,QWHUURJDWH &)15FG G G G G G


G G G G,QWHUURJDWH &)15FG G G G


G G G G G G G G



G G5HOHDVH FRPSOHWH G G G G G G



G G G G G G G G

Figure 4.9: Interrogation of call forwarding on mobile subscriber not reachable

4.2 Functions and information flows

4.2.1 Call re-routed from VLR

The following Mobile Additional Function has been identified for the PLMN:

MAF010

Examination of call forwarding on mobile subscriber not reachable authorizations

The ability of a PLMN component to determine the authorizations relating to call forwarding on mobilesubscriber not reachable in case the mobile subscriber is not reachable in the VLR, in case of no paging responseor radio congestion. See figure 4.10.

Location: VLR.

The information flows for forwarding to fixed terminal and to mobile station are shown in figures 4.11 and 4.12respectively. These flows represent the case where the mobile subscriber is not reachable in the VLR, and that this factwas not detected at interrogation from the HLR. This situation occurs if the MSC requests the VLR to provideinformation for a mobile terminating call towards a subscriber who is detached in the VLR.

Figures 4.13 and 4.14 show the information flows in case of no paging response.

Figures 4.15 and 4.16 show the information flows in case of radio congestion.

4.2.2 Call re-routed from HLR

The following Mobile Additional Function has been identified for the PLMN:

MAF010


The ability of a PLMN component to determine the authorizations relating to call forwarding on mobilesubscriber not reachable in case the mobile subscriber is deregistered or purged in the HLR or not reachable inthe VLR. See figure 4.10.

Location: HLR.

ETSI


The information flows for forwarding to fixed terminal and to mobile station are shown in figures 4.17 and 4.18respectively. These flows represent the case where the call is re-routed from the HLR because information from theVLR indicates that the subscriber cannot be reached in the VLR. This situation occurs if the VLR detects at roamingnumber request time that the subscriber concerned is detached or that there is no roaming number available.

Figures 4.19 and 4.20 show the information flows for forwarding to fixed terminal and to mobile station respectively incase where the call is re-routed by the HLR because the subscriber is deregistered or purged in the HLR.

ETSI




idle

initiatehandlingof CFNRc

activefor this

BS


reached


set forwarding cause=CFNRc




presented


restricted


idle


allowed

seterror

set indicator ='mobile subscriber

not reachable'

yes

no

yes

no

yes

no

yes

no

Figure 4.10: MAF010 Call forwarding on mobile subscriber not reachable authorisations examination(VLR and HLR)

ETSI


MSa/TEa GMSC HLRb VLRb MSCb LEcFFFFF FFFFF FFFFF FFFFFFF FFFFFF FFFFF


G G 6HW�XSG G G G G G G G G G

G G��!G G,QIR UHTG G G G G G G G

G G G G��!G G 3URYLGH G G G G G G

G G G G G G 5RDP 1R G G G G G G

G G G G G G��!G G G G G G


G G G G G G 5RDP 1R G G G G G G

G G G G,QIR DFNG G��G G G G G G

G G G G��G G G G G G G G

G G G G 6HW�XS G G G G



G G G G G G G G ,QIR UHT G G G G

G G G G G G G G��G G G G

G G G G G G G0$)��G G G G G

G G G G G G G G ,QIR DFN G G G G

G G G G G G G G��!G G G G


G G G G 5HOHDVH G25��1G G G

G G5HOHDVHG G��G G G G

G G��G G G G G G G G G G




G G G G G G G G G25��<G��!G G




G G G G 1RWLILFDWLRQ G25��<G G G

G G 1RWLI G G��G G G G

G G��G G G G G G G G G G


NOTE: info: information Y: Yesreq: request N: Noack: acknowledgenotif: notificationRoam No: roaming numberOR1: Call to be forwardedOR2: Notification to calling subscriber required

Figure 4.11: Information flow for call forwarding on mobile subscriber not reachable in case ofmobile subscriber not reachable in the VLR (to fixed terminal) (re-routing by VLR)

ETSI


MSa/TEa GMSC HLRb VLRb MSCb HLRc MSCcFFFFF FFFFF FFFFF FFFFFFF FFFFFF FFFFF FFFFF


G G6HW�XSG G G G G G G G G G G G


G G G G��!G G 3URYLGH G G G G G G G G

G G G G G G 5RDP 1R G G G G G G G G

G G G G G G��!G G G G G G G G



G G G G,QIR DFNG G��G G G G G G G G





G G G G G G G G ,QIR UHTG G G G G G



G G G G G G G G ,QIR DFNG G G G G G



G G G G 5HOHDVH G25��1G G G G G

G G5HOHDVH G��G G G G G G




G G G G G G G G G25��<G ,QIR UHT G G G G



G G G G G G G G G G ,QIR DFN G G G G







G G1RWLI G G��G G G G G G



NOTE: info: information Y: Yesreq: request N: Noack: acknowledgenotif: notificationRoam No: roaming numberOR1: Call to be forwardedOR2: Notification to calling subscriber required

Figure 4.12: Information flow for call forwarding on mobile subscriber not reachable in case ofmobile subscriber not reachable in the VLR (to mobile station) (re-routing by VLR)

ETSI


MSa/TEa GMSC HLRb VLRb MSCb MSb LEcFFFFF FFFFF FFFFF FFFFFFF FFFFFFFFF FFFFF FFFFF


G G6HW�XS G G G G G G G G G G G G



G G G G G G URDP 1R G G G G G G G G




G G G G,QIR DFNG G��G G G G G G G G









G G G G G G G G��!G G3DJLQJ G G G G


G G G G G G G G G QR G G G G G

G G G G G G G G GUHVSRQVHG G G G G

G G G G G G G G $EVHQW G G G G G G

G G G G G G G G VXEVFULEHUG G G G G G



G G G G G G G G ,PSRVVLEOHG G G G G G

G G G G G G G25��1 G FDOO G G G G G G

G G G G G G G G FRPSOHWLRQG G G G G G



G G5HOHDVHG G��G G G G G G


G G G G G G G25��< G&RQQHFW WR G G G G G G

G G G G G G G G IROORZLQJ G G G G G G










NOTE: info: information Y: Yesreq: request N: Noack: acknowledgenotif: notificationroam: roamingOR1: Call to be forwardedOR2: Notification to calling subscriber required

Figure 4.13: Information flow for call forwarding on mobile subscriber not reachable in case of nopaging response (to fixed terminal) (re-routing by VLR)

ETSI


MSa/TEa GMSC HLRb VLRb MSCb MSb HLRc MSCcFFFF FFFF FFFF FFFFFFF FFFFFFFFF FFFF FFFF FFFF



G G��!G G,QIR UHT G G G G G G G G G G G G

G G G G��!G G 3URYLGH G G G G G G G G G G

G G G G G G URDP 1R G G G G G G G G G G

G G G G G G��!G G G G G G G G G G


G G G G G G 5RDP 1R G G G G G G G G G G

G G G G,QIR DFN G G��G G G G G G G G G G









G G G G G G G G��!G G3DJLQJG G G G G G


G G G G G G G G G QR G G G G G G G

G G G G G G G G GUHVSRQVHG G G G G G G

G G G G G G G G $EVHQW G G G G G G G G

G G G G G G G G VXEVFULEHUG G G G G G G G




G G G G G G G25��1 G ,PSRVVLEOHG G G G G G G G


G G G G G G G G FRPSOHWLRQG G G G G G G G





G G G G G G G25��< G&RQQHFW WR G G G G G G G G

G G G G G G G G IROORZLQJ G G G G G G G G


G G G G G G G G��!G G ,QIR UHT G G G G














Figure 4.14: Information flow for call forwarding on mobile subscriber not reachable in case of nopaging response (to mobile station) (re-routing by VLR)

ETSI


MSa/TEa GMSC HLRb VLRb MSCb MSb LEcFFFF FFFFF FFFFF FFFFFFF FFFFFFFFFFF FFFFF FFFF









G G G G,QIR DFN G G��G G G G G G G G








G G G G G G G G&RPSOHWH FDOOG G G G G G


G G G G G G G G G UDGLR G G G G G

G G G G G G G G GFRQJHVWLRQG G G G G

G G G G G G G G 5DGLR G G G G G G

G G G G G G G G FRQJHVWLRQ G G G G G G




G G G G G G G 25��1G ,PSRVVLEOH G G G G G G

G G G G G G G G FDOO G G G G G G




G G5HOHDVHG G��G G G G G G



G G G G G G G 25��<G &RQQHFW WR G G G G G G

G G G G G G G G IROORZLQJ G G G G G G











Figure 4.15: Information flow for call forwarding on mobile subscriber not reachable in case of radiocongestion (to fixed terminal) (re-routing by VLR)

ETSI


MSa/TEa GMSC HLRb VLRb MSCb MSb HLRc MSCcFFF FFF FFF FFFFFFF FFFFFFFFFFF FFF FFF FFF




G G G G��!G G 3URYLGH G G G G G G G G G G

G G G G G G URDP 1R G G G G G G G G G G

G G G G G G��!G G G G G G G G G G


G G G G G G 5RDP 1R G G G G G G G G G G

G G G G,QIR DFNG G��G G G G G G G G G G








G G G G G G G G&RPSOHWH FDOOG G G G G G G G


G G G G G G G G G UDGLR G G G G G G G

G G G G G G G G GFRQJHVWLRQG G G G G G G

G G G G G G G G 5DGLR G G G G G G G G

G G G G G G G G FRQJHVWLRQ G G G G G G G G




G G G G G G G 25��1G ,PSRVVLEOH G G G G G G G G









G G G G G G G 25��<G &RQQHFW WR G G G G G G G G

G G G G G G G G IROORZLQJ G G G G G G G G


G G G G G G G G��!G G ,QIR UHT G G G G














Figure 4.16: Information flow for call forwarding on mobile subscriber not reachable in case of radiocongestion (to mobile station) (re-routing by VLR)

ETSI


MSa/TEa GMSC HLRb VLRb LEcFFFFF FFFFFF FFFFFFF FFFFF FFFFFF

G G G G G G G G G G


G G��!G G,QIR UHTXHVWG G G G G G

G G G G��!G G 3URYLGH G G G G

G G G G G G URDPLQJ 1R G G G G

G G G G G G��!G G G G

G G G G G G G G G G

G G G G G G 1RW G G G G

G G G G G G UHDFKDEOH G G G G

G G G G G G��G G G G

G G G G G0$)��G G G G G

G G G G ,QIR DFN G G G G G G

G G 5HOHDVH G25��1G��G G G G G G

G G��G G G G G G G G

G G G G G G G G G G

G G G G G G G G G G

G G G25��<G 6HW�XS G G

G G G G��!G G

G G G G G G G G G G

G G G G G G G G G G

G G1RWLILFDWLRQG25��<G G G G G G G


G G G G G G G G G G

NOTE: info: information Y: Yesack: acknowledge N: NoOR1: Call to be forwardedOR2: Notification to calling subscriber required

Figure 4.17: Information flow for call forwarding on mobile subscriber not reachable in case ofmobile subscriber not reachable in the VLR (to fixed terminal) (re-routing by HLR)

MSa/TEa GMSC HLRb VLRb HLRc VLRc MSCcFFFFF FFFFFF FFFFFFF FFFFF FFFFFF FFFFF FFFFF




G G G G G G URDPLQJ 1R G G G G G G G G



G G G G G G 1RW G G G G G G G G

G G G G G G UHDFKDEOH G G G G G G G G

G G G G G G��G G G G G G G G

G G G G G0$)��G G G G G G G G G


G G 5HOHDVH G G��G G G G G G G G G G

G G��G25��1G G G G G G G G G G G



G G G25��<G��!G G 3URYLGH G G G G

G G G G G G G G G GURDPLQJ 1RG G G G



G G G G G G G G G G5RDPLQJ 1RG G G G





G G G G 6HW�XS G G

G G G G��!G G


G G 1RWLI G25��<G G G G G G G G G G G



NOTE: info: information Y: Yesreq: request N: Noack: acknowledgenotif: notificationOR1: Call to be forwardedOR2: Notification to calling subscriber required

Figure 4.18: Information flow for call forwarding on mobile subscriber not reachable in case ofmobile subscriber not reachable in the VLR (to mobile station) (re-routing by HLR)

ETSI


MSa/TEa GMSC HLRb VLRb LEcFFFFF FFFFFF FFFFFFF FFFFF FFFFFF

G G G G G G G G G G


G G��!G G,QIR UHTXHVWG G G G G G


G G G G G G G G G G

G G G G G G G G G G

G G G G G G G G G G

G G G G G G G G G G

G G G G G G G G G G

G G G G G G G G G G

G G G G G0$)��G G G G G

G G G G ,QIR DFN G G G G G G

G G 5HOHDVH G25��1G��G G G G G G


G G G G G G G G G G

G G G G G G G G G G

G G G25��<G 6HW�XS G G

G G G G��!G G

G G G G G G G G G G

G G G G G G G G G G

G G1RWLILFDWLRQG25��<G G G G G G G


G G G G G G G G G G

NOTE: info: information Y: Yesack: acknowledge N: NoOR1: Call to be forwardedOR2: Notification to calling subscriber required

Figure 4.19: Information flow for call forwarding on mobile subscriber not reachable in case ofmobile subscriber deregistered or purged (to fixed terminal) (re-routing by HLR)

MSa/TEa GMSC HLRb VLRb HLRc VLRc MSCcFFFFF FFFFFF FFFFFFF FFFFF FFFFFF FFFFF FFFFF












G G 5HOHDVH G G��G G G G G G G G G G

G G��G25��1G G G G G G G G G G G



G G G25��<G��!G G 3URYLGH G G G G

G G G G G G G G G GURDPLQJ 1RG G G G



G G G G G G G G G G5RDPLQJ 1RG G G G





G G G G 6HW�XS G G

G G G G��!G G


G G 1RWLI G25��<G G G G G G G G G G G



NOTE: info: information Y: Yesreq: request N: Noack: acknowledgenotif: notificationNo:numberOR1: Call to be forwardedOR2: Notification to calling subscriber required

Figure 4.20: Information flow for call forwarding on mobile subscriber not reachable in case ofmobile subscriber deregistered or purged (to mobile station) (re-routing by HLR)

ETSI


4.2.3 Call re-routed from HLR for Pre-Paging

If the Pre-Paging is performed by the VPLMN, in addition to subclause 4.2.2, the following Mobile Additional Functionhas been identified for Pre-Paging in the PLMN. In this case, the subclause 4.2.1 is not identified for Pre-Paging in thePLMN:

MAF010


The ability of a PLMN component to determine the authorizations relating to call forwarding on mobilesubscriber not reachable in case of no paging response or radio congestion for Pre-Paging in the VLR. Seefigure 4.10.

Location: HLR.

The information flows for forwarding to fixed terminal and to mobile station are shown in figures 4.21 and 4.22respectively. These flows represent the case where the call is re-routed from the HLR because of no paging response forPre-Paging from the MSC

Figures 4.23 and 4.24 show the information flows in case of radio congestion for Pre-Paging.

MSa/TEa GMSC HLRb VLRb MSCb MSb LEc FFFFFF FFFFFF FFFFFFF FFFFF FFFFFFFFF FFFFF FFFFF








G G G G G G G G��!G G3DJLQJ G G G G


G G G G G G G G G QR G G G G G

G G G G G G G G GUHVSRQVHG G G G G




G G G G G G Absent G G G G G G G G

G G G G G GsubscriberG G G G G G G G

G G G G G G<---------G G G G G G G G


G G G G,QIR ackG G G G G G G G G G

G G G G<-------G G G G G G G G G G

G G GOR1:NG G G G G G G G G G G

G G5HOHDVHG G G G G G G G G G G G

G G<------G G G G G G G G G G G G

G G GOR1:YG G G G G G G G G G G


G G��--------------------------------------------------------------------------------Æ G G


G GNotification G G G G G G G G G G G





NOTE: info: information Y: Yesreq: request N: Noack: acknowledgeroam: roamingOR1: Call to be forwardedOR2: Notification to calling subscriber required

Figure 4.21: Information flow for call forwarding on mobile subscriber not reachable in case of nopaging response for Pre-Paging (to fixed terminal) (re-routing by HLR)

ETSI


MSa/TEa GMSC HLRb VLRb MSCb MSb HLRC VLRc MSCcFFFF FFFFFFF FFFFF FFFF FFFFFFFFFF FFFF FFFF FFFF FFFFG G G G G G G G G G G G G G G G G GG G6HW�XSG G G G G G G G G G G G G G G GG G��!G G,QIR UHTG G G G G G G G G G G G G GG G G G��!G G Provide G G G G G G G G G G G GG G G G G G roam No G G G G G G G G G G G GG G G G G G--------->G G G G G G G G G G G GG G G G G G G G 3DJH 06 G G G G G G G G G GG G G G G G G G��!G G3DJLQJG G G G G G G GG G G G G G G G G G��!G G G G G G G GG G G G G G G G G QR G G G G G G G G GG G G G G G G G GUHVSRQVHG G G G G G G G GG G G G G G G G $EVHQW G G G G G G G G G GG G G G G G G GVXEVFULEHUG G G G G G G G G GG G G G G G Absent G G��G G G G G G G G G GG G G G G GVXEVFULEHUG G G G G G G G G G G GG G G G G G��-G G G G G G G G G G G GG G G G GMAFG G G G G G G G G G G G GG G G G,QIR DFNG010G G G G G G G G G G G G GG G G G��G G G G G G G G G G G G G GG G GOR1:NG G G G G G G G G G G G G G GG G Rel G G G G G G G G G G G G G G G GG G<-----G G G G G G G G G G G G G G G GG G GOR1:YG Info req G GProvide G G GG G G G��---------------------------------------->G Groam No G G GG G G G G G G G G G G G G G��!G G G GG G G G G G G G G G G G G G (Note 1) GG G G G G G G G G G G G G GRoam G G G GG G G G G G G G G G G G G GNo G G G GG G G G G Info ack G G G G G G G G<----G G G GG G G G<------------------------------------------------------------G G G G G GG G G G G G G G 6HW-up G G G G G G G G GG G G G----------------------------------------------------------------------------->G GG G G G G G G G G G G G G G G G G GG GNotif GOR2:YG G G G G G G G G G G G G G GG G<-----G G G G G G G G G G G G G G G GG G G G G G G G G G G G G G G G G GG G G G G G G G G G G G G G G G G G

NOTE: info: information Y: Yesreq: request N: Noack: acknowledgeRel: Releaseroam: roamingNotif: NotificationOR1: Call to be forwardedOR2: Notification to calling subscriber required

NOTE 1: The procedure of the paging would be performed. Figure 4.22: Information flow for call forwarding on mobile subscriber not reachable in case of no

paging response (to mobile station) (re-routing by HLR)

ETSI


MSa/TEa GMSC HLRb VLRb MSCb MSb LEc FFFFF FFFFFF FFFFFFF FFFFF FFFFFFFFFFF FFFFF FFFFF










G G G G G G G G G radio G G G G G

G G G G G G G G GFRQJHVWLRQG G G G G




G G G G G G Absent G G G G G G G G

G G G G G GsubscriberG G G G G G G G

G G G G G G<---------G G G G G G G G


G G G G,QIR ackG G G G G G G G G G

G G G G<-------G G G G G G G G G G

G G GOR1:NG G G G G G G G G G G

G G5HOHDVHG G G G G G G G G G G G




G G��----------------------------------------------------------------------------------Æ G G


G GNotification G G G G G G G G G G G





NOTE: info: information Y: Yesreq: request N: Noack: acknowledgeroam: roamingOR1: Call to be forwardedOR2: Notification to calling subscriber required

Figure 4.23: Information flow for call forwarding on mobile subscriber not reachable in case of radiocongestion for Pre-Paging (to fixed terminal) (re-routing by HLR)

ETSI


MSa/TEa GMSC HLRb VLRb MSCb MSb HLRC VLRc MSCcFFFF FFFFF FFFF FFFF FFFFFFFFFF FFFF FFFF FFFF FFF GG G G G G G G G G G G G G G G G GG G6HW�XSG G G G G G G G G G G G G G G GG G��!G G,QIR UHTG G G G G G G G G G G G G GG G G G��!G G Provide G G G G G G G G G G G GG G G G G G roam No G G G G G G G G G G G GG G G G G G--------->G G G G G G G G G G G GG G G G G G G G 3DJH 06 G G G G G G G G G GG G G G G G G G��!G G G G G G G G G GG G G G G G G G G G G G G G G G G GG G G G G G G G G radio G G G G G G G G GG G G G G G G G GcongestionG G G G G G G G GG G G G G G G G $EVHQW G G G G G G G G G GG G G G G G G GVXEVFULEHUG G G G G G G G G GG G G G G G Absent G G��G G G G G G G G G GG G G G G GVXEVFULEHUG G G G G G G G G G G GG G G G G G��-G G G G G G G G G G G GG G G G GMAFG G G G G G G G G G G G GG G G G,QIR DFNG010G G G G G G G G G G G G GG G G G��G G G G G G G G G G G G G GG G GOR1G G G G G G G G G G G G G G GG G Rel G :NG G G G G G G G G G G G G G GG G<-----G G G G G G G G G G G G G G G GG G GOR1G Info req G GProvide G G GG G G :YG��------------------------------------------>G Groam No G G GG G G G G G G G G G G G G G��-->G G G GG G G G G G G G G G G G G G (Note 1) GG G G G G G G G G G G G G GRoam G G G GG G G G G G G G G G G G G GNo G G G GG G G G G Info ack G G G G G G G G<----G G G GG G G G<--------------------------------------------------------------G G G G G GG G G G G G G G 6HW-up G G G G G G G G GG G G G------------------------------------------------------------------------------->G GG G G G G G G G G G G G G G G G G GG GNotif GOR2G G G G G G G G G G G G G G GG G<-----G :YG G G G G G G G G G G G G G GG G G G G G G G G G G G G G G G G GG G G G G G G G G G G G G G G G G G

NOTE: info: information Y: Yesreq: request N: Noack: acknowledgeRel: Releaseroam: roamingNotif: NotificationOR1: Call to be forwardedOR2: Notification to calling subscriber required

NOTE 1: The procedure of the paging would be performed.Figure 4.24: Information flow for call forwarding on mobile subscriber not reachable in case of radio

congestion (to mobile station) (re-routing by HLR)

4.3 Information stored in the HLR The following logical states are applicable for CFNRc (refer to 3G TS 23.011 for an explanation of the notation):









ETSI



- the state of CFNRc (which shall be one of the valid states listed above) for each applicable elementary basicservice group;



- no notification;

- notification.

- the subscription option " MSISDN of the served subscriber can be presented to the forwarded-to subscriber" on aper subscriber basis;






4.4 State transition modelThe following figure shows the successful cases of transition between the applicable logical states of CFNRc. The statechanges are either caused by actions of the service provider, the mobile user or the network.

Note that error cases are not shown in the diagram as they normally do not cause a state change. Additionally, somesuccessful requests may not cause a state change. Hence, they are not shown in the diagram.

The diagram only shows operations on an elementary basic service group.

ETSI








P rovis ion


N o t Induced)



D eactiva tion

A ctiva tion

D eactiva tion

E rasure



W ithdraw al


Figure 4.25: State transition model for CFNRc

4.5 Transfer of information from HLR to VLRIf the provisioning state for CFNRc is "Provisioned" then, when the subscriber registers on a VLR, the HLR shall sendthat VLR information about the logical state of CFNRc for all relevant elementary basic service groups.

If the registration state for CFNRc is "Registered" then, when the subscriber registers on a VLR, the HLR shall sendthat VLR the registration parameter "forwarded-to number" for all relevant elementary basic service groups andinformation about the subscription options "notification to the calling party"" and "MSISDN of the served subscribercan be presented to the forwarded-to subscriber".

If the logical state or the registration parameter "forwarded-to number" of CFNRc is changed while a subscriber isregistered on a VLR then for the affected basic service groups, the HLR shall inform the VLR respectively of the newlogical state or the new registration parameter of CFNRc.

If information about the subscription option "notification to the calling party" of CFNRc is changed while a subscriberis registered on a VLR and the registration state of CFNRc is "Registered" then the HLR shall inform the VLR of thenew information about the subscription option of CFNRc.

4.6 Information stored in the VLRFor CFNRc the VLR shall store the service state information, the registration parameter "forward-to number" and thesubscription options received from the HLR.


ETSI




In response to a CFNRc interrogation request, if the MS or any network element involved is of Phase 1, onlyinformation concerning basic service groups for which the activation state has the value "Active and Operative" will bereturned. This means that the subscriber will not be aware that the forwarded to number is registered if CFNRc isdeactivated or active (quiescent). A subaddress (if registered) will not be included.

Note that if any network element involved is of Phase 1, CFNRc Registration requests which use a subaddress and allCFNRc Activation and Deactivation requests will be rejected, as these are not specified in Phase 1.





3) Erased => P bit =1, R bit = 0, A bit = 0, Q bit = 0 or 1.


When passing CFNRc information to a Phase 1 VLR, the HLR shall send the service state information in a form whichthe VLR can accept, based on the logical state held in the HLR, as follows:










4.8.4 GMSC only supports Phase 1 call handling

When a call is forwarded on not reachable at the GMSC, the HLR shall not pass the subaddress to a Phase 1 GMSC.Calls shall be forwarded without the subaddress.


When a call is forwarded on not reachable at the VMSC, as the HLR does not pass the subaddress to the VLR, callsshall be forwarded without the subaddress.

ETSI



When passing CFNRc information to a VLR not supporting CAMEL or supporting CAMEL Phase 1 only, the HLRshall send the registration parameter "forwarded-to number" only if it is registered in a format which the VLR canaccept, i.e. international format.

If the registration state for CFNRc is "Registered" and the forwarded-to number is registered in a format other thaninternational, then when updating a VLR not supporting CAMEL or supporting CAMEL Phase 1 only the HLR shallmodify the service state information of CFNRc as follows:


=> (Provisioned, Not Registered, Not Active, Not Induced);


=> (Provisioned, Not Registered, Not Active, Not Induced);


=> (Provisioned, Not Registered, Not Active, Not Induced).



4.8.7 GMSC does not support CAMEL or supports CAMEL Phase 1 only

If the activation state of CFNRc is "Active and Operative" and if the forwarded-to number is registered in a format otherthan international and if the GMSC does not support CAMEL or supports CAMEL Phase 1 only, then when a requestfor routeing information for a mobile terminated call is received in the HLR, CFNRc shall not be invoked in the HLR.The mobile terminated call establishment shall be continued towards the MSCb.

NOTE: CFNRc will be handled in the VLRb according to the service state information for CFNRc stored there.

4.9 Contents of messagesThe same additions apply for CFNRc as for CFB, see subclause 2.9.

4.10 Support of Long Forwarded-to NumbersThe handling for CFNRc is the same as that for CFB, see subclause 2.10.

ETSI


Annex A (informative):Change history

Change historyTSG CN# Spec Version CR <Phase> New Version Subject/CommentApr 1999 GSM 03.82 8.0.0 Transferred to 3GPP CN1CN#03 23.082 R99 3.0.0 Approved at CN#03CN#05 23.082 3.0.0 001 R99 3.1.0 Addition of the description related to Pre-

Paging in case of “Absent Subscriber”CN#07 23.082 3.1.0 003r3 R99 3.2.0 Introduction of ‘Notification to CSE flag’ to

the call forwarding supplementary service.CN#07 23.082 3.1.0 004r2 R99 3.2.0 Addition of Long Forwarded-to NumbersCN#07 23.082 3.1.0 005 R99 3.2.0 Inclusion of TIF-CSICN#08 23.082 3.2.0 006 R99 3.3.0 Indication in PRN of support of Long FTNsCN#08 23.082 3.2.0 007r1 R99 3.3.0 Interworking cases for Long Forwarded-to

NumbersCN#09 23.082 3.3.0 008r1 R99 3.4.0 SDL refreshCN#10 23.082 3.4.0 009r1 R99 3.5.0 Correction of message between VLR and

HLR

90

ETSI


History

Document history

V3.1.0 January 2000 Publication

V3.2.0 April 2000 Publication

V3.3.0 June 2000 Publication

V3.4.0 October 2000 Publication

V3.5.0 December 2000 Publication

Date post:	22-Jul-2020
Category:	Documents
Upload:	others
View:	5 times
Download:	0 times

TS 123 082 - V3.5.0 - Digital cellular telecommunications ... · ETSI 3GPP TS 23.082 version 3.5.0...

Documents