hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.40 Support of Disaster Roaming with Minimization of Service Interruption | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.40.1 General | Subject to operator policy and national/regional regulations, 5GS provides Disaster Roaming service for the UEs from PLMN(s) with Disaster Condition. The UE shall attempt Disaster Roaming only if:
- there is no available PLMN which is allowable (see TS 23.122 [17]);
- the UE is not in RM-REGISTERED and CM-CONNECTED sta... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.40.2 UE configuration and provisioning for Disaster Roaming | A UE supporting Disaster Roaming is configured with the following information:
- Optionally, indication of whether disaster roaming is enabled in the UE;
- Optionally, indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN';
- Optionally, list of PLMN(s) to be used in Di... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.40.3 Disaster Condition Notification and Determination | The NG-RAN in the PLMN that provides Disaster Roaming service, broadcasts an indication of accessibility for Disaster Roaming service and optionally, a 'list of one or more PLMN(s) with Disaster Condition for which Disaster Roaming service is offered by the available PLMN' in the impacted area as described in TS 38.304... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.40.4 Registration for Disaster Roaming service | For a UE to receive Disaster Roaming service from a PLMN providing Disaster Roaming service, the UE sends a NAS Registration Request message with Registration Type value "Disaster Roaming Initial Registration" or "Disaster Roaming Mobility Registration Update":
- When the AMF in the PLMN providing Disaster Roaming serv... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.40.5 Handling when a Disaster Condition is no longer applicable | When a UE detects a Disaster Condition is no longer applicable, the UE performs PLMN selection as described in TS 23.122 [17] and TS 24.501 [47] and may return to the PLMN previously with Disaster Condition.
A PLMN providing Disaster Roaming:
- May trigger the Disaster Inbound Roaming UEs to return to the PLMN previous... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.40.6 Prevention of signalling overload related to Disaster Condition and Disaster Roaming service | The load control, congestion and overload control mechanism specified in clause 5.19 and access control and barring specified in clause 5.2.5 can be used to mitigate the load caused by UE requesting the Disaster Roaming service in the PLMN providing Disaster Roaming service and returning of UE to allowable PLMN when Di... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.41 NR RedCap and NR eRedCap UEs differentiation | This functionality is used by the network to identify traffic to/from UEs accessing over NR RedCap or NR eRedCap, e.g. for charging differentiation.
An NR RedCap UE or NR eRedCap UE using NR shall provide an NR RedCap indication or respectively an NR eRedCap indication to the NG-RAN during RRC Connection Establishment ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.42 Support of Non-seamless WLAN offload | Non-seamless WLAN offload is an optional capability of a UE supporting WLAN radio access.
The architecture to support authentication for Non-seamless WLAN offload in 5GS is defined in clause 4.2.15.
A UE supporting Non-seamless WLAN offload may, while connected to WLAN access, route specific data flows via the WLAN acc... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.43 Support for 5G Satellite Backhaul | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.43.1 General | Satellite may be used as part of the backhaul between (R)AN and 5GC. The 5G System supports to report of usage of satellite backhaul as described in clause 5.43.2.
For some deployments, UPF may be deployed on the satellite. In these cases, edge computing or local switch via UPF deployed on the satellite may be performe... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.43.2 Edge Computing via UPF deployed on satellite | This clause only applies to the case where Edge Computing is deployed with UPF and Edge Computing services on-board the satellite. The UPF deployed on satellite can act as UL CL/BP/local PSA UPF or act as PSA UPF.
NOTE 1: In this Release, Edge Computing via UPF deployed on satellite only applies to GEO satellite backha... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.43.3 Local switch for UE-to-UE communications via UPF deployed on GEO satellite | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.43.3.1 General | The UE to UE traffic may be locally routed by UPF(s) deployed on satellite (i.e. through local switch) to the target UE without traversing back to the satellite gateway on the ground.
Local switching via UPF(s) deployed on satellite in this clause only applies on GEO satellite backhaul case and considers only DNNs and ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.43.3.2 Local switch with PSA UPF deployed on satellite | If SMF selects the UPF deployed on satellite as PSA of UE's PDU Session, the SMF configures the UE's N4 session to forward/detect packet to/from the internal interface as specified for the configuration for the 5GVN group member's N4 Session in clause 5.8.2.13.1 (Support for unicast traffic forwarding of a 5G VN).
SMF ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.43.3.3 Local switching with UL CL/BP and local PSA UPF deployed on satellite | If the UEs using GEO satellite backhaul are served by the same SMF and the GEO satellite(s) serving the UEs has UPF deployed, the SMF may determine to activate local switching and N19 forwarding for the UEs, based on:
1) AF request including of UE identifiers which require communication between UEs as described in clau... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.43.4 Reporting of satellite backhaul to SMF | If the AMF is aware that a satellite backhaul is used towards 5G AN, the AMF may report this to SMF as part of the PDU Session establishment procedure as described in clause 4.3.2 of TS 23.502 [3]. If AMF is aware that satellite backhaul category changes (e.g. at handover), the AMF reports the current Satellite backhau... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.43.5 QoS monitoring when dynamic Satellite Backhaul is used | If dynamic satellite backhaul is used, QoS monitoring may be used to measure packet delay as specified in clause 5.45.2.
If the Satellite backhaul category received from SMF indicates dynamic satellite backhaul is used, the PCF may, based on PCF local policy or configuration, request QoS monitoring for the packet delay... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.44 Support of Personal IoT network service | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.44.1 General | Personal IoT Network (PIN) provides local connectivity between PINEs, i.e. UEs and/or non-3GPP devices. PINEs communicate using PIN direct communication, PIN indirect communication and the PIN-DN communication. The management of the PIN direct communication is out of the scope of this specification. For the PIN indirec... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.44.2 UE policy delivery for PIN | For a PEGC registered in the 5G network, the 5G network supports the provisioning of URSP rules that include a PIN ID as Traffic Descriptor. URSP rules with a PIN ID in the Traffic Descriptor are sent to the PEGC based on the information provided from an AF for PIN as specified in TS 23.502 [3] and TS 23.503 [45] for p... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.44.3 Session management enhancement for PIN service support | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.44.3.1 PDU Session Establishment for PIN | When a PDU Session associated with a PIN is established by PEGC, an SMF is selected according to clause 4.3.2.2.3 of TS 23.502 [3] based on (DNN, S-NSSAI) combination. The PEGC may use IP address allocation methods as specified in clause 5.8.2 (e.g. IPv6 Prefix Delegation feature).
One PEGC may serve more than one PIN.... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.44.3.2 Session management related policy control | For PIN indirect communication and PIN-DN communication via PEGC and 5G network with PDU session, the 5G network supports the session policy control. The policy control is based on session management procedures as specified in TS 23.502 [3] and TS 23.503 [45].
An AF for PIN may provide QoS parameters for PIN traffic to... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.44.3.3 Non-3GPP QoS Assistance Information | QoS experienced by a PINE connected behind a PEGC depends on the end-to-end path between the PINE and the DN, i.e. depends on the QoS differentiation in both the 3GPP network and the non-3GPP network attached to the PEGC. Non-3GPP QoS Assistance Information (N3QAI) enables the PEGC to perform QoS differentiation for PI... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.44.3.4 Non-3GPP delay budget between PINE and PEGC | For PIN indirect communication and PIN-DN communication of a PINE via a PEGC and 5G network, non-3GPP delay is the delay between the PEGC and the PINE. 5GC may need to be aware of the non-3GPP delay and compensate for this delay in 5GS. The compensation is achieved by adjusting the dynamic CN PDB for the 3GPP network b... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.44.4 Identifiers for PIN | A PIN is managed at the PIN application layer. A unique PIN ID in a PLMN is designated to a PIN, e.g. by PIN server as specified in TS 23.542 [181]. In 5GS the PIN ID is only used in the traffic descriptor of URSP rules, for routing traffic of specific PIN towards a dedicated (DNN, S-NSSAI) combination as specified in ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.45 QoS Monitoring | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.45.1 General | QoS monitoring comprises of measurements of QoS monitoring parameters and reports of the measurement result for a QoS Flow and can be enabled based on 3rd party application requests and/or operator policies configured in the PCF. Event Reporting from PCF is specified in clause 6.1.3.18 of TS 23.503 [45] and User Plane ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.45.2 Packet delay monitoring | QoS Monitoring for packet delay allows for the measurement of UL packet delay, DL packet delay or round trip packet delay between UE and PSA UPF. The details of the QoS Monitoring for packet delay are described in clause 5.33.3.
The PCF may calculate Packet Delay Variation (clause 5.37.7) and the round trip packet dela... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.45.3 Congestion information monitoring | The NG-RAN may be required to provide the UL and/or DL QoS Flow congestion information to UPF (i.e. a percentage of congestion level for exposure). The UPF may be required to monitor and expose the UL and/or DL QoS Flow congestion information reported from the NG-RAN.
QoS monitoring request for congestion information p... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.45.4 Data rate monitoring | The QoS Monitoring for data rate allows the measurement of the UL and/or DL data rate per QoS flow at the PSA UPF and it can be applied to a Non-GBR or GBR QoS flow. The data rate is measured over a monitoring averaging window with a standardized value.
The SMF may configure the UPF to perform and report QoS monitoring... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.45.5 Void | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.45.6 Available bitrate monitoring | The QoS Monitoring for available bitrate allows the measurement and report of the UL and/or DL available bitrate for a GBR QoS Flow without Alternative QoS Profiles at the NG-RAN. The available bitrate refers to the bitrate that NG-RAN is able to provide for a QoS Flow within a duration. The duration is based on RAN im... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.46 Assistance to AI/ML Operations in the Application Layer | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.46.1 General | This clause describes the list of 5GC enablers to support the following AI/ML operations in the Application layer over the 5G System:
- AI/ML operation splitting between AI/ML endpoints;
- AI/ML model/data distribution and sharing;
- Distributed/Federated Learning.
NOTE 1: Requirements on 5G System assistance to AI/ML ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.46.2 Member UE selection assistance functionality for application operation | 5G System may support Member UE selection assistance functionality to assist the AF to select member UE(s) that can be used in application operations such as AI/ML based applications (e.g. Federated Learning) as specified in clause 5.46.1 according to the AF's inputs.
The Member UE selection assistance functionality sh... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.47 Support for Network Controlled Repeater (NCR) | A Network-Controlled Repeater node, referred to as NCR-node, is an RF repeater that enables wireless amplifying-and-forwarding functionality in NG-RAN as defined in TS 38.300 [27].
In NCR operation, the NCR-MT as defined in TS 38.300 [27] interacts with the 5GC using procedures defined for UE. The following aspects are... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.48 Subscription-based routing to a target core network | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.48.1 Overview | The "subscription-based routing to a target core network" feature forwards traffic related with a UE to a target (partner) PLMN as specified in clauses 4.2.3 and 4.2.4.
This subscription-based routing to a target core network feature may apply to all signalling and User Plane traffic related to a UE or only to the SM s... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.49 Support for Mobile gNB with Wireless Access Backhauling (MWAB) | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.49.1 General | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.49.1.1 Principles and functional entities | Mobile gNB with Wireless Access Backhauling (MWAB) provides an NR access link to UEs in proximity and connects to the 5GC serving the UE through an IP connectivity provided by a Backhaul PDU session(s), as illustrated in figure 5.49.1.1-1. The MWAB consists of a gNB component (MWAB-gNB) and a UE component (MWAB-UE). Th... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.49.1.2 Backhaul PDU Session handling for MWAB | The use of multiple BH PDU Sessions for MWAB-gNB N2, N3, Xn interfaces and OAM access is based on configuration from OAM of the MWAB Broadcasted PLMN/SNPN.
The MWAB-gNB requests BH PDU Session(s) from the MWAB-UE by providing corresponding traffic descriptors specified in TS 23.503 [45] and TS 24.526 [110], via the imp... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.49.1.3 Support of QoS for UEs served by a MWAB | The MWAB-UE considers the traffic from the MWAB-gNB as application layer traffic and applies the related QoS handling as specified in clause 5.7 for BH PDU Session(s). The MWAB-UE may establish and modify the BH PDU Sessions based on necessary information provided by MWAB-gNB (e.g. according to the QoS requirements ide... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.49.1.4 Support of network slicing for UEs served by a MWAB | A MWAB-gNB can be configured to associate S-NSSAI(s) in the MWAB-Broadcasted PLMN/SNPN to the traffic descriptor for selection of the BH PDU Sessions parameters e.g. use dedicated S-NSSAI in BH PLMN. If no such association exists for a specific S-NSSAIs of the MWAB Broadcasted PLMN/SNPN, the MWAB-gNB associates this S-... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.49.2 Configuration of the MWAB | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.49.2.1 Configuration of the MWAB-UE | The MWAB-UE manages the BH PDU Session(s) for the MWAB operation based on the configuration by the HPLMN or Subscribed SNPN of the MWAB-UE. The configuration of the MWAB-UE can be UE Local Configuration, or URSP rules as defined in TS 23.503 [45], for the determination of the proper PDU session parameters, e.g. the DNN... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.49.2.2 Configuration of the MWAB-gNB | The MWAB-gNB's configuration is managed by the OAM of the MWAB Broadcasted PLMN/SNPN and the address (or FQDN) of the OAM server per MWAB Broadcasted PLMN/SNPN may be configured at the MWAB-gNB. The OAM server of the MWAB Broadcasted PLMN/SNPN provides (re-)configuration parameters considering location of MWAB as speci... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.49.3 Authorization aspects | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.49.3.1 General | There are two aspects related to the authorization of an MWAB. One aspect is the authorization of the MWAB-UE to establish a BH PDU Session. The other aspect is related to the authorization of the MWAB-gNB to operate as a gNB logically belonging to a MWAB Broadcasted PLMN/SNPN which the MWAB-gNB announces in the SIB. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.49.3.2 MWAB-UE authorization | The MWAB-UE is authorized based on its subscription information which includes dedicated S-NSSAI(s) and DNN for MWAB operation. Such dedicated S-NSSAI(s) and DNN(s) shall be part of the subscription information for the MWAB-UE as specified in clause 5.2.3.3.1 of TS 23.502 [3].
The authorization of the MWAB-UE to establ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.49.3.3 MWAB-gNB authorization | The authorization of the MWAB-gNB is managed by the OAM system of the MWAB-Broadcasted PLMN/SNPN as specified in TS 38.401 [42]. The MWAB-gNB establishes a secure and trusted connection to the OAM server using the IP connectivity provided by the MWAB-UE via the Backhaul PDU Session(s) as specified in clause 5.49.1.
The... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.49.4 Support of Additional ULI | The TAC and cell ID broadcasted by the MWAB-gNB are configured and reconfigured e.g. upon MWAB mobility as specified in TS 38.401 [42]. The MWAB-gNB provides these in the User Location Information (ULI) to the AMF serving the UE's accessing MWAB-gNB.
When a UE is served by a cell of MWAB-gNB, the MWAB-gNB shall also pr... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.49.5 Mobility support of MWAB | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.49.5.1 UE mobility when a MWAB-gNB cell is involved | No MWAB-specific enhancements impacting the UE are defined to handle a UE mobility to and from a MWAB-gNB while the UE is in RRC_IDLE, RRC_INACTIVE or RRC_CONNECTED modes, irrespective of whether the MWAB is static or the MWAB is moving, i.e.:
- For UEs in RRC_IDLE and RRC_INACTIVE state, procedure for cell (re) select... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.49.5.2 UE mobility when the UE is moving together with a MWAB cell | For a UE served by an MWAB-gNB cell, the MWAB-gNB may trigger the handover procedures for UEs in RRC_CONNECTED mode as specified in TS 38.401 [42]. For UEs in RRC_IDLE and RRC_INACTIVE state, the existing NAS mobility procedures and Connection Resume procedure are used as specified in TS 23.502 [3]. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.49.5.3 Impact of MWAB mobility | The mobility of MWAB includes the MWAB-UE and the MWAB-gNB aspect.
- The mobility of the MWAB-UE reuses the exiting UE mobility procedures specified for normal UE, subject to constraints specified in TS 38.401 [42]..
- During mobility, a MWAB-gNB can obtain or apply a new configuration as specified in TS 38.401 [42] fr... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.49.6 Control of UE access to MWAB | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.49.6.1 General | Control of UE access to MWAB is supported. If the MWAB-gNB is serving a PNI-NPN, the CAG mechanism described in clause 5.49.6.2 is used. If the MWAB-gNB is serving an SNPN, the SNPN control mechanism described in clause 5.49.6.3 is used.
The MWAB-gNB and the 5GC can reuse other existing mechanisms e.g. forbidden Tracki... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.49.6.2 Control of UE access to an MWAB serving PNI-NPN | According to operator's policy, access control may be applied to UE access to MWAB-gNB cell supporting a PNI-NPN.
If the MWAB-gNB is serving a PNI-NPN, the CAG mechanism defined in clause 5.30.3 can be used for managing UE's access to the MWAB-gNB cell, with the following additional considerations:
- The MWAB-gNB is co... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.49.6.3 Control of UE access to an MWAB broadcasted SNPN | If the MWAB-gNB is serving an SNPN, as illustrated in Annex S, clause S.3, the existing SNPN control mechanism defined in clause 5.30.2.5 can be used to manage the UE's access to MWAB-gNB.
Dedicated SNPN ID(s) or GIN(s) can be used if differentiation is desired in control of UE access to the SNPN via MWAB-gNB or other ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.49.7 Location Service Support of UEs served by MWAB | Location Service involving MWAB is described in clause 5.19 of TS 23.273 [87]. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.49.8 Support of regulatory service via MWAB | Based on the OAM configurations, an MWAB may support emergency services for UEs connected to the MWAB-gNB.
When the MWAB determines that a UE which connects to the MWAB-gNB initiates an emergency PDU Session, e.g. via AS layer signalling, or based on the ARP of the PDU Session context, the following handling applies:
-... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.50 Support for NR Femto | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.50.1 Overview | This clause provides an overview of 5GS functionalities and architecture to support NR Femto deployments.
NOTE: For NR Femto deployments, it is considered that NR Femto nodes are connected to 5GC, not EPC.
For the support of NR Femto in 5GS, the architecture is described in clause 5.50.2.
For the UE access control to t... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.50.2 5GS architecture to support NR Femto | In 5GS, an NR Femto node connects to 5GC directly or via NR Femto Gateway (NR Femto GW) as specified in TS 38.300 [27] (see Annex V).
The NR Femto GW serves as a concentrator for the N2 interface, as described in TS 38.300 [27]. The NR Femto GW appears to the AMF as a gNB. The NR Femto GW appears to the NR Femto node(s... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.50.3 CAG Information Provisioning | In 5G, a CAG owner or an authorized administrator can control/provision subscribers allowed to access CAG cells via the AF using CAG Information Provisioning as defined in clause 4.15.6.2 and 4.15.6.3h of TS 23.502 [3].
In this Release of the specification, CAG Information Provisioning is only applied for non-roaming c... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.51 Support of Energy Efficiency and Energy Saving | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.51.1 General | The 5GS supports some features aimed at Energy saving described in the following clauses. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.51.2 Energy Consumption Information collection, calculation and exposure | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.51.2.1 General | The Energy Information Function (EIF) is defined to:
- collect the UE related Energy Consumption information;
- calculate the Energy Consumption information at UE, S-NSSAI, PDU Session and Service Data Flow (e.g. per UE per application) granularity; and
- expose the Energy Consumption information to the authorized cons... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.51.2.2 Energy Consumption information collection | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.51.2.2.1 General | The Energy Information Function (EIF) collects the UE related Energy Consumption information include Node-level energy consumption information, Node-level data volume from OAM and data volume of the required granularities (i.e. S-NSSAI, PDU Session and/or Service Data Flow) from UPF (via SMF).
Node level energy consump... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.51.2.2.2 Energy Consumption information collection from SMF | The serving SMFs are retrieved by the EIF from the UDM of the UE based on the provided input parameters including the UE ID and (S-NSSAI, DNN).
The EIF invokes Nsmf_EventExposure_Subscribe as defined in TS 23.502 [3] with the required granularities (UE ID, DNN/S-NSSAI, application information (e.g. Application Identifi... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.51.2.2.3 Energy Consumption information collection from OAM | Table 5.51.2.2.3-1 provides the list of information received from OAM. EIF requests the energy consumption and data volume information per NF level from OAM by providing the serving gNB ID(s) and (I-)UPF ID(s) received from SMFs.
The node-level reporting interval from the OAM is the PLMN wide configurable starting time... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.51.2.3 Energy Consumption information calculation | EIF calculates the Energy Consumption information of the required granularities (UE, S-NSSAI, PDU Session and/or Service Data Flow), based on input parameters from Tables 5.51.2.2.2-2 and 5.51.2.2.3-1 and gets the results. Some example formulas to support the above calculation are described in Annex T. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.51.2.4 Energy Consumption information exposure | AF/NEF or 5GC NF subscribes the EIF for Energy consumption information of required granularities (UE, S-NSSAI, PDU session and/or Service Data Flow).
- For UE level energy exposure, the consumer NF provides UE ID (SUPI/GPSI).
- For S-NSSAI of the UE level exposure, the consumer NF provides UE ID (SUPI/GPSI), S-NSSAI.
-... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.51.3 Void | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.51.4 BDT based on network energy related information | 5GS supports BDT (background data transfer) policy selection and re-negotiation process by taking energy indicator from AF into consideration as specified in clause 6.1.2.4 of TS 23.503 [45]. The PCF may make BDT policy decisions based on operator's policy. The PCF may also trigger the re-negotiation of BDT policy with... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.51.5 Subscription information aspects | The Subscription data for a UE may include an Energy Saving Indicator that the UE is subject to network energy saving operation. The values of the Energy Saving Indicator point to energy saving behaviour configured in the NG-RAN and/or AM-PCFs of the PLMN. The possible energy saving behaviours for a PLMN and the mappin... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.51.6 Policy control aspects | During AM policy association establishment or modification procedures, if the Energy Saving Indicator is included in the UE subscription data, the AMF sends to the PCF the Energy Saving Indicator as described in clause 5.51.5. Based on the Energy Saving Indicator it receives from the AMF for a UE, the PCF may make AM p... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.52 QoS differentiation of traffic for Non-3GPP Device Identifier | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.52.1 General | This clause specifies the scenario of a non-3GPP device connecting through the UE. In this scenario QoS differentiation of traffic is applied to the traffic that originates from or is directed to the non-3GPP device. The non-3GPP device does not use NAS and is not authenticated by 5GC.
The support of identification of ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.52.2 Traffic identification | When a non-3GPP device is connecting to the UE, the UE may bind the Non-3GPP Device Identifier to a non-3GPP device, for the traffic of non-3GPP devices that require differentiated QoS. This binding enables the 5G System to distinguish between the traffic generated by different non-3GPP devices connected through the sa... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.52.3 Session management enhancement | For the traffic of non-3GPP devices requiring differentiated QoS, the Non-3GPP Device Connection Information may be signalled by the UE as defined in TS 24.501 [47]. When a non-3GPP device is connected to the UE, the UE may include the Non-3GPP Device Connection Information in PDU Session Modification Request to SMF. T... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.52.4 QoS differentiation | QoS differentiation and policy control is defined in clause 6.1.3.31 of TS 23.503 [45]. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 6 Network Functions | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 6.1 General | Clause 6 provides the functional description of the Network Functions and network entities and the principles for Network Function and Network Function Service discovery and selection.
NG-RAN functions and entities are described in TS 38.300 [27] and TS 38.401 [42].
Security functions and entities are described in TS 3... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 6.2 Network Function Functional description | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 6.2.1 AMF | The Access and Mobility Management function (AMF) includes the following functionality. Some or all of the AMF functionalities may be supported in a single instance of an AMF:
- Termination of RAN CP interface (N2).
- Termination of NAS (N1), NAS ciphering and integrity protection.
- Registration management.
- Connecti... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 6.2.2 SMF | The Session Management function (SMF) includes the following functionality. Some or all of the SMF functionalities may be supported in a single instance of a SMF:
- Session Management e.g. Session Establishment, modify and release, including tunnel maintain between UPF and AN node.
- UE IP address allocation & manageme... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 6.2.3 UPF | The User plane function (UPF) includes the following functionality. Some or all of the UPF functionalities may be supported in a single instance of a UPF:
- Anchor point for Intra-/Inter-RAT mobility (when applicable).
- Allocation of UE IP address/prefix (if supported) in response to SMF request.
- External PDU Sessio... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 6.2.4 PCF | The Policy Control Function (PCF) includes the following functionality:
- Supports unified policy framework to govern network behaviour.
- Provides policy rules to Control Plane function(s) to enforce them.
- Accesses subscription information relevant for policy decisions in a Unified Data Repository (UDR).
- Support P... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 6.2.5 NEF | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 6.2.5.0 NEF functionality | The Network Exposure Function (NEF) supports the following independent functionality:
- Exposure of capabilities and events:
NF capabilities and events may be securely exposed by NEF for e.g. 3rd party, Application Functions, Edge Computing as described in clause 5.13.
NEF stores/retrieves information as structured dat... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 6.2.5.1 Support for CAPIF | When an NEF is used for external exposure, the CAPIF may be supported. When CAPIF is supported, an NEF that is used for external exposure supports the CAPIF API provider domain functions. The CAPIF and associated API provider domain functions are specified in TS 23.222 [64].
6.2.5a Void |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 6.2.6 NRF | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 6.2.6.1 General | The Network Repository Function (NRF) supports the following functionality:
- Supports service discovery of NRF services and their endpoint addresses by the NRF bootstrapping service.
- Supports service discovery function. Receive NF Discovery Request from NF instance or SCP and provides the information of the discover... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 6.2.6.2 NF profile | NF profile of NF instance maintained in an NRF includes the following information:
- NF instance ID.
- NF type.
- PLMN ID in the case of PLMN, PLMN ID + NID in the case of SNPN.
- Network Slice related Identifier(s) e.g. S-NSSAI, NSI ID.
- FQDN or IP address of NF.
- NF capacity information.
- NF priority information.
... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.