ETSI TS 129 116-2017 LTE Representational state transfer over xMB reference point between content provider and BM-SC (V14 2 0 3GPP TS 29 116 version 14 2 0 Release 14)《长期演进技术(LTE) .pdf

1、 ETSI TS 129 116 V14.0.0 (2017-04) LTE; Representational state transfer over xMB reference point between content provider and BM-SC (3GPP TS 29.116 version 14.0.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 129 116 V14.0.0 (2017-04)13GPP TS 29.116 version 14.0.0 Release 14Reference DTS/TSGC-032

2、9116ve00 Keywords LTE 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

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

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

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

6、.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 shall not be modified with

7、out the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Me

8、mbers. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 129 116 V14.0.0 (2017-04)23GPP TS 29.116 version 14.0.0 Release 14Intellectu

9、al Property Rights IPRs essential or potentially essential to the present document 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 (I

10、PRs); 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 bee

11、n 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. Foreword This Technical Specification (TS) has been produced by ETSI 3r

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

13、, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In 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

14、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 ETSI TS 129 116 V14.0.0 (2017-04)33GPP TS 29.116 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal

15、verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions, symbols and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 xMB reference point . 8g34.1 Overview 8g34.2 Reference model . 8g34.3 Functional elements 8g34.3.1 BM-SC 8g34.3.2 Content Provider / Multicast Broad

16、cast Source 8g34.4 Procedures over xMB reference point 8g34.4.1 Introduction. 8g34.4.2 Authentication Procedures 8g34.4.3 Authorization Procedures . 8g34.4.4 Service Management Procedures 9g34.4.4.1 Create Service . 9g34.4.4.2 Get Service Properties . 9g34.4.4.3 Update Service Properties . 9g34.4.4.

17、4 Delete Service . 9g34.4.4.5 Service Notifications . 9g34.4.5 Session Management Procedures 9g34.4.5.1 Create Session . 9g34.4.5.2 Get Session Properties. 9g34.4.5.3 Update Session Properties . 9g34.4.5.4 Delete Session . 9g35 xMB API 10g35.1 Overview 10g35.1.1 Supported Methods . 10g35.1.2 Error H

18、andling 11g35.1.3 xMB Entry Point Discovery . 11g35.2 Resources . 11g35.2.1 Services. 11g35.2.1.1 Properties 11g35.2.1.2 API Operations 15g35.2.1.2.1 Introduction . 15g35.2.1.2.2 Service Creation 15g35.2.1.2.3 Service Modification . 15g35.2.1.2.4 Service Deletion 17g35.2.1.2.5 Service Retrieval . 18

19、g35.2.2 Sessions 20g35.2.2.1 Properties 20g35.2.2.2 API Operations 33g35.2.2.2.1 Introduction . 33g35.2.2.2.2 Session Creation 33g35.2.2.2.3 Session Modification . 34g35.2.2.2.4 Session Deletion 36g35.2.2.2.5 Session Retrieval . 37g35.2.3 Reports 39g3ETSI ETSI TS 129 116 V14.0.0 (2017-04)43GPP TS 29

20、.116 version 14.0.0 Release 145.2.3.1 Properties 39g35.2.3.2 API Operations 40g35.2.3.2.1 Introduction . 40g35.2.3.2.2 Report Retrieval. 41g35.2.4 Notifications . 44g35.2.4.1 Properties 44g35.2.4.2 API Operations 47g35.2.4.2.1 Introduction . 47g35.2.4.2.2 Notification Retrieval 48g36 User Plane Proc

21、edures 49g36.1 Introduction 49g36.2 File Session 49g36.2.1 General 49g36.2.2 Push Mode 49g36.2.3 Pull Mode . 49g36.3 Application Session 50g36.3.1 General 50g36.2.2 Push Mode 50g36.2.3 Pull Mode . 50g36.3 RTP Streaming . 51g36.4 Transport 51g37 Security. 51g37.1 Overview 51g37.2 Authentication 2 pre

22、sented 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 i

23、n the document. ETSI ETSI TS 129 116 V14.0.0 (2017-04)63GPP TS 29.116 version 14.0.0 Release 141 Scope The present document describes the REST-based protocol for the xMB reference point between the Content Provider and the BM-SC. The xMB reference point and related stage 2 protocol procedures are de

24、fined in 3GPP TS 23.246 2 and in 3GPP TS 26.346 3. 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.)

25、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 t

26、he same Release as the present document. 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 23.246: “Multimedia Broadcast/Multicast Service (MBMS) Architecture and Functional Description“. 3 3GPP TS 26.346: “Multimedia Broadcast/Multicast Service (MBMS); Protocols and Codecs“. 4 IETF

27、RFC 5246 (August 2008): “The Transport Layer Security (TLS) Protocol“, T. Dierks, E. Rescorla. 5 IETF RFC 6749 (October 2012): “The OAuth 2.0 Authorization Framework“, D. Hardt, Ed. 6 IETF RFC 7231 (June 2014): “Hypertext transfer protocol (HTTP/1.1): Semantics and Content“, R. Fielding and J. Resch

28、ke, Ed. 7 3GPP TS 33.210: “3G security; Network Domain Security (NDS); IP network layer security“. 8 IETF RFC 7235: “Hypertext Transfer Protocol (HTTP/1.1): Authentication“ 9 IETF RFC 4918, “HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)“. 10 3GPP TS 26.234, “Transparent end-t

29、o-end Packet-switched Streaming Service (PSS); Protocols and codecs“. 11 IETF RFC 3711, “The Secure Real-time Transport Protocol (SRTP)“. 12 IETF RFC 4347, “Datagram Transport Layer Security“. 13 IETF RFC 2818, “HTTP over TLS“. 14 IETF RFC 5246, “The Transport Layer Security (TLS) Protocol Version 1

30、.2“. 15 IETF RFC 2459, “Internet X.509 Public Key Infrastructure Certificate and CRL Profile“. 16 IETF RFC 6749, “The OAuth 2.0 Authorization Framework“. 17 IETF RFC 7235, “Hypertext Transfer Protocol (HTTP/1.1): Authentication“. 18 3GPP TS 26.247: “Transparent end-to-end Packet-switched Streaming S

31、ervice (PSS); Progressive Download and Dynamic Adaptive Streaming over HTTP (3GP-DASH)“. 19 IETF RFC 3926: “FLUTE - File Delivery over Unidirectional Transport“. ETSI ETSI TS 129 116 V14.0.0 (2017-04)73GPP TS 29.116 version 14.0.0 Release 1420 3GPP TS 29.061: “Interworking between the Public Land Mo

32、bile Network (PLMN) supporting packet based services and Packet Data Networks (PDN)“. 21 3GPP TS 26.347: “MBMS URLs and APIs“. 3 Definitions, symbols 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 appl

33、y. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 1. Content Provider: Entity/Entities which supplies/supply content in the form of streaming media or non-real-time (NRT) files to be delivered to UEs over the 3GPP network, via

34、MBMS Bearer and/or unicast bearer services. Also referred to in this document as the Multicast Broadcast Source. The Content Provider may reside either inside or outside the operators network. Service: One of the resource types exposed by the RESTful xMB API and operated on by a Content Provider usi

35、ng HTTP methods. It corresponds to a Content Providers service offering for delivery over the MBMS network to UEs. Each service instance created over the xMB API maps to an MBMS User Service as specified by 3GPP TS 26.346 3. The delivery of the contents of a created service is performed during one o

36、r more sessions associated with that service. Session: One of the resource types exposed by the RESTful xMB API and operated on by a Content Provider using HTTP methods. It represents one or more time intervals during which the MBMS Bearer is active for the transmission of service contents from the

37、BM-SC to the UE. Each session instance, besides the activity times, may contain various properties pertaining to transport, media and application level information (session type, session state, data rate, permitted delay, user plane ingestion mode, targeted delivery area, reporting parameters, ident

38、ification of content components delivered during the session, etc.). 3.2 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 abbre

39、viation, if any, in 3GPP TR 21.905 1. API Application Programming Interface BM-SC Broadcast Multicast Service Center CDN Content Delivery Network CP Content Provider DASH Dynamic Adaptive Streaming over HTTP FER Forward Error Correction FLUTE File Delivery over Unidirectional Transport HTTP HyperTex

40、t Transfer Protocol IS Initialization Segment JSON JavaScript Object Notation MPD Media Presentation Description MSA MBMS Service Area REST Representational State Transfer SACH Service Announcement ChannelSAF Service Announcement Function SLA Service Level Agreement TLS Transport Layer Security TMGI

41、 Temporarily Mobile Group Identity TSI Transport Session Identifier URI Universal Resource Identifier WebDAV Web Distributed Authoring and Versioning ETSI ETSI TS 129 116 V14.0.0 (2017-04)83GPP TS 29.116 version 14.0.0 Release 144 xMB reference point 4.1 Overview 4.2 Reference model The xMB referenc

42、e point resides between the BM-SC and the Content Provider as depicted in Figure 4.2.1. Control- and user-plane procedures are operated over the xMB-C and xMB-U reference points, respectively. The overall xMB reference model is depicted in subclause 5.4A of 3GPP TS 26.346 3. Figure 4.2.1 xMB referen

43、ce point 4.3 Functional elements 4.3.1 BM-SC The complete functionality of the BM-SC is defined in 3GPP TS 26.346 3. In the context of the xMB reference point, the BM-SC represents the peer endpoint to the Content Provider in supporting all procedures on the xMB interface. 4.3.2 Content Provider / M

44、ulticast Broadcast Source The functional role of the Content Provider is defined in subclause 4.4.1a of 3GPP TS 26.346 3. Using the xMB reference point, a Content Provider/Multicast Broadcast Source may provide media, as well as service descriptions and control data, to the BM-SC to set up and manag

45、e MBMS User Service(s) from the BM-SC to MBMS clients (the latter is not depicted in Figure 4.2.1). 4.4 Procedures over xMB reference point 4.4.1 Introduction All procedures that operate across the xMB reference point, as specified in subclause 5.4A of 3GPP TS 26.346 3, are summarized in the followi

46、ng subclauses. 4.4.2 Authentication Procedures Authentication procedures shall be performed via TLS as specified by 3GPP TS 33.210 7 and IETF RFC 5246 4. The Content Provider shall act as the TLS client and the BM-SC as the TLS server when the Content Provider wants to provision new services or mana

47、ge existing services. Similarly, the BM-SC shall act as the client when the BM-SC wishes to send reports and notifications to the Content Provider. All of the following procedures require the authentication procedure to be completed successfully. 4.4.3 Authorization Procedures The authorization proc

48、edure shall be done using OAuth as specified by IETF RFC 5246 4. The TLS client shall act as the OAuth client and BM-SC shall act as the server. All following procedures shall use the Access Token provided by ETSI ETSI TS 129 116 V14.0.0 (2017-04)93GPP TS 29.116 version 14.0.0 Release 14the BM-SC du

49、ring authorization. Any unauthorized procedure in the following shall be responded with a corresponding error code. Editors Note: BM-SC Authorization is FFS pending feedback from SA3 and SA4. 4.4.4 Service Management Procedures 4.4.4.1 Create Service This procedure is used by the Content Provider to create a service at the BM-SC. The Content Provider shall use HTTP POST for this purpose. A successfully created service is associated with a resource identifier which is used by the Content Provider to disco