|
TECHNICAL REPORT
Universal Mobile Telecommunications System (UMTS);
LTE;
5G;
Guidelines on the Framework for Live Uplink Streaming (FLUS)
(3GPP TR 26.939 version 15.1.0 Release 15)
---------------------- Page: 1 ----------------------
3GPP TR 26.939 version 15.1.0 Release 15 1 ETSI TR 126 939 V15.1.0 (2018-10)
Reference
RTR/TSGS-0426939vf10
Keywords
5G,LTE,UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
The present document can be downloaded from:
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
If you find errors in the present document, please send your comment to one of the following services:
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.
© ETSI 2018.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
3GPP and LTE are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M logo is protected for the benefit of its Members.
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
---------------------- Page: 2 ----------------------
3GPP TR 26.939 version 15.1.0 Release 15 2 ETSI TR 126 939 V15.1.0 (2018-10)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Foreword
This Technical Report (TR) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or
GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.
The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under
.
Modal verbs terminology
In the present document "should", "should not", "may", "need not", "will", "will not", "can" and "cannot" are to be
interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
---------------------- Page: 3 ----------------------
3GPP TR 26.939 version 15.1.0 Release 15 3 ETSI TR 126 939 V15.1.0 (2018-10)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 5
Introduction . 5
1 Scope . 6
2 References . 6
3 Definitions and abbreviations . 7
3.1 Definitions . 7
3.3 Abbreviations . 7
4 FLUS Overview . 7
5 Guidelines for IMS-based FLUS . 7
6 Guidelines for non-IMS-based FLUS . 8
6.1 Use Case: Sharing to a Social Network Service . 8
6.1.1 Use Case Description . 8
6.1.2 Potential Realization in FLUS . 8
6.2 Use Case: Live uplink video stream from drones or moving vehicles . 8
6.2.1 Use Case Description . 8
6.3 Use Case: Breaking-News reporter . 9
6.3.1 Use Case Description . 9
6.4 Use Case: Immersive media conversations . 9
6.4.1 Description . 9
7 FLUS User Plane Instantiations . 9
7.1 Non-IMS-based User Plane Instantiations . 9
7.1.1 Introduction. 9
7.1.2 fMP4-based Instantiations . 9
7.1.2.1 Introduction . 9
7.1.3 fMP4 over MMTP Instantiation. 10
7.1.3.1 General . 10
7.1.3.2 MMTP Signaling . 10
7.1.3.3 Synchronization . 11
7.1.3.4 Session Initiation and Description . 12
7.1.4 fMP4-based Instantiation with HTTP Delivery. . 12
7.1.4.1 General Description . 12
7.1.4.2 Rate Adaptation . 14
7.1.5 fMP4-based Instantiation using multiple segments per track . 14
7.1.5.1 General Description . 14
8 Example FLUS Workflows . 15
8.1 Example Workflow using F-U MMTP . 15
8.2 Example Call Flow for fragmented MP4 with HTTP Delivery . 16
8.2.1 Assumptions . 16
8.2.2 CMAF Format Example . 18
9 Guidelines for QoS usage for FLUS . 20
9.1 Use-Case introduction . 20
9.2 Discussion of the 3GPP QoS Framework . 21
9.2.1 Introduction. 21
9.2.2 Architecture . 21
9.2.3 Relevant 3GPP sections . 22
9.2.4 Usage of 3GPP QoS parameters . 23
9.2.5 Desired QoS flow behavior . 24
ETSI
---------------------- Page: 4 ----------------------
3GPP TR 26.939 version 15.1.0 Release 15 4 ETSI TR 126 939 V15.1.0 (2018-10)
Annex A: Immersive media signalling . 26
A.1 General . 26
A.2 Audio . 26
A.3 Video . 26
A.4 Examples of SDP offers and answers . 27
A.4.1 H.264 (AVC), H.265 (HEVC), and EVS . 27
Annex B: Change history . 29
History . 30
ETSI
---------------------- Page: 5 ----------------------
3GPP TR 26.939 version 15.1.0 Release 15 5 ETSI TR 126 939 V15.1.0 (2018-10)
Foreword
This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
Introduction
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.
ETSI
---------------------- Page: 6 ----------------------
3GPP TR 26.939 version 15.1.0 Release 15 6 ETSI TR 126 939 V15.1.0 (2018-10)
1 Scope
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.
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] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP 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] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal
Terrestrial Radio Access Network (E-UTRAN) access".
[6] 3GPP TS 23.501: "System Architecture for the 5G System".
[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)".
nd
[9] ISO 23008-1: 2 Edition AMD2, "Enhancements for Mobile Environments".
[10] IETF RFC 6455: "The WebSocket Protocol".
[11] IETF RFC 5234 (2008): "Augmented BNF for Syntax Specifications: ABNF", D. Crocker, P.
Overell.
[12] IETF RFC 6817: " Low Extra Delay Background Transport (LEDBAT)".
[13] ISO 23000-19: "Common Media Application Format for Segmented Media (CMAF)”.
[14] IETF RFC 7230: "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing”.
[15] IETF RFC 7540: "Hypertext Transfer Protocol Version 2 (HTTP/2)”.
ETSI
---------------------- Page: 7 ----------------------
3GPP TR 26.939 version 15.1.0 Release 15 7 ETSI TR 126 939 V15.1.0 (2018-10)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following
apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP
TR 21.905 [1].
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.
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An
abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in
3GPP TR 21.905 [1].
FLUS Framework for Live Uplink Streaming
MCC Mobile Country Code
MNC Mobile Network Code
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.
The present document provides guidelines for the usage of FLUS and describes different user plane instantiations that
can be used with FLUS.
5 Guidelines for IMS-based FLUS
Guidelines for the usage of FLUS in the IMS-based operation mode are not provided in the present document.
ETSI
---------------------- Page: 8 ----------------------
3GPP TR 26.939 version 15.1.0 Release 15 8 ETSI TR 126 939 V15.1.0 (2018-10)
6 Guidelines for non-IMS-based FLUS
6.1 Use Case: Sharing to a Social Network Service
6.1.1 Use Case Description
In this example scenario, a user is sharing a 360 degree video that is being captured through a VR camera and sent as a
fish eye, side-by-side 2D video. The 360 video stream is shared with a FLUS Sink in the network that relays the stream
to a popular social network service (SNS).
6.1.2 Potential Realization in FLUS
Note: There may be two or more realizations: (1) The FLUS Sink is a transport layer proxy and forwards encrypted
traffic to the SNS. (2) The FLUS Sink offers post-processing and forwards the post processed traffic to
the SNS or to distribution.
Once the user selects to start sharing, the UE discovers an appropriate FLUS Sink that supports the specific SNS and
that can stitch the fish eye into a 360 video and transcode the content to match the distribution format. The UE decides
to use RTMP for this session, so it also verifies that the FLUS Sink is capable of receiving RTMP streams.
For the discovery, the UE checks the FLUS OMA DM Management Object first but it fails to find a FLUS Sink that
supports the required capabilities. It then uses the pre-configured FLUS Sink discovery link to send an HTTP POST
request:
http://flus.mnc.mcc.pub.3gppnetwork.org/flus/v1.0/sinks/
In the body of the POST request, the UE includes a JSON or XML document that describes the required capabilities.
The network replies with a short list of FLUS Sinks that support the desired capabilities. The UE then randomly picks
one of the FLUS Sinks and queries its capabilities using the Sink's URL and the path "/flus/v1.0/capabilities". The
response is a JSON or XML document that describes all capabilities of the Sink.
The UE proceeds then to FLUS session creation, which returns a session identifier. The session creation request may
contain some configuration information or the UE may do that in a separate request. As part of the configuration, the
FLUS Source may include a workflow description that requests the Sink to perform VR Stitching, transcoding, and
distribution to the SNS.
Upon successful session creation and configuration, the UE connects to the provided link and starts sending the RTMP
stream to the Sink. The Sink will perform the requested processing and distribution on behalf of the Source. It may also
request the network to allocate appropriate QoS for the lifetime of the session.
When the user presses the stop button, the FLUS Sink will send a termination request to end the session.
6.2 Use Case: Live uplink video stream from drones or moving
vehicles
6.2.1 Use Case Description
The media producer for an event is using drone-mounted-360 cameras or other moving vehicles like F1 cars, sailing
boats or bicycles to capture scenes from more innovative angles. The drone is flown using line of sight, i.e. the drone
pilot has direct visual contact to the drone. Other vehicles may have the driver / pilot on-board.
The live video is streaming to the live ingest server and then used together with other camera feeds in a live TV
broadcast.
In particular for battery powered cameras, it may be beneficial to avoid processing like 360 video stitching on the
device. Instead, it may be beneficial to leverage network based post processing functions, e.g. multiple video streams
are transmitted and the stitching function is executed in the network.
Use-Case example: An event-organizer plans to use multiple drone mounted-camera to capture live video from an
event. All live video streams should be routed to an editing facility, where a program direct decides on the sequencing
of live video into a single linear program. The media source of each drone is configured with their own target quality
ETSI
---------------------- Page: 9 ----------------------
3GPP TR 26.939 version 15.1.0 Release 15 9 ETSI TR 126 939 V15.1.0 (2018-10)
(bitrate) and target delay. Each media source is configured with a unique media sink so that the program director can
identify each media source.
Note, this use-case can be seen generic so that the camera is not limited to be "drone mounted" but can be mounted to
any devices, including stationary objects.
6.3 Use Case: Breaking-News reporter
6.3.1 Use Case Description
A News Corporation uses 5G and mobile equipment to speed up and simplify their breaking-news operations. Either,
professional cameras are equipped with 5G uplink streaming modems, or regular smartphones (with external
microphones) are used for video capturing. The universally available 3GPP coverage is used to stream the live video
(with configurable, low delay) from the breaking news scene into the broadcast operation studio.
A news corporation negotiates a service level agreement with an operator so that a set of reporters can do sequential or
simultaneous live reports. The general frame agreement between the news corporation and the MNO foresees, that each
reporter can determine its own maximal video quality (measured in bit per sec). Each reporter should set its own
quality, but some reporters are allowed to provider higher quality (i.e. use higher bitrates) than others.
6.4 Use Case: Immersive media conversations
6.4.1 Description
In this scenario, streams of 360 video and multi-channel audio are transmitted from a media sender to a media receiver,
as illustrated in Figure 1, which at the receiver side, are projected on a screen or a HMD, and played out with
loudspeakers or a headphone. In the other direction, video bit-streams of lower quality or resolution are transmitted to
show the sender how the far-end user is watching and hearing the video and audio. A session is used to provide two-
way real-time voice conversation. The 360 video and multi-channel audio are synchronized but arrives slightly later
than the speech frames captured at similar times.
7 FLUS User Plane Instantiations
7.1 Non-IMS-based User Plane Instantiations
7.1.1 Introduction
This clause describes a set of instantiations for the generic FLUS User Plane that is not based on IMS.
7.1.2 fMP4-based Instantiations
7.1.2.1 Introduction
All instantiations of this clause are based on the fragmented ISOBMFF [3] format which is profiled by CMAF [4]. The
following description summarizes the used media format used in the present document:
1) Each media component is formatted as a CMAF Track.
2) Each CMAF Track starts with a CMAF Header followed by one or more CMAF Fragments. A CMAF Fragment
contains one or more CMAF Chunks. Note that CMAF requires that only the first CMAF chunk of a CMAF
fragment is constrained to be an adaptive switching point. All subsequent CMAF Chunks do not need to contain
any service access point.
3) When CMAF Fragments contain more than one CMAF chunk, it is beneficial that the first CMAF Chunk of the
CMAF Fragment is preceded by a SegmentTypeBox that includes the compatible_brands 'cmfl', 'cmff'.
Note that the present document only considers the CMAF file format specific features.
ETSI
---------------------- Page: 10 ----------------------
3GPP TR 26.939 version 15.1.0 Release 15 10 ETSI TR 126 939 V15.1.0 (2018-10)
7.1.3 fMP4 over MMTP Instantiation
7.1.3.1 General
MMTP is a transport protocol that supports the streaming of fragment ISOBMFF-formatted content using a dedicated
payload format, the MPU payload format. Media data is streamed as a CMAF Header, followed by CMAF chunks for
each media component separately. The CMAF Header is conformant to the MPU Header format and the CMAF Chunk
is conformant to the MPU Fragment as specified in [7].
The FLUS Source and FLUS Sink use the MMTP protocol [7] over UDP, over DTLS/UDP or over WebSocket [10].
This instantiation is identified in the SDP by the protocol identifier: "MMTP/UDP", "MMTP/DTLS/UDP", or using a
WebSocket URL ("ws" or "wss") respectively, as specified in [9].
This instantiation is also identified in the F-C configuration by the following urn:
"org:3gpp:flus:2018:instantiations:mmtp" or "org:3gpp:flus:2018:instantiations:mmtp-ws", depending on whether using
mmtp over UDP or over WebSocket.
Exactly one MMTP flow is used and each media component is sent using the MPU-mode, where each MPU conforms
to the restrictions in clause 7.1.2.1.
The FLUS Source is required to maintain NTP synchronization, with a tolerance of ±20 ms, when setting the
MPU_timestamp_descriptor and the MMTP delivery timestamp.
An fMP4 over MMTP/UDP or MMTP/DTLS/UDP session is described through an SDP file according to the
constraints in [9]. The SDP is sent from the FLUS Sink to the FLUS source and includes exactly one media line that
describes an MMTP flow in receive-only mode and with the target UDP port on which the MMTP flow is to be
received at the FLUS Sink.
If the FLUS Sink is behind a NAT or Firewall, it has to ensure that the port is open (with
...