TR 29.893
Study on IETF QUIC Transport for 5GC Service Based Interfaces

3GPP‑Page fToC_↓ Partial Content _→

V18.0.0 (Wzip) 2023/09 42 p.

Rapporteur:: Ms. Qi, Caixia
HuaWei Technologies Co., Ltd

full Table of Contents for TR 29.893 Word version: 18.0.0

each clause number in 'red' refers to the equivalent title in the Partial Content

Scope p. 6

References p. 6

Definitions, symbols and abbreviations p. 8

3.1	Definitions p. 8
3.2	Abbreviations p. 8

Architectural Baseline p. 8

Transport Protocol Features Required For 3GPP 5GC SBI p. 9

5.1

Introduction p. 9

5.2

Requirements from Transport Protocol for 3GPP 5GC SBI p. 9

5.3

Features of QUIC p. 10

5.3.1	General p. 10
5.3.2	Framing and Multiplexing p. 10
5.3.3	Improved Recovery and Acknowledgement p. 11
5.3.4	Encrypted and Integrity Protected Transport details p. 11
5.3.5	Connection Setup Improvements p. 11
5.3.6	0-RTT Data p. 12
5.3.7	Connection ID p. 12
5.3.8	Connection Migration p. 12
5.3.9	Stream Prioritization p. 13
5.3.10	Flow Control p. 13
5.3.11	Protocol Versioning p. 13
5.3.12	QUIC Extensibility p. 13
5.3.13	Connection Configuration p. 14
5.3.14	User-Land Implementations p. 14
5.3.15	Pluggable Sender Side Congestion Control p. 14
5.3.16	Checking that the QUIC connection is alive p. 14
5.3.17	62 bits stream identifiers p. 14
5.3.18	Running atop of UDP p. 15

5.4

Features of QUIC Applicable to 3GPP SBI p. 15

5.4.1	General p. 15
5.4.2	Framing and Multiplexing p. 15
5.4.3	Encrypted and Integrity Protected Transport details p. 15
5.4.4	Connection setup improvements p. 15
5.4.5	Connection ID and Connection Migration p. 16
5.4.6	Improved Recovery and Acknowledgement p. 16

5.5

Features of QUIC Not Applicable to 3GPP SBI p. 16

5.5.1	General p. 16
5.5.2	0-RTT DATA p. 16

5.6

Comparison of Applicable Features with Rel-15 Transport p. 17

HTTP/3 p. 20

Introduction p. 20

HTTP/3 Proxies p. 21

General p. 21

When NF Service Consumer Side Uses QUIC p. 22

6.2.2.1	Case A: Invoking http API Supporting Only TCP Transport p. 22
6.2.2.2	Case B: Invoking http API Supporting QUIC Transport p. 24
6.2.2.3	Case C: Invoking https API Supporting Only TCP Transport p. 25
6.2.2.4	Case D: Invoking https API Supporting QUIC Transport p. 26

6.2.3

When NF Service Consumer Side Uses TCP p. 27

6.2.3.1	Invoking http API Supporting QUIC Transport p. 27
6.2.3.2	Invoking https API Supporting QUIC Transport p. 27

6.3

Considerations for HTTP/3 p. 28

6.3.1	General p. 28
6.3.2	Connection setup and management p. 28
6.3.3	Streams, framing and multiplexing p. 28
6.3.4	Prioritization p. 29
6.3.5	Server Push p. 29
6.3.6	Compression (HPACK vs QPACK) p. 29

Key Requirements for Supporting QUIC p. 29

7.1	Introduction p. 29
7.2	Discovery of QUIC support p. 29
7.3	Discovery of NRF's Support for QUIC p. 30
7.4	Migration to QUIC p. 30
7.5	Support of Indirect Communication p. 30

Solutions for Key Requirements p. 30

8.1

Introduction p. 30

8.2

Solutions for Discovery of QUIC support p. 31

8.2.1	Using the Discovery Service of the NRF p. 31
8.2.2	Using Alt-Svc Header p. 31

8.3

Solutions for Discovery of NRF's Support for QUIC p. 32

8.3.1	Providing NRF Transport Capability from NSSF p. 32
8.3.2	Providing Remote PLMN NRF's Transport Capability during NF Discovery p. 32
8.3.3	Discovery Based On Local Configuration p. 32

8.4

Solutions for Migration to QUIC p. 33

8.4.1	Deployment Topologies to Introduce NF Services with QUIC Support p. 33
8.4.2	Steps to Follow When Introducing NF Services with QUIC Support p. 33
8.4.3	Use of QUIC by NF Service Consumers p. 33
8.4.4	Decommissioning TCP p. 33