ETSI TS 101 498-1-2006 Digital Audio Broadcasting (DAB) Broadcast website Part 1 User application specification (V2 1 1)《数字音频广播(DAB) 广播站点 第1部分 用户应用规范(版本2 1 1)》.pdf

《ETSI TS 101 498-1-2006 Digital Audio Broadcasting (DAB) Broadcast website Part 1 User application specification (V2 1 1)《数字音频广播(DAB) 广播站点 第1部分 用户应用规范(版本2 1 1)》.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 101 498-1-2006 Digital Audio Broadcasting (DAB) Broadcast website Part 1 User application specification (V2 1 1)《数字音频广播(DAB) 广播站点 第1部分 用户应用规范(版本2 1 1)》.pdf（27页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 101 498-1 V2.1.1 (2006-01)Technical Specification Digital Audio Broadcasting (DAB);Broadcast website;Part 1: User application specificationEuropean Broadcasting Union Union Europenne de Radio-Tlvision EBUUER ETSI ETSI TS 101 498-1 V2.1.1 (2006-01) 2 Reference RTS/JTC-DAB-43 Keywords audio,

2、broadcast, DAB, digital, receiver 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 Individual co

3、pies 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 Portable Document Format

4、 (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 on the current sta

5、tus 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 be reproduced exce

6、pt 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 ETSI registered for

7、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 TS 101 498-1 V2.1.1 (2006-01) 3 Conte

8、nts Intellectual Property Rights5 Foreword.5 Introduction 6 1 Scope 7 2 References 7 3 Abbreviations .8 4 Syntax specification .8 5 Operation of the MOT BWS user application8 5.1 The World Wide Web and the Internet 8 5.2 The MOT Broadcast website9 5.2.1 The BWS Server for the PC receiver class .9 5.

9、2.2 The application decoder for an integrated receiver.10 5.2.3 The application decoder for a PC based receiver10 5.3 The BWS MOT carousel10 5.4 MOT parameters for individual objects11 5.4.1 The ContentName parameter 11 5.4.2 The MimeType parameter 12 5.4.3 The CompressionType parameter.12 5.4.4 The

10、 AdditionalHeader parameter12 5.4.5 The ProfileSubset parameter.12 5.4.6 Parameters for “Conditional access on MOT level“ .12 5.5 MOT parameters for the entire carousel.13 5.5.1 The DirectoryIndex parameter13 6 The BWS decoder 14 6.1 Presenting the service.14 6.1.1 The PC based BWS decoder.14 6.1.2

11、The integrated BWS decoder14 6.2 Resolving URLs .14 6.2.1 Handling invalid URLs.15 6.2.2 Handling absolute and relative paths 15 6.2.3 Handling requests for URLs that refer to directories 15 6.2.4 Starting the service16 6.2.5 Error handling, including requests for objects that do not exist16 6.3 Det

12、ermining object type .17 6.4 The DAB Gateway Interface 17 7 Application signalling 18 7.0 General .18 7.1 Specifying BWS user application content profiles.19 7.1.1 Fact of service parameters 19 7.1.1.1 Supported content types 19 7.1.1.2 Supported profile of HTML19 7.1.1.3 Supported additional HTTP h

13、eader fields .19 7.1.1.4 Maximum object size 20 7.1.1.5 Maximum total size of all objects rendered within a page 20 7.1.2 Quality of service parameters .20 7.1.2.1 Minimum receiver cache size20 7.1.2.2 Minimum receiver display characteristics.20 7.1.2.3 Maximum carousel period.20 7.2 Application pro

14、file specifications.21 7.2.1 Basic Integrated Receiver content profile.21 7.2.2 Unrestricted (PC) content profile21 ETSI ETSI TS 101 498-1 V2.1.1 (2006-01) 4 Annex A (informative): Implementation tips.22 A.1 General tips 22 A.1.1 Mapping of URLs to ContentNames22 A.2 Integrated BWS receiver 23 A.2.1

15、 Mapping URLs to ContentNames 23 A.2.2 The MOT parameter MimeType 23 A.2.3 The MOT parameter CompressionType.23 A.2.4 The MOT parameter AdditionalHeader .23 A.2.5 Object updates24 A.3 PC based receivers24 A.3.1 Mapping URLs to ContentNames 24 A.3.2 The MOT parameter MimeType 24 A.3.3 The MOT paramet

16、er CompressionType.24 A.3.4 The MOT parameter AdditionalHeader .25 A.3.5 Object updates25 History 27 ETSI ETSI TS 101 498-1 V2.1.1 (2006-01) 5 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to th

17、ese 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. Lates

18、t updates 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

19、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 Joint Technical Committee (JTC) Broadcast of the European Broadcasting Union (EBU), Comit Europen de Normalisation ELECtrotechnique (CENELEC

20、) 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 including in the Me

21、morandum 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-making and pr

22、ogramme-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 established in 1

23、987, 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 members of the Eu

24、reka 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. The present document is part 1 of a multi

25、-part deliverable covering Digital Audio Broadcasting (DAB); Broadcast website, as identified below: Part 1: “User application specification“; Part 2: “Basic profile specification“; Part 3: “TopNews basic profile specification“. ETSI ETSI TS 101 498-1 V2.1.1 (2006-01) 6 Introduction The growth of th

26、e Internet and the popularity of the “World Wide Web“, based on the Hyper Text Transfer Protocol (HTTP) and the Hyper Text Markup Language (HTML), makes web related services an extremely attractive way of providing information to users. The public have already accepted a technology that is now commo

27、n both in the home and in the workplace, and HTML is a content format that is widely used and supported well by many content creation tools. The DAB Broadcast website user application gives DAB multiplex operators the opportunity to use HTML as a content format to support information services by usi

28、ng the concept of a “broadcast website“. The MOT BWS user application is designed to allow an entire website to be delivered to a receiver using only the broadcast channel of DAB and without the need for any form of return channel. Version 1.1.1 of the present document lists restrictions that apply

29、to pilot project receivers. Since these old receivers are no longer relevant, the corresponding clauses are no longer part of this revision of the present document. The readers should refer to the earlier version (V1.1.1) of the present document for more details regarding the support of these outdat

30、ed receivers. The MOT parameter Label is also no longer mentioned in the present version of the BWS standard; see the earlier version (V1.1.1) of the present document and V1.2.1 of the MOT standard for a description of this MOT parameter and its use by the old pilot project receivers. ETSI ETSI TS 1

31、01 498-1 V2.1.1 (2006-01) 7 1 Scope The present document describes the protocol required to create a broadcast carousel of files for a “website“. Receivers may then extract information directly from this carousel in order to present the service. The DAB Broadcast website application applies the DAB-

32、MOT protocol 3 and allows a service provider to deliver HTML content via DAB without the need for a return channel. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. References are either specific (identified

33、 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 in the expected location might be

34、 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 ETSI TS 101 756: “Digital Audio Broadcasting (DAB); Registered Tables“. 3 ETSI EN 301 234: “Digital Audio Broadcasting (DAB); Multim

35、edia Object Transfer (MOT) protocol“. 4 ETSI TS 101 498-2: “Digital Audio Broadcasting (DAB); Broadcast website; Part 2: Basic profile specification“. 5 IETF RFC 1945: “Hypertext Transfer Protocol - HTTP/1.0“. 6 IETF RFC 2068: “Hypertext Transfer Protocol - HTTP/1.1“. 7 IETF RFC 1738: “Uniform Resou

36、rce Locators (URL)“. 8 IETF RFC 2045: “Multipurpose Internet Mail Extensions (MIME) - Part 1“. 9 IETF RFC 2046: “Multipurpose Internet Mail Extensions (MIME) - Part 2“. 10 IETF RFC 2047: “Multipurpose Internet Mail Extensions (MIME) - Part 3“. 11 IETF RFC 2048: “Multipurpose Internet Mail Extensions

37、 (MIME) - Part 4“. 12 IETF RFC 2049: “Multipurpose Internet Mail Extensions (MIME) - Part 5“. 13 ETSI TS 101 498-3: “Digital Audio Broadcasting (DAB); Broadcast website; Part 3: TopNews basic profile specification“. ETSI ETSI TS 101 498-1 V2.1.1 (2006-01) 8 3 Abbreviations For the purposes of the pr

38、esent document, the following abbreviations apply: BWS Broadcast WebSite CA Conditional Access CGI Common Gateway Interface DAB Digital Audio Broadcasting DGI DAB Gateway Interface FIG Fast Information Group HTML Hyper Text Markup Language HTTP Hyper Text Transfer Protocol IETF Internet Engineering

39、Task Force NOTE: The IETF is an international body responsible for the development of Internet standards. IP Internet Protocol MIME Multi-purpose Internet Mail Extensions MOT Multimedia Object Transfer RFC Request For Comments - RFCs are used by the IETF for standards and recommendations TCP Transmi

40、ssion Control Protocol UA User ApplicationURL Uniform Resource Locator 4 Syntax specification The specifications of syntax that appear in the present document are written using a form of pseudo-code that is similar to the procedural language “C“; this provides for easy specification of loops and con

41、ditional data structures. Within these specifications, the type of individual data fields is expressed using the mnemonics given in table 1. Table 1: Data type mnemonics for syntax specification Mnemonic Description uimsbf Unsigned integer, most significant bit first bslbf Bit string, left bit first

42、 rpchof Remainder polynomial coefficients, high order first 5 Operation of the MOT BWS user application 5.1 The World Wide Web and the Internet On the Internet, the World Wide Web (WWW) is based largely on the use of HTTP and HTML. HTTP is a protocol that is designed to be used with the TCP/IP proto

43、col stack. It works by using TCP/IP sockets to exchange HTTP requests and HTTP responses and therefore requires a bi-directional communication channel on two levels: TCP is a connection-oriented protocol that uses a system of acknowledgements and timeouts to implement a reliable, bi-directional stre

44、am channel over an IP network. The acknowledgements are used to verify that information has been correctly received and so the protocol inherently requires bi-directional communication, even if the information carried within the stream is uni-directional. HTTP is a request-response protocol used for

45、 exchanging information in a client-server system. An HTTP client (a web browser) first makes a TCP/IP connection to an HTTP server and requests an object from the server. The server uses the same TCP/IP connection to return the requested data, so HTTP is also necessarily bi-directional in nature. E

46、TSI ETSI TS 101 498-1 V2.1.1 (2006-01) 9 On the WWW, web browsers make requests for web objects to a web server (HTTP server) which the server usually stores locally in the form of files. This means that an entire website can be represented as a set of files. Because both TCP/IP and HTTP are necessa

47、rily bi-directional protocols, it is not possible to use these protocols in a broadcast channel. However, by transporting the complete set of files for the website in the broadcast channel, a web-like experience can be created. 5.2 The MOT Broadcast website The Broadcast website user application use

48、s the MOT protocol to create a broadcast carousel of files for a website. Receivers may then extract information directly from this carousel in order to present the service. Two distinct classes of receiver are envisaged: integrated receivers where native DAB BWS browser software is required to be w

49、ritten for a specific DAB radio platform; PC based receivers where the application decoder makes the service available by using the installed desktop web browser. Also PDA systems and high-end mobile phones will probably already provide a web browser. In this case the software architecture for the BWS receiver will most probably follow the same rules as the PC based receivers. Because the capabilities of integrated BWS receivers will necessarily be limited by the software installed in them at the time of sale, content intende