Document text
ETSITS123 094v3.o.o
(2000-01)
Technical Specification
Digital cellular telecommunications system (Phase 2+) (GSM);
Universal Mobile Telecommunications System (UMTS);
Follow-Me (FM) - Stage 2
(3G TS 23.094 version 3.0.0 Release 1999)
3B&
GLOBAL SYSTEM FOR
MOBILE COMMUNICATIONS
(3G TS 23.094 version 3.0.0 Release 1999)
ETSI TS 123 094 V3.0.0 (2000-01)
Reference
DTS/TSGN-SS23094U
Keywords
GSM, UMTS
ETSI
Postal address
F-06921 Sophia Antipolis Cedex - FRANCE
Office address
650 Route des Lucioles - Sophia Antipolis
Valbonne - FRANCE
+33 4 92 94 42 00 Fax: +33 4 93 65 47 1 6
Siret N°348 623 562 00017 - NAF 742 C
Association a but non lucratif enregistree a la
Sous-Prefecture de Grasse (06) N° 7803/88
Tel
Internet
[email protected]
Individual copies of this ETSI deliverable
can be downloaded from
http://www.etsi.org
If you find errors in the present document, send your
comment to: [email protected]
Important notice
This ETSI deliverable may be made available in more than one electronic version or in print. In any case of existing or
perceived 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
drive within ETSI Secretariat.
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.
ETSI
(3G TS 23.094 version 3.0.0 Release 1 999) 2 ETSI TS 1 23 094 V3.0.0 (2000-01 )
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect
of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server
(http://www.etsi.org/ipr).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in SR 000 314 (or the updates on the ETSI Web server)
which are, or may be, or may become, essential to the present document.
Foreword
id ,
This Technical Specification (TS) has been produced by the ETSI 3 Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities or GSM identities.
These should be interpreted as being references to the corresponding ETSI deliverables. The mapping of document
identities is as follows:
For 3GPP documents:
3G TS I TR nn.nnn "<title>" (with or without the prefix 3G)
is equivalent to
ETSI TS I TR Inn nnn "[Digital cellular telecommunications system (Phase 2+) (GSM);] Universal Mobile
Telecommunications System; <title>
For GSM document identities of type "GSM xx.yy", e.g. GSM 01.04, the corresponding ETSI document identity may be
found in the Cross Reference List on www.etsi.org/key
ETSI
(3G TS 23.094 version 3.0.0 Release 1 999) 3 ETSI TS 1 23 094 V3.0.0 (2000-01 )
Contents
Foreword 4
1 Scope 4
2 Normative references 5
3 Definitions and Abbreviations 6
3.1 Definitions 6
3.2 Abbreviations 6
4 Handling of Follow Me 7
4.1 General 7
4.1.1 Provision 7
4.1.2 Registration 7
4.1.3 Erasure 8
4.1.4 Interrogation 8
4.2 Information Flows 8
4.2.1 Information Flow for the handling of FM by the initiating subscriber 8
4.2.2 Information Flow for the handling of FM by the remote party 10
4.3 Handling of FM control in HLRa and FFNb 10
4.3.1 Handling of FM control in HLRa 10
4.3.2 Handling of FM control in FFNb 12
4.4 USSD interworking and Cross-phase compatibility 19
5 Information stored in the network entities 20
5.1 Information stored in HLRa and FFNb 20
5.2 State transition model 20
5.3 Information stored in the VLR 21
5.4 Transfer of information fromHLR to VLR 21
Annex A (informative): Checking matrix for FM-CFU interaction in FFNb 22
Annex B (normative): FM control Messages and their contents 24
B.l General principles 24
B.2 Information Elements used in the messages 24
B.3 Messages Contents of the FM Request 25
B.4 Messages Contents of the HLR-FM-Request 26
Annex C (informative): Change history 29
History 30
ETSI
(3G TS 23.094 version 3.0.0 Release 1 999) 4 ETSI TS 1 23 094 V3.0.0 (2000-01 )
Foreword
This Technical Specification has been produced by the 3GPP.
The contents of the present document are subject to continuing work within the TSG and may change following
formal TSG approval. Should the TSG modify the contents of this TS, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version 3.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 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 specification;
1 Scope
This Technical Specification specifies the stage 2 description for the Follow Me feature.
The Follow Me feature enables a mobile subscriber A to manipulate the Follow Me data of a remote party B in such
a way that subsequent calls directed to remote party B will be forwarded to subscriber A.
ETSI
(3G TS 23.094 version 3.0.0 Release 1 999) 5 ETSI TS 1 23 094 V3.0.0 (2000-01 )
2 Normative references
The following documents contain provisions which, through reference in this text, constitute provisions of the
present document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies.
[I] TR 21.905: "3G Vocabulary".
[2] TS 22.004: "General on Supplementary Services".
[3] TS 22.030: "Man-Machine Interface (MMI) of the Mobile Station (MS)".
[4] TS 22.082: "Call Forwarding (CF) supplementary services - Stage 1".
[5] TS 22.094: "Follow Me (FM) feature - Stage 1 " .
[6] TS 23.01 1: "Technical realisation of Supplementary Services - General Aspects".
[7] TS 23.015: "Technical realisation of Operator Determined Barring (ODB)".
[8] TS 23.090: "Unstructured Supplementary Services Data (USSD)- Stage 2".
[9] TS 23.082: "Call Forwarding (CF) supplementary services - Stage 2".
[10] TS 22.090: "Unstructured Supplementary Services Data (USSD)- Stage 1".
[II] TS 24.090: "Unstructured Supplementary Services Data (USSD)- Stage 3".
[12] TS 29.002: "Mobile Application Part (MAP)".
ETSI
(3G TS 23.094 version 3.0.0 Release 1999)
ETSI TS 123 094 V3.0.0 (2000-01)
Definitions and Abbreviations
3.1
Definitions
initiating subscriber:
initiating number:
remote party:
The mobile subscriber who modifies the Follow Me data of the remote party.
The number (the MSISDN of the initiating subscriber) to which incoming calls, originally
destined for the remote party, shall be forwarded. It is subsequently also referred to as
MSISDNa
Is characterised by the remote number which is defined in the numbering plan of a PLMN
operator. The Follow Me feature enables the initiating subscriber to modify the Follow
Me data of the remote party.
In particular cases the remote party is a GSM subscriber of the PLMN and the remote
number denotes her basic MSISDN.
Is an initiating subscriber who is allowed to modify the Follow Me data of a remote party
who has been registered to another initiating subscriber for the Follow Me application.
The FM service supervisor shall be authorised by her network operator.
Is a number in E. 164 format which identifies a remote party. In general this number is not
assigned to a subscriber and can be regarded as a "dummy MSISDN". In particular cases
the remote party is a GSM subscriber of the PLMN and the remote number denotes her
basic MSISDN.
The remote number is entered by the initiating subscriber for registration, interrogation,
forced erasure and erasure of the Follow Me feature with respect to the remote party.
Follow Me function node: Is a network node in the PLMN operator of the remote party. The FM data of the
remote party are stored in this node. This node can be implemented in
- an HLR
- any other operator specific network node e.g.
a gsmSCF
- an SCP
FM service supervisor:
remote number:
3.2 Abbreviations
FM
FFN
SCP
Follow Me
Follow Me function node
Service Control Part
Other abbreviations used in this ETS are listed in TR 21.905.
ETSI
(3G TS 23.094 version 3.0.0 Release 1 999) 7 ETSI TS 1 23 094 V3.0.0 (2000-01 )
Handling of Follow Me
4.1 General
Follow Me enables an initiating mobile subscriber A to have control over the Follow Me data of a remote party B.
The remote party B is characterised by the remote number which is defined in the numbering plan of a PLMN
operator. Initiating Subscriber A shall be able to manipulate the Follow Me data of remote party B such that
subsequent calls destined for remote party B are forwarded to initiating subscriber A. In the case of Forced Erasure
by an FM service supervisor, the initiating subscriber is allowed to erase the Follow Me data of a remote party who
has been registered to a different initiating subscriber for the Follow Me application.
Follow Me is a PLMN specific feature and the control operations of FM are based on USSD. All messages between
the MS and the mobile network and internal to the mobile network are USSD messages.
This Technical Specification deals with the control operations of FM in HLRa and FFN. If the FFN is an HLR, the
control of the requests for both FM and CFU services is specified (see 4.3.2).
The functionality of forwarding calls for remote party B to initiating subscriber A (after successful registration of
FM) is out of the scope of this specification. This functionality is the same as the functionality of the Call
Forwarding Unconditional Supplementary Service applied to all telecommunication services of remote party B for
which CFU is applicable.
NOTE: the "served mobile subscriber" in [5] corresponds to the "remote party" in this document and
the "forwarded-to subscriber" in [5] corresponds to the "initiating subscriber" in this document.
NOTE: The forwarding of calls for remote party B to initiating subscriber A can be achieved by invoking the
Call Forwarding Unconditional Supplementary Service or by making use of an equivalent operator
specific service (e.g. via CAMEL).
The functionality of the control of Follow Me (registration, erasure, forced erasure and interrogation) is split
between the HLR of the initiating subscriber A (HLRa) and the FFN of the remote party B (FFNb).
4.1.1 Provision
FM can be registered / erased / interrogated by an initiating subscriber A with respect to a remote party B if both
parties are provisioned with FM.
To enable forced erasure by an FM service supervisor, the FM service shall be provisioned to the FM service
supervisor. Additionally, she needs the subscription entitlement to perform the forced erasure.
NOTE: In general remote party B does not correspond to a GSM subscriber. In this case provisioning of FM
for remote party B is operator specific.
If remote party B is a GSM subscriber and if the forwarding of calls for remote party B to initiating subscriber A is
achieved by invoking the Call Forwarding Unconditional Supplementary Service, provision of CFU for remote party
B is required.
4.1.2 Registration
The initiating subscriber registers the FM feature with respect to a particular remote party.
If an initiating subscriber A successfully registers FM with respect to a remote party B then FM becomes registered,
active and operative for remote party B.
As a result of the registration subsequent calls directed to remote party B are forwarded to initiating subscriber A.
NOTE: The remote party cannot register FM with respect to herself.
ETSI
(3G TS 23.094 version 3.0.0 Release 1 999) 8 ETSI TS 1 23 094 V3.0.0 (2000-01 )
4.1.3 Erasure
If an initiating subscriber A or the FM service supervisor successfully erases FM with respect to a remote party B
then FM becomes not registered and not active for remote party B.
If remote party B is a GSM subscriber and successfully erases FM then FM becomes not registered and not active
for remote party B.
4.1.4 Interrogation
If an initiating subscriber A or the FM service supervisor successfully interrogates FM with respect to a remote party
B then this procedure interrogates the FM data of subscriber B.
If remote party B is a GSM subscriber and successfully interrogates FM then this procedure interrogates her own
FM data.
4.2 Information Flows
4.2.1 Information Flow for the handling of FM by the initiating subscriber
Figure 4. 1 shows the Information Flow for the control of FM (registration, erasure, forced erasure and interrogation)
by the initiating subscriber.
For any control operation on FM, the initiating subscriber (MSa) enters a Follow Me Request (FM-Request). This is
a USSD string containing the requested FM operation and the remote number. The Follow Me Request is routed via
the MSC/VLR to the HLR of the initiating subscriber (HLRa).
The HLRa performs a series of checks as described in the SDLs (4.3.1). If these checks fail, the MSa receives a
response (FM-Response) indicating the error.
If the checks pass, the HLRa forwards the operation request (HLR-FM -Request) to the FFN of the remote party
(FFNb).
FFNb carries out the appropriate control operation and checks as described in the SDLs (4.3.2) for the remote party.
The result of this operation (success or error) is reported back in a USSD Response to the initiating subscriber.
ETSI
(3G TS 23.094 version 3.0.0 Release 1999)
ETSI TS 123 094 V3.0.0 (2000-01)
MSa
MSC
VLR
HLRa
FFNb
FM-Request
(OC,SC,RN,
[(SI.PIM,)] [AI])
FM-Response
(Error)
FM-Response
Result)
FM-Request
(OC.SC.RN,
[(SI.PIM,)] [AI])
FM-Response
(Error)
FM-Response
^Result)
(OC,SC,RN,
[(SI.PIM,)] [AI])
FM-Response
(Error)
FM-Request
PR1
N
t
FM-Response
esult)
OR1
Y
HLR-FM-Request
(OC,SC,RN,AI,
[(SI.PIM,)] [AI,]
MSISDN-A)
HLR-FM-Respons
t
esult)
Figure 4.1 : Information flow for the control of FM by the initiating subscriber
NOTE 1: ORl:N The case where the checks in the HLR result in a negative outcome, e.g. FM is not
provisioned for the initiating subscriber or the initiating subscriber is not allowed to operate FM for
the remote party.
ORl:Y The case where all the checks in the HLR are successful, e.g. FM is provisioned for the
initiating subscriber and the initiating subscriber is allowed to operate FM for the remote party.
NOTE 2: [...]Optional parameter
(...)] Conditional parameter
OCOperation Code (Register, Erase or Interrogate)
SC Service Code for FM
RN Remote Number
SI Supervisor Indicator. This parameter is conditional and only used for forced erasure by a FM
service supervisor.
PIM MSISDN of previous initiating subscriber who has registered the FM to remote number. This
parameter is conditional and only used for forced erasure by a FM service supervisor.
AI Supplementary Information containing additional information.
MSISDN-A initiating number in international format
ETSI
(3G TS 23.094 version 3.0.0 Release 1 999) 1 ° ETSI TS 1 23 094 V3.0.0 (2000-01 )
4.2.2 Information Flow for the handling of FM by the remote party
Control of FM by the remote party is possible if the remote party is a GSM subscriber.
The information flow for control of FM by the remote party (erasure and interrogation of her own FM data) is the
same as the information flow for control of FM by the initiating subscriber.
If a remote party tries to register FM to herself the registration is rejected and an error is reported.
4.3 Handling of FM control in HLRa and FFNb
HLRa and FFNb can both receive FM control messages, based on USSD. The USSD handler in each entity analyses
the Service Code contained in the USSD string and, recognising the Service Code for FM, invokes the FM USSD
application.
The FM control messages and their contents are given in Annex B (normative).
4.3.1 Handling of FM control in HLRa
The FM USSD application in HLRa is the process FM_initiating_subscriber_handling_in_HLR (Figure 4.2). It
receives the FM-Request from the initiating subscriber. This FM-Request is an USSD-string containing
the operation code (register, erase, interrogate)
the remote number
an additional operator specific information field.
The HLR checks
The provisioning of FM to the initiating subscriber
Whether the FFN can be deduced from the remote number
Whether any operator specific restrictions to engage in FM activity with the remote party apply
If the initiating subscriber requires forced erasure, the HLR checks Whether the initiating subscriber is
entitled to do it, i.e. Whether the initiating subscriber is a FM service supervisor.
The basic MSISDN of the initiating subscriber is sent together with the original USSD string to the FFN of the
remote party.
The HLR forwards the response from the FFN to the initiating subscriber.
ETSI
(3G TS 23.094 version 3.0.0 Release 1999)
11
ETSI TS 123 094 V3.0.0 (2000-01)
Process FMInitiatingSubscriberHandlinginHLR
1(1)
A process in the HLR to handle,
an FM-Request from an initiating"
subscriber.
Idle
Signals to/from the left \
areto/ftomtheVLRofthe
initiating subscriber;
Signals to/from the right
are to/from the FFN
FM-Request
(Operation,
RemoteNumb
Additionaljnfol
HLR receives USSD
string from initiating
subscriber
check if initiating
subscriber is FM
provisioned
check if address of FFN
can be deduced from
RemoteNumber
Error :=
unknown Remote
Party
Error :=
unauthorised
request
HLR-FM-Request ;
FM-Request
+ initial MSISDN
Check iif the forced erasure
is allowed to the initiating
subscriber.
check operator specific
restrictions on initiating
subscriber to engage
Remote Party in FM activity
Basic MSISDN of initiating
subscriber is sent to the FFNb
together with the FM-Request
within the MAP operation.
FM-Response
(Error)
Idle
HLR-FM-Request
(Operation,
RemoteNumber,
Additionaljnfo,
lnitJal_MSISDN)
^
wai_foranswer_
from FFN
HLR-FM-Respon
(Result)
FM-Response
(Result)
Idle
Figure 4.2: Process: FMInitiatingSubscriberHandlinginHLR
ETSI
(3G TS 23.094 version 3.0.0 Release 1999)
12
ETSI TS 123 094 V3.0.0 (2000-01)
4.3.2 Handling of FM control in FFNb
If the FFN is an HLR, the FFN is responsible for handling the interactions between FM and CFU. Two kinds of
request may be received in an FFN which deals with forwarding services:
CFU requests sent by the VLR for CFU operations (only if the FFN is a HLR)
FM-HLR-Requests which are USSD strings sent by HLRa for FM operations
When the control process in the FFN receives a CFU request, it shall either pass the CFU operation request directly
to a CFU process or reject it depending on the registration and/or activation states of both FM and CFU services (see
Table A.l for permission checks).
On receipt of an HLR-FM request, the control process in the FFN performs a series of FM specific checks and
checks the states of both FM and CFU. If the checks are successful, a CFU operation request is sent to a CFU
process. On receipt of an HLR-FM-Request from HLRa, the FFN performs a series of checks, e.g.:
If the remote party is a GSM subscriber:
Provisioning of FM to the remote party
Provisioning of CFU to the remote party
Illegal interaction with CFU registered or active to remote party
If the remote number is registered in the FFN
If any operator specific restrictions to engage in FM activity with the initiating subscriber apply
- Specific checks for forced erasure.
Depending on the requested operation, one of the following procedures is performed:
Registration with implicit Activation (procedure Handle_Remote_Party_Registration, Figure 4.6)
Erasure with implicit Deactivation (procedure Handle_Remote_Party_Erasure, Figure 4.7)
Interrogation (procedure Handle_Remote_Party_Interrogation, Figure 4.8)
Figure 4.3 shows the message flow between the process Forwarding_Service_Control and the processes
handling CFU operation requests, defined in [9].
from/to
HLRa
from/to
VLR
Block FFN Processes
FM-HLR-Request
FM-HLR-Responsel
TCFU-Request
CFU acknowledge
this is applicable
if the FFN is a HLR "
1(1)
process_
forwarding
Service_
control
-' Process defined in 03.94
CFU operation request
acknowledge
Processes defined
in 03.82: CFU1,
CFU2.CFU3 or
CFU4
process_CFU_
handling
Figure 4.3: FFN_processes
ETSI
(3G TS 23.094 version 3.0.0 Release 1999)
13
ETSI TS 123 094 V3.0.0 (2000-01)
Process Forwarding_Service_Control
This process describes
the case where the FFN is a
HLR. Camel or IN solution '
should have the similar
behavior. ,
Signals to/from the right are r
to/from the appropriate CFU
process. Signals to/from the
left are to/from the VLR
unless otherwise stated.
it's from the HLR of
the initiating subscriber.
Result :=
Conflicting
situation
with other SS
1(2)
CFU operation
request
J it should contain the appropiate
message, e.g. "register CFU" etc.
"\
wait_for_response
acknowledge
acknowledge
I
if ifs an FM-Request
J the message is to the VLR
■ of the initiating subscriber.
4.4 Process Forwarding_Service_Control
ETSI
(3G TS 23.094 version 3.0.0 Release 1999)
14
ETSI TS 123 094 V3.0.0 (2000-01)
Procedure FM_Remote_Party_Handling_in_FFN
KD
This process describes the case
where the FFN is an HLR.
IN solutions should have
similar behaviour.
signals to/from the left are
to/fromtheHLRotthe
initiating subscriber
Result :=
unknown remote
party
check operator specific
restrictions on remote party
to be engageed in FM activity
with initiating subscriber
handle_Remote_
Party_
Registration
Figure 4.5: Procedure: FM_Remote_Party_Handling_in_FFN
ETSI
(3G TS 23.094 version 3.0.0 Release 1999)
15
ETSI TS 123 094 V3.0.0 (2000-01)
Procedure Handle_Remote_Party_Registration
1(1)
This process describes the case
where the FFN is an HLR.
1 IN solutions should have
'similar behaviour. '
signals to/from the left arel,
to/from the HLR of the
initiating subscriber
signals to/from the right are
to/from the CFU process as
indicated
initiating subscriber
may not register FM
of her own number
Figure 4.6: Procedure: Handle_Remote_Party_Registration
ETSI
(3G TS 23.094 version 3.0.0 Release 1999)
16
ETSI TS 123 094 V3.0.0 (2000-01)
Procedure Register_FM_for_Remote_Party
This process describes the case .
where the FFN is an HLR.
IN solutions should have
similar behaviour.
KD
signals to/from the right are
to/from the CFU process as
indicated.
Result := remote
party already
regi stered
if yes, the initiating
subscriber repeats
her previous
registration
Figure 4.6a: Procedure Register_FM_for_Remote_Party
ETSI
(3G TS 23.094 version 3.0.0 Release 1999)
17
ETSI TS 123 094 V3.0.0 (2000-01)
Procedure Handle_Remote_Party_Erasure
KD
This process describes the case ^
where the FFN is an HLR.
IN solutions should have
similar behaviour.
signals to/from the left are \
to/from the H LR of the
initiating subscriber
signals to/from the right are
to/from the CFU process as
indicated.
Result :=FM
not registered to
remote party
if yes, remote party
erases her own
FM data
result := Remote
party not
registered to this
MS ISDN
if yes, then FM service
] supervisor
performs FM erasure
Result := Remote
party not registered
tothisMSISDN
Result:-
FM successful
de registered
^
Result := corresponding
unsuccessful
outcome code
HLR-FM-
Response
(Result)
Figure 4.7: Procedure: Handle_Remote_Party_Erasure
ETSI
(3G TS 23.094 version 3.0.0 Release 1999)
18
ETSI TS 123 094 V3.0.0 (2000-01)
Procedure Erase_FM_for_Remote_Party
1(1)
This procedure is called , ,
by the procedure
handle_Remote_party_Erasure
after the authorisation checks
have been done. This procedure
describes the case if the FFN is
an HLR. Camel or IN solution
should have the same behavior..
signals to/from the left are '•
to/fromtheHLRofthe
initiating subscriber
signals to/from the right are
to/from the CFU process as
indicated.
to process CFU2
~ (GSM 03.82)
Erase_CFU
(BS = all BS)
wait_for_
response
from process CFU2
(GSM 03.82) ~
from process CFU2
~ (GSM 03.82)
acknowledge
(result)
acknowledge
(error)
Result := pass
Result := (error)
Figure 4.7a: Procedure Erase_FM_for_Remote_party
ETSI
(3G TS 23.094 version 3.0.0 Release 1999)
19
ETSI TS 123 094 V3.0.0 (2000-01)
Procedure Handle_Remote_Party_lnterrogation
This procedure describes ^
the case whenre the FFN is n
an HLR. IN solutions should
have similar behaviour.
signals to/from the left are
to/fromtheHLRofthe
initiating subscriber
Result :=
FM not registered
to remote party
Result :=FM
active to MSISDN
HLR-FM-
Response
(Result)
1(1)
The MSISDN digits are sent
in the USSD response
separated by a blank
character from the outcome
code
Figure 4.8: Procedure Handle_Remote_Party_lnterrogation
4.4 USSD interworking and Cross-phase compatibility
All the messages between MS and the mobile network and internal to the mobile network, which are used for
control of Follow Me, are USSD Phase 2 messages.
A Cross-phase compatibility mechanism specified in [6] for networks or MS not supporting USSD Phase 2 is not
required.
Networks subject to the Interoperability Directive have to implement FM using USSD Phase 2.
Note: As an option, these networks may also implement FM using USSD Phase 1.
ETSI
(3G TS 23.094 version 3.0.0 Release 1999)
20
ETSI TS 123 094 V3.0.0 (2000-01)
Information stored in the network entities
5.1
Information stored in HLRa and FFNb
The HLRa shall store:
the state of FM (which shall be one of the valid states listed below);
The FFNb shall store:
the state of FM if the remote party is a GSM subscriber
the registration parameter:
- the initiating number (MSISDN A )
The following logical states are applicable for FM (refer to TS 23.01 1 for an explanation of the notation):
In HLRa (for the initiating subscriber)
Provisioning State Registration State Activation State HLR Induction State
(Not Provisioned, Not Registered, Not Active, Not Induced)
(Provisioned, Not Registered, Not Active, Not Induced)
The registration and activation state is the same for each applicable elementary basic service group.
The provisioning state shall be per subscriber, and hence the same for all basic service groups.
In FFNb (for the remote party)
Provisioning State Registration State
(Not Provisioned, Not Registered,
(Provisioned, Not Registered,
(Provisioned, Registered,
Activation State
Not Active,
Not Active,
Active and Operative,
HLR Induction State
Not Induced)
Not Induced)
Not Induced)
The registration and activation state is the same for each applicable elementary basic service group.
The provisioning state shall be per subscriber, and hence the same for all basic service groups.
5.2
State transition model
The following figure shows the successful cases of transition between the applicable logical states of FM. The state
changes are caused by actions of the service provider, the mobile user or the network.
Note: Error cases are not shown in the diagram as they do not normally cause a state change. Successful
requests that do not cause a state change are not shown in the diagram.
The diagram only shows operations on an elementary basic service group.
ETSI
(3G TS 23.094 version 3.0.0 Release 1999)
21
ETSI TS 123 094 V3.0.0 (2000-01)
Provision
(Provisioned,
Not Registered,
Not Active,
Not Induced)
(Not Provisioned,
Not Registered,
Not Active,
Not Induced)
Withdrawal
Registration
Erasure
(Provisioned,
Registered,
Active and Operative,
Not Induced)
Figure 5.1 : State transition model for FM
5.3
Information stored in the VLR
There is no FM information stored in the VLR
5.4 Transfer of information from HLR to VLR
There is no FM information transferred from HLR to VLR
ETSI
(3G TS 23.094 version 3.0.0 Release 1999)
22
ETSI TS 123 094 V3.0.0 (2000-01)
Annex A (informative):
Checking matrix for FM-CFU interaction in FFNb
The following table is applicable under the assumption that FM and CFU are always provisioned to the
remote party.
If FM is not provisioned then there is no interaction between FM and CFU.
If FM is Registered and Active, CFU must also be Registered and Active.
Interrogation of both FM and CFU is allowed in any registration state.
Operation
Registration States
Outcome
FM
CFU
Registration FM
Not registered
Not registered
FM: Registered and Active
CFU: Registered and Active
Registered, not active
operation not allowed
Registered, active
operation not allowed
registered and active
Registered, active
see note 1
Erasure FM
Not registered
Not registered
operation not allowed,
see note 2
Registered, not active
operation not allowed
Registered, active
operation not allowed
registered and active
Registered, active
FM: Not Registered
CFU: Not Registered
Registration
CFU
Not registered
Not registered
FM: Not registered
CFU: Registered, active
see note 3
Registered, not active
FM: Not registered
CFU: Registered, active
see note 3
Registered, active
FM: Not registered
CFU: Registered, active
see note 3
registered and active
Registered, active
operation not allowed,
see note 4
ETSI
(3G TS 23.094 version 3.0.0 Release 1999)
23
ETSI TS 123 094 V3.0.0 (2000-01)
Erasure CFU
Not registered
Not registered
operation not allowed,
see note 3
Registered, not active
FM: Not registered
CFU: Not registered
note 3
Registered, active
FM: Not registered
CFU: Not registered
see note 3
registered and active
Registered, active
operation not allowed,
see note 4
Activation CFU
Not registered
Not registered
operation not allowed,
see note 3
Registered, not active
FM: Not registered
CFU: Registered, active
see note 3
Registered, active
FM: Not registered
CFU: Registered, active
see note 3
registered and active
Registered, active
operation not allowed,
see note 4
Deactivation
CFU
Not registered
Not registered
operation not allowed,
see note 3
Registered, not active
operation not allowed,
see note 3
Registered, active
FM: Not registered
CFU: Registered, not active
see note 3
registered and active
Registered, active
operation not allowed,
see note 4
Table A.1 : Operation allowance check according registration states of FM and CFU (informative)
Note 1 :
Note 2
Note 3
Note 4
The operation is only allowed when the registration is made by the same initiating subscriber. The
registration states of FM and CFU shall not be changed by the operation.
The outcome code should be "Remote party not registered".
Refer to TS 23.082 for CFU handling.
Conflicting situation with other supplementary service (see TS 22.082: Exceptional procedures or
unsuccessful outcome)
ETSI
(3G TS 23.094 version 3.0.0 Release 1 999) 24 ETSI TS 1 23 094 V3.0.0 (2000-01 )
Annex B (normative):
FM control Messages and their contents
B.1 General principles
All messages used for the control of FM are based on mobile initiated USSD. The principles of USSD can be found
in TS 22.090, TS 23.090, TS 24.090 and TS 29.002.
This document is only concerned with the contents of the USSD strings.
B.2 Information Elements used in the messages
The operation code
The operation code is defined in TS 22.030 for the control of Supplementary Services and consists of the two
characters:
** for Registration
## for Erasure
*# for Interrogation
The Service Codes
The Service Code is service specific for FM.
The remote number
The remote number is the basic MSISDN of the remote party if the remote party is a GSM subscriber. It is entered
by the initiating subscriber as part of the registration request. It is a number in international format.
Additional information field
An additional information field which does not exceed 30 characters may be optionally included in all FM control
messages to convey operator specific information to the FFNb. The content and use of this additional information is
operator specific and out of scope of this specification.
The initiating number
The initiating number is the basic MSISDN of the initiating subscriber. It is derived by HLRa from the IMSI of the
initiating subscriber.
This parameter is used in international format according to the scheme:
- country code, national (significant) number.
ETSI
(3G TS 23.094 version 3.0.0 Release 1999)
25
ETSI TS 123 094 V3.0.0 (2000-01)
B.3 Messages Contents of the FM Request
Contents of the USSD string of FM-Request:
All parameters are entered by the initiating subscriber and transported transparently to HLRa
Parameter
number
Value
Parameter
mandatory (M)
or optional (O)
Comment
1
OC
M
Operation Code:
OC = ** ... for Registration
OC = ##... for Erasure
OC = *# ... for Interrogation
2
sc
M
Service Code for Follow Me. SMG1 has been asked
to allocate 25 for FM.
3
*
M
Delimiter
4
REMOTE
NUMBER
M
remote number
5
*
M
Delimiter.
6
Supervisor
Indicator
C
Supervisor Indicator = 88. Used for Forced Erasure
by FM Service Supervisor.
7
*
M
Delimiter
8
MSISDN
C
MSISDN of previous initiating subscriber who has
registered the FM to remote number. This
parameter is conditional, only used for forced
erasure.
9
*
M
Delimiter
10
Additional
information field
O
For operator specific use
last
#
M
End of USSD string
Table B.1 : Contents of the USSD string of FM-Request
ETSI
(3G TS 23.094 version 3.0.0 Release 1 999) 26 ETSI TS 1 23 094 V3.0.0 (2000-01 )
B.4 Messages Contents of the HLR-FM- Request
Contents of the USSD string of HLR-FM- Request is the same of FM-Request described in B.3. Additionally, the
MSISDNa is sent to the FFNb together with the FM-Request within the MAP operation. Contents of the FM-
Response Messages
The FM-Response messages which are generated by the HLR, as well as the HLR-FM-Response messages which
are received by the HLR from the FFN and are forwarded unchanged as FM-Response messages to the MS, contain
the following two parts:
mandatory part: two digit outcome codes, which are interpreted in the MS according to operator specific
requirements
optional part: the response texts.
The optional part is separated by a space character as separator which occurs together with the optional part.
These outcome codes indicating success or error of the requested FM operation are 2 USSD characters according to
the following table (table B.2):
ETSI
(3G TS 23.094 version 3.0.0 Release 1999)
27
ETSI TS 123 094 V3.0.0 (2000-01)
Scenario
Text examples for MS display
Reg
Era
Interr
Outcome
Code
Outcome codes for successful
cases
00 series
Success registration Case
Follow Me activated
X
01
Success erasure Case
Follow Me deactivated
X
02
Success interrogation Case
Follow Me active to
<MSISDN>
The MSISDN digits are sent in
the USSD response separated
by a blank character from the
outcome code.
X
03
Operator Specific outcome codes
04-06
Reserved for future enhancement
07-09
Spare outcome codes
1 series
Outcome codes generated at
the HLRa in non-successful
cases
20,30
series
Incoming barrings
Illegal interaction with incoming
barring
X
X
X
21
Unauthorised request
Unauthorised request
X
X
X
22
Operator Specific outcome codes
23-30
Reserved for future enhancement
31-39
Outcome codes generated at
both the HLRa and the FM
function node in non-
successful cases
40 series
Unknown remote party
Unknown remote party
X
X
X
41
FM not subscribed
FM not subscribed
X
X
X
42
Operator Specific outcome codes
43-45
Reserved for future enhancement
46-49
Spare unsuccessful outcome
codes
50 series
Outcome codes generated at
the FM function node in non-
successful cases
60,70
series
Remote party already
registered
Remote party already registered
X
61
FM not registered to remote party
FMnot
registered to remote party
X
X
62
Remote party not registered to
this MSISDN
Remote party not
registered to this MSISDN
X
63
Remote Party Authorisation failed
Unauthorised changes to remote
party
X
X
64
Call Forwarding active or
registered
Illegal interaction with call
forwarding
X
65
Incoming or outgoing barrings
Illegal interaction with call
barrings
X
X
66
ETSI
(3G TS 23.094 version 3.0.0 Release 1999)
28
ETSI TS 123 094 V3.0.0 (2000-01)
Request to own MSISDN not
possible
Request to own MSISDN not
possible
X
67
Operator Specific outcome codes
68-72
Reserved for future enhancement
73-79
Outcome codes could be sent
back by CFU processes in
unsuccessful cases
forwarded-to number is invalid
directory number
forwarded-to number is invalid
directory number
X
80
insufficient information
insufficient information
X
X
81
forwarded-to number is a special
service code
forwarded-to number is a special
service code (e.g. police)
X
82
Conflicting situation with other
supplementary services
Conflicting situation with other
supplementary services (e.g.
incoming call barring has been
activated)
X
X
83
Inconsistent with registration
Inconsistent with registration
X
84
Spare unsuccessful outcome
codes
85-99
Table B.2 Outcome codes for FM-Response
ETSI
(3G TS 23.094 version 3.0.0 Release 1999) 29
ETSI TS 123 094 V3.0.0 (2000-01)
Annex C (informative):
Change history
Change history
TSG CN#
Version
CR
Tdoc CN
New Version
Subject/Comment
CN#06
-
NP-
99461
3.0.0
Approved at TSG CN#06 and placed under Change Control
ETSI
3GPP
(3G TS 23.094 version 3.0.0 Release 1999) 30
ETSI TS 123 094 V3.0.0 (2000-01)
History
Document history
V3.0.0
January 2000
Publication
ETSI