B.4 Messages Contents of the HLR-FM-Request
23.0943GPPFollow-Me (FM)Release 17Stage 2TS
Contents of the USSD string of HLR-FM- Request is the same of FM-Request described in clause 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).
Table B.2 Outcome codes for FM-Response
|
Scenario |
Text examples for MS display |
Reg |
Era |
Interro |
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 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 code |
10 |
||||
|
Reserved for GSM-Railway |
11-12 |
||||
|
Spare outcome codes |
13-19 |
||||
|
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 |
Remote party already registered |
X |
61 |
||
|
FM not registered to remote party |
FM not |
X |
X |
62 |
|
|
Remote party not registered to this MSISDN |
Remote party not |
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 |
|
|
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 |