hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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]. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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]. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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). |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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]. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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.
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.
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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.5 Data related to basic services | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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]. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.7 Mobile station status data | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.7.9 Data related to UE reachability procedures | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.8 Data related to Operator Determined Barring | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.8.2 Operator Determined Barring general data | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.9 Data related to handover | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.10 Data related to short message support | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.11 Data related to subscriber trace | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.12 Data related to the support of voice group and broadcast calls | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.13.17 DRX Parameters | DRX Parameters is defined in 3GPP TS 23.060 [21].
DRX Parameters is temporary subscriber data stored in SGSN. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.