1、 ETSI TR 126 981 V15.0.0 (2018-07) LTE; MBMS Extensions for Provisioning and Content Ingestion (3GPP TR 26.981 version 15.0.0 Release 15) TECHNICAL REPORT ETSI ETSI TR 126 981 V15.0.0 (2018-07)13GPP TR 26.981 version 15.0.0 Release 15Reference RTR/TSGS-0426981vf00 Keywords LTE ETSI 650 Route des Luc
2、ioles 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 downloaded from: http:/www.etsi.org/stand
3、ards-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 perceived difference in content
4、s 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. I
5、nformation 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/CommiteeSupportStaff.aspx Copyri
6、ght 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 c
7、opyright 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 for the benefit of its Members
8、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 981 V15.0.0 (2018-07)23GPP TR 26.981 version 15.0.0 Release 15Intellectual Property Rights Essential pate
9、nts 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); Essenti
10、al, 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
11、 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 a
12、sserted 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 endorseme
13、nt 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 identit
14、ies 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 the present document “should“, “should
15、 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 ETSI TR 1
16、26 981 V15.0.0 (2018-07)33GPP TR 26.981 version 15.0.0 Release 15Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 6g34 Use-Cases . 7g3
17、4.1 Live Video from multiple cameras angles into a stadium 7g34.1.1 Use-Case Description . 7g34.1.2 Recommended requirements and working assumption . 7g34.2 Nation-Wide TV channels 8g34.2.1 Use-Case Description . 8g34.2.2 Recommended requirements and working assumption . 8g34.3 VOD prepositioning .
18、9g34.3.1 Use-Case Description . 9g34.3.2 Recommended requirements and working assumption . 9g34.4 Software Update . 10g34.4.1 Use-Case Description . 10g34.4.2 Recommended requirements and working assumption . 10g34.5 TV Program Guide update delivery 10g34.5.1 Use-Case Description . 10g34.5.2 Recomme
19、nded requirements and working assumption . 11g35 Architecture Considerations . 11g35.1 Introduction 11g35.2 Reference Model 11g35.3 Provisioning and Ingestion Procedures 12g35.3.1 Introduction. 12g35.3.2 Provisioning and Ingestion Procedure for Live DASH services (MBMS Broadcast only) 13g35.3.3 Prov
20、isioning and Ingestion Procedure for Live DASH services (with Service Continuity) . 15g35.3.4 Provisioning and Ingestion Procedure for File Delivery Services (without File Schedule) 15g35.3.5 Provisioning and Ingestion Procedure for File Carousel Services 18g35.3.6 Provisioning and Ingestion Procedu
21、re for File Delivery Services using continuous Push ingest (without File Schedule) . 21g36 Security aspects 21g37 Survey of Existing Protocols for a Provisioning Interface . 21g38 Conclusions and Recommendations . 23g3Annex A: Provisioning Procedure Overview . 24g3A.1 Service, Session and Content Pr
22、ovisioning Overview . 24g3A.1.0 Workflow . 24g3A.1.1 Service Provisioning. 25g3A.1.2 Session Provisioning 25g3A.1.3 Content Provisioning 26g3Annex B: Abstract Representation of API using IDL 27g3B.1 Introduction 27g3ETSI ETSI TR 126 981 V15.0.0 (2018-07)43GPP TR 26.981 version 15.0.0 Release 15B.2 S
23、urvey of Interface Description Languages . 27g3B.3 OMG IDL (Object Management Group Interface Description Language) 28g3Annex C: API Modelling Languages 30g3C.1 Introduction 30g3C.2 RESTful API Modeling Language (RAML) 30g3C.3 Open API Initiative (successor of Swagger) 31g3Annex D: MB2 Reference Poi
24、nt 37g3D.1 Introduction 37g3D.2 Shortcomings of MB2 37g3Annex E: Change history 39g3History 40g3ETSI ETSI TR 126 981 V15.0.0 (2018-07)53GPP TR 26.981 version 15.0.0 Release 15Foreword This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP). The contents of the presen
25、t 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
26、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
27、is incremented when editorial only changes have been incorporated in the document. Introduction The present document has been created as part of the study item on “MBMS Extensions on Provisioning and Content Ingestion“. The intention is to identify key functionality of an interface from external app
28、lication service/content providers to the BM-SC for provisioning and content ingestion in order to leverage all delivery methods and procedures through the interface. Mechanisms that would be suitable for delivery of multimedia content from external application service/content providers to the BM-SC
29、 should be identified. The provisioning and content ingestion interface definition should be aligned with the Client side APIs for MBMS (TRAPI) and the study on Enhanced TV Services. ETSI ETSI TR 126 981 V15.0.0 (2018-07)63GPP TR 26.981 version 15.0.0 Release 151 Scope The present document is a stud
30、y of an interface from external content providers to the BM-SC for provisioning and content ingestion. 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
31、 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 implicitl
32、y 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 22.246: “Multimedia Broadcast/Multicast Service (MBMS) user services; Stage 1“. 3 3GPP TS 26.346: “Multimedia Broadcast/Multicast Service (MB
33、MS); Protocols and codecs “. 4 3GPP TR 26.917: “MBMS/PSS Enhancements to Support Television Services“. 5 3GPP TR 23.746: “Study on System Architecture Enhancements to eMBMS for Television Video Service“. 6 3GPP TS 23.468: “Group Communication System Enablers for LTE (GCSE_LTE); Stage 2“. 3 Definitio
34、ns 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. 3.2 Abbreviations For
35、 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. ADF Associated Delivery Function API Application Pro
36、gramming Interface BM-SC Broadcast Multicast Service Center CP Content Provider DASH Dynamic Adaptive Streaming over HTTP DRM Digital Rights Management GBR Guaranteed Bitrate GUI Graphical User Interface MBMS Multimedia Broadcast/Multicast Service MPD Media Presentation Description MSA MBMS Service
37、Area MDF MBMS (Download Interface Server / Identifiers and procedures of server system ; Each of the Client and Server interfaces in the IDL description above can individually define the identifiers and procedures for the respective application/system. For example, the Client interface can define id
38、entifiers and procedures as shown below: interface Client long a; / identifier/ variable long sum (in long b, in long c); / procedure that returns the sum of two numbers ; In addition to defining basic interfaces, OMG provides capabilities for: - extending the interfaces to generate derived interfac
39、es (using the inheritance mechanism) - different types of abstract and local interfaces - different types of declarations such as value declarations, constant declarations, type declarations, exception declarations, operation declarations, attribute declarations, event declarations, and component de
40、clarations - scoping rules and name resolution Once, all the interfaces are defined and the IDL description is completed, the description can be mapped to client and/or servers language. The mapped description can then be used directly by the client in its implementation without complete understanding of the detailed servers implementation. As a results, this enables the client and server development to progress in parallel as long as they adhere to the agreed upon interface description and specification.
