Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 26.238  Word version:  16.6.2

Top   Top   None   None   Next
0…   4…

 

0  IntroductionWord‑p. 5
The Framework for Live Uplink Streaming (FLUS) is an enabler for live media streaming from a source entity to a sink entity. FLUS offers an IMS-based and a non-IMS-based instantiation. The IMS/MTSI-based instantiation enables the establishment of live media streaming between two UEs or between a source entity and a sink entity, within and across operator networks. Compared with MTSI, where limited types of QoS for speech or video media are used, FLUS can provide a wider range of QoS operation, e.g., in the maximum delay, available bandwidth or target packet loss rate.
In the non-IMS-based instantiation, it is possible to operate FLUS as a more generic framework that is controlled through a RESTful API and that supports other media plane protocols (i.e. not based on IMS or MTSI).
In addition to providing a wider range of QoS operation over radio links, other advanced functionalities of FLUS, such as the signalling of immersive media, can be used to complement existing 3GPP services.
Up

1  ScopeWord‑p. 6
The present document 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 this document.
When used as a generic framework, only the F-C procedures for establishing the FLUS session are required to be supported by the FLUS source and the FLUS sink entities, and no other feature or procedure specified in this 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 FLUS source and the FLUS sink entities are required to support the IMS control plane and media plane procedures, and the service quality is determined by the MTSI service policy.
The specification is written in a forward-compatible way in order to allow additions of media components and functionality in releases beyond Release 15.
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]
Recommendation ITU-R BS.2051-1 (06/2017): "Advanced Sound System for Programme Production".
[3]
ISO/IEC 23090-2:2019: "Information technology - Coded representation of immersive media - Part 2: Omnidirectional media format".
[4]
TS 26.114: "IP Multimedia Subsystem (IMS); Multimedia telephony; Media handling and interaction".
[5]
TS 26.235: "Transparent end-to-end Packet-switched Streaming Service (PSS); Protocols and codecs".
[6]
TS 24.147: "Conferencing using the IM Multimedia (IM) Core Network (CN) subsystem; Stage 3".
[7]
TS 23.003: "Numbering, addressing and identification".
[8]
TS 33.203: "3G security; Access security for IP-based services".
[9]
TS 33.210: "3G security; Network Domain Security (NDS); IP network layer security".
[10]
TS 33.328: "IP Multimedia Subsystem (IMS) media plane security".
[11]
RFC 7231:  "Hypertext transfer protocol (HTTP/1.1): Semantics and Content" (June 2014).
[12]
TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".
[13]
TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
[14]
TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications".
[16]
TS 26.501: "5G Media Streaming (5GMS); General description and architecture".
[17]
ISO/IEC DIS 23090-8: "Information technology -- Coded representation of immersive media -- Part 8: Network based media processing" (under development).
[18]
RFC 4574:  "The Session Description Protocol (SDP) Label Attribute" (August 2006).
[19]
TS 36.321: "Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification".
[20]
TS 38.321: "NR; Medium Access Control (MAC) protocol specification".
[21]
OMA-ERELD-DM-V1_2-20070209-A: "Enabler Release Definition for OMA Device Management, Approved Version 1.2".
[22]
TR 26.939: "Guidelines on the Framework for Live Uplink Streaming (FLUS)".
[23]
TS 26.511: "5G Media Streaming (5GMS); Profiles, codecs and formats".
[24]
RFC 7798  (2016): "RTP Payload Format for High Efficiency Video Coding (HEVC)"
[25]
TS 26.445: "Codec for Enhanced Voice Services (EVS); Detailed Algorithmic Description".
[26]
RFC 4867  (2007): "RTP Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs".
[27]
RFC 6416  (2011): "RTP Payload Format for MPEG-4 Audio/Visual Streams".
[28]
OASIS Standard, MQTT Version 5.0: https://docs.oasis-open.org/mqtt/mqtt/v5.0/mqtt-v5.0.html
[29]
TS 24.147: Conferencing using the IP Multimedia (IM); Core Network (CN) subsystem;
Up

3  Definitions and abbreviationsWord‑p. 7

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 FLUS source and a FLUS sink within which media content can be sent from the source to the sink.
Media session:
A subset or part of a FLUS session between a FLUS source and a FLUS sink including the duration to establish the Media Media session, the time period during which media content can be sent from the FLUS source to the FLUS sink and the duration to terminate the MMedia session. One or more MMedia sessions are delivered during a FLUS session. A MMedia session may be established and controlled by a well-defined control protocol.
Media stream:
The content sent from a FLUS source to a FLUS sink within a MMedia session.
Up

3.2  Symbols

For the purposes of the present document, the following symbols apply:
<symbol> <Explanation>

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
HMD
Head Mounted Display
IMS
IP Multimedia Subsystem
MO
Management Object
NBMP
Network Based Media Processing

Up   Top   ToC