Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TR 26.939  Word version:  17.0.0

Top   Top   None   None   Next
0…   6…

 

0  IntroductionWord‑p. 6

The present document describes the ways to use the Framework for Live Uplink Streaming to setup services that allow the end user to stream live feeds into the network or to a second party.

1  ScopeWord‑p. 7

The present document describes how to use the Framework for Live Uplink Streaming (FLUS) to stream live feeds to the network or to a second party. It describes the usage of both variants: the IMS-based and the non-IMS-based framework to carry regular 2D and 360 degrees video feeds. It also describes a set of instantiations for the non-IMS-based solution as the FLUS User Plane has been left for the discretion of implementations to support a diversity of requirements that require different instantiations of the user plane.
Up

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.
  • 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]
TS 26.238: "Uplink streaming".
[3]
ISO 14496-12: "Information technology - Coding of audio-visual objects - Part 12: ISO base media file format".
[4]
ISO 23000-19: "Information technology - Coding of audio-visual objects - Part 19: Common media application format (CMAF) for segmented media".
[5]
TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
[6]
TS 23.501: "System Architecture for the 5G System (5GS)".
[7]
ISO 14496-12: "Information technology - Coding of audio-visual objects - Part 12: ISO base media file format".
[8]
ISO 23008-1: "Information technology - High efficiency coding and media delivery in heterogeneous environments - Part 1: MPEG media transport (MMT) ".
[9]
ISO 23008-1: 2nd Edition AMD2, "Enhancements for Mobile Environments".
[10]
RFC 6455:  "The WebSocket Protocol".
[11]
RFC 5234  (2008): "Augmented BNF for Syntax Specifications: ABNF", D. Crocker, P. Overell.
[12]
RFC 6817:  "Low Extra Delay Background Transport (LEDBAT) ".
[13]
ISO 23000-19: "Common Media Application Format for Segmented Media (CMAF) ".
[14]
RFC 7230:  "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing".
[15]
RFC 7540:  "Hypertext Transfer Protocol Version 2 (HTTP/2) ".
[16]
TS 26.114: "IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction".
[17]
TS 26.247: "Transparent end-to-end Packet-switched Streaming Service (PSS); Progressive Download and Dynamic Adaptive Streaming over HTTP (3GP-DASH)".
[18]
TS 26.244: "Transparent end-to-end packet-switched streaming service (PSS); 3GPP file format (3GP)".
[19]
TS 23.203: "Policy and Charging Control Architecture".
[20]
DVB CM-AVC Report on Low-Latency Live Service with DASH.
[21]
"Facebook (A)Live? Are live social broadcasts really broadcasts?", by A. Raman, G. Tyson and N. Sastry, WWW 2018: The 2018 Web Conference, April 23-28, 2018, Lyon, France, https://arxiv.org/pdf/1803.02791.pdf.
[22]
TS 26.347: "Multimedia Broadcast/Multicast Service (MBMS); Application Programming Interface and URL".
[23]
TR 26.985: "Vehicle-to-everything (V2X) media handling and interaction".
[24]
ISO/IEC 23090-8 Information technology - Coded representation of immersive media - Part 8: Network based media processing
Up

3  Definitions and abbreviationsWord‑p. 8

3.1  Definitions

For the purposes of the present document, the terms and definitions 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.
FLUS session:
A logical association between a source and a sink within which media content can be sent from the source to the sink.
Media session
A subset or part of a FLUS session including the duration to establish the media session, the time period during which media content can be sent from FLUS source to FLUS sink and the duration to terminate the media session.
Media stream:
The content sent from a FLUS source to a FLUS sink within a media session.
Up

3.3  Abbreviations

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.
FLUS
Framework for Live Uplink Streaming
MCC
Mobile Country Code
MNC
Mobile Network Code
NBMP
Network Based Media Processing

4  FLUS Overview

FLUS defines a FLUS source entity and a FLUS sink entity that can support point-to-point transmission of speech/audio, video, and text. It defines media handling (e.g., signalling, transport, packet-loss handling, and adaptation). The goal is to ensure a reliable and interoperable service with a predictable media quality while allowing for flexibility in the service offerings.
A FLUS source entity, which may be embedded in a single UE, or distributed among a UE and separate audio-visual capture devices, may support all or a subset of the features specified in the present document.
When used as a generic framework, only the F-C procedures for establishing the FLUS session are required to be supported by the source and sink entities, and no other feature or procedure specified in the present document is mandated. Impact on the service quality and network capacity is left to the discretion of the implementation and the service utilizing the framework. For example, configuration of media formats and codecs follows the requirements of the respective service.
When offered as part of a 3GPP IMS/MTSI service, the source and sink are required to support the IMS control plane and media plane procedures, and the service quality is determined by the MTSI service policy.
When offered as part of a 3GPP non-IMS/MTSI instantiation, the service may make use of the Network Assistance feature for uplink services. For the IMS instantiation of FLUS, the source and sink may make use of Access Network Bitrate Recommendation (ANBR) functionality as defined in clause 10.7 of TS 26.114.
The present document provides guidelines for the usage of FLUS and describes different user plane instantiations that can be used with FLUS.
Up

5  Guidelines for IMS-based FLUSWord‑p. 9

Guidelines for the usage of FLUS in the IMS-based operation mode are not provided in the present document.

Up   Top   ToC