hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.4.6.1 User plane architecture to support 5G LAN-type service | The general User Plane architectures described in clause 4.2.3 and clause 4.2.4 apply to 5G LAN-type services, with the additional options described in this clause.
Figure 4.4.6.1-1 depicts the non-roaming user plane architecture to support 5G LAN-type service using local switch.
Figure 4.4.6.1-1: Local-switch based us... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.4.6.2 Reference points to support 5G LAN-type service | N19: Reference point between two UPFs for direct routing of traffic between different PDU Sessions without using N6. It has a per 5G VN group granularity. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.4.7 MSISDN-less MO SMS Service | MSISDN-less MO SMS via T4 is subscription based. The subscription provides the information whether a UE is allowed to originate MSISDN-less MO SMS.
The UE is pre-configured with the Service Centre address that points to SMS-SC that performs this MO SMS delivery via NEF delivery procedure. The recipient of this short me... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.4.8 Architecture to enable Time Sensitive Communication, Time Synchronization and Deterministic Networking | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.4.8.1 General | The 5G System can be extended to support the following:
a) Integration of 5GS into a TSN data network (DN): Integration as a bridge in an IEEE 802.1 Time Sensitive Networking (TSN). The 5GS bridge supports the Time sensitive communication as defined in IEEE 802.1 Time Sensitive Networking (TSN) standards. The architect... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.4.8.2 Architecture to support IEEE Time Sensitive Networking | The 5G System is integrated with the external network as a TSN bridge. This "logical" TSN bridge (see Figure 4.4.8.2-1) includes TSN Translator functionality for interoperation between TSN Systems and 5G System both for user plane and control plane. 5GS TSN translator functionality consists of Device-side TSN translato... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.4.8.3 Architecture for AF requested support of Time Sensitive Communication and Time Synchronization | This clause describes the architecture to enable Time Sensitive Communication AF requested time sensitive communication and time synchronization services. The Time Sensitive Communication and Time Synchronization related features that are supported based on AF request are described in clauses 5.27.1 and 5.27.2, respect... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 4.4.8.4 Architecture to support IETF Deterministic Networking | The 5G System is integrated with the Deterministic Network as defined in IETF RFC 8655 [150] as a logical DetNet transit router, see Figure 4.4.8.4-1. The TSCTSF performs mapping in the control plane between the 5GS internal functions and the DetNet controller. 5G System specific procedures in 5GC and RAN remain hidden... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5 High level features | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.1 General | Clause 5 specifies the high level functionality and features of the 5G System for both 3GPP and Non-3GPP access and for the interoperability with the EPC defined in TS 23.401 [26]. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.2 Network Access Control | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.2.1 General | Network access is the means for the user to connect to 5G CN. Network access control comprises the following functionality:
- Network selection,
- Identification and authentication,
- Authorisation,
- Access control and barring,
- Policy control,
- Lawful Interception. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.2.2 Network selection | In order to determine to which PLMN to attempt registration, the UE performs network selection. The network selection procedure comprises two main parts, PLMN selection and access network selection. The requirements for the PLMN selection are specified in TS 22.011 [25] and the procedures are in TS 23.122 [17]. The acc... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.2.3 Identification and authentication | The network may authenticate the UE during any procedure establishing a NAS signalling connection with the UE. The security architecture is specified in TS 33.501 [29]. The network may optionally perform an PEI check with 5G-EIR. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.2.4 Authorisation | The authorisation for connectivity of the subscriber to the 5GC and the authorization for the services that the user is allowed to access based on subscription (e.g. Operator Determined Barring, Roaming restrictions, Access Type and RAT Type currently in use) is evaluated once the user is successfully identified and au... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.2.5 Access control and barring | When the UE needs to transmit an initial NAS message, the UE shall request to establish or resume an RRC Connection first and the NAS shall provide the RRC establishment or resume related information to the lower layer. The RAN handles the RRC Connection with priority during and after the RRC Connection Establishment p... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.2.6 Policy control | Network access control including service authorization may be influenced by Policy control, as specified in clause 5.14. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.2.7 Lawful Interception | For definition and functionality of Lawful Interception, please see TS 33.126 [35]. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.3 Registration and Connection Management | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.3.1 General | The Registration Management is used to register or deregister a UE/user with the network and establish the user context in the network. The Connection Management is used to establish and release the signalling connection between the UE and the AMF. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.3.2 Registration Management | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.3.2.1 General | A UE/user needs to register with the network to receive services that requires registration. Once registered and if applicable the UE updates its registration with the network (see TS 23.502 [3]):
- periodically, in order to remain reachable (Periodic Registration Update); or
- upon mobility (Mobility Registration Upda... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.3.2.2 5GS Registration Management states | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.3.2.2.1 General | Two RM states are used in the UE and the AMF that reflect the registration status of the UE in the selected PLMN:
- RM-DEREGISTERED.
- RM-REGISTERED. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.3.2.2.2 RM-DEREGISTERED state | In the RM‑DEREGISTERED state, the UE is not registered with the network. The UE context in AMF holds no valid location or routing information for the UE so the UE is not reachable by the AMF. However, some parts of UE context may still be stored in the UE and the AMF e.g. to avoid running an authentication procedure du... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.3.2.2.3 RM-REGISTERED state | In the RM‑REGISTERED state, the UE is registered with the network. In the RM-REGISTERED state, the UE can receive services that require registration with the network.
In the RM-REGISTERED state, the UE shall:
- perform Mobility Registration Update procedure if the current TAI of the serving cell (see TS 37.340 [31]) is... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.3.2.2.4 5GS Registration Management State models | Figure 5.3.2.2.4-1: RM state model in UE
Figure 5.3.2.2.4-2: RM state model in AMF |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.3.2.3 Registration Area management | Registration Area management comprises the functions to allocate and reallocate a Registration area to a UE. Registration area is managed per access type i.e. 3GPP access or Non-3GPP access.
When a UE registers with the network over the 3GPP access, the AMF allocates a set of tracking areas in TAI List to the UE. When ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.3.2.4 Support of a UE registered over both 3GPP and Non-3GPP access | This clause applies to Non-3GPP access network corresponding to the Untrusted Non-3GPP access network, to the Trusted Non-3GPP and to the W-5GAN. In the case of W-5GAN the UE mentioned in this clause corresponds to the 5G-RG.
For a given serving PLMN there is one RM context for a UE for each access, e.g. when the UE is... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.3.3 Connection Management | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.3.3.1 General | Connection management comprises the functions of establishing and releasing a NAS signalling connection between a UE and the AMF over N1. This NAS signalling connection is used to enable NAS signalling exchange between the UE and the core network. It comprises both the AN signalling connection between the UE and the AN... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.3.3.2 5GS Connection Management states | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.3.3.2.1 General | Two CM states are used to reflect the NAS signalling Connection of the UE with the AMF:
- CM-IDLE
- CM-CONNECTED
The CM state for 3GPP access and Non-3GPP access are independent of each other, i.e. one can be in CM-IDLE state at the same time when the other is in CM-CONNECTED state. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.3.3.2.2 CM-IDLE state | A UE in CM-IDLE state has no NAS signalling connection established with the AMF over N1. The UE performs cell selection/cell reselection according to TS 38.304 [50] and PLMN selection according to TS 23.122 [17].
There are no AN signalling connection, N2 connection and N3 connections for the UE in the CM-IDLE state.
If... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.3.3.2.3 CM-CONNECTED state | A UE in CM-CONNECTED state has a NAS signalling connection with the AMF over N1. A NAS signalling connection uses an RRC Connection between the UE and the NG-RAN and an NGAP UE association between the AN and the AMF for 3GPP access. A UE can be in CM-CONNECTED state with an NGAP UE association that is not bound to any ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.3.3.2.4 5GS Connection Management State models | Figure 5.3.3.2.4-1: CM state transition in UE
Figure 5.3.3.2.4-2: CM state transition in AMF
When a UE enters CM-IDLE state, the UP connection of the PDU Sessions that were active on this access are deactivated.
NOTE: The activation of UP connection of PDU Sessions is documented in clause 5.6.8. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.3.3.2.5 CM-CONNECTED with RRC_INACTIVE state | RRC_INACTIVE state applies to NG-RAN. UE support for RRC_INACTIVE state is defined in TS 38.306 [69] for NR and TS 36.306 [70] for E-UTRA connected to 5GC. RRC_INACTIVE is not supported by NB-IoT connected to 5GC.
The AMF shall provide assistance information to the NG-RAN, to assist the NG-RAN's decision whether the UE... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.3.3.3 NAS signalling connection management | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.3.3.3.1 General | NAS signalling connection management includes the functions of establishing and releasing a NAS signalling connection. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.3.3.3.2 NAS signalling connection establishment | NAS signalling connection establishment function is provided by the UE and the AMF to establish a NAS signalling connection for a UE in CM-IDLE state. The AMF shall provide the list of recommended cells/ TAs / NG-RAN node identifiers for paging, if the NG-RAN had provided that information in an earlier AN Release Proce... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.3.3.3.3 NAS signalling connection Release | The procedure of releasing a NAS signalling connection is initiated by the AN node (either 5G (R)AN node or N3IWF) or the AMF. The NG-RAN node may include the list of recommended cells/ TAs / NG-RAN node identifiers for paging, during the AN Release Procedure in the AN (see clause 4.2.6 of TS 23.502 [3]). The AMF store... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.3.3.4 Support of a UE connected over both 3GPP and Non-3GPP access | The AMF manages two CM states for an UE: a CM state for 3GPP access and a CM state for Non-3GPP access. An N2 interface can serve the UE for either 3GPP access or for Non 3GPP access. UE connected over both 3GPP and Non-3GPP has got two N2 interfaces, one for each access. A UE may be in any combination of the CM states... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.3.4 UE Mobility | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.3.4.1 Mobility Restrictions | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.3.4.1.1 General | Mobility Restrictions restrict mobility handling or service access of a UE. The Mobility Restriction functionality is provided by the UE (only for mobility restriction categories provided to the UE), the radio access network and the core network.
Unless otherwise stated, Mobility Restrictions only apply to 3GPP access ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.3.4.1.2 Management of Service Area Restrictions | This clause describes Service Area Restrictions for 3GPP access. For Service Area Restrictions when using wireline access, see TS 23.316 [84].
A Service Area Restriction may contain one or more (e.g. up to 16) entire Tracking Areas each or the Service Area Restriction may be set as unlimited (i.e. contain all Tracking ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.3.4.2 Mobility Pattern | The Mobility Pattern is a concept that may be used by the AMF to characterise and optimise the UE mobility. The AMF determines and updates Mobility Pattern of the UE based on subscription of the UE, statistics of the UE mobility, network local policy and the UE assisted information, or any combination of them. The stat... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.3.4.3 Radio Resource Management functions | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.3.4.3.1 General | To support radio resource management in NG-RAN the AMF provides the parameter 'Index to RAT/Frequency Selection Priority' (RFSP Index) to NG-RAN across N2. The RFSP Index is mapped by the RAN to locally defined configuration in order to apply specific RRM strategies, taking into account any available information in RAN... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.3.4.3.2 Preferred band(s) per data radio bearer(s) | The NG-RAN may prefer to use specific radio resources per data radio bearer(s), e.g. depending on the Network Slices associated to the data radio bearer used by the UE. The UE idle mode mobility control and priority-based reselection mechanism operates as described in clause 5.3.4.3.1 and when UP resources are activate... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.3.4.3.3 Redirection to dedicated frequency band(s) for an S-NSSAI | If a Network Slice, S-NSSAI, is configured to be available only in TAs covering specific dedicated frequency band(s), then there may be a need to redirect the UE to the dedicated frequency band(s) when such S-NSSAI is requested. If the Requested NSSAI contains S-NSSAI(s) that are not available in the UE's current TA, s... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.3.4.3.4 Network Slice based cell reselection and Random Access | When one or more S-NSSAI(s) are associated with NSAG(s), the UE may perform Network Slice based cell reselection and Random Access as described in TS 38.300 [27], TS 38.304 [50], TS 38.331 [28], TS 38.321 [143] and TS 24.501 [47].
When providing NSAG Information to the UE, the AMF shall also provide the NSAG priority i... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.3.4.4 UE mobility event notification | 5G System supports the functionality of tracking and reporting UE mobility events.
The AMF provides the UE mobility related event reporting to NF that has been authorized to subscribe to the UE mobility event reporting service. Any NF service consumer such as SMF, NEF, LMF, TSCTSF or NWDAF that wants to be reported on ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.3.5 Triggers for network analytics | Triggers for the AMF to request for or subscribe to the analytics information from the NWDAF are internal logic in the AMF and may include for example:
- UE access and mobility related event subscription by other NFs (e.g. SMF, NEF);
- locally detected events;
- analytics information received.
The trigger conditions ma... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4 3GPP access specific aspects | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.1 UE reachability in CM-IDLE | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.1.1 General | Reachability management is responsible for detecting whether the UE is reachable and providing UE location (i.e. access node) for the network to reach the UE. This is done by paging UE and UE location tracking. The UE location tracking includes both UE registration area tracking (i.e. UE registration area update) and U... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.1.2 UE reachability allowing mobile terminated data while the UE is CM-IDLE | The AMF considers a UE in RM-REGISTERED state to be reachable by CN paging if the UE CM state in the AMF is CM-IDLE state unless the UE applies MICO mode or the UE has indicated Unavailability Period Duration. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.1.3 Mobile Initiated Connection Only (MICO) mode | A UE may indicate preference for MICO mode during Initial Registration or Mobility Registration Update procedure. The AMF, based on local configuration, Expected UE Behaviour and/or Network Configuration parameters if available from the UDM, UE indicated preferences, UE subscription information and network policies, or... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.1.4 Support of Unavailability Period | During Registration procedure, the UE supporting the Unavailability Period feature provides "Unavailability Period Support" indication as part of 5GMM Core Network Capability in Registration Request message for initial registration and for every mobility registration. The AMF indicates whether the corresponding feature... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.2 UE reachability in CM-CONNECTED | For a UE in CM-CONNECTED state:
- the AMF knows the UE location on a serving (R)AN node granularity.
- the NG-RAN notifies the AMF when UE becomes unreachable from RAN point of view.
UE RAN reachability management is used by RAN for UEs in RRC_INACTIVE state, see TS 38.300 [27]. The location of a UE in RRC_INACTIVE sta... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.3 Paging strategy handling | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.3.1 General | Based on operator configuration, the 5GS supports the AMF and NG-RAN to apply different paging strategies for different types of traffic.
In the case of UE in CM-IDLE state, the AMF performs paging and determines the paging strategy based on e.g. local configuration, what NF triggered the paging and information availab... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.3.2 Paging Policy Differentiation | Paging policy differentiation is an optional feature that allows the AMF, based on operator configuration, to apply different paging strategies for different traffic or service types provided within the same PDU Session. In this Release of the specification this feature applies only to PDU Session of IP type.
When the ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.3.3 Paging Priority | Paging Priority is a feature that allows the AMF to include an indication in the Paging Message sent to NG-RAN that the UE be paged with priority. The decision by the AMF whether to include Paging Priority in the Paging Message is based on the ARP value in the message received from the SMF for an IP packet waiting to b... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.4 UE Radio Capability handling | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.4.1 UE radio capability information storage in the AMF | This clause applies when no radio capability signalling optimisation is used between a UE and the network.
The UE Radio Capability information is defined in TS 38.300 [27] and contains information on RATs that the UE supports (e.g. power class, frequency bands, etc). Consequently, this information can be sufficiently l... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.4.2 Void | 5.4.4.2a UE Radio Capability Match Request
If the AMF requires more information on the UE radio capabilities support to be able to set the IMS voice over PS Session Supported Indication (see clause 5.16.3), then the AMF may send a UE Radio Capability Match Request message to the NG-RAN. This procedure is typically used... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.4.3 Paging assistance information | The paging assistance information contains UE radio related information that assists the RAN for efficient paging. The Paging assistance information contains:
a) UE radio capability for paging information:
- The UE Radio Capability for Paging Information contains information derived by the NG-RAN node (e.g. band suppor... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.5 DRX (Discontinuous Reception) framework | The 5G System supports DRX architecture which allows Idle mode DRX cycle is negotiated between UE and the AMF. The Idle mode DRX cycle applies in CM-IDLE state and in CM-CONNECTED with RRC_INACTIVE state.
If the UE wants to use UE specific DRX parameters, the UE shall include its preferred values consistently in every ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.6 Core Network assistance information for RAN optimization | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.6.1 General | Core Network assistance information for RAN aids the RAN to optimize the UE state transition steering and the RAN paging strategy formulation in RRC_INACTIVE state. The Core Network assistance information includes the information set, Core Network assisted RAN parameters tuning, which assist RAN optimize the UE RRC sta... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.6.2 Core Network assisted RAN parameters tuning | Core Network assisted RAN parameters tuning aids the RAN to minimize the UE state transitions and achieve optimum network behaviour. How the RAN uses the CN assistance information is not defined in this specification.
Core Network assisted RAN parameters tuning may be derived by the AMF per UE in the AMF based on colle... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.6.3 Core Network assisted RAN paging information | Core Network assisted RAN paging information aids the RAN to formulate a RAN paging policy and strategy in RRC_INACTIVE state, besides the PPI and QoS information associated to the QoS Flows as indicated in clause 5.4.3.
CN assisted RAN paging information may be derived by the AMF per UE and/or per PDU Session based on... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.7 NG-RAN location reporting | NG-RAN supports the NG-RAN location reporting for the services that require accurate cell identification (e.g. emergency services, lawful intercept, charging) or for the UE mobility event notification service subscribed to the AMF by other NFs. The NG-RAN location reporting may be used by the AMF when the target UE is ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.8 Support for identification and restriction of using unlicensed spectrum | Support for NG-RAN using unlicensed spectrum is defined in TS 38.300 [27] and TS 36.300 [30].
For NG-RAN, in the case of NR in stand-alone mode, all cells are in unlicensed spectrum and the NR is used as primary RAT. NR or E-UTRA cells in unlicensed spectrum, can be used as secondary cells as specified in the Dual Conn... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.9 Wake Up Signal Assistance | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.9.1 General | The RAN and UE may use a Wake Up Signal (WUS) to reduce the UE's idle mode power consumption. The RAN sends the WUS shortly before the UE's paging occasion. The WUS feature enables UEs to determine that in the paging occasions immediately following their WUS occasion they will not be paged if their WUS is not transmitt... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.9.2 Group Wake Up Signal | To support the Wake Up Signal (WUS), the WUS Assistance Information is used by the ng-eNB to help determine the WUS group used when paging the UE (see TS 36.300 [30]).
The content of the WUS Assistance Information consists of the paging probability information. The paging probability information provides a metric on th... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.10 Support for identification and restriction of using NR satellite access | Support for NR satellite access is specified in TS 38.300 [27].
Editor's note: TS 38.300 [27] not yet updated by RAN groups.
The AMF determines the RAT Type for NR satellite access, i.e. NR(LEO), NR(MEO), NR(GEO) and NR(OTHERSAT). When the UE is accessing NR using satellite access, an indication is provided in N2 inter... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.11 Support for integrating NR satellite access into 5GS | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.11.1 General | This clause describes the specific aspects for NR satellite access, including transparent satellite payloads and regenerative satellite payloads, as defined in TS 38.300 [27]. The description for satellite access in this specification is applicable to both transparent satellite payload and regenerative satellite payloa... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.11.2 Support of RAT types defined in 5GC for satellite access | In case of NR satellite access, the RAT Types values "NR(LEO)", "NR(MEO)", "NR(GEO)" and "NR(OTHERSAT)" are used in 5GC to distinguish the different NR satellite access types (see clause 5.4.10).
When a UE is accessing to the network via satellite access, the AMF determines the RAT type as specified in clause 5.4.10.
N... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.11.3 Void | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.11.4 Verification of UE location | In order to ensure that the regulatory requirements are met, the network may be configured to enforce that the selected PLMN is allowed to operate in the current UE location by verifying the UE location during Mobility Management and Session Management procedures. The UE that supports network verified UE location over ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.11.5 Network selection for NR satellite access | Network selection principles specified in clause 5.2.2 apply also for NR satellite access.
For NR satellite access, a UE with location capability should use its awareness of its location to select a PLMN that is allowed to operate in the UE location as specified in TS 23.122 [17].
In order to ensure that the regulatory... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.11.6 Support of Mobility Registration Update | A moving radio cell for NR satellite access may indicate support for one or more TACs for each PLMN. A UE that is registered with a PLMN may access a radio cell and does not need to perform a Mobility Registration Update procedure as long as at least one supported TAC for the RPLMN or equivalent to the RPLMN is part of... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.11.7 Tracking Area handling for NR satellite access | In the case of NR satellite access with moving cells, in order to ensure that each TA is Earth-stationary even if the radio cells are moving across the Earth's surface, the NG-RAN may change the TAC values that are broadcast in a cell's system information as the cell moves, as described in TS 38.300 [27] and TS 38.331 ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.11.8 Support for mobility Forbidden Area and Service Area Restrictions for NR satellite access | Forbidden Area functionality is supported as described in clause 5.3.4.1.1 with the modifications described below:
- The AMF and the UE receive the broadcast TAI (if a single TAI is broadcast) or all broadcast TAIs (if multiple TAIs are broadcast) from the NG-RAN as described clause 5.4.11.7. The AMF considers the UE t... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.11.9 N2 interface and connection management for regenerative satellite payload | The NG Removal procedure defined in TS 38.413 [34] can be used to remove the interface between a gNB and an AMF in a controlled manner, e.g. when the gNB is leaving the service area of an AMF when using regenerative satellite payload.
The serving AMF for a UE can remain the same during feeder link switchover.
NOTE 1: I... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.12 Paging Early Indication with Paging Subgrouping Assistance | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.12.1 General | The RAN and UE may use a Paging Early Indication with Paging Subgrouping (PEIPS) to reduce the UE's power consumption in RRC_IDLE and RRC_INACTIVE over NR (see TS 38.304 [50]).
The paging subgrouping can be based on either the UE's temporary ID or a Paging Subgroup ID allocated by the AMF. Paging subgrouping based on t... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.12.2 Core Network Assistance for PEIPS | To support the Paging Early Indication with Paging Subgrouping (PEIPS), Paging Subgrouping Support Indication and the PEIPS Assistance Information is used by the AMF and NG-RAN to help determine whether PEIPS applies to the UE and which paging subgroup used when paging the UE (see TS 38.300 [27]).
In the Registration R... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.13 Support of discontinuous network coverage for satellite access | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.13.0 General | The present clause 5.4.13 provides optional enhancements to support discontinuous coverage:
- Mobility management and power saving optimization, see clause 5.4.13.1; and
- Coverage availability information provisioning to the UE, see clause 5.4.13.2; and
- Coverage availability information provisioning to the AMF, see ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.13.1 Mobility Management and Power Saving Optimization | For NR satellite access that provides discontinuous network coverage the Mobility Management and Power Saving Optimization functionality may be used.
If both the UE and the network support "Unavailability Period Support" and if the UE determines it will lose coverage and will become unavailable and the UE decides to re... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.13.2 Coverage availability information provisioning to the UE | A UE may use satellite coverage availability information for satellite access to support discontinuous coverage operations. Satellite coverage availability information can be provided to a UE by an external server via a PDU Session or SMS. The protocol and format of satellite coverage availability information via PDU s... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.13.3 Coverage availability information provisioning to the AMF | The AMF may use satellite coverage availability information to support satellite access by UEs with discontinuous coverage operation. Satellite coverage availability information may be provisioned to the AMF by O&M.
NOTE: The satellite coverage availability information provisioned to the AMF describes when and where sa... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.13.4 Paging | In the case of NR satellite access that provides discontinuous network coverage, AMF may utilize sub-area paging as described in clause 4.2.3.3 of TS 23.502 [3] (e.g. first page in the last known cell-id or TA and retransmission in all registered TAs). The AMF may utilize the location information as received at or befo... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.4.13.5 Overload control | The AMF and UE may only use the procedure defined in this clause if both the UE and AMF indicate support for "Unavailability Period Support", see clause 5.4.13.1. A UE indicating support for "Unavailability Period Support" shall support the procedures defined in this clause when leaving coverage and re-gaining coverage... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.