Content for TS 23.008 Word version: 18.1.0

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.16 Data related to Location Services p. 79

2.16.1 Subscriber Data stored in HLR p. 79

2.16.1.1 Privacy Exception List p. 79

This data contains the privacy classes for any target MS that identify the LCS clients permitted to locate the MS. For a detailed definition of this data, refer to TS 23.271.

2.16.1.2 GMLC Numbers p. 79

This data contains the GMLC addresses for an MS subscriber. These addresses may be used to verify that a location request from specific LCS clients is authorized for the target MS.

2.16.1.3 MO-LR List p. 79

This data contains the classes of MO-LR that are permitted for the MS subscriber. For a detailed definition of this data, refer to TS 23.271.

2.16.1.4 Service Types |R5| p. 79

This data contains the privacy settings for any target MS that identify the permitted service types for LCS clients requesting positioning of the MS. For a detailed definition of this data, refer to TS 23.271.

2.16.2 Data stored in GMLC p. 79

The GMLC stores data related to LCS clients. Refer to TS 23.271 for a detailed description.

2.16.3 Data stored in SMLC (GSM only) p. 79

The SMLC stores data related to associated Type A and Type B LMUs from which location measurements may be received. Refer to GSM 23.271 [56] for a detailed description.

2.16.4 Data stored in LMU (GSM only) p. 80

The LMU stores data related to its LCS measurement and O&M capabilities and may store data related to LCS measurements and O&M reports that it is required to provide to its controlling SMLC. The nature and content of this data is not defined in GSM.

2.16.5 Data stored in the MSC (GSM only) p. 80

In order to support routing of connectionless LCS messages to an SMLC or a Type B LMU, the MSC may store permanent routing data for an SMLC or a Type B LMU in association with a specific location area identifier or location area identifier plus cell identifier.

2.16.6 Data stored in the BSC (GSM only) p. 80

In order to support routing of connectionless LCS messages to an SMLC or a Type B LMU, the BSC may store permanent routing data for an SMLC or a Type B LMU in association with a specific location area identifier or location area identifier plus cell identifier.

2.16.7 Subscriber Data stored in HSS |R15| p. 80

2.16.7.1 List of Broadcast Location Assistance Data Types p. 80

This data contains information used to determine which ciphering key data should be provided to the UE if requested by the UE, when location assistance data is broadcast in E-UTRAN using ciphering. For a detailed definition of this data, refer to TS 23.271.

2.17 Data related to Super-Charger p. 80

2.17.1 Age Indicator p. 80

This data indicates the age of the subscription data provided by the HLR, e.g. the date and time at which the subscriber data was last modified in the HLR.

2.18 Data related to bearer service priority p. 80

2.18.1 CS Allocation/Retention priority p. 80

The Circuit Switched ( CS ) Allocation/Retention priority corresponds to the allocation/retention priority which is defined in TS 23.107. It specifies the relative importance compared to other UMTS bearers for allocation and retention of the UMTS bearer in the CS domain.

The parameter is permanent subscriber data and is conditionally stored in the HLR and VLR.

2.19 Data related to charging p. 80

2.19.1 Subscribed Charging Characteristics p. 80

Subscribed Charging Characteristics are specified in TS 32.251, for example whether the subscriber is a normal, prepaid, flat rate and/or hot billing subscriber.

Subscribed Charging Characteristics is permanent subscriber data and conditionally stored in HSS/HLR, SGSN, MME and ePDG (for GTP-based S2b only) (see TS 23.060, TS 23.401 and TS 29.273).

2.20 Data related to IMS Centralized Service |R8| p. 81

2.20.1 ICS Indicator p. 81

The ICS Indicator specifies whether or not the subscriber is an ICS user (see TS 23.292).

The ICS Indicator is permanent subscriber data and is conditionally stored in the HSS, MME, VLR and SGSN.

2.21 Data related to SRVCC |R8| p. 81

2.21.1 STN-SR p. 81

2.21.1.1 General |R16| p. 81

The STN-SR identifies the Session Transfer Number for SRVCC or 5G-SRVCC (see TS 23.003).

The STN-SR is temporary data and is conditionally stored in the UDM, HSS, AMF, MME and SGSN (see TS 23.216).

2.21.1.2 STN-SR in EPS or GPRS |R16| p. 81

The existence or absence of a STN-SR data in the HSS indicates that the user is SRVCC subscribed or not SRVCC subscribed. This information on SRVCC subscription is independent of the STN-SR value. The creation or deletion of the STN-SR data in the HSS is ensured by provisioning.

2.21.1.3 STN-SR in 5GS |R16| p. 81

The existence or absence of a STN-SR data in the UDM indicates that the user is 5G-SRVCC subscribed or not 5G-SRVCC subscribed. This information on SRVCC subscription is independent of the STN-SR value. The creation or deletion of the STN-SR data in the UDM is ensured by provisioning.

2.21.2 UE SRVCC Capability |R10| p. 81

2.21.2.1 General |R16| p. 81

This information element indicates the SRVCC capability of the UE and is described in TS 23.237.

2.21.2.2 UE SRVCC Capability in EPS |R16| p. 81

The UE SRVCC Capability is temporary data conditionally stored in the HSS, MME and SGSN.

2.21.2.3 UE SRVCC Capability in 5GS |R16| p. 81

The UE 5G SRVCC Capability is temporary data conditionally stored in the UDM and AMF.

2.21.3 Subscribed vSRVCC |R11| p. 81

The Subscribed vSRVCC is permanent data and is conditionally stored in the HSS and MME (see TS 23.216). The Subscribed vSRVCC indicates that the user is subscribed to the Single Radio Video Call Continuity (vSRVCC) or not.

2.21.4 CS to PS SRVCC Allowed |R11| p. 82

The CS to PS SRVCC Allowed indicator is permanent data and is conditionally stored in the HSS and VLR (see TS 23.216). The CS to PS SRVCC Allowed indicator indicates per PLMN whether the user is allowed to have CS to PS Single Radio Voice Call Continuity or not.