5 Information stored in the network entities
23.0943GPPFollow-Me (FM)Release 17Stage 2TS
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 (MSISDNA).
The following logical states are applicable for FM (refer to TS 23.011 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 |
Activation State |
HLR Induction State |
|
(Not Provisioned, |
Not Registered, |
Not Active, |
Not Induced) |
|
(Provisioned, |
Not Registered, |
Not Active, |
Not Induced) |
|
(Provisioned, |
Registered, |
Active and Operative, |
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.
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.
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.
Table A.1: Operation allowance check according registration states of FM and CFU (informative)
|
Operation |
Registration States |
Outcome |
|
|---|---|---|---|
|
FM |
CFU |
||
|
Registration FM |
Not registered |
Not registered |
FM: 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, |
|
Registered, not active |
operation not allowed |
||
|
Registered, active |
operation not allowed |
||
|
registered and active |
Registered, active |
FM: Not Registered |
|
|
Registration CFU |
Not registered |
Not registered |
FM: Not registered |
|
Registered, not active |
FM: Not registered |
||
|
Registered, active |
FM: Not registered |
||
|
registered and active |
Registered, active |
operation not allowed, |
|
|
Erasure CFU |
Not registered |
Not registered |
operation not allowed, |
|
Registered, not active |
FM: Not registered |
||
|
Registered, active |
FM: Not registered |
||
|
registered and active |
Registered, active |
operation not allowed, |
|
|
Activation CFU |
Not registered |
Not registered |
operation not allowed, |
|
Registered, not active |
FM: Not registered |
||
|
Registered, active |
FM: Not registered |
||
|
registered and active |
Registered, active |
operation not allowed, |
|
|
Deactivation CFU |
Not registered |
Not registered |
operation not allowed, |
|
Registered, not active |
operation not allowed, |
||
|
Registered, active |
FM: Not registered |
||
|
registered and active |
Registered, active |
operation not allowed, |
|
|
NOTE 1: 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. NOTE 2: The outcome code should be "Remote party not registered". NOTE 3: Refer to TS 23.082 for CFU handling. NOTE 4: Conflicting situation with other supplementary service (see TS 22.082: Exceptional procedures or unsuccessful outcome). |
|||
Annex B (normative):
FM control Messages and their contents