hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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]. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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]. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.16.7 Subscriber Data stored in HSS | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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]. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.17 Data related to Super-Charger | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.18 Data related to bearer service priority | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.19 Data related to charging | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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]). |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.20 Data related to IMS Centralized Service | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.21 Data related to SRVCC | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.21.1 STN-SR | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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]). |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.21.2 UE SRVCC Capability | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.21.2.1 General | This information element indicates the SRVCC capability of the UE and is described in 3GPP TS 23.237 [87]. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.21.2.2 UE SRVCC Capability in EPS | The UE SRVCC Capability is temporary data conditionally stored in the HSS, MME and SGSN. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.21.2.3 UE SRVCC Capability in 5GS | The UE 5G SRVCC Capability is temporary data conditionally stored in the UDM and AMF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.22 Data related to MBMS | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 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. |
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. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.