1、 ETSI TS 102 635-1 V1.1.1 (2009-08)Technical Specification Digital Audio Broadcasting (DAB);Middleware;Part 1: System aspectsEuropean Broadcasting Union Union Europenne de Radio-Tlvision EBUUER ETSI ETSI TS 102 635-1 V1.1.1 (2009-08) 2 Reference DTS/JTC-DAB-54-1 Keywords Broadcasting, DAB, digital E
2、TSI 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 copies of the present document can be
3、 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 (PDF). In case of dispute, the ref
4、erence 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 status of this and other ETSI document
5、s 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 except as authorized by written permiss
6、ion. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2009. European Broadcasting Union 2009. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Marks of ETSI register
7、ed 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. LTE is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are
8、 Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 102 635-1 V1.1.1 (2009-08) 3 Contents Intellectual Property Rights7 Foreword.7 1 Scope 8 2 References 8 2.1 Normative references .8 2.2 Informative references9 3 Definitions, abbreviations and conventions .10 3.1 Definitions10 3.
9、2 Abbreviations .10 3.3 Conventions10 3.3.1 Syntax of binary messages10 3.3.2 BNF 11 4 Introduction 11 5 System architecture 11 5.1 Introduction 11 5.2 Receiver model.11 5.2.1 System resources 12 5.2.2 System software12 5.3 Application.12 6 Basic data formats 13 6.1 Image file formats 13 6.1.1 JPEG
10、.13 6.1.2 PNG 13 6.2 Font file formats .13 6.3 Video file formats.13 6.4 Audio file formats 13 7 Transport protocol13 7.1 Broadcast channel protocol 14 7.1.1 File transport protocol.14 7.1.2 Packet streaming protocol.14 7.1.3 Trigger protocol14 7.2 Communication channel protocol.15 7.2.1 Transmissio
11、n Control Protocol (TCP) 15 7.2.2 User Datagram Protocol (UDP)15 7.2.3 Hyper Text Transfer Protocol (HTTP)15 7.2.4 Domain Name Service (DNS) 15 8 Locator model 16 8.1 Introduction 16 8.2 Format 16 8.3 Use in APIs.16 9 Security model16 9.1 Purpose.16 9.1.1 Guarantee of application integrity 16 9.1.2
12、Verification of application provider16 9.1.3 Control of application permissions .17 9.1.4 Trace of tasks performed by applications .17 9.1.5 Authority delegation among applications .17 9.2 Application authentication17 9.2.1 Application signing.17 9.2.2 Application authentication procedure .18 9.2.3
13、X.509 profile.18 ETSI ETSI TS 102 635-1 V1.1.1 (2009-08) 4 9.2.3.1 signatureAlgorithm .18 9.2.3.2 tbsCertificate .18 9.2.4 Root certificates and CRL management .19 9.3 Application authorization .20 9.3.1 Introduction.20 9.3.2 Notation for permissions.20 9.3.3 Permission request 20 9.3.4 Receiver sec
14、urity policy20 9.3.5 Authority delegation .21 9.4 Formats of the relevant messages.21 9.4.1 Format of certificate message .21 9.4.2 Signature format .21 9.4.3 Credential format 22 10 Graphic system model22 10.1 Introduction 22 10.2 Video plane 23 10.3 Graphics plane23 10.4 Composing a screen23 11 Ap
15、plication model24 11.1 Introduction 24 11.2 Application storage and removal24 11.2.1 Storage 24 11.2.2 Receiver policy .24 11.3 Application storage, update, and removal 24 11.3.1 Application download.24 11.3.2 Application update24 11.3.3 Application removal .24 11.4.4 Lifecycle .25 11.4.4.1 Loaded s
16、tate 25 11.4.4.2 Paused state.25 11.4.4.3 Active state25 11.4.4.4 Destroyed state26 11.5 MIDlet model .26 12 Application signalling and transport 26 12.1 Application module 26 12.1.1 Definition and purpose of application module26 12.1.2 Structure of application module27 12.1.2.1 ZIP format.27 12.1.2
17、.2 Application-defined format.27 12.1.3 Application module ID and version27 12.1.4 Accessing contents of application module28 12.1.4.1 Introduction.28 12.1.4.2 URL to an application module 28 12.1.5 Compression of application module .28 12.1.6 Transport of application module.28 12.1.7 Signing applic
18、ation module 29 12.2 Application ID29 12.3 Application signalling 29 12.3.1 Signalling structure.29 12.3.1.1 Application information message30 12.3.1.2 Module information message30 12.3.1.3 Service binding message .31 12.3.1.4 Application control message .31 12.3.1.5 Certificate message .31 12.3.2 M
19、essage transport .31 12.3.3 Message monitoring31 12.4 Application state control 31 12.4.1 Application download.32 12.4.2 Application update32 12.4.3 Application removal .32 ETSI ETSI TS 102 635-1 V1.1.1 (2009-08) 5 12.4.4 Application execution.32 12.4.5 Application termination 32 12.5 Application mo
20、dule and message formats32 12.5.1 Relationship with platform standards .32 12.5.2 Message version33 12.5.3 Common data format 33 12.5.3.1 UTF-8 string33 12.5.3.2 Descriptor33 12.5.3.3 Descriptor loop34 12.5.3.4 Digital signature34 12.5.3.5 Credentials 34 12.5.4 Application module format.34 12.5.5 Fo
21、rmat of application information message35 12.5.6 Application related descriptors .37 12.5.6.1 Module download descriptor.37 12.5.6.2 Application description descriptor 38 12.5.6.3 Application icon descriptor .38 12.5.6.4 Autodownload descriptor38 12.5.6.5 Signal bound descriptor.39 12.5.6.6 MIDlet d
22、escriptor39 12.5.6.7 Profile extension descriptor.40 12.5.6.8 Application expiration descriptor40 12.5.7 Format of module information message .41 12.5.8 Format of service binding message.42 12.5.9 Format of application control message .43 12.5.10 Format of certificate message .43 13 Java environment
23、43 13.1 Introduction 43 13.2 Requirements on Java environment43 13.3 DMB extensions.43 13.3.1 Standard optional packages.44 13.3.2 Simultaneous execution of multiple applications .44 13.3.3 Graphics extension44 13.4 Simultaneous execution of multiple applications .44 13.4.1 Requirements 44 13.4.2 JV
24、M implementation 45 13.5 Standard properties.45 13.5.1 MIDlet properties45 13.5.2 System properties45 13.6 Basic APIs46 13.6.1 AsyncResult/AsyncRequestor pattern.46 13.6.2 AttributedObject pattern .47 13.7 Graphic user interface API .47 13.7.1 Screen management 47 13.7.2 Processing alpha values 48 1
25、3.7.3 User interface elements.49 13.7.4 Key mapping.49 13.7.5 Reserving keys for exclusive use49 13.7.6 Loading fonts dynamically .50 13.8 Media control API50 13.8.1 A MMAPI 1.1 profile .50 13.8.2 Player creation 50 13.9 Broadcast data access API50 13.9.1 File access API .50 13.9.1.1 Creation of fil
26、e objects50 13.9.1.2 Directory .50 13.9.1.3 Metadata51 13.9.1.4 File access .51 13.9.1.5 File update.51 13.9.2 Packet access API .51 13.9.3 Trigger API.51 ETSI ETSI TS 102 635-1 V1.1.1 (2009-08) 6 13.10 Service information API.52 13.10.1 Introduction.52 13.10.2 Service information object52 13.10.2.1
27、 SI database 52 13.10.3 SI query and view .52 13.11 Tuning API.52 13.11.1 Tuner.52 13.11.2 TunerLock.52 13.12 Service selection API .52 13.13 CAS API.53 13.13.1 Communication with CA module .53 13.13.2 Purchasable entities.53 13.14 Application control API .53 13.15 Inter-application communication AP
28、I 53 13.15.1 Messages.53 13.15.2 Port54 13.15.3 Sending messages .54 13.15.4 Receiving messages 54 13.16 Resource manager API.54 13.16.1 Introduction.54 13.16.2 Resource objects .54 13.16.3 Resource group and choice .55 13.16.4 Resource group .55 13.16.5 Resource choice 55 13.16.6 Nesting resource g
29、roups and choices55 13.16.7 Rule for determining resource ownership.55 13.17 Storage API 56 13.17.1 Implementation requirements .56 13.17.2 Per-application storage .56 13.17.3 Permissions.56 13.18 Communication channel API .56 Annex A (informative): Automated test environment for receiver certificat
30、ion 57 Annex B (informative): Delivery and processing of key events among embedded applications and MATE59 B.1 Introduction 59 B.2 Key processing of embedded applications .59 B.3 Key focus management of MATE applications .59 Annex C (informative): Accessing location information from Java application
31、s.60 Annex D (normative): API specification 61 History 251 ETSI ETSI TS 102 635-1 V1.1.1 (2009-08) 7 Intellectual 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 av
32、ailable 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 updates are available on the ETSI Web se
33、rver (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 the ETSI Web server) which are, or may
34、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) and the European Telecommunications Stan
35、dards 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 Memorandum of Understanding also CENELEC, wh
36、ich 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 programme-exchange domains. The EBU has acti
37、ve 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 1987, with funding from the European Commis
38、sion, 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 23, for DAB (see note 2) which now has worldwide acceptance. The members of the Eureka Project 147 are drawn from broadcast
39、ing 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. ETSI ETSI TS 102 635-1 V1.1.1 (2009-08) 8 1 Scope The present document establishes
40、 a standard for a platform-independent environment, where executable applications can be signalled and transferred to a receiver via a broadcasting network and executed on the receiver. It does not suppose the exclusive use of a specific broadcast network but defines the commonly-required specificat
41、ions among diverse broadcast networks. It includes the definitions of basic data formats, protocols to deliver data, to signal downloadable applications and to download them, ways to denote resources on broadcast networks, and detailed interfaces among receiver platform, broadcast and communication
42、networks, and the applications. In order to apply the present document to a target broadcast network, it is required to map abstract interfaces to concrete entities of the network and to add additional definitions specific to the network. 2 References References are either specific (identified by da
43、te 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 accepted that it will be possible to u
44、se 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. NOTE: While any hyperlinks included
45、 in this clause-were valid at the time of publication ETSI cannot 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 refe
46、rences, the latest edition of the referenced document (including any amendments) applies. 1 JSR 118: “Mobile Information Device Profile 2.0“. NOTE: See at (http:/www.jcp.org/en/jsr/detail?id=118). 2 JSR 217: “Personal Basis Profile 1.1“. NOTE: See at (http:/www.jcp.org/en/jsr/detail?id=217). 3 ISO/I
47、EC 10918-1: 1994 “Information Technology Digital compression and coding of continuous-tone still images Requirements and Guidelines“. NOTE: See at (http:/www.w3.org/Graphics/JPEG/itu-t81.pdf). 4 JPEG File Interchange Format, Eric Hamilton, C-Cube Microsystems. NOTE: See at (http:/www.w3.org/Graphics
48、/JPEG/jfif3.pdf). 5 PNG (Portable Network Graphics) Specification, Version 1.0. W3C Recommendation, October 1, 1996. NOTE: See at (http:/www.w3.org/TR/REC-png.html). ETSI ETSI TS 102 635-1 V1.1.1 (2009-08) 9 6 IETF RFC 793 (TCP): “Transmission Control Protocol“, J. Postel. 7 IETF RFC 768 (UDP): “Use
49、r Datagram Protocol“, J. Postel. 8 IETF RFC 2616: “IETF Hypertext Transfer Protocol - HTTP/1.1“. 9 IETF RFC 1034: “Domain Names - Concepts and facilities“. 10 IETF RFC 1035: “Domain Names - Implementation and specification“. 11 IETF RFC 1982: “Serial Number Arithmetic“. 12 IETF RFC 2181: “Clarifications to the DNS Specification“. 13 IETF RFC 3280: “Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile“. 14 IETF RFC 2396: “Uniform Resource Identifiers (URI): Generic Syntax“. 15 IE
