Summary based on the input provided by NTT DOCOMO in SP-220260. Steering of roaming (SOR) allows the Home PLMN (HPLMN) operator to steer a UE to a visited PLMN (VPLMN) on which the HPLMN wants the UE to register, when the UE registers on another VPLMN. This capability may be needed for reasons such as reselection to a higher priority PLMN based on business arrangements (clause 6.30.1 of TS 22.261). Steering of Roaming (SOR) is used since GSM, and the requirements are provided in TS 22.011. In 5G, the Control Plane SOR solution (CP-SOR) was introduced using the same requirements in TS 22.011. In Rel-17, additional requirements specific for CP-SOR were provided in TS22.261 that allows the HPLMN to control the timing when a UE registered on a VPLMN, in automatic mode (see clause 3.1 of TS 23.122) and currently in CONNECTED mode, enters IDLE mode and initiates higher priority PLMN selection based on the type of ongoing communication. Upon receiving CP-SOR information defined in Rel-15 and Rel-16, while the UE is in CONNECTED mode, the UE waits until it moves to idle mode before performing SOR and attempting to obtain service on a higher priority PLMN. The UEs in 5G may stay in connected mode for a rather long time, whole day or longer, without going to idle mode. The HPLMN operator may have means to evaluate what is more convenient to provide the service for the user (e.g., based on their subscription profile, more efficient economically from wholesale perspective, allow users to use dedicated "economical" retail plans on specific VPLMN, etc.) and decide which VPLMN is more appropriate for the user to register on. Therefore, new requirements are introduced to allow the HPLMN to enforce the interruption of the ongoing sessions for the sake of performing SOR and moving the UE to another VPLMN to obtain service on a higher priority PLMN. This feature introduces means to send additional steering of roaming information, called steering of roaming connected mode control information (SOR-CMCI) that enables the HPLMN to control the timing of a UE in connected mode to move to idle mode to perform the steering of roaming. The UE shall support the SOR-CMCI. The support and use of SOR-CMCI by the HPLMN is based on the HPLMN's operator policy. The SOR-CMCI is provided by the HPLMN operator using different means, a specific application function (SOR-AF) or the information can be stored in the repository system (UDR). This information can be provided to the UE during registration procedure or after the registration (triggered by some parameters in the SOR-AF or the UDR). The UE's type of ongoing communication / session(s) should be taken into consideration. The high priority services and emergency services are exempted from being interrupted (i.e. this feature is not applicable). The new SOR related information is to be exchanged between the HPLMN UDM and the UE in a secured manner therefore the HPLMN data management application function ensures the security of the information using the Authentication Server Function (AUSF). The SOR information is transparent for the VPLMN, and if the VPLMN manipulates the information then the security of the information will break. To ensure the security of the information, the HPLMN may request the UE to provide an acknowledgement that the information is received securely. This feature is optional for the HPLMN. This means that if this optional feature is not selected by the HPLMN operator, then there shall be no impact on the existing SOR functionality. This feature is applicable only when the UE is in automatic network selection mode (see TS 23.122).

Summary based on the input provided by China Telecom in SP-220261. Binding the Access and Mobility Management (AM) and the Session Management (SM) policies provides several benefits, such as the change of RAT/Frequency Selection Priority (RFSP) values for a UE when the quota for the Data Network Name (DNN) for enhanced Mobile Broadband (eMBB) reaches the limit, or simplify the network deployment. A simple way to achieve such binding is to select the same Policy Control Function (PCF) for the AMF and the SMF. In Rel 15 and 16, the same PCF selection for the AMF and the SMF is achieved by the mechanism of AMF optionally forwarding the selected PCF to SMF instance(s) during the PDU Session Establishment procedure(s), and the SMF may select the received PCF for SM Policy Control based on local policies. But it is applicable only in the UE initially accessing via 5GS scenario. This Rel 17 work item specifies a mechanism to achieve the same PCF selection for AMF and SMF in the EPS to 5GS mobility scenario, where the PCF selection for AMF may be performed after the PCF selection for SMF/PGW-C. In this WI, subscription data is expanded to assist the same PCF selection, to offer more flexibility for operation of corresponding service. The mechanism in this WI is based on the PGW-C+SMF registration of the selected PCF for SM Policy Control into the UDM+HSS. When performing PCF selection, based on subscription data for the PCF selection received from the UDM, the AMF determines that the same PCF for AMF and the SMF serving a specific DNN and/or S-NSSAI needs to be selected, then it selects the PCF ID serving the specific DNN and/or S-NSSAI received from UDM before initiating the Establishment of AM Policy Association. It is applicable for EPS to 5GS Mobility. For the scenario of pure 5GS, based on subscription data for the PCF selection received from the UDM, the AMF determines that the same PCF for AMF and SMF serving a specific DNN and/or S-NSSAI needs to be selected, then it forwards the PCF ID for AM policies to the SMF and may additionally indicate to the SMF that the same PCF should be selected for SM Policy Control.

Summary based on the input provided by Huawei in CP-220152. The work item defines some enhancements on the interfaces between vNSSF and hNSSF, vNRF and hNRF, vSEPP and hSEPP in stage3 for inter PLMN roaming in 5GC scenario. Inter PLMN roaming is deployed for a user roaming into a vPLMN which has a roaming agreement with the UE's hPLMN. Some enhancements in stage3 are specifies with regards to Inter PLMN roaming scenarios:

• The NSSF in the vPLMN can invoke the Nnssf_NSSelection service provided by the NSSF in the hPLMN, TS 29.531 specification for the interface between vNSSF and hNSSF is updated to specify the condition/procedure to support the communication.
• Multiple NRFs can be deployed in a vPLMN and/or an hPLMN. TS 29.510 specification for the interface between vNRF and hNRF is updated to support the modification or removal of the subscription in the hNRF if multiple NRFs are deployed in hPLMN.
• TS 29.573 specification for the interface between vSEPP and hSEPP is updated based on the requirements from GSMA and SA3 on the enhancements to the roaming.

Summary based on the input provided by Ericsson in CP-220212. A remote GTP-U restart will lead massive amount of signalling in the network (for reporting GTP-U Error Indication and PFCP Session Modification Signalling messages) over Sx/N4 interface. To avoid that, this work item specifies following enhancements:

• procedures to detect and report the peer GTP-U entity restart;
• protocol support in GTP-U to enable to detect peer GTP-U entity restart;
• protocol support in PFCP to enable User Plane function to report the peer GTP-U entity restart to the Control Plane function.

Summary based on the input provided by Huawei in CP-210183. An optimize solution to reduce the load of signalling for pull mode in EPS and 5GS is defined. A notification push solution for push mode in 5GS is defined. In stage 3, we define the GET method to retrieve the PFD for the application(s) by the client, the server responds a whole representation of the resource for the requested application identifier(s) even in the case that the client requests the PFDs when the caching timer expires and the PFD(s) is not changed at the server. It brings a large signalling load if the whole set of the PFD(s) are always returned by considering that the number of the PFD(s) is very large in the deployment. For push mode, in order to protect the PCEF/TDF from overload, CT3 introduces the notification push for the Push mode in EPS, i.e. the PFDF sends a request with notification flag to the PCEF/TDF and then PCFE/TDF initiates separate pull requests to retrieve the PFDs for different application identifier(s) immediately or within the allowed-delay by considering the load of the PCEF/TDF. But this optimized solution is not defined in 5GS. CT3#110e decided to implement the solution to resolve the above identified issues.

Summary based on the input provided by China Telecom in CP-202251. This work item enables the support of the (Extended) Protocol Configuration Options [(e)PCO] parameters related to the Password Authentication Protocol (PAP) / Challenge Handshake Authentication Protocol (CHAP) over 5GS. This is needed in the following cases:

• migration from EPS to 5GS and potential requirements related to legacy deployments for access to corporate networks, e.g. support of PAP/CHAP in DN-AAA server owned by 3rd parties,
• access to corporate networks by early 5GS deployments (e.g. with standalone SMF), e.g. to support PAP/CHAP in DN-AAA server or LNS owned by 3rd parties.

Summary based on the input provided by Ericsson in CP-220211. The work item defines a User Plane (GTP-U) based solution to start pause of charging for a PDN connection or a PDU session to reduce the Charging Data Record discrepancies between SGW or I/V-SMF and PGW or (h)SMF caused by the control plane signalling latency in existing solution. PGW/SMF Pause of Charging feature is to limit a mismatch between PGW-C/SMF and SGW/I/V-SMF charging volume and packet counts. To further reduce charging discrepancies due to control plane signalling latency, the work item specifies following enhancements to enable start of pause of charging via user plane path:

• a new feature "Notify Start Pause of Charging via user plane feature" (NSPOC) is introduced in PFCP to enable CP function ((SGW-C and PGW-C for EPC, I/V-SMF and (H-)SMF for 5GC) to instruct UP function (SGW-U and PGW-U for EPC, I/V-UPF and PSA UPF), to trigger pause of charging at the upstream GTP-U entity via sending one or more GTP-U Tunnel Status messages, so that the upstream GTP-U entity can stop usage measurement for those URRs applicable for charging; and
• a new mechanism to stop/resume the usage measurement in PFCP when NSPOC is supported; and
• a new GTP-U message "Tunnel Status" is introduced in GTP-U protocol to be used to notify the upstream GTP-U entity to start pause of charging; and
• the support of NSPOC feature is exchanged via control plane signalling between PGW-C/SMF and SGW/I/V-SMF respectively.

Summary based on the input provided by Ericsson in SP-220586. This Work Item added management support for the optimization of Conditional Handover (CHO) and Dual Active Protocol Stack (DAPS) handover. It gives the operator the ability to control and observe CHO and DAPS handover. CHO and DAPS HO were specified by RAN2 and RAN3 under the Work Item NR_Mob_enh-Core. Conditional Handover (CHO) is a new feature defined by RAN2 and RAN3. CHO is different from legacy handover in that the source cell may prepare handovers to one or many target cells, but the execution of the handover is not done by the source cell but by the UE. Dual Active Protocol Stack (DAPS) handover is a new feature define by RAN2 and RAN3. DAPS handover is different from legacy handover in that the UE sets up a connection to the target cell before the connection to the source cell is taken down, sometimes called "make before break". For legacy handover, 3GPP SA5 have previously defined management support for Mobility Robustness Optimization (MRO), under the Self Organizing Network (SON) umbrella. The Enhancement of Handover Optimization Work Item has supplemented the existing MRO management features with enhancements for CHO and DAPS handover. These enhancements include support for configuring CHO and DAPS handover. This support consists of enabling and disabling CHO and DAPS handover. Furthermore, new Performance Measurements for CHO and DAPS handover were added. In addition, a new Key Performance Indicator (KPI) for handover success rate was specified. This new KPI includes legacy handover, CHO and DAPS handover. For the configuration, Stage 1 is specified in TS 28.313, and Stage 2 and 3 is specified in TS 28.541. For Performance Measurements, Stage 1 is in TS 28.313, and Stage 2 is in TS 28.552. For the new KPI, Stage 2 is in TS 28.554.

Summary based on the input provided by NTT DOCOMO in CP-220343. This Work Item enables restoration of profiles between UDR and related NF consumers, to maintain the status up to date as much as possible even in case data stored in UDR is lost or corrupted. Data stored in UDR is automatically updated in normal operation. Some data is stored in volatile storage units due to its nature, such as location of UE, subscription data, policy data, and loss or corruption of storage containing such data could negatively impact the service to subscribers. Replication of volatile storage units and periodic back-up of data are used to avoid loss or corruption, however further procedures are required in case the integrity of data in UDR cannot be ensured, especially when relying on replicated data. Following enhancements are specified to fulfil these required procedures:

• Preparation of profile in NF consumers
• Path and contents of notification sent from UDR to NF consumers when loss or corruption at UDR is detected
• Procedure for synchronization initiated by the NF consumer upon receiving notification of loss or corruption

Summary based on the input provided by Ericsson in SP-220588. Separate IP address pools are used in many enterprise use cases, general management of network IP space resources and/or for UPF selection. This WI has added support for providing IP pool information ("IP Index") from UDM to SMF as part of a Session Management subscription data. The SMF can use the subscriber's IP Index to assist in selecting how the IP address is to be allocated when multiple allocation methods, or multiple instances of the same method are supported. The IP Index can e.g. be used to select between different IP pools. The feature is described in TS 23.501, TS 23.502 and TS 29.503.

Summary based on the input provided by Ericsson in SP-220589. This function improves the dynamic handling of event configuration for cancellation or adding of an individual member or a sub-set of members in a group with active event configuration. The function is to ensure that event cancellation/adding of some member(s) does not affect other members in the group. For a UE belonging to a group which has an active group-based event configuration, the UE's event monitoring can be cancelled due to different reasons (e.g. the UE is removed from the group by AS/AF, the UEs' subscription is deleted from the HSS/UDM while monitoring is active, etc.). It's also possible that AS or AF adds a new UE into an existing group which has active event configuration. The specifications are improved to specify that event configuration can be updated with event cancellation/adding can be sent from AS/AF for individual UE or a sub-set of the UEs (i.e. the external identifiers or MSISDNs of the UEs) in a group which has an active event configuration. The specifications also specify the event cancellation triggered by HSS/UDM for induvial UE or sub-set of the UEs in a group. HSS/UDM informs AS/AF of these individual UE or a sub-set of the UEs (i.e. the external identifiers or MSISDNs of the UEs) via SCEF/NEF. The function is described in TS 23.682, TS 23.502, TS 29.122, TS 29.336, TS 29.503, TS 29.518 and TS 29.522.

Summary based on the input provided by Ericsson in SP-220590. This Work Item provides the capability for an Application Function (AF) to request for a UE either service area coverage or the indication that high throughput is desired or both. It specifies two methods:

1. The AF requests a service area coverage for the UE and/or indicates that high throughput is desired, knowing that certain conditions are met, i.e., the application traffic needs a change of service area coverage or high throughput.
2. The AF provides the service area coverage and/or the indication that high throughput is desired for one or multiple UEs that may or may not already be registered or fulfil certain conditions related to application traffic.

In method a) the AF contacts the NEF then the NEF contacts the BSF to retrieve the identity of the PCF serving the UE. In method b) the AF contacts the NEF then the NEF stores the AF request in the UDR as Data Set "Application Data" and Data Subset "AM influence information". In both methods, the AF provides the service area coverage that the PCF takes as input for policy decisions then to determine whether the service area restrictions need to be updated. The AF provides the indication that high throughput is desired that is considered by the PCF to decide if the RFSP value index for a UE needs to be changed. The PCF reports to the AF that the request was executed. The specification work applies for non-roaming scenarios.

Summary based on the input provided by Tencent in SP-220897. 5G-AIS aims to enable 5G system to provide QoS provisioning for advanced interactive services such as cloud gaming, XR etc. According to SA1 requirements, QoS enhancements for advanced interactive services have been specified in TS 23.501 / 502/ 503. According to SA1 requirements within clause 7.6 of TS 22.261, QoS enhancements including new QoS parameters e.g. new standardized 5QI(s) corresponding to QoS requirements from SA1 have been specified in TS 23.501, TS 23.502 and TS 23.503. In TS 23.501, it was captured that Interactive services that require high data rate and low latency communication, e.g. cloud gaming and AR/VR services are documented in TS 22.261. Standardized 5QI characteristics for such services are provided in Table 5.7.4-1. There have been LS exchanges between SA2, RAN1 and SA4 to confirm these new standardized 5QIs.

Meanwhile, in TS 23.501, it was specified that TSCAI can be used to describe the related traffic characteristics as defined in clause 5.27.2. In TS 23.502, procedure enhancements are specified including adding time domain between PCF and NEF and new procedure for AF to send TSC and non-TSC QoS requirements for AIS. In TS 23.503, PCC support for AIS is specified and TSCAI is extended to integrate TSN and AIS. No summary was provided for these aspects: