hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.1.18 Solution #1.18: Policy for DualSteer steering and switching | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.1.18.1 Description | This solution addressed Key Issue #1.4 "Policy enhancement for DualSteer".
Policy for steering:
During the registration procedure of the DualSteer device, the AMF may initiate UE Policy Association procedure to provide policies (e.g. URSP rule) for DualSteer traffic steering. In the UE policy association procedure, AM-... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.1.18.2 Procedures | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.1.18.2.1 Procedures for Policy for DualSteer Traffic Steering | Figure 6.1.18.1-1: Policy for DualSteer traffic steering
1. The DualSteer device uses SUPI1 to send registration request including DualSteer capability and UE Policy Container to AMF-1 over 3GPP aceess1.
2. The AMF-1 establishes UE Policy Association with the PCF when a UE Policy Container is received from the UE.
3. T... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.1.18.2.2 Procedures for Policy for DualSteer Traffic Switching | Figure 6.1.18.1-2: Policy for DualSteer traffic switching
0. After the establishment of PDU Session for DualSteer, some specific service data may be steered on 3GPP access-1 as in clause 6.1.18.2.1.
1. According to network situation change or service requirement from AF, PCF may decide whether to update the policy to g... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.1.18.3 Impacts on services, entities and interfaces | PCF:
- Generating PCC rules for DualSteer service based on DualSteer data and/or application data.
UDM/UDR:
- Providing DualSteer related subscription data to PCF for DualSteer related policy. |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.1.19 Solution #1.19: PDU Session Control for DualSteer | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.1.19.1 Description | This solution is targeting for KI#1.3 Session management aspects for DualSteer and KI#1.4 Policy enhancements for DualSteer.
Additionally, we need to consider the WT#1 based on the SID.
Accordingly we can summarize the requirements like the following.
- DS supporting UE (or DS device) can register two 3GPP access netwo... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.1.19.2 Procedures | The procedures are described in Figure 6.1.19.2-1.
Figure 6.1.19.2-1: Procedure for PDU Session Control for DualSteer
NOTE: Single AMF is not assumed in the Figure 6.1.19.2-1.
1. DS supporting UE (or DS device) receives UE Policy from the network. It includes information on transmission over single 3GPP access is allow... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.1.19.3 Impacts on services, entities and interfaces | UDM:
- UDM stores DS Information including primary 3GPP access network when a PDU Session is established. Notifies SMF whether the DS supporting UE (or DS device) has PDU session over primary 3GPP access.
SMF:
- SMF checks UDM information if the request is allowed. If it is allowed, SMF registers (SUPI, SMF ID, PDU ses... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2 Solutions for ATSSS_Ph4 | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.1 Solution #2.1: Policy Control for the MPQUIC Steering Functionality for non-UDP Traffic | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.1.1 Description | This solution is proposed to address Key Issue #2.1.
The MPQUIC steering functionality can be enhanced to enable different CONNECT protocols to be used (i.e. with protocol values connect-udp [6], connect-ip [7], connect-ethernet [8]), possibly concurrently in the same PDU session. Furthermore, at least one of these CON... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.1.2 Procedure | Figure 6.2.1.2-1: Policy-Controlled MA PDU Session using MPQUIC Steering Mode for Non-UDP Traffic
The above Figure 6.2.1.2-1 shows how the CONNECT protocol and values of related parameters are selected over an MA PDU Session using the MPQUIC steering functionality.
0. Policy rules that include allowed CONNECT protocol(... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.1.3 Impacts on services, entities and interfaces | UE:
- Select the CONNECT protocol and values of related parameters to use in the CONNECT request (based on ATSSS rules from the SMF including allowed CONNECT protocol(s) and values of related parameters).
PCF, UDM:
- MA PDU session control information in PCC rules can include allowed CONNECT protocol(s) and values of r... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.2 Solution #2.2: Ipsec establishment using null encryption with ePDG co-located in the UPF | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.2.1 Description | This solution addresses key issue #2.2.
This solution basically re-use the existing ePDG architecture/functionality, which means the ePDG is co-located with the PSA UPF. Figure 6.2.2.1-1 shows overall architecture of this solution. When a UE establishes MA PDU Session over 3GPP access, the SMF+PGW-C, based on interacti... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.2.2 Procedures | Figure 6.2.2.2-1: MA PDU Session Establishment using ePDG co-located in the UPF
1. A UE registers over 3GPP access.
2. The UE sends PDU Session Establishment Request to establish a MA PDU Session. In the request message, the UE indicates that the UE support simplified ATSSS architecture over non-3GPP access.
3. Based o... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.2.3 Impacts on services, entities and interfaces | UE:
- includes capability of simplified ATSSS architecture over non-3GPP access during the PDU Session Establishment Request procedure.
- based on received ePDG information during the MA PDU Session establishment, connects to the ePDG and triggers initial attach procedure.
SMF+PGW-C:
- based on UE capability, requests ... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.3 Solution #2.3: MPQUIC Steering Functionality extended with additional CONNECT methods | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.3.1 Description | This solution addresses KI#2.1.
The Rel-18 MPQUIC functionality enables steering, switching, and splitting of UDP traffic between the UE and UPF, in accordance with the ATSSS policy created by the network. The operation of the MPQUIC functionality is based on RFC 9298 [6] "proxying UDP in HTTP", which specifies how UDP... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.3.1.1 HTTP CONNECT methods | Proxy UDP (connect-udp):
- Proxying of UDP traffic is based on RFC 9298 [6] supporting proxy of UDP traffic in HTTP/3. The UDP Proxying Payload contains the payload of a UDP packet. The proxied UDP payload is encapsulated in HTTP/3 datagrams [11].
Proxy TCP (connect-tcp):
- draft-ietf-httpbis-connect-tcp [10] defines a... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.3.2 Procedures | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.3.2.1 MA PDU Session Establishment | Figure 6.2.3.2-1: PDU Session Establishment
1. The UE sends a PDU Session Establishment Request message and includes the ATSSS capabilities as per rel-18. In addition, if the UE supports MPQUIC with other proxy protocols than connect-udp and in case of IP-based PDU Session types, the UE includes the supported MPQUIC pr... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.3.2.2 PDN Connections and Multi Access PDU Sessions | When the UE wants to request a new PDN Connection in 3GPP access in EPC and wants to use this PDN Connection as user-plane resource associated with a MA PDU Session, the PDN Connection procedure as defined in clause 4.22.2.3.2 of TS 23.502 [4], is used with the following differences:
- If the UE supports MPQUIC with ot... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.3.3 Impacts on services, entities and interfaces | UE:
- Support for additional MPQUIC proxy protocols.
- SM NAS enhancements to negotiate the support for additional MPQUIC proxy protocols (enhanced 5GSM capability, enhanced ATSSS container).
- IKEv2 enhancements to negotiate the support for additional MPQUIC proxy protocols (enhanced 5GSM capability, enhanced ATSSS co... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.4 Solution #2.4: MPQUIC steering functionality using IP proxying over HTTP | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.4.1 Introduction | The solution in this clause specifies a new ATSSS steering functionality, called Multipath QUIC-IP (MPQUIC-IP) steering functionality, and addresses the objective of KI#2.1 for a QUIC-based steering functionality to allow the transport of IP packets over multiple accesses between UE and UPF. It generalizes on the curre... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.4.2 High-level Description | The key principles of the solution are summarized below.
- After the MA PDU Session establishment, the UE creates one or more multipath QUIC connections with the UPF. Each multipath QUIC connection is associated with a QoS flow, i.e. it carries the traffic mapped to a QoS flow.
- The UE operates as a connect-ip client ... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.4.3 Procedures | Figure 6.2.4.3-1 below depicts the key steps of the procedure that enables data traffic to be exchanged between the UE and UPF using the MPQUIC-IP steering functionality.
Figure 6.2.4.3-1: Procedure for enabling data traffic using the MPQUIC-IP steering functionality
1. The UE establishes a MA PDU Session with the 5G c... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.5 Solution #2.5: MPQUIC steering functionality using Ethernet proxying over HTTP | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.5.1 Introduction | The solution in this clause specifies a new ATSSS steering functionality, called Multipath QUIC-Ethernet (MPQUIC-E) steering functionality, and addresses the objective of KI#2.1 for a QUIC-based steering functionality to allow the transport of Ethernet frames over multiple access between UE and UPF.
This solution exten... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.5.2 High-level Description | The key principles of the solution are summarized below.
- After the Ethernet MA PDU Session establishment, the UE creates one or more multipath QUIC connections with the UPF. Each multipath QUIC connection is associated with a QoS flow, i.e. it carries the traffic mapped to a QoS flow.
- The UE operates as a connect-e... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.5.3 Procedures | Figure 6.2.5.3-1 below depicts the key steps of the procedure that enables data traffic to be exchanged between the UE and UPF using the MPQUIC-E steering functionality.
Figure 6.2.5.3-1: Procedure for enabling data traffic using the MPQUIC-E steering functionality
1. The UE establishes an Ethernet MA PDU Session with ... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.6 Solution #2.6: for KI#2.2 | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.6.0 Introduction | As shown in the following figure, the UE accesses via both 3GPP and non-3GPP (WLAN) accesses to the network. On the 3GPP side, the UE transfers the NAS message to the AMF, and receives the UPF IP Address for non-3GPP access in the PDU Session establishment accept message. On the non-3GPP sides, the UE connects to the U... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.6.1 PDU Session establishment of Solution #2.6 | Figure 6.2.6.1: PDU Session establishment of Solution #2.6
3GPP Access:
1. UE sends MA PDU Session establishment request to AMF based on the current specification.
Editor's note: Whether to reuse "MA PDU session indication" or to define a new indication is FFS.
Editor's note: Whether to define a new ATSSS-Lite capabili... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.6.2 System impact | The solution has impact on the UE and some NFs, as follows.
UPF:
- Supports the ATSSS-Lite functionality, including allocation of the public IP address for this ATSSS-Lite functionality, establishment of the IPSec tunnel with the UE, and forwarding the UE NAI and EAP messages to the SMF via the N4 Session.
SMF:
- Suppo... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.7 Solution #2.7: Architecture for ATSSS-Lite | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.7.1 Description | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.7.1.1 Introduction | This solution addresses KI 2.2 (Simplified ATSSS architecture over non-3GPP access) and introduces the architecture for a lightweight version of ATSSS, name ATSSS-Lite. This new architecture is based on the principles described in the following clauses. The solution does not apply to ATSSS-LL. |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.7.1.2 Architecture without TNGF/N3IWF | This solution proposes an architecture in which there is no gateway for access to 5G CN via non-3GPP access, such as TNGF (for trusted non-3GPP access) or N3IWF (for untrusted non-3GPP access). In particular, the UE does not establish any IPSec connection to the 5G CN. Instead, the UE connects to the UPF via the public... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.7.1.3 Non-Integrated Non-3GPP Access and re-use of the MA PDU Session concept | The ATSSS-Lite architecture leads to the notion of Non-Integrated Non-3GPP Access (NIN3A) (see clauses 3.1 and 3.2). The solution proposes to reuse the definition of Multiple Access PDU Session described in clause 3.1 of TS 23.501 [3] for NIN3A, which reads as follows:
MA PDU Session: A PDU Session that provides a PDU ... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.7.1.4 Re-use of high layer steering functionality and traffic security | The assumption for ATSSS-Lite is that the steering functionalities in the UE and in the UPF are high layer steering functionalities. They are based on the existing MPTCP and MQUIC steering functionalities that are used in the legacy ATSSS (see clauses 5.32.6.2.1 and 5.32.6.2.2 of TS 23.501 [3]).
Editor's note: Whether ... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.7.1.5 Protocol stacks connectivity via Non-3GPP | The solution is based on the following assumptions:
- The NAS signalling between UE and CN is carried only over the 3GPP access. This implies that there is no need to have NAS signalling between UE and CN exchanged over NIN3A when the UE is connected via 3GPPA. Consequently, no CP protocol stack between UE and CN over ... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.7.1.6 Re-use of steering modes, MPTCP/MQUIC measurements and extension URSP/ATSSS/N4 rules | Since the steering functionality for ATSSS-Lite is based on MPTCP or MPQUIC, the MPTCP/MQUIC measurements mechanisms can be used instead of the 3GPP defined PMF (Performance Measurement Function) to measure Round Trip Time (RTT) and Packet Loss Rate (PLR). Because of that, at least in principle, the existing ATSSS stee... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.7.2 Procedures | The procedures in this clause describe how the MA PDU Session can be established for ATSSS-Lite and how the appropriate SMF and UPF can be selected according to the indicated UE capability. Figures 6.2.7.2.1-1 and 6.2.7.2.1-2 describe two options of how a MA PDU Session over the Nx interface can be established. Such Fi... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.7.2.1 Option 1: ATSSS capable AMF | This option assumes that the AMF supports ATSSS-Lite.
Figure 6.2.7.2.1-1: Simplified ATSSS-Lite MA PDU Session Establishment - Option 1
The main steps of the MA PDU Session Establishment procedure for ATSSS-Lite can be summarized as follows:
1. When sending the PDU Session Establishment Request to the CN, the UE Includ... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.7.2.2 Option 2: ATSSS capable SMF supports ATSSS-Lite | This option assumes that an ATSSS capable SMF supports ATSSS-Lite, whereas the AMF is transparent to ATSSS-Lite.
Figure 6.2.7.2.2-2: Simplified ATSSS-Lite MA PDU Session Establishment - Option 2
With the assumptions above, Option 2 is based on the same steps of Option 1, with the key difference that the (legacy) ATSSS ... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.7.2.3 Enhancements to MA PDU Session Modification | Figure 6.2.7.2.3-1: MA PDU session modification for using NIN3A
1. The UE issues new PDU session modification request (for the MA PDU session supporting ATSSS between 3GPP and NIN3A) to get a new Access Info data.
2. The SMF requests Access Info data from the PSA UPF of MA PDU Session.
3. The SMF provides Access Info d... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.7.3 Impacts on services, entities and interfaces | UE:
- Indicates UE ATSSS-Lite Capability.
Editor's note: Whether this is indicated only in SM signalling at PDU session establishment or also to AMF is FFS.
- Receives Access Info data from the SMF.
- Creates new MPTCP/MP-QUIC path to the existing MA PDU session using the received Access Info data.
- Ability to request... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.8 Solution #2.8: Simplified ATSSS over non-3GPP based on direct MPQUIC connection between UE and UPF | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.8.1 Description | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.8.1.1 General | This solution addresses KI#2.2.
Since QUIC is encrypted, there is a possibility to use the MPQUIC Steering Functionality between UE and UPF without the underlying IPSec layer and without a Gateway such as N3WIF or TNGF (subject to SA3 analysis and confirmation). In this case there is no NAS signalling connection via no... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.8.2 Procedures | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.8.2.1 General | The procedures below describe two options:
- Option 1: In this option, the MA PDU session establishment procedure is transparent to the AMF.
- Option 2: In this option the AMF is enhanced to support simplified ATSSS procedures over non-3GPP access. |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.8.2.2 Registration via 3GPP access | Option 1 (MA PDU session establishment procedure is transparent to the AMF):
- In this option there are no impacts to the registration procedure via 3GPP access.
Option 2 (AMF is enhanced to support simplified ATSSS procedures over non-3GPP access):
- During the Registration procedure the network indicates to the UE th... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.8.2.3 MA PDU Session Establishment via 3GPP access | Figure 6.2.8.2.3-1: PDU Session Establishment over 3GPP access
Option 1 (without AMF impacts):
1. The UE sends a PDU Session Establishment Request message and includes its ATSSS Capabilities, also indicating that it is capable of "direct ATSSS via non-3GPP access using MPQUIC".
NOTE 1: This option is assumed to be tran... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.8.2.4 Addition of non-3GPP access user-plane resources | The use of MPQUIC over non-3GPP access is based on the MPQUIC steering functionality in Rel-18, with the clarifications and changes described in this clause.
Figure 6.2.8.2.4-1: Addition of non-3GPP access user-plane resources
After MA PDU Session Establishment via 3GPP access, and after the multipath QUIC connections ... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.8.2.5 Handling of the MA PDU Session in case the UE loses 3GPP access coverage | 6.2.8.2.5.1 General
In case the UE loses 3GPP coverage and is no longer reachable via 3GPP access, it is not possible to execute NAS procedures between the UE and 5GC. In this case the UE and SMF may keep the MA PDU Session active over non-3GPP access with limited capabilities (no support for PDU Session Modification) ... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.8.3 Impacts on services, entities and interfaces | UE:
- Support for ATSSS using MPQUIC towards UPF without N3IWF/TNGF, using separate MPQUIC proxy address for 3GPP and non-3GPP accesses.
- Receives two MPQUIC Proxy address information items (instead of one in Rel-18) from the SMF: one each to be used by the QUIC client for QUIC paths established via 3GPP access and no... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.9 Solution #2.9: MPQUIC Connect-IP/Ethernet over Ethernet PDU Session Type | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.9.1 Description | This solution addresses KI#2.1.
This solution addresses the potential impact on Ethernet ROHC (Robust Header Compression) for Ethernet PDU Session over NG-RAN when IP tunnelling are used for the Ethernet MA-PDU Session.
Editor's note: Whether the solution for Ethernet PDU Session type can work on ROHC is FFS.
MPQUIC Co... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.9.2 Procedures | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.9.2.1 MA PDU Session Establishment with Ethernet PDU Session Type | Figure 6.2.9.2-1: PDU Session Establishment
1. The UE sends a PDU Session Establishment Request message with the PDU session type as Ethernet and includes the ATSSS capabilities as for Rel-18. In addition, if the UE supports any MPQUIC proxy protocols in the case of Ethernet PDU Session type, the UE includes the suppor... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.9.3 Impacts on services, entities and interfaces | UE:
- Support for MPQUIC proxy protocols for Ethernet PDU Session type.
- SM NAS enhancements to negotiate the support for MPQUIC proxy protocols (enhanced 5GSM capability, enhanced ATSSS container) for Ethernet PDU Session type.
- IKEv2 enhancements to negotiate the support MPQUIC proxy protocols (enhanced 5GSM capabi... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.10 Solution #2.10: MPQUIC steering functionality using TCP proxying over HTTP | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.10.1 Introduction | The solution in this clause addresses the objective of KI#2.1 for a QUIC-based steering functionality to allow the transport of TCP packets over multiple accesses between UE and UPF. It generalizes on the current solution for ATSSS Phase 3 [17] for proxying UDP packets over HTTP over MP QUIC and extends it to TCP traff... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.10.2 High-level Description | The key principles of the solution are summarized below.
- After the MA PDU Session establishment, the UE creates one or more multipath QUIC connections with the UPF. Each multipath QUIC connection is associated with a QoS flow, i.e. it carries the traffic mapped to a QoS flow.
- The UE operates as a connect-tcp client... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.10.3 Procedures | Figure 6.2.10.3-1 below depicts the key steps of the procedure that enables data traffic to be exchanged between the UE and UPF using the MPQUIC steering functionality. The figure shows a 1:1 relation between QUIC packets sent between UE and UPF and TCP payload segments received from the UE's application or from N6, bu... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.11 Solution #2.11: Coexistence between different proxying-over-HTTP solutions | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.11.1 Introduction | Up until Rel-18, there has been only one MPQUIC proxy mode, that is, the "connect-udp", which within the scope of ATSSS, enabled traffic steering, switching, and splitting of UDP traffic. Since there was only one proxy mode (connect-udp), it has been associated to one MPQUIC steering functionality, thus, there was a 1:... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.11.2 High-level Description | With the introduction of multiple MPQUIC proxying mechanisms (i.e. connect-udp, connect-tcp, connect-ip and connect-ethernet) to support different types of traffic (i.e. UDP, TCP, IP, Ethernet), there are two possible ways on how these mechanisms can co-exist:
a) Defining one MPQUIC steering functionality with multiple... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.12 Solution #2.12: NULL Encryption IPSec User Plane Tunnelling for MA PDU Session using MPQUIC based steering and switching | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.12.1 Description | This solution addresses the Key Issue#2.2 "Simplified ATSSS architecture over non-3GPP access" that related to eliminate IPSec tunnel encapsulation. |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.12.2 Procedures | As an example, we detail the procedure to establish user plane resources over untrusted non-3GPP access for a Multi-Access PDU Session using only MPQUIC based steering and switching functionality. We assume that other procedures follow a similar pattern in which the network once it determines that user plane resources ... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.12.3 Impacts on services, entities and interfaces | Editor's note: This clause captures impacts on existing 3GPP services, entities and interfaces.
This solution assumes as a prerequisite the implementation of the solutions addressing KI#2.1 in both UE and the network.
AMF:
- Supports extension of the N2 PDU Session signalling between the AMF and N3IWF with an optional ... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.13 Solution #2.13: Eliminate IPSec tunnel for UP | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.13.1 Description | This solution addresses the Key Issue#2.2 "Simplified ATSSS architecture over non-3GPP access" that related to eliminate IPSec tunnel encapsulation. |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.13.2 Procedures | Figure 6.2.13.2-1: PDU Session Establishment for UP w/o IPSec tunnel over non-3GPP access
0. The SMF is aware of the Tunnel Capabilities of the N3IWF/TNGF for UP, e.g. based on operator configuration.
1. The UE sends a PDU Session Establishment Request (Tunnel Capabilities) message for ATSSS to AMF. This message shall ... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 6.2.13.3 Impacts on services, entities and interfaces | SMF:
- Indicates N3IWF/TNGF to use another tunnel technology to stop IPSec SA creation for UP of PDU Session.
- Indicates UE to use another tunnel technology to stop using IPSec tunnel for UP of PDU Session over non-3GPP access.
N3IWF/TNGF:
- Support to use another tunnel technology indicated by network to stop IPSec S... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 7 Overall Evaluation | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 7.1 Overall Evaluation for DualSteer | Editor's note: This clause will provide evaluation of different solutions for DualSteer. |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 7.2 Overall Evaluation for ATSSS_Ph4 | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 7.2.1 Void | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 7.2.2 Evaluation for Key Issue #2.2: Simplified ATSSS architecture over non-3GPP access | The following solutions have been proposed for simplifying the overall architecture over non-3GPP access:
Table 7.2.2-1
Solution
Brief summary of the solution
Evaluation
#2.2
The UPF has a Public IP address,
UE establishes an IPSec with the ePDG collocated with UPF and perform authentication via AAA server.
UE establis... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 8 Conclusions | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 8.1 Conclusions for DualSteer | It is concluded that there is no normative work for KI#1.1, 1.2, 1.3, and 1.4 in Release 19. |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 8.2 Conclusions for ATSSS_Ph4 | |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 8.2.1 Conclusion for Key Issue #2.1 | a) New MPQUIC steering functionalities are defined:
- Multipath QUIC-IP (MPQUIC-IP) steering functionality based on CONNECT-IP [7] to tunnel IP packets between a client (UE) and a proxy (UPF) using HTTP/3 over MPQUIC;
- Multipath QUIC-Ethernet (MPQUIC-E) steering functionality based on CONNECT-Ethernet [8] to proxy Eth... |
557e33e967524f3273f1f0ba5f818ce9 | 23.700-54 | 8.2.2 Conclusions for Key Issue #2.2 | It is concluded that there is no normative work for KI#2.2 in Release 19. Annex A: Change history Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 2024-01 SA2#160-AH-e S2-2401316 - - - Proposed skeleton approved at SA2#160-AH-e 0.0.0 2024-01 SA2#160-AH-e - - - - Documented approved p-CR at S2#160... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 1 Scope | The present document is to investigate and identify potential architecture and system level enhancements to support additional scenarios and requirements for UAV (Uncrewed Aerial Vehicle) and UAM (Urban Air Mobility) including:
- Enhancement of NEF services to support service exposure and interactions between MNOs and ... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- Fo... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 3 Definitions of terms and abbreviations | |
7c76e660d457710d658498e24c37271e | 23.700-59 | 3.1 Terms | For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
No-transmit zones: Geographical area where aerial UE are not allowed to operate in a certain frequen... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
DAA Detect and Avoid
LDS Localized DAA Server
NTZ No-Transmit Zone
NWDAA Ne... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 4 Architectural Assumptions and Requirements | |
7c76e660d457710d658498e24c37271e | 23.700-59 | 4.1 Architectural Assumptions | The following architectural assumptions apply:
- For solutions to enable network-assisted/ground-based mechanism for DAA (Detect And Avoid),
- co-existence with and leveraging, to the extent possible, Direct DAA solutions specified in TS 23.256 [2] shall be considered.
- sensing related information is out of scope of t... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 4.2 Architectural Requirements | Editor's note: This clause provides list of architectural requirements, if needed.
- The existing procedures specified in TS 23.256 [2] should be reused as much as possible for solutions.
- Service exposure mechanisms defined in TS 23.256 [2] should be reused as much as possible.
The following architectural requirement... |
7c76e660d457710d658498e24c37271e | 23.700-59 | 5 Key Issues |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.