Content for TR 26.804 Word version: 17.1.0
1 Scope p. 10
This Technical Report identifies and evaluates a set of potential improvements and extensions, referred to as key topics. The key topics are
- Content Preparation
- Traffic Identification
- Additional / New transport protocols
- Uplink media streaming
- Background traffic
- Content Aware Streaming
- Network Event usage
- Per-application-authorization
- Support for encrypted and high-value content
- Scalable distribution of unicast Live Services
- Document the above key topics in more detail, in particular how they relate to the 5GMS Architecture and protocols.
- Study collaboration scenarios between the 5G System and Application Provider for each of the key topics.
- Based on the 5GMS Architecture, develop one or more deployment architectures that address the key topics and the collaboration models.
- Map the key topics to basic functions and develop high-level call flows.
- Identify the issues that need to be solved.
- Provide candidate solutions (including call flows) for each of the identified issues.
- Coordinate work with other 3GPP groups e.g. SA2, SA3, SA5, and others as needed.
- Coordinate work with external organizations such as DASH-IF, CTA WAVE, ISO/IEC JTC29 WG3 (MPEG Systems), or IETF, as needed.
- Identify gaps and recommend potential normative work for stage-2 call flows and possibly stage-3.
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]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
Akamai Blog, "A QUICk Introduction to HTTP/3", April 2020, https://developer.akamai.com/blog/2020/04/14/quick-introduction-http3
[3]
Fielding, R., Nottingham, M., and J. Reschke, "HTTP/1.1", Work in Progress, Internet-Draft, draft-ietf-httpbis-messaging-13, 14 December 2020, http://www.ietf.org/internet-drafts/draft-ietf-httpbis-messaging-13.txt
[4]
Belshe, M., Peon, R., and M. Thomson, Ed., "Hypertext Transfer Protocol Version 2 (HTTP/2)", RFC 7540, May 2015, https://www.rfc-editor.org/info/rfc7540
[5]
draft-ietf-quic-http-34 "Hypertext Transfer Protocol Version 3 (HTTP/3)", February 2021
[6]
D. Bhat, A. Rizk, and M. Zink, "Not so QUIC: A Performance Study of DASH over QUIC," NOSSDAV'17: Proceedings of the 27th Workshop on Network and Operating Systems Support for Digital Audio and VideoJune 2017 Pages 13-18 https://doi.org/10.1145/3083165.3083175
[7]
AWS: "Achieving Great Video Quality Without Breaking the Bank", Streaming Media June 2019, https://pages.awscloud.com/rs/112-TZM-766/images/GEN elemental-wp-achieving-great-video-quality-without-breaking-the-bank.pdf
[8]
Netflix, "Optimized shot-based encodes: Now Streaming!", Netflix Blog, May 2018, https://netflixtechblog.com/optimized-shot-based-encodes-now-streaming-4b9464204830
[9]
DASH-IF/DVB: "Report on Low-Latency Live Service with DASH", July 2017, available here: https://dash-industry-forum.github.io/docs/Report%20on%20Low%20Latency%20DASH.pdf
[10]
DASH-IF: "IOP Guidelines v5, Low-latency Modes for DASH", available here: https://dash-industry-forum.github.io/docs/CR-Low-Latency-Live-r8.pdf
[11]
ISO/IEC 23009-1: "Information technology - Dynamic adaptive streaming over HTTP (DASH) - Part 1: Media presentation description and segment formats".
[12]
RFC 8673: "HTTP Random Access and Live Content".
[13]
TR 26.939: "Guidelines on the Framework for Live Uplink Streaming (FLUS)".
[14]
TS 26.238: "Uplink Streaming".
[15]
TS 26.501: "5G Media Streaming (5GMS); General description and architecture".
[16]
TS 26.512: "5G Media Streaming (5GMS); Protocols".
[17]
ISO/IEC 13818-1:2019: "Information technology - Generic coding of moving pictures and associated audio information - Part 1: Systems".
[18]
SCTE 35 2020: "Digital Program Insertion Cueing Message", https://www.scte.org/pdf-redirect/?url=https://scte-cms-resource-storage.s3.amazonaws.com/SCTE-35-2020_notice-1609861286512.pdf
[19]
ISO/IEC 23000-19:2020: "Information technology - Multimedia application format (MPEG-A) -Part 19: Common media application format (CMAF) for segmented media".
[20]
ISO/IEC 23009-1:2019/DAMD1: "Information technology - Dynamic adaptive streaming over HTTP (DASH) - Part 1: Media presentation description and segment formats - Amendment 1: CMAF support, events processing model and other extensions".
[21]
VSF TR-06-01:2020, "RIST Simple Profile", https://vsf.tv/download/technical_recommendations/VSF_TR-06-1_2020_06_25.pdf
[22]
VSF TR-06-02: "RIST Main Profile", https://www.videoservicesforum.org/download/technical_recommendations/VSF_TR-06-2_2020_03_24.pdf
[23]
TS 23.501: "System architecture for the 5G System (5GS)".
[24]
TS 23.502: "Procedures for the 5G System (5GS)".
[25]
TS 29.517: "5G System; Application Function Event Exposure Service; Stage 3".
[26]
TS 29.244: "Interface between the Control Plane and the User Plane nodes; Stage 3".
[27]
RFC 6733: "Diameter Base Protocol".
[28]
TS 29.514: "5G System; Policy and Charging Control over Rx reference point; Stage 3".
[29]
RFC 7657: "Differentiated Services (Diffserv) and Real-Time Communication", November 1995.
[30]
RFC 3168: "The Addition of Explicit Congestion Notification (ECN) to IP", September 2001.
[31]
C. Krasic, M. Bishop, and A. Frindell, Ed., draft-ietf-quic-qpack-21, "QPACK: Header Compression for HTTP/3", Work in Progress, Internet-Draft, 2 February 2021.
[32]
RFC 9000: "QUIC: A UDP-Based Multiplexed and Secure Transport", May 2021.
[33]
RFC 9001: "Using TLS to Secure QUIC", May 2021.
[34]
IETF, RFC 9002: "QUIC Loss Detection and Congestion Control", May 2021.
[35]
RFC 5681: "TCP Congestion Control".
[36]
M. Kuehlewind and B. Trammell, draft-ietf-quic-manageability-11, "Manageability of the QUIC Transport Protocol", Work in Progress, Internet-Draft, 30 June 2021.
[37]
N. Cardwell et. al. "BBR Updates: Internal Deployment, Code, Draft Plans", 9 March 2021, https://datatracker.ietf.org/meeting/110/materials/slides-110-iccrg-bbr-updates-00.pdf
[38]
ETSI TS 103 799: "Publicly Available Specification (PAS); DASH-IF Content Protection Information Exchange Format".
[39]
ISO/IEC JTC1/SC29/WG11/N19062 23090-8 FDIS: "MPEG-I: Network-based Media Processing - Network-Based Media Processing Specification".
[40]
TS 26.247: "Transparent end-to-end Packet-switched Streaming Service (PSS); Progressive Download and Dynamic Adaptive Streaming over HTTP (3GP-DASH)".[41] 3GPP TS 23.503: "Policy and charging control framework for the 5G System (5GS); Stage 2".
[42]
TS 29.514: "5G System; Policy Authorization Service; Stage 3".
[43]
TS 29.522: "5G System; Network Exposure Function Northbound APIs; Stage 3".
[44]
TS 29.122: "T8 reference point for Northbound APIs".
[45]
TS 29.512: "5G System; Session Management Policy Control Service; Stage 3".
[46]
TS 26.803: "5G Media Streaming (5GMS); Architecture extensions".
[47]
TS 23.558: "Architecture for enabling Edge Applications (EA)".
[48]
TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services".
[49]
Tdoc S4-210723: "Generic architecture for data collection and reporting", submission from BBC, Dolby Laboratories Inc., LM Ericsson and Qualcomm Incorporated to SA4#114-e, May 19-28, 2021.
[50]
Tdoc S2-2103267: "Extension of Naf_EventExposure for observed service experience data collection from UEs", CR from InterDigital to SA2#144e, Apr 12-16, 2021.
[51]
TS 26.114: "IP Multimedia Subsystem (IMS); Multimedia telephony; Media handling and interaction".
[52]
Tdoc S2-2104496: "Extension of Naf_EventExposure for observed service experience data collection from UEs", CR from Qualcomm Incorporated to SA2#145e, May 17-28, 2021.
[53]
TS 26.118: "Virtual Reality (VR) profiles for streaming applications".
[54]
TS 26.346: "Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs".
[55]
TS 29.554: "Background Data Transfer Policy Control Service; Stage 3".
[56]
TS 28.530: "Management and orchestration; Concepts, use cases and requirements".
[57]
TS 28.531: "Management and orchestration; Provisioning".
[58]
TS 28.532: "Management and orchestration; Generic management services".
[59]
TS 28.533: "Management and orchestration; Architecture framework".
[60]
TS 28.540: "Management and orchestration; 5G Network Resource Model (NRM); Stage 1".
[61]
TS 28.541: "Management and orchestration; 5G Network Resource Model (NRM); Stage 2 and stage 3".
[62]
TS 28.542: "Management and orchestration of networks and network slicing; 5G Core Network (5GC) Network Resource Model (NRM); Stage 1".
→ to date, still a draft
[63]
→ to date, still a draft
TS 28.543: "Management and orchestration of networks and network slicing; 5G Core Network (5GC) Network Resource Model (NRM); Stage 2 and stage 3".
→ to date, still a draft
[64]
→ to date, still a draft
TS 28.545: "Management and orchestration; Fault Supervision (FS)".
[65]
TS 28.546: "Management and orchestration of networks and network slicing; Fault Supervision (FS); Stage 2 and stage 3".
→ to date, still a draft
[66]
→ to date, still a draft
TS 28.552: "Management and orchestration; 5G performance measurements".
[67]
TS 28.554: "Management and orchestration; 5G end to end Key Performance Indicators (KPI)".
[68]
TS 23.434: "Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows".
[69]
TS 23.700-99: " Study in Network slice capability exposure for application layer enablement (NSCALE)".
[70]
TS 29.520: " 5G System; Network Data Analytics Services; Stage 3".
[71]
TR 23.700-40: "Study on enhancement of network slicing; Phase 2".
[72]
TS 26.531: "Data Collection and Reporting; General Description and Architecture".
[73]
TR 26.802: "Multicast Architecture Enhancement for 5G Media Streaming".
[74]
RFC 822: "STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES", August 13, 1982.
[75]
RFC 1521: "MIME (Multipurpose Internet Mail Extensions)", September 1993.
[76]
RFC 2474: "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers".
[77]
RFC 2475: "An Architecture for Differentiated Services".
[78]
RFC 3246: "An Expedited Forwarding PHB (Per-Hop Behavior)".
[79]
RFC 2597: "Assured Forwarding PHB Group".
[80]
S. Hurst, draft-hurst-quic-rtp-tunnelling: "QRT: QUIC RTP Tunnelling", Internet-Draft, Work in Progress.
[81]
J. Ott and M. Engelbart, draft-engelbart-rtp-over-quic: "RTP over QUIC", Internet-Draft, Work in Progress.
[82]
SRT Alliance, "Secure Reliable Transport (SRT) Protocol", https://github.com/Haivision/srt
[83]
M.P. Sharabayko and M.A. Sharabayko, draft-sharabayko-srt-over-quic-00,"Tunnelling SRT over QUIC", Internet-Draft, Work in Progress, 28 July 2021.
[84]
Robin Marx, Luca Niccolini, Marten Seemann, draft-ietf-quic-qlog-main-schema-01, "Main logging schema for qlog", Internet-Draft, Work in Progress, 25 October 2021.
[85]
Robin Marx, Luca Niccolini, Marten Seemann, draft-ietf-quic-qlog-h3-events-00, "HTTP/3 and QPACK event definitions for qlog", Internet-Draft, Work in Progress, 10 June 2021.
[86]
Robin Marx, Luca Niccolini, Marten Seemann, draft-ietf-quic-qlog-quic-events-00, "QUIC event definitions for qlog", Internet-Draft, Work in Progress, 10 June 2021.
[87]
Roger Pantos and William May, Jr., "HTTP Live Streaming", RFC 8216, August 2017.
[88]
TR 26.925: "Typical traffic characteristics of media services on 3GPP networks".
[89]
TR 26.917: "Multimedia Broadcast Multicast Services (MBMS) and Packet-switchedStreaming Service (PSS) enhancements to support television services".
[90]
"DASH-IF WebRTC-based Streaming", https://dashif.org/news/webrtc/
[91]
RFC 6749: "The OAuth 2.0 Authorization Framework".
[92]
RFC 6750: "The OAuth 2.0 Authorization Framework: Bearer Token Usage".
[93]
TS 33.501: "Security architecture and procedures for 5G System".
[94]
TS 26.531: "Data Collection and Reporting; General Description and Architecture".
[95]
TS 26.532: "Data Collection and Reporting; Protocols and Formats".
3 Definitions of terms, symbols and abbreviations p. 14
3.1 Terms p. 14
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. 14
Void.
3.3 Abbreviations p. 14
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.
CDN
Content Delivery Network
DS
Differentiated Service
FAR
Forward Action Rule
MAR
Multi-Access Rule
PDR
Packet Detection Rule
PFCP
Packet Forwarding Control Protocol
QER
QoS Enforcement Rule
QLOG
QUIC Logging
PHB
Per-Hop Behaviour
PFD
Packet Flow Description
SDF
Service Data Flow
URL
Uniform Resource Locator
URR
Usage Reporting Rule
