Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.008  Word version:  17.1.0

Top   Top   Up   Prev   Next
0…   2…   2.3…   2.4…   2.5…   2.8…   2.10…   2.13…   2.13.50…   2.13.100…   2.13.150…   2.14…   2.16…   2.22…   2.23…   2.25…   3…   3.2…   3.4…   3.10…   3.13…   3.14…   3.15…   4…   5.1   5.2   5.2A   5.2B   5.3   5.4…   5.6…   5.8…   5.10…

 

2.5  Data related to basic servicesp. 37

2.5.1  Provision of bearer servicep. 37

Provision of bearer service is a parameter identifying whether a bearer service is provisioned to the mobile subscriber or not. This provision can be achieved through subscription of the mobile subscriber or the bearer service can be generally available. The parameter "provision of bearer service" must be set for the bearer service defined in TS 22.002 for which a subscription is required.
Provision of bearer service is permanent subscriber data and is stored in the HLR and VLR.
Up

2.5.2  Provision of teleservicep. 37

Provision of teleservice is a parameter identifying whether a teleservice is provisioned to the mobile subscriber or not. This provision can be achieved through subscription of the mobile subscriber or the teleservice can be generally available. The parameter "provision of teleservice" must be set for the teleservices defined in GSM 02.03 [36] for which a subscription is required.
Provision of teleservice is permanent subscriber data and is stored in the HLR, Gn/Gp-SGSN and VLR.
Up

2.5.3  Bearer capability allocationp. 37

Bearer capability allocation is a parameter stored against each ISDN number in the case when the Home PLMN allocates one directory number per teleservice and bearer service. In this case it is used to permit the establishment of the correct bearer capability on the connection to the MS. (See TS 29.007). The bearer capability allocation is not required when the Home PLMN only allocates one directory number per subscriber for all bearer services and teleservices. It is permanent data stored conditionally in theTS 43.020.
Up

2.5.4  Transfer of SM optionp. 38

Transfer of SM option is a parameter indicating which path should be used for transfer of Terminating Short Message when GPRS is not supported by the GMSC. Two options are possible:
  • transfer of SM via the MSC when GPRS is not supported in the GMSC: this option is used to indicate that SM shall always be sent via the MSC when the GMSC does not support the GPRS functionality;
  • transfer of SM via the Gn/Gp-SGSN when GPRS is not supported in the GMSC: this option is used to indicate that SM shall always be sent via the Gn/Gp-SGSN when the GMSC does not support the GPRS functionality.
Transfer of SM option is permanent subscriber data stored in HLR for a GPRS subscription.
The data has an interim nature since in the final solution, the decision on SM Transfer is taken in the SMS-GMSC.
Up

2.6  Data related to supplementary servicesp. 38

Subscriber data related to supplementary services are contained in the 3GPP TS 23.08x and 3GPP TS 23.09x series of Technical Specifications, that is TS 23.081 and following describing the network functionality of supplementary services. Additionally, subscriber data related to the Multicall (MC) supplementary service are contained in TS 23.135.
There is no data type which is mandatory for all supplementary services; note that the provision status is mandatory for all supplementary services except CUG, TS 23.085. All other data are conditional depending on the provision.
Up

2.7  Mobile station status datap. 38

2.7.1  IMSI detached flagp. 38

IMSI detached flag is a parameter indicating that the MS is in the IMSI detached state, i.e. the subscriber is no longer reachable. For definition and handling see TS 23.012 and TS 29.002. The parameter takes the following values:
  • IMSI detached;
  • IMSI attached.
The parameter is temporary subscriber data and is stored conditionally in the VLR.

2.7.2  Mobile station Not Reachable for GPRS (MNRG)p. 38

In HLR, MNRG indicates whether the MS is marked as GPRS detached or GPRS not reachable in the Gn/Gp-SGSN and possibly in the GGSN. The reason why the MS is GPRS not reachable is indicated in the Mobile Not Reachable via SGSN Reason (MNRR-SGSN).
In Gn/Gp-SGSN, MNRG indicates whether activity from the MS shall be reported to the HLR.
In GGSN, MNRG indicates whether the MS is marked as GPRS detached in the Gn/Gp-SGSN.
MNRG is described in TS 23.060. It is temporary subscriber data stored in the HLR, in the Gn/Gp-SGSN and in the GGSN.
Up

2.7.3  Mobility Management Statep. 38

The Mobility Management State indicates the GPRS state of the MS. It takes one of three possible values:
  1. READY: The MS is GPRS attached and its location is known at Cell Identity level.
  2. STANDBY: The MS is GPRS attached and its location is known at Routing Area level.
  3. IDLE: The MS is not GPRS attached.
The parameter is described in TS 23.060. It is temporary subscriber data stored in the SGSN.

2.7.4  Restoration flagsp. 39

In the case of SGSN, MME, VLR or HLR failure, location register data have to be restored as described in TS 23.007 and TS 29.002. The following flags are used for this purpose.

2.7.4.1  Confirmed by Radio Contact indicatorp. 39

Confirmed by Radio Contact indicator is a restoration indicator defined in TS 23.007.
It is temporary subscriber data, stored in the VLR.

2.7.4.2  Subscriber Data Confirmed by HLR/HSS indicatorp. 39

Subscriber Data Confirmed by HLR/HSS indicator is a restoration indicator defined in TS 23.007.
It is temporary subscriber data, stored in the VLR, in the SGSN and in the MME.

2.7.4.3  Location Information Confirmed in HLR/HSS indicatorp. 39

Location Information Confirmed in HLR/HSS indicator is a restoration indicator defined in TS 23.007.
It is temporary subscriber data, stored in the VLR and in the SGSN and in the MME.

2.7.4.4  Check SS indicatorp. 39

Check SS indicator is a restoration indicator defined in TS 23.007.
It is temporary subscriber data and is stored in the HLR.

2.7.4.5  VLR-Reliable indicator |R10|p. 39

VLR-Reliable indicator is a restoration indicator defined in TS 23.007.
It is temporary subscriber data and is stored in the SGSN and in the MME.

2.7.5  MS purged for non-GPRS flagp. 39

MS purged for non-GPRS flag is set in the HLR per IMSI record in order to indicate that the subscriber data for the MS concerned have been purged in the VLR. The parameter takes the following values:
  • MS purged;
  • MS not purged.
The default value is "MS not purged". The parameter is temporary subscriber data, stored in the HLR.

2.7.6  MS purged for GPRS/UE purged in SGSN flagp. 39

MS purged for GPRS/UE purged in SGSN flag is set in the HLR/HSS per IMSI record in order to indicate that the subscriber data for the MS/UE concerned have been purged in the SGSN. The parameter takes the following values:
  • MS purged for GPRS/UE purged in SGSN;
  • MS not purged for GPRS/UE not purged in SGSN.
The default value is "MS not purged for GPRS"/"UE not purged in SGSN". The parameter is temporary subscriber data, stored in the HLR/HSS for a PS subscription.
Up

2.7.6A  UE purged in MME flag |R8|p. 40

UE purged in MME flag is set in the HSS per IMSI record in order to indicate that the subscriber data for the UE concerned have been purged in the MME. The parameter shall take the following values:
  • UE purged in MME;
  • UE not purged in MME.
The default value is "UE not purged in MME". The parameter is temporary subscriber data, stored in the HSS for a PS subscription.

2.7.7  Mobile station Not Reachable via MSC Reason (MNRR-MSC)p. 40

Mobile station Not Reachable via MSC Reason (MNRR-MSC) for SMS is defined in TS 23.040.The MNRR-MSC is temporary subscriber data. It is conditionally stored in the HLR.

2.7.7A  Mobile station Not Reachable via SGSN Reason (MNRR-SGSN) |R7|p. 40

Mobile station Not Reachable via SGSN Reason (MNRR-SGSN) for SMS is defined in TS 23.040.The MNRR-SGSN is temporary subscriber data. It is conditionally stored in the HLR.

2.7.8  Subscriber data dormant |R7|p. 40

Subscriber data dormant is set in the VLR per IMSI record in order to indicate that the subscriber data belong to a subscriber that has moved outside the VLR area (see TS 23.012). The parameter takes the following values:
  • Subscriber data dormant;
  • Subscriber data not dormant.
The parameter is temporary subscriber data and is stored in the VLR.

2.7.8A  Cancel Location received |R10|p. 40

Cancel Location received is set by a VLR supporting the MT roaming retry feature per IMSI record to indicate that a Cancel Location message has been received from the HLR. This is used to determine whether to trigger MT roaming retry upon receipt of an incoming call, see clause 7.3.2.1 of TS 23.018. The parameter takes the following values: true or false.
The parameter is temporary subscriber data and is stored in the VLR.
Up

2.7.9  Data related to UE reachability procedures |R8|p. 40

2.7.9.1  URRP-MMEp. 40

The UE Reachability Request Parameter for the MME (URRP-MME) indicates that UE activity notification from MME has been requested by the HSS. For definition and handling of the data see TS 23.401.
URRP-MME is temporary subscriber data conditionally stored in the MME and in the HSS.

2.7.9.2  URRP-SGSN |R9|p. 40

The UE Reachability Request Parameter for the SGSN (URRP-SGSN) indicates that UE activity notification from SGSN has been requested by the HSS. For definition and handling of the data see TS 23.060.
URRP-SGSN is temporary subscriber data conditionally stored in the SGSN and in the HSS.

2.7.9.3  Service-related Entity list |R10|p. 41

This information element is a list of service related entities (i.e. gsmSCF address list or AS Identity list, see the definition of gsmSCF address list in clause 2.14.2.4 and the definition of AS Identity list in clause 3.5.7) which have subscribed to a notification of UE reachability (e.g. IP-SM-GW )
Service-related Entity list is temporary subscriber data stored in the HSS.
Up

Up   Top   ToC