Content for TR 23.700-54 Word version: 19.0.0
1 Scope
2 References
3 Definitions of terms and abbreviations
3.1 Terms
3.2 Abbreviations
4 Architectural Assumptions and Requirements
4.1 Architectural Assumptions
4.2 Architectural Requirements
...
...
1 Scope p. 10
The scope of this Technical Report is to:
-
study and identify potential architecture and system level enhancements for the 5G system to support the operation of the DualSteer Device that is capable of traffic steering and switching of user data for different services across two 3GPP access networks. The study addresses the service requirements documented in TS 22.261 and focuses on various aspects of architecture and functional enhancements including:
- impacts on subscription;
- impacts on registration procedure; and
- impacts on session management procedure and policies.
- study how the MPQUIC steering functionality defined in Rel-18 ATSSS can be extended to be able to steer, switch, and split non-UDP traffic (TCP, IP, Ethernet traffic); and
- study whether and how an alternative architecture and system level enhancements for ATSSS that does not require the existing non-3GPP interworking/gateway function, i.e. N3IWF, TNGF.
2 References p. 10
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.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
[9]
[11]
[17]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 22.261: "Service requirements for the 5G system".
[3]
TS 23.501: "System architecture for the 5G System (5GS)".
[4]
TS 23.502: "Procedures for the 5G System (5GS)".
[5]
TS 23.503: "Policy and charging control framework for the 5G System (5GS); Stage 2".
[6]
RFC 9298: "Proxying UDP in HTTP".
[7]
RFC 9484: "Proxying IP in HTTP".
[8]
draft-ietf-masque-connect-ethernet-05: "Proxying Ethernet in HTTP".
RFC 9114: "Hypertext Transfer Protocol Version 3 (HTTP/3)".
[10]
draft-ietf-httpbis-connect-tcp-06: "Template-Driven HTTP CONNECT Proxying for TCP".
RFC 9297: "HTTP Datagrams and the Capsule Protocol".
[12]
RFC 9000: "QUIC - A UDP based Multiplexed and Secured Protocol".
[13]
RFC 9001: "Using TLS to Secure QUIC".
[14]
RFC 9002: "QUIC Loss Detection and Congestion Control".
[15]
RFC 9221: "An Unreliable Datagram Extension to QUIC".
[16]
draft-ietf-quic-multipath-12: "Multipath Extension for QUIC".
TR 23.700-53: "Study on access traffic steering, switching and splitting support in the 5G system architecture; Phase 3".
[18]
RFC 9369: "QUIC Version 2".
[19]
RFC 9220: "Bootstrapping WebSockets with HTTP/3".
[20]
TS 33.402: "3GPP System Architecture Evolution (SAE); Security aspects of non-3GPP accesses".
[21]
TS 29.500: "Technical Realization of Service Based Architecture; Stage 3".
[22]
RFC 4555: "IKEv2 Mobility and Multihoming Protocol (MOBIKE)".
[23]
TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode".
[24]
TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN)".
[25]
TS 32.421: "Telecommunication management; Subscriber and equipment trace; Trace concepts and requirements".
3 Definitions of terms and abbreviations p. 11
3.1 Terms p. 11
For the purposes of the present document, the terms given in TR 21.905 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.
Non-Integrated Non-3GPP Access:
a type of non-3GPP access network that provides direct IP connectivity between the UE and the UPF without any intermediate NF such as Non-3GPP InterWorking Function (N3IWF) and Trusted Non-3GPP Gateway Function (TNGF). When a UE is connected using Non-Integrated Non-3GPP Access, the UE data flows can be routed via this access to operator services.
3.2 Abbreviations p. 11
4 Architectural Assumptions and Requirements p. 11
4.1 Architectural Assumptions p. 11
4.1.1 Architectural Assumptions for DualSteer p. 11
Void.
4.1.2 Architectural Assumptions for ATSSS_Ph4 p. 11
The following general assumptions apply:
- The Rel-18 ATSSS as specified in TS 23.501, TS 23.502, and TS 23.503 are regarded as the baseline for this study.
- Current Non-3GPP InterWorking Function (N3IWF) and Trusted Non-3GPP Gateway Function (TNGF) are not used to simplify the operation over non-3GPP access.
- Any alternative architecture and system level enhancements would also be applicable for a UE behind an RG.
- Any new steering functionality shall be based on the multipath extensions of the QUIC protocols as defined in IETF.
- All ATSSS steering functionalities (existing and new) shall reside in the UE and in an UPF. Steering functionalities outside either of the UE or the UPF are not considered.
- Any new ATSSS capabilities specified for UE would be applicable for ATSSS-capable 5G-RGs, if endorsed by BFF and/or CableLabs; FN-RG are not in the scope of the study.
4.2 Architectural Requirements p. 12
4.2.1 Architectural Requirements for DualSteer p. 12
4.2.2 Architectural Requirements for ATSSS_Ph4 p. 12
- New ATSSS capabilities shall either be able to co-exist with the existing ATSSS capabilities or any dependencies between new and existing capabilities shall be explicitly defined.
- The benefit and drawback of new solutions compared to existing TNGF and N3IWF shall be analyzed before any conclusion on WT#3.
