1、 ETSI TR 126 939 V15.0.0 (2018-07) Universal Mobile Telecommunications System (UMTS); LTE; 5G; Guidelines on the Framework for Live Uplink Streaming (FLUS) (3GPP TR 26.939 version 15.0.0 Release 15) TECHNICAL REPORT ETSI ETSI TR 126 939 V15.0.0 (2018-07)13GPP TR 26.939 version 15.0.0 Release 15Refer
2、ence DTR/TSGS-0426939vf00 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 enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice
3、The present document can be downloaded from: http:/www.etsi.org/standards-search 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 authorizatio
4、n 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 awar
5、e 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 https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comment to one of the following ser
6、vices: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx 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 s
7、hall 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. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the benefit of its Members. 3GPPTM and L
8、TETMare 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. GSMand the GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI TR 126 939 V15.0.0 (2018-07)23GPP TR 26.939
9、 version 15.0.0 Release 15Intellectual 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 fo
10、und 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 P
11、olicy, 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
12、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 thos
13、e 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 technica
14、l 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 http:/webapp.etsi.org/key/queryform.a
15、sp. 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
16、ETSI deliverables except when used in direct citation. ETSI ETSI TR 126 939 V15.0.0 (2018-07)33GPP TR 26.939 version 15.0.0 Release 15Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions and abbreviat
17、ions . 6g33.1 Definitions 6g33.3 Abbreviations . 7g34 FLUS Overview . 7g35 Guidelines for IMS-based FLUS 7g36 Guidelines for non-IMS-based FLUS 7g36.1 Use Case: Sharing to a Social Network Service . 7g36.1.1 Use Case Description 7g36.1.2 Potential Realization in FLUS 7g36.2 Use Case: Live uplink vid
18、eo stream from drones or moving vehicles . 8g36.2.1 Use Case Description 8g36.3 Use Case: Breaking-News reporter 8g36.3.1 Use Case Description 8g36.4 Use Case: Immersive media conversations 9g36.4.1 Description 9g37 FLUS User Plane Instantiations . 9g37.1 Non-IMS-based User Plane Instantiations . 9g
19、37.1.1 Introduction. 9g37.1.2 fMP4-based Instantiations 9g37.1.2.1 Introduction . 9g37.1.3 fMP4 over MMTP Instantiation 9g37.1.3.1 General 9g37.1.3.2 MMTP Signaling . 10g37.1.3.3 Synchronization 11g37.1.3.4 Session Initiation and Description . 11g37.1.4 fMP4-based Instantiation with HTTP Delivery. .
20、 12g37.1.4.1 General Description 12g37.1.4.2 Rate Adaptation . 13g37.1.5 fMP4-based Instantiation using multiple segments per track . 14g37.1.5.1 General Description 14g38 Example FLUS Workflows 14g38.1 Example Workflow using F-U MMTP . 14g38.2 Example Call Flow for fragmented MP4 with HTTP Delivery
21、 15g38.2.1 Assumptions . 15g38.2.2 CMAF Format Example . 17g39 Guidelines for QoS usage for FLUS 19g39.1 Use-Case introduction 19g39.2 Discussion of the 3GPP QoS Framework . 20g39.2.1 Introduction. 20g39.2.2 Architecture 20g39.2.3 Relevant 3GPP sections 21g39.2.4 Usage of 3GPP QoS parameters . 22g39
22、.2.5 Desired QoS flow behavior . 23g3ETSI ETSI TR 126 939 V15.0.0 (2018-07)43GPP TR 26.939 version 15.0.0 Release 15Annex A: Immersive media signalling . 25g3A.1 General . 25g3A.2 Audio 25g3A.3 Video 25g3A.4 Examples of SDP offers and answers . 26g3A.4.1 H.264 (AVC), H.265 (HEVC), and EVS . 26g3Anne
23、x B: Change history 28g3History 29g3ETSI ETSI TR 126 939 V15.0.0 (2018-07)53GPP TR 26.939 version 15.0.0 Release 15Foreword 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
24、 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
25、; 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 incorpo
26、rated 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 ETSI TR 126 939 V15.0.0 (2018-07)63GPP TR 26.939 version 15.0.0 Releas
27、e 151 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 al
28、so 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
29、, 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,
30、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.23
31、8: “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
32、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:“In
33、formation technology High efficiency coding and media delivery in heterogeneous environments Part 1: MPEG media transport (MMT)“. 9 ISO 23008-1: 2ndEdition AMD2, “Enhancements for Mobile Environments“. 10 IETF RFC 6455: “The WebSocket Protocol“. 11 IETF RFC 5234 (2008): “Augmented BNF for Syntax Spe
34、cifications: ABNF“, D. Crocker, P. Overell. 12 IETF RFC 6817: “ Low Extra Delay Background Transport (LEDBAT)“. 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
35、 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. ETSI ETSI TR 126 939 V15.0.0 (2018-07)73GPP TR 26.939 version 15.0
36、.0 Release 15Media 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 sourc
37、e 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
38、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, tran
39、sport, 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-
40、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
41、 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
42、 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 instanti
43、ations 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. 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 examp
44、le 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
45、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. ETSI ETSI TR 126 939 V15.0.0 (2018-07)83GPP TR 26.
46、939 version 15.0.0 Release 15Once 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
47、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 r
48、equest: 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
49、of the FLUS Sinks and queries its capabilities using the Sinks 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,
