ETSI TS 101 993-2002 Digital Audio Broadcasting (DAB) A Virtual Machine for DAB DAB Java Specification《数字音频广播(DAB) DAB用虚拟机 DAB Java规范(版本1 1 1)》.pdf

1、ETSI TS 101 993 1.1.1 (2002-03) Technical Specificafion Digital Audio Broadcasting (DAB); A Virtual Machine for DAB: DAB Java Specification 2 ETSI TS 101 993 VI .I .I (2002-03) The pre ent d Reference DTS/JTC-DAB-27 Keywords API, audio, broadcasting, DAB, data, digital ETSI 650 Route des Lucioles F-

2、O6921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 O0 Fax: +33 4 93 65 47 16 Siret No 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-prfecture de Grasse (06) No 7803/88 Important notice Individual copies of the present document can be downloaded from: http:/w.e

3、tsi.orq cument may be made available in more than one electronic version or in print. In any ca e 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 printing on ETSI printe

4、rs 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 hp:l/partal.etsi.arltb/sa

5、slsaus.asp If you find errors in the present document, send your comment to: Cori vriaht Notifica tion No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. O European Telecommunications Standards Instit

6、ute 2002. O European Broadcasting Union 2002. All rights reserved. DECTTM, PLUGTESTSTMand UMTSTMare Trade Marks of ETSI registered for the benefit of its Members. TIPHONTM and the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark of

7、 ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI 3 ETSI TS 101 993 VI .I .I (2002-03) Contents Intellectual Property Rights . .5 Foreword . 5 Introduction . .5 1 2 3 3.1 3.2 4 4.0 4.1 4.1.1 4.2 4.3 4.3.1 4.3.2 4.4 4.4.1 4.4.2 4.4.3 4.4.4 4.4.5 4.4.6 4.4.7

8、 4.4.8 4.4.9 4.4.10 4.4.11 4.4.12 4.4.13 4.5 4.6 4.7 Scope 6 References . .6 Definitions and abbreviations .6 Definitions . 6 Abbreviations . . 7 The DAB package 7 Summary . 7 The communication concept 7 The communication between the application and the DA 7 Commands 8 Examples 11 EPG . 11 Ticker 17

9、 Command Types 19 Tuning . . .20 Searching 21 Scanning . . .22 Accessing service directory information Accessing service information Monitoring reception quality Selecting an audio service . Selecting an object . . .23 . .24 . .25 Selecting a slideshow or a dynamic label service . Selecting a broadc

10、ast website service . . . . . . . 5 The runtime package 43 5.0 Summary . .43 5.1 The DAB Application Model . . .43 5.2 Control of Java applications . 45 5.2.1 Packaging 45 5.2.2 Loading classes . . .46 5.2.3 Control of applications. . . .46 5.2.3.1 Application context . . .46 5.2.3.2 Proxy . . .46 5

11、.2.3.3 Example 48 5.3 5.4 5.4.1 5.4.2 5.5 6 6.1 6.1.1 6.1.2 Security managenient . 50 Resource management . Model . . Conflict Reso . Configuration managemen . The User YO Package . 58 Signalling . 58 DAB Java User Application Profile ( DJUAP) . 58 Platform 58 ETSI 4 ETSI TS 101 993 VI . 1 . 1 (2002

12、-03) 6.1.3 6.1.4 6.1.5 6.1.6 6.1.6.1 6.1.6.2 6.2 6.2.1 6.2.1.1 6.2.1.2 Version 58 Content 58 Access . 58 Defined profiles 59 Standard Personal Java Profile (SPJP) 59 Network enabled Personal Java Profile (NPJP) 59 DABJava platforms 59 PersonalJava 1.1 . 59 Core Packages . 59 . DABJava profiles: spec

13、ific packages 60 6.2.1.2.1 Standard Personal Java Profile (SPJP) 60 6.2.1.2.2 Network-enabled Personal Java Profile (NPJP) 60 Annex A (normative): The DAB Java Classes . 61 A.l Package dab 61 A.2 Package dab.si 113 A.3 Package dab.events . 121 A.4 Package dab.data 145 Annex B (informative): Bibliogr

14、aphy . 159 History 160 ETSI 5 ETSI TS 101 993 VI .I .I (2002-03) 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 available for ETSI members and non-mem

15、bers, and can be found in ETSI SR O00 3 14: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notijied to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (5). Pursuant to the ETSI IPR

16、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 O00 3 14 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This

17、 Technical Specification (TS) has been produced by the Joint Technical Committee (JTC) Broadcast of the European Broadcasting Union (EBU), Comit Europen de Normalisation ELECtrotechnique (CENELEC) and the European Telecommunications Standards Institute (ETSI). NOTE: The EBU/ETSI JTC Broadcast was es

18、tablished 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, which is responsible for the standardization of radio and televisio

19、n 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 active members in about 60 countries in the European broadcasting are

20、a; its headquarters is in Geneva. European Broadcasting Union CH-I218 GRAND SACONNEX (Geneva) Switzerland Tel: +41 22 717 21 11 Fax: +41 22 717 24 81 I n t rod uct ion This clause contains an extension of the DAB specifications to provide a Java-based software framework for developing portable DAB d

21、ata services applications. A task force (Task Force Virtual Machine) was established inside the EUREKA 147 Consortium to discuss and to spec a Virtual Machine for executing applications. The concept of Virtual Machine is related to the requirements of providing a type of application that can be exec

22、uted independently from hardware specific configuration. Due to its strong flexibility and commercial success, Java was chosen as a base technology for solving the requirements of a portable environment and for speciSling a set of API designed for the DAB environment. A DAB extension to the Java API

23、 have been designed by the members of the Task Force for virtual Machine: such extension provides the software framework for designing, implementing and executing portable applications specifically targeted to the DAB system. The DAB Java Framework is divided in three basics module or packages: a DA

24、B specific extension of the Java API, a runtime support for the DAB applications execution environment, and a DAB I/O package for signalling the DAB Java extension over the DAB signal. ETSI 6 ETSI TS 101 993 VI .I .I (2002-03) 1 Scope The present document specifies a DAB related API for Java. This A

25、PI enables the download of Java programs via DAB and their control of their execution. Additionally, it provides an interface to the functionality of DAB. 2 Refe re nces The following documents contain provisions which, through reference in this text, constitute provisions of the present document. R

26、eferences are either specific (identified by date of publication andor 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. il ETSI EN 301 234 (V1.2.1 onwards): “Digital Audio Broadca

27、sting (DAB); Multimedia Object Transfer (MOT) protocol“. ETSI TS 101 812: “Digital Video Broadcasting (DVB); Multimedia Home Platform (MHP) Specification“. ETSI EN 300 401: “Radio Broadcasting Systems; Digital Audio Broadcasting (DAB) to mobile, portable and fixed receivers“. 21 31 3 3.1 Definitions

28、 and abbreviations De fin it ions For the purposes of the present document, the following terms and definitions apply: application controller: This entity is part of the runtime framework and is responsible for the control of a downloaded application. It acts as an intermediate between the applicati

29、on that initiated the download and the downloaded application. command: transaction between a DAB client and the DAB package. It consists of a request, which is sent from the client to the package and confirmations and notifications, which are sent from the package to the client. DAB resource: colle

30、ction of hardware and software components that reside on a DAB terminal NOTE: For example, hardware resources are audio, video, input devices, DAB receiver settings and commands; software resources are DAB Platform API access, DAB terminal API access, etc. package: This is used throughout the text i

31、n two ways. First, it designates a Java package. Additionally, it also designates a component in DAB Java. virtual component: PAD user application, which is treated like a regular (audio or data) component ETSI 7 ETSI TS 101 993 VI .I .I (2002-03) 3.2 Abbreviations For the purposes of the present do

32、cument, the following abbreviations apply: API DAB EPG FIG IO JDK MOT NPJP PAD SPJP UA VM WIRC Application Programming Interface Digital Audio Broadcasting Electronic Programme Guide Fast Information Group Input/Output Java Development Kit Multimedia Object Transfer Network-enabled Personal Java Pro

33、file Programme Associated Data Standard Personal Java Profile User Apllication Virtual Machine (not only the Java Virtual Machine, but also in the sense of the whole runtime environment for DABJava) WorldDAB Information and Registration Centre, Wyvil Court, Wyvil Road, LONDON SW8 2TG, England, Tel:

34、+44 171 896 90 51, Fax: +44 171 896 90 55, E-mail: -g 4 4.0 The DAB package Summary The DAB package enables applications (and applets) to access DAB resources. In clause 4.1 the basic and high-level communication concept is described. The former is based on the Event-Listener pattern. The latter con

35、sists of transactions, so called commands, in which the application sends requests to the package and the package responds with confirmations and notifications. In clause 4.2 the particular commands and resulting patterns are presented. The use of these commands is exemplified in clause 4.3. For eac

36、h command there is a typical interaction. This is described in clause 4.4. In clause 4.5 the dependencies between the commands are explained. The commands can be only be used if the client is registered. This is shown in clause 4.6. Clause 4.7 consists of a description of the classes, which are cont

37、ained in the package. 4.1 The communication concept This clause describes the communication concepts for the use of the DAB package. The DAB package provides high-level access to the services of the Digital Audio Broadcasting (DAB) System. The package uses the Event-Listener pattern (see Bibliograph

38、y, “Design Pattern, Element of Reusable Object-oriented Software by Erich Gamma“) for the communication between the DAB system and the application. On top on this basic communication pattern a transaction concept is defined (e.g. to deal with ongoing events). 4.1 .I The communication between the app

39、lication and the DAB package The DAB package provides an asynchronous interface. If an application calls a method of DABSource (the basic interface), the result is not passed back as a return value. Instead the method initiates a new transaction and just returns. This transaction will generate event

40、s for intermediate or final results that are passed to the application using the DABListener interface. This mechanism for passing back results to the application, follows the Event-Listener pattern. The package acts as a source for events that are distributed to all components which implement the D

41、ABLis tener interface and which are registered as listeners. ETSI 8 ETSI TS 101 993 VI .I .I (2002-03) The following piece of code shows, how to use this in an application: import dab.*; public class MyApplication extends DABAdapter private DABClient dabClient=new DABClientO; public void start 0 / C

42、onfiguration dabclient. open ( ) ; / Registration dabClient.addDABListener(this); . / initiate request for object dabclient. select0bj ectReq (.) ; . dabClient.removeDABListener(this); public void selectObjectCnf(Select0bjectCnfEvent e) . 1 The class MyApplication is subclassing DABAdapter to act as

43、 a DABListener. DAPAdapter is an auxiliary class, which implements the DABLis tener with empty methods. The variable dabclient is used to interface to the DAB package. Before the client can be used, the connection to the receiver has to be set up using open. The next step is to register the applicat

44、ion, so that it gets events. This is achieved by calling addDABListener. When we initiate a request like select0bj ectReq (see table i), the package will call our select0bj ectCnf method for events of type SelectObj ectCnfEvent. In the end the application calls removeDABListener to stop any event di

45、stribution to itself. Commands The basic transaction model in the DAB package is that a client issues requests and the DAB package responds with confirmations and notifications. Such a transaction is called a command. A command is initiated by a request and is finalized by a confiimation. If notific

46、ations are sent while a command is executed, the notification informs about the progress of the transaction. Notifications are also used in situations when a DAB client requests particular information which cannot be delivered immediately or in situations where updates may occur after the fiist requ

47、est for information has been satisfied. In the latter case notifications are delivered after the confiimation until the command is explicitly cancelled. ETSI 9 ETSI TS 101 993 VI .I .I (2002-03) SeledSI SeledReceptionlnfo SeledObject Get Location Info OperationControl selectSIReq SelectSICnf siNt se

48、lectReceptionlnfoReq selectReceptionlnfoCnf receptionlnfoNt selectObjectReq selectObjectCnf object Nt getLocationlnfoReq getlocationlnfocnf IocationlnfoNt ope ration Co ntro I Req ope ration Co ntro ICnf ServiceFollowing Ntf, Svstem Fai lu re To summarize this, commands are executed by sending reque

49、sts, confirmations and notifications. Three different command patterns are used in the DAB package (see figure 1). All commands are listed in table 1 sorted by the pattern type (endings with Req = request, Cnf = confirmation, Ntf = notification). The patterns describe only the message sequence for one command. If commands are interleaved which means two commands running at the same time an arbitrary sequence of message types is possible. I Svstem Failure“ ETSI 10 ETSI TS 101 993 VI .I .I (2002-03) (CommandName)Req 1 1 time (CommandName)Cnf a) Req - Cn