1、 ETSI TS 102 652 V1.1.1 (2007-10)Technical Specification Digital Audio Broadcasting (DAB);Intellitext;Application specificationEuropean Broadcasting Union Union Europenne de Radio-Tlvision EBUUER ETSI ETSI TS 102 652 V1.1.1 (2007-10) 2 Reference DTS/JTC-DAB-50 Keywords DAB, text ETSI 650 Route des L
2、ucioles 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 copies of the present document can be downloaded from: h
3、ttp:/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 (PDF). In case of dispute, the reference shall be the
4、 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 status of this and other ETSI documents is available at h
5、ttp:/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 except as authorized by written permission. The copyright
6、and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2007. European Broadcasting Union 2007. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTMand the TIPHON log
7、o 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 102 652 V1.1.1 (2007-10) 3 Contents Intellectual Property Rights4 Foreword.4 1 Scope 5 2
8、 References 5 2.1 Normative references .5 3 Definitions and abbreviations.5 3.1 Definitions5 3.2 Abbreviations .6 4 Introduction 6 5 Message format 7 6 Updating and deleting messages 8 6.1 Updating messages.8 6.2 Deleting messages 8 7 Receiver behaviour.8 7.1 Validation.8 7.2 Parsing9 7.3 Automatic
9、deletion of messages.9 7.4 Segregation of data.9 Annex A (informative): Example Intellitext strings 10 A.1 Example 1.10 A.2 Example 2.11 A.3 Example 3.11 A.4 Example 4.13 Annex B (informative): Intellitext 1.0 and backwards compatibility 14 B.1 Differences between Intellitext 1.1 and 1.014 B.2 Recei
10、ver behaviour.14 B.2.1 Validation.14 B.2.2 Parsing14 B.2.3 Automatic deletion of messages.15 B.2.4 Segregation of data.15 B.3 Examples 15 History 16 ETSI ETSI TS 102 652 V1.1.1 (2007-10) 4 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been decl
11、ared 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); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which
12、 is available from the ETSI Secretariat. Latest 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
13、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 Joint Technical Committee (JTC) Broadcast of the European Broadcasting Union (EBU), Comit Euro
14、pen de Normalisation ELECtrotechnique (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 b
15、ecame a tripartite body by including 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
16、 the technical, legal, programme-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
17、81 The Eureka Project 147 was established 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 h
18、as worldwide acceptance. The members 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 partn
19、ers. ETSI ETSI TS 102 652 V1.1.1 (2007-10) 5 1 Scope The present document describes the Intellitext DL extension, including structure and formatting of data and receiver and broadcast requirements. It also covers backwards compatibility with earlier versions of Intellitext. 2 References References a
20、re 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. Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is ac
21、cepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference.
22、 For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably, the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the reference should, as far as possible, remain valid for the expect
23、ed life of the document. The reference shall include the method of access to the referenced document and the full network address, with the same punctuation and use of upper case and lower case letters. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI can
24、not guarantee their long term validity. 2.1 Normative references The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (includi
25、ng any amendments) applies. 1 ETSI EN 300 401: “Radio Broadcasting Systems; Digital Audio Broadcasting (DAB) to mobile, portable and fixed receivers“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: element: syntact
26、ic part of an Intellitext message message: complete set of associated dynamic label segments whitespace: one or more of the space character (code 20 hex) ETSI ETSI TS 102 652 V1.1.1 (2007-10) 6 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: DAB Digital
27、 Audio Broadcasting DL Dynamic Label X-PAD eXtended Programme Associated Data 4 Introduction The present document describes an extension to the existing DAB Dynamic Label X-PAD application (see EN 300 401 1 clause 7.4.5.2) to enable hierarchical-menu-driven text services on a compatible receiver. Th
28、e data is compiled into a simple Teletext-like database of information which the user of any DAB radio equipped with this application can browse on demand. Intellitext messages are a special form of DL messages, formatted in such a way that receivers not supporting Intellitext will continue to funct
29、ion normally. The Intellitext system provides a means for broadcasters to control the lifetime and basic formatting of broadcast information, while the display of information is user-driven. The Intellitext system allows the broadcaster to dictate the structure and design of menus, including menu na
30、ming. The information provided by each service provider is stored in such a way that it cannot be altered by any other service provider. Navigation is usually via a simple up/down/select interface, with the actual display being tailored to the resources available to a given receiver. Intellitext mes
31、sages consists of a category, a sub-category and some data. Within a given category, the sub-categories may be ordered by using a numerical index; similarly the data items are ordered within the sub-category. An example of the type of user display is shown in figure 1. talkSPORT Football Prem Lge Ta
32、ble 1. Chelsea 27 pts 2. Spurs 18 pts 3. Charlton 16 pts 4. Man Utd 14 pts 5. Man City 14 pts Results Arsenal 0, Wigan 3 Spurs 2, Man Utd 1 West Ham 2, Sunderland 3 Figure 1: Example of display of Intellitext message data ETSI ETSI TS 102 652 V1.1.1 (2007-10) 7 5 Message format Intellitext data is t
33、ransmitted in the DAB DL, and will thus be displayed to users of non-compatible receivers (usually as “scrolling text“). It is therefore necessary that no “special“ characters are used as mark-up characters, as these may be misinterpreted by receivers. Broadcasters should account for non-compatible
34、receivers when deciding broadcast schemas. The format of an Intellitext message is as follows: - : The message comprises the following elements: the category this message refers to; the (optional) sub-category index within the category; the sub-category this message refers to; the data index within
35、the sub-category; zero or more data items; the (optional) lifetime of the data items. The entire message must fit into a standard DL message, and thus has a total length of no more than 128 bytes. The message may contain as many data items as will fit within the space limitations. All elements of th
36、e Intellitext message shall start and end with non-whitespace characters. Because Intellitext messages may be displayed by non-Intellitext capable receivers, the broadcaster may add whitespace between elements in order to present the message in human-readable form. Intellitext receivers will remove
37、this whitespace (including any whitespace between elements and separating characters) during parsing of messages, such that each element starts and ends with a non-whitespace character. The element is descriptive text which identifies the broad category that the message applies to. There may be seve
38、ral different elements broadcast, but only one per message. The element consists of one to 16 characters, and shall not include the hyphen (“-“) or square bracket (“ or “) characters. The element is an identifier which allows the receiver to order the elements within a category. It is an optional el
39、ement. If the element is omitted, the receiver defined default behaviour shall apply. The element consists of the “ character, a positive integer in the range 0 to 255 coded as 1 to 3 numeric characters, followed by the “ character. The and optional elements are separated from the element by a hyphe
40、n character (“-“). The element is descriptive text which identifies the sub-category within the category that the message applies to. There may be several different elements broadcast, but only one per message. The element consists of one to 16 characters, and shall not include the colon (“:“) or sq
41、uare bracket (“ or “) characters. The element is an identifier which allows the receiver to order the element or elements contained in this message within the sub-category. The element consists of the “ character, a positive integer in the range 0 to 255 coded as 1 to 3 numeric characters, followed
42、by the “ character. The element is separated from the element by a colon character (“:“). The element is text which provides information within the sub-category. Each element may contain zero or more data items, the limit being set by the size of the DL message. The element consists of one or more d
43、ata items. A data item consists of one or more characters, at least one of which must be non-whitespace, and shall not contain the semi-colon character (“;“). Additional data items after the first are separated by semi-colon characters (“;“). When multiple data items have been transmitted in a eleme
44、nt, the receiver will order them alphabetically with respect to each other. If a broadcaster-defined ordering is required, the data items should be broadcast in separate messages so that each has a unique . ETSI ETSI TS 102 652 V1.1.1 (2007-10) 8 The element controls the lifetime of the message with
45、in the receiver. It is an optional element. If the element is omitted, the receiver defined default value shall apply. The element consists of one, two or three period characters (“.“) and may only take the following values: “.“ : 24 hours; “ : 12 hours; “.“ : 1 hour. The element always appears at t
46、he end of the message. No trailing characters are permitted (this will lead to the characters comprising the element being treated as part of the final element). If the final data element ends with one or more period characters (“.“), then this will be interpreted as a element. If this behaviour is
47、not desired, a space character (“ “) should be appended to the element. The applies to all the data items within the message. 6 Updating and deleting messages 6.1 Updating messages To update the element of a message, a new message with the same , and is transmitted with the updated element. The new
48、element may have a different number of data items as desired. To update the element of a message, a new message with the same , and is transmitted with the updated element. The element and element may both be updated with a single message. The lifetime of a message may be extended by repeating the m
49、essage. Receivers shall re-calculate the lifetime of the message each time it is received. 6.2 Deleting messages To delete a message, a new message with the same , and is transmitted with. a element with zero data items (i.e. the element is a colon character (“:“). NOTE: There are no guarantees that all receivers that were tuned to a service when the original message was broadcast will still be tuned to that service when a delete command is transmitted. It is therefore strongly recommended that the element should always be used. Messages w
