2 Definition of subscriber data for CS and PS domain

23.0083GPPOrganization of subscriber dataRelease 17TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

2.1 Data related to subscription, identification and numbering

2.1.1 Data defining the subscription profile

2.1.1.1 International Mobile Subscriber Identity (IMSI)

International Mobile Subscriber Identity (IMSI) is defined in 3GPP TS 23.003 [5].

IMSI is permanent subscriber data. IMSI is stored in HLR, HSS, CSS, VLR, SGSN, S4-SGSN, GGSN, MME, S-GW, P-GW, ePDG, SCEF and SMLC. For Anonymous Access, IMSI is not used in SGSN nor in GGSN. The IMSI serves as the root of the subscriber data pseudo-tree.

For emergency attached UEs without IMSI (e.g; UICCless UE) or with an unauthenticated IMSI, IMEI is used instead of IMSI to identify the UE.

2.1.1.2 Network Access Mode (NAM)

The Network Access Mode (NAM) defines if the subscriber is registered to get access to the CS domain (non-GPRS/EPS), to the PS domain (GPRS/EPS) or to both domains using 3GPP access networks. NAM describes the first level of the subscriber data pseudo-tree below the IMSI root. It is permanent subscriber data stored in the HSS/HLR and the SGSN with the Gs interface option, and the MME with the SGs interface option.

2.1.1.3 IMSI Unauthenticated indicator

For an emergency attached UE with an unauthenticated IMSI, the IMSI Unauthenticated indicator is set to reflect that the IMSI is unauthenticated. See 3GPP TS 23.401 [74], 3GPP TS 23.060 [21] and 3GPP TS 23.402 [77].

The IMSI Unauthenticated indicator is a temporary subscriber data stored in the MME, S-GW, P-GW, SGSN, S4-SGSN, GGSN and ePDG.

2.1.2 Mobile Station International ISDN Number (MSISDN)

Mobile Station ISDN Number (MSISDN) is defined in 3GPP TS 23.003 [5].

The MSISDN is permanent subscriber data and is conditionally stored in HLR, VLR, SGSN, GGSN, HSS, MME, S-GW, P-GW, SCEF, 3GPP AAA Server and ePDG(for GTP-based S2b only), and is optionally stored in CSS. If the multinumbering option applies, the MSISDN stored in the VLR and in the Gn/Gp-SGSN is the Basic MSISDN, see clause 2.1.3.1.

2.1.3 MSISDNs for multinumbering option

If the HPLMN allocates different MSISDNs for different Basic Services (see 3GPP TS 29.007 [28]), these numbers are conditionally stored as permanent data in the HLR.

2.1.3.1 The Basic MSISDN indicator

The Basic MSISDN is defined in 3GPP TS 23.012 [8]. The Basic MSISDN indicator marks the MSISDN to be used as Basic MSISDN.

It is permanent subscriber data stored conditionally in the HLR.

2.1.3.2 The MSISDN-Alert indicator

The MSISDN-Alert is defined in 3GPP TS 23.040 [10]. The MSISDN-Alert indicator marks the MSISDN to be used as MSISDN-Alert.

It is permanent subscriber data stored conditionally in the HLR.

2.1.4 Temporary mobile subscriber identity (TMSI)

Temporary mobile subscriber identity (TMSI) is defined in 3GPP TS 23.003 [5].

The TMSI is temporary subscriber data and is conditionally stored in the VLR.

2.1.5 Packet-Temporary Mobile Subscriber Identity (P-TMSI)

Packet-Temporary Mobile Subscriber Identity (P-TMSI) is defined in 3GPP TS 23.003 [5]. Its usage is described in 3GPP TS 23.060 [11]. P-TMSI is accompanied by the P-TMSI Signature, see clause 2.3.7.

The P-TMSI is temporary subscriber data and is conditionally stored in the SGSN.

2.1.6 Temporary Link Layer Identifier (TLLI)

Temporary Link Layer Identifier (TLLI) is defined in 3GPP TS 23.003 [5]. It is derived from the P-TMSI by the MS and occurs in the variants Local TLLI and Foreign TLLI. The TLLI is temporary subscriber data and is conditionally stored in the SGSN. For use of TLLI see 3GPP TS 23.060 [11].

2.1.7 Random TLLI

Random TLLI is chosen randomly by the MS. It is defined in 3GPP TS 23.003 [5]. Random TLLI is short living temporary subscriber data and is conditionally stored in the SGSN. For use of Random TLLI see 3GPP TS 23.060 [11].

A Random TLLI may be used if no valid P-TMSI is available.

2.1.8 Local Mobile Station Identity (LMSI)

Local Mobile Station Identity (LMSI) is defined in 3GPP TS 23.003 [5]. The LMSI is temporary subscriber data. The LMSI may be stored in the VLR; if it is received in the HLR it must be stored there.

2.1.9 International Mobile Equipment Identity (IMEI)

International Mobile Equipment Identity (IMEI) is defined in 3GPP TS 23.003 [5]. The IMEI is temporary subscriber data and is conditionally stored in the HSS, SGSN, S4-SGSN, GGSN, MME, SGW, PGW, ePDG and 3GPP AAA Server.

2.1.10 External Identifier Set

The External Identifier set contains one or more External Identifier as defined in 3GPP TS 23.003 [5].

Any one of the External Identifier from the IMSI’s External Identifier Set shall uniquely identify a single subscriber (IMSI).

The External Identifier Set is permanent subscriber data and is stored in the HSS and conditionally in the SCEF.

2.1.11 UE radio capability ID

The UE radio capability ID is defined in 3GPP TS 23.003 [5]. Its usage is described in 3GPP TS 23.401 [74].

The UE radio capability ID is temporary subscriber data and is conditionally stored in the MME.

2.2 Data related to Mobile Station types

2.2.1 Mobile Station Category

Mobile Station Category has a structure identical to that of "Calling Party’s Category" defined in ISUP (ITU‑T Recommendation Q.763 [38]).

The following values of category shall be supported:

– ordinary subscriber.

The category is assigned per IMSI.

Mobile Station Category is permanent subscriber data and is stored in HLR and VLR.

2.2.2 LMU Identifier (GSM only)

The LMU identifier is part of the subscriber data for a Type A LMU, when associated with an NSS based SMLC, and serves to distinguish a Type A LMU from a normal MS.

2.2.3 International Mobile Equipment Identity and Software Version (IMEISV)

International Mobile Equipment Identity and Software Version (IMEISV) is defined in 3GPP TS 23.003 [5]. The IMEISV is temporary subscriber data and is conditionally stored in the VLR, SGSN, HLR, S4-SGSN, GGSN, MME, SGW, PGW, ePDG and 3GPP AAA Server.

2.3 Data related to authentication and ciphering

2.3.1 Random Number (RAND), Signed Response (SRES) and Ciphering Key (Kc)

Random Number (RAND), Signed Response (SRES) and Ciphering Key (Kc) form a triplet vector used for authentication and encryption as defined in 3GPP TS 43.020 [31].

For GSM users, triplet vectors are calculated in the 2G AuC and provided to the 2G HLR (see GSM 12.03 [36]), and for UMTS users triplet vectors are derived from quintuplet vectors in the 3G HLR or 3G VLR, if needed (see 3GPP TS 33.102 [52]).

A set of up to 5 triplet values are sent from the 2G HLR to the VLR and the SGSN on request. These data are temporary subscriber data conditionally stored in the VLR and the SGSN.

2.3.2 Random Challenge (RAND), Expected Response (XRES), Cipher Key (CK), Integrity Key(IK) and Authentication Token(AUTN), KASME

Random Challenge (RAND), Expected Response (XRES), Cipher Key (CK), Integrity Key(IK) and Authentication Token (AUTN) form a quintuplet vector used for user authentication, data confidentiality and data integrity as defined in 3GPP TS 33.102 [52].

Random Challenge (RAND), Expected Response (XRES), Key for Access Security Management Entity (KASME) and Authentication Token (AUTN) form an EPS vector used for user authentication, data confidentiality and data integrity as defined in 3GPP TS 33.401 [73].

When both HLR and VLR or SGSN are 3G, a set of quintuplet vectors are calculated in the AuC, and up to 5 quintuplets are sent from the HLR to the VLR and to the SGSN on request (see 3GPP TS 29.002 [27]). These data are temporary subscriber data conditionally stored in the HLR, the VLR and the SGSN.

When the HLR is 2G and the VLR or SGSN are 3G, quintuplet vectors are derived by the 3G VLR or SGSN from the received triplet vectors from the HLR, if needed (see 3GPP TS 33.102 [52]).

2.3.3 The Ciphering Key Sequence Number (CKSN)

The Ciphering Key Sequence Number (CKSN) is used to ensure GSM authentication information (Kc) consistency between the MS and the VLR and between the MS and the SGSN.

CKSN and its handling are defined in 3GPP TS 24.008 [26] and 3GPP TS 43.020 [31]. It is a temporary subscriber data and is stored in the VLR and in the SGSN.

2.3.4 The Key Set Identifier (KSI)

The Key Set Identifier (KSI) is used to ensure UMTS authentication information (CK and IK) consistency between the MS and the VLR and between the MS and the SGSN.

For EPS the Key Set Identifier (KSI also noted KSI_ASME ) is used to ensure EPS authentication information (K_ASME) consistency between the MS and the MME.

KSI and its handling are defined in UMTS TS 24.008 [26] and UMTS TS 33.102 [52]. It is temporary subscriber data and is stored in the VLR and the SGSN.

KSI_ASME and its handling are defined in 3GPP TS 23.401[74]. It is temporary subscriber data and is stored in the MME.

2.3.5 Selected Ciphering Algorithm

Selected Ciphering Algorithm is defined in 3GPP TS 23.060 [21].

Selected Ciphering Algorithm is temporary subscriber data stored in the SGSN.

2.3.6 Current Kc

Current Kc is defined in 3GPP TS 43.020 [31].

Current Kc is temporary subscriber data stored in the SGSN.

2.3.7 P-TMSI Signature

P-TMSI Signature is defined in TSs 3GPP TS 23.003 [5] and 3GPP TS 23.060 [21]. It is used for identification checking purposes.

P-TMSI Signature is temporary subscriber data and is conditionally stored in the SGSN.

2.3.8 Access Network Identity (ANID)

Access Network Identity is defined in TSs 3GPP TS 24.302 [82] and 3GPP TS 29.273 [78].

ANID is temporary subscriber data stored in HSS and 3GPP AAA server.

2.3.9 Key Status

Key Status is defined in 3GPP TS 25.413 [120].

Key Status is temporary subscriber data stored in VLR and SGSN.

2.4 Data related to roaming

2.4.1 Mobile Station Roaming Number (MSRN)

Mobile Station Roaming Number (MSRN) is defined in 3GPP TS 23.003 [5].

NOTE: There may be more than one MSRN simultaneously per IMSI.

The MSRN is short-lived temporary subscriber data stored in the VLR.

2.4.2 Location Area Identification (LAI)

Location Area Identification (LAI) is defined in 3GPP TS 23.003 [5].

The LAI is temporary subscriber data and is stored in the VLR.

2.4.3 Routing Area Identification (RAI)

Routing Area Identification (RAI) is defined in 3GPP TS 23.003 [5].

The RAI is temporary subscriber data and is stored in the SGSN.

2.4.4 Void

2.4.5 VLR number

VLR number is defined in 3GPP TS 23.003 [5].

The VLR number is temporary subscriber data and is stored in the HLR. Absence of the VLR number in HLR indicates that the mobile station is deregistered for non-GPRS or the subscriber has not a non-GPRS subscription in the HLR. The VLR number is stored in the SGSN with the Gs interface option. For usage of the VLR number in SGSN, please refer to 3GPP TS 23.060 [21].

The VLR number is temporary subscriber data and is stored in the CSS. Absence of the VLR number in the CSS indicates that no subsequent update of the CSG subscription information is needed at the VLR upon CSG subscription change.

2.4.6 MSC number

MSC number is defined in 3GPP TS 23.003 [5].

The MSC number is temporary subscriber data and is stored in the HLR and conditionally in the VLR. For absence of the MSC number in the HLR, the remarks on VLR number apply accordingly, see clause 2.4.5.

2.4.7 HLR number

HLR number is defined in 3GPP TS 23.003 [5].

The HLR number may be stored in the VLR and Gn/Gp-SGSN. It is received as a mandatory parameter in the updating location accepted message. This data may be needed to retrieve subscribers to be restored after HLR reset.

The HLR number is temporary subscriber data and may optionally be stored in the VLR and Gn/Gp-SGSN.

2.4.8 GSN number

2.4.8.0 General

GSN number occurs as SGSN number and as GGSN number.

2.4.8.1 SGSN number

SGSN number is the SS7 address of the SGSN . It is defined in 3GPP TS 23.003 [5].

The SGSN number is temporary subscriber data and is stored in the HLR for a GPRS subscription. It is conditionally stored in the VLR if the Gs interface is installed. Absence of the SGSN number in the HLR indicates that the mobile station is deregistered for GPRS or the subscriber has no GPRS subscription in the HLR. Absence of the SGSN number in the VLR indicates that there is no association between the VLR and the SGSN for this MS. The SGSN number is to be distinguished from the SGSN address described in clause 2.13.10.

The SGSN number is temporary subscriber data and is stored in the CSS. Absence of the SGSN number in the CSS indicates that no subsequent update of the CSG subscription information is needed at the SGSN upon CSG subscription change.

2.4.8.2 GGSN number

GGSN number is the SS7 address of the GGSN .It is defined in 3GPP TS 23.003 [5]. Its usage is described in 3GPP TS 23.060 [21]. It is contained in the GGSN-list stored in the HLR and does not appear as separate subscriber data. Cf. clause 2.13.11.

2.4.8.3 IWF number

IWF number is the SS7 address of the IWF. It has the same format as a "VLR number" or "SGSN number" which are defined in 3GPP TS 23.003 [5]. Its usage is described in 3GPP TS 29.305 [83].

2.4.9 MLC number

The MLC number occurs as an SMLC number and as a GMLC number.

2.4.9.1 SMLC number (GSM only)

The SMLC number is the E.164 address of an NSS based SMLC.

The SMLC number is permanent data that may be stored in an MSC in association with either a set of IMSIs belonging to LMUs controlled by the SMLC or a set of cell identifiers belonging to the geographic area served by the SMLC.

2.4.9.2 GMLC number

The GMLC number is the E.164 address of the GMLC. One or more GMLC numbers may be stored in the MS subscriber data in the HLR and downloaded to the VLR and SGSN. These GMLC numbers identify the GMLCs for the particular MS from which a location request for this MS may be confined for particular LCS clients.

2.4.10 Subscription restriction

Subscription restriction is a parameter indicating whether or not certain restrictions apply to the subscription. The parameter takes either of the following values (see also GSM 02.13 [36]):

– accessible area for service;

– all GSM PLMNs;

– one national and all foreign GSM PLMNs;

– regionally restricted (part of a GSM PLMN in one country);

– regionally restricted plus all other GSM PLMNs.

The HLR/HSS associates location updating information with subscription restriction. It deregisters the MS if the PLMN is not allowed and sets:

– the MSC area restricted flag if the MSC area is not allowed, see clause 2.4.12;

– SGSN area restricted flag if the SGSN area is not allowed, see clause 2.4.14.

Handling of Regionally Restricted Subscription is defined in clause 2.4.11. By operator agreement, regional restriction in parts of different GSM PLMNs is also possible.

The subscription restriction is permanent subscriber data and is stored in the HLR.

2.4.11 Regional Subscription Information

If a mobile subscriber has a regional subscription, the HLR/HSS shall store a list of up to ten Regional Subscription Zone Identities (RSZIs) per Network Destination Code (NDC) of the PLMN involved. The structure of RSZI is defined in 3GPP TS 23.003 [5]; since it is composed of the PLMN identification (CC NDC) and the Zone Code it is sufficient to store the Zone Code List per CC NDC.

On updating the MME, VLR or the SGSN, the HLR/HSS identifies the VPLMN and NDC given by the VLR or SGSN number or VPLMN-Id and transfers the pertaining Zone Code List to the VLR or SGSN or MME. The VLR or SGSN or MME derives from the Zone Code List the allowed and not allowed MSC or SGSN or MME areas and location areas; it sets the "LA not allowed flag" should the target LAI of the mobile station be excluded, and it informs the HLR/HSS should the MSC or SGSN or MME area be excluded. Signalling of cause value "location area not allowed" towards the mobile station is defined in TSs 3GPP TS 29.002 [27] and 3GPP TS 24.008 [26].

2.4.11.1 RSZI lists

The RSZI lists are permanent subscriber data stored conditionally in the HLR/HSS.

2.4.11.2 Zone Code List

The VLR and the SGSN and the MME shall store as permanent and conditional subscriber data at least those Zone Codes by which they are affected.

2.4.12 MSC area restricted flag

MSC area restricted flag is a parameter which can take either of the following values:

– MSC area restricted;

– MSC area not restricted.

The parameter is set in the HLR during updating of the VLR. Handling of unsupported services and information received from the VLR based on national roaming or regionally restricted subscription (clause 2.4.11) determine its value. The parameter contributes to the "MS Not Reachable" state for handling of terminating traffic in the HLR. The default value is "MSC area not restricted".

The MSC area restricted flag is temporary subscriber data and is contained in the HLR.

2.4.13 LA not allowed flag

The LA not allowed flag is set in the VLR depending on National Roaming, Regionally Restricted Subscription and Roaming Restriction Due To Unsupported Feature, see 3GPP TS 29.002. It is applied to restrict service on a location area basis.

The LA not allowed flag is temporary subscriber data stored in the VLR.

2.4.14 SGSN area restricted flag

SGSN area restricted flag is a parameter which can take either of the following values:

– SGSN area restricted;

– SGSN area not restricted.

The parameter is set in the HLR during updating of the SGSN. Handling of unsupported services and information received from the SGSN based on national roaming or regionally restricted subscription (clause 2.4.11) determine its value. The parameter contributes to the "MS Not Reachable" state for handling of terminating traffic in the HLR. The default value is "SGSN area not restricted".

The SGSN area restricted flag is temporary subscriber data and is contained in the HLR.

2.4.14a RA not allowed flag

The RA not allowed flag is set in the SGSN depending on National Roaming, Regionally Restricted Subscription and Roaming Restricted in the SGSN Due To Unsupported Feature, see 3GPP TS 29.002. It is applied to restrict service on a routing area basis.

The RA not allowed flag is temporary subscriber data stored in the SGSN.

2.4.14b TA not allowed flag

The TA not allowed flag is set in the MME depending on National Roaming, Regionally Restricted Subscription and Roaming Restricted in the MME Due To Unsupported Feature, see 3GPP TS 29.272[81]. It is applied to restrict service on a tracking area basis.

The TA not allowed flag is temporary subscriber data stored in the MME.

2.4.15 Service restriction data induced by roaming

If in the course of roaming or at updating of the VLR or SGSN or MMEthe HLR/HSS is informed that the VLR or SGSN or MME does not support certain sensitive services or features, or, the HLR/HSS is informed in data request that the VLR or the SGSN or the MME supports only specific services, features or phases which do not correspond to subscribed services, features or phases, the HLR/HSS takes appropriate measures to restrict service for the mobile station in that VLR or SGSN or MME by setting and sending network induced replacing services such as available services, features or phases, barring programs or the roaming restriction for the MSC or SGSN or MME area.

These network-induced data have to be kept separate in the HLR, and where possible as discussed below in the VLR, from the permanent subscriber data of the call barring supplementary services, from the barring related data that can be modified by the subscriber or from the permanent regional subscription data.

These network-induced data have to be kept separate in the HLR/HSS, and where possible as discussed below in the SGSN and MME, from the permanent regional subscription data.

The network induced data take precedence over the subscriber data of the user where they are in conflict. If, in the course of roaming, restrictions caused by a service are lifted, the original subscriber data have to be re-installed both in HLR, in SGSN, in MME and in VLR when applicable, regarding any remaining restrictions due to other service replacements.

All network-induced restriction data are temporary subscriber data.

For ODB, 3GPP TS 23.015 [9] recommends mainly barring programs to replace this feature. The replacing barring data are conditionally stored in the HLR and VLR. In the VLR they cannot be distinguished from the permanent supplementary services data with the available signalling means, and no additional storage is needed. Interrogation shall reflect in both HLR and VLR the valid setting of the replacing temporary data; to prevent interference with Subscriber Controlled Input and to inform the customer on the restriction, the "control of barring services" subscription option is also temporarily set to the value "by the service provider".

CUG is also replaced by Outgoing Call Barring as described in 3GPP TS 23.085 [18].

Roaming restriction in the MSC area due to unsupported features is used to replace AoCC, see 3GPP TS 23.086, and Zone Codes for regional subscription, see clause 2.4.11 and 3GPP TS 29.002. A flag in the HLR and the VLR, see clause 2.4.15.2, collects the sources of network-induced roaming restriction which are also kept separate by the HLR.

Roaming restriction in the SGSN area due to unsupported features is used to replace Zone Codes for regional subscription, see clause 2.4.11 and 3GPP TS 29.002. A flag in the HLR and the SGSN, see clause 2.4.15.3, collects the sources of network-induced roaming restriction which are also kept separate by the HLR.

Roaming restriction in the MME area due to unsupported features is used to replace Zone Codes for regional subscription, see clause 2.4.11 and 3GPP TS 29.272[81]. A flag in the HSS and the MME, see clause 2.4.15.3a, collects the sources of network-induced roaming restriction which are also kept separate by the HSS.

2.4.15.1 ODB-induced barring data

ODB-induced barring data are temporary data stored conditionally in the HLR; they include the necessary replacing barring programs for outgoing and incoming calls depending on the ODB profile. The subscription option "control of barring services" is set to "by the service provider". The corresponding barring supplementary services for outgoing calls are set by the HLR and sent to the VLR.

2.4.15.2 Roaming restriction due to unsupported feature

Roaming restriction due to unsupported feature is a parameter which indicates that one or several services or features are not supported by the MSC, resulting in roaming restriction in the MSC area. It can take either of the following values:

– roaming restricted;

– roaming not restricted.

The parameter governs the "LA not allowed flag" in the VLR (see clause 2.4.13) and the "MSC area restricted flag" in the HLR (see clause 2.4.12); see also 3GPP TS 29.002.

The flag "roaming restriction due to unsupported feature" is temporary subscriber data stored in the VLR and in the HLR.

2.4.15.3 Roaming restricted in the SGSN due to unsupported feature

Roaming restricted in the SGSN due to unsupported feature is a parameter which indicates that one or several services or features are not supported by the SGSN, resulting in roaming restriction in the SGSN area. It can take either of the following values:

– roaming restricted;

– roaming not restricted.

The parameter governs the "RA not allowed flag" in the SGSN (see clause 2.4.14a) and the "SGSN area restricted flag" in the HLR (see clause 2.4.14); see also 3GPP TS 29.002.

The flag "roaming restricted in the SGSN due to unsupported feature" is temporary subscriber data stored in the SGSN and in the HLR.

2.4.15.3a Roaming restricted in the MME due to unsupported feature

Roaming restricted in the MME due to unsupported feature is a parameter which indicates that one or several services or features are not supported by the MME, resulting in roaming restriction in the MME area. It can take either of the following values:

– roaming restricted;

– roaming not restricted.

The parameter governs the "TA not allowed flag" in the MME (see clause 2.4.14b).

The flag "roaming restricted in the MME due to unsupported feature" is temporary subscriber data stored in the MME and in the HSS.

2.4.16 Cell Global ID or Service Area ID

The Cell Global ID or Service Area ID indicates the cell global identity of the cell in GSM (see 3GPP TS 23.003 [5]) or the service area identification of the service area in UMTS (see 3GPP TS 23.003 [5]) in which the MS is currently in radio contact or in which the MS was last in radio contact. The VLR and SGSN shall update the stored Cell Global ID or Service Area ID at establishment of every radio connection.

The cell ID is temporary subscriber data stored in the VLR and SGSN. It is conditional data, the VLR and SGSN shall store it whenever the subscriber data is marked as confirmed by radio contact.

The Cell Global ID or Service Area ID is temporary subscriber data stored in SGSN and GGSN/PDN-GW.

2.4.16A E-UTRAN Cell Global ID

The E-UTRAN Cell Global ID indicates the cell global identity of the cell in EPS (see 3GPP TS 23.003 [5]) in which the MS is currently in radio contact or in which the MS was last in radio contact.

The E-UTRAN Cell Global ID is temporary subscriber data stored in MME, PDN-GW and, when received via the SGs interface, in the VLR.

2.4.16B NR Cell Global Identity (NCGI)

The NR Cell Global Identity indicates the cell global identity of the cell in 5GS (see 3GPP TS 23.003 [5]) in which the UE is currently in radio contact or in which the UE was last in radio contact.

The NR Cell Global Identity is temporary subscriber data stored in AMF, SMF.

2.4.17 Localised Service Area Information

If a mobile subscriber has a localised service area subscription, the HLR shall store a list of up to 20 Localised Service Area Identities (LSA IDs) per PLMN. The structure of LSA ID is defined in 3GPP TS 23.003 [5].

On updating the VLR or the Gn/Gp-SGSN, the HLR identifies the VPLMN given by the VLR or SGSN number and transfers the applicable LSA ID List to the VLR or Gn/Gp-SGSN. The VLR or Gn/Gp-SGSN derives from the LSA ID List the allowed LSA(s), priority of each LSA, the preferential access indicator, the active mode support indicator and active mode indication and the "LSA only access" indicator.

2.4.17.1 LSA Identity

LSA Identity (LSA ID) is defined in 3GPP TS 23.003 [5]. The element uniquely identifies a LSA.

2.4.17.2 LSA Priority

Localised Service Area Priority (LSA Priority) is defined in GSM 08.08. The LSA Priority is permanent subscriber data stored conditionally in the HLR.

2.4.17.2A LSA Preferential Access Indicator

The Localised Service Area Preferential Access Indicator defines if the subscriber shall be favoured in cells belonging to the LSA at resource allocation compared to other subscribers. The LSA Preferential Access Indicator is permanent subscriber data stored conditionally in the HLR.

2.4.17.2B LSA Active Mode Support Indicator

The Localised Service Area Active Mode Support Indicator defines if cells belonging to the LSA shall be favoured for the subscriber compared to other cells at resource allocation. The LSA Active Mode Indicator is permanent subscriber data stored conditionally in the HLR.

2.4.17.3 LSA Only Access Indicator

The LSA Only Access Indicator defines if the subscriber is only allowed within its subscribed LSAs. The LSA Only Access Indicator is permanent subscriber data stored conditionally in the HLR.

2.4.17.4 LSA Active Mode Indicator

The Localised Service Area Active Mode Indicator defines if the LSA Identity of the cell in which the MS is currently in radio contact with shall be indicated to the subscriber in active mode. The LSA Active Mode Indicator is permanent subscriber data stored conditionally in the HLR.

2.4.17.5 VPLMN Identifier

The VPLMN Identifier identifies the VPLMN in which an LSA Identity is applicable. This identifier is not applicable to Universal LSA IDs as defined in 3GPP TS 23.003 [5]. The VPLMN identifier is permanent subscriber data stored conditionally in the HLR.

2.4.18 Access Restriction Data

The use of this data is described in 3GPP TS 23.221 [57] and in 3GPP TS 23.401 [74] clauses 4.3.28, 4.3.2a and 4.3.30.

The Access Restriction Data is permanent subscriber data and is conditionally stored per PLMN in the HLR/HSS, the VLR, the SGSN and the MME.

The parameter takes either of the following values:

– GERAN not allowed, the subscriber shall not be allowed to access the network in GERAN radio access. Valid for Idle and Connected mode;

– UTRAN not allowed, the subscriber shall not be allowed to access the network in LA/RAs using a UTRAN radio access. Valid for Idle and Connected mode;

– E-UTRAN not allowed, the subscriber shall not be allowed to access the network in TAs using a E-UTRAN radio access. Valid for Idle and Connected mode;

– GAN not allowed, the subscriber shall not be allowed to access the network via GAN;

– I-HSPA-Evolution not allowed, the subscriber shall not be allowed to access the network in LA/RAs using I-HSPA-Evolution radio access. Valid for Idle and Connected mode;

– HO-To-Non-3GPP-Access not allowed, the subscriber is not allowed to get EPS services that require handover support between 3GPP and non-3GPP accesses;

– NB-IoT not allowed, the subscriber shall not be allowed to access the network in TAs using a NB-IoT radio access. Valid for Idle and Connected mode;

– Enhanced Coverage not allowed, the subscriber shall not be allowed to use enhanced coverage;

– NR as secondary RAT not allowed, the subscriber shall not be allowed to access the network using NR radio access as secondary RAT. Valid for Idle and Connected mode;

– Unlicensed Spectrum as secondary RAT not allowed, the subscriber shall not be allowed to access the network using unlicensed spectrum in the form of LAA, LWA/LWIP or NR in unlicensed bands as secondary RAT. Valid for Idle and Connected mode.

– E-UTRAN(LEO) not allowed, the subscriber shall not be allowed to access the network in TAs using a E-UTRAN(LEO) satellite access. Valid for Idle and Connected mode;

– E-UTRAN(MEO) not allowed, the subscriber shall not be allowed to access the network in TAs using a E-UTRAN(MEO) satellite access. Valid for Idle and Connected mode;

– E-UTRAN(GEO) not allowed, the subscriber shall not be allowed to access the network in TAs using a E-UTRAN(GEO) satellite access. Valid for Idle and Connected mode;

– E-UTRAN(OTHERSAT) not allowed, the subscriber shall not be allowed to access the network in TAs using a E-UTRAN(OTHERSAT) satellite access. Valid for Idle and Connected mode;

– NB-IoT(LEO) not allowed, the subscriber shall not be allowed to access the network in TAs using a NB-IoT(LEO) satellite access. Valid for Idle and Connected mode;

– NB-IoT(MEO) not allowed, the subscriber shall not be allowed to access the network in TAs using a NB-IoT(MEO) satellite access. Valid for Idle and Connected mode;

– NB-IoT(GEO) not allowed, the subscriber shall not be allowed to access the network in TAs using a NB-IoT(GEO) satellite access. Valid for Idle and Connected mode;

– NB-IoT(OTHERSAT) not allowed, the subscriber shall not be allowed to access the network in TAs using a NB-IoT(OTHERSAT) satellite access. Valid for Idle and Connected mode;

– LTE-M(LEO) not allowed, the subscriber shall not be allowed to access the network in TAs using a LTE-M(LEO) satellite access. Valid for Idle and Connected mode;

– LTE-M(MEO) not allowed, the subscriber shall not be allowed to access the network in TAs using a LTE-M(MEO) satellite access. Valid for Idle and Connected mode;

– LTE-M(GEO) not allowed, the subscriber shall not be allowed to access the network in TAs using a LTE-M(GEO) satellite access. Valid for Idle and Connected mode;

– LTE-M(OTHERSAT) not allowed, the subscriber shall not be allowed to access the network in TAs using a LTE-M(OTHERSAT) satellite access. Valid for Idle and Connected mode;

Only the access restriction for WB-E-UTRAN and NB-IoT may include a different value per PLMN.

The use of this parameter for LA/RA/TA update procedures is described in 3GPP TS 23.012 [8], 3GPP TS 23.060 [21], and 3GPP TS 23.401 [74].

2.4.19 Selected CN operator ID

The selected CN operator ID indicates which core network operator Network Sharing supporting UEs have chosen in a shared network. The use of this data is described in 3GPP TS 23.251 [61]. And this data is identified by a PLMN ID (MCC+MNC) as described in 3GPP TS 23.003 [5].

The selected CN operator ID is temporary subscriber data stored conditionally in the VLR and the SGSN in a shared network for non-GPRS and GPRS services respectively.

This data is also stored in VLR for GPRS services if the Gs inerface is installed.

2.4.20 IP-SM-GW number

The IP-SM-GW number is the E.164 address of the IP-SM-GW.

The IP-SM-GW number indicates the address of the external IP-SM-GW that is registered for a subscriber to be used for delivering mobile terminated short messages. The IP-SM-GW number is temporary subscriber data and is stored conditionally in the HLR. The absence of the IP-SM-GW number in the HLR indicates that no external IP-SM-GW is registered; in this case an IP-SM-GW number pre-configured in the HLR can be used as an alternative route for delivering mobile terminated short messages.

2.4.20A IP-SM-GW Diameter Identity

The IP-SM-GW Diameter Identity indicates the Diameter Name and Realm of the external IP-SM-GW that is registered for a subscriber to be used for delivering mobile terminated short messages via Diameter. The IP-SM-GW Diameter Identity is temporary subscriber data and is stored conditionally in the HSS.

2.4.21 Paging Area

As an option, and for paging optimization purpose, the VLR may control Paging Areas. A Paging Area is a list of up to 5 Location Areas. The structure of the Location Area is specified in 3GPP TS 29.002 [27]. The Paging Area is temporary data stored in the VLR and in the HLR.

The use of this data is described in TS 23.012 [8] and in TS 23.018 [70].

2.4.22 Closed Subscriber Group Information

If a mobile subscriber has a Closed Subscriber Group (CSG) subscription, the HLR/HSS shall store Closed Subscriber Group Information which is a list of up to 50 CSG-Ids per PLMN and for each CSG-Id optionally an associated expiration date which indicates the point in time when the subscription to the CSG-Id expires and optionally corresponding APNs which can be accessed via Local IP access from this CSG identified by the CSG-Id; an absent expiration date indicates unlimited subscription; an expired expiration date may indicate that removal of the CSG-Id from the UE (e.g. by OMA DM or OTA update) is pending. The structure of CSG-Id is defined in 3GPP TS 23.003 [5].

On updating the VLR or the SGSN or MME, the HSS/HLR identifies and stores the VPLMN and the list of equivalent PLMNs provided by the VLR, SGSN or MME, and transfers the applicable CSG-Ids, expiration dates and the APNs allowed for LIPA (if present) to the VLR or SGSN or MME.

If an applicable (i.e. applicable for the current serving PLMN) CSG-Id is added to the Closed Subscriber Group Information in the subscriber data in the HLR/HSS, or an expiration date for an applicable CSG-Id is changed (added, modified or removed), or the APNs allowed for LIPA for an applicable CSG-Id is changed (added, modified or removed), then the HLR/HSS shall transfer applicable CSG-Ids, expiration dates, and APNs allowed for LIPA to the VLR or SGSN or MME.

NOTE 1: The APNs allowed for LIPA information are not applicable to the VLR.

When a CSG-Id expires, or the expiration date is changed (added or modified) to an expired date, the CSG-Id should be removed from the UE (e.g. by OMA DM or OTA update). After successful removal of the CSG-Id from the UE, the HLR/HSS should delete the CSG-Id and, if applicable, update the VLR or SGSN or MME. The two operations may not be correlated in the sense that they may be performed independently by different systems. The temporal relationship between the two operations is out scope of this specification and therefore depends on the operator policy.

If the subscription is terminated by other means than expiry, then CSG-Ids that are not expired should not be removed at the HLR/HSS; rather the expiration date may be modified to an expired date.

CSG-Ids that are expired should not be removed from the HLR/HSS before being removed from the UE.

NOTE 2: In the VLR or SGSN or MME an expired CSG-Id subscription indicates that the UE is not allowed service in the CSG. However, since the CSG-Id removal from the UE is pending, the UE may still camp on that CSG and therefore the UE may still be paged in the CSG.

Closed Subscriber Group Information is permanent subscriber data and is conditionally stored in HLR/HSS, VLR, SGSN, and MME.

2.4.23 Service Centre Address

The Service Centre Address, specified in the 3GPP TS 29.002 [27], represents the address of a Short Message Service Centre.

It is permanent subscriber data and is stored conditionally in the HLR/HSS and the IP-SM-GW (AS).

2.4.24 Subscribed Periodic LAU Timer

The Subscribed Periodic LAU Timer value (see 3GPP TS 23.012 [8]) is permanent data conditionally stored in the HLR and VLR. The use of this data is described in 3GPP TS 23.012 [8].

2.4.25 CSS number

CSS number is the international ISDN number of the CSS. It is defined in 3GPP TS 23.003 [5].

The CSS number is temporary subscriber data and is conditionally stored in the VLR and Gn/Gp-SGSN.

2.4.26 VPLMN Closed Subscriber Group Information

If the VPLMN supports VPLMN Autonomous CSG Roaming by providing CSG membership to the roaming subscriber, the CSS shall store Closed Subscriber Group Information which is a list of up to 50 CSG-Ids in the VPLMN and for each CSG-Id optionally an associated expiration date which indicates the point in time when the subscription to the CSG-Id expires; an absent expiration date indicates unlimited subscription. The structure of CSG-Id is defined in 3GPP TS 23.003 [5].

NOTE 1: The HPLMN enables Autonomous CSG Roaming in the VPLMN via Service Level Agreement.

When a CSG-Id expires, or the expiration date is changed (added or modified) to an expired date, the CSG-Id may be removed from the CSS and the VLR or SGSN or MME based on implementation.

If the subscription is terminated by other means than expiry, then CSG-Ids that are not expired should not be removed at the CSS; rather the expiration date may be modified to an expired date and then be updated by the CSS to the VLR or SGSN or MME.

VPLMN Closed Subscriber Group Information as described in 3GPP TS 29.002 [27] and 3GPP TS 29.272 [81] is permanent subscriber data and is conditionally stored in CSS, VLR, SGSN, and MME.

2.4.27 IAB-Operation Allowed indication

The IAB-Operation Allowed indication defines if the subscriber is allowed for IAB node operation as specified in 3GPP TS 23.401 [74].

The IAB-Operation Allowed indication is permanent subscriber data and is conditionally stored in the HSS and the MME.

2.5 Data related to basic services

2.5.1 Provision of bearer service

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 3GPP TS 22.002 [2] for which a subscription is required.

Provision of bearer service is permanent subscriber data and is stored in the HLR and VLR.

2.5.2 Provision of teleservice

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.

2.5.3 Bearer capability allocation

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 3GPP TS 29.007 [28]). 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 the3GPP TS 43.020 [31].

2.5.4 Transfer of SM option

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.

2.6 Data related to supplementary services

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 3GPP TS 23.081 [14] and following describing the network functionality of supplementary services. Additionally, subscriber data related to the Multicall (MC) supplementary service are contained in3GPP TS 23.135 [25].

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, 3GPP TS 23.085 [18]. All other data are conditional depending on the provision.

2.7 Mobile station status data

2.7.1 IMSI detached flag

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 3GPP TS 23.012 [8] and 3GPP TS 29.002 [27]. 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)

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 3GPP TS 23.060 [21]. It is temporary subscriber data stored in the HLR, in the Gn/Gp-SGSN and in the GGSN.

2.7.3 Mobility Management State

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 3GPP TS 23.060 [21]. It is temporary subscriber data stored in the SGSN.

2.7.4 Restoration flags

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

2.7.4.1 Confirmed by Radio Contact indicator

Confirmed by Radio Contact indicator is a restoration indicator defined in 3GPP TS 23.007 [6].

It is temporary subscriber data, stored in the VLR.

2.7.4.2 Subscriber Data Confirmed by HLR/HSS indicator

Subscriber Data Confirmed by HLR/HSS indicator is a restoration indicator defined in 3GPP TS 23.007 [6].

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 indicator

Location Information Confirmed in HLR/HSS indicator is a restoration indicator defined in 3GPP TS 23.007 [6].

It is temporary subscriber data, stored in the VLR and in the SGSN and in the MME.

2.7.4.4 Check SS indicator

Check SS indicator is a restoration indicator defined in 3GPP TS 23.007 [6].

It is temporary subscriber data and is stored in the HLR.

2.7.4.5 VLR-Reliable indicator

VLR-Reliable indicator is a restoration indicator defined in 3GPP TS 23.007 [6].

It is temporary subscriber data and is stored in the SGSN and in the MME.

2.7.5 MS purged for non-GPRS flag

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 flag

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.

2.7.6A UE purged in MME flag

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)

Mobile station Not Reachable via MSC Reason (MNRR-MSC) for SMS is defined in 3GPP TS 23.040 [10].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)

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

2.7.8 Subscriber data dormant

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 3GPP TS 23.012 [8]). 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

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 3GPP TS 23.018 [5a]. The parameter takes the following values: true or false.

The parameter is temporary subscriber data and is stored in the VLR.

2.7.9 Data related to UE reachability procedures

2.7.9.1 URRP-MME

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 3GPP TS 23.401 [74].

URRP-MME is temporary subscriber data conditionally stored in the MME and in the HSS.

2.7.9.2 URRP-SGSN

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 3GPP TS 23.060 [21].

URRP-SGSN is temporary subscriber data conditionally stored in the SGSN and in the HSS.

2.7.9.3 Service-related Entity list

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.

2.8 Data related to Operator Determined Barring

2.8.1 Subscriber status

Subscriber status is a flag which indicates whether the subscriber is subject to operator determined barring.

It is permanent subscriber data, and is conditionally stored in the HLR/HSS, the SGSN, the MME and the VLR.

2.8.2 Operator Determined Barring general data

2.8.2.1 Barring of outgoing calls

Barring of outgoing calls indicates which one of the following categories of operator determined barring of outgoing calls applies to the subscriber:

– No barring of outgoing calls;

– Barring of all outgoing calls;

– Barring of all outgoing international calls;

– Barring of all outgoing international calls except those directed to the home PLMN country;

– Barring of all outgoing inter-zonal calls;

– Barring of all outgoing inter-zonal calls except those directed to the home PLMN country;

– Barring of all outgoing international calls except those directed to the home PLMN country AND barring of all outgoing inter-zonal calls.

It is permanent data, and is stored conditionally in the HLR/HSS, the SGSN and the VLR.

2.8.2.2 Barring of incoming calls

Barring of incoming calls indicates which one of the following categories of operator determined barring of incoming calls applies to the subscriber:

– No barring of incoming calls;

– Barring of all incoming calls;

– Barring of all incoming calls when roaming outside the home PLMN country;

– Barring of all incoming calls when roaming outside the zone of the home PLMN country.

It is permanent data, and is stored conditionally in the HLR.

2.8.2.3 Barring of roaming

Barring of roaming indicates which one of the following categories of operator determined barring of roaming applies to the subscriber:

– No barring of roaming;

– Barring of roaming outside the home PLMN;

– Barring of roaming outside the home PLMN country.

It is permanent data, and is stored conditionally in the HLR/HSS for non-GPRS, GPRS subscription and EPS subscription.

2.8.2.4 Barring of premium rate calls

Barring of premium rate calls indicates which one of the following categories of operator determined barring of premium rate calls applies to the subscriber:

– No barring of premium rate calls;

– Barring of premium rate (information) calls;

– Barring of premium rate (entertainment) calls;

– Barring of premium rate (information) calls and premium rate (entertainment) calls.

It is permanent subscriber data, and is stored conditionally in the HLR and the VLR.

2.8.2.5 Barring of supplementary services management

Barring of supplementary services management is a flag which indicates whether the subscriber is subject to operator determined barring of supplementary services management.

It is permanent subscriber data, and is stored conditionally in the HLR and the VLR.

2.8.2.6 Barring of registration of call forwarding

Barring of registration of call forwarding indicates which one of the following categories of operator determined barring of registration of call forwarding applies to the subscriber:

– Barring of registration of any forwarded-to number;

– Barring of registration of any international forwarded-to number;

– Barring of registration of any international forwarded-to number except a number within the HPLMN country;

– Barring of registration of any inter-zonal forwarded-to number;

– Barring of registration of any inter-zonal forwarded-to number except a number within the HPLMN country.

It is permanent subscriber data, and is stored conditionally in the HLR.

2.8.2.7 Barring of invocation of call transfer

Barring of invocation of call transfer indicates which of the following categories of operator determined barring of invocation of call transfer applies to the subscriber:

One of:

– Barring of invocation of any call transfer;

– Barring of invocation of call transfer where at least one of the two calls is a call charged to the served subscriber;

– Barring of invocation of call transfer where at least one of the two calls is a call charged to the served subscriber at international rates;

– Barring of invocation of call transfer where at least one of the two calls is a call charged to the served subscriber at inter-zonal rates;

and independently:

– Barring of invocation of call transfer where both calls are calls charged to the served subscriber;

and independently:

– Barring of invocation of call transfer when there is an existing transferred call for the served subscriber in the same MSC/VLR.

It is permanent subscriber data, and is stored conditionally in the HLR and the VLR.

2.8.2.8 Barring of Packet Oriented Services

Barring of Packet Oriented Services indicates which one of the following categories of operator determined barring of Packet Oriented Services applies to the subscriber:

– Barring of all Packet Oriented Services;

– Barring of Packet Oriented Services from access points that are within the HPLMN whilst the subscriber is roaming in a VPLMN;

– Barring of Packet Oriented Services from access points that are within the roamed to VPLMN.

It is permanent subscriber data, and is stored conditionally in the HLR/HSS, the SGSN and MME.

2.8.3 Operator Determined Barring PLMN-specific data

Operator determined barring PLMN-specific data indicates which of the following categories of operator specific barring, in any combination, applies to the subscriber:

– Operator specific barring (type 1);

– Operator specific barring (type 2);

– Operator specific barring (type 3);

– Operator specific barring (type 4).

It is permanent subscriber data. It is stored conditionally in the HLR/HSS, the SGSN and in the VLR when the subscriber is registered in the home PLMN.

2.8.4 Notification to CSE flag

This information element indicates whether the change of ODB data shall trigger Notification on Change of Subscriber Data or not.

2.8.5 gsmSCF address list

This information element contains the list of gsmSCF addresses to which Notification on Change of Subscriber Data is to be sent.

2.9 Data related to handover

2.9.1 Handover Number

Handover Number is defined in 3GPP TS 23.003 [5] and its use is specified in 3GPP TS 23.009 [7].

The Handover Number is short-lived subscriber data and is stored in the VLR.

2.10 Data related to short message support

2.10.1 Messages Waiting Data (MWD)

Messages Waiting Data (MWD) is defined in 3GPP TS 23.040 [10].

The MWD is temporary subscriber data, and is conditionally stored in the HLR.

2.10.2 Mobile Station Not Reachable Flag (MNRF)

Mobile Station Not Reachable Flag (MNRF) is defined in 3GPP TS 23.040 [10].

The MNRF is temporary data. It is stored in the VLR, MME and conditionally stored in the HLR.

2.10.3 Memory Capacity Exceeded Flag (MCEF)

Memory Capacity Exceeded Flag (MCEF) is defined in 3GPP TS 23.040 [10].

The MCEF is temporary subscriber data and is conditionally stored in the HLR.

2.10.4 Mobile station Not Reachable for GPRS (MNRG)

For MNRG see clause 2.7.2.

2.10.4A UE Not Reachable via IP-SM-GW Flag (UNRI)

For UNRI see clause 3.2.5.

2.10.5 Mobile station Not Reachable via MSC Reason (MNRR-MSC)

For MNRR-MSC see clause 2.7.7.

2.10.5A Mobile station Not Reachable via SGSN Reason (MNRR-SGSN)

For MNRR-SGSN see clause 2.7.7A.

2.10.5B UE Not Reachable via IP-SM-GW Reason (UNRR)

For UNRR see clause 3.2.6.

2.10.6 MME Number for MT SMS

MME number for MT SMS is the E.164 address for the MME that supports SMS in MME. It is defined in 3GPP TS 23.003 [5]. Its usage is described in 3GPP TS 29.272 [81].

The MME number for MT SMS is temporary subscriber data and is stored in the HSS when the MME was registered as an MSC for MT SMS.

2.10.7 PS and SMS Only

This parameter indicates that the subscription is for PS Only, and permits CS service access only for SMS.

This parameter is permanent subscriber data and is conditionally stored in the HSS and SGSN.

2.10.8 SMS In SGSN Allowed

This parameter indicates that the SMS in SGSN feature is allowed for the user.

This parameter is permanent subscriber data and is conditionally stored in the HSS and SGSN.

2.11 Data related to subscriber trace

2.11.1 Trace Reference

The Trace Reference is defined in 3GPP TS 52.008 [37].

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

2.11.2 Trace Type

The Trace Type is defined in 3GPP TS 52.008 [37].

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

2.11.3 Operations Systems Identity

The Operations Systems Identity is defined in 3GPP TS 52.008 [37].

The Operations Systems Identity is permanent subscriber data and is conditionally stored in the HLR and VLR.

2.11.4 HLR Trace Type

The HLR Trace Type is defined in 3GPP TS 52.008 [37].

The HLR Trace Type is permanent subscriber data and is conditionally stored in the HLR.

2.11.5 MAP Error On Trace

The MAP Error On Trace is defined in 3GPP TS 52.008 [37].

The MAP Error On Trace is temporary subscriber data and is conditionally stored in the HLR.

2.11.6 Trace Activated in VLR

The Trace Activated in VLR flag is defined in 3GPP TS 52.008 [37].

The Trace Activated in VLR flag is temporary subscriber data and is conditionally stored in the HLR and VLR.

2.11.7 Trace Activated in SGSN

The Trace Activated in SGSN flag is defined in 3GPP TS 52.008 [37].

The Trace Activated in SGSN flag is temporary subscriber data and is conditionally stored in the HLR and SGSN.

2.11.8 Foreign Subscriber Registered in VLR

The Foreign Subscriber Registered in VLR flag is handled by operation and maintenance means in the VLR and is defined in 3GPP TS 52.008 [37].

The Foreign Subscriber Registered in VLR flag is permanent subscriber data and is conditionally stored in the VLR.

2.11.9 Trace Reference 2

Trace reference 2 is defined in 3GPP TS 32.421 [65[ and in 3GPP TS 32.422 [64].

The Trace Reference 2 is permanent subscriber data and is conditionally stored in the HSS/HLR, VLR, SGSN, MME , SGW, PGW and 3GPP AAA Server.

2.11.10 Trace depth

The Trace depth is defined in 3GPP TS 32.422 [64].

The Trace depth is permanent subscriber data and is conditionally stored in the HSS/HLR, VLR, SGSN, MME, SGW, PGW and 3GPP AAA Server.

2.11.11 List of NE types to trace

The List of NE types to trace is defined in 3GPP TS 32.422 [64].

The List of NE types to trace is permanent subscriber data and is conditionally stored in the HSS/HLR, VLR, SGSN, MME and 3GPP AAA Server.

2.11.12 Triggering events

The Triggering event is defined in 3GPP TS 32.422 [64].

The Triggering event is permanent subscriber data and is conditionally stored in the HSS/HLR, VLR, SGSN, MME, SGW, PGW and 3GPP AAA Server.

2.11.13 List of interfaces to trace

The List of interfaces to trace is defined in 3GPP TS 32.422 [64].

The List of interfaces to trace is permanent subscriber data and is conditionally stored in the HSS/HLR, VLR, SGSN, MME, SGW, PGW and 3GPP AAA Server.

2.11.14 IP address of Trace Collection Entity

The IP address of Trace Collection Entity is defined in 3GPP TS 32.422 [64].

The IP address of Trace Collection Entity is permanent subscriber data and is conditionally stored in the HSS/HLR, VLR, SGSN, MME, SGW, PGW and 3GPP AAA Server.

2.11.15 MDT-Configuration

The MDT-Configuration is defined in 3GPP TS 32.422 [64]. It contains:

Job type

Area Scope

List of measurements

Reporting Trigger

Report Interval

Report Amount

Event Threshold RSRP

Event Threshold RSRQ

Logging Interval

Logging Duration

The MDT-Configuration is permanent subscriber data and is conditionally stored in the HSS/HLR, VLR, SGSN, and MME.

2.11.16 MDT User Consent

The MDT User Consent parameter indicates whether the user has given his consent for MDT activation. For details see 3GPP TS 32.422 [64].

The MDT User Consent is permanent subscriber data and is conditionally stored in the HSS/HLR, VLR, SGSN, and MME.

2.12 Data related to the support of voice group and broadcast calls

2.12.1 VGCS Group Membership List

VGCS Group Membership List and its special condition of storage in VLR is defined in 3GPP TS 43.068 [33].

The VGCS Group Membership List is permanent subscriber data. It is stored conditionally in HLR and in the VLR.

2.12.2 VBS Group Membership List

VBS Group Membership List and its special condition of storage in VLR is defined in 3GPP TS 43.069 [34].

The VBS Group Membership List is permanent subscriber data. It is stored conditionally in HLR and in the VLR.

2.12.2.1 Broadcast Call Initiation Allowed List

The Broadcast Call Initiation Allowed List and its special condition of storage in VLR is defined in 3GPP TS 43.069[34].

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

2.13 Data related to PS NAM

The data listed in this clause pertain to the Network Access Mode "PS " and have no counterpart for CS.

2.13.1 PDP Type

PDP Type is defined in 3GPP TS 23.060 [21]. It indicates which type of protocol is used by the MS for a certain service, e.g. IP and X.25.

PDP Type is permanent subscriber data and conditionally stored in HLR, SGSN and GGSN.

2.13.2 PDP Address

PDP Address is defined in 3GPP TS 23.060 [21]. It holds the address of the MS for a certain service, e.g. an IP address. If dynamic addressing is allowed, PDP Address is empty in the HLR, and, before the PDP context is activated, empty in the SGSN.

PDP Address is permanent subscriber data and conditionally stored in HLR, SGSN and GGSN.

2.13.3 NSAPI

NSAPI is defined in 3GPP TS 23.060 [21]. It holds the index of the PDP Context.

NSAPI is temporary subscriber data and conditionally stored in SGSN and GGSN.

2.13.4 Packet Data Protocol (PDP) State

PDP State is defined in 3GPP TS 23.060 [21]. The PDP State is either ACTIVE or INACTIVE.

PDP State is temporary subscriber data and conditionally stored in SGSN.

2.13.5 New SGSN Address

New SGSN Address is defined in 3GPP TS 23.060 [21]. It is the IP-address of the new SGSN, to which N-PDUs should be forwarded from the old SGSN after an inter-SGSN routing update.

New SGSN Address is temporary subscriber data and conditionally stored in SGSN.

2.13.6 Access Point Name (APN)

Access Point Name (APN) is defined in 3GPP TS 23.003 [5] and 3GPP TS 23.060 [21] and 3GPP TS 23.401[74]. The APN field in the HLR/HSS contains either only an APN Network Identifier (i.e. an APN without APN Operator Identifier) or the wild card value (defined in 3GPP TS 23.003 [5]).APN is permanent subscriber data conditionally stored in HLR/HSS, in GGSN, SGSN, MME, S-GW, PDN and SCEF.

2.13.7 GGSN Address in Use

GGSN Address in Use is defined in 3GPP TS 23.060 [21]. It is the IP address of the GGSN currently used by a certain PDP Address of the MS.

GGSN Address is temporary subscriber data and conditionally stored in Gn/Gp-SGSN.

2.13.8 VPLMN Address Allowed

VPLMN Address Allowed is defined in 3GPP TS 23.060 [21]. It specifies per VPLMN whether the MS is allowed to use a dynamic address allocated in the VPLMN.

VPLMN Address Allowed is permanent subscriber data and conditionally stored in HLR and SGSN.

2.13.9 Dynamic Address

Dynamic Address is defined in 3GPP TS 23.060 [21]. It indicates whether the address of the MS is dynamic.

Dynamic Address is temporary subscriber data conditionally stored in GGSN.

2.13.10 SGSN Address

SGSN Address is defined in 3GPP TS 23.003 [5]. It is the IP Address of the SGSN currently serving the MS.

SGSN Address is temporary subscriber data stored in HLR and stored conditionally in GGSN. A pendant is the SGSN number, cf clause 2.4.8.

2.13.11 GGSN-list

GGSN-list is defined in 3GPP TS 23.060 [21]. It defines the GGSNs to be contacted when activity from the MS is detected and MNRG is set. It contains the GGSN number and optionally the GGSN IP address.

GGSN-list is temporary subscriber data stored in the HLR.

2.13.12 Quality of Service Subscribed

Quality of Service Subscribed is defined in 3GPP TS 23.060 [21]. It specifies the quality of service subscribed for a certain PDP context.

Quality of Service Subscribed is permanent subscriber data and conditionally stored in HLR and SGSN.

2.13.13 Quality of Service Requested

Quality of Service Requested is defined in 3GPP TS 23.060 [21]. It specifies the quality of service requested for a certain PDP context.

Quality of Service Requested is temporary subscriber data and conditionally stored in Gn/Gp-SGSN.

2.13.14 Quality of Service Negotiated

Quality of Service Negotiated is defined in 3GPP TS 23.060 [21]. It specifies the quality of service for a certain PDP context, negotiated between the MS and the SGSN, and then the GGSN.

Quality of Service Negotiated is temporary subscriber data and conditionally stored in Gn/Gp-SGSN and GGSN.

2.13.15 SND

SND is defined in 3GPP TS 23.060 [21]. It is the GPRS Tunnelling Protocol sequence number of the next downlink N‑PDU.

SND is temporary subscriber data conditionally stored in Gn/Gp-SGSN and GGSN.

2.13.16 SNU

SNU is defined in 3GPP TS 23.060 [21]. It is the GPRS Tunnelling Protocol sequence number of the next uplink N‑PDU.

SNU is temporary subscriber data and conditionally stored in SGSN and GGSN.

2.13.17 DRX Parameters

DRX Parameters is defined in 3GPP TS 23.060 [21].

DRX Parameters is temporary subscriber data stored in SGSN.

2.13.18 Compression

Compression is defined in 3GPP TS 23.060 [21]. There is one set of negotiated compression parameters per QoS priority level.

Compression is temporary subscriber data conditionally stored in the SGSN.

2.13.19 Non-GPRS Alert Flag (NGAF)

Non-GPRS Alert Flag (NGAF) is defined in 3GPP TS 23.060 [21]. It indicates whether activity from the MS shall be reported to the MSC/VLR.

NGAF is temporary subscriber data and is conditionally stored in the SGSN if the Gs interface is installed.

2.13.20 Classmark

MS Classmark is defined in 3GPP TS 24.008 [26].

Classmark is temporary subscriber data stored in the SGSN.

2.13.21 Tunnel Endpoint IDentifier (TEID)

Tunnel Endpoint Identifier is defined in 3GPP TS 29.060 [29]. TEID is temporary subscriber data conditionally stored in SGSN and GGSN.

2.13.22 Radio Priority

Radio Priority is defined in 3GPP TS 23.060 [21]. It indicates the RLC/MAC radio priority level for uplink user data transmission for a certain PDP context.

Radio Priority is temporary subscriber data and conditionally stored in SGSN.

2.13.23 Radio Priority SMS

Radio Priority SMS is defined in 3GPP TS 23.060 [21]. It indicates the RLC/MAC radio priority level for uplink SMS transmission.

Radio Priority SMS is temporary subscriber data and conditionally stored in SGSN.

2.13.24 PDP Context Identifier

PDP Context Identifier is defined in 3GPP TS 23.060 [21]. It identifies uniquely each PDP context.

PDP Context Identifier is permanent subscriber data and conditionally stored in HLR and Gn/Gp-SGSN.

2.13.25 PDP Context Charging Characteristics

PDP Context Charging Characteristics is defined in 3GPP TS 32. 251 [41]. It indicates the charging type to be applied to the PDP context.

PDP Context Charging Characteristics is permanent subscriber data and conditionally stored in HLR, SGSN and GGSN.

2.13.26 MME name

MME name is defined in 3GPP TS 23.003 [5].

The MME name is temporary subscriber data and is stored in the HSS. Absence of the MME name in HSS indicates that the UE is not registered for EPS via 3GPP E-UTRAN access. The MME name is conditionally stored in the VLR for MMEs for which the SGs interface is supported.

The MME name is temporary subscriber data and is stored in the CSS. Absence of the MME name in the CSS indicates that no subsequent update of the CSG subscription information is needed at the MME upon CSG subscription change.

2.13.27 VLR name

The VLR name is conditionally stored in the MME for VLRs for which the SGs interface is supported. Absence of the VLR name in MME indicates that there is no association between MME and VLR.

2.13.28 Non-EPS Alert Flag (NEAF)

Non-EPS Alert Flag (NEAF) indicates whether activity from the UE shall be reported to the VLR.

NEAF is temporary subscriber data and is conditionally stored in the MME for which the SGs interface is supported.

2.13.29 UE level APN-OI-Replacement

UE level APN-OI-Replacement (see 3GPP TS 23.401 [74] and 3GPP TS 23.060 [21]) is permanent data conditionally stored in the HSS and MME/SGSN.

2.13.30 Subscribed UE-AMBR

Subscribed UE-AMBR indicates the UE-AMBR for the uplink/downlink provided by the HSS to the MME/SGSN over the S6a/S6d/Gr interface for all non-GBR Bearers according to the subscription of the user.

Subscribed UE-AMBR (see 3GPP TS 23.401[74], 3GPP TS 23.060 [21] and 3GPP TS 23.501 [112]) is permanent data stored in HSS, SGSN, MME, UDM and AMF.

2.13.30A Used UE-AMBR

Used UE-AMBR indicates the UE-AMBR that is calculated by the MME/SGSN as the sum of the Used/Authorized APN-AMBRs of all active APNs up to the value of the Subscribed UE-AMBR.

Used UE-AMBR (see 3GPP TS 23.401[74] and 3GPP TS 23.060 [21]) is temporary data stored in MME and SGSN.

2.13.31 APN-Configuration-Profile

The APN-Configuration-Profile contains a Context-Identifier identifying the default APN-Configuration, optionally an additional Context-Identifer identifying another default APN-Configuration for those subscriptions having APNs with both, IP-based and Non-IP PDN types, and a list of APN-Configurations, each identified by a Context-Identifier. For detailed content see 3GPP TS 29.272[81] and 3GPP TS 29.273 [78].

The default APN configuration (default APN) for IP-based PDN types and the default APN for Non-IP PDN type are permanent data.

The list of APN-Configuration is permanent data stored in HSS, MME, S4-SGSN, ePDG and AAA-server with the following exceptions:

– PDN GW identity for the active IP-based PDN connections; stored in HSS if the user has non-3GPP subscription and the PDN connection is applicable to both 3GPP and non-3GPP accesses. For static PDN GW allocation, the PDN GW identity is also permanent data.

– APN-Specific-Data optionally stored as part of the APN context for the wildcard APN.

2.13.32 Subscribed APN-AMBR

Subscribed APN-AMBR indicates the APN-AMBR for the uplink/downlink provided by the HSS to the MME/SGSN over the S6a/S6d/Gr interface for all non-GBR Bearers according to the subscription of the user.

Subscribed APN-AMBR is part of each APN configuration (see 3GPP TS 29.272[81] and 3GPP TS 29.273[78]) and part of each PDP-Context (see 3GPP TS 29.002 [27]) and is permanent data stored in HSS, 3GPP AAA Server, MME, SGSN, GGSN, P-GW and ePDG(for GTP-based S2b only).

2.13.32A Used APN-AMBR

Used (Authorized) APN-AMBR indicates the APN-AMBR for the uplink/downlink authorized by the PCRF/PGW for all non-GBR bearers related with the same APN.

Used APN-AMBR is temporary data stored in MME, SGSN, GGSN and P-GW for each active APN (see 3GPP TS 23.401[74], 3GPP TS 23.060 [21] and 3GPP TS 23.402 [77]).

2.13.33 Subscribed-RAT-Frequency-Selection-Priority-ID

The Subscribed-RFSP-ID (see 3GPP TS 23.401 [74] and 3GPP TS 23.060 [21) is permanent data conditionally stored in HSS, S4-SGSN, Gn/Gp-SGSN and MME.

2.13.34 GUTI

The GUTI (see 3GPP TS 23.003 [5]) is temporary data conditionally stored in MME.

2.13.35 ME Identity

The ME Identity is temporary data and contains the IMEISV see clause 2.2.3.

2.13.36 Selected NAS Algorithm

Selected NAS security algorithm sent by MME to UE (see 3GPP TS 23.401 [74]) and is temporary data stored in MME

2.13.37 Selected AS Algorithm

Selected AS security algorithms are defined in 3GPP TS 23.401 [74] and is temporary subscriber data stored in the MME.

2.13.38 Context Identifier

Index of the PDN subscription context (see 3GPP TS 23.401 [74]) is permanent data stored in HSS and MME.

2.13.39 PDN Address

Indicates subscribed IPv4 address and/or IPv6 prefix is temporary data stored in S-GW, PDN-GW, MME, ePDG and 3GPP AAA Server, and is permanent data in HSS (static address allocation based on subscriber profile in HSS; see 3GPP TS 23.401 [74]).

2.13.40 VPLMN Address Allowed

VPLMN Address Allowed specifies per VPLMN whether for this APN the UE is allowed to use the PDN GW in the domain of the HPLMN only, or additionally the PDN GW in the domain of the VPLMN (see 3GPP TS 23.401 [74]). It is permanent data stored in HSS, and temporary data in MME, ePDG and 3GPP AAA Server.

2.13.41 PDN GW identity

PDN GW identity is the identity of the PDN GW used for this APN. The PDN GW identity may be an FQDN or an IP address. The PDN GW identity is permanent data in HSS when static assignment is used and temporary data in HSS when dynamic assignment is used. It is temporary data in MME, S4-SGSN, ePDG and 3GPP AAA Server.

2.13.42 Tracking Area List

Tracking area list contains the current list of tracking areas (see 3GPP TS 23.401 [74]) and is temporary data stored in MME.

2.13.43 APN Restriction

APN Restriction is defined in 3GPP TS 23.060 [21] for GPRS and in 3GPP TS 23.401 [74] for EPS. It is temporary data stored in MME, SGSN and S-GW and contains the maximum restriction for each PDP context/EPS Bearer Context.

2.13.44 APN in use

APN in use contains the APN (see 2.13.6) currently in use (see 3GPP TS 23.401 [74], 3GPP TS 23.060 [21] and 3GPP TS 23.402 [77] ) and it is temporary data stored in S4-SGSN, MME, S-GW, ePDG and PDN-GW.

2.13.45 TAI

TAI of the TA in which the last Tracking Area Update was initiated and is temporary data stored in MME, AMF and SMF and, when received via the SGs interface, in the VLR it contains the TAI of the last received E-UTRAN Cell Global ID.

2.13.46 E-UTRAN Cell Identity Age

E-UTRAN Cell Identity Age contains time elapsed since the last E-UTRAN Cell Global Identity was acquired (see 3GPP TS 23.401 [74]) and is temporary data stored in MME and, when received via the SGs interface, in the VLR.

2.13.47 MME F-TEID for S11 (Control Plane)

F-TEID for S11 is defined in 3GPP TS 29.274 [75]. MME F-TEID for S11 is temporary data conditionaly stored in MME and S-GW.

2.13.48 MME UE S1AP ID

"MME UE S1AP ID" is the Unique identity of the UE within MME (see 3GPP TS 23.401 [74]) and is temporary data stored in MME.

2.13.49 S-GW F-TEID for S11 (Control Plane)

F-TEID for S11 is defined in 3GPP TS 29.274[75]. S-GW F-TEID for S11 is temporary data conditionaly stored in MME and S-GW.

2.13.50 S4-SGSN F-TEID for S4 (Control plane)

F-TEID for S4 is defined in 3GPP TS 29.274[75]. S4-SGSN F-TEID for S4 is temporary data conditionally stored in S-GW and S4-SGSN.

2.13.51 S4-SGSN F-TEID for S4 (User plane)

F-TEID for S4 is defined in 3GPP TS 29.274[75]. S4-SGSN F-TEID for S4 is temporary data conditionally stored in S-GW and S4-SGSN.

2.13.52 S-GW F-TEID for S5/S8 (control plane)

F-TEID for S5/S8(control plane) is defined in 3GPP TS 29.274[75]. S-GW F-TEID for S5/S8(control plane) is temporary data conditionally stored in PDN-GWand S-GW.

2.13.53 S-GW F-TEID for S1-U

F-TEID for S1-U is defined in 3GPP TS 29.274[75]. S-GW F-TEID for S1-U is temporary data conditionally stored in eNodeB and S-GW.

2.13.54 S-GW F-TEID for S5/S8 (user plane)

F-TEID for S5/S8 (user plane) is defined in 3GPP TS 29.274[75]. S-GW F-TEID for S5/S8 (user plane) is temporary data conditionally stored in PDN-GWand S-GW.

2.13.55 eNodeB Address

The eNodeB Address identifies the IP address of the eNodeB currently used for control plane signalling (see 3GPP TS 23.401 [74]) and is temporary data stored in MME.

2.13.56 eNodeB UE S1AP ID

The "eNodeB UE S1AP ID " is the Unique identity of the UE within eNodeB (see 3GPP TS 23.401 [74]) and is temporary data stored in MME.

2.13.57 eNodeB F-TEID for S1-U

F-TEID for S1-U is defined in 3GPP TS 29.274[75]. The eNodeB F-TEID for S1-U is temporary data conditionally stored in eNodeB, S-GW and MME.

2.13.58 E-UTRAN/UTRAN Key Set flag

The "E-UTRAN/UTRAN Key Set flag" indicates whether the UE is using security keys derived from UTRAN or E-UTRAN security association (see 3GPP TS 23.401 [74]). E-UTRAN/UTRAN Key Set flag is temporary data conditionally stored in MME.

2.13.59 Selected CN operator id

Selected CN operator id contains the selected core network operator identity (to support network sharing as defined in TS 23.251 [61]). Selected CN operator id is temporary data conditionally stored in MME.

2.13.60 UE Radio Access Capability

UE Radio Access Capability (see 3GPP TS 23.401 [74]) is temporary data conditionally stored in MME.

NOTE: The actual size of UE Radio Access Capability depends on the features and bands supported by the UE and the eNodeB as specified in 3GPP TS 36.331[96]. Its size is constrained by the message size limits on the interfaces the information is conveyed (e.g. the maximum S1-AP SCTP packet size of 65535 bytes).

The MME shall store the UE Radio Access Capability Information received from the eNodeB without any truncation.

2.13.61 UE Network Capability

UE network capabilities (see 3GPP TS 23.401 [74]) including security algorithms and key derivation functions which shall be supported by the UE. UE Network Capability is temporary data conditionally stored in MME.

2.13.62 Location Change Report

Location Change Report indicates the requirement to communicate Cell or TAI to the PDN GW with this EPS bearer Context (see 3GPP TS 23.401 [74]) and is temporary data stored in MME and S4-SGSN.

2.13.63 UE Specific DRX Parameters

UE specific DRX parameters for A/Gb mode, Iu mode and S1-mode (see 3GPP TS 23.401[74]). UE specific DRX parameters are temporary data conditionaly stored in MME.

2.13.64 PDN-GW F-TEID for S5/S8 (user plane)

F-TEID for S5/S8 (user plane) is defined in 3GPP TS 29.274[75]. PDN-GW F-TEID for S5/S8 (user plane) is temporary data conditionally stored in PDN-GW, MME, S4-SGSN and S-GW for each EPS Bearer within the PDN connection see 3GPP TS 23.401[74] and 3GPP TS 23.060 [21].

2.13.65 PDN GW F-TEID for S5/S8 (control plane)

F-TEID for S5/S8 (control plane) is defined in 3GPP TS 29.274[75]. PDN-GW F-TEID for S5/S8 (control plane) is temporary data conditionally stored in PDN-GW, MME, S4-SGSN and S-GW.

2.13.66 EPS Bearer ID

An EPS bearer identity uniquely identifies an EPS bearer for one UE accessing via E-UTRAN, UTRAN, GERAN or an S2b bearer for one UE accessing via non-3GPP access with GTP on S2b. It also uniquely identifies an EPS bearer for a T6a connection to an SCEF.

EPS Bearer ID is temporary data stored in MME, S4 SGSN, S-GW, ePDG(for GTP-based S2b only) and PDN-GW for each EPS Bearer or S2b bearer within the PDN connection see 3GPP TS 23.401[74], 3GPP TS 23.060 [21] and 3GPP TS 23.402 [77].

When EPS Bearer ID identifies a T6a connection, EPS Bearer ID is temporary data stored in the MME and in the SCEF, see 3GPP TS 29.128 [106].

2.13.67 EPS Bearer QoS

EPS Bearer QoS contains QCI and ARP and optionally: GBR and MBR in case of GBR bearer. ARP contains a priority level, the preemption capability and the preemption vulnerability. EPS Bearer QoS is temporary data stored in MME, S4 SGSN, S-GW, ePDG(for GTP-based S2b only) and PDN-GW for each EPS Bearer within the PDN connection; see 3GPP TS 23.401 [74] , 3GPP TS 23.060 [21] and 3GPP TS 23.402 [77].

2.13.67A EPS Subscribed QoS Profile

EPS Subscribed QoS Profile contains QoS parameters (QCI and ARP) for the EPS default bearer of an APN, and it is permanent data stored in HSS, MME and S4-SGSN.

The QCI values allowed for the EPS Subscribed QoS Profile shall be only those associated to non-GBR bearers.

2.13.68 UL TFT

Uplink Traffic Flow Template for each EPS Bearer or S2b bearer within the PDN connection see 3GPP TS 23.401[74] and 3GPP TS 23.402 [77], and is temporary data stored inS-GW (for PMIP-based S5/S8 only), PDN-GW and ePDG (for GTP-based S2b only).

2.13.69 DL TFT

Downlink Traffic Flow Template for each EPS Bearer or S2b bearer within the PDN connection see 3GPP TS 23.401[74] and 3GPP TS 23.402 [77], and is temporary data stored inS-GW (for PMIP-based S5/S8 only) and PDN-GW.

2.13.70 Charging Id

Charging Id is defined in 3GPP TS 32.298[76] and temporary data conditionally stored in PDN-GW and S-GW for each EPS Bearer within the PDN connection see 3GPP TS 23.401[74].

2.13.71 EPS PDN Connection Charging Characteristics

EPS PDN Connection Charging Characteristics are defined in 3GPP TS 32.251[84] as permanent subscriber data conditionally stored in the HSS, 3GPP AAA Server and temporary data conditionally stored in MME, S-GW, ePDG and PDN-GW for each PDN connection see 3GPP TS 23.401[74] and 3GPP TS 23.402 [77].

2.13.72 Default bearer

Default bearer Identifies the EPS Bearer Id of the default bearer within the given PDN connection (see 3GPP TS 23.401[74] , 3GPP TS 23.060 [21] and 3GPP TS 23.402 [77] ) and is temporary data stored in MME , S4 SGSN, S-GW, ePDG (for GTP-based S2b only) and PGW.

2.13.73 Void

2.13.74 Void

2.13.75 RAT Type (Access Type)

RAT Type (radio access technology, access type) contains the current RAT type of the Last known access system. RAT Type is temporary data conditionally stored in HSS, 3GPP AAA Server, S4-SGSN, MME, S-GW, PDN-GW and ePDG.

The parameter takes the values as defined for RAT-Type AVP in the 3GPP TS 29.212 [90].

2.13.76 S101 HRPD access node IP address

S101 HRPD access node IP address contains the IP address of the HRPD AN used for the S101 tunnel for a UE (see 3GPP TS 23.402) and is temporary data stored conditionally in the MME.

2.13.77 S103 Forwarding Address

S103 Forwarding Address contains the HSGW IP address used for data forwarding to the HRPD access over S103 interface (see 3GPP TS 23.402) and is temporary data stored conditionally in the MME.

2.13.78 S103 GRE key(s)

GRE Key(s) used for the data forwarding tunnel to the HSGW – one per UE-PDN connection and is Temporary data conditionally stored S-GW.

2.13.79 Permanent User Identity

Permanent user identity is defined in 3GPP TS 23.003[5] and is permanent data mandatory stored in HSS, 3GPP AAA-server, 3GPP AAA-server proxy, PDN-GW S-GW and ePDG.

2.13.80 Mobility Capabilities

Mobility Capabilities is defined in 3GPP TS 29.273 [78] and is temporary data conditionally stored in ePDG, PDN-GW and 3GPP-AAA-server.

2.13.81 MAG IP address

MAG IP address is defined in 3GPP TS 29.273 [78] and is temporary data conditionally stored in 3GPP-AAA-server.

2.13.82 Visited Network Identifier

Visited Network Identifier is defined in 3GPP TS 29.273 [78] and is temporary data conditionally stored in 3GPP-AAA-server.

2.13.83 EAP payload

EAP payload is defined in 3GPP TS 29.273 [78]. and is temporary data conditionally stored in 3GPP-AAA-server.

2.13.84 Void

2.13.85 Void

2.13.86 MIP Subscriber profile

MIP Subscriber profile is defined in 3GPP TS 29.273 [78] and is temporary data conditionally stored in AAA-server and Trusted Non-3GPP or ePDG.

2.13.87 Uplink S5 GRE Key

Uplink traffic of a given PDN connection sent over PMIP-based S5 is encapsulated with the uplink S5 GRE key (see 3GPP TS 29.275[79]) and is temporary data stored in MME, SGW and PDN-GW.

2.13.88 Downlink S5 GRE Key

Downlink traffic of a given PDN connection sent over PMIP-based S5 is encapsulated with the downlink S5 GRE key (see 3GPP TS 29.275[79]) and is temporary data stored in SGW and PDN-GW.

2.13.89 Uplink S8 GRE Key

Uplink traffic of a given PDN connection sent over PMIP-based S8 is encapsulated with the S5/S8 uplink GRE key (see 3GPP TS 29.275[79]) and is temporary data stored in MME, SGW and PDN-GW.

2.13.90 Downlink S8 GRE Key

Downlink traffic of a given PDN connection sent over PMIP-based S8 is encapsulated with the S5/S8 uplink GRE key (see 3GPP TS 29.275[79]) and is temporary data stored in SGW and PDN-GW.

2.13.91 S2a GRE Keys

Traffic of a given PDN connection sent over PMIP-based S2a is encapsulated with the per-direction (uplink or downlink) S2a GRE key (see 3GPP TS 29.275[79]) and is temporary data stored in the Trusted non-3GPP Access’ MAG, and SGW (S2a chained with S8) or PDN-GW (unchained S2a).

2.13.92 S2b GRE Keys

Traffic of a given PDN connection sent over PMIP-based S2b is encapsulated with the per-direction (uplink or downlink) S2b GRE key (see 3GPP TS 29.275[79]) and is temporary data stored in the ePDG, and SGW (S2b chained with S8) or PDN-GW (unchained S2b).

2.13.93 Mobile Node Identifier

Mobile Node Identifier is defined in 3GPP TS 29.275[79] and is temporary data stored in SGW and PDN-GW.

For emergency attached UEs without IMSI (e.g. UICCless UE) or with an unauthenticated IMSI, the Mobile Node Identifier is derived from the UE IMEI to identify the UE.

2.13.94 IPv4 Default Router Address

IPv4 Default Router Address (see 3GPP TS 29.275[79]) is temporary data stored in SGW and PDN-GW.

2.13.95 Link-local address

Link-local address (see 3GPP TS 29.275[79]) is temporary data stored in SGW and PDN-GW.

2.13.96 Non 3GPP User Data

Non 3GPP User Data (see 3GPP TS 29.273 [78]) is permanent data conditionally stored in HSS. The Non 3GPP User Data (or a subset of it) is stored as temporary data also in the 3GPP AAA Server, Trusted Non-3GPP access network and ePDG. A further subset, the APN context for the served PDN connection is stored in the PDN GW as temporary data.

2.13.97 3GPP AAA Server Identity

The 3GPP AAA Server Identity is the Diameter identity of the 3GPP AAA server defined in 3GPP TS 29.273 [78] and is temporary data stored in the HSS, PDN GW, Trusted Non-3GPP access network and ePDG. Absence of the 3GPP AAA Server Identity in the HSS indicates that the UE is not registered for EPS via non 3GPP access.

2.13.98 Selected IP mobility mode

IP mobility mode is defined in 3GPP TS 24.302 [82] and is temporary data conditionally stored in the 3GPP AAA Server, Trusted Non-3GPP access network and ePDG.

2.13.99 Diameter Server Identity of HSS

The Diameter Server Identity of HSS identifies the HSS storing the EPS related data of a user. The format of the Diameter Server Identity is the Diameter Identity defined in IETF RFC 3588 [51].

The Diameter Server Identity of the HSS is temporary data and is conditionally stored in MME, S4-SGSN and 3GPP AAA Server.

2.13.100 SGSN name

SGSN name is defined in 3GPP TS 23.003 [5].

The SGSN name is temporary subscriber data and is stored in the HSS, if S6d interface is supported.

The SGSN name is temporary subscriber data and is stored in the CSS, if S7d interface is supported. Absence of the SGSN name in the CSS indicates that no subsequent update of the CSG subscription information is needed at the SGSN upon CSG subscription change.

2.13.101 S-GW F-TEID for S12

F-TEID for S12 is defined in 3GPP TS 29.274[75]. S-GW F-TEID for S12 is temporary data conditionally stored in RNC and S-GW.

2.13.102 RNC F-TEID for S12

F-TEID for S12 is defined in 3GPP TS 29.274[75]. RNC F-TEID for S12 is temporary data conditionally stored in RNC, S-GW and S4-SGSN.

2.13.103 MME F-TEID for S3

F-TEID for S3 is defined in 3GPP TS 29.274[75]. MME F-TEID for S3 is temporary data conditionally stored in S4-SGSN and MME.

2.13.104 S4-SGSN F-TEID for S3

F-TEID for S3 is defined in 3GPP TS 29.274[75]. S4-SGSN F-TEID for S3 is temporary data conditionally stored in S4-SGSN and MME.

2.13.105 PDN GW Allocation Type

PDN GW Allocation Type specifics if the PDN has been statically provisioned for a certain APN, or if it can be dynamically selected by the MME. It is permanent data stored in HSS, and temporary data stored in MME.

2.13.106 S-GW F-TEID for S4 (control plane)

F-TEID for S4 (control plane) is defined in 3GPP TS 29.274[75]. S-GW F-TEID for S4 (control plane) is temporary data conditionally stored in S4-SGSN and S-GW.

2.13.107 S-GW F-TEID for S4 (user plane)

F-TEID for S4 (user plane) is defined in 3GPP TS 29.274[75]. S-GW F-TEID for S4 (user plane) is temporary data conditionally stored in S4-SGSN and S-GW.

2.13.108 RAT-Frequency-Selection-Priority-ID in Use

The RFSP-ID in Use (see 3GPP TS 23.401 [74] and 3GPP TS 23.060 [21]) is temporary data conditionally stored in S4-SGSN, Gn/Gp-SGSN and MME.

2.13.109 APN level APN-OI-Replacement

APN level APN-OI-Replacement (see 3GPP TS 23.401 [74] and 3GPP TS 23.060 [21]) is permanent data conditionally stored in the HSS and MME/SGSN.

APN level APN-OI-Replacement has the same role as UE level APN-OI-Replacement.

If both the APN level APN-OI-Replacement and UE level APN-OI-Replacement are present, the APN level APN-OI-Replacement has a higher priority than UE level APN-OI-Replacement.

2.13.110 Unauthenticated IMSI

For an emergency attached UE with an unauthenticated IMSI, the Unauthenticated IMSI is temporary data stored in SGW and the PDN-GW. See 3GPP TS 29.275 [79].

2.13.111 PDN Connection ID

PDN Connection ID (see 3GPP TS 29.275[79]) is used to uniquely identify a PDN Connection over PMIP based interface if multiple PDN Connections to the same APN is supported. PDN Connection ID is temporary data and is conditionally stored in SGW, PDN-GW, trusted-non-3GPP access or ePDG if both MAG and LMA support multiple PDN connection to the same APN.

2.13.112 MS Network Capability

MS network capabilities (see 3GPP TS 23.060 [21]) including security algorithms and capabilities which shall be supported by the MS. MS Network Capability is temporary data conditionally stored in MME and SGSN.

2.13.113 Voice Domain Preference and UE’s Usage Setting

Voice domain preference and UE’s usage setting (see 3GPP TS 24.008 [26]) provides the network with the UE’s usage setting and the voice domain preference. The network uses the UE’s usage setting and the voice domain preference to select the RFSP index in use as specified in 3GPP TS 23.401 [74]. Voice domain preference and UE’s usage setting is temporary data conditionally stored in MME and SGSN.

2.13.114 SIPTO Permission

SIPTO Permission indicates whether the traffic associated with a particular APN is allowed or not for SIPTO above RAN, as defined in 3GPP TS 23.060 [21], 3GPP TS 23.401 [74] and 3GPP TS 23.402 [77].

The SIPTO Permission for the wild card APN shall apply to any APN that is not explicitly present in the subscription data.

SIPTO Permission is permanent data and is conditionally stored in the HSS, MME, SGSN, 3GPP AAA Server and Trusted Non-3GPP access network (eHRPD).

2.13.114A SIPTO Local Network Permission

SIPTO Local Network Permission indicates whether the traffic associated with a particular APN is allowed or not for SIPTO at the Local Network, as defined in 3GPP TS 23.060 [21] and 3GPP TS 23.401 [74].

The SIPTO Local Network Permission for the wild card APN shall apply to any APN that is not explicitly present in the subscription data.

SIPTO Local Network Permission is permanent data and is conditionally stored in the HSS, MME and SGSN.

2.13.115 Subscribed Periodic RAU/TAU Timer

The Subscribed Periodic RAU/TAU Timer (see 3GPP TS 23.401 [74] and 3GPP TS 23.060 [21]) is permanent data conditionally stored in the HLR/HSS, MME and SGSN.

2.13.116 ePDG F-TEID for S2b (control plane)

F-TEID for S2b (control plane) is defined in 3GPP TS 29.274[75]. ePDG F-TEID for S2b (control plane) is temporary data conditionally stored in ePDG (for GTP-based S2b only) and PGW.

2.13.117 ePDG F-TEID for S2b (user plane)

F-TEID for S2b (user plane) is defined in 3GPP TS 29.274[75]. ePDG F-TEID for S2b (user plane) is temporary data conditionally stored in ePDG (for GTP-based S2b only) and PGW.

2.13.118 PGW F-TEID for S2b (control plane)

F-TEID for S2b (control plane) is defined in 3GPP TS 29.274[75]. PGW F-TEID for S2b (control plane) is temporary data conditionally stored in ePDG (for GTP-based S2b only) and PGW.

2.13.119 PGW F-TEID for S2b (user plane)

F-TEID for S2b (user plane) is defined in 3GPP TS 29.274[75]. PGW F-TEID for S2b (user plane) is temporary data conditionally stored in ePDG (for GTP-based S2b only) and PGW.

2.13.120 MPS CS Priority

MPS CS Priority indicates that the UE is subscribed to the eMLPP in the CS domain, as defined in 3GPP TS 23.401 [74].

MPS CS Priority is permanent data and is conditionally stored in the MME.

NOTE: The MME gets the MPS CS Priority information from the HLR/HSS, which derives this information from the eMLPP Subscription Data as defined in the 3GPP TS 29.002 [27].

2.13.121 MPS EPS Priority

MPS EPS Priority indicates that the UE is subscribed to the MPS in the EPS domain, as defined in 3GPP TS 23.401 [74].

MPS EPS Priority is permanent data and is conditionally stored in the HLR/HSS and MME.

2.13.122 LIPA Permission

LIPA Permission indicates whether the corresponding APN is allowed to be accessed via Local IP Access, as defined in 3GPP TS 23.060 [21] and 3GPP TS 23.401 [74].

The LIPA Permission for a Wildcard APN applies to any APN that is not explicitly present in the subscription data.

LIPA Permission is permanent data and is conditionally stored in the HLR/HSS, MME and SGSN.

2.13.123 LIPA Allowed VPLMN List

LIPA Allowed VPLMN List indicates the PLMNs where the UE is allowed to use LIPA, it is permanent data and is conditionally stored in the HLR/HSS.

2.13.124 VPLMN LIPA Allowed

VPLMN LIPA Allowed indicates whether the UE is allowed to use LIPA in the PLMN where the UE is attached, as defined in the 3GPP TS 23.060 [21] and the 3GPP TS 23.401 [74].

VPLMN LIPA Allowed is permanent data and is conditionally stored in the MME and the SGSN.

2.13.125 Relay Node Indicator

Relay Node Indicator indicates whether the subscriber is a Relay Node (see 3GPP TS 36.300 [88]).

Relay Node Indicator is permanent data and is conditionally stored in the HLR/HSS and MME.

2.13.126 Restricted RAT Types

Restricted RAT Types contains the RAT types that are disallowed for a user when accessing EPS service from non-3GPP accesses.

Restricted RAT Types is permanent subscriber data and is conditionally stored in the HLR/HSS, 3GPP AAA Server, UDM and AMF.

The parameter takes either of the following values:

– WLAN not allowed, the subscriber shall not be allowed to access the network using WLAN radio access. Valid for Idle and Connected mode;

– CDMA2000_1X not allowed, the subscriber shall not be allowed to access the network using CDMA2000_1X radio access. Valid for Idle and Connected mode;

– HRPD not allowed, the subscriber shall not be allowed to access the network using HRPD radio access. Valid for Idle and Connected mode;

– UMB not allowed, the subscriber shall not be allowed to access the network using UMB radio access. Valid for Idle and Connected mode;

– EHRPD not allowed, the subscriber shall not be allowed to access the network using EHRPD radio access. Valid for Idle and Connected mode.

2.13.127 Higher bitrates than 16Mbps flag

Higher bitrates than 16Mbps flag (see 3GPP TS 23.060 [21]) is temporary data conditionally stored in Gn/Gp-SGSN or S4-SGSN.

2.13.128 Void

2.13.129 UE Local IP Address

UE Local IP Address is defined in 3GPP TS 23.139 [91]. UE Local IP Address is temporary data conditionally stored in the ePDG.

2.13.130 UE UDP Port Number

UE UDP Port Number is defined in 3GPP TS 23.139 [91]. UE UDP Port Number is temporary data conditionally stored in the ePDG.

2.13.131 H(e)NB Local IP Address

H(e)NB Local IP Address is defined in 3GPP TS 23.139 [91]. H(e)NB Local IP Address is temporary data conditionally stored in the MME, S4-SGSN, and P-GW.

2.13.132 H(e)NB UDP Port Number

H(e)NB UDP Port Number is defined in 3GPP TS 23.139 [91]. H(e)NB UDP Port Number is temporary data conditionally stored in the MME, S4-SGSN, and P-GW.

2.13.133 Diameter Server Identity of CSS

The Diameter Server Identity of CSS identifies the CSS storing theVPLMN CSG Roaming subscription related data of a user. The format of the Diameter Server Identity is the Diameter Identity defined in IETF RFC 3588 [51].

The Diameter Server Identity of the CSS is temporary data and is conditionally stored in MME and S4-SGSN.

2.13.134 MME/S4 SGSN Identifier

MME/S4-SGSN Identifier is defined in 3GPP TS 29.274 [75]. MME/S4 SGSN Identifier is temporary data conditionally stored in the SGW and PGW.

2.13.135 SGW node name

SGW node name is defined in 3GPP TS 29.274 [75]. SGW node name is temporary data conditionally stored in the MME/S4 SGSN.

2.13.136 Co-located GGSN-PGW FQDN

Co-located GGSN-PGW FQDN is defined in 3GPP TS 29.060 [29]. Co-located GGSN-PGW FQDN is temporary data conditionally stored in the MME/S4 SGSN/Gn/Gp SGSN.

2.13.137 GERAN Cell Identity Age

GERAN Cell Identity Age contains time elapsed since the last GERAN Cell Global Identity was acquired (see 3GPP TS 23.060 [21]) and is temporary data stored in SGSN.

2.13.138 UTRAN Service Area Identity Age

UTRAN Service Area Identity Age contains time elapsed since the last UTRAN Service Area Identity Age was acquired (see 3GPP TS 23.060 [21]) and is temporary data stored in SGSN.

2.13.139 Default APN for Trusted WLAN

The Default APN for Trusted WLAN identifies the subscriber’s default APN to be used for Trusted WLAN access to EPC over S2a in the Transparent single-connection mode. For detailed content see 3GPP TS 29.273 [78].

The Default APN for Trusted WLAN is permanent data conditionally stored in the HSS and 3GPP AAA Server.

2.13.140 Access Information for Trusted WLAN

The list of Access Information for Trusted WLAN contains information about the allowed access methods (i.e. EPC access and/or non-seamless WLAN offload) for a subscriber connecting via a trusted WLAN. For detailed content see 3GPP TS 29.273 [78].

The list of Access Information for Trusted WLAN is permanent data conditionally stored in the HSS and 3GPP AAA Server.

2.13.141 Homogeneous Support of IMS Voice over PS Sessions

Homogeneous Support of IMS Voice over PS Sessions (see 3GPP TS 23.401 [74] and 3GPP TS 23.060 [21]) is temporary data stored in the HSS/HLR, SGSN and MME.

2.13.142 Signalling Priority Indication

Signalling Priority Indication indicates that the UE signalled low access priority when the UE established the PDN connection or PDP context, as defined in 3GPP TS 23.401[74] and 3GPP TS 23.060 [21].

Signalling Priority Indication is temporary data conditionally stored in Gn/Gp-SGSN, S4-SGSN, MME, GGSN, SGW or PGW.

2.13.143 Restoration Priority

Restoration Priority is defined in 3GPP TS 23.007 [6]. It indicates the relative priority of a user’s PDN connection among PDN connections to the same APN when restoring PDN connections affected by an SGW or PGW failure/restart.

Restoration Priority is permanent subscriber data conditionally stored in the HSS, MME and S4-SGSN.

2.13.144 Void

2.13.145 Presence Reporting Area Action

Presence Reporting Area Action is defined in in 3GPP TS 23.060 [21] and in 3GPP TS 23.401 [74]. It denotes whether the MME/SGSN is requested to report changes of UE presence in Presence Reporting Area, and include the Presence Reporting Area Identifier, and the list of Presence Reporting Area elements if provided by the PGW.

Presence Reporting Area Action is temporary data conditionally stored in the MME, S4-SGSN and PGW.

2.13.146 WLAN offloadability

The WLAN offloadability information is a bitmask which indicates whether the traffic associated with the APN is allowed to be offloaded to WLAN from UTRAN or E-UTRAN. For detailed content see 3GPP TS 29.272 [81].

WLAN offloadability is permanent data and conditionally stored in HSS, MME, S4-SGSN.

2.13.147 CN Assistance Information

2.13.147.1 General

CN Assistance Information is a set of parameters which are calculated in the MME for the Core Network assisted eNodeB parameters tuning (see 3GPP TS 23.401 [74]); these parameters aid the eNodeB to minimize the UE state transitions and achieve optimum network behaviour.

2.13.147.2 Expected UE Activity Behaviour

The Expected UE Activity Behaviour (see 3GPP TS 36.413 [101]) indicates the expected pattern of the UE’s changes between ECM-CONNECTED and ECM-IDLE states.

Expected UE Activity Behaviour is temporary subscriber data and is conditionaly stored in the MME.

2.13.147.3 Expected HO Interval

The Expected HO Interval (see 3GPP TS 36.413 [101]) indicates the expected time interval between inter-eNB handovers of the UE.

Expected HO Interval is temporary subscriber data and is conditionaly stored in the MME.

2.13.148 Active Time Value for PSM

Active Time Value for PSM is defined in 3GPP TS 23.401[74] and 3GPP TS 23.060 [21]. Active Time Value for PSM is temporary data conditionaly stored in MME, S4-SGSN and Gn/Gp-SGSN.

2.13.149 Origination Time Stamp

The Origination Time Stamp indicates the time at which an entity originates a request. This is used for detecting and handling requests which collide with an existing session context. See 3GPP TS 29.274 [75].

The Origination Time Stamp is temporary data conditionally stored in PGW, 3GPP AAA Server and PCRF.

2.13.150 DL Data Buffer Expiration Time

DL Data Buffer Expiration Time is defined in 3GPP TS 23.060 [21] and 3GPP TS 23.401 [74]. It indicates the time until the SGW buffers DL data, for a UE that is transiently not reachable due to power saving functions, when the MME or SGSN has requested extended buffering at the SGW.

DL Data Buffer Expiration Time is temporary data conditionally stored in the MME, SGSN and SGW.

2.13.151 DL Buffering Suggested Packet Count

DL Buffering Suggested Packet Count is defined in 3GPP TS 23.060 [21] and 3GPP TS 23.401 [74]. It indicates the number of downlink packets the MME or SGSN suggests the SGW to store, for a UE that is transiently not reachable due to power saving functions, when the MME or SGSN requests extended buffering at the SGW.

DL Buffering Suggested Packet Count is permanent data conditionally stored in the HSS/HLR, MME, and the SGSN.

NOTE: The number of downlink packets the SGW decides to buffer is an implementation choice of the SGW, which can be dependent on the DL Buffering Suggested Packet Count.

2.13.152 Notify-on-available-after-DDN-failure flag

The Notify-on-available-after-DDN-failure flag is defined in 3GPP TS 23.682 [102].

The Notify-on-available-after-DDN-failure flag is temporary data conditionally stored in the MME and S4-SGSN.

2.13.153 IMSI Group Identifier List

IMSI Group Identifier (IMSI-Group-Id) is defined in 3GPP TS 23.003 [5].

A list of IMSI Group Identifier may be stored within the subscription data for a subscriber.

The IMSI Group Identifier List is permanent subscriber data conditionally stored in HSS, SGSN, MME, UDM and AMF.

2.13.154 UE Usage Type

The UE Usage Type indicates the usage characteristics of the UE for use with Dedicated Core Networks (DCN); it is subscription information that enables the UE to be served by a specific DCN (i.e., one or more MME/SGSN and optionally one or more SGW/PGW/PCRF), as described in 3GPP TS 23.401 [74].

UE Usage Type is permanent data and conditionally stored in HSS, MME, SGSN, UDM and AMF.

2.13.155 Emergency Indication

The Emergency Indication information indicates a UE request to establish a PDN connection for emergency services. See 3GPP TS 24.302 [82] and 3GPP TS 29.273 [78].

Emergency Indication is temporary data conditionally stored in the ePDG, 3GPP AAA Server and 3GPP AAA Proxy.

2.13.156 Remote UE Contexts

Remote UE Contexts is defined in 3GPP TS 29.274 [21]. Remote UE Contexts is temporary data conditionally stored in MME, SGW and PGW.

2.13.157 Extended Idle Mode DRX parameters

The Extended Idle Mode DRX parameters is defined in 3GPP TS 23.401 [74].

The Extended Idle Mode DRX parameters is temporary data conditionally stored in the MME and SGSN.

The Extended Idle Mode DRX cycle length (a part of the Extended Idle Mode DRX parameters) is permanent data stored in HSS.

2.13.158 Delay Tolerant Connection Indication

Delay Tolerant Connection Indication is defined in the 3GPP TS 23.401 [74] and 3GPP TS 23.060 [21]. Delay Tolerant Connection Indication is permanent data conditionally stored in MME, S4-SGSN, Gn/Gp-SGSN, PGW and GGSN.

2.13.159 Pending Network Initiated PDN Connection Signalling Indication

Pending Network Initiated PDN Connection Signalling Indication is defined in the 3GPP TS 23.401 [74] and 3GPP TS 23.060 [21]. Pending Network Initiated PDN Connection Signalling Indication is temporary data conditionally stored in MME, S4-SGSN and Gn/Gp-SGSN.

2.13.160 UE Radio Capability for Paging information

UE Radio Capability for Paging information is defined in the clause 5.11.4 of 3GPP TS 23.401 [74]. UE Radio Capability for Paging information is temporary data conditionally stored in MME.

2.13.161 Information on Recommended Cells and ENBs for Paging

Information on Recommended Cells and ENBs for Paging is defined in 3GPP TS 23.401 [74].

Information on Recommended Cells and ENBs for Paging is temporary data conditionally stored in the MME.

2.13.162 Paging Attempt Count

Paging Attempt Count is defined in 3GPP TS 23.401 [74].

Paging Attempt Count is temporary data conditionally stored in the MME.

2.13.163 User Plane Integrity Protection Indicator

User Plane Integrity Protection Indicator is defined in 3GPP TS 43.020 [31].

User Plane Integrity Protection Indicator is permanent data conditionally stored in the HSS and SGSN.

2.13.164 Non-IP-PDN-Type-Indicator

Non-IP-PDN-Type-Indicator is defined in 3GPP TS 29.272 [81]. It indicates whether the PDN type of the corresponding APN is Non-IP.

Non-IP-PDN-Type-Indicator is permanent subscriber data conditionally stored in the HSS and MME.

2.13.165 Non-IP-Data-Delivery-Mechanism

Non-IP-Data-Delivery-Mechanism is defined in 3GPP TS 29.272 [81]. It indicates the mechanism to be used for Non-IP Data Delivery over a certain APN.

The parameter takes either of the following values:

– SGi-Based-Data-Delivery;

– SCEF-Based-Data-Delivery.

Non-IP-Data-Delivery-Mechanism is permanent subscriber data conditionally stored in the HSS and MME.

2.13.166 SCEF-ID

SCEF-ID is defined in 3GPP TS 29.272 [81]. It indicates the identity (FQDN) of the SCEF to be used for Non-IP Data Delivery over a certain APN, when the selected data delivery mechanism is SCEF-based.

SCEF-ID is permanent subscriber data conditionally stored in the HSS and MME.

2.13.167 PDN Type

PDN Type is defined in 3GPP TS 29.274 [81]. It indicates whether the PDN type is IPv4, IPv6, IPv4v6, Non-IP, or Ethernet.

PDN Type is permanent subscriber data conditionally stored in the HSS, S4-SGSN, MME, SGW and PGW.

NOTE: The S4-SGSN doesn’t support Ethernet PDN type.

2.13.168 PDN-Connection-Restricted flag

The PDN-Connection-Restricted flag is defined in 3GPP TS 29.272 [81]. It indicates whether a registration without a PDN connection is enforced for this user when applicable.

The PDN-Connection-Restricted flag is permanent subscriber data conditionally stored in the HSS and MME.

2.13.169 Preferred-Data-Mode

Preferred-Data-Mode is defined in 3GPP TS 29.272 [81]. It indicates, for an SGi PDN connection, whether it is preferred to transmit the user’s traffic associated to the APN over the User Plane or the Control Plane.

Preferred-Data-Mode is permanent subscriber data conditionally stored in the HSS and MME.

2.13.170 IOV_updates counter

IOV_updates counter is defined in the 3GPP TS 29.060 [29]. IOV_updates counter is temporary data conditionally stored in a Gn/Gp-SGSN and S4-SGSN.

2.13.171 Emergency Info

Emergency Info is defined in 3GPP TS 29.272 [81]. It contains the identity of the PGW dynamically allocated for emergency services.

Emergency Info is temporary subscriber data conditionally stored in the HSS, 3GPP AAA Server, MME and ePDG.

2.13.172 Dedicated Core Network Identifier

Dedicated Core Network Identifier is defined in the 3GPP TS 23.003 [5]. Dedicated Core Network Identifier is temporary data conditionally stored in a Gn/Gp-SGSN, S4-SGSN and MME.

2.13.173 Acknowledgements Of Downlink NAS Data PDUs flag

The Acknowledgement Of Downlink NAS Data PDUs flag is defined in 3GPP TS 29.272 [81]. It indicates whether acknowledgement of downlink NAS data PDUs for Control Plane CIoT Optimization is disabled for the UE.

The Acknowledgement Of Downlink NAS Data PDUs flag is permanent subscriber data conditionally stored in the HSS and MME.

2.13.174 Service Gap Time

The Service Gap Time is defined in 3GPP TS 29.272 [81]. It indicates the minimum number of seconds during which the UE shall stay in ECM-IDLE mode, after leaving the ECM-CONNECTED mode, before being allowed to send a subsequent connection request to enter ECM-CONNECTED mode again.

The Service Gap Time is permanent subscriber data conditionally stored in the HSS and MME.

2.13.175 Subscribed Additional RRM Policy Index

The Subscribed Additional RRM Policy Index (see 3GPP TS 23.401 [74]) is permanent data conditionally stored in HSS and MME.

2.13.176 Additional RRM Policy Index in Use

The Additional RRM Policy Index in Use (see 3GPP TS 23.401 [74]) is temporary data conditionally stored in MME.

2.13.177 Ethernet-PDN-Type-Indicator

Ethernet-PDN-Type-Indicator is defined in 3GPP TS 29.272 [81]. It indicates whether the PDN type of the corresponding APN is Ethernet.

Ethernet-PDN-Type-Indicator is permanent subscriber data conditionally stored in the HSS and MME.

2.14 Data related to CAMEL

2.14.1 Subscriber Data stored in HLR

2.14.1.1 Originating CAMEL Subscription Information (O-CSI)

This data defines the contents of the Originating CAMEL subscription information used to interwork with the gsmSCF for MO and MF call. It consists of:

– A TDP list. The TDP list is a list of TDP descriptions. Each TDP description contains the following elements:

1. DP Value. The DP value identifies the DP in the MO State Model where service triggering may take place.
For O-CSI, the allowed DP value are DP Collected_info, DP Route_Select_Failure.

2. A gsmSCF address. It is the gsmSCF address ( E.164 number) where the CAMEL service is treated for the subscriber. A gsmSCF address is associated to each serviceKey.

3. A serviceKey. The serviceKey identifies to the gsmSCF the service logic. A serviceKey is associated to each TDP.

4. A default Call Handling. The default call handling indicates whether the call shall be released or continued as requested in case of error in the gsmSSF to gsmSCF dialogue. A default Call Handling is associated to each serviceKey.

5. DP criteria. The DP criteria indicates on which criteria the gsmSSF shall access the gsmSCF. DP criteria is associated to each TDP.

TDP	Triggering Criteria (see note)	ServiceKey	gsmSCF address	Default Call Handling
DP Collected_ Info	No Criterion Number criteria Basic service code criteria Call type criteria	One ServiceKey	One E.164 gsmSCF address	One Default call handling
DP Route_Select_ Failure	No criterion Cause value criteria	One ServiceKey	One E.164 gsmSCF address	One Default call handling
NOTE: One or more TDP criteria shall be applicable. All applicable triggering criteria must be satisfied before the dialogue is established with the gsmSCF.

– CAMEL capability handling. It gives the CAMEL phase associated to the O-CSI (CAMEL phase 1, phase 2, phase 3, or phase 4).

– The CSI state. The CSI state indicates whether the O-CSI is active or not.

– The notification flag, the notification flag indicates whether changes of the O-CSI shall trigger Notification on Change of Subscriber Data.

2.14.1.2 Terminating CAMEL Subscription Information (T-CSI) and VMSC Terminating CAMEL Subscription Information (VT-CSI));

This data defines the contents of the terminating CAMEL subscription information used to interwork with the gsmSCF for MT call. It consists of:

– A TDP list. The TDP list is a list of TDP descriptions. Each TDP description contains the following elements:

1. DP Value. The DP value identifies the DP in the MT State Model where service triggering may take place. For T-CSI, the allowed DP value are DP Terminating_Attempt_Authorised, DP T_Busy, DP T_No_Answer.

2. A gsmSCF address. It is the gsmSCF address (E.164 number) where the CAMEL service is treated for the subscriber. A gsmSCF address is associated to each serviceKey.

3. A serviceKey. The serviceKey identifies to the gsmSCF the service logic. A serviceKey is associated to each TDP.

5. DP criteria. The DP criteria indicates on which criteria the gsmSSF shall access the gsmSCF. DP criteria is associated to each TDP.

TDP	Triggering Criteria (see note)	ServiceKey	gsmSCF address	Default Call Handling
DP Terminating_ Attempt_Authorised	No Criterion Basic service criteria	One serviceKey	One E.164 gsmSCF address	One Default call handling
DP T_Busy	No criterion Cause value criteria	One serviceKey	One E.164 gsmSCF address	One Default call handling
DP T_No_Answer	No criterion Cause value criteria	One service Key	One E.164 gsmSCF address	One Default call handling
NOTE: One or more TDP criteria shall be applicable. All applicable triggering criteria must be satisfied before the dialogue is established with the gsmSCF.

– CAMEL capability handling. It gives the CAMEL phase associated to the T-CSI/VT-CSI (CAMEL phase1, phase2, or phase3, or phase4).

– The CSI state indicates whether the T-CSI/VT-CSI is active or not.

– Notification flag. The notification flag indicates whether the change of the T-CSI/VT-CSI shall trigger Notification on Change of Subscriber data.

2.14.1.3 Location information/Subscriber state interrogation.

This data item indicates whether or not the HLR shall send the location information and state of the called subscriber, as available, when a GMSC requests routeing information for an MT call.

2.14.1.4 USSD CAMEL subscription information(U-CSI)

This data is used on USSD request receipt from the MS. It consists of a list of:

– a service code: the service code defines a specific application in the gsmSCF;

– a gsmSCFaddress: it is the gsmSCF address (E.164 number) where the USSD application is treated for this subscriber.

2.14.1.5 Supplementary Service invocation notification(SS-CSI)

This data is used to notify the gsmSCF about Supplementary service invocation. It consists of:

– notification criterion, which may be a list of Supplementary Service(s). The possible Supplementary Services are: ECT, CD or MPTY, CCBS;

– a gsmSCFaddress: it is the gsmSCF address (E.164 number) where the notification of the Supplementary Service invocation is treated for this subscriber;

– CSI state, indicates whether the SS-CSI is active or not;

– notification flag: it indicates whether the change of the SS-CSI shall trigger Notification on Change of Subscriber data.

2.14.1.6 Translation Information flag (TIF-CSI)

– TIF-CSI flag is used to indicate that the HLR shall not attempt to perform any actions on the FTN (translation, prohibited FTN checks, call barring checks) at the registration procedure.

– Notification flag. The notification flag indicates whether the change of TIF-CSI flag shall trigger Notification on Change of Subscriber data.

2.14.1.7 Mobility Management event notification (M-CSI)

This data indicates which Mobility Management events shall be reported to the gsmSCF. It consists of:

– gsmSCF address: this is the address of the gsmSCF where the Mobility Management event notification shall be sent to. The gsmSCF address is in E.164 format.

– ServiceKey: the serviceKey is included in the notification to the gsmSCF and indicates to the gsmSCF which Service Logic shall be applied.

– Mobility Management Triggers: these triggers define which Mobility Managements events shall be reported to the gsmSCF. The mobility managements triggers may contain one or any combination of the following elements:

– Location update in the same VLR service area;

– Location update to another VLR service area;

– IMSI attach;

– MS initiated IMSI detach (explicit detach);

– Network initiated IMSI detach (implicit detach).

– The CSI state, indicates whether the M-CSI is active or not.

– Notification flag. The notification flag indicates whether the change of M-CSI shall trigger Notification on Change of Subscriber data.

2.14.1.8 Mobile Originated Short Message Service CAMEL Subscription Information (MO-SMS-CSI)

This data defines the contents of the MO SMS CAMEL subscription information. The MO SMS CAMEL Subscription Information is used for the following interworking:

– Interworking between gsmSCF and gsmSSF, for CAMEL control of circuit switched MO SMS;

– Interworking between gsmSCF and gprsSSF, for CAMEL control of packet switched MO SMS.

MO-SMS-CSI consists of the following data items:

– TDP List. The TDP list is a list of SMS TDP descriptions. Each TDP description contains the following elements:

1. DP Value. The DP value identifies the DP in the MO SMS State Model where service triggering may take place.
For MO-SMS-CSI, the only allowed DP value is SMS_Collected_Info.

2. gsmSCF Address. The gsmSCF address is the address (E.164 number) of the gsmSCF where the MO SMS CAMEL Service associated with this TDP, is located for this subscriber.

3. ServiceKey. The serviceKey identifies to the gsmSCF the service logic that shall be applied.

4. Default SMS handling. The default SMS handling indicates whether the MO SMS submission request shall be rejected or continued in the case of error in the dialogue between the gsmSSF and gsmSCF or between the gprsSSF and gsmSCF;

– CAMEL Capability Handling. CAMEL Capability Handling indicates the CAMEL Phase that is required for the MO SMS service. The CAMEL Capability Handling for MO-SMS-CSI shall have the value CAMEL phase 3.

– CSI state: indicates whether the MO-SMS-CSI is active or not.

– Notification flag indicates whether the change of the SMS-CSI shall trigger Notification on change of subscriber Data or not.

2.14.1.9 Mobile Terminating Short Message Service CAMEL Subscription Information (MT-SMS-CSI)

This data defines the contents of the mobile terminating short message service CAMEL subscription information. The MT-SMS-CSI CAMEL Subscription Information is used for the following interworking:

– Interworking between gsmSCF and gsmSSF, for CAMEL control of circuit switched MT SMS;

– Interworking between gsmSCF and gprsSSF, for CAMEL control of packet switched MT SMS.

MT-SMS-CSI consists of the following data items:

– TDP List. The TDP list is a list of MT SMS TDP descriptions. Each TDP description contains the following elements:

1. DP Value. The DP value identifies the DP in the MT SMS State Model where service triggering may take place.
For MT-SMS-CSI, the only allowed DP value is DP SMS-Delivery-Request

2. gsmSCF Address. The gsmSCF address is the address (E.164 number) of the gsmSCF where the MT SMS CAMEL Service associated with this TDP, is located for this subscriber.

3. ServiceKey. The serviceKey identifies to the gsmSCF the service logic that shall be applied.

4. Default SMS handling. The default SMS handling indicates whether the MT SMS delivery request shall be rejected or continued in the case of error in the dialogue between the gsmSSF and gsmSCF or between the gprsSSF and gsmSCF.

5. DP criterion. The DP criterion indicates on which criterion the gsmSSF shall access the gsmSCF. A DP criterion is associated with each TDP. For MT-SMS the DP criterion is the TDPU type. The criterion may be absent.

TDP	Triggering Criterion	ServiceKey	gsmSCF address	Default SMS Handling
DP SMS-Delivery Request	TDPU type	One serviceKey	One E.164 gsmSCF address	One Default SMS handling

– CAMEL Capability Handling. CAMEL Capability Handling indicates the CAMEL Phase that is required for the MT SMS service. The CAMEL Capability Handling for MT-SMS-CSI shall have the value CAMEL phase 4.

– CSI state: indicates whether the MT-SMS-CSI is active or not.

– Notification flag indicates whether the change of the MT-SMS-CSI shall trigger Notification on change of subscriber Data or not.

2.14.1.10 GPRS CAMEL Subscription Information (GPRS-CSI)

This data defines the contents of the GPRS CAMEL subscription information. The GPRS CAMEL Subscription Information is used for the interworking between gsmSCF and gprsSSF, for CAMEL control of packet switch call.

GPRS-CSI consists of the following data items:

– TDP List. The TDP list is a list of GPRS TDP descriptions. Each TDP description contains the following elements:

1. DP Value. The DP value identifies the DP in the GPRS State Model where service triggering may take place.

2. gsmSCF Address. The gsmSCF address is the address (E.164 number) of the gsmSCF where the GPRS CAMEL Service associated with this TDP, is located for this subscriber.

3. Service Key. The service key identifies to the gsmSCF the service logic that shall be applied.

4. Default GPRS handling. The default GPRS handling indicates whether the GPRS submission request shall be rejected or continued in the case of error in the dialogue between the gprsSSF and gsmSCF.

– CAMEL Capability Handling. CAMEL Capability Handling indicates the CAMEL Phase that is required for the GPRS service. The CAMEL Capability Handling for GPRS-CSI shall have the value CAMEL phase 3.

– The CSI state indicates whether the GPRS-CSI is active or not.

– The notification flag indicates whether the change of the GPRS-CSI shall trigger Notification on change of subscriber Data or not.

2.14.1.11 Dialled service CAMEL Subscription Information (D-CSI)

This data defines the contents of the dialled service CAMEL subscription information used to interwork with the gsmSCF for MO and MF call. It is applicable at TDP Analysed Info. It consists of:

– DP Criteria list. This consists of 1 to 10 entries. Each entry shall contain the following items:

1. DP Criterion. It indicates when the gsmSSF shall request gsmSCF for instructions. It is a destination number.

2. A gsmSCF address. It is the gsmSCF address (E.164 number) where this Subscribed Dialled CAMEL service is treated for the subscriber. A gsmSCF address is associated to each DP Criterion.

3. A serviceKey. The serviceKey identifies to the gsmSCF the service logic. A serviceKey is associated to each DP Criterion.

4. A default Call Handling. It indicates whether the call shall be released or continued as requested in case of error in the gsmSSF to gsmSCF dialogue. A default Call Handling is associated to each DP Criterion.

– CAMEL capability handling. It indicates the CAMEL phase associated to the D-CSI (CAMEL phase3, or Camel phase4 shall be indicated).

– CSI state: indicates whether the D-CSI is active or not.

– Notification Flag. It indicates whether the change of the D-CSI shall trigger the Notification on Change of Subscriber Data.

2.14.1.12 Mobility Management for GPRS event notification (MG-CSI)

This data indicates which Mobility Management for GPRS subscriber events shall be reported to the gsmSCF. It consists of:

– gsmSCF address: this is the address of the gsmSCF where the Mobility Management event notification shall be sent to. The gsmSCF address is in E.164 format.

– Service Key: the service key is included in the notification to the gsmSCF and indicates to the gsmSCF which Service Logic shall be applied.

– Mobility Management Triggers: these triggers define which Mobility Managements events shall be reported to the gsmSCF. The mobility management triggers may contain one or any combination of the following elements:

– Routeing area update of MS to a different SGSN service area;

– Routeing area update of MS within the same SGSN service area;

– GPRS attach (e.g. MS switched on, successful routeing area update after network initiated detach);

– MS-initiated GPRS detach (e.g. MS switched off);

– Network-initiated transfer to the "not reacheable for paging" state (the network has not received a periodic routeing area update from the MS and assumes that the MS is unreacheable).

– The CSI state indicates whether the MG-CSI is active or not.

– Notification flag. The notification flag indicates whether the change of MG-CSI shall trigger Notification on Change of Subscriber data.

2.14.2 Other Data stored in the HLR

2.14.2.1 Negotiated CAMEL Capability Handling

The HLR shall have a set of negotiated CAMEL Capability Handling variables. Each CSI that may be downloaded to the VLR or to the SGSN shall have a negotiated CAMEL Capability Handling (CCH) variable associated with it.

The negotiated CCH variable for a CSI indicates what CAMEL Phase is indicated in that CSI in the VLR or SGSN.

When the negotiated CCH variable has a value NULL, it indicates that the given CSI has not been downloaded to the VLR or SGSN.

The following table shows the negotiated CAMEL Capability Handling variables.

Variable name	Associated CSI	CSI stored in	Allowable values for negotiated CCH
O-CSI Negotiated CAMEL Capability Handling	O-CSI	VLR	NULL, 1, 2, 3, 4
D-CSI Negotiated CAMEL Capability Handling	D-CSI	VLR	NULL, 3, 4
SS-CSI Negotiated CAMEL Capability Handling	SS-CSI	VLR	NULL, 2
VT-CSI Negotiated CAMEL Capability Handling	VT-CSI	VLR	NULL, 3, 4
MO-SMS-CSI VLR Negotiated CAMEL Capability Handling	MO-SMS-CSI	VLR	NULL, 3
MT-SMS-CSI VLR Negotiated CAMEL Capability Handling	MT-SMS-CSI	VLR	NULL, 4
M-CSI Negotiated CAMEL Capability Handling	M-CSI	VLR	NULL, 3
MG-CSI Negotiated CAMEL Capability Handling	MG-CSI	SGSN	NULL, 4
MO-SMS-CSI SGSN Negotiated CAMEL Capability Handling	MO-SMS-CSI	SGSN	NULL, 3
MT-SMS-CSI SGSN Negotiated CAMEL Capability Handling	MT-SMS-CSI	SGSN	NULL, 4
GPRS-CSI Negotiated CAMEL Capability Handling	GPRS-CSI	SGSN	NULL, 3

There is no negotiated CAMEL Capability Handling variable associated with TIF-CSI.

The HLR does not store a Negotiated CAMEL Capability Handling for CSIs that are sent to the GMSC, since a subscriber is not permanently registered in a GMSC.

2.14.2.2 Supported CAMEL Phases

The HLR shall store the supported CAMEL Phases of the VLR where the subscriber is currently registered and the SGSN where the subscriber is currently attached.

The following variables are required:

– VLR Supported CAMEL Phases

– SGSN Supported CAMEL Phases

The HLR does not store the Supported CAMEL Phases of the GMSC, since a subscriber is not permanently registered at a GMSC.

2.14.2.2A Offered CAMEL4 CSIs

The HLR shall store the offered CAMEL4 CSIs of the VLR where the subscriber is currently registered and the SGSN where the subscriber is currently attached.

The following variables are required:

– VLR Offered CAMEL4 CSIs

– SGSN Offered CAMEL4 CSIs

The HLR does not store the Offered CAMEL4 CSIs of the GMSC, since a subscriber is not permanently registered at a GMSC.

2.14.2.3 UG-CSI

The USSD general CAMEL service(UG-CSI) is also stored in the HLR. This data is used on USSD request receipt from the MS. It consists of a list of:

– a service code. The service code defines a specific application in the gsmSCF;

– a gsmSCFaddress. It is the gsmSCF address (E.164 number) where the USSD application is treated for this subscriber.

2.14.2.4 gsmSCF address for CSI

This information element contains the list of gsmSCF address (E.164 address) to which Notification on Change of Subscriber Data is to be sent.

2.14.3 Subscriber data stored in VLR

2.14.3.1 Originating CAMEL Subscription Information (O-CSI)

The Originating CAMEL Subscription Information (O-CSI) are stored in the VLR.

This data defines the contents of the originating CAMEL subscription information used to interwork with the gsmSCF for MO and CF calls. It consists of:

– A TDP list: The TDP list is a list of TDP descriptions. Each TDP description contains the following elements:

1. DP Value. The DP value identifies the DP in the MO State Model where service triggering may take place.
For O-CSI, the allowed DP value are DP Collected_info, DP Route_Select_Failure.

2. A gsmSCF address. It is the gsmSCF address (E.164 number) where the CAMEL service is treated for the subscriber. A gsmSCF address is associated to each serviceKey.

3. A serviceKey. The serviceKey identifies to the gsmSCF the service logic.. A serviceKey is associated to each TDP.

5. DP criteria: The DP criteria indicates on which criteria the gsmSSF shall access the gsmSCF. DP criteria is associated to each TDP.

– CAMEL capability handling. It gives the CAMEL phase associated to the O-CSI (CAMEL phase1, or phase2, phase3, or phase4).

2.14.3.2 VMSC Terminating CAMEL Subscription Information (VT-CSI)

This data defines the contents of the visited terminating CAMEL subscription information used by the VMSC to interwork with the gsmSCF for an MT call. It consists of:

– A TDP list. The TDP list is a list of TDP descriptions. Each TDP description contains the following elements:

1. DP Value. The DP value identifies the DP in the MT State Model where service triggering may take place. For VT-CSI, the allowed DP value are DP Terminating Attempt Authorised, DP T_Busy, DP T_No_Answer.

2. A gsmSCF address. It is the gsmSCF address (E.164 number) where the CAMEL service is treated for the subscriber. A gsmSCF address is associated to each serviceKey.

3. A serviceKey. The serviceKey identifies to the gsmSCF the service logic. A serviceKey is associated to each TDP.

5. DP criteria: The DP criteria indicates on which criteria the gsmSSF shall access the gsmSCF.

– CAMEL capability handling. It gives the CAMEL phase associated to the VT-CSI. It is set to CAMEL phase3 or phase4.

2.14.3.3 Supplementary Service invocation notification(SS-CSI)

This data is used to notify the gsmSCF about Supplementary Service invocation. It consists of :

– a notification criterion, which may be ECT, CD or MPTY

– a gsmSCFaddress. It is the gsmSCF address (E.164 number) where the notification of the Supplementary service invocation is treated for this subscriber.

2.14.3.4 Mobility Management event notification (M-CSI)

This data indicates which Mobility Management events shall be reported to the gsmSCF. It consists of:

– gsmSCF address : This is the address of the gsmSCF where the Mobility Management event notification shall be sent to. The gsmSCF address must be in E.164 format.

– ServiceKey: The serviceKey is included in the notification to the gsmSCF and indicates to the gsmSCF which Service Logic shall be applied.

– Mobility Management Triggers. These triggers define which Mobility Managements events shall be reported to the gsmSCF. The mobility managements triggers may contain one or any combination of the following elements:

– Location update in the same VLR service area;

– Location update to another VLR service area;

– IMSI attach;

– MS initiated IMSI detach (explicit detach);

– Network initiated IMSI detach (implicit detach).

2.14.3.5 Mobile Originating Short Message Service CAMEL Subscription Information (MO-SMS-CSI)

This data defines the contents of the MO SMS CAMEL subscription information used for the interworking between gsmSCF and gsmSSF, for CAMEL control of circuit switched MO SMS.

MO-SMS-CSI consists of the following data items:

– TDP List. The TDP list is a list of SMS TDP descriptions. Each TDP description contains the following elements:

1. DP Value. The DP value identifies the DP in the MO SMS State Model where service triggering may take place.
For MO-SMS-CSI, the only allowed DP value is SMS_Collected_Info.

2. gsmSCF Address. The gsmSCF addess is the address (E.164 number) of the gsmSCF.

3. ServiceKey. The serviceKey identifies to the gsmSCF the service logic that shall be applied.

– CAMEL Capability Handling. CAMEL Capability Handling indicates the CAMEL Phase that is required for the MO SMS service.
The CAMEL Capability Handling for MO-SMS-CSI shall have the value CAMEL phase 3.

2.14.3.6 Mobile Terminating Short Message Service CAMEL Subscription Information (MT-SMS-CSI)

This data defines the contents of the mobile terminating short message service CAMEL subscription information. The MT-SMS-CSI CAMEL Subscription Information is used for interworking between gsmSCF and gsmSSF, for CAMEL control of circuit switched MT SMS.

MT-SMS-CSI consists of the following data items:

– TDP List. The TDP list is a list of MT SMS TDP descriptions. Each TDP description contains the following elements:

1. DP Value. The DP value identifies the DP in the MT SMS State Model where service triggering may take place.
For MT-SMS-CSI, the only allowed DP value is SMS-Delivery-Request

2. gsmSCF Address. The gsmSCF address is the address (E.164 number) of the gsmSCF where the MT SMS CAMEL Service associated with this TDP, is located for this subscriber.

3. Service Key. The service key identifies to the gsmSCF the service logic that shall be applied.

TDP	Triggering Criterion	ServiceKey	gsmSCF address	Default SMS Handling
DP SMS-Delivery Request	TDPU type	One serviceKey	One E.164 gsmSCF address	One Default SMS handling

2.14.3.7 Dialled service CAMEL Subscription Information (D-CSI)

This data defines the contents of the dialled service CAMEL subscription information used to interwork with the gsmSCF for MO and MF call. It is applicable at TDP Analysed Info. It consists of:

– DP Criteria list, this consists of 1 to 10 entries containing : DP Criterion: It indicates when the gsmSSF shall request gsmSCF for instructions.

1. A gsmSCF address. It is the gsmSCF address (E.164 number) where this Subscribed Dialled CAMEL service is treated for the subscriber. A gsmSCF address is associated to each DP Criterion.

2. A serviceKey. The serviceKey identifies to the gsmSCF the service logic. A serviceKey is associated to each DP Criterion.

3. A default Call Handling. It indicates whether the call shall be released or continued as requested in case of error in the gsmSSF to gsmSCF dialogue. A default Call Handling is associated to each DP Criterion.

– CAMEL capability handling. It indicates the CAMEL phase associated to the D-CSI (CAMEL phase3 or CAMEL phase4 shall be indicated).

2.14.3.8 Translation Information flag (TIF-CSI)

This flag is used to indicate that the VLR shall not attempt to perform any actions on the deflected to number (DTN).

2.14.4 Data stored in SGSN

2.14.4.1 Mobile Originating Short Message Service CAMEL Subscription Information (MO-SMS-CSI)

This data defines the contents of the MO SMS CAMEL subscription information. The MO-SMS-CSI in SGSN is used for the Interworking between SGSN and gsmSCF, for CAMEL control of packet switched MO SMS.

MO-SMS-CSI consists of the following data items:

– TDP List. The TDP list is a list of SMS TDP descriptions. Each TDP description contains the following elements:

1. DP Value. The DP value identifies the DP in the MO SMS State Model where service triggering may take place.
For MO-SMS-CSI, the only allowed DP value is SMS_Collected_Info.

2. gsmSCF Address. The gsmSCF addess is the address (E.164 number) of the gsmSCF where the MO SMS CAMEL Service associated with this TDP, is located for this subscriber.

3. ServiceKey. The serviceKey identifies to the gsmSCF the service logic that shall be applied.

4. Default SMS handling. The default SMS handling indicates whether the MO SMS submission request shall be rejected or continued in the case of error in the dialogue between the gprsSSF and gsmSCF.

– CAMEL Capability Handling. CAMEL Capability Handling indicates the CAMEL Phase that is required for the MO SMS service.
The CAMEL Capability Handling for MO-SMS-CSI in SGSN shall have the value CAMEL phase 3.

2.14.4.2 Mobile Terminating Short Message Service CAMEL Subscription Information (MT-SMS-CSI)

This data defines the contents of the mobile terminating short message service CAMEL subscription information. The MT-SMS-CSI CAMEL Subscription Information is used for the Interworking between gsmSCF and gprsSSF, for CAMEL control of packet switched MT SMS.

MT-SMS-CSI consists of the following data items:

– TDP List. The TDP list is a list of MT SMS TDP descriptions. Each TDP description contains the following elements:

1. DP Value. The DP value identifies the DP in the MT SMS State Model where service triggering may take place.
For MT-SMS-CSI, the only allowed DP value is SMS-Delivery-Request

2. gsmSCF Address. The gsmSCF address is the address (E.164 number) of the gsmSCF where the MT SMS CAMEL Service associated with this TDP, is located for this subscriber.

3. ServiceKey. The serviceKey identifies to the gsmSCF the service logic that shall be applied.

4. Default SMS handling. The default SMS handling indicates whether the MT SMS delivery request shall be rejected or continued in the case of error in the dialogue between the gprsSSF and gsmSCF.

TDP	Triggering Criterion	ServiceKey	gsmSCF address	Default SMS Handling
DP SMS-Delivery Request	TDPU type	One serviceKey	One E.164 gsmSCF address	One Default SMS handling

2.14.4.3 GPRS CAMEL Subscription Information (GPRS-CSI)

This data defines the contents of the GPRS CAMEL subscription information. The GPRS CAMEL Subscription Information is used for the interworkingbetween gsmSCF and gprsSSF, for CAMEL control of packet switch call.

The GPRS-CSI consists of the following data items:

– TDP List. The TDP list is a list of GPRS TDP descriptions. Each TDP description contains the following elements:

1. DP Value. The DP value identifies the DP in the GPRS State Model where service triggering may take place.

2. gsmSCF Address. The gsmSCF address is the address (E.164 number) of the gsmSCF where the GPRS CAMEL Service associated with this TDP, is located for this subscriber.

3. Service Key. The service key identifies to the gsmSCF the service logic that shall be applied.

4. Default GPRS handling. The default GPRS handling indicates whether the GPRS submission request shall be rejected or continued in the case of error in the dialogue between the gprsSSF and gsmSCF.

– CAMEL Capability Handling. CAMEL Capability Handling indicates the CAMEL Phase that is required for the GPRS service. The CAMEL Capability Handling for GPRS-CSI in SGSN shall have the value CAMEL phase 3.

2.14.4.4 Mobility Management for GPRS event notification (MG-CSI)

This data indicates which Mobility Management for GPRS events shall be reported to the gsmSCF. It consists of:

– gsmSCF address : This is the address of the gsmSCF where the Mobility Management for GPRS event notification shall be sent to. The gsmSCF address must be in E.164 format.

– Service Key: The service key is included in the notification to the gsmSCF and indicates to the gsmSCF which Service Logic shall be applied.

– Mobility Management Triggers. These triggers define which Mobility Management events shall be reported to the gsmSCF. The mobility management triggers may contain one or any combination of the following elements:

– Routeing area update of MS to a different SGSN service area;

– Routeing area update of MS within the same SGSN service area;

– GPRS attach (e.g. MS switched on, successful routeing area update after network initiated detach);

– MS-initiated GPRS detach (e.g. MS switched off);

– Network-initiated transfer to the "not reacheable for paging" state (the network has not received a periodic routeing area update from the MS and assumes that the MS is unreacheable).

2.15 Data related to IST

2.15.1 IST Alert Timer

The IST Alert Timer indicates the timer value that the VMSC and the GMSC shall use to inform the HLR about each of the call activities that an IST non-CAMEL subscriber performs.

This parameter is only sent to the VLRs which support the non-CAMEL IST functionality.

2.16 Data related to Location Services

2.16.1 Subscriber Data stored in HLR

2.16.1.1 Privacy Exception List

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 3GPP TS 23.271 [56].

2.16.1.2 GMLC Numbers

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

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

2.16.1.4 Service Types

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 3GPP TS 23.271 [56].

2.16.2 Data stored in GMLC

The GMLC stores data related to LCS clients. Refer to 3GPP TS 23.271 [56] for a detailed description.

2.16.3 Data stored in SMLC (GSM only)

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)

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)

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)

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

2.16.7.1 List of Broadcast Location Assistance Data Types

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 3GPP TS 23.271 [56].

2.17 Data related to Super-Charger

2.17.1 Age Indicator

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

2.18.1 CS Allocation/Retention priority

The Circuit Switched ( CS ) Allocation/Retention priority corresponds to the allocation/retention priority which is defined in 3GPP TS 23.107 [93]. 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

2.19.1 Subscribed Charging Characteristics

Subscribed Charging Characteristics are specified in 3GPP TS 32.251[84], 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 3GPP TS 23.060 [21], 3GPP TS 23.401 [74] and 3GPP TS 29.273[78]).

2.20 Data related to IMS Centralized Service

2.20.1 ICS Indicator

The ICS Indicator specifies whether or not the subscriber is an ICS user (see 3GPP TS 23.292 [71]).

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

NOTE: The value of ICS Indicator is unique for a given subscriber, for both CS and PS, so its value is the same when sent by the HSS/HLR to the MME/SGSN/VLR over the different interfaces.

2.21 Data related to SRVCC

2.21.1 STN-SR

2.21.1.1 General

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

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

2.21.1.2 STN-SR in EPS or GPRS

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.

NOTE: Backward compatibility cases (e.g. Pre-Release 10 AS) can still require provisioning of the STN-SR.

2.21.1.3 STN-SR in 5GS

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

2.21.2.1 General

This information element indicates the SRVCC capability of the UE and is described in 3GPP TS 23.237 [87].

2.21.2.2 UE SRVCC Capability in EPS

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

2.21.2.3 UE SRVCC Capability in 5GS

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

2.21.3 Subscribed vSRVCC

The Subscribed vSRVCC is permanent data and is conditionally stored in the HSS and MME (see 3GPP TS 23.216 [80]). 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

The CS to PS SRVCC Allowed indicator is permanent data and is conditionally stored in the HSS and VLR (see 3GPP TS 23.216 [80]). 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.

2.22 Data related to MBMS

2.22.1 MBMS GW F-TEID for Sm (Control Plane)

The MBMS GW F-TEID for Sm (Control Plane) is defined in 3GPP TS 29.274 [75]. MBMS GW F-TEID for Sm (control plane) is temporary data conditionally stored in MBMS GW and MME.

2.22.2 MBMS GW F-TEID for Sn (Control Plane)

The MBMS GW F-TEID for Sn (Control Plane) is defined in 3GPP TS 29.274 [75]. MBMS GW F-TEID for Sn (control plane) is temporary data conditionally stored in MBMS GW and SGSN.

2.22.3 Temporary Mobile Group Identity

Temporary Mobile Group Identity (TMGI) (see 3GPP TS 23.246 [85]) is permanent data stored in MBMS GW, MME, SGSN and BM-SC.

2.22.4 MBMS Flow Identifier

The MBMS Flow Identifier is defined in 3GPP TS 23.246 [85]. MBMS Flow Identifier is permanent data conditionally stored in MBMS GW, MME, SGSN and BM-SC.

2.22.5 MBMS IP Multicast Distribution

The MBMS IP Multicast Distribution is defined in 3GPP TS 29.274 [75]. MBMS IP Multicast Distribution is temporary data conditionally stored in MBMS GW, MME and SGSN.

2.22.6 MBMS Service Area

The MBMS Service Area is defined in 3GPP TS 23.246 [85]. MBMS Service Area is permanent data conditionally stored in MBMS GW, MME, SGSN and BM-SC.

2.22.7 MME F-TEID for Sm (Control Plane)

The MME F-TEID for Sm (Control Plane) is defined in 3GPP TS 29.274 [75]. This is temporary data conditionally stored in MBMS GW and MME.

2.22.8 SGSN F-TEID for Sn (Control Plane)

The SGSN F-TEID for Sn (Control Plane) is defined in 3GPP TS 29.274 [75]. This is temporary data conditionally stored in MBMS GW and S4-SGSN.

2.22.9 SGSN F-TEID for Sn (User Plane)

The SGSN F-TEID for Sn (User Plane) is defined in 3GPP TS 23.246 [85]. This is temporary data stored in MBMS GW and S4-SGSN.

2.22.10 MBMS session identifier

The MBMS Session identifier is defined in 3GPP TS 23.246 [85]. This is permanent data conditionally stored in MBMS GW, MME, SGSN and BM-SC.

2.22.11 MBMS session duration

MBMS session duration is defined in 3GPP TS 23.246 [85]. This is permanent data conditionally stored in MBMS GW, MME, SGSN and BM-SC.

2.22.12 QoS parameters

QoS parameters is defined in 3GPP TS 23.246 [85]. QoS is permanent data conditionally stored in MBMS GW, MME, SGSN and BM-SC.

2.22.13 MBMS Time to Data Transfer

The MBMS Time to Data Transfer is defined in 3GPP TS 23.246 [85]. This is permanent data conditionally stored in MBMS GW, MME, SGSN and BM-SC.

2.22.14 MBMS Data Transfer Start

The MBMS Data Transfer Start is defined in 3GPP TS 23.246 [85]. This is permanent data conditionally stored in MBMS GW, MME and BM-SC.

2.22.15 List of downstream nodes

The List of downstream nodes is defined in 3GPP TS 23.246 [85]. This is temporary data stored in MBMS GW, MME, SGSN and BM-SC.

2.22.16 MBMS Session Re-establishment Indication

The MBMS Session Re-establishment Indication is defined in 3GPP TS 23.007 [6]. This is temporary data conditionally stored in MME, SGSN, MBMS GW and BM-SC.

2.22.17 GCS AS Address

The GCS AS Address is defined in 3GPP TS 23.468 [95]. It is used to address the AS over the MB2-C reference point. This is temporary data stored in BM-SC.

2.22.18 MB2-U Port Number

The MB2-U Port Number is defined in 3GPP TS 23.468 [95]. It is used by the BM-SC to receive data related to one MBMS bearer from a GCS AS over the MB2-U reference point. This is temporary data stored in BM-SC.

2.22.19 MBMS Start Time

The MBMS Start Time is defined in 3GPP TS 23.468 [95]. This is temporary data stored in BM-SC.

2.22.20 TMGI Expiration Time

The TMGI Expiration Time is defined in 3GPP TS 23.468 [95]. This is temporary data stored in BM-SC.

2.22.21 MBMS Alternative IP Multicast Distribution

The MBMS Alternative IP Multicast Distribution is defined in 3GPP TS 29.274 [75]. The MBMS Alternative IP Multicast Distribution is temporary data conditionally stored in MBMS GW and MME.

2.22.22 MBMS Cell List

The MBMS Cell List is defined in 3GPP TS 23.246 [85]. The MBMS Cell List is permanent data conditionally stored in the BM-SC, MBMS GW and MME.

2.23 Data related to Cellular IoT Control Plane Optimizations

2.23.1 Robust Header Compression Context

The Robust Header Compression Configuration and Context contains the ROHC configuration and context used between the UE and the MME for the small data transferred over control plane. It is defined in IETF RFC 4995 [104]. The contents of the ROHC configuration and the ROHC context are specified in 3GPP TS 24.301 [105]. It is a temporary data conditionally stored in the MME.

2.23.2 Void

2.23.3 MME F-TEID for S11 (User Plane)

F-TEID for S11 is defined in 3GPP TS 29.274 [75].

MME F-TEID for S11 is temporary data conditionally stored in MME and S-GW.

2.23.4 S-GW F-TEID for S11(User Plane)

F-TEID for S11 is defined in 3GPP TS 29.274 [75].

S-GW F-TEID for S11 is temporary data conditionally stored in MME and S-GW.

2.23.5 Serving-PLMN-Rate-Control

The Serving-PLMN-Rate-Control contains the rate control information requested for CIoT in the serving PLMN. It is defined in 3GPP TS 23.682 [102] and 3GPP TS 29.128 [106]. It is permanent data conditionally stored in the MME, SGW, PGW and SCEF.

2.23.6 APN-Rate-Control

The APN-Rate-Control contains the rate control information per APN allowed for CIoT from the home operator. It is defined in 3GPP TS 23.682 [102] and 3GPP TS 29.128 [106]. It is permanent data conditionally stored in the SCEF and PGW.

2.23.7 Not Reachable for NIDD Flag

The Not Reachable for NIDD Flag is defined in 3GPP TS 29.128 [106]. It indicates that Non-IP Data has been attempted to be delivered by one or more SCEF(s) to a UE that is temporarily not reachable due to a power saving function (e.g. extended idle mode DRX or UE Power Saving Mode) and that the corresponding SCEF(s) need to be notified when the UE is reachable or about to become reachable.

The Not Reachable for NIDD Flag (together with the list of SCEF(s)) is temporary data conditionally stored in the MME.

2.23.8 NIDD Authorization

The NIDD Authorization contains whether the UE is authorized for MT/MO NIDD for a given APN, and the time period when this authorization is valid. It is permanent data conditionally stored in the HSS and SCEF.

2.24 Data related to ERP

2.24.1 General

Following clauses describe the data that are defined on a per user basis and are related to EAP-Reauthentication Protocol (ERP).

2.24.2 ERP-Authorization

ERP-Authorization is defined in 3GPP TS 29.273 [78].

ERP-Authorization is used to indicate if a user is authorized to use ERP.

ERP-Authorization is permanent data conditionally stored in the HSS and the 3GPP AAA Server.

2.24.3 ERP Keying Material

ERP Keying Material is composed of rMSK and eventually rMSK Lifetime.

rMSK and rMSK Lifetime are defined in IETF RFC 6696 [110].

ERP Keying Material is temporary data conditionnaly stored in the 3GPP AAA Server or the 3GPP AAA Proxy.

2.24.4 ERP Realm

ERP-Realm is defined in 3GPP TS 29.273 [78].

ERP-Realm is used to identify the realm in which is located the ER server that will serve the user.

ERP-Realm is permanent data conditionnaly stored in the 3GPP AAA Server or the 3GPP AAA Proxy.

2.25 Data related to the support of 5GS

2.25.1 SUPI

The Subscription Permanent Identifier (SUPI) is defined in clause 2.2A of 3GPP TS 23.003 [5]).

SUPI is permanent data conditionally stored in the UDM, AMF, SMF, SMSF and NEF.

2.25.2 GPSI

The Generic Public Subscription Identifier (GPSI) shall contain either an External Id (see clause 19.7.2 of 3GPP TS 23.003 [5]) or an MSISDN (see clause 3.3 of 3GPP TS 23.003 [5]). Multiple identifiers may be assigned to a user.

GPSI is permanent data conditionaly stored in the UDM, AMF, SMF and NEF.

2.25.3 Internal Group ID-list

Internal Group ID-list is a list of the subscribed internal group(s) that the UE belongs to.

Internal Group ID is permanent data conditionaly stored in the UDM, AMF and SMF.

2.25.4 Subscribed NSSAI

The Subscribed NSSAI (Network Slice Selection Assistance Information) represents the set of S-NSSAI(s) for a SUPI.

The NSSAI is permanent data conditionally stored in UDM, AMF and SMF.

2.25.5 Default S-NSSAI

The default S-NSSAI (Network Slice Selection Assistance Information) represents the default S-Nssai for a SUPI.

The default S-NSSAI is permanent data conditionally stored in UDM and AMF.

2.25.6 5G QoS Parameters

5G QoS Parameters (see 3GPP TS 23.501 [112]) are permanent data conditionally stored in UDM and SMF.

2.25.7 Forbidden area

Forbidden area defines areas in which the subscriber is not permitted to initiate any communication with the network (see 3GPP TS 23.501 [112] and 3GPP TS 23.316 [120]).

Forbidden area is permanent data conditionally stored in UDM and AMF.

2.25.8 Service Area Restriction

Service Area Restriction indicates either Allowed areas in which the UE is permitted to initiate communication with the network, or Non-allowed areas in which the UE and the network are not allowed to initiate Service Request or SM signalling to obtain user services. (see 3GPP TS 23.501 [112]) and 3GPP TS 23.316 [120]).

Service Area Restriction is permanent data conditionally stored in UDM and AMF.

2.25.9 RFSP Index

RAT/Frequency Selection Priority Index (RFSP Index), an index to a specific RRM configuration as defined in 3GPP TS 23.501 [112].

RFSP Index is permanent data and is conditionally stored in the UDM and AMF.

2.25.10 Priority Service

Priority indicates that the UE is subscribed to the MPS or MCX in the 5GS domain, as defined in 3GPP TS 23.501 [112] and 3GPP TS 23.379 [115].

Priority service is permanent data and is conditionally stored in the UDM and AMF.

2.25.11 DNN Info

Data Network Name Information (DNN Info) contains the DNN and optionaly the default DNN indicator and LBO roaming allowed for the DNN see 3GPP TS 29.503 [114].

DNN Info is permanent data and is conditionally stored in the UDM and SMF.

2.25.12 DNN Configuration

Data Network Name Configuration (DNN Configuration) contains the DNN, pduSessionTypes, SSC modes, 5G QoS parameters, sessionAMBR, 3gppChargingCharacteristics, static IP Address and acsInfo see 3GPP TS 29.503 [114].

DNN Configuration is permanent data and is conditionally stored in the UDM and SMF.

2.25.13 Steering of Roaming Information

Steering of roaming information (see 3GPP TS 29.503 [114]) contains e.g. the preferred PLMN/AccessTechnologies.

Steering of roaming information is temporary data and is conditionally stored in the UDM, AMF and AUSF.

2.25.14 SMS supported Data

SMS supported Data (see 3GPP TS 29.503 [114]) contains the supported SMS service delivery options of the UE.

SMS supported Data is temporary data and is conditionally stored in the UDM, AMFand SMSF.

2.25.15 SMSF Registrations

SMSF Registrations (see 3GPP TS 29.503 [114]) contains the SMSF address registered for SMS service.

SMSF Registration is temporary data and is conditionally stored in the UDM, AMF and SMSF.

2.25.16 SMS subscribed

SMS subscribed (see 3GPP TS 29.503 [114]) indicates if the subscriber has subscription for:

– MT SMS service

– MO SMS service.

SMS subscribed is permanent data and is mandatory stored in the UDM and SMSF.

2.25.17 SMS barring

SMS barring indicates if the subscriber has barrings for:

– Barring of all incoming calls for MT-SMS

– Barring of incoming calls for MT-SMS when roaming outside the Home Public Land Mobile Network (PLMN) country

– Barring of all outgoing calls for MO-SMS

– Barring of outgoing calls for MO-SMS when roaming outside the Home Public Land Mobile Network (PLMN) country.

SMS barring is permanent data and is conditionally stored in the UDM and SMSF.

2.25.18 SMS Roaming

The SMS Roaming (see 3GPP TS 29.503 [114]) if the subscriber is restriction for MT and MO SMS services when roaming.

The SMS Roaming is permanent data and is conditionally stored in the UDM, AMF and SMSF.

2.25.19 Core Network Type Restriction

Core Network Type Restriction defines the types of Core Networks that are disallowed for a UE.

Core Network Type Restriction is permanent data and is conditionally stored in the UDM and AMF.

2.25.20 LADN Information

LADN (Local Area Data Network) information (i.e. LADN service area information and LADN DNN) list of DNNs with LADN indication.

LADN Information is permanent data and is conditionally stored in the UDM and AMF.

2.25.21 Subscribed Periodic Registration Timer

Subscribed periodic registration timer (see 3GPP TS 23.502 [113]) is permanent data conditionally stored in UDM and AMF.

2.25.22 PEI

The PEI (see 3GPP TS 23.502 [113] and 3GPP TS 23.316 [120]) is temporary data conditionally stored in UDM, AMF and SMF.

2.25.23 5G GUTI

The 5G GUTI (see 3GPP TS 23.003 [5]) is temporary data conditionally stored in AMF.

2.25.24 PLMN Identifier

The PLMN Identifier identifies the VPLMN in which the subscriber is serving or allowed to serve. The PLMN identifier is permanent subscriber data stored conditionally in the UDM, AMF, SMF and SMSF.

2.25.25 PDU Session

The PDU session (see 3GPP TS 29.503 [114]) is the association between the UE and a Data Network that provides a PDU connectivity service.

The PDU session is temporary data conditionaly stored in the UDM, AMF and SMF.

2.25.26 Trace Data

The Trace Data (see 3GPP TS 32.422 [64]) is the association between the UE and a Data Network that provides a PDU connectivity service.

The Trace Data is permanent data conditionaly stored in the UDM, AMF and SMF.

2.25.27 Mobile Initiated Connection Only (MICO) mode

The Mobile Initiated Connection Only (MICO) mode (see 3GPP TS 23.501 [112]) provides the information if MICO mode is allowed.

The Mobile Initiated Connection Only (MICO) mode is permanent data conditionaly stored in the UDM and AMF.

2.25.28 UE purged in AMF flag

UE purged in AMF flag is set in the UDM per IMSI record in order to indicate that the subscriber data for the UE concerned have been purged in the AMF. The parameter shall take the following values:

– UE purged in AMF;

– UE not purged in AM.

The default value is "UE not purged in AMF". The parameter is temporary subscriber data, stored in the UDM.

2.25.29 GUAMI

The GUAMI (Globally Unique AMF Identifier) (see 3GPP TS 23.501 [112]) of the serving AMF.

The GUAMI is temporay data conditionaly stored in the UDM, SMF and AMF.

2.25.30 RAND, AUTN, XRES, CK’, IK’

Random Challenge (RAND), Authentication Token (AUTN), Expected Response (XRES), Cipher Key prime (CK’) and (IK’) form a quintuplet vector for user authentication based on EAP-AKA’ as defined in clause 6.1.3.1 of 3GPP TS 33.501 [116].

This quintuplet is provided by the UDM to the AUSF.

2.25.31 RAND, AUTN, XRES*

Random Challenge (RAND), Authentication Token (AUTN) and Expected Response prime (XRES*) form a triplet for user authentication based on 5G AKA as defined in clause 6.1.3.2.0 of 3GPP TS 33.501 [116].

This triplet is provided by the UDM to the AUSF. The Expected Response prime (XRES*) is used in particular during the confirmation phase by the AUSF.

2.25.32 RAND, AUTN, HXRES*

Random Challenge (RAND), Authentication Token (AUTN) and H-Expected Response prime (HXRES*) form a triplet for user authentication based on 5G AKA as defined in clause 6.1.3.2.0 of 3GPP TS 33.501 [116].

This triplet is provided by the AUSF to the AMF.

2.25.33 Kausf

The Kausf is defined in 3GPP TS 33.501 [116]. It is a key either provided by the UDM if 5G-AKA is selected as authentication method or derived at the AUSF if EAP-AKA’ is selected.

NOTE: For 5G-AKA, the Kausf is provided along with RAND, AUTN and XRES*.

The Kausf is temporary data condtionnaly stored at the AUSF.

2.25.34 Kseaf

The Kseaf is defined in 3GPP TS 33.501 [116]. It is a key provided by the AUSF to the AMF acting as an SEAF.

NOTE: For 5G-AKA, the Kseaf is provided if confirmation from AUSF is successful.

2.25.35 AuthenticationMethod

The AuthenticationMethod is described in 3GPP TS 33.501 [116].

The AuthenticationMethod is permanent data mandatory stored at the UDM.

2.25.36 PermanentKey

The PermanentKey is described in 3GPP TS 33.501 [116]. The permanent key shall be stored encrypted.

The PermanentKey is permanent data contitionaly stored at the UDM.

2.25.37 SequenceNumber

The SequenceNumber is described in 3GPP TS 33.102 [52].

The SequenceNumber is temporary data conditionaly stored at the UDM.

2.25.38 AuthenticationManagementField

The AuthenticationManagementField is described in 3GPP TS 33.501 [116].

The AuthenticationManagementField is permanent data conditionaly stored at the UDM.

2.25.39 VectorAlgorithm

The VectorAlgorithm the algorithm used for the generation of authentication vectors see 3GPP TS 29.505 [119].

The VectorAlgorithm is permanent data conditionaly stored at the UDM.

2.25.40 Milenage

The Milenage described in 3GPP TS 35.206 [117].

The Milenage is permanent data conditionaly stored at the UDM.

2.25.41 Tuak

The Tuak described in 3GPP TS 35.231 [118].

The Tuak is permanent data conditionaly stored at the UDM.

2.25.42 Opc

The Opc described in 3GPP TS 35.205 [117].

The Opc is permanent data conditionaly stored at the UDM.

2.25.43 Topc

The Topc described in 3GPP TS 35.231 [118].

The Topc is permanent data conditionaly stored at the UDM.

2.25.44 Authentication Status

The authentication status of the UE contains authentication result, timestamp, and the serving network name.

The Authentication Status is temporary data conditionaly stored at the UDM.

2.25.45 SoR-XMAC-I_UE

The SoR-XMAC-I_UE of the UE contains the expected SoR-XMAC-I_UE as specified in 3GPP TS 33.501 [116].

The SoR-XMAC-I_UEis temporary data conditionaly stored at the UDM.

2.25.46 Shared Data Ids

The Shared Data Id is defined in 3GPP TS 29.503 [114].

Shared Data Ids are permanent data and are conditionally stored in the UDM, AMF, SMSF and SMF.

2.25.47 Access Restriction Data

The use of this data is described in 3GPP TS 23.501 [112] clause 5.3.4.1.1.

The Access Restriction Data is permanent subscriber data and is conditionally stored per PLMN in the UDM and the AMF.

The parameter takes either of the following values:

– NR not allowed as primary RAT, the subscriber shall not be allowed to access the network in TAs using NR radio access. Valid for Idle and Connected mode;

– NR not allowed as secondary RAT, the subscriber shall not be allowed to access the network using NR radio access as secondary RAT. Valid for Connected mode;

NOTE: As specified in clause 4.11.1.2.1 of 3GPP TS 23.502 [113], this restriction can also be applied when attached to EPC depending on operator policy, and in this case AMF will send this information to MME during handover from 5GC to EPC in order to allow MME to make appropriate handling, e.g. SGW selection based on access restriction, or whether or not to allocate resources for secondary RAT during inter RAT handover.

– NR in unlicensed bands not allowed as primary RAT, the subscriber shall not be allowed to access the network in TAs using NR radio access in unlicensed bands. Valid for Idle and Connected mode;

– NR in unlicensed bands not allowed as secondary RAT, the subscriber shall not be allowed to access the network using NR radio access in unlicensed bands as secondary RAT. Valid for Connected mode;

– E-UTRA not allowed as primary RAT, the subscriber shall not be allowed to access the network in TAs using E-UTRA radio access. Valid for Idle and Connected mode;

– E-UTRA not allowed as secondary RAT, the subscriber shall not be allowed to access the network using E-UTRA radio access as secondary RAT. Valid for Connected mode;

– E-UTRA in unlicensed bands not allowed as secondary RAT, the subscriber shall not be allowed to access the network using E-UTRA radio access in unlicensed bands as secondary RAT. Valid for Connected mode;

– NB-IoT not allowed, the subscriber shall not be allowed to access the network in TAs using NB-IoT radio access. Valid for Idle and Connected mode;

– LTE-M not allowed, the subscriber shall not be allowed to access the network in TAs using LTE-M radio access. Valid for Idle and Connected mode;

– NR(LEO) satellite access not allowed as primary RAT, the subscriber shall not be allowed to access the network in TAs using NR(LEO) satellite access. Valid for Idle and Connected mode;

– NR(MEO) satellite access not allowed as primary RAT, the subscriber shall not be allowed to access the network in TAs using NR(MEO) satellite access. Valid for Idle and Connected mode;

– NR(GEO) satellite access not allowed as primary RAT, the subscriber shall not be allowed to access the network in TAs using NR(GEO) satellite access. Valid for Idle and Connected mode;

– NR(OTHERSAT) satellite access not allowed as primary RAT, the subscriber shall not be allowed to access the network in TAs using NR(OTHERSAT) satellite access. Valid for Idle and Connected mode;

– NR RedCap not allowed as primary RAT, the subscriber shall not be allowed to access the network in TAs using NR radio access with reduced radio capability. Valid for Idle and Connected mode.

Only the access restriction for WB-E-UTRA and NB-IoT may include a different value per PLMN.

The use of this parameter for TA update procedures is described in 3GPP TS 23.501 [112].

2.25.48 IAB-Operation Allowed indication

The IAB-Operation Allowed indication defines if the subscriber is allowed for IAB node operation as specified in 3GPP TS 23.501 [112].

The IAB-Operation Allowed indication is permanent subscriber data and is conditionally stored in the UDM and the AMF.

2.25.49 UE radio capability ID

The UE radio capability ID is defined in 3GPP TS 23.003 [5]. Its usage is described in 3GPP TS 23.501 [112].

The UE radio capability ID is temporary subscriber data and is conditionally stored in the AMF.

2.25.50 RG Level Wireline Access Characteristics

RG Level Wireline Access Characteristics (see 3GPP TS 23.316 [120]) are permanent data conditionally stored in UDM and AMF.

2.25.51 RG-TMBR

RG-TMBR (see 3GPP TS 23.316 [120]) are permanent data conditionally stored in UDM and AMF.

2.25.52 List of 5GS Broadcast Location Assistance Data Types

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 NG-RAN using ciphering. For a detailed definition of this data, refer to 3GPP TS 23.273 [121].

The list of 5GS Broadcast Location Assistance Data Types is permanent subscriber data and is conditionally stored in the UDM and the AMF.