hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.7.1 General | A 5GS supports Network Slicing and might need to interwork with the EPS in its PLMN or in other PLMNs as specified in clause 5.17.2. The EPC may support the Dedicated Core Networks (DCN). In some deployments, the MME selection may be assisted by a DCN-ID provided by the UE to the RAN (see TS 23.401 [26]).
Mobility betw... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.7.2 Idle mode aspects | In addition to the interworking principles documented in clause 5.17.2 the following applies for interworking with N26:
- When UE moves from 5GS to EPS, the UE context information sent by AMF to MME includes the UE Usage type, which is retrieved from UDM by AMF as part of subscription data.
- When UE moves from EPS to ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.7.3 Connected mode aspects | In addition to the interworking principles documented in clause 5.17.2 the following applies for interworking with N26:
- When a UE is CM-CONNECTED in 5GC and a handover to EPS occur, the AMF selects the target MME based on the source AMF Region ID, AMF Set ID and target location information. The AMF forwards the UE co... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.7.4 Support of Network Slice usage control and Interworking with EPC | As described in clause 5.15.15, if Network Slice usage control is required for a PDN Connection, the SMF+PGW-C configures PDU Session inactivity timer to the UPF+PGW-U. When the SMF+PGW-C receives inactivity report of the PDN Connection from the UPF+PGW-U, the SMF+PGW-C releases the PDN Connection. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.8 Configuration of Network Slice support and availability in a PLMN | A Network Slice may be supported in the whole PLMN or in one or more Tracking Areas of the PLMN. A Network Slice is supported within a TA if the 5G-AN has been configured to support the S-NSSAI in the TA.
Network Slices are defined to be available within an NS-AoS when the Network Slice is supported in the set of TAs w... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.9 Operator-controlled inclusion of NSSAI in Access Stratum Connection Establishment | The Serving PLMN can control per Access Type which (if any) NSSAI the UE includes in the Access Stratum when establishing a connection caused by Service Request, Periodic Registration Update or Registration procedure used to update the UE capabilities. In addition, the Home and Visited PLMNs can also instruct the UE to... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.10 Network Slice-Specific Authentication and Authorization | A serving PLMN or SNPN shall perform Network Slice-Specific Authentication and Authorization for the S-NSSAIs of the HPLMN or SNPN which are subject to it based on subscription information. The UE shall indicate in the Registration Request message in the UE 5GMM Core Network Capability whether it supports NSSAA feature... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.11 Network Slice Admission Control | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.11.0 General | The Network Slice Admission Control Function (NSACF) monitors and controls the number of registered UEs per network slice and/or the number of PDU Sessions per network slice for the network slices that are subject to Network Slice Admission Control (NSAC). The NSACF is configured with the maximum number of UEs and/or t... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.11.1 Network Slice Admission Control for maximum number of UEs | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.11.1.1 Non-Hierarchical NSAC architecture | The NSACF keeps track of the current number of UEs registered for a network slice so that it can ensure it does not exceed the maximum number of UEs allowed to register with the network slice. The NSACF also maintains a list of UE IDs registered with a network slice that is subject to NSAC. When an event related to a U... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.11.1.2 Hierarchical NSAC architecture | In the Hierarchical NSAC architecture, the NSACFs deployed in the NSAC service areas interacts with the Primary NSACF when needed and as explained below.
The main differences between the non-Hierarchical architecture and the Hierarchical architecture is that the AMFs and the NSACFs deployed in the Hierarchical architec... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.11.1.3 Centralized NSAC architecture | The main differences between the NSACFs deployed in a non-Hierarchical architecture and NSACFs deployed in a Centralized NSAC architecture is as follows:
- If multiple NSAC service areas are deployed in PLMN, the AMF provides the NSAC Service Area Identifier information to the centralized NSACF. The centralized NSACF a... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.11.2 Network Slice Admission Control for maximum number of PDU sessions | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.11.2.1 Non- Hierarchical NSAC architecture | The NSACF keeps track of the current number of PDU Sessions per network slice so that it can ensure it does not exceed the maximum number of PDU session allowed to be served by the network slice. When an event related to a UE causes the current number of PDU sessions established within the network slice is to increase,... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.11.2.2 Hierarchical NSAC architecture | The main differences between the NSACFs deployed in a non-Hierarchical architecture and NSACFs deployed in a Hierarchical architecture is as follows:
- The NSCAF is enhanced to support PDU session admission quota-based control.
- When the local maximum number of PDU sessions is reached, the NSACF interacts with the Pri... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.11.2.3 Centralized NSAC architecture | The main differences between the NSACFs deployed in a non-Hierarchical NSAC architecture and NSACFs deployed in a Centralized NSAC architecture is as follows
- If multiple NSAC service areas are deployed in a PLMN, the SMF provides the NSAC Service Area Identifier to the centralized NSACF. The centralized NSACF also st... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.11.3 Network Slice Admission Control for Roaming | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.11.3.0 General | In the case of roaming, depending on operator's policy, a roaming agreement or an SLA between the VPLMN and the HPLMN, NSAC of roaming UEs is performed by one of the following modes of NSAC admission:
- VPLMN NSAC Admission; or
- VPLMN with HPLMN assistance NSAC Admission; or
- HPLMN NSAC Admission.
The VPLMN (AMF and ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.11.3.1 VPLMN NSAC Admission Mode | For NSAC of roaming UEs for maximum number of UEs per network slice and/or maximum number of PDU Sessions per network slice managed by the VPLMN, the following principles shall be used:
- For NSAC for the maximum number of UEs for S-NSSAI of the HPLMN, a NSACF in the VPLMN can be configured with the maximum number of a... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.11.3.2 VPLMN with HPLMN assistance NSAC Admission | In this admission mode HPLMN delegates NSAC for S-NSSAIs subject to NSAC to the VPLMN, both for number of registered UEs and the number of LBO PDU sessions.
Every NSACF performing admission in the VPLMN for each S-NSSAI of the HPLMN that is subject to NSAC and mapped to a corresponding S-NSSAI of the VPLMN, fetches fro... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.11.3.3 HPLMN NSAC Admission Mode | In this admission mode the AMF or SMF in VPLMN interacts with HPLMN for admission, both for number of registered UEs or the number of LBO PDU sessions respectively.
For each S-NSSAI of the HPLMN that is subject to NSAC and mapped to a corresponding S-NSSAI of the VPLMN, AMF performs NSAC admission for the number of reg... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.11.4 Network Slice status notifications and reports to a consumer NF | A consumer NF (e.g. AF, Primary NSACF) can subscribe with the NSACF for Network Slice status notifications and reports. Upon such subscription, the corresponding NSACF in different NSAC architecture as defined in clause 5.15.11.0 can provide event based notifications and reports to the consumer NF (e.g. to AF via NEF) ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.11.5 Support of Network Slice Admission Control and Interworking with EPC | This clause describes the NSAC for maximum number of registered UEs and for maximum number of PDU Sessions for network slice subjected to EPS interworking. The NSAC for maximum number of UE with at least one PDU Session/PDN Connection is described in clause 5.15.11.5a. A network slice subject to both NSAC and EPS count... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.12 Support of subscription-based restrictions to simultaneous registration of network slices | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.12.1 General | The subscription information for a UE may include for each S-NSSAI Network Slice Simultaneous Registration Group (NSSRG) information constraining which S-NSSAIs can be simultaneously provided to the UE in the Allowed NSSAI.
When S-NSSAIs have associated NSSRG information, then the S-NSSAIs in the Allowed NSSAI shall sh... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.12.2 UE and UE configuration aspects | A UE may support the subscription-based restrictions to simultaneous registration of network slices feature. In this case, the UE indicates its support in the Registration Request message in the Initial Registration and the Mobility Registration Update as part of the UE 5GMM Core Network Capability.
When the serving AM... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.13 Support of data rate limitation per Network Slice for a UE | A UE subscription information may include an optional Slice Maximum Bit Rate for the UE (Subscribed UE-Slice-MBR) for an S-NSSAI, which applies for 3GPP access type only. The Subscribed UE-Slice-MBR includes a UL and a DL value. If a Subscribed UE-Slice-MBR is associated to an S-NSSAI in the subscription information, i... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.14 Network Slice AS Groups support | The NG-RAN may support Network Slice AS Groups (NSAGs) which are used as specified in TS 38.300 [27], TS 38.331 [28], TS 38.321 [143] and TS 38.304 [50]. A Network Slice AS Group is an identifier of a group of network slices which are associated with it. A Network Slice AS Group association with a group of network slic... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.15 Support of Network Slice usage control | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.15.1 General | Network Slice usage control is achieved as follows:
1) Configuring network-controlled Slice Usage Policy to supporting UEs (see clause 5.15.15.2).
2) Configuring PDU Sessions inactivity timers and Network Slice deregistration inactivity timers (see clause 5.15.15.3).
NOTE: The use of Network Slice Usage Control while r... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.15.2 UE Configuration of network-controlled Slice Usage Policy | The UE during the Registration procedure may indicate in UE MM Core Network Capability that it supports UE configuration of network-controlled Slice Usage Policy. If so, the AMF determines Slice Usage Policy for one (or more) Network Slice(s) for the UE and configures the UE with this information together with Configur... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.15.3 Network-based per UE Network Slice usage behaviour control | The 5GC performs Network Slice usage monitoring to be able to enforce the release of inactive PDU Sessions and deregistering of UEs from Network Slices with no PDU Sessions on them according to its own policies. In order to support usage monitoring for a Network Slice:
- The AMF runs a slice deregistration inactivity t... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.16 Optimized handling of temporarily available network slices | A network slice may be available for all UEs or a limited number of UEs only for a limited time that is known at the network in advance e.g. by OAM or subscription. The limited time duration may be due to, for example, the fact that network slice is only temporarily or periodically active in the deployment (e.g. for a ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.17 Partial Network Slice support in a Registration Area | A Network Slice may be supported in one or more TAs in a PLMN/SNPN. The Partial Network Slice support in a Registration Area for a UE includes configuring the UE with a Partially Allowed NSSAI and/or S-NSSAI(s) rejected partially in the RA.
When creating a Registration Area for UEs registering over the 3GPP access and ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.18 Support for Network Slices with Network Slice Area of Service not matching deployed Tracking Areas | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.18.1 General | The network support for a Network Slice is defined on a per Tracking Area granularity. It may be beneficial to deploy some Network Slices such that the Network Slice have a limited geographical availability that is not matching existing Tracking Area boundaries.
The operator can in this case decide to change the topolo... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.18.2 S-NSSAI location availability information | S-NSSAI location availability information defines additional restrictions to the usage of an S-NSSAI in TAs where the Network Slice availability does not match the TA boundaries. The AMF is configured per S-NSSAI whether to send the S-NSSAI location availability information to supporting UEs.
The S-NSSAI location avail... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.18.3 Network based monitoring and enforcement of Network Slice Area of Service not matching deployed Tracking Areas | OAM may configure RRM policies for S-NSSAIs on a per cell basis as defined in TS 28.541 [149], i.e. cells outside the Network Slice Area of Service while in a TA supporting the S-NSSAI are allocated with no RRM resources for the S-NSSAI.
The network may enforce the NS-AoS for an S-NSSAI as follows:
1. The network may m... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.19 Support of Network Slice Replacement | The Network Slice Replacement feature is used to temporarily replace an S-NSSAI with an Alternative S-NSSAI when an S-NSSAI becomes unavailable or congested in the 5GC. The Network Slice Replacement may be triggered in the following cases:
- If the NSSF detects that an S-NSSAI becomes unavailable or congested (e.g. bas... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.15.20 Support of Network Slice Instance Replacement | The Network Slice Instance Replacement is used when a PDU Session for a given S-NSSAI is established using a selected Network Slice instance and the S-NSSAI corresponding to this Network Slice instance is associated with multiple Network Slice instances. In this case, the network may change the Network Slice instance f... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.16 Support for specific services | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.16.1 Public Warning System | The functional description for supporting Public Warning System for 5G System can be found in TS 23.041 [46]. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.16.2 SMS over NAS | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.16.2.1 General | This clause includes feature description for supporting SMS over NAS in 5G System. Support for SMS incurs the following functionality:
- Support for SMS over NAS transport between UE and AMF. This applies to both 3GPP and Non 3GPP accesses.
- Support for AMF determining the SMSF for a given UE.
- Support for subscripti... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.16.2.2 SMS over NAS transport | 5G System supports SMS over NAS via both 3GPP access and non-3GPP access.
During Registration procedure, a UE that wants to use SMS provides an "SMS supported" indication over NAS signalling indicating the UE's capability for SMS over NAS transport. "SMS supported" indication indicates whether UE can support SMS delive... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.16.3 IMS support | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.16.3.1 General | IP-Connectivity Access Network specific concepts when using 5GS to access IMS can be found in TS 23.228 [15].
5GS supports IMS with the following functionality:
- Indication toward the UE if IMS voice over PS session is supported.
- Capability to transport the P-CSCF address(es) to UE.
- Paging Policy Differentiation f... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.16.3.2 IMS voice over PS Session Supported Indication over 3GPP access | The serving PLMN AMF shall send an indication toward the UE during the Registration procedure over 3GPP access to indicate if an IMS voice over PS session is supported or not supported in 3GPP access and non-3GPP access. A UE with "IMS voice over PS" voice capability over 3GPP access should take this indication into ac... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.16.3.3 Homogeneous support for IMS voice over PS Session supported indication | 5GC shall support the usage of "Homogeneous Support of IMS Voice over PS Sessions" indication between AMF and UDM.
When the AMF initiates Nudm_UECM_Registration operation to the UDM, it shall:
- if "IMS Voice over PS Sessions" is supported homogeneously in all TAs in the serving AMF for the UE, include the "Homogeneous... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.16.3.4 P-CSCF address delivery | At PDU Session Establishment procedure related to IMS, SMF shall support the capability to send the P-CSCF address(es) to UE. The SMF is located in VPLMN if LBO is used. This is sent by visited SMF if LBO is used. For Home routed, this information is sent by the SMF in HPLMN. P-CSCF address(es) shall be sent transparen... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.16.3.5 Domain selection for UE originating sessions / calls | For UE originating calls, the 5GC capable UE performs access domain selection. The UE shall be able to take following factors into account for access domain selection decision:
- The state of the UE in the IMS. The state information shall include: Registered, Unregistered.
- The "IMS voice over PS session supported ind... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.16.3.6 Terminating domain selection for IMS voice | When requested by IMS, the UDM/HSS shall be able to query the serving AMF for T-ADS related information. T-ADS is a functionality located in the IMS and is performed as specified in TS 23.221 [23].
The AMF shall respond to the query with the following information unless the UE is detached:
- whether or not IMS voice ov... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.16.3.7 UE's usage setting | If the UE is configured to support IMS voice, the UE shall include the information element "UE's usage setting" in Registration Request messages. The UE's usage setting indicates whether the UE behaves in a "voice centric" or "data centric" way (as defined in clause 5.16.3.5).
A UE supporting IMS voice over 3GPP access... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.16.3.8 Domain and Access Selection for UE originating SMS | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.16.3.8.1 UE originating SMS for IMS Capable UEs supporting SMS over IP | To allow for appropriate domain selection for SMS delivery, it should be possible to provision UEs with the following HPLMN operator preferences on how an IMS enabled UE is supposed to handle SMS services:
- SMS is not to be invoked over IP networks: the UE does not attempt to deliver SMS over IP networks. The UE attem... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.16.3.8.2 Access Selection for SMS over NAS | It should be possible to provision UEs with the HPLMN SMS over NAS operator preferences on access selection for delivering SMS over NAS signalling.
Based on the SMS over NAS preference:
- SMS is preferred to be invoked over 3GPP access for NAS transport: the UE attempts to deliver MO SMS over NAS via 3GPP access if the... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.16.3.9 SMF support for P-CSCF restoration procedure | For the support of P-CSCF restoration the SMF behaves as described in TS 23.380 [61]. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.16.3.10 IMS Voice Service via EPS Fallback or RAT fallback in 5GS | In order to support various deployment scenarios for obtaining IMS voice service, the UE and NG-RAN may support the mechanism to direct or redirect the UE from NG-RAN either towards E-UTRA connected to 5GC (RAT fallback) or towards EPS (E-UTRAN connected to EPC System fallback).
Following principles apply for IMS Voice... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.16.3.11 P-CSCF discovery and selection | P-CSCF selection functionality may be used by the SMF to select the P-CSCF for an IMS PDU Session of the UE.
The SMF can utilize the Network Repository Function to discover the P-CSCF instance(s). The NRF provides the IP address or the FQDN of P-CSCF instance(s) to the SMF. The P-CSCF selection function in the SMF sele... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.16.3.12 HSS discovery and selection | HSS discovery and selection functionality is used by the I-CSCF/S-CSCF/IMS-AS to select an HSS that manages the user's IMS subscriptions and has the ability to serve the IMS services for the UE, see clause AA.3.3 of TS 23.228 [15] and clause 6.3.1 for details. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.16.4 Emergency Services | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.16.4.1 Introduction | Emergency Services are provided to support IMS emergency sessions. "Emergency Services" refers to functionalities provided by the serving network when the network is configured to support Emergency Services. Emergency Services are provided to normally registered UEs and to Emergency Registered UEs, that can be either n... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.16.4.2 Architecture Reference Model for Emergency Services | According to clause 4.2, the non-roaming architectures (Figure 4.2.3-1 and Figure 4.2.3-2) and roaming architecture with the visited operator's application function (Figure 4.2.4-1 and Figure 4.2.4-4) apply for Emergency Services. The other non-roaming and roaming architectures with services provided by the home networ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.16.4.3 Mobility Restrictions and Access Restrictions for Emergency Services | When Emergency Services are supported and local regulation requires IMS Emergency Sessions to be provided regardless of Mobility Restrictions or Access Restrictions, the Mobility Restrictions or Access Restrictions (see clause 5.3.4.1) should not be applied to UEs receiving Emergency Services. Additionally, due to Mobi... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.16.4.4 Reachability Management | Over 3GPP access, an Emergency Registered UE when its Periodic Registration Update timer expires shall not initiate a Periodic Registration Update procedure but shall enter the RM-DEREGISTERED state. For such UEs, the AMF runs a mobile reachable timer with a similar value to the UE's Periodic Registration Update timer.... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.16.4.5 SMF and UPF selection function for Emergency Services | When a SMF is selected for Emergency Services, the SMF selection function described in clause 6.3.2 for normal services is applied to the Emergency DNN or the AMF selects the SMF directly from the AMF Emergency Configuration Data. If the SMF selection function described in clause 6.3.2 is used it shall always derive a ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.16.4.6 QoS for Emergency Services | Local regulation may require supporting emergency calls from an unauthorised UE. In such a case, the SMF may not have subscription data. Additionally, the local network may want to provide Emergency Services support differently than what is allowed by a UE subscription. Therefore, the initial QoS parameters used for es... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.16.4.7 PCC for Emergency Services | Dynamic PCC is used for UEs establishing emergency service and shall be used to manage IMS emergency sessions when an operator allows IMS emergency sessions. When establishing Emergency Services with a SMF, the PCF provides the SMF with the QoS parameters, including an ARP value reserved for the Emergency Services to p... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.16.4.8 IP Address Allocation | Emergency service is provided by the serving PLMN or SNPN. The UE and serving PLMN or SNPN must have compatible IP address versions in order for the UE to obtain a local emergency PDU Session. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.16.4.9 Handling of PDU Sessions for Emergency Services | The QoS Flows of a PDU Session associated with the emergency DNN shall be dedicated for IMS emergency sessions and shall not allow any other type of traffic. The emergency contexts shall not be changed to non-emergency contexts and vice versa. The UPF shall block any traffic that is not from or to addresses of network ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.16.4.10 Support of eCall Only Mode | For service requirements for eCall only mode, refer to TS 22.101 [33].
A UE configured for eCall Only Mode shall remain in RM-DEREGISTERED state, shall camp on a network cell when available but shall refrain from any Registration Management, Connection Management or other signalling with the network. The UE may instiga... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.16.4.11 Emergency Services Fallback | In order to support various deployment scenarios for obtaining Emergency Services, the UE and 5GC may support the mechanism to direct or redirect the UE either towards E-UTRA connected to 5GC (RAT fallback) when only NR does not support Emergency Services or towards EPS (E-UTRAN connected to EPC System fallback) when t... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.16.5 Multimedia Priority Services | TS 22.153 [24] specifies the service requirements for Multimedia Priority Service (MPS). MPS allows Service Users (as per TS 22.153 [24]) priority access to system resources in situations such as during congestion, creating the ability to deliver or complete sessions of a high priority nature. Service Users are governm... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.16.6 Mission Critical Services | According to TS 22.280 [37], a Mission Critical Service (MCX Service) is a communication service reflecting enabling capabilities Mission Critical Applications and provided to end users from Mission Critical Organizations and mission critical applications for other businesses and organizations (e.g. utilities, railways... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.17 Interworking and Migration | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.17.1 Support for Migration from EPC to 5GC | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.17.1.1 General | Clause 5.17.1 describes the UE and network behaviour for the migration from EPC to 5GC.
Deployments based on different 3GPP architecture options (i.e. EPC based or 5GC based) and UEs with different capabilities (EPC NAS and 5GC NAS) may coexist at the same time within one PLMN.
It is assumed that a UE that is capable o... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.17.1.2 User Plane management to support interworking with EPS | In order to support the interworking with EPC, the SMF+PGW-C provides information over N4 to the UPF+PGW-U related to the handling of traffic over S5-U. Functionality defined in TS 23.503 [45] for traffic steering control on SGi-LAN/N6 can be activated in UPF+PGW-U under consideration of whether the UE is connected to ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.17.1.3 QoS handling for home routed roaming | During mobility from EPS to 5GS, the handling of QoS constraints in V-SMF is specified in clauses 4.11.1.2.2 and 4.11.1.3.3 of TS 23.502 [3] and follows the same principle as described in clause 5.7.1.11. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.17.2 Interworking with EPC | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.17.2.1 General | Interworking with EPC in this clause refers to mobility procedures between 5GC and EPC/E-UTRAN, except for clause 5.17.2.4. Network slicing aspects for EPS Interworking are specified in clause 5.15.7
In order to interwork with EPC, the UE that supports both 5GC and EPC NAS can operate in single-registration mode or dua... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.17.2.2 Interworking Procedures with N26 interface | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.17.2.2.1 General | NOTE 1: Additional network slicing and Interworking with EPS with N26 aspects are specified in clause 5.15.7.
Interworking procedures using the N26 interface, enables the exchange of MM and SM states between the source and target network. The N26 interface may be either intra-PLMN or inter-PLMN (e.g. to enable inter-PL... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.17.2.2.2 Mobility for UEs in single-registration mode | When the UE supports single-registration mode and network supports interworking procedure with the N26 interface:
- For idle mode mobility from 5GS to EPS, the UE performs either TAU or Attach procedure with EPS GUTI mapped from 5G-GUTI sent as old Native GUTI, as described in clause 4.11.1.3.2.1 of TS 23.502 [3] and i... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.17.2.3 Interworking Procedures without N26 interface | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.17.2.3.1 General | For interworking without the N26 interface, IP address preservation is provided to the UEs on inter-system mobility by storing and fetching SMF+PGW-C and corresponding APN/DNN information via the HSS+UDM. In such networks AMF also provides an indication that interworking without N26 is supported to UEs during Initial R... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.17.2.3.2 Mobility for UEs in single-registration mode | When the UE supports single-registration mode and network supports interworking procedure without N26 interface:
- For mobility from 5GC to EPC, the UE with at least one PDU Session established in 5GC may either:
- if supported and if it has received the network indication that interworking without N26 is supported, pe... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.17.2.3.3 Mobility for UEs in dual-registration mode | To support mobility in dual-registration mode, the support of N26 interface between AMF in 5GC and MME in EPC is not required. A UE that supports dual registration mode may operate in this mode when it receives an indication from the network that interworking without N26 is supported.
For UE operating in dual-registrat... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.17.2.3.4 Redirection for UEs in connected state | When the UE supports single-registration mode or dual-registration mode without N26 interface:
- If the UE is in CM-CONNECTED state in 5GC, the NG-RAN may perform RRC Connection Release with Redirection to E-UTRAN based on certain criteria (e.g. based on local configuration in NG-RAN, or triggered by the AMF upon recei... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.17.2.4 Mobility between 5GS and GERAN/UTRAN | IP address preservation upon direct mobility between 5GS and GERAN/UTRAN is not supported.
Upon mobility from 5GS to GERAN/UTRAN (e.g. upon leaving NG-RAN coverage) the UE shall perform the A/Gb mode GPRS Attach procedure or Iu mode GPRS Attach procedure (see TS 23.060 [56]).
As a UE option, to support IP address prese... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.17.2.5 Secondary DN authentication and authorization in EPS Interworking case | Secondary authentication/authorization by a DN-AAA server during the establishment of a PDN connection over 3GPP access to EPC, is supported based on following principles:
- It is optional for the UE to support EAP-based secondary authentication and authorization by DN-AAA over EPC,
- A SMF+PGW-C shall be used to serve... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.17.3 Interworking with EPC in presence of Non-3GPP PDU Sessions | When a UE is simultaneously connected to the 5GC over a 3GPP access and a non-3GPP access, it may have PDU Sessions associated with 3GPP access and PDU Sessions associated with non-3GPP access. When inter-system handover from 5GS to EPS is performed for PDU Sessions associated with 3GPP access, the PDU Sessions associa... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.17.4 Network sharing support and interworking between EPS and 5GS | The detailed description for supporting network sharing and interworking between EPS and 5GS is described in clauses 4.11.1.2.1, 4.11.1.2.2, 4.11.1.3.2 and 4.11.1.3.3 of TS 23.502 [3]. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.17.5 Service Exposure in Interworking Scenarios | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.17.5.1 General | Clause 4.3.5 shows the Service Exposure Network Architecture in scenarios where for EPC-5GC Interworking is required.
In scenarios where interworking between 5GS and EPC is possible, the network configuration is expected to associate UEs with SCEF+NEF node(s) for Service Capability Exposure. The SCEF+NEF hides the unde... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.17.5.2 Support of interworking for Monitoring Events | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.17.5.2.1 Interworking with N26 interface | In addition to the interworking principles documented in clause 5.17.2.2, the following applies for interworking with N26:
- When UE moves from EPS to 5GS, when the AMF registers in UDM, if no event subscription via UDM is available, the AMF indicates the situation to the UDM and in this case the UDM can decide if the ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.17.5.2.2 Interworking without N26 interface | In addition to the interworking principles documented in clause 5.17.2.3, the additional behaviour at EPS to 5GS mobility in clause 5.17.5.2.1 also applies.
When SCEF+NEF performs the procedure of monitoring via the AMF as described in clause 4.15.3.2.4 ("Exposure with bulk subscription") in TS 23.502 [3], if the AMF d... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.17.5.3 Availability or expected level of a service API | A service related with common north-bound API may become unavailable due to UE being served by a CN node not supporting the service. If the availability or expected level of support of a service API associated with a UE changes, for example due to a mobility between 5GC and EPC, the AF shall be made aware of the change... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.