Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TR 23.700-93  Word version:  17.0.0

Top   Top   None   None   Next
1…   5…   7… 
1 Scope  2 References  3 Definitions of terms, symbols and abbreviations  3.1 Terms  3.2 Symbols  3.3 Abbreviations  4 Architectural Assumptions and Requirements 
...

 

1  Scope  p. 8

This Technical Report investigates following aspects for UEs that can establish a MA PDU Session to 5GC over both 3GPP and non-3GPP accesses:
  • Whether and how to support additional steering mode(s), with potential PMF extensions if needed.
  • Whether and how to support additional steering functionality(ies). Proposed solutions shall be based on IETF protocols or extension of such protocols (i.e. QUIC/MP-QUIC).
  • Whether and how to support multi-access PDU session with one 3GPP access leg over EPC and the other access leg over non-3GPP access 5GS.
Up

2  References  p. 8

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]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
IEEE Std 802.11-2012: "IEEE Standard for Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications".
[3]
TS 23.501: "System Architecture for the 5G System; Stage 2".
[4]
TS 23.502: "Procedures for the 5G System; Stage 2".
[5]
TS 23.503: "Policy and Charging Control Framework for the 5G System; Stage 2".
[6]
draft-ietf-quic-transport-00:  "QUIC: A UDP-Based Multiplexed and Secure Transport".
[7]
draft-ietf-quic-recovery-00:  "QUIC Loss Detection and Congestion Control".
[8]
draft-ietf-quic-datagram-00:  "An Unreliable Datagram Extension to QUIC".
[9]
draft-piraux-quic-tunnel-00:  "Tunneling Internet protocols inside QUIC".
[10]
draft-deconinck-quic-multipath-00:  "Multipath Extensions for QUIC (MP-QUIC)".
[11]
RFC 1928:  "SOCKS Protocol Version 5".
[12]
TS 23.316: "Wireless and wireline convergence access support for the 5G System (5GS); Stage 2".
[13]
TR 23.793: "Study on access traffic steering, switch and splitting support in the 5G System (5GS) architecture".
[14]
TS 33.210: "3G security; Network Domain Security (NDS); IP network layer security".
[15]
RFC 3393:  "IP Packet Delay Variation Metric for IP Performance Metrics (IPPM)".
[16]
RFC 3550:  " RTP: A Transport Protocol for Real-Time Applications".
[17]
RFC 5481:  " Packet Delay Variation Applicability Statement".
[18]
draft-ietf-quic-tls-00:  "Using Transport Layer Security (TLS) to Secure QUIC".
[19]
draft-ietf-masque-connect-udp-00:  "The CONNECT-UDP HTTP Method".
[20]
draft-westerlund-masque-transport-issues-00:  "Transport Considerations for IP and UDP Proxying in MASQUE".
[21]
TS 29.512: "5G System; Session Management Policy Control Service; Stage 3".
[22]
TS 29.244: "Interface between the Control Plane and the User Plane nodes".
[23]
TS 24.193: "5G System; Access Traffic Steering, Switching and Splitting (ATSSS); Stage 3".
[24]
TS 29.214: "Policy and charging control over Rx reference point".
[25]
draft-ietf-quic-invariants-00:  "Version-Independent Properties of QUIC".
[26]
draft-pauly-masque-quic-proxy-00:  "QUIC-Aware Proxying Using CONNECT-UDP".
[27]
draft-ietf-masque-ip-proxy-reqs-00:  "Requirements for a MASQUE Protocol to Proxy IP Traffic".
Up

3  Definitions of terms, symbols and abbreviations  p. 9

3.1  Terms  p. 9

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.

3.2  Symbols  p. 9

For the purposes of the present document, the following symbols apply:

3.3  Abbreviations  p. 10

For the purposes of the present document, the abbreviations given in TR 21.905 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.

4  Architectural Assumptions and Requirements  p. 10

For all objectives, the architectural requirements and assumption include:
  • NG RAN, W-5GAN and any 5G AN shall not be impacted.
  • The study is restricted to ATSSS support for traffic routed over one 3GPP access and one non-3GPP access.
  • The study uses 5GS Rel-16 ATSSS as a starting point: MA PDU Session shall be reused.
  • Any additional steering functionality shall be based on IETF protocols or extensions of such protocols (i.e. QUIC/MP-QUIC [10]), any differences from the existing IETF drafts shall be clearly specified and minimized.
  • the Rel-17 ATSSS work applies also to 5G-RG.
For the support of additional steering mode(s) or of additional steering functionality(ies), the architectural requirements and assumptions include also:
  • Any additional steering functionalities in the User Plane should reside in UE and UPF as shown in Figure 4-1 below.
Copy of original 3GPP image for 3GPP TS 23.700-93, Fig. 4-1: Architecture assumption for ATSSS_Ph2 support
Figure 4-1: Architecture assumption for ATSSS_Ph2 support
(⇒ copy of original 3GPP image)
Up

4.1  Architecture Assumptions  p. 10

In this release, for a GBR QoS Flow of MA PDU Session, it is assumed that the SMF provides a QoS profile to a single access network at a given time.

4.2  Architectural Requirements  p. 10

Up   Top   ToC