ETSI TS 126 238-2018 Universal Mobile Telecommunications System (UMTS) LTE 5G Uplink streaming (V15 1 0 3GPP TS 26 238 version 15 1 0 Release 15 Includes Diskette).pdf

1、 ETSI TS 126 238 V15.1.0 (2018-07) Universal Mobile Telecommunications System (UMTS); LTE; 5G; Uplink streaming (3GPP TS 26.238 version 15.1.0 Release 15) TECHNICAL SPECIFICATION ETSI ETSI TS 126 238 V15.1.0 (2018-07)13GPP TS 26.238 version 15.1.0 Release 15Reference RTS/TSGS-0426238vf10 Keywords 5G

2、,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 The present document can be downloade

3、d 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 authorization of ETSI. In case of any existing or

4、 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

5、 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 services: https:/portal.etsi.org/People/

6、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 shall not be modified without the writ

7、ten 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 LTETMare trademarks of ETSI registered

8、 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 TS 126 238 V15.1.0 (2018-07)23GPP TS 26.238 version 15.1.0 Release 15Intellectua

9、l 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

10、 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 IP

11、R 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 trademar

12、ks 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

13、does not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports us

14、ing 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.asp. Modal verbs terminology In

15、 the present document “shall“, “shall not“, “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 del

16、iverables except when used in direct citation. ETSI ETSI TS 126 238 V15.1.0 (2018-07)33GPP TS 26.238 version 15.1.0 Release 15Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 7

17、g33.1 Definitions 7g33.2 Symbols 7g33.3 Abbreviations . 7g34 System architecture 7g34.1 General . 7g34.2 System 7g34.2.1 General 7g34.2.2 Uplink streaming for MTSI 9g34.2.3 Uplink streaming for PSS-based distribution 10g34.3 Terminal . 10g34.4 Procedures 11g34.4.1 General 11g34.4.2 FLUS session esta

18、blishment . 11g34.4.3 FLUS session update 12g34.4.4 FLUS sink capability discovery 12g34.4.5 FLUS session termination . 12g34.5 FLUS source systems . 12g34.5.1 Introduction. 12g34.5.2 General source systems . 12g34.5.3 Vendor-specific source system . 14g34.5.4 Default source system . 14g34.5.5 3DOF

19、FLUS source system 15g34.5.5.1 Introduction . 15g34.5.5.2 Coordinate system . 15g34.5.5.3 Descriptive Parameters 16g35 Protocols . 17g35.1 General . 17g35.2 IMS-based system 18g35.2.1 System configuration 18g35.2.1.1 Introduction . 18g35.2.1.2 FLUS sink configuration and selection . 18g35.2.1.2.1 UE

20、-based FLUS sink . 18g35.2.1.2.2 Network-based FLUS sink 18g35.2.1.3 FLUS management object . 18g35.2.2 Session management. 20g35.2.3 Data transport 20g35.3 Generic FLUS system 20g35.3.1 System configuration 20g35.3.2 Session management . 20g35.3.2.1 FLUS sink capability discovery 20g35.3.2.2 FLUS s

21、ession establishment . 20g35.3.2.4 FLUS session update . 21g35.3.2.5 FLUS session termination . 22g35.3.2.6 List of FLUS sink capabilities . 22g35.3.2.7 List of FLUS session properties 22g3ETSI ETSI TS 126 238 V15.1.0 (2018-07)43GPP TS 26.238 version 15.1.0 Release 155.3.3 Data transport 23g36 Termi

22、nal capabilities 23g36.1 General . 23g37 Uplink Streaming Control Interface . 24g37.1 General . 24g37.1.1 Resources 24g37.1.1.1 Sink Resource . 24g37.1.1.2 Session Resource. 24g37.1.2 Supported Methods . 25g37.1.3 Error Handling 25g37.2 Discovery . 25g37.3 Capability retrieval . 25g37.4 Uplink strea

23、ming configuration 26g37.4.1 FLUS session properties fetch procedure . 26g37.4.2 FLUS session update procedure 27g37.4.2.1 Partial modification of FLUS session . 27g37.4.2.2 Full modification of FLUS session . 28g37.5 Session establishment . 28g37.6 Session termination 29g38 FLUS Security 30g38.1 IM

24、S-based FLUS 30g38.2 Non-IMS-based FLUS . 30g3Annex A (informative): Change history . 31g3History 32g3ETSI ETSI TS 126 238 V15.1.0 (2018-07)53GPP TS 26.238 version 15.1.0 Release 15Foreword This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). The contents

25、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: V

26、ersion 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

27、 third digit is incremented when editorial only changes have been incorporated in the document. Introduction 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 IM

28、S/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 ope

29、ration, 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). I

30、n 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. ETSI ETSI TS 126 238 V15.1.0 (2018-07)63GPP TS 26.238 version 15.1.0 Release 151 Scope The pre

31、sent 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 w

32、ith 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

33、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 this document is mandated. Impact on the service quality and network capacity is left to the discretion of th

34、e 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 proc

35、edures, 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. 2 References The following documents contain provisions which, through r

36、eference 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

37、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 Recommendation ITU-R BS.

38、2051-1 (06/2017): “Advanced Sound System for Programme Production“. 3 ISO/IEC DIS 23090-2: “Omnidirectional Media Format. N16824“. 4 3GPP TS 26.114: “IP Multimedia Subsystem (IMS); Multimedia telephony; Media handling and interaction“. 5 3GPP TS 26.235: “Transparent end-to-end Packet-switched Stream

39、ing Service (PSS); Protocols and codecs“. 6 3GPP TS 24.147: “Conferencing using the IM Multimedia (IM) Core Network (CN) subsystem; Stage 3”. 7 3GPP TS 23.003: “Numbering, addressing and identification“. 8 3GPP TS 33.203: “3G security; Access security for IP-based services“. 9 3GPP TS 33.210: “3G se

40、curity; Network Domain Security (NDS); IP network layer security“. 10 3GPP TS 33.328: “IP Multimedia Subsystem (IMS) media plane security“. 11 IETF RFC 7231: “Hypertext transfer protocol (HTTP/1.1): Semantics and Content“. 12 3GPP TS 24.229: “IP multimedia call control protocol based on Session Init

41、iation Protocol (SIP) and Session Description Protocol (SDP); Stage 3“. ETSI ETSI TS 126 238 V15.1.0 (2018-07)73GPP TS 26.238 version 15.1.0 Release 153 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

42、 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

43、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. One or more media sessions are delivered during a FLUS session. A media session may be e

44、stablished and controlled by a well-defined control protocol. Media stream: The content sent from a FLUS source to a FLUS sink within a media session. 3.2 Symbols For the purposes of the present document, the following symbols apply: 3.3 Abbreviations For the purposes of the present document, the ab

45、breviations 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 HMD Head Mounted Display IMS IP Multimedia Subsystem 4 S

46、ystem architecture 4.1 General This clause introduces the system architecture for FLUS. 4.2 System 4.2.1 General Figure 4.2-1 depicts the architecture showing the relevant entities for providing an uplink streaming service. ETSI ETSI TS 126 238 V15.1.0 (2018-07)83GPP TS 26.238 version 15.1.0 Release

47、 15Figure 4.2-1: FLUS architecture The uplink streaming service architecture is based on a FLUS source located in a UE and a FLUS sink located in either another UE or in the network. The FLUS source receives media content from one or more capture devices. In the context of this specification, the ca

48、pture devices are considered as parts of a UE or are connected to it. When the FLUS sink is located in a UE, the FLUS sink shall forward media content to a decoding and rendering function. When the FLUS sink is located in the network, the FLUS sink may forward media content to a processing or distri

49、bution sub-function. The processing and distribution sub-functions are not in scope of the present specification. The FLUS sink may act as a Media Gateway Function (MGW) and/or an Application Function (AF). The F reference point connects a FLUS source and a FLUS sink. The F reference point enables the FLUS source to establish and control a single FLUS session. The F reference point also enables the FLUS sink and the FLUS source to mutually authenticate and authorize each other. The F reference point shall support security function for confiden