1、 ETSI EN 301 234 V2.1.1 (2006-05)European Standard (Telecommunications series) Digital Audio Broadcasting (DAB);Multimedia Object Transfer (MOT) protocolEuropean Broadcasting Union Union Europenne de Radio-Tlvision EBUUER ETSI ETSI EN 301 234 V2.1.1 (2006-05) 2 Reference REN/JTC-DAB-38A Keywords aud
2、io, broadcasting, DAB, digital, multimedia, protocol 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 n
3、otice Individual copies of the present document can be downloaded from: http:/www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Porta
4、ble Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the 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
5、 on the current status of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may
6、 be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2006. European Broadcasting Union 2006. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of E
7、TSI registered for the benefit of its Members. TIPHONTMand the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI EN 301 234 V2.1.1
8、(2006-05) 3 Contents Intellectual Property Rights6 Foreword.6 Introduction 7 1 Scope 8 2 References 8 3 Definitions and abbreviations.9 3.1 Definitions9 3.2 Abbreviations .11 4 General description of the MOT protocol 12 4.1 Requirements of Multimedia services 12 4.2 Problems MOT solves 12 4.3 Receiv
9、er architecture reference model .13 5 Structural description .14 5.1 Segmentation of MOT entities .15 5.1.1 Segmentation header.17 5.1.2 Segmentation of the MOT body .17 5.1.3 Segmentation of the MOT directory.17 5.1.4 Segmentation of the MOT header.18 5.2 Transporting MOT segments - network level.1
10、8 5.2.1 Packet mode18 5.2.2 X-PAD 18 5.3 Transmission Mechanisms .20 5.3.1 Single object transmission (MOT header mode) 20 5.3.1.1 Repetition on object level20 5.3.1.2 Repetition of MSC data groups/MOT segments .21 5.3.1.3 Repeated transmission of header information (combined with repetition on obje
11、ct level) .21 5.3.2 Multiple object transmissions (MOT directory mode)22 5.3.2.1 Interleaving MOT entities in one MOT stream.23 6 MOT header information24 6.1 Header core 24 6.2 Header extension 25 6.2.1 Future expansion of the parameter data field26 6.2.2 Parameters of the header extension for MOT
12、header mode and MOT directory mode 27 6.2.2.1 MOT Basic transport parameters 27 6.2.2.1.1 ContentName.27 6.2.2.1.2 MimeType .27 6.2.2.1.3 CompressionType28 6.2.3 Parameters of the header extension for MOT directory mode only28 6.2.3.1 MOT caching support parameters .28 6.2.3.1.1 Expiration 28 6.2.3.
13、1.2 PermitOutdatedVersions30 6.2.3.1.3 UniqueBodyVersion30 6.2.3.1.4 Priority.30 6.2.3.1.5 RetransmissionDistance.30 6.2.3.2 MOT conditional access parameters .31 6.2.3.2.1 CAInfo.31 6.2.3.2.2 CAReplacementObject 31 6.2.3.3 MOT profile identification31 6.2.3.3.1 ProfileSubset .32 6.2.4 Coding of par
14、ameters32 6.2.4.1 Coding of time parameters 32 6.3 List of all MOT parameters in the MOT header extension.32 ETSI ETSI EN 301 234 V2.1.1 (2006-05) 4 7 MOT transport modes 34 7.1 MOT header mode35 7.1.1 New object/object update35 7.1.2 Management of TransportIds36 7.1.3 Updating header information/tr
15、iggering objects .36 7.2 MOT directory mode37 7.2.1 Introduction.37 7.2.2 Assembly of MOT bodies and MOT directory.37 7.2.3 MOT directory coding 37 7.2.4 List of all MOT parameters in the MOT directory extension .39 7.2.4.1 SortedHeaderInformation39 7.2.4.2 DefaultPermitOutdatedVersions .40 7.2.4.3
16、DefaultExpiration40 7.2.5 Segment size of the MOT directory40 7.2.6 Identification of the MOT directory41 7.2.7 Use of the MOT directory mode.41 7.2.7.1 Segment reception order .41 7.2.7.2 Service acquisition 41 7.2.7.3 Version control41 7.2.7.4 Allocation of TransportIds 42 7.2.7.5 Prioritizing obj
17、ects within the data carousel .42 7.2.7.6 Managing updates to the data carousel42 7.2.7.7 MOT decoder behaviour in case no data is received for a long time 42 7.2.8 MOT directory compression.43 8 MOT functionality44 8.1 MOT caching support (MOT directory mode only) .44 8.1.1 Object reassembly.46 8.1
18、.2 Object validity 46 8.1.2.1 MOT expire time handling48 8.1.2.2 Unique MOT body version .49 8.1.2.3 Temporarily using outdated MOT bodies .50 8.1.3 Object management 51 8.2 Transfer of directory structures using MOT.52 Annex A (normative): Comparing ContentNames54 Annex B (informative): User applic
19、ation definitions and MOT 55 Annex C (informative): Model of an MOT decoder and its interfaces57 C.1 Network level .59 C.2 MSC Data group level60 C.3 Segmentation and object level60 C.3.1 General description of the MOT decoder.60 C.3.2 The reassembly unit60 C.3.2.1 MOT directory mode 60 C.3.2.2 MOT
20、header mode61 C.3.2.3 Segmentation of MOT bodies.61 C.3.3 The object management unit 61 C.3.3.1 MOT directory mode 61 C.3.3.2 MOT header mode62 C.3.4 Advanced MOT reassembly units 62 C.3.4.1 Collecting MOT body segments whose TransportId is not described in the MOT directory .62 C.3.4.1.1 Start-up o
21、f the MOT directory mode decoder.63 C.3.4.1.2 Updates to the MOT directory 63 C.3.4.1.3 Collecting MOT body segments .64 C.3.4.2 MOT caching support: relative expire times (MOT parameters Expiration and DefaultExpiration)65 C.3.4.3 Acquiring both compressed and uncompressed MOT directories 65 C.3.5
22、Advanced MOT object management68 C.3.5.1 MOT directory mode 68 ETSI ETSI EN 301 234 V2.1.1 (2006-05) 5 C.3.5.1.1 Support of MOT parameters DefaultPermitOutdatedVersions and PermitOutdatedVersions 70 C.4 User application level.71 Annex D (informative): MOT decoding in MOT directory mode (example)72 A
23、nnex E (informative): Example for evaluation of relative expire times (MOT parameters Expiration and DefaultExpiration) 73 Annex F (informative): Managing changes to the MOT data carousel.75 F.1 General principle75 F.2 Advanced approach 75 Annex G (informative): Implementation tips for “Transfer of
24、directory structures via MOT“ (receiver side) .77 Annex H (informative): Bibliography.78 History 79 ETSI ETSI EN 301 234 V2.1.1 (2006-05) 6 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these
25、 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 u
26、pdates are available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). 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
27、the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This European Standard (Telecommunications series) has been produced by Joint Technical Committee (JTC) Broadcast of the European Broadcasting Union (EBU), Comit Europen de Normalisation ELECtrotech
28、nique (CENELEC) and the European Telecommunications Standards Institute (ETSI). NOTE 1: The EBU/ETSI JTC Broadcast was established in 1990 to co-ordinate the drafting of standards in the specific field of broadcasting and related fields. Since 1995 the JTC Broadcast became a tripartite body by inclu
29、ding in the Memorandum of Understanding also CENELEC, which is responsible for the standardization of radio and television receivers. The EBU is a professional association of broadcasting organizations whose work includes the co-ordination of its members activities in the technical, legal, programme
30、-making and programme-exchange domains. The EBU has active members in about 60 countries in the European broadcasting area; its headquarters is in Geneva. European Broadcasting Union CH-1218 GRAND SACONNEX (Geneva) Switzerland Tel: +41 22 717 21 11 Fax: +41 22 717 24 81 The Eureka Project 147 was es
31、tablished in 1987, with funding from the European Commission, to develop a system for the broadcasting of audio and data to fixed, portable or mobile receivers. Their work resulted in the publication of European Standard, EN 300 401 1, for DAB (see note 2) which now has worldwide acceptance. The mem
32、bers of the Eureka Project 147 are drawn from broadcasting organizations and telecommunication providers together with companies from the professional and consumer electronics industry. NOTE 2: DAB is a registered trademark owned by one of the Eureka Project 147 partners. National transposition date
33、s Date of adoption of this EN: 19 May 2006 Date of latest announcement of this EN (doa): 31 August 2006 Date of latest publication of new National Standard or endorsement of this EN (dop/e): 28 February 2007 Date of withdrawal of any conflicting National Standard (dow): 28 February 2007 ETSI ETSI EN
34、 301 234 V2.1.1 (2006-05) 7 Introduction The present document is a complete revision of V1.2.1. It does not change the former MOT specifications but tries to give a much more extensive and understandable description of what MOT is, how it works and how an MOT decoder can be implemented. The present
35、document concentrates on describing the transport related issues; all user application specific issues will now be handled by the user applications specifications. MOT considers itself the multimedia transport protocol that provides the necessary tools to carry all kind of multimedia data. It is the
36、 user application to decide which of the tools provided by MOT it uses and the user applications might also extend or restrict some functionality that is described in the present document. Some general and transport related MOT parameters (MimeType, CA related parameters, CompressionType, ProfileSub
37、set) were removed from the MOT broadcast web site specification 6 and added to the present document. User application specific parameters (TriggerTime, Label) are no longer explained in the present document and will be described in user application specifications (MOT broadcast website 6; MOT Slide
38、Show 5). A clear indication of the differences between MOT header mode and MOT directory mode is given. Backwards compatible extensions reduce the footprint of the MOT decoder and permit much better user behaviour during changes to a data carousel. MOT directory compression permits better use of the
39、 broadcast channel. A detailed description of a model of an MOT decoder and its interfaces is given in annex C. This should help implementing a fully standard compliant and efficient MOT decoder. Additional clauses describe features that an advanced MOT decoder should use to further improve the perf
40、ormance of the MOT decoder and to enhance the user experience. The present document contains identifier fields that require values to be registered. Registered value lists associated with data broadcasting specifications for DAB are maintained by the WorldDAB Information and Registration Centre (WIR
41、C). Since the lists and tables contained within the present document might be outdated, please refer to the most recent versions of TS 101 756 7. The present document also describes the procedures for registering values in an existing table as well as registering new tables. ETSI ETSI EN 301 234 V2.
42、1.1 (2006-05) 8 1 Scope The present document specifies a transmission protocol, which allows to broadcast various kinds of data using the Digital Audio Broadcasting (DAB) system. It is tailored to the needs of Multimedia services and the specific constraints given by the broadcasting characteristics
43、 of the DAB system. After reception this data can be processed and presented to the user. The present document defines the transport specific encoding for data types not specified in EN 300 401 1 according to the transport mechanisms provided by DAB. It allows a flexible utilization of the data chan
44、nels incorporated in the DAB system, as well as methods to manage and maintain a reliable transmission in a uni-directional broadcast environment. Provisions are also made for the creation and presentation of advanced Multimedia services using formats such as Hyper Text Markup Language (HTML) (see R
45、FC 2854 2) or Multimedia and Hypermedia information coding Experts Group (MHEG) (see ISO/IEC 13522 3). The present document describes the core transport protocol. Subsequent parts or revisions of the present document will describe backwards compatible extensions. Aspects related to the further decod
46、ing and processing of the data objects carried are outside the scope of the present document. Hardware implementation considerations are not covered. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. Referenc
47、es are either specific (identified by date of publication and/or edition number or version number) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version applies. Referenced documents which are not found to be publicly available
48、 in the expected location might be found at http:/docbox.etsi.org/Reference. 1 ETSI EN 300 401: “Radio Broadcasting Systems; Digital Audio Broadcasting (DAB) to mobile, portable and fixed receivers“. 2 IETF RFC 2854: “The text/html Media Type“. 3 ISO/IEC 13522 (all parts): “Information technology -
49、Coding of multimedia and hypermedia information“. 4 IETF RFC 2045 to 2049: “Multipurpose Internet Mail Extensions (MIME)“. 5 ETSI TS 101 499: “Digital Audio Broadcasting (DAB); MOT Slide Show; User Application Specification“. 6 ETSI TS 101 498-1: “Digital Audio Broadcasting (DAB); Broadcast website; Part 1: User application specification“. 7 ETSI TS 101 756: “Digital Audio Broadcasting (DAB); Registered Tables“. 8 ETSI TS 102 367: “Digital Audio Broadcasting (DAB); Conditional access“. 9 ETSI TR 101 496-2: “Digital Audio Broadc
