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 state over non-3GPP access connected to 5GCN;
- the UE cannot get service over non-3GPP access through ePDG;
- the UE supports Disaster Roaming service;
- the UE has been configured by the HPLMN with an indication of whether Disaster roaming is enabled in the UE set to "disaster roaming is enabled in the UE" as specified in clause 5.40.2; and
- a PLMN without Disaster Condition is able to accept Disaster Inbound Roamers from the PLMN with Disaster Condition.
In this Release of the specification, the Disaster Condition only applies to NG-RAN nodes, which means the rest of the network functions except one or more NG-RAN nodes of the PLMN with Disaster Condition can be assumed to be operational. |
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 Disaster Condition.
The Activation of Disaster Roaming is performed by the HPLMN by setting the indication of whether Disaster roaming is enabled in the UE to "disaster roaming is enabled in the UE" using the UE Parameters Update Procedure as defined in TS 23.502 [3]. The UE shall only perform disaster roaming if the HPLMN has configured the UE with the indication of whether disaster roaming is enabled in the UE and set the indication to "disaster roaming is enabled in the UE". The UE, registered for Disaster Roaming service, shall deregister from the PLMN providing Disaster Roaming service if the received indication of whether disaster roaming is enabled in the UE is set to "disaster roaming is disabled in the UE".
The optional 'list of PLMN(s) to be used in Disaster Condition' may be pre-configured in USIM or provided by the HPLMN during and after a successful registration procedure over 3GPP access or non-3GPP access via Registration Request procedure or UE Configuration Update procedure as defined in TS 23.502 [3]. The 'list of PLMN(s) to be used in Disaster Condition' may be configured over non-3GPP access before disaster condition has occurred.
While roaming (i.e. not in HPLMN), the Registered PLMN may provide the 'list of PLMN(s) to be used in Disaster Condition' during and after a successful registration procedure to the UE via Registration Request procedure or UE Configuration Update procedure as specified in TS 23.502 [3]. This list shall not alter any list provided by the HPLMN and shall only be used if the UE is configured by the HPLMN using the UE Parameters Update Procedure as defined in TS 23.502 [3] with the indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN' set to "True".
The details of the UE behaviour regarding the usage of this list are described in TS 23.122 [17] and TS 24.501 [47]. If the UE is not configured with 'list of PLMN(s) to be used in Disaster Condition', the UE follows the procedure described in TS 23.122 [17] to select PLMN to be used in Disaster Condition.
The HPLMN may use UE Parameters Update Procedure as defined in TS 23.502 [3] to update the Disaster Roaming information configuration in UE, if the UDM has received MINT support indication as indicated in 5GMM capability from the AMF. The UE indicates the support of MINT in 5GMM capability as specified in clause 5.4.4a, during registration procedure as defined in TS 23.502 [3]. |
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 [50] and TS 38.331 [28].
A UE determines the Disaster Condition based on the information broadcasted from the NG-RAN providing Disaster Roaming service and performs the network selection and the access control for the Disaster Roaming as described in TS 23.122 [17] and TS 24.501 [47].
NOTE 1: How a PLMN is notified that another PLMN is a PLMN with Disaster Condition and how a PLMN is notified of the area where the associated Disaster Condition applies is managed by the government agencies or the authorities and is out of scope of 3GPP.
NOTE 2: The broadcast for Disaster Roaming service from the NG-RAN occurs only during the Disaster Condition. |
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 service receives a NAS Registration Request with Registration Type set to "Disaster Roaming Initial Registration" or "Disaster Roaming Mobility Registration Update";
- the AMF controls if the UE is allowed to access Disaster Roaming service in the area with Disaster Condition as specified in clause 4.2.2.2.2 of TS 23.502 [3];
- the AMF may provide the Disaster Roaming service indication to AUSF and UDM as specified in clause 4.2.2.2.2 of TS 23.502 [3] and TS 33.501 [29]. The AMF may provide the Disaster Roaming service indication to SMF as specified in clause 4.3.2 of TS 23.502 [3].
NOTE 1: The AUSF and the UDM are configured with Disaster Condition via OAM based on operator policy and the request by the government agencies. Based on this local configuration and/or the Disaster Roaming service indication, the AUSF can execute authentication of the UE and the UDM can provides the subscription data for a Disaster Roaming service to the AMF and/or the SMF.
To support the Disaster Roaming service, the PLMN providing Disaster Roaming service is configured to support communication with the network entities in the HPLMN of the UE, i.e. configurations related to roaming interfaces for communication between serving PLMN and HPLMN shall be deployed in the affected entities. This communication between the PLMNs need only be enabled during the Disaster Condition.
The Disaster Roaming service is limited to the impacted geographic area with Disaster Condition. The NG-RAN nodes and AMF in the PLMN providing Disaster Roaming service are configured with the area information, i.e. a list of TAIs which can be formulated by the PLMN providing the Disaster Roaming service based on the geographic area with Disaster Condition in the other PLMN(s).
The AMF in the PLMN providing Disaster Roaming service provides the mobility restriction list to the NG-RAN as specified in clause 5.3.4.1.1 considering the area with Disaster Condition and also indicating that EPC is not an allowed core network.
NOTE 2: From the perspective of emergency services, a UE is following procedures as described in clause 4.24 of TS 24.501 [47] when registered for Disaster Roaming service.
NOTE 3: When the UE is registered for Disaster Roaming service, SMS over NAS can be supported with the procedures as described in clause 4.13.3.1 of TS 23.502 [3] based on subscription data. |
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 previously with Disaster Condition when the Disaster Inbound Roamers attempt to transit to 5GMM-CONNECTED mode.
- May trigger the Disaster Inbound Roaming UEs to return to the PLMN previously with Disaster Condition by triggering Deregistration procedure.
- May trigger the Disaster Inbound Roaming UEs to return to the PLMN previously with Disaster Condition by rejecting Registration Request message.
- May trigger the Disaster Inbound Roaming UEs to return to the PLMN previously with Disaster Condition by rejecting Service Request message.
- Shall organise the return of the Disaster Roaming UEs in a manner that does not cause overload (e.g. of signalling) in the PLMN that previously had the Disaster Condition.
- Stop broadcasting of providing Disaster Roaming service as specified in clause 5.40.3.
- May determine that the disaster condition has ended and the UE which is registered for disaster roaming services has an emergency PDU session, the AMF initiates the UE configuration update procedure to indicate that the UE is registered for emergency services as described in TS 24.501 [47].
- May determine that the disaster condition has ended and inform the UE by initiating the UE configuration update procedure indicating re-registration from UE is required as specified in clause 5.4.4 of TS 24.501 [47] if the UE is in CM-CONNECTED mode.
NOTE: Whether and how long the PLMN waits before paging the Disaster Inbound Roamers upon being notified that a Disaster Condition no longer applies is up to operator's policy.
The HPLMN i.e. the UDM may trigger the Disaster Inbound Roaming UEs to return to the PLMN previously with Disaster Condition by triggering Deregistration procedure. |
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 Disaster Condition is no longer applicable.
To prevent signalling overload in PLMN providing Disaster Roaming, the HPLMN or registered PLMN:
- may provide the UE in a prioritized manner with the list of PLMNs described in clause 5.40.2 for Disaster Roaming;
- may provide disaster roaming wait range information to control when the UE can initiate the registration for Disaster Roaming service upon arriving in the PLMN providing Disaster Roaming service as specified in TS 23.122 [17] and TS 24.501 [47]; and
- applies Access Identity 3 for Disaster Roaming service request as specified in TS 24.501 [47].
NOTE: The mechanisms available at the AMF and the SMF for mitigation of overload and congestion are used for 5GSM congestion mitigation during the Disaster Roaming.
To prevent signalling overload by returning UEs in PLMN previously with Disaster Condition which is no long applicable, the HPLMN or registered PLMN:
- may provide disaster return wait range information to control when the UE can initiate the registration upon returning to the PLMN previously with Disaster Condition as specified in TS 23.122 [17] and TS 24.501 [47]. |
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 procedure as defined in TS 38.300 [27].
When the UE has provided an NR RedCap indication indicating support of NR RedCap to the NG-RAN during RRC Connection Establishment, the NG-RAN shall provide an NR RedCap Indication to the AMF in the Initial UE Message (see clause 4.2.2.2.1 of TS 23.502 [3] and TS 38.413 [34]).
When the UE has provided an NR eRedCap indication indicating support of NR eRedCap to the NG-RAN during RRC Connection Establishment, the NG-RAN shall provide an NR eRedCap Indication to the AMF in the Initial UE Message (see clause 4.2.2.2.1 of TS 23.502 [3] and TS 38.413 [34]).
When the AMF receives an NR RedCap Indication or NR eRedCap Indication from NG-RAN in an Initial UE Message, the AMF shall store the NR RedCap Indication or NR RedCap Indication in the UE context, consider that the RAT type is NR RedCap or NR eRedCap and signal it accordingly to the SMSF during registration procedure for SMS over NAS, to the SMF during PDU Session Establishment or PDU Session Modification procedure. The PCF can also receive the NR RedCap or NR eRedCap RAT type when applicable from the AMF using the PCRT on Access Type change specified in clause 6.1.2.5 of TS 23.503 [45] during AM Policy Association Establishment or AM Policy Association Modification procedure and from the SMF using the PCRT on Access Type change specified in clause 6.1.3.5 of TS 23.503 [45] during SM Policy Association Establishment or SM Policy Association Modification procedure.
During handover from E-UTRA to NR, the target NG-RAN (i.e. gNB) provides the NR RedCap indication or NR eRedCap indication to AMF in NGAP Path Switch Request message during Xn handover, or NGAP Handover Request Acknowledge message during N2 handover (including intra 5GS N2 handover and EPS to 5GS handover) based on the UE capability information provided by the source RAN to the target RAN as specified in TS 38.300 [27].
The NFs interacting with CHF shall include the NR RedCap or NR eRedCap as RAT type.
Upon AMF change, the source AMF shall provide the "NR RedCap Indication" or "NR eRedCap Indication" to the target AMF.
If a UE supports either NR RedCap or NR eRedCap as specified in TS 38.306 [69] and the UE NG-RAN Radio Capability information changes following the procedure in clause 5.4.4.1, when the UE performs RRC Connection Establishment procedure, the UE shall report the NR RedCap indication or NR eRedCap indication that applies to the new Radio Capability. |
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 access without traversing the 5GC. These UE data flows are identified using URSP configuration for Non-Seamless Offload, or UE Local Configurations as defined in TS 23.503 [45]. For these data flows, the UE uses the local IP address allocated by the WLAN access network and no IP address preservation is provided between WLAN and NG-RAN.
For performing the Non-seamless WLAN offload, the UE needs to acquire a local IP address from the WLAN access network and it is not required to connect to an N3IWF, ePDG or TNGF. If the WLAN access network is configured to require the 5GS based access authentication of the UE for connecting to the WLAN, the UE performs the authentication procedure for Non-seamless WLAN offload in 5GS defined in clause 4.2.15 and in Annex S of TS 33.501 [29]. After successful authentication, the UE is not considered to be entered in 5GS Registered state. The UE can send and receive traffic not traversing the 5GC and which is not under the control of the 5GC.
A non-3GPP access network may be connected via SWa' to multiple PLMNs for 5G NSWO. In a roaming scenario the HPLMN may be reached by the UE via a WLAN access connected to more than one VPLMN. Therefore, a UE when roaming shall be able to indicate a specific selected VPLMN using decorated NAI for 5G NSWO, as specified in clauses 28.7.9.1 and 28.7.9.2 of TS 23.003 [19], through which the NSWO request should be sent towards the HPLMN.
A non-3GPP access network may be connected to multiple SNPNs different from the Credentials Holder for 5G NSWO. When using the credentials owned by CH, the UE shall be able to indicate a specific selected SNPN (e.g. using decorated NAI for 5G NSWO) through which the NSWO request should be sent towards the CH in the following scenarios:
- The CH hosts AUSF/UDM and the CH is reached by the UE via a WLAN access connected to a SNPN different from the CH as defined in Figure 4.2.15-3a.
- The CH hosts AAA server and the CH is reached by the UE via a WLAN access connected to the AAA proxy in specific SNPN as defined in Figure 4.2.15-3b.
A UE connected to a WLAN access network using 5GS credentials (as shown in Figure 4.2.15-1), may also be connected to the 5GC, for example to establish a PDU session. For example, the UE may connect to the 5GC either via another access type (such as NG-RAN), or via the same WLAN access network by performing the 5GS registration via Untrusted non-3GPP access procedure (using N3IWF) or interworking between ePDG connected to EPC and 5GS (using ePDG) defined in TS 23.502 [3].
When a UE is connected to a WLAN access network (e.g. using 5GS credentials) and using an Untrusted non-3GPP access, the UE can perform Non-Seamless Offload of some or all data traffic to this WLAN access network sending the traffic outside the IPSec tunnel encapsulation as defined in URSP rules with Non-Seamless Offload indication.
A UE may use the Registration procedure for Trusted non-3GPP access defined in clause 4.12a.2.2 of TS 23.502 [3] and then determine to send some traffic (to be subject to Non-seamless WLAN offload) outside of the IPSec tunnel established with the TNGF.
NOTE: A UE cannot first connect to a WLAN access network using 5GS credentials and without performing 5GS registration and then later, on this WLAN access network, perform 5GS registration using the Trusted non-3GPP access procedure without first having to release the WLAN and then to establish a new WLAN association per the Registration procedure for Trusted non-3GPP access as defined in clause 4.12a.2.2 of TS 23.502 [3].
When the UE decides to use 5G NSWO to connect to the WLAN access network using its 5GS credentials but without registration to 5GS, the NAI format for 5G NSWO is used whose realm is different than the realm defined for usage of Trusted non-3GPP access to the 5GC (defined in clauses 28.7.6 and 28.7.7 of TS 23.003 [19]).
The NAI format for 5G NSWO is defined in TS 23.003 [19]. |
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 performed as described in clauses 5.43.2 and 5.43.3. Deployments with satellite backhaul and edge computing with UPF on the ground is supported as described in clause 5.13, i.e. without satellite backhaul specific requirements. |
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 backhaul.
To select the UPF deployed on satellite as PSA, the following enhancements apply:
- If the UE is accessing gNB with satellite backhaul and AMF is aware of the satellite backhaul category, the AMF sends the satellite backhaul category to the PCF. If GEO satellite backhaul category is indicated, the PCF may take it into account to generate or update the URSP rule as defined in clause 6.1.2.2 of TS 23.503 [45] to including an appropriate Route Selection Descriptor for services deployed on GEO satellite, which further enable PDU Session Establishment with PSA UPF on the satellite.
Based on GEO satellite ID provided by the AMF, the SMF performs PSA UPF selection or UL CL/BP/local PSA selection and insertion during the PDU Session Establishment procedure as described in clause 4.3.2 of TS 23.502 [3] or PDU Session Modification procedure as described in clause 4.3.3 of TS 23.502 [3] to select the UPF deployed on the GEO satellite if available, which includes:
- Based on configuration, the AMF may determine the GEO Satellite ID serving the UE and send it to the SMF. If GEO satellite ID changes, e.g. due to UE handover to an gNB using different GEO satellite as part of backhaul, the AMF may update the latest GEO Satellite ID to the SMF.
NOTE 2: It is assumed that AMF determines the GEO Satellite ID based on local configuration, e.g. based on Global RAN Node IDs associated with satellite backhaul.
- The SMF determines DNAI based on local configuration, DNN or S-NSSAI or both and the GEO Satellite ID received from AMF.
NOTE 3: It is assumed that one or more DNAI values are assigned for each GEO Satellite ID by the operator. SMF is locally configured with mapping relationship between DNAI and GEO Satellite ID.
- If the UE is allowed to access the service(s) according to the EAS Deployment Information as described in clause 6.2.3.4 of TS 23.548 [130], the SMF selects the PSA UPF or UL CL/BP/local PSA based on the DNAI corresponding to the GEO Satellite ID and other factors as described in clause 6.2.3.2 of TS 23.548 [130].
NOTE 4: EASDF may be deployed on satellite based on local configuration. |
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 slices for 5G VN.
N19 tunnel may be established between two UPFs deployed on different satellites for traffic between UEs. Also, N6 may be used for carrying traffic between UPFs deployed on different satellites.
Only a single SMF is supported for local switching and N19 forwarding, i.e. both UEs are served by the same SMF.
NOTE: The latency optimisation that can be gained by inter-satellite link between UPFs on different GEO satellites depends on the distance between the satellites that can be substantial, depending on the number of deployed satellites.
Clause 5.43.3.2 describes the case of PSA UPF deployed on satellite, clause 5.43.3.3 describes the case of UL CL/BP and local PSA deployed on satellite (PSA UPF is on the ground). Selection of PSA UPF or UL CL/BP/local PSA on satellite is described in clause 6.3.3 and determination of DNAI to select the UPF deployed on the corresponding GEO satellite reuses the mechanism described in clause 5.43.2.
A combination of DNN/S-NSSAI is assigned by the operator for the communications between UEs where backhaul with UPF is deployed on GEO satellite, the URSP is described in TS 23.503 [45] and its configuration to enable the selection PSA UPF on the GEO satellite reuses the mechanism described in clause 5.43.2. |
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 may reuse the mechanism described in clause 5.8.2.13.1 to configure group-level N4 session rules for each N19 tunnel.
For establishing N19 tunnel between the PSA UPFs onboard the satellite, the PSA UPFs are controlled by the same SMF.
- To process packets between UE and servers residing in DN, SMF configures rules to route traffic via N6 as described in clause 5.8.2.13.1.
The group-level N4 session is per DNN and S-NSSAI. The SMF can create, update or delete the group-level N4 Session, i.e. add or delete N4 rules, allocate or release the N19 tunnel resources based on operator deployment, e.g. based on GEO satellite's planned obsolescence or new GEO satellite setup.
N6 may be used for carrying traffic between PSA UPFs deployed on different satellites. If N6 is used, SMF configures corresponding N4 rules for processing traffic to/from N6. |
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 clause 5.29.2; and/or
2) Destination IP address(es) reported by on-ground PSA UPF as current reporting mechanism in clause 5.8.5.7. To enable the destination IP address(es) reporting, SMF configures the on-ground PSA UPF to detect UL packets with destination IP addresses which belong to the current UPF address pool.
If the SMF determines that the UEs (i.e. corresponding to AF request in bullet 1) and/or the Destination IP address(es) reported in bullet 2)) are under the same GEO satellite (or multiple connectable GEO satellites) based on GEO Satellite ID(s) reported by AMF and the UEs are allowed to access the DNAIs corresponding to the GEO satellite IDs, for each UE communicating with target UE(s) in the communication group, the SMF may select and insert the UPF deployed on GEO satellite according to the DNAI as UL CL/BP and L-PSA and configures UL CL/BP with the following rule:
- Route the data traffic received from the UE and destined to IP address(es) of the target UE(s) to the L-PSA.
- Route other data traffic received from the UE to the PSA UPF of the UE's PDU Session.
NOTE 1: The SMF determines the GEO satellites are connectable based on configuration.
The SMF configures the Local PSA with local forwarding rules to forward the data traffic to the target UEs directly. If the selected L-PSAs are different for the UEs in the communication group, N19 tunnel is established between the L-PSAs. For establishing N19 tunnel between the UPFs onboard the satellite, the UPFs are controlled by the same SMF. If UEs are members of the same 5G VN group, the SMF may configure the local data forwarding rules on L-PSA(s) using 5GVN user plane handing mechanism in clause 5.8.2.13.1 (Support for unicast traffic forwarding of a 5G VN).
NOTE 2: The selected UPF deployed on satellite can be inserted as UL CL/BP/L-PSA reusing existing UL CL/BP insertion procedures defined in TS 23.502 [3] or TS 23.548 [130].
N6 may be used for carrying traffic between L-PSA UPFs deployed on different satellites. If N6 is used, SMF configures corresponding N4 rules for processing traffic to/from N6. |
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 backhaul category to SMF. The SMF reports it to the PCF when the "Satellite backhaul category change" PCRT was armed as specified in TS 23.503 [45], or notifies it to other NFs if requested as described in clause 5.2.8.3 of TS 23.502 [3]. When the backhaul network changes from a type of satellite to terrestrial network, the AMF reports that non-satellite backhaul network is used with the Satellite backhaul category.
Satellite backhaul category refers to the type of the satellite (i.e. GEO, MEO, LEO or OTHERSAT, DYNAMIC_GEO, DYNAMIC_MEO, DYNAMIC_LEO and DYNAMIC_OTHERSAT) used in the backhaul as specified in clause 5.4.3.39 of TS 29.571 [183]. The dynamic satellite backhaul category (i.e. DYNAMIC_GEO, DYNAMIC_MEO, DYNAMIC_LEO and DYNAMIC_OTHERSAT) refers that i.e. capabilities (latency and/or bandwidth) of the satellite backhaul change over time due to e.g. use of varying inter-satellite links as part of backhaul. Only a single backhaul category can be indicated.
NOTE: It is assumed that the AMF can determine the Satellite backhaul category for the notification to the SMF based on local configuration, e.g. based on Global RAN Node IDs associated with satellite backhaul. |
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 between UE and PSA UPF as specified in clause 5.45.2. The AF may trigger QoS monitoring by requesting QoS monitoring report from the PCF e.g. when the AF has received a dynamic satellite backhaul category.
NOTE: PCF handling of satellite backhaul category indication and possible QoS monitoring is specified in TS 23.503 [45]. |
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 indirect communication and PIN-DN communication, the data traffic and PIN management traffic pass via a PEGC. With the support of the PEGC registered to 5G network, the PINEs have access to the 5G network services and may communicate with other PINEs within the PIN or with the DN via 5G network. A PEGC may support multiple PINs. For each PIN, a dedicated (DNN, S-NSSAI) combination shall be configured.
PIN and PINEs are managed by specific PEMC with support of an AF, if AF (Application Server and PIN server as specified in TS 23.542 [181]) is deployed. A PIN includes at least one PEGC and at least one PEMC. The management of the PIN (i.e. the management of PIN creation, deletion and update) and PINE (including the management role distribution between PEMC and AF) is out of the scope of this specification.
The PEGC is a UE with subscription data related to PIN within the 5GS (i.e. dedicated (DNN, S-NSSAI) combination(s) for PIN) and shall register to 5G network as UE in order to support PIN indirect communication and PIN-DN communication via dedicated PDU session. The UE acting as PEMC does not have subscription data related to PIN within the 5GS and behaves as normal UE if it is registered in 5GS.
An AF for PIN may be deployed to support the PIN service. The AF for PIN may communicate with PINEs, including PEMC and PEGC, via application layer for management of the PIN which is transported as user plane data transparently to 5G network and the AF for PIN may communicate with the 5GC via NEF.
The PEMC can manage a PIN via PIN direction communication or PIN indirect communication with the other PINEs of the PIN or via PIN-DN communication with an AF for PIN which enables the exchange of information with 5GC.
The 5GC is enhanced to support the delivery of UE policy related to PIN service for PEGC (as specified in clause 5.44.2) and to support the PDU session management for PIN service (as specified in clause 5.44.3).
See information in Annex P for the relation between PIN and 5GS. The PINE, PEMC and PEGC application layer functionalities are defined in TS 23.542 [181] and are transparent in 5G network.
The support of PIN by 5G-RG and FN-RG is not specified.
Redundant PDU session for URLLC is not supported in conjunction with PIN. |
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 policy delivery. |
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. The PEGC may use a single or multiple PDU sessions to serve multiple PINs. One PDU Session may be shared by more than one PIN served by the PEGC, if differentiation or isolation for the traffics to/from different PINs via the PEGC is not required in 5GS. Otherwise, different (DNN, S-NSSAI) combinations shall be applied to distinguish the PINs by different PDU sessions of the PEGC.
One PIN can be served by only one PDU session in the PEGC. If there are multiple PDU sessions for a PIN from different PEGCs connecting to the same UPF, the same mechanism for local switching in the UPF as defined for 5G VN group communication, as described in clause 5.8.2.13, may be applied. |
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 5GC as specified in clauses 4.15.6.6, 4.15.6.6a and 4.15.6.14 of TS 23.502 [3].
An AF for PIN may influence traffic routing for PDU sessions for PIN-DN communication as specified in clause 5.6.7 and in clause 4.3.6 of TS 23.502 [3]. |
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 PINEs in the non-3GPP network behind the PEGC.
During PDU session establishment and PDU session modification procedure, if the SMF provides the PEGC with QoS flow descriptions, the SMF may additionally signal N3QAI for each QoS flow to the PEGC based on the (DNN, S-NSSAI) combination of the PDU Session. Based on the N3QAI together with QoS rule information, the PEGC may reserve resources in the non-3GPP network. N3QAI consists of the following QoS information: QoS characteristics, GFBR/MFBR, Maximum Packet Loss Rate.
How to enforce QoS based on the N3QAI in the non-3GPP network is considered outside the scope of 3GPP. |
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 by the non-3GPP delay (i.e. the network determined original PDB value is unchanged, but it needs to cover non-3GPP delay, besides the AN PDB and CN PDB).
If the PEGC supports providing of the non-3GPP delay budget for a specific QoS flow of the PIN traffic, the PEGC may provide a non-3GPP delay budget to SMF by using the UE requested PDU Session Modification procedure. Based on the (DNN, S-NSSAI) combination of the PDU Session, the SMF may, according to operator policy and implementation, consider the non-3GPP delay budget when signalling the dynamic CN PDB to NG-RAN. The dynamic CN PDB signalled to the NG-RAN may be calculated as the sum of the value of dynamic CN PDB for the related GBR QoS flow and the requested non-3GPP delay budge. If the dynamic CN PDB changes in the SMF (e.g. when an I-UPF is inserted by the SMF), based on the (DNN, S-NSSAI) combination of the PDU Session, the SMF may apply the non-3GPP delay budget again before signalling the dynamic CN PDB to NG-RAN. The non-3GPP delay budget does not impact the QoS flow binding in SMF.
NOTE: For deployments that support a PEGC to request a non-3GPP delay budget it is assumed that RAN is locally configured to give precedence to the CN PDB value received via N2 signalling as specified in clause 5.7.3.4.
It is assumed that the PEGC will limit the frequency of triggering the UE-initiated PDU Session Modification request to provide the non-3GPP delay budget to the network to avoid unnecessary signalling. |
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 clause 6.6.2 of TS 23.503 [45].
If a PIN contains more than one PEGCs, the list of PEGCs may be grouped together following the 5G VN group management principles as specified in clause 5.29.2. Then the PEGCs of a PIN can be identified by an External Group ID by an AF for PIN. The AF for PIN may use the External Group ID to manage the list of PEGCs that are part of a PIN and for providing URSP guidance (as specified in clause 5.44.2) and/or QoS requests applicable to all the PEGCs (as specified in clause 5.44.3).
NOTE: The PEMCs can also be grouped together with the PEGCs using the 5G VN group management functionality for enabling the PEMCs to communicate with PEGCs via UPF local switch in order to manage the PIN. |
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 QoS Flow related QoS monitoring and reporting in clause 5.8.2.18.
The AF may request measurements for one or more of the following QoS monitoring parameters, which may trigger QoS monitoring for service data flow(s):
- UL packet delay, DL packet delay, round trip packet delay for a service data flow, see clause 5.45.2.
- Congestion, see clause 5.45.3.
- Data Rate, see clause 5.45.4.
- Packet Delay Variation, see clause 5.37.7.
- Round trip packet delay considering UL on a service data flow and DL of another service data flow, see clause 5.37.4.
- Available Bitrate, see clause 5.45.6.
The following AF requested QoS requirements may trigger QoS monitoring for service data flow(s):
- Round-trip latency requirement, see clause 5.37.6.
The PCF may generate the authorized QoS Monitoring policy for a service data flow based on the QoS Monitoring request received from the AF (as described in clause 6.1.3.21 of TS 23.503 [45]) or based on PCF local policy or configuration reasons, such as PCF awareness of dynamic satellite backhaul connection. The PCF includes the authorized QoS Monitoring policy in the PCC rule and provides it to the SMF.
The QoS monitoring parameter(s) that can be measured by means of QoS monitoring are listed below. The QoS monitoring policy in PCC rule (described in clause 6.3.1 of TS 23.503 [45]) may include the following:
- UL packet delay, DL packet delay, round trip packet delay, see clause 5.45.2.
- Congestion, see clause 5.45.3.
- Data Rate, see clause 5.45.4.
- Available Bitrate, see clause 5.45.6.
The SMF configures the UPF to perform QoS monitoring for the QoS Flow and to report the monitoring results as described in clause 5.8.2.18 with parameters determined by the SMF based on the authorized QoS Monitoring policy received from the PCF or local configuration or both.
The SMF may also configure NG RAN to measure the QoS monitoring parameters by sending QoS monitoring request based on the authorized QoS Monitoring policy received from the PCF and/or local configuration. The QoS monitoring request to the NG RAN for different parameters is as defined in clause 5.45.2, 5.45.3 and 5.45.6.
Based on configuration, the AMF may know whether the QoS monitoring feature (i.e. each of Packet delay monitoring and/or Congestion monitoring) is supported by all NG RAN nodes in an area. The AMF shall, when configured, inform the SMF about the support of the QoS monitoring feature by sending the parameter NG RAN QoS monitoring capability during PDU Session establishment, PDU Session modification, Service request and UE mobility procedures. The SMF determines whether QoS monitoring is possible or not for the PDU Session based on whether the NG RAN QoS monitoring capability is received (or not) from the AMF and the QoS monitoring capability of the UPF. QoS monitoring is possible if the SMF has received the NG RAN QoS monitoring capability in the last message received from AMF (i.e. Nsmf_PDUSession_CreateSMContext or Nsmf_PDUSession_UpdateSMContext service operation) and the UPF also supports the corresponding QoS monitoring capability. Otherwise, QoS monitoring is not possible for the PDU Session for the respective QoS monitoring parameter(s). The SMF may need to notify the PCF when the support for QoS monitoring has changed as described in clause 6.1.3.5 of TS 23.503 [45] also indicating the affected QoS monitoring parameter(s).
NOTE 1: The AMF is not required to immediately update the SMF about a change of support of the QoS monitoring feature (by all NG RAN nodes in an area) when the change is happening outside of the UE mobility procedures. As AF logic can depend on the QoS monitoring reports, the change from support of QoS monitoring to no support of QoS monitoring is more important to notify than the change in the other direction and is therefore expected to take place in a timely manner.
The following clauses describe the QoS monitoring parameters which can be measured and any specific actions or constraints for their measurement.
NOTE 2: The QoS monitoring parameter which can be measured are parameters which describe the QoS experienced in the 5GS by the application, i.e. they are not restricted to the 5G QoS Parameters defined in clause 5.7.2. |
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 delay when UL and DL are on different QoS flows (clause 5.37.4) based on packet delay monitoring results of QoS flows. |
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 provided by the SMF to the NG-RAN is to trigger the NG-RAN to measure and report UL and/or DL QoS Flow congestion information to PSA UPF as defined in 5.37.3.
NOTE 1: How the RAN measures and reports the congestion information is up to RAN implementation.
NOTE 2: It is assumed that the RAN reports whenever there is a change in the percentage of packets to be marked with ECN for L4S marking and/or congestion information. The granularity of change in percentage determination is up to RAN implementation.
For the reporting of the congestion information from PSA UPF, the periodical reporting is not applied and only the Reporting frequency 'event triggered' applies, see clause 5.8.2.18.
The PSA UPF reports the received UL and/or DL QoS Flow congestion information to the target NF as instructed by the QoS Monitoring request (see clause 5.8.2.18) from the SMF.
Only ECN marking for L4S in NG-RAN (as described in clause 5.37.3) or QoS monitoring of congestion information may be requested to NG-RAN for a QoS Flow. QoS Monitoring of congestion information for exposure and ECN marking for L4S (in NG-RAN or UPF) are mutually exclusive, therefore, measurements of Congestion information on a QoS Flow are not exposed in QoS Monitoring reports if SMF enables ECN marking for L4S (see clauses 5.37.3 and 5.37.4). |
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 for data rates as described in clause 5.8.2.18. According to the QoS Monitoring request for UL and/or DL data rate from the SMF, the UPF is required to initiate data rate measurement for a QoS Flow and to report the measured data rate as instructed. |
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 implementation.
NOTE 1: How the NG-RAN measures the available bitrate is NG-RAN implementation specific.
NOTE 2: The available bitrate can be between the GFBR and the MFBR. The available bitrate can also be below the GFBR for a QoS Flow with QoS Notification Control enabled without Alternative QoS Profiles.
For the reporting of the available bitrate, periodic reporting is not applied and only threshold-based reporting applies. Based on the PCC rule containing available bitrate as QoS monitoring parameter and Reporting threshold(s) per direction in the QoS Monitoring policy (as described in clause 6.1.3.27.1 of TS 23.503 [45]), the SMF configures the NG-RAN to measure and report the available bitrate by sending QoS monitoring request including the threshold(s). Based on the QoS monitoring request, if the bitrate that NG-RAN is able to provide matches or exceeds indicated Reporting threshold(s), the NG-RAN reports the UL and/or DL available bitrate information of the highest fulfilled threshold to the PSA UPF via the GTP-U header of UL packets.
NOTE 3: The NG-RAN is expected to immediately report the UL and/or DL available bitrate when it matches or exceeds a lower threshold value and report the UL and/or DL available bitrate when it matches or exceeds a higher threshold value with some hysteresis.
The SMF may configure the PSA UPF to perform QoS monitoring for available bitrate as described in clause 5.8.2.18. For the reporting of the available bitrate via the PSA UPF, only event-based reporting applies in the PSA UPF. The Reporting threshold(s) in the PCC rule are not sent to UPF. In UPF, the event for the reporting is the reception of available bitrate information from NG-RAN. According to the QoS Monitoring request for the available bitrate from the SMF, the PSA UPF monitors and exposes the available bitrate information reported from NG-RAN to the target NF as instructed.
During handover, the QoS Monitoring configuration is provided to the Target NG-RAN per QoS Flow in the QoS Monitoring configuration. |
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 operations in the Application layer are specified in clause 6.40 of TS 22.261 [2].
The AF may subscribe to NEF monitoring events as described in clause 4.15.3.2.3 of TS 23.502 [3] in order to assist its application AI/ML operations. For example, the AF may subscribe to session inactivity time monitoring event in order to assist the AI/ML application server in scheduling available UE(s) to participate in the AI/ML operation (e.g. Federated Learning). In addition, the AF may subscribe to NEF to be notified on the traffic volume exchanged between the UE and the AI/ML application server in order to assist the AF with the transfer of AI/ML data.
The AF that aims to provide an AI/ML operation may request assistance from the 5GC as described in clause 5.46.2. The AF initially provides a list of target member UE(s) and at least one filtering criterion, when subscribing to the NEF to be notified about a subset list of UE(s) (i.e. list of candidate UE(s)) that fulfil certain filtering criteria. Details of the procedures are described in clause 4.15.13 of TS 23.502 [3]. This subset list of UE(s) may become the member UE(s) used in the AI/ML operation depending on the AF's final decision, considering its internal logic. Alternatively, the AF may select the list of UEs for the AI/ML operation without NEF involvement as described in Annex I of TS 23.502 [3]: in this case, the AF determines a list of UEs without any assistance from the NEF and may use, for example, NWDAF analytics to assist with the AI/ML operation over 5G System.
The AF may request the network to provide a recommended time window for the AI/ML operation using the Planned Data Transfer with QoS (PDTQ) requirements and procedures as described in clause 6.1.2.7 of TS 23.503 [45] and in clause 4.16.15 of TS 23.502 [3].
At the time or during the AI/ML operation, the AF may request the serving NEF to provide QoS for a list of UEs. Each UE is identified by its UE IP address. The AF may subscribe to QoS Monitoring which may include also Consolidated Data Rate monitoring as described in clause 5.45 and in clause 4.15.6.13 of TS 23.502 [3] for those AF requests for QoS that result in a successful resource allocation. The AF provides QoS parameters that are derived from the performance requirements listed in clause 7.10 of TS 22.261 [2].
As a result of the AF subscription to NEF to provide the subset list of UE(s) that fulfil certain filtering criteria, the AF may be notified about changes in the subset list of UE(s) and in such a case the AF may determine a updated list of UEs used in the AI/ML operation from the new subset list of UE(s) provided by NEF and the AF may request a new recommended time window for the AI/ML operation using the Planned Data Transfer with QoS (PDTQ) requirements as described in clause 6.1.2.7 of TS 23.503 [45] and in clause 4.16.15 of TS 23.502 [3]. The AF may request the NEF to provide QoS for the updated list of UEs, each identified by UE IP address, that results in QoS resources previously allocated to some UEs to be released, while QoS resources for other UEs to be allocated and QoS monitoring to be initiated.
The AF may also subscribe to, or request Network Data Analytics as defined in TS 23.288 [86], such as End-to-end data volume transfer time analytics, DN performance analytics, Network performance analytics, UE mobility analytics, WLAN performance analytics etc. in order to assist its AI/ML operations.
The AF hosting an AI/ML based application may provision the Expected UE Behaviour parameters captured in Table 4.15.6.3-1 of TS 23.502 [3] and/or the Application-Specific Expected UE Behaviour parameter(s) captured in Table 4.15.6.3f-1 of TS 23.502 [3] to the 5GC. The parameters may be provisioned with corresponding confidence and/or accuracy levels and a threshold may also be provided to the UDM by the NF (e.g. AMF or SMF) subscribing to such externally provisioned parameters as described in clause 4.15.6.2 of TS 23.502 [3].
In addition, the following principles apply when 5GS assists the AI/ML operation at the application layer:
- AF requesting 5GS assistance to AI/ML operations in the application layer shall be authorized by the 5GC using the existing mechanisms.
NOTE 2: In this Release, assistance to AI/ML operations in the application layer is not supported for roaming UEs.
NOTE 3: Policy and charging control as defined in TS 23.503 [45] can be used for traffic related to AI/ML operations as described in clause 6.40.1 of TS 22.261 [2]. Capabilities based on Flow Based Charging can be used together with an appropriate PCF configuration for charging differentiation between AI/ML traffic and other type of traffic from the same application. As long as the AF can provide different filter information as described in TS 23.503 [45] for the AI/ML traffic and the other type of traffic from the same application in the procedures utilized for the resource request, the PCF can assign different rating groups (i.e. charging key) or rating group + service-ids based on an appropriate PCF configuration. The UPF will then handle such traffic accordingly. This enables charging of AI/ML traffic according to operator's policies.
- Application AI/ML decisions and their internal operation logic reside at the AF and UE application client and is out of scope of 3GPP.
- Based on application logic, it is the application decision whether to request assistance from 5GC, e.g. for the purpose of selection of Member UEs that participate in certain AI/ML operation.
- In this Release, 5GS assistance to AI/ML operations in the application layer is conducted within a single slice. |
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 shall be hosted by NEF and the features of the Member UE selection assistance functionality hosted by the NEF include (see clause 4.15.13 of TS 23.502 [3] for details of Member UE selection procedures):
- Receiving a request from the AF that shall include a list of target member UE(s) (which may not necessarily be a part of the subsequent updated request), optionally (a) time window(s) and one or more filtering criteria as specified in Table 4.15.13.2-1 of TS 23.502 [3] (e.g. UE current location, UE historical location, UE direction, UE separation distance, QoS requirements, DNN, preferred access/RAT type, Desired end-to-end data volume transfer time performance, or Service Experience).
- Referring to the filtering criteria provided by the AF and then interacting with 5GC NFs using existing services in order to have the corresponding data for all the UEs in the list of target member UE from relevant 5GC NFs (e.g. PCF, NWDAF, AMF, SMF) to derive the list(s) of candidate UE(s) (i.e. UE(s) among the list of target member UE(s) provided by the AF) which fulfil the filtering criteria.
- Providing the AF with the Member UE selection assistance information, including one or more lists of candidate UE(s) and optionally other additional information (e.g. one or more recommended time window(s) for performing the application operation, QoS of each target UE, UE(s) location, Access/RAT type, or Service Experience). NEF may also provide the number of UEs per each filtering criterion that do not fulfil the corresponding filtering criterion.
The Member UE selection assistance information provided by the NEF may be used by the AF to select member UE(s) used in application AI/ML operation. (See clause 5.2.6.32 of TS 23.502 [3] for details of parameters).
NOTE: The AF can decide whether to use the Member UE selection assistance functionality provided by NEF.
Without using the Member UE selection assistance functionality, AF in either trusted or untrusted domain can select the Member UE(s) for e.g. participating in federating learning operation, by collecting the corresponding data using network exposure information as described in clause 4.15 of TS 23.502 [3], e.g. UE location reporting from the AMF, user plane information from the UPF and network data analytics from NWDAF. |
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 enhanced to support the NCR operation:
- The UE Subscription data as defined in clause 5.2.3 of TS 23.502 [3] is enhanced to include the authorization information for the NCR operation;
- During the UE Registration procedure, the AMF is enhanced to perform authorization of the NCR based on subscription information from UDM. The AMF uses Initial UE Context Setup procedure to provide NCR authorization status information to NG-RAN.
- If the authorization status of NCR-MT changes after initial registration, the AMF uses the UE Context Modification procedure to NG-RAN to update the NG-RAN with the new authorization status. |
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 signalling and User Plane traffic related to the PDU sessions established by the UE to some DNN(s) and/or S-NSSAI(s) and/or related to a SUPI range and/or subscription data.
NOTE: This function assumes relevant SLA between the HPLMN of the UE and the target PLMN.
The NF/NF Service discovery and selection mechanisms for serving the UE (all signalling and User Plane traffic) or a PDU session (corresponding SM signalling and User Plane traffic) in the target PLMN makes use of a corresponding Routing Indicator, or SUPI range, or S-NSSAI(s) and DNN(s) as defined in clauses 6.3.1 and 6.3.8 to discover and select a NF/NF Service in the target network. |
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). The MWAB-gNB is based on the gNB functionality specified in TS 38.300 [27] and TS 38.401 [42]. The MWAB may be mounted on a moving vehicle and may serve UEs inside or outside the vehicle.
The MWAB-UE establishes the IP connectivity for the backhaul links for the MWAB-gNB, via NR Uu, using the existing registration procedure and PDU session establishment procedure. The backhaul links are between the MWAB-gNB and entities of the network (e.g. AMF, UPF, other gNBs and OAM server) that a MWAB-gNB cell serves. The IP connectivity provided by the MWAB-UE may be either via the same PLMN/SNPN that the MWAB-gNB serves or a different PLMN/SNPN, depending on the MWAB-UE PLMN selection mechanism as specified in TS 23.122 [17]. Different possible deployment scenarios are presented in Annex S.
NOTE 1: It is assumed that there is no address translation affecting the IP layer of the backhauling interfaces. The entity allocating the IP address (either the BH-SMF or the BH-UPF or an external server) ensures that the IP address is visible on the N6 reference point to the MWAB Broadcasted PLMN, i.e. no NAT is used on the BH-UPF based on the dedicated S-NSSAI(s) and DNN(s) for MWAB operation.
MWAB operation supports both PLMN and SNPN cases. When the MWAB-gNB is serving a PLMN, the UEs served by MWAB may be non-roaming or roaming in the MWAB Broadcasted PLMN. In case the MWAB-gNB is serving a SNPN, the subscribed SNPN of the UEs may be different from the MWAB Announced SNPN. The UEs served by the MWAB are not aware of the network serving the MWAB-UE.
Figure 5.49.1.1-1: MWAB architecture for 5GS
NOTE 2: In this Release, the CU/DU split of the MWAB-gNB is not supported.
NOTE 3: The interface between MWAB-UE and MWAB-gNB is implementation based and not in scope of this specification.
MWAB-UE has a single NR Uu hop to the BH NG-RAN, using either TN or NTN access technology. The NR Uu access link between the MWAB-gNB and the served UE(s) does not use NTN access technology. 5G MOCN can be supported by the MWAB-gNB.
The details of the MWAB configuration/provisioning process are described in clause 5.49.2.
In order to operate as MWAB, the MWAB-gNB component and MWAB-UE component are authorized and controlled separately. The detailed procedures for the authorization of MWAB are described in clause 5.49.3.
When UE(s) are served by MWAB, the MWAB-gNB provides additional User Location Information to the 5GC as described in clause 5.49.4.
Service continuity for the UE(s) served by the MWAB-gNB is supported when the MWAB moves. The UE(s) move or do not move together with the MWAB. The detailed procedures for the support of mobility are described in clause 5.49.5.
The MWAB shall be able to serve UE(s) without any MWAB-specific enhancements. For some operations, the MWAB may be configured to provide access only to certain UEs. Existing access control mechanisms, e.g. CAG control, can be used to manage the UE(s)'s access to the MWAB-gNB. The details of the access control for the UEs served by MWAB are described in clause 5.49.6.
The LCS framework as defined in TS 23.273 [87] is used for providing the location service to the UE(s) served by MWAB. When the AMF determines the UE is served by a MWAB cell based on e.g. the Additional ULI, the AMF selects the LMF that can support the MWAB handling and sends MWAB indication and Additional ULI (if available) to the LMF as defined in clause 8.3.2.2 of TS 23.273 [87]. Details on supporting the LCS over MWAB are described in clause 5.49.7.
Regulatory services (e.g. emergency services, priority services) can be supported by the MWAB and the details are provided in clause 5.49.8.
Details on MWAB-gNB's Xn connection are specified in TS 38.401 [42]. |
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 implementation based internal communication between the MWAB-gNB and the MWAB-UE.
The MWAB-UE establishes, modifies BH PDU Sessions based on the received traffic descriptors from MWAB-gNB, configured URSP rules, and local configuration.
NOTE: The MWAB-gNB, acting as upper layer of the MWAB-UE described in TS 24.526 [110], can categorize the traffic in different ways (e.g. based on different interfaces Xn/N2/N3/OAM, or nature of the traffic (control signalling vs user plane traffic), or slices supported by the MWAB-gNB) and provides corresponding traffic descriptors to MWAB-UE. The internal communication details between MWAB-gNB and MWAB-UE is outside the scope of this specification. For slice information based categorization, see clause 5.49.1.4. |
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 identified by the MWAB-gNB based on the QoS information of the PDU Session(s) in the UE contexts of the MWAB-gNB and/or based on OAM configuration) via implementation-based internal communication between MWAB-gNB and MWAB-UE.
Based on configuration and traffic mapping specified in TS 38.414 [195] and clause 5.7.1.5, the MWAB-gNB (in the Uplink direction) and the UPFs (in the Downlink direction) in the MWAB Broadcasted PLMN/SNPN set proper marking information (DSCP) for the N3 GTP-U traffic for the UE(s) served by the MWAB-gNB. When Xn is supported for MWAB, based on TS 38.401 [42], the MWAB-gNB and its neighbour NG-RAN node set proper DSCP for the Xn-U traffic based on OAM configurations, as defined in TS 38.424 [217]. The MWAB gNB additionally marks the DSCP value based on configuration for N2, Xn-C and OAM traffic it sources, i.e. not related to PDU Sessions(s) of the UE.
The MWAB-gNB provides the information to the MWAB-UE for the mapping of DSCP values used for N3 traffic and Xn traffic in the MWAB Broadcasted PLMN/SNPN to QoS flows to be used in the BH PLMN/SNPN (including the required Packet Filter Set for filtering of packets) and the corresponding QoS requirements (e.g. QoS Flow level parameters including e.g. 5QI). The MWAB-UE then initiates PDU session establishment or modification procedure to establish or update the BH PDU session(s) for N3 traffic and Xn traffic delivery based on the received information.
Based on the information provided by the MWAB-gNB and received during the PDU session establishment/modification, the MWAB-UE processes the UL N3 traffic and Xn traffic as described in clause 5.7.1.7. The BH UPF processes the DL N3 traffic and Xn traffic as described in clause 5.7.1.6.
The MWAB-UE may indicate to the MWAB-gNB the current BH PDU Session's QoS Flow level QoS parameters, e.g. for admission control of the QoS-Flows of the UEs served by the MWAB. |
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-NSSAI to default traffic descriptors for the selection of BH PDU Session(s) for the related N2 and/or N3 backhauling. The MWAB-gNB requests the BH PDU sessions as specified in clause 5.49.1.2.
When the MWAB-gNB obtains the S-NSSAI of a UE PDU Sessions from the UE PDU session context during PDU session establishment, it checks whether a configured association exists for the S-NSSAI of the PDU session of the UE and, if so, it uses the related BH PDU session for the UE's PDU Session.
If a new BH PDU Session needs to be established for supporting a UE's traffic for a S-NSSAI in the MWAB-Broadcasted PLMN/SNPN, after the completion of the PDU session establishment procedure, the MWAB-UE may trigger a PDU session resource modification procedure to shift the N3 traffic for the UE to the new BH PDU sessions.
NOTE: Due to the limitation of the maximum number of PDU sessions supported by a UE, it is expected that there can only be a small number of dedicated BH PDU sessions for specific S-NSSAI(s) in the MWAB-broadcasted PLMN. |
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, S-NSSAI, the SSC Mode, etc. The URSP rules can be preconfigured or provisioned to the MWAB-UE by its HPLMN using UE Policy delivery as described in clause 4.2.4.3 of TS 23.502 [3]. |
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 specified in TS 38.401 [42], e.g. for the purpose including the access stratum operation of the MWAB-gNB, the N2, N3 and Xn interface management, activating/deactivating the MWAB-gNB operation and to assist the MWAB-gNB providing information used by MWAB-UE for the BH PDU Session(s) management via URSP processing.
NOTE 1: It is expected the OAM of the MWAB Broadcasted PLMN/SNPN is aware of location in which the MWAB operation can be authorized and also can obtain MWAB's current location. Only when the MWAB is authorized successfully, the configuration information can be provisioned to the MWAB-gNB. Alternatively, the OAM can also provision configuration parameters related to different areas, as defined in TS 38.401 [42].
The MWAB-gNB shall be configured with the supported S-NSSAI(s) in the MWAB Broadcasted PLMN/SNPN.
NOTE 2: A MWAB-gNB is not expected to be configured to support any dedicated S-NSSAI for BH PDU Session(s) used by MWAB-UEs for MWAB operation in the MWAB Broadcasted PLMN/SNPN as specified in TS 38.401 [42]. The support at a MWAB-gNB of S-NSSAIs dedicated to MWAB-UE BH PDU Session(s) in the MWAB Broadcasted PLMN/SNPN would mean that the MWAB-gNB could support serving the MWAB-UEs BH-PDU Session(s) in the broadcasted PLMN/SNPN. |
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 establish connectivity in a BH PLMN/SNPN is based on whether dedicated S-NSSAI(s) for MWAB operations are received as part of Allowed NSSAI in BH PLMN/SNPN following existing procedures as described in clause 5.15 and whether it can establish BH PDU session(s) in the BH PLMN/SNPN using the dedicated S-NSSAI(s) and DNN(s).
The MWAB-UE authorization supports time-based or location-based control.
- For time-based control, existing time-based network slice subscription control can be reused (including the enhancements in clause 5.15.16).
- For location-based control, existing mechanism, e.g. service area restriction, LADN based control (see e.g. clauses 5.6.5 and 5.6.5a) can be reused.
NOTE 1: When the MWAB-UE can no longer use S-NSSAI(s) dedicated to MWAB operation,, e.g. the dedicated S-NSSAIs and DNNs for MWAB operation are removed from the subscription (i.e. the MWAB becomes unauthorized) and a UE subscription update (including a UE configuration update) step happens, or the MWAB-UE moves to an area where the S-NSSAI is not available, if the AMF is configured to do so for the dedicated S-NSSAI and DNN for MWAB operation, the AMF delays the corresponding PDU session release based on an operator configuration (e.g. a local configured timer to allow time for the MWAB-gNB to handover the UE(s) it serves to other cells).
NOTE 2: If the S-NSSAI(s) used by BH PLMN for MWAB operation is not dedicated for MWAB, the behaviours of AMF as in NOTE 1 cannot be limited to MWAB-UEs only. Additionally, it may also not be possible to configure specific treatment for MWAB-UEs (different from other UEs) in the NG-RAN.
The MWAB-UE may be connected to the BH PLMN/SNPN for other services, if allowed by the subscription data, even if the S-NSSAIs and DNNs for Backhaul PDU sessions are no longer authorized. |
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 OAM of the MWAB Broadcasted PLMN/SNPN determines when/where the MWAB-gNB can operate or when/where it needs to shut down. The OAM of the MWAB Broadcasted PLMN/SNPN may pre-configure the MWAB-gNB to turn on/shut down the operations of respective MWAB Broadcasted PLMN/SNPN part. When the MWAB-gNB is no longer authorized to operate by OAM of the MWAB Broadcasted PLMN/SNPN, the MWAB-gNB should handover the UE(s) of the MWAB Broadcasted PLMN/SNPN to other cells.
NOTE: It is expected the HPLMN/Subscribed SNPN network ensures that the BH PDU sessions authorization for MWAB UE does not interfere with the ability of the OAM of the MWAB Broadcasted PLMN/SNPN to manage the MWAB-gNB, e.g. the S-NSSAI(s) for the BH PDU session(s) of the MWAB-UE is(are) maintained long enough in the MWAB-UE subscription and are available for the MWAB-UE for a location and time that is sufficient for the MWAB-UE, so that the BH PDU sessions are available for the MWAB-gNB to be able to perform OAM-controlled shut down, which may include handing over the UEs it serves.
When the MWAB-gNB stops operating under OAM control, the MWAB-gNB may trigger the MWAB-UE to release the BH PDU sessions. |
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 provide the Additional User Location Information (Additional ULI) that reflects the location of the MWAB-UE to the AMF when it sends the User Location Information (ULI) over N2 messages. In the Additional ULI, the MWAB-gNB provides the TAI/NR CGI of the MWAB Broadcasted PLMN/SNPN with which the UE is registered as specified in TS 38.401 [42].
NOTE: For the case of MWAB broadcasted PLMN/SNPN being different from the BH PLMN, MWAB-gNB formulates the Additional ULI as specified in TS 38.401 [42] based on MWABs geo-location. The MWAB can determine its geo-location using GNSS or via a MWAB-UE initiated 5GC-MO-LR procedures as specified in TS 23.273 [87]. If the MWAB broadcasted PLMN/SNPN is the same as the BH PLMN, then the TAI/NR CGI of the cell serving the MWAB-UE is included in the Additional ULI as specified in TS 38.401 [42].
If serving cell change report is required by AMF as specified in clause 4.10 of TS 23.502 [3], the MWAB-gNB shall report Additional ULI (and ULI) for the UE even when only serving cell of the MWAB-UE changes.
The AMF may consider the 'Additional ULI' when it determines UE location and manages the UE location related functions (e.g. Mobility Restrictions).
Based on operator policy, the AMF may send the Additional ULI when the AMF provides user location information it has received over the N2 interface to a NF (e.g. the LMF as specified in clause 5.19.1 of TS 23.273 [87]). |
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) selection as specified in TS 38.304 [50] and TS 23.122 [17] for RRC_IDLE and RRC_INACTIVE is used irrespective of cells are belonging to a MWAB-gNB or a gNB.
- For UEs in RRC_CONNECTED state, the MWAB-gNB or gNB triggers the handover procedures to the neighbouring cells as specified in TS 38.300 [27] and TS 23.502 [3] irrespective of whether the cells are belonging to a MWAB-gNB or a gNB. |
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] from the OAM server of MWAB Broadcasted PLMN/SNPN and, if any new AMF was provided as part of the new configuration, the MWAB-gNB (i.e. new logical gNB as specified in TS 38.401 [42]) sets up the N2 connection with the new AMF and it (i.e. old logical gNB as specified in TS 38.401 [42]) releases the N2 connection with any old AMF removed from the MWAB-gNB configuration.
NOTE: It is expected the MWAB-gNB removes the old configuration after the MWAB-gNB has completed the handover of the UEs in RRC_CONNECTED state.
- The MWAB-UE may request new or modify existing BH PDU Sessions for the corresponding N2, N3 and Xn interfaces, upon request from the MWAB-gNB as it moves in the network and the MWAB-gNB updates the TNL association as specified in clause 5.21.1 and TS 38.401 [42] to use the new TNL information associated with the new BH PDU Session(s) as needed.
- SSC mode 3 may be applied to the BH PDU Sessions to minimize traffic interruption when UPF re-allocation for these BH PDU Sessions is required during the MWAB mobility.
- When it is required to change AMF for the UEs served by the MWAB-gNB upon mobility of a MWAB into a new region, the TAC(s) and Cell ID(s) the MWAB-gNB announces also change. The MWAB-gNB, for UEs in RRC_CONNECTED mode, behaves as specified in TS 38.401 [42].
- To prevent handover of a MWAB-UE towards a target MWAB-gNB, the target MWAB-gNB (i.e. during Xn handover or during N2 HO after target AMF slice control as described in step 4 in clause 4.9.1.3.2 of TS 23.502 [3]) fails the handover as specified in TS 38.401 [42] because the dedicated slices for BH PDU sessions of the MWAB-UE are not supported by the target MWAB-gNB. |
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 Tracking Area, UAC, to manage the UE's access to an MWAB-gNB cell.
NOTE: MWAB-UE's access to the network is controlled with mechanisms defined in clause 5.2 for PLMN and clauses 5.30.2 and 5.30.3 for SNPN/PNI-NPN, based on subscription data of the MWAB-UE. It is not addressed in this clause. |
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 configured either during the communication with the OAM of MWAB-gNB or (pre-)configuration mechanism, with one or more CAG identifiers which are unique within the scope of this PLMN.
- If the MWAB-gNB is (pre-)configured with the PLMN list supporting PNI-NPN, the corresponding CAG Identifiers per PLMN is also configured in the MWAB.
- The MWAB-gNB performs UE access control based on the CAG identifier associated with the MWAB-gNB cell, as defined in clause 5.30.3.4. The MWAB-gNB takes the role of the NG-RAN.
NOTE: In the case of UE not supporting CAG functionality, the MWAB-gNB and 5GC of MWAB Broadcasted PLMN can use other existing mechanisms e.g. forbidden Tracking Area, to manage UE's access to a MWAB-gNB cell.
- Time validity information may be provided to the UE together with the CAG Identifier(s) of the MWAB-gNB(s) that the UE can access. If the evaluation of the time validity information of an entry in the Allowed CAG list changes, the updated Allowed CAG list will be provided to UE and MWAB-gNB by the AMF for enforcement, to make sure that UE not accessing the corresponding MWAB-gNB cell outside of the time duration.
Dedicated CAG ID(s) can be used for the control of UE access to a PNI-NPN via MWAB cells. |
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 fixed gNBs. |
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:
- If the HPLMN of MWAB-UE has configured it with specific S-NSSAI and DNN for BH PDU Session(s) to serve emergency PDU Session for UEs accessing this MWAB, the MWAB uses a BH PDU Session associated with this specific S-NSSAI and DNN. The MWAB-UE establishes such PDU session if it was not yet established.
- If a new BH PDU sessions using this specific S-NSSAI and DNN is established, the emergency PDU Session establishment procedure for the UE(s) served by the MWAB-gNB should not be interrupted by the establishment of the new BH PDU Session. To avoid interruption of the establishment of the emergency PDU Sessions of the UE(s) served by the MWAB-gNB, the MWAB-gNB should complete the emergency PDU Session establishment by using the existing BH PDU Sessions for N3 traffic and then trigger PDU Session resource modification procedure for the emergency PDU Sessions of the UE(s) to associate the emergency PDU Session N3 interface to the new BH PDU Session to serve emergency PDU Session for UEs accessing this MWAB.
- If the HPLMN of MWAB-UE has not configured the MWAB-UE with specific S-NSSAI and DNN for BH PDU Session(s) to serve emergency PDU Session(s) for UEs accessing this MWAB, the MWAB reuses the existing BH PDU Session(s) for N2/N3 interface.
- If there are UEs with emergency services, the MWAB-gNB will not stop operating (e.g. due to de-authorization) as MWAB until it handovers the UEs to other cells as described in clause 5.49.3.
- Based on configuration for the specific S-NSSAI and DNN for BH PDU Session to serve emergency PDU Sessions, the BH PLMN/SNPN and the MWAB attempt to guarantee the resources of the BH PDU session(s) to serve emergency PDU Session in the BH PLMN/SNPN so that they are not released when MWAB is serving the emergency services.
NOTE: If the MWAB is configured to support emergency services for the UEs it serves, it is assumed that the MWAB Broadcasted PLMN/SNPN and BH PLMN/SNPN are in the same country. |
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 the NR Femto cell, the existing CAG concept defined in the clause 5.30.3 for PNI-NPN is used. The Femto cell may broadcast one or multiple CAG Identifiers as specified in the clause 5.30.3 if access control is needed.
The CAG owner or an authorized administrator may control/provision subscribers to allow accessing their NR Femto/CAG cells as described in clause 5.50.3.
An NR Femto Hosting Party plays the role of a CAG owner. |
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) as an AMF. The N2 and N3 interface between the NR Femto node(s) and the 5GC is the same, regardless whether the NR Femto node(s) is(are) connected to the 5GC via an NR Femto GW or not.
In a deployment with a locally deployed UPF close to the location of NR Femto node(s), the edge computing functionality specified in clause 5.13 can be applied. |
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 case.
NOTE: The CAG information provisioned by AF can only be used for UE's allowed CAG list for HPLMN. |
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 consumer NF(s) (AF/NEF or 5GC NF).
Procedures for energy consumption information collection and exposure are defined in clause 4.29 of TS 23.502 [3]. |
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 consumption is collected PLMN-wide at a configurable starting time with interval T such that the Energy Consumption information reported to the EIF is time-aligned.
NOTE: If the reported Energy Consumption information is not time-aligned, it cannot be aggregated. |
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 Identifier, or Packet Filters)) to retrieve the information from SMF, which is shown in Table 5.51.2.2.2-1. The SMF receives the data volume of the required granularities from the PSA UPF. The SMF then sends the collected data volume, along with the serving gNB ID(s) and (I-)UPF ID(s) to EIF for energy consumption calculation. And the information collected from SMF by EIF, is shown in Table 5.51.2.2.2-2.
Table 5.51.2.2.2-1: Information to SMF for user-plane energy consumption calculation
Information
Description
UE ID
SUPI.
S-NSSAI +DNN
Slice and DNN applicable to a PDU session.
IP 5-Tuple
IP-5-tuple.
NOTE 1: The user-plane energy consumption information reporting interval from the SMFs is the PLMN-wide configurable starting time and interval T.
Table 5.51.2.2.2-2: Information from SMF for user-plane energy consumption calculation
Information
Description
UE IP address
UE IP address.
UE ID
SUPI.
S-NSSAI
Network Slice applicable to a UE
S-NSSAI +DNN
Slice and DNN applicable to a PDU session.
Packet Filters
Packet Filters as in clause 5.7.6 for IP or Ethernet traffic.
Application Identifier
Identification for the traffic of the service data flow.
List of Data Volume information
The data volume and the associated UPF(s) and gNB(s) serving the UE within the time interval.
> UL/DL Data Volume
The UL/DL Data Volume of a PDU Session identified by (UE-ID, S-NSSAI/DNN) or a Service Data flow (UE ID, S-NSSAI, DNN, Packet Filters/Application Identifier).
> (I-)UPF ID(s)
Identifier of any (I-)UPF(s) associated to a reported data volume used by a PDU Session identified by (UE-ID, S-NSSAI/DNN) or a Service Data flow (UE ID, S-NSSAI, DNN, Packet Filters/Application Identifier).
> gNB ID
Identifier of the gNB serving the UE.
Reference to Time Interval
Indicate the time interval of the collected information (e.g. time stamps).
NOTE 2: Each entry of List of Data Volume information represents the serving gNB and UPF(s) corresponding to the same Data Volume regarding the required granularities. A new entry is added when the gNB or UPF(s) is changed. |
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 and interval T which is the same as data volume reporting interval from SMFs.
Table 5.51.2.2.2-1: Information from OAM for user-plane energy consumption calculation
Information
Description
gNB energy consumption
The Energy consumed by a gNB over the configured time interval T based on clause 6.7.3.4.2 of TS 28.554 [209].
gNB data volume
The UL/DL data volume handled by a gNB over the configured time interval T based on clause 6.7.1.1 of TS 28.554 [209].
UPF energy consumption
The Energy consumed by a UPF over the configure time interval T based on clause 6.7.3.1 of TS 28.554 [209].
UPF data volume
Data volume consumed at a UPF.
When the serving gNB and/or the (I-)UPF(s) of the UE are changed, the serving gNB ID and UPF ID will be updated to the EIF through SMF(s).
NOTE 1: The Node-level Energy Consumption information received from OAM could be used by EIF for all the UEs serving by the NF Node.
NOTE 2: In this Release, only the energy related information of user plane communication is supported and that of control plane signalling is not supported.
The EIF acts as the enforcement point for user consent for collection and processing of energy-related information depending on local regulations. For support of user consent (for collection and processing of energy-related information), the EIF communicates with the UDM as specified in Annex V of TS 33.501 [29]. |
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.
- For PDU session level exposure, the consumer NF provides UE ID (SUPI/GPSI), DNN/S-NSSAI.
- For Service Data Flow level exposure (e.g. per UE per application), the consumer NF provides UE ID (SUPI/GPSI), DNN/S-NSSAI and application information, e.g. Application Identifier, or Flow description(s).
The consumer NF may also subscribe the above information exposure with providing reporting period, reporting frequency. If the consumer NF is AF/NEF, it may subscribe the Energy consumption information exposure of required granularity and may provide reporting threshold for the required granularity and the reporting time period.
NOTE: For the threshold-based reporting, the EIF sends the Energy consumption information of the required granularity to the NEF/AF once when the Energy consumption information of the required granularity matches or exceeds the threshold during the reporting time period.
Editor's note: Whether and how the renewable energy is introduced is FFS and depending on SA WG5. |
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 the AF. |
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 mapping of the Energy Saving Indicator values to the respective behaviour are operator-defined and outside the scope of this specification. The AMF receives the Energy Saving indicator in the UE Subscription data. The AMF forwards the Energy Saving indicator to the NG-RAN and to the PCF.
Editor's note: Whether the indicator is provided to the NG-RAN and how it is used in the NG-RAN is FFS. |
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 policy decisions for the UE based on the operator policy as described in clause 6.1.2.1.1 of TS 23.503 [45]. |
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 traffic for non-3GPP devices connecting behind a 5G-RG is specified in TS 23.316 [84].
The Non-3GPP Device Identifier is unique within the scope of the UE's SUPI.
In this Release of the specification, QoS differentiation for non-3GPP device connecting behind a UE is not supported in LBO roaming scenario. |
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 same UE.
NOTE 1: How the UE identifies the non-3GPP device and binds the Non-3GPP Device Identifier to a non-3GPP device is implementation specific. How the Non-3GPP Device Identifier(s) that are associated with the UE's SUPI in the 5GC are known to the UE is implementation specific.
NOTE 2: At any point in time the Non-3GPP Device Identifier can be bound to only one non-3GPP device.
Non-3GPP Device Identifier Information is stored in the UDR and includes a Non-3GPP Device Identifier and QoS Information. The content of the Non-3GPP Device Identifier Information is further described in clause 4.15.6.15 of TS 23.502 [3]. |
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. The SMF forwards the Non-3GPP Device Connection Information to the PCF for policy control.
NOTE 1: It is up to UE implementation to determine when to initiate PDU Session Modification procedure for updating the Non-3GPP Device Connection Information.
For an Ethernet PDU Session, the Non-3GPP Device Connection Information includes:
- Non-3GPP Device Identifier;
- MAC address used in PDU session;
- Optionally, VLAN tag ID that is associated with the non-3GPP device used in PDU session.
For an IPv4 or IPv4v6 PDU Session, the Non-3GPP Device Connection Information includes:
- Non-3GPP Device Identifier;
- IPv4 Address associated with the non-3GPP device used in PDU session;
- Optionally, port ranges associated with the non-3GPP device used in PDU session.
For an IPv6 or IPv4v6 PDU Session, the Non-3GPP Device Connection Information includes:
- Non-3GPP Device Identifier;
- IPv6 Address/prefix(sub) associated with the non-3GPP device used in PDU session;
- Optionally, port ranges associated with the non-3GPP device used in PDU session.
NOTE 2: If IPv4v6 PDU Session is applied, it is up to UE implementation to determine to use IPv4 or IPv6 or both Address/prefix(sub) based on the associated traffic of the non-3GPP device and the IP allocation by the network to the PDU Session.
Editor's note: The detailed encoding of Non-3GPP Device Connection Information will be defined in stage-3.
If the PCF indicates to the SMF that the corresponding Non-3GPP Device Identifier is not available for the UE as specified in clause 6.1.3.31 of TS 23.503 [45], the SMF rejects the PDU Session Modification with a cause code to notify the UE that the Non-3GPP Device Identifier is not available for the UE. |
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 33.501 [29] and TS 33.535 [124].
5G Media streaming functions are described in TS 26.501 [135]. |
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.
- Connection management.
- Reachability management.
- Mobility Management.
- Lawful intercept (for AMF events and interface to LI System).
- Provide transport for SM messages between UE and SMF.
- Transparent proxy for routing SM messages.
- Access Authentication.
- Access Authorization.
- Provide transport for SMS messages between UE and SMSF.
- Security Anchor Functionality (SEAF) as specified in TS 33.501 [29].
- Location Services management for regulatory services.
- Provide transport for Location Services messages between UE and LMF as well as between RAN and LMF.
- EPS Bearer ID allocation for interworking with EPS.
- UE mobility event notification.
- S-NSSAIs per TA mapping notification.
- Support for Control Plane CIoT 5GS Optimisation.
- Support for User Plane CIoT 5GS Optimisation.
- Support for restriction of use of Enhanced Coverage.
- Provisioning of external parameters (Expected UE Behaviour parameters or Network Configuration parameters).
- Support for Network Slice-Specific Authentication and Authorization.
- Support for charging.
- Controlling the 5G access stratum-based time distribution based on UE's subscription data.
- Controlling the gNB's time synchronization status reporting and subscription.
NOTE 1: Regardless of the number of Network functions, there is only one NAS interface instance per access network between the UE and the CN, terminated at one of the Network functions that implements at least NAS security and Mobility Management.
In addition to the functionalities of the AMF described above, the AMF may include the following functionality to support non-3GPP access networks:
- Support of N2 interface with N3IWF/TNGF. Over this interface, some information (e.g. 3GPP Cell Identification) and procedures (e.g. Handover related) defined over 3GPP access may not apply and non-3GPP access specific information may be applied that do not apply to 3GPP accesses.
- Support of NAS signalling with a UE over N3IWF/TNGF. Some procedures supported by NAS signalling over 3GPP access may be not applicable to untrusted non-3GPP (e.g. Paging) access.
- Support of authentication of UEs connected over N3IWF/TNGF.
- Management of mobility, authentication and separate security context state(s) of a UE connected via a non-3GPP access or connected via a 3GPP access and a non-3GPP access simultaneously.
- Support as described in clause 5.3.2.3 a co-ordinated RM management context valid over a 3GPP access and a Non 3GPP access.
- Support as described in clause 5.3.3.4 dedicated CM management contexts for the UE for connectivity over non-3GPP access.
- Determine whether the serving N3IWF/TNGF is appropriate based on the slices supported by the N3IWFs/TNGFs as specified in clause 6.3.6 and clause 6.3.12 respectively.
NOTE 2: Not all of the functionalities are required to be supported in an instance of a Network Slice.
In addition to the functionalities of the AMF described above, the AMF may include policy related functionalities as described in clause 6.2.8 of TS 23.503 [45].
The AMF uses the N14 interface for AMF re-allocation and AMF to AMF information transfer. This interface may be either intra-PLMN or inter-PLMN (e.g. in the case of inter-PLMN mobility).
In addition to the functionality of the AMF described above, the AMF may include the following functionality to support monitoring in roaming scenarios:
- Normalization of reports according to roaming agreements between VPLMN and HPLMN (e.g. change the location granularity in a report from cell level to a level that is appropriate for the HPLMN); and
- Generation of charging/accounting information for Monitoring Event Reports that are sent to the HPLMN.
In addition to the functionality of the AMF described above, the AMF may provide support for AMF overload control, Network Slice restriction and Network Slice instance restriction based on NWDAF analytics.
In addition to the functionalities of the AMF described above, the AMF may provide support for the Disaster Roaming as described in clause 5.40.
In addition to the functionalities of the AMF described above, the AMF may also include following functionalities to support Network Slice Admission Control:
- Support of NSAC for maximum number of UEs as defined in clauses 5.15.11.1 and 5.15.11.3.
In addition to the functionality of the AMF described above, the AMF may include the following functionality to support SNPNs:
- Support for Onboarding of UEs for SNPNs.
In addition to the functionalities of the AMF described above, the AMF may also include following functionalities to support satellite backhaul:
- Support for reporting satellite backhaul category and its modification based on AMF local configuration to SMF as defined in clause 5.43.4.
In addition to the functionalities of the AMF described above, the AMF may also include following functionalities for regenerative-based satellite access:
- Support for NG Removal procedure defined in TS 38.413 [34].
In addition to the functionalities of the AMF described above, the AMF may also include following functionalities to support UE-Satellite-UE communication:
- Support for reporting to SMF the UE's serving satellite identifier and its change as defined in clause 5.4.14.
In addition to the functionalities of the AMF described above, the AMF may provide support for Network Slice instance change for PDU sessions as defined in clause 5.15.5.3.
In addition to the functionalities of the AMF described above, the AMF may also support functionalities for Partial Network Slice support in a Registration Area as described in clause 5.15.17.
In addition to the functionalities of the AMF described above, the AMF may also include functionalities to support NS-AoS not matching deployed Tracking Areas as described in clause 5.15.18.
In addition to the functionalities of the AMF described above, the AMF may also include functionalities to support Network Slice Replacement as described in clause 5.15.19.
In addition to the functionalities of the AMF described above, the AMF may also include functionalities to enforce the LADN Service Area per LADN DNN and S-NSSAI for a UE as described in clause 5.6.5a, as well as to enforce the LADN Service Area per LADN DNN for a UE in clause 5.6.5.
In addition to the functionalities of the AMF described above, the AMF may also include following functionalities to support Indirect Network Sharing:
- Support for selecting the SMF of participating operator (H-SMF) possibly considering the relevant UE location information as specified in clause 6.3.2.
- Support for Network Slicing handling considering what is described in clause 5.18.5.
NOTE 3: The AMF of hosting operator can identify the UE's participating operator (i.e. in the case of Indirect Network Sharing) during the registration procedure based on internal implementation and then the H-SMF selection can be performed considering the relevant UE location information.
In addition to the functionalities of the AMF described above, the AMF may also include following functionalities to support Local Offloading Management as specified in clause 5.34.11:
- Support to decide the insertion or removal of I-SMF to support Local Offloading Management based on SMF selection subscription data, the current UE location, SMF service area and local offloading management service area.
In addition to the functionalities of the AMF described above, the AMF may provide support for energy related features as described in clause 5.51. |
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 & management (including optional Authorization). The UE IP address may be received from a UPF or from an external data network.
- DHCPv4 (server and client) and DHCPv6 (server and client) functions.
- Functionality to respond to Address Resolution Protocol (ARP) requests and / or IPv6 Neighbour Solicitation requests based on local cache information for the Ethernet PDUs. The SMF responds to the ARP and / or the IPv6 Neighbour Solicitation Request by providing the MAC address corresponding to the IP address sent in the request.
- Selection and control of UP function, including controlling the UPF to proxy ARP or IPv6 Neighbour Discovery, or to forward all ARP/IPv6 Neighbour Solicitation traffic to the SMF, for Ethernet PDU Sessions.
- Configures traffic steering at UPF to route traffic to proper destination.
- 5G VN group management, e.g. maintain the topology of the involved PSA UPFs, establish and release the N19 tunnels between PSA UPFs, configure traffic forwarding at UPF to apply local switching, N6-based forwarding or N19-based forwarding, manage traffic forwarding in the case that a SMF Set or multiple SMF Sets are serving a 5G VN.
- Termination of interfaces towards Policy control functions.
- Lawful intercept (for SM events and interface to LI System).
- Support for charging.
- Control and coordination of charging data collection at UPF.
- Termination of SM parts of NAS messages.
- Downlink Data Notification.
- Initiator of AN specific SM information, sent via AMF over N2 to AN.
- Determine SSC mode of a session.
- Support for Control Plane CIoT 5GS Optimisation.
- Support of header compression.
- Act as I-SMF in deployments where I-SMF can be inserted, removed and relocated.
- Provisioning of external parameters (Expected UE Behaviour parameters or Network Configuration parameters).
- Support P-CSCF discovery for IMS services.
- Act as V-SMF with following roaming functionalities:
- Handle local enforcement to apply QoS SLAs (VPLMN).
- Charging (VPLMN).
- Lawful intercept (in VPLMN for SM events and interface to LI System).
- Support for interaction with external DN for transport of signalling for PDU Session authentication/authorization by external DN.
- Instructs UPF and NG-RAN to perform redundant transmission on N3/N9 interfaces.
- Generation of the TSC Assistance Information based on the TSC Assistance Container received from the PCF.
- Support for RAN feedback for BAT offset and adjusted periodicity as defined in clause 5.27.2.5.
NOTE 1: Not all of the functionalities are required to be supported in an instance of a Network Slice.
In addition to the functionalities of the SMF described above, the SMF may include policy related functionalities as described in clause 6.2.2 of TS 23.503 [45].
In addition to the functionality of the SMF described above, the SMF may include the following functionality to support monitoring in roaming scenarios:
- Normalization of reports according to roaming agreements between VPLMN and HPLMN; and
- Generation of charging information for Monitoring Event Reports that are sent to the HPLMN.
The SMF may also include following functionalities to support Edge Computing enhancements (further defined in TS 23.548 [130]):
- Selection of EASDF, obtain and/or provision DNS security information of the EASDF and provision of its address to the UE as the DNS Server for the PDU session;
- Usage of EASDF services as defined in TS 23.548 [130];
- For supporting the Application Layer Architecture defined in TS 23.558 [134]: Provision and updates of ECS Address Configuration Information to the UE;
- For supporting the HR-SBO as defined in clause 6.7 of TS 23.548 [130].
- For supporting Local Offloading Management as defined in clause 6.10 of TS 23.548 [130].
NOTE 2: In case an I-SMF is inserted to locally manage edge computing related information and the traffic is locally offloaded, only the I-SMF performs the EASDF selection and uses the EASDF services for the locally offloaded PDU sessions.
- For supporting the N6 delay measurement as described in clause 5.8.2.23.
- Based on N6 delay measurements and user plane latency (between the 5G AN and candidate UPF(s)):
- Supporting the (re)selection of local PSA UPF as defined in clause 6.2.3.2 of TS 23.548 [130].
- Supporting to trigger (re)discovery of EAS(es) as defined in clause 6.2.3.2 of TS 23.548 [130].
The SMF and SMF+ PGW-C may also include following functionalities to support Network Slice Admission Control:
- Support of NSAC for maximum number of PDU sessions as defined in clauses 5.15.11.2, 5.15.11.3 and 5.15.11.5.
- Support of NSAC for maximum number of UEs as defined in clauses 5.15.11.3 and 5.15.11.5.
The SMF may also include following functionalities:
- Providing per-QoS flow Non-3GPP QoS assistance information to the UE (e.g. PEGC) and formulation of the CN PDB based on non-3GPP delay budget from UE (e.g. PEGC) as described in clause 5.44.3.4.
- Support of PDU Set based handling as described in clause 5.37.5.
In addition to the functionalities of the SMF described above, the SMF may also include functionalities to support Network Slice Replacement as described in clause 5.15.19.
The SMF may also include functionalities to support indirect UPF event exposure service subscription on behalf of the consumer NF(s) as described in clause 4.15.4.5 of TS 23.502 [3].
In addition to the functionality of the SMF described above, the SMF may provide support for SMF overload control based on NWDAF analytics.
In addition to the functionality of the SMF described above, the SMF may provide support for energy related features as described in clause 5.51.
In addition to the functionality of the SMF described above, the SMF may include the following functionality to support communication via satellite access and/or satellite backhaul:
- Support for reporting satellite backhaul category and its modification to PCF as described in clause 5.43.4.
- Support for reporting to PCF the UE's serving satellite identifier and its change as defined in clause 5.4.14. |
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 Session point of interconnect to Data Network.
- Packet routing & forwarding (e.g. support of Uplink classifier to route traffic flows to an instance of a data network, support of Branching point to support multi-homed PDU Session, support of traffic forwarding within a 5G VN group (UPF local switching, via N6, via N19)).
- Packet inspection (e.g. Application detection based on service data flow template and the optional PFDs received from the SMF in addition, IP or MAC filter-based packet detection functionality).
- User Plane part of policy rule enforcement, e.g. Gating, Redirection, Traffic steering).
- Lawful intercept (UP collection).
- Traffic usage reporting.
- QoS handling for user plane, e.g. UL/DL rate enforcement, Reflective QoS marking in DL.
- Uplink Traffic verification (SDF to QoS Flow mapping).
- Transport level packet marking in the uplink and downlink.
- Downlink packet buffering and downlink data notification triggering.
- Sending and forwarding of one or more "end marker" to the source NG-RAN node.
- Functionality to respond to Address Resolution Protocol (ARP) requests and / or IPv6 Neighbour Solicitation requests based on local cache information for the Ethernet PDUs. The UPF responds to the ARP and / or the IPv6 Neighbour Solicitation Request by providing the MAC address corresponding to the IP address sent in the request.
- Packet duplication in downlink direction and elimination in uplink direction in GTP-U layer.
- NW-TT functionality.
- High latency communication, see clause 5.31.8.
- ATSSS Steering functionality to steer the MA PDU Session traffic, refer to clause 5.32.6.
NOTE: Not all of the UPF functionalities are required to be supported in an instance of user plane function of a Network Slice.
- Inter PLMN UP Security (IPUPS) functionality, specified in clause 5.8.2.14.
- Event exposure, including exposure of network information, i.e. the QoS monitoring information, as specified in clause 5.8.2.18, events as specified in clause 5.2.26.2 of TS 23.502 [3], exposure of data collected for analytics, as specified in clause 5.2.26.2 of TS 23.502 [3] and exposure of the TSC management information as specified in clause 5.8.5.14.
- Exposure of the UE information, e.g. UE IP address translation information as specified in clause 5.2.26.3 of TS 23.502 [3] and clause 4.15.10 of TS 23.502 [3] if Network address translation (i.e. NAT) functionality of the UE IP address is deployed within UPF.
- Support of PDU Set Handling as defined in clause 5.37.5.
- Support MoQ relay functionality as defined in clause 5.37.9.2.
- NAT information exposure functionality (if NAT is deployed within UPF) as described in clause 5.8.2.17.
- Features indicated by the means of operator configurable UPF capabilities, as described in clause 5.8.2.21.
- Handling of Payload Headers as defined in clause 5.8.2.22.
- Support N6 delay measurement and reporting to SMF, as defined in clause 5.8.2.23. |
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 PDU Set Handling as defined in clause 5.37.5.
NOTE: The PCF accesses the UDR located in the same PLMN as the PCF.
The details of the PCF functionality are defined in clause 6.2.1 of TS 23.503 [45]. |
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 data using a standardized interface (Nudr) to the Unified Data Repository (UDR).
- Secure provision of information from external application to 3GPP network:
It provides a means for the Application Functions to securely provide information to 3GPP network, e.g. Expected UE Behaviour, 5G-VN group information, CAG information, time synchronization service information, PDU Set handling service specific information and Non-3GPP Device Identifier Information. In that case the NEF may authenticate and authorize and assist in throttling the Application Functions.
- Translation of internal-external information:
It translates between information exchanged with the AF and information exchanged with the internal network function. For example, it translates between an AF-Service-Identifier and internal 5G Core information such as DNN, S-NSSAI, as described in clause 5.6.7.
In particular, NEF handles masking of network and user sensitive information to external AF's according to the network policy.
- Redirecting the AF to a more suitable NEF/L-NEF e.g. when serving an AF request for local information exposure and detecting there is a more appropriate NEF instance to serve the AF's request.
- The Network Exposure Function receives information from other network functions (based on exposed capabilities of other network functions). NEF stores the received information as structured data using a standardized interface to a Unified Data Repository (UDR). The stored information can be accessed and "re-exposed" by the NEF to other network functions and Application Functions and used for other purposes such as analytics.
- A NEF may also support a PFD Function: The PFD Function in the NEF may store and retrieve PFD(s) in the UDR and shall provide PFD(s) to the SMF on the request of SMF (pull mode) or on the request of PFD management from NEF (push mode), as described in TS 23.503 [45].
- A NEF may also support a 5G-VN Group Management Function: The 5G-VN Group Management Function in the NEF may store the 5G-VN group information in the UDR via UDM as described in TS 23.502 [3].
- Support management of ECS Address Information.
- Support management of relationship between DNAI and EAS Address Information.
- Exposure of analytics:
NWDAF analytics may be securely exposed by NEF for external party, as specified in TS 23.288 [86].
- Retrieval of data from external party by NWDAF:
Data provided by the external party may be collected by NWDAF via NEF for analytics generation purpose. NEF handles and forwards requests and notifications between NWDAF and AF, as specified in TS 23.288 [86].
- Support of Non-IP Data Delivery:
NEF provides a means for management of NIDD configuration and delivery of MO/MT unstructured data by exposing the NIDD APIs as described in TS 23.502 [3] on the N33/Nnef reference point. See clause 5.31.5.
- Charging data collection and support of charging interfaces.
- Support of Member UE selection assistance functionality:
- NEF may provide one or more list(s) of candidate UE(s) (among the list of target member UE(s) provided by the AF) and additional information to the AF based on the parameters contained in the request from the AF as described in clause 5.46.2. NEF supports the translation of the member UE selection filtering criteria parameters received from the AF to the corresponding event or analytics filters that can be understood by the 5GC NFs for events or analytics related data collection. NEF interacts with 5GC NFs using existing services in order to collect the corresponding data and then derive the list(s) of candidate UE(s) and other assistance information as described in clause 4.15.13 of TS 23.502 [3].
- Support of Multi-member AF session with required QoS for a set of UEs identified by a list of UE addresses:
- Details are specified in clause 4.15.6.13 of TS 23.502 [3].
- Support of UAS NF functionality:
Details are defined in TS 23.256 [136].
- Support of EAS deployment functionality:
Details are defined in TS 23.548 [130].
- Support of SBI-based MO SM transmit for MSISDN-less MO SMS:
Details are defined in TS 23.540 [142].
- Support PDU Set Handling as defined in clause 5.37.5.
- Support management of common EAS and common DNAI:
Details are defined in TS 23.548 [130].
- Support of Vertical Federated Learning (VFL):
Details are defined in TS 23.288 [86].
- Support request and exposure of energy related information as defined in clause 5.51.
A specific NEF instance may support one or more of the functionalities described above and consequently an individual NEF may support a subset of the APIs specified for capability exposure.
NOTE: The NEF can access the UDR located in the same PLMN as the NEF.
The services provided by the NEF are specified in clause 7.2.8.
For external exposure of services related to specific UE(s), the NEF resides in the HPLMN. Depending on operator agreements, the NEF in the HPLMN may have interface(s) with NF(s) in the VPLMN.
When a UE is capable of switching between EPC and 5GC, an SCEF+NEF is used for service exposure. See clause 5.17.5 for a description of the SCEF+NEF. |
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 discovered NF instances (be discovered) to the NF instance or SCP, including the scenario of NF instances residing in a target PLMN to which traffic from certain UEs will be routed as specified in clause 6.44 of TS 22.261 [2]. The NRF may adjust the discovery results based on output of signalling storm analytics as described in TS 23.288 [86].
- Supports P-CSCF discovery (specialized case of AF discovery by SMF).
- Maintains the NF profile of available NF instances and their supported services.
- Maintains SCP profile of available SCP instances.
- Supports SCP discovery by SCP instances.
- Notifies about newly registered/updated/ deregistered NF and SCP instances along with its potential NF services to the subscribed NF service consumer or SCP (NWDAF may use the notification of updates for signalling storm analytics).
- Maintains the health status of NFs and SCP.
In the context of Network Slicing, based on network implementation, multiple NRFs can be deployed at different levels (see clause 5.15.5):
- PLMN level (the NRF is configured with information for the whole PLMN),
- shared-slice level (the NRF is configured with information belonging to a set of Network Slices),
- slice-specific level (the NRF is configured with information belonging to an S-NSSAI).
In the context of roaming, multiple NRFs may be deployed in the different networks (see clause 4.2.4):
- the NRF(s) in the Visited PLMN (known as the vNRF) configured with information for the visited PLMN.
- the NRF(s) in the Home PLMN (known as the hNRF) configured with information for the home PLMN and optionally with information for target PLMN(s) to which traffic from certain UEs will be routed as specified by clause 6.44 of TS 22.261 [2], referenced by the vNRF via the N27 interface. The hNRF may also query a NRF in a target PLMN as specified in clause 4.17.5 of TS 23.502 [3].
NOTE: The NRF in HPLMN interacts with NRF in target PLMN for certain UEs based on SUPI or Routing Indicator, if one of these parameters is included in the query. |
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.
NOTE 1: This parameter is used for AMF selection, if applicable, as specified in clause 6.3.5. See clause 6.1.6.2.2 of TS 29.510 [58] for its detailed use.
- NF Set ID.
- NF Service Set ID of the NF service instance.
- NF Specific Service authorization information.
- if applicable, Names of supported services.
- Endpoint Address(es) of instance(s) of each supported service.
- Identification of stored data/information.
NOTE 2: This is only applicable for a UDR profile. See applicable input parameters for Nnrf_NFManagement_NFRegister service operation in clause 5.2.7.2.2 of TS 23.502 [3]. This information applicability to other NF profiles is implementation specific.
- Other service parameter, e.g. DNN or DNN list, notification endpoint for each type of notification that the NF service is interested in receiving.
- Location information or serving scope for the NF instance.
NOTE 3: This information is operator specific. Examples of such information can be geographical location, data centre.
- TAI(s).
- NF load information.
- Routing Indicator, Home Network Public Key identifier, for UDM and AUSF.
- For UDM, AUSF and NSSAAF in the case of access to an SNPN using credentials owned by a Credentials Holder with AAA Server, identification of Credentials Holder (i.e. the realm of the Network Specific Identifier based SUPI).
- For UDM and AUSF and if UDM/AUSF is used for access to an SNPN using credentials owned by a Credentials Holder, identification of Credentials Holder (i.e. the realm if Network Specific Identifier based SUPI is used or the MCC and MNC if IMSI based SUPI is used); see clause 5.30.2.1.
- For AUSF and NSSAAF in the case of SNPN Onboarding using a DCS with AAA server, identification of DCS (i.e. the realm of the Network Specific Identifier based SUPI).
- For UDM and AUSF and if UDM/AUSF is used as DCS in the case of SNPN Onboarding, identification of DCS (i.e. the realm if Network Specific Identifier based SUPI, or the MCC and MNC if IMSI based SUPI).
- One or more GUAMI(s), in the case of AMF.
- For the UPF, see clause 5.2.7.2.2 of TS 23.502 [3].
- UDM Group ID, range(s) of SUPIs, range(s) of GPSIs, range(s) of internal group identifiers, range(s) of external group identifiers for UDM.
- UDR Group ID, range(s) of SUPIs, range(s) of GPSIs, range(s) of external group identifiers for UDR.
- AUSF Group ID, range(s) of SUPIs for AUSF.
- PCF Group ID, range(s) of SUPIs for PCF.
- HSS Group ID, set(s) of IMPIs, set(s) of IMPU, set(s) of IMSIs, set(s) of PSIs, set(s) of MSISDN for HSS.
- CHF Group ID(s), range(s) of SUPIs, range(s) of GPSI(s), list of PLMN(s) for CHF, as defined in clause 6.1 of TS 32.290 [67] and TS 29.510 [58].
- For NWDAF, the following information are supported:
- Analytics ID(s) (possibly per service).
- NWDAF Serving Area information (refer to clause 6.3.13).
- Supported Analytics Delay per Analytics ID (if available).
- NF types of the NF data sources, NF Set IDs of the NF data sources, if available.
- Analytics aggregation capability (if available).
- Analytics metadata provisioning capability (if available).
- ML model Filter information parameters include S-NSSAI(s) and Area(s) of Interest for the trained ML model(s) per Analytics ID(s).
- ML Model Interoperability indicator (if available) per Analytics ID(s).
- HFL capability information per analytics ID including FL capability type (i.e. HFL server and/or HFL client), if available).
- VFL capability information per analytics ID including VFL capability type (i.e. VFL server, VFL client), if available.
- Time interval supporting HFL (if available).
- Time interval supporting VFL (if available).
- VFL interoperability indicator per Analytics ID.
- Accuracy checking capability for ML model accuracy monitoring or Analytics Accuracy Monitoring (if available).
- Roaming exchange capability (if available).
- LMF-based AI/ML positioning indication (indicating that the NWDAF containing MTLF supports ML model training for LMF-based AI/ML positioning).
NOTE 4: The NWDAF's Serving Area information is common to all its supported Analytics IDs.
NOTE 5: The Analytics IDs supported by the NWDAF may be associated with a Supported Analytics Delay i.e. the Analytics report can be generated with a time (including data collection delay and inference delay) in less than or equal to the Supported Analytics Delay.
NOTE 6: The determination of Supported Analytics Delay and how the NWDAF avoid updating its Supported Analytics Delay in NRF frequently is NWDAF implementation specific.
- For trusted AF as VFL client, the following information is supported:
- Analytics ID(s).
- VFL capability information per analytics ID including VFL capability type (i.e. VFL client).
- VFL interoperability indicator per Analytics ID.
- Optionally, the time interval supporting VFL.
- optionally supported feature ID(s) per Analytics ID.
- For NEFs serving untrusted AFs:
- Event ID(s) supported by AFs.
- For VFL Analytics ID(s) supported by AFs.
- VFL capability information per analytics ID including VFL capability type (i.e. VFL client), supported by AFs.
- VFL interoperability indicator per Analytics ID.
- For VFL optionally, the time interval supporting VFL.
- For VFL, optionally feature ID(s) per Analytics ID supported by AFs.
- Event Exposure service supported event ID(s) by UPF.
- Application Identifier(s) supported by AFs, in the case of NEF.
- Range(s) of External Identifiers, or range(s) of External Group Identifiers, or the domain names served by the NEF, in the case of NEF.
NOTE 7: This is applicable when NEF exposes AF information for analytics purpose as detailed in TS 23.288 [86].
NOTE 8: It is expected service authorization information is usually provided by OA&M system and it can also be included in the NF profile in the case that e.g. an NF instance has an exceptional service authorization information.
NOTE 9: The NRF may store a mapping between UDM Group ID and SUPI(s), UDR Group ID and SUPI(s), AUSF Group ID and SUPI(s) and PCF Group ID and SUPI(s), to enable discovery of UDM, UDR, AUSF and PCF using SUPI, SUPI ranges as specified in clause 6.3 or interact with UDR to resolve the UDM Group ID/UDR Group ID/AUSF Group ID/PCF Group ID based on UE identity, e.g. SUPI (see clause 6.3.1 for details).
- IP domain list as described in clause 6.1.6.2.21 of TS 29.510 [58], Range(s) of (UE) IPv4 addresses or Range(s) of (UE) IPv6 prefixes, Range(s) of SUPIs or Range(s) of GPSIs or a BSF Group ID, in the case of BSF.
- SCP Domain the NF belongs to.
- DCCF Serving Area information, NF types of the data sources, NF Set IDs of the data sources, if available, in the case of DCCF.
- Supported DNAI list, in the case of SMF.
- Supported Local Offloading Management service area, in the case of SMF.
- For SNPN, capability to support SNPN Onboarding in the case of AMF and capability to support User Plane Remote Provisioning in the case of SMF.
- IP address range, DNAI for UPF.
- Supported operator configurable UPF capabilities (as described in clause 5.8.2.21) in the case of UPF.
- Supported DNS security protocols, in the case of EASDF.
- Additional V2X related NF profile parameters are defined in TS 23.287 [121].
- Additional ProSe related NF profile parameters are defined in TS 23.304 [128].
- Additional MBS related NF profile parameters are defined in TS 23.247 [129].
- Additional UAS related NF profile parameters are defined in TS 23.256 [136].
- Additional Ranging based services and Sidelink Positioning related NF profile parameters are defined in TS 23.586 [180].
- For additional information in PCF profile, see clause 5.2.7.2.2 of TS 23.502 [3]. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.