hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.32.2 Multi Access PDU Sessions | A Multi-Access PDU (MA PDU) Session is managed by using the session management functionality specified in clause 5.6, with the following additions and modifications:
- When the UE wants to request a new MA PDU Session:
- If the UE is registered to the same PLMN over 3GPP and non-3GPP accesses, then the UE shall send a ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.32.3 Policy for ATSSS Control | If dynamic PCC is to be used for the MA PDU Session, the PCF may take ATSSS policy decisions and create PCC rules that contain MA PDU Session Control information, (as specified in TS 23.503 [45]), which determines how the uplink and the downlink traffic of the MA PDU Session should be distributed across the 3GPP and no... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.32.4 QoS Support | The 5G QoS model for the Single-Access PDU Session is also applied to the MA PDU Session, i.e. the QoS Flow is the finest granularity of QoS differentiation in the MA PDU Session. One difference compared to the Single-Access PDU Session is that in a MA PDU Session there can be separate user-plane tunnels between the AN... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.32.5 Access Network Performance Measurements | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.32.5.1 General principles | When an MA PDU Session is established, the network may provide the UE with Measurement Assistance Information. This information assists the UE in determining which measurements shall be performed over both accesses, as well as whether measurement reports need to be sent to the network.
Measurement Assistance Informatio... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.32.5.2 Round Trip Time Measurements | RTT measurements can be conducted by the UE and UPF independently. There is no measurement reporting from one side to the other. RTT measurements are defined to support the "Smallest Delay", "Priority-based", "Load Balancing" or "Redundant" steering mode (i.e. when RTT threshold value is applied).
The estimation of the... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.32.5.3 Access Availability/Unavailability Report | If required by the network in the Measurement Assistance Information, the UE shall provide access availability/unavailability reports to the network. How the UE detects the unavailability and the availability of an access is based on implementation. The CM state of a UE is not a factor when determining whether the 3GPP... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.32.5.4 Protocol stack for user plane measurements and measurement reports | Figure 5.32.5.4-1: UE/UPF measurements related protocol stack for 3GPP access and for an MA PDU Session with type IP
In the case of an MA PDU Session with type Ethernet, the protocol stack over 3GPP access is that same as the one in the above figure, but the PMF protocol operates on top of Ethernet, instead of UDP/IP.
... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.32.5.5 UE Assistance Operation | When UE-assistance operation is authorized by the PCF in the PCC Rule, the SMF provides an indication for UE-assistance in the ATSSS Rule to the UE, as described in clause 5.32.8 and in the MAR to the UPF, as described in clause 5.8.5.8.
If the UE receives the UE-assistance indicator in an ATSSS rule (as specified in c... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.32.5.6 Suspend and Resume Traffic Duplication | As part of the Redundant Steering Mode, a UPF can decide to suspend traffic duplication for a UE by sending PMF- Suspend Duplication Request message to the UE. How the UPF determines to suspend traffic duplication is implementation specific.
NOTE 1: The Suspension of traffic duplication can be caused by e.g. the locall... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.32.6 Support of Steering Functionalities | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.32.6.1 General | The functionality in an ATSSS-capable UE that can steer, switch and split the MA PDU Session traffic across 3GPP access and non-3GPP access, is called a "steering functionality". An ATSSS-capable UE may support one or more of the following types of steering functionalities:
- Steering functionalities based on multi-pat... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.32.6.2 Steering Functionalities based on multi-path protocols | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.32.6.2.1 MPTCP Functionality | As mentioned in clause 5.32.6.1, the MPTCP functionality in the UE applies the MPTCP protocol (IETF RFC 8684 [81]) and the provisioned ATSSS rules for performing access traffic steering, switching and splitting. The MPTCP functionality in the UE may communicate with the MPTCP Proxy functionality in the UPF using the us... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.32.6.2.2 MPQUIC Functionalities | MPQUIC functionalities are supported as follows:
- The MPQUIC functionalities enable steering, switching and splitting of data traffic between the UE and UPF, in accordance with the ATSSS policy created by the network.
- The operation of the MPQUIC-UDP functionality is based on IETF RFC 9298 [170] "proxying UDP in HTTP... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.32.6.3 Steering Functionalities based on data switching | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.32.6.3.1 ATSSS-LL Functionality | The ATSSS-LL functionality in the UE does not apply a specific protocol. It is a data switching function, which decides how to steer, switch and split the uplink traffic across 3GPP and non-3GPP accesses, based on the provisioned ATSSS rules and local conditions (e.g. signal loss conditions). The ATSSS-LL functionality... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.32.7 Interworking with EPS | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.32.7.1 General | Multi-access connectivity using ATSSS established via EPC only is not supported.
Interworking for MA PDU Session, if allowed by the network, is based on the interworking functionality specified in clause 5.17.2, with the differences and clarifications described in the following clauses.
A PDN Connection in EPS may be m... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.32.7.2 Interworking with N26 Interface | Interworking with N26 interface is based on clause 5.17.2.2, with the following differences and clarifications:
- When the UE is registered to the same PLMN over 3GPP and non-3GPP accesses and the UE request a new MA PDU Session via non-3GPP access, the AMF also includes the indication of interworking with N26 to SMF.
... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.32.7.3 Interworking without N26 Interface | Interworking without N26 interface is based on clause 5.17.2.3, with the following differences and clarifications:
- After UE moves from 5GS to EPS, UE may send a PDN Connectivity Request with "handover" indication to transfer the MA PDU Session to EPS. Then, if the UE or the network does not support MA PDU Session wit... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.32.8 ATSSS Rules | As specified in clause 5.32.3, after the establishment of a MA PDU Session, the UE receives a prioritized list of ATSSS rules from the SMF. The structure of an ATSSS rule is specified in Table 5.32.8-1.
Table 5.32.8-1: Structure of ATSSS Rule
Information name
Description
Category
SMF permitted to modify in a PDU contex... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.33 Support for Ultra Reliable Low Latency Communication | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.33.1 General | The following features described in 5.33 may be used to enhance 5GS to support Ultra Reliable Low Latency Communication (URLLC):
- Redundant transmission for high reliability communication.
In this Release, URLLC applies to 3GPP access only.
When a PDU Session is to serve URLLC QoS Flow, the UE and SMF should establish... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.33.2 Redundant transmission for high reliability communication | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.33.2.1 Dual Connectivity based end to end Redundant User Plane Paths | In order to support highly reliable URLLC services, a UE may set up two redundant PDU Sessions over the 5G network, such that the 5GS sets up the user plane paths of the two redundant PDU Sessions to be disjoint. The user's subscription indicates if user is allowed to have redundant PDU Sessions and this indication is ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.33.2.2 Support of redundant transmission on N3/N9 interfaces | If the reliability of NG-RAN node, UPF and CP NFs are high enough to fulfil the reliability requirement of URLLC services served by these NFs, but the reliability of single N3 tunnel is considered not high enough, e.g. due to the deployment environment of backhaul network, the redundant transmission may be deployed bet... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.33.2.3 Support for redundant transmission at transport layer | Redundant transmission can be supported within the 5G System without making any assumption on support for protocols such as IEEE FRER in the application layer (DN only) at the same time it can be supported without requiring redundant GTP-U tunnel over N3. The backhaul provides two disjoint transport paths between UPF a... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.33.3 QoS Monitoring for packet delay | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.33.3.1 General | QoS Monitoring for packet delay can be applied based on 3rd party application request or PCF policy control or both, e.g. to assist URLLC services. The packet delay between UE and PSA UPF is a combination of the RAN part of UL/DL packet delay as defined in TS 38.314 [120] and UL/DL packet delay between NG-RAN and PSA U... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.33.3.2 Per QoS Flow per UE QoS Measurement | SMF may activate the end to end UL/DL packet delay measurement between UE and PSA UPF for a QoS Flow during the PDU Session Establishment or Modification procedure.
The SMF sends a QoS Monitoring request to the PSA UPF via N4 and NG-RAN via N2 signalling to request the QoS monitoring between PSA UPF and NG-RAN. The QoS... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.33.3.3 GTP-U Path Measurement | The SMF can request to activate QoS monitoring for the GTP-U path(s) between all UPF(s) and the (R)AN based on locally configured policies. Alternatively, when a QoS monitoring policy is received in a PCC rule and the QoS monitoring is not yet active for the DSCP corresponding to the 5QI in the PCC rule, the SMF activa... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.34 Support of deployments topologies with specific SMF Service Areas | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.34.1 General | When the UE is outside of the SMF Service Area, or current SMF cannot serve the target DNAI for the traffic routing for local access to the DN or when the UE is within the SMF service area as well as Local Offloading Management service area and Local Offloading Management (see clause 6.10 of TS 23.548 [130] and clause ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.34.2 Architecture | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.34.2.1 SBA architecture | In non-roaming case the SBA architecture described in Figure 4.2.3-1 shall apply. In local breakout scenarios the SBA architecture described in Figure 4.2.4-1 shall apply. In Home Routed scenarios the SBA architecture described in Figure 4.2.4-3 shall apply. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.34.2.2 Non-roaming architecture | Figure 5.34.2.2-1 depicts the non-roaming architecture with an I-SMF insertion to the PDU Session without UL-CL/BP, using reference point representation.
NOTE 1: N16a is the interface between SMF and I-SMF.
NOTE 2: N38 is the interface between I-SMFs.
Figure 5.34.2.2-1: Non-roaming architecture with I-SMF insertion to ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.34.2.3 Roaming architecture | Figure 5.34.2.3-1 depicts 5G System roaming architecture in the case of local break out scenario where the SMF controlling the UPF connecting to NG-(R)AN is separated from the SMF controlling PDU Session anchor, using the reference point representation.
Figure 5.34.2.3-1: Roaming 5G System architecture with SMF/I-SMF -... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.34.3 I-SMF selection, V-SMF reselection | The AMF is responsible of detecting when to add or to remove an I-SMF or a V-SMF for a PDU Session. For this purpose, the AMF gets from NRF information about the Service Area, supported DNAI(s) of SMF(s) and SMF(s) supporting Local Offloading Management. Local Offloading Management described in clause 5.34.11 and in cl... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.34.4 Usage of an UL Classifier for a PDU Session controlled by I-SMF | This clause applies only in the case of non-roaming or LBO roaming as control of UL CL/BP in VPLMN is not supported in HR case.
When I-SMF is involved for a PDU Session, it is possible that the UL CL controlled by I-SMF is inserted into the data path of the PDU Session. The usage of an ULCL controlled by I-SMF in the d... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.34.5 Usage of IPv6 multi-homing for a PDU Session controlled by I-SMF | This clause applies only in the case of non-roaming or LBO roaming as control of UL CL/BP in VPLMN is not supported in HR case.
When I-SMF is involved for a PDU Session, it is possible that the BP controlled by I-SMF is inserted into the data path of the PDU Session. The usage of a BP controlled by I-SMF in the data pa... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.34.6 Interaction between I-SMF and SMF for the support of traffic offload by UPF controlled by the I-SMF | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.34.6.1 General | This clause applies only in the case of non-roaming or LBO roaming as control of UL CL/Branching Point in VPLMN is not supported in HR case. It applies for the architectures described in clauses 5.34.4 and 5.34.5
If the local offloading management is applied for the PDU session, see clause 6.10 of TS 23.548 [130] and c... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.34.6.2 N4 information sent from SMF to I-SMF for local traffic offload | The SMF generates N4 information for local traffic offload based on the available DNAI(s) indicated by the I-SMF, PCC rules associated with these DNAI(s) and charging requirement. This N4 information is sent from the SMF to the I-SMF after UL CL/Branching Point insertion/update/removal and the I-SMF uses this N4 inform... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.34.7 Event Management | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.34.7.1 UE's Mobility Event Management | When an I-SMF is involved in a PDU Session, the SMF and I-SMF independently subscribe to "UE mobility event notification" service provided by AMF. The AMF treats the SMF's and I-SMF's subscription separately and notifies the event directly to the SMF or I-SMF. If the SMF does not know the serving AMF address, the SMF g... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.34.7.2 SMF event exposure service | Consumers of SMF events do not need to be aware of the insertion / removal / change of an I-SMF as they always subscribe to the SMF of the PDU Session.
Except for the events documented in the present clause, the I-SMF does not need to support the events defined in clause 5.2.8.3.1 of TS 23.502 [3].
For Events "First do... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.34.7.3 AMF implicit subscription about events related with the PDU Session | When creating an association with a SMF or I-SMF for a PDU Session, the AMF implicitly subscribes to SMF / I-SMF about events related with the PDU Session (the AMF provides the relevant notification information to the SMF or the I-SMF respectively). This implicit subscription is implicitly released when the correspondi... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.34.8 Support for Cellular IoT | This clause defines the specific impacts of deployments topologies with specific SMF Service Areas on how 5GS supports Cellular IoT as defined in clause 5.31.
For a PDU Session supporting Control Plane CIoT 5GS Optimisation as defined in clause 5.31.4:
- For a PDU Session towards a DNN/S-NSSAI for which the SMF Selecti... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.34.9 Support of the Deployment Topologies with specific SMF Service Areas feature within and between PLMN(s) | When Deployments Topologies with specific SMF Service Areas need to be used in a PLMN for a S-NSSAI, all AMF serving this S-NSSAI are configured to support Deployments Topologies with specific SMF Service Areas.
NOTE 1: The specifications do not support AMF selection related with Deployment Topologies with specific SMF... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.34.10 Support for 5G LAN-type service | This clause defines how 5GS supports 5G LAN-type service as defined in clause 5.29 in the case of deployments topologies with specific SMF Service Areas.
The UE may be connected with the PSA via an I-UPF which is controlled by the I-SMF. In this case, traffic switching (e.g. UPF local traffic switching) is controlled b... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.34.11 Support for Local Offloading Management | When the Local Offloading Management is allowed based on SMF selection subscription data and the UE is within the local offloading management service area, an I-SMF supporting the Local Offloading Management is inserted between the SMF and the AMF, even if the UE is within the SMF service area. The local offloading man... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.35 Support for Integrated access and backhaul (IAB) | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.35.1 IAB architecture and functional entities | Integrated access and backhaul (IAB) enables wireless in-band and out-of-band relaying of NR Uu access traffic via NR Uu backhaul links. In this Release of the specification, NR satellite access is not applicable. The serving PLMN may provide the mobility restriction for NR satellite access as specified in clause 5.3.4... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.35.2 5G System enhancements to support IAB | In IAB operation, the IAB-UE interacts with the 5GC using procedures defined for UE. The IAB-node gNB-DU only interacts with the IAB-donor-CU and follows the CU/DU design defined in TS 38.401 [42].
For the IAB-UE operation, the existing UE authentication methods as defined in TS 33.501 [29] applies. Both USIM based met... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.35.3 Data handling and QoS support with IAB | Control plane and user plane protocol stacks for IAB operation are defined in TS 38.300 [27].
QoS management for IAB can remain transparent to the 5GC. If NG-RAN cannot meet a QoS requirement for a QoS Flow to IAB-related resource constraints, the NG-RAN can reject the request using procedures defined in TS 23.502 [3].... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.35.4 Mobility support with IAB | For UEs, all existing NR intra-RAT mobility and dual-connectivity procedures are supported when the UE is served by an IAB-node except for the cases of NR satellite access. For a UE served by an IAB-node when the serving IAB-node changes its IAB-donor-CU due to mobility, the mobility support is specified in clause 5.35... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.35.5 Charging support with IAB | IAB-donor has all the information regarding the UE and the IAB-node and corresponding mapping of the bearers. The PDU sessions for the UE and IAB-node are separate from IAB-node onwards to the core network. Therefore, the existing charging mechanism as defined in clause 5.12 can be used to support IAB. |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.35.6 IAB operation involving EPC | When the IAB-donor gNB has connection to both EPC and 5GC, based on PLMN configuration, there are two possible operation modes:
- the IAB-node connects to a 5GC via the IAB-donor gNB, while the UEs served by the IAB-node connect to EPC with Dual Connectivity as defined in TS 37.340 [31]. In this operation mode, the IAB... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.36 RIM Information Transfer | The purpose of RIM Information Transfer is to enable the transfer of RIM information between two RAN nodes via 5GC. The RIM Information Transfer is specified in TS 38.413 [34].
When the source AMF receives RIM information from source NG-RAN towards target NG-RAN, the source AMF forwards the RIM information to the targe... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.37 Support for high data rate low latency services, eXtended Reality (XR) and interactive media services | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.37.1 General | This clause provides an overview of 5GS functionalities for support of XR services (AR/VR applications) and interactive media services that require high data rate and low latency communication, e.g. cloud gaming and tactile/multi-modal communication services according to service requirements documented in TS 22.261 [2]... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.37.2 Policy control enhancements to support multi-modal services | A multi-modal service is a communication service that consists of several data flows that relate to each other and that are subject to application coordination. The data flows can transfer different types of data (for example audio, video, positioning, haptic data) and may come from different sources(e.g. a single UE, ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.37.3 Support of ECN marking for L4S to expose the congestion information | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.37.3.1 General | L4S (Low Latency, Low Loss and Scalable Throughput) is described in IETF RFC 9330 [159], IETF RFC 9331 [160] and IETF RFC 9332 [161]. It exposes congestion information by marking ECN bits in the IP header of the user IP packets between the UE and the application server to trigger application layer rate adaptation.
In 5... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.37.3.2 Support of ECN marking for L4S in NG-RAN | ECN marking for L4S may be supported in NG-RAN as specified in TS 38.300 [27].
To enable ECN marking for L4S in NG-RAN, dedicated QoS Flow(s) are used for carrying L4S enabled IP traffic. The SMF may be instructed, based on either dynamic or predefined PCC rule, to provide an indication for ECN marking for L4S to NG-RA... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.37.3.3 Support of ECN marking for L4S in PSA UPF | To enable ECN marking for L4S by a PSA UPF, a QoS Flow level ECN marking for L4S indicator may be sent by SMF to PSA UPF over N4. SMF also indicates to NG-RAN to report the congestion information (i.e. a percentage of packets that UPF uses for ECN marking for L4S) of the QoS Flow on UL and/or DL directions via GTP-U he... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.37.3.4 Support of ECN marking for L4S in N3IWF and TNGF | ECN marking for L4S may be supported in N3IWF and TNGF, as specified in clauses 6.2.9 and 6.2.9A, respectively.
To enable ECN marking for L4S in N3IWF and TNGF, dedicated QoS Flow(s) and non-3GPP access resources (i.e. IPsec Child SAs) are used for carrying L4S enabled IP traffic. The SMF may be instructed, based on ei... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.37.4 Network Exposure of 5GS information | 5GS and XR/media services cooperate to provide a better user experience using External Network Exposure.
Based on the AF request, the 5GS can expose the following information based on the QoS Monitoring as defined in clause 5.33.3 and/or clause 5.45:
- The UL and/or DL congestion information monitoring (see clause 5.45... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.37.5 PDU Set based Handling | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.37.5.1 General | A PDU Set is comprised of one or more PDUs carrying an application layer payload such as a video frame or video slice. The PDU Set based QoS handling by the 5G-AN is determined by PDU Set QoS Parameters in the QoS profile of the QoS Flow (specified in clause 5.7.7) and PDU Set Information provided by the PSA UPF via N3... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.37.5.2 PDU Set Information and Identification | To support PDU Set based QoS handling, the PSA UPF identifies PDUs that belong to a PDU Set and determines the below PDU Set Information and sends it to the 5G-AN in the GTP-U header. The PDU Set Information is used by the 5G-AN for PDU Set based QoS handling as described above.
The PDU Set Information comprises:
- PDU... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.37.5.3 Non-homogenous support of PDU set based handling in NG-RAN | The SMF, by sending PDU Set QoS parameters (as described in clause 5.7.7.1) or a DL PDU Set Information Marking Support Indication (as described in clause 5.37.5.1) to the NG-RAN, requests the NG-RAN to activate PDU Set handling for a given QoS Flow and the NG-RAN provides the SMF with a PDU Set Based Handling Support ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.37.6 UL/DL policy control based on round-trip latency requirement | For XR and other interactive media services that require very low Round-Trip (RT) latency, Uplink-Downlink policy control may be supported to meet the RT latency requirement. RT latency requirement is the upper bound for the sum of UL delay and DL delay of a single data flow or two different data flows between UE and N... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.37.7 5GS Packet Delay Variation monitoring and reporting | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.37.7.1 General | The 5GS Packet Delay Variation is the variation of packet delay measured between UE and PSA UPF. The AF may send the requirement for Packet Delay Variation monitoring to 5GS together with the requirement for packet delay measurement, as described in clause 6.1.3.26 of TS 23.503 [45].
Upon AF request for Packet Delay Va... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.37.8 UE power saving management | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.37.8.1 General | The following traffic assistance information may be provided by the CN to NG-RAN in order to configure UE power saving management scheme for connected mode DRX:
- UL and/or DL Periodicity;
- N6 Jitter Information associated with the DL Periodicity;
- Indication of End of Data Burst.
The UL and/or DL Periodicity and N6 ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.37.8.2 Periodicity and N6 Jitter Information associated with Periodicity | In the procedures for setting up or updating an AF session with QoS, the 5G System may be provided with UL/DL Periodicity information for NG-RAN to configure UE power management for connected mode DRX. The UL/DL Periodicity information is provided by the AF to the PCF via NEF or directly to the PCF when the AF is trust... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.37.8.3 End of Data Burst Indication | An indication of End of Data Burst may be provided to the NG-RAN by the PSA UPF, e.g. to configure UE power management schemes like connected mode DRX.
Based on the End of Data Burst Marking Indication in a PCC rule and/or on local operator policies, SMF should request the PSA UPF to detect the last PDU of the data bur... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.37.9 Support of transferring media related information over N6 | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.37.9.1 General | This clause describes the procedure to support transferring of media related information (i.e. information related to the media being transmitted, either explicitly provided by the AS or inferred from protocol headers or payload, e.g. PDU Set Information, Data Burst Size, etc.) over N6. Such support is necessary is whe... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.37.9.2 Usage of Media Over QUIC in order to Handle end-to-end encrypted XR and media flows | When a PSA UPF that supports MoQ relay functionality has been selected, encrypted Metadata associated with traffic can be transported between the UPF and the AS via Media over QUIC (MoQ), IETF draft-ietf-moq-transport [201].
A PSA UPF supporting the MoQ relay functionality can be selected by SMF with the consideration ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.37.9.3 Use of connect-UDP | When the traffic is UDP and encrypted end-to-end, the UPF may be configured by the SMF establish a connection to an HTTP/3 AS proxy using connect-UDP according to IETF RFC 9298 [170], acting as an HTTP/3 client configured to use a UDP proxy. The AS then provides media related information within HTTP datagrams. The medi... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.37.9.4 Usage of UDP Option transferring media related information over N6 | The mechanism described in this clause uses connect-udp in tunnel mode for On-path N6 signalling to establish a UDP tunnel between the UPF as HTTP/3 client and the AS as HTTP/3 proxy according to clause 5.37.9.2 to securely transfer media related information. This clause defines the differences with the mechanisms defi... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.37.10 Supporting dynamically changing traffic characteristics via the User Plane | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.37.10.1 DL Data Burst Size marking | The Data Burst Size may be provided to the NG-RAN in the downlink GTP-U header by the UPF in order to assist radio resource management. As described in clause 6.1.3.27.5 of TS 23.503 [45] the PCF may include a Data Burst Size Marking Indication within a PCC Rule to request the UPF to identify and mark the Data Burst Si... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.37.10.2 Time to Next Burst marking | The time to next data burst, which is the interval between the transmission of the last PDU in the current data burst and the first PDU of the next data burst, may be provided to the NG-RAN by the UPF to assist NG-RAN's behaviour in downlink. As described in clause 6.1.3.27.5 of TS 23.503 [45] the PCF may include a Tim... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.37.10.3 Expedited Data Transfer with reflective QoS | Expedited Data Transfer with reflective QoS can be requested by AF to expedite the data transfer of larger payload for IP flow(s) of XR application. Expedited Data Transfer can be used for non-GBR SDF only.
To enable Expedited Data Transfer, the AF provides two media flows that contains the same SDF filter associated w... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.37.11 Traffic identification and differentiated QoS for multiplexed media flows | XR and interactive media services can send data traffic of different media components with different QoS requirements. Several media flows could be multiplexed on the same end-to-end transport layer connection. In order to uniquely identify each media flow, the IP Packet Filter can further include multiplexed media spe... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.38 Support for Multi-USIM UE | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.38.1 General | A network and a Multi-USIM UE may support one or more of the following features for Multi-USIM UE operation:
- Connection Release as described in clause 5.38.2;
- Paging Cause Indication for Voice Service, as described in clause 5.38.3;
- Reject Paging Request, as described in clause 5.38.4;
- Paging Restriction, as de... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.38.2 Connection Release | A Multi-USIM UE may request the network to release the UE from RRC_CONNECTED state in 3GPP access for a USIM due to activity on another USIM in 3GPP access, if both UE and network indicate the Connection Release feature is supported to each other.
In the case of NAS connection release procedure, the UE indicates that i... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.38.3 Paging Cause Indication for Voice Service | A Multi-USIM UE and the network may support Paging Cause Indication for Voice Service feature.
The network that supports Paging Cause Indication for Voice Service feature shall provide a Voice Service Indication for IMS voice service in the Paging message, only if the UE indicates the Paging Cause Indication for Voice ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.38.4 Reject Paging Request | A Multi-USIM UE may set up a connection to respond to a page with a Reject Paging Indication to the network indicating that the UE does not accept the paging and requests to return to CM-IDLE state after sending this response, if both UE and network indicate the Reject Paging Request feature is supported to each other.... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.38.5 Paging Restriction | A Multi-USIM UE and the network may support Paging Restriction. A Multi-USIM UE, if the AMF indicates that the network supports Paging Restriction feature, may indicate Paging Restriction Information in the Service Request or Registration Request message (including the case where the Registration Request is sent due to... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.38.6 Paging Timing Collision Control | To avoid possible paging occasion collision and to enhance the likelihood that paging is received successfully for different USIMs, a Multi-USIM UE may need a new 5G-GUTI to modify the timing of the Paging Occasions (POs) for a USIM when the USIM's registration is not emergency registration. When a Multi-USIM UE needs ... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.39 Remote provisioning of credentials for NSSAA or secondary authentication/authorization | |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.39.1 General | The UE's subscribed network (i.e. HPLMN, or subscribed SNPN) may provide functionalities to provision or update the credentials used for NSSAA or credentials used for secondary authentication/authorization to the UE. The provisioning procedure is supported via User Plane.
For User Plane Remote Provisioning, the UE esta... |
fbecc7f0dcf9784c6066646052ab0c0e | 23.501 | 5.39.2 Configuration for the UE | In order to enable UP Remote Provisioning of credentials for NSSAA or secondary authentication/authorization, UE Configuration Data for UP Remote Provisioning are either pre-configured on the UE or provided by the network to the UE. UE Configuration Data for UP Remote Provisioning provided by the network take precedenc... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.