hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.23 Data related to Cellular IoT Control Plane Optimizations | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.23.2 Void | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.24 Data related to ERP | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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). |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.25 Data related to the support of 5GS | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.25.6 5G QoS Parameters | 5G QoS Parameters (see 3GPP TS 23.501 [112]) are permanent data conditionally stored in UDM and SMF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.25.23 5G GUTI | The 5G GUTI (see 3GPP TS 23.003 [5]) is temporary data conditionally stored in AMF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.25.35 AuthenticationMethod | The AuthenticationMethod is described in 3GPP TS 33.501 [116].
The AuthenticationMethod is permanent data mandatory stored at the UDM. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.25.37 SequenceNumber | The SequenceNumber is described in 3GPP TS 33.102 [52].
The SequenceNumber is temporary data conditionaly stored at the UDM. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.25.38 AuthenticationManagementField | The AuthenticationManagementField is described in 3GPP TS 33.501 [116].
The AuthenticationManagementField is permanent data conditionaly stored at the UDM. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.25.40 Milenage | The Milenage described in 3GPP TS 35.206 [117].
The Milenage is permanent data conditionaly stored at the UDM. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.25.41 Tuak | The Tuak described in 3GPP TS 35.231 [118].
The Tuak is permanent data conditionaly stored at the UDM. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.25.42 Opc | The Opc described in 3GPP TS 35.205 [117].
The Opc is permanent data conditionaly stored at the UDM. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.25.43 Topc | The Topc described in 3GPP TS 35.231 [118].
The Topc is permanent data conditionaly stored at the UDM. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.25.45 SoR-XMAC-IUE | The SoR-XMAC-IUE of the UE contains the expected SoR-XMAC-IUE as specified in 3GPP TS 33.501 [116].
The SoR-XMAC-IUE is temporary data conditionaly stored at the UDM. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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 (RedCap). Valid for Idle and Connected mode.
- NR eRedCap not allowed as primary RAT, the subscriber shall not be allowed to access the network in TAs using NR radio access with enhanced reduced radio capability (eRedCap). 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]. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.25.51 RG-TMBR | RG-TMBR (see 3GPP TS 23.316 [120]) are permanent data conditionally stored in UDM and AMF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3 Definition of data for IP Multimedia domain | This clause describes the IMS data for IMS subscribers and PSI users. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.1 Data related to subscription, identification and numbering | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.1.1 Private User Identity | The Private User Identity is applicable to IMS subscribers only. The Private User Identity is in the form of a Network Access Identifier (NAI), which is defined in IETF RFC 4282 [48].
If the GAA bootstrapping is based on authentication data from the IM domain, the corresponding Private User Identity from the IM d omain (IMPI) is used as it is. If the GAA bootstrapping is based on the authentication data from the CS/PS domain, a Private User Identity is derived from user's IMSI according 3GPP TS 23.003 [5] is used.
The Private User Identity is permanent subscriber data and is stored in HSS and in S-CSCF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.1.2 Public User Identities | The Public User Identities of an IMS subscriber contain one or several instances of Public User Identity or Wildcarded Public User Identity, which are defined in 3GPP TS 23.003 [5].
The Public User Identities are permanent subscriber data and are stored in HSS, S-CSCF and BSF.
3.1.2A Private Service Identity
The Private Service Identity is applicable to a PSI user and is similar to a private user identity in the form of a Network Access Identifier (NAI), which is defined in IETF RFC 4282 [48]. The Private Service Identity is operator defined.
The Private Service Identity is permanent data and is stored in HSS and S-CSCF.
3.1.2B Public Service Identity
The Public Service Identity hosted by an application server may match either to a distinct PSI or a wilcarded PSI that is stored in the HSS. The PSI is defined in 3GPP TS 23.003 [5].
The relationship between Wildcarded Public Service Identities and Private Service Identities is one-to-one.
A Public Service Identity (distinct PSI or Wildcarded PSI) cannot be shared by more than one Private Service Identity.
The Public Service Identity is permanent data and is stored in HSS and S-CSCF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.1.3 Barring indication | Flag associated to each Public User Identity to indicate that the identity is barred from any IMS communication. A Public User Identity that is barred is allowed to register with the IMS.
The Barring indication is permanent subscriber data and is stored in the HSS and in the S-CSCF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.1.4 List of authorized visited network identifiers | The list of authorized visited network identifiers is associated with the Public User Identity to indicate which visited network identifiers are allowed for roaming. If the Public User Identity is part of a set of implicitly registered Public User Identities, the list of authorized visited network identifiers shall be the same for the whole set.
The list of authorized visited network identifiers is permanent subscriber data and is stored in the HSS. This list can be a linear list of visited network identifiers or a compound list of network identifier types e.g. home PLMN or home country; however the exact structure of the list is an implementation option. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.1.5 Services related to Unregistered State | The Services related to Unregistered State is a parameter associated to each Public User Identity and Public Service Identity and it indicates whether the identity has services related to unregistered state or not. For a Public Service Identity the parameter shall always be set to value indicating that the identity has services related to unregistered state.
The Services related to Unregistered State is permanent subscriber data stored in the HSS. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.1.6 Implicitly Registered Public User Identity Sets | The Implicitly Registered Public User Identity Set contains one or several instances of Public User Identity of an IMS subscriber, and is defined in 3GPP TS 29.228 [43] following the described concept in 3GPP TS 23.228 [42]. Several Implicitly Registered Public User Identity Sets can be configured for a given user. Each Public User Identity shall be included in no more than one Implicitly Registered Public User Identity Set.
The Implicitly Registered Public User Identity Sets are permanent subscriber data and are conditionally stored in HSS and in S-CSCF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.1.7 Default Public User Identity indicator | The Default Public User Identity indicator marks the Public User Identity to be used as default Public User Identity in each Implicitly Registered Public User Identity Set, and is defined in 3GPP TS 29.228 [43]. There shall be one Default Public User Identity per Implicitly Registered Public User Identity Set.
The Default Public User Identity indicator is permanent subscriber data and is conditionally stored in the HSS. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.1.8 PSI Activation State | The PSI Activation State is specific for Public Service Identities and is defined in 3GPP TS 29.328 [54].
The PSI Activation State indicator for distinct PSIs is temporary subscriber data and is stored in the HSS. The PSI Activation State indicator for wildcarded PSIs is permanent subscriber data and is stored in the HSS. A wildcarded PSI or a distinct PSI that matches a wildcarded PSI shall not be activated/deactivated via the Sh interface. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.1.9 Display Name | The Display Name is a string associated with a Public Identity
The Display Name is permanent subscriber data and is conditionally stored in the HSS and in the S-CSCF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.1.10 Alias Public User Identity Sets | The Alias Public User Identity Set contains two or more Public User Identities of an IMS subscriber, and these Public User Identities in the set are aliases of each other and their treatment is identical. Several Alias Public User Identity Sets can be configured for a given user. Each Public User Identity shall be included in no more than one Alias Public User Identity Set. All the Public User Identities in every Alias Public User Identity Set shall be included in the same Implicitly Registered Public User Identity Set, and shall be linked to the same Service Profile and share the same service data for each and every service, but there can be more than one Alias Public User Identity Set per Implicitly Registered Public User Identity Set and Service Profile.
The Alias Public User Identity Sets are permanent subscriber data and are conditionally stored in the HSS and in the S-CSCF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.1.11 Loose-Route Indication | The Loose-Route Indication indicates if the loose-route mechanism is required for all the Public User Identities belonging to a Private User Identity. It is defined in 3GPP TS 29.228 [43] following the described concept in 3GPP TS 24.229 [68].
The Loose-Route Indication shall have the same value for all the Private Identities of the IMS subscription if at least one Public User Identity is shared by the multiple Private Identities; otherwise, each Private User Identity may have a different Loose-Route Indication value.
The Loose-Route Indication is permanent subscriber data and is conditionally stored in the HSS and in the S-CSCF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.1.12 Service Priority Level | The Service Priority Level indicates the Priority Level allowed for the Public Identity. It is defined in 3GPP TS 29.228 [43] following the described concept in 3GPP TS 24.229 [68].
The Service Priority Level is permanent subscriber data and is conditionally stored in the HSS and the S-CSCF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.1.13 Extended Priority | The Extended Priority provides priority information for the Public Identity. It provides support for more than one subscribed namespaces in an operator's network, as included in priority mechanisms described in 3GPP TS 24.229 [68] and it is defined in 3GPP TS 29.228 [43].
The Extended Priority is permanent subscriber data and is conditionally stored in the HSS and the S-CSCF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.1.14 Reference Location Information | The Reference Location Information contains the reference location for the Private User Identity (e.g. line identification in the case of fixed line access). It is defined in 3GPP TS 29.228 [43] following the described concept in 3GPP TS 23.167 [89].
The Reference Location Information is permanent subscriber data and is conditionally stored in the HSS and the S-CSCF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.1.15 Priviledged-Sender Indication | The Priviledged-Sender Indication indicates if the corresponding Private User Identity shall be considered a priviledged sender. It is defined in 3GPP TS 29.228 [43] following the described concept in 3GPP TS 24.229 [68].
If for an IMS subscription at least one Public User Identity is shared by more than one Private Identity, then all these Private Identities shall have the same value for the Priviledged-Sender Indication; otherwise, each Private User Identity may have a different Priviledged-Sender Indication value.
The Priviledged-Sender Indication is permanent subscriber data and is conditionally stored in the HSS and in the S-CSCF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.1.16 Additional MSISDN (A-MSISDN) | An Additional MSISDN (A-MSISDN) is an MSISDN optionally assigned in addition to the already assigned MSISDN(s) to a user with PS subscription. For the definition of A-MSISDN see 3GPP TS 23.003 [5].
It is a permanent subscriber data stored in the HSS/HLR. It is temporarily stored in the MME, SGSN and AS. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.2 Data related to registration | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.2.1 Registration Status | The Registration Status, specified in 3GPP TS 29.228 [43], contains the status of registration of a Public User Identity or a Public Service Identity (i.e. registered, not registered, unregistered). A Public Service Identity shall have only the registration status not registered or unregistered.
The Registration Status is temporary subscriber data and is stored in HSS. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.2.2 S-CSCF Name | For an IMS subscriber, the S-CSCF Name identifies the S-CSCF allocated to the IMS subscriber when the subscriber is registered to IP Multimedia Services. It is used during mobile terminated sessions set-up and re-registrations.
For a Public Service Identity the S-CSCF Name identities the S-CSCF allocated to the PSI for basic IMS routing. It is used during terminated call set-up for a PSI user.
The S-CSCF Name shall be in the form of a SIP URL as defined in IETF RFC 3261 [45] and RFC 2396 [46].
For an IMS subscriber and PSI user, the S-CSCF Name is temporary data and is stored in HSS.
3.2.2A AS Name
For a PSI user the AS Name identifies the application server hosting the Public Service Identity and is used for direct routing of a Public Service Identity.
The AS Name shall be in the form of a SIP URL as defined in IETF RFC 3261 [45] and RFC 2396 [46].
The AS Name is permanent data and is stored in the HSS. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 3.2.3 Diameter Client Identity of S-CSCF | The Diameter Client Identity of the S-CSCF identifies the Diameter client in the S-CSCF when the IMS subscriber is registered to IP Multimedia Services or a PSI user has an assigned S-CSCF. It is used in requests sent by the HSS to the S-CSCF. The format of the Diameter Client Identity is the Diameter Identity defined in IETF RFC 3588 [51].
The Diameter Client Identity of the S-CSCF is temporary data and is stored in HSS. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.