WO2000022816A1 - Gestion et duree de vie d'une application logicielle pour des applications de diffusion - Google Patents

Gestion et duree de vie d'une application logicielle pour des applications de diffusion Download PDF

Info

Publication number
WO2000022816A1
WO2000022816A1 PCT/US1999/023721 US9923721W WO0022816A1 WO 2000022816 A1 WO2000022816 A1 WO 2000022816A1 US 9923721 W US9923721 W US 9923721W WO 0022816 A1 WO0022816 A1 WO 0022816A1
Authority
WO
WIPO (PCT)
Prior art keywords
applications
terminal
application
api
api enables
Prior art date
Application number
PCT/US1999/023721
Other languages
English (en)
Inventor
Petr Peterka
Branislav N. Meandzija
Geetha Mangalore
Samuel A. Iacovera
Original Assignee
General Instrument Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by General Instrument Corporation filed Critical General Instrument Corporation
Priority to KR1020017004614A priority Critical patent/KR20010080122A/ko
Priority to BR9914557-0A priority patent/BR9914557A/pt
Priority to EP99951932A priority patent/EP1119963A1/fr
Priority to JP2000576614A priority patent/JP2002527844A/ja
Priority to CA002346483A priority patent/CA2346483A1/fr
Priority to AU64264/99A priority patent/AU766782B2/en
Publication of WO2000022816A1 publication Critical patent/WO2000022816A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N5/00—Details of television systems
    • H04N5/44—Receiver circuitry for the reception of television signals according to analogue transmission standards
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/443—OS processes, e.g. booting an STB, implementing a Java virtual machine in an STB or power management in an STB
    • H04N21/4431—OS processes, e.g. booting an STB, implementing a Java virtual machine in an STB or power management in an STB characterized by the use of Application Program Interface [API] libraries
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/442—Monitoring of processes or resources, e.g. detecting the failure of a recording device, monitoring the downstream bandwidth, the number of times a movie has been viewed, the storage space available from the internal hard disk
    • H04N21/4424—Monitoring of the internal components or processes of the client device, e.g. CPU or memory load, processing speed, timer, counter or percentage of the hard disk space used
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
    • H04N21/81—Monomedia components thereof
    • H04N21/8166—Monomedia components thereof involving executable data, e.g. software

Definitions

  • the present invention provides a software architecture for managing applications at a television set-top terminal.
  • the following acronyms and terms are used:
  • API Application Programming Interface
  • ATSC Advanced Television Systems Committee
  • DASE ATSC T3/S17 Digital TV Application Software Environment
  • DAVIC Digital Audio-Visual Council
  • DTV Digital Television
  • EPG Electronic Program Guide
  • IRD Integrated Receiver Decoder
  • ISO International Standards Organization
  • JVM Java Virtual Machine
  • a set-top terminal also referred to as an IRD or a subscriber terminal, is a device that receives and decodes television signals for presentation by a television.
  • the signals can be delivered over a satellite, through a cable plant, or by means of terrestrial broadcast, for example.
  • VOD video on demand
  • voice mail voice mail
  • audio mail e.g., audio mail
  • telephony services stock ticker
  • weather data e.g., weather data
  • travel information e.g., travel information
  • games e.g., gambling, banking, shopping, voting, and others.
  • applications may also enable Internet connectivity and possibly Internet-based telephony.
  • the set top functionality is enabled through specialized hardware and software.
  • the applications may be communicated to a set- top terminal via a network, loaded locally (e.g., via a smart card) , or installed at the time of manufacture, for example.
  • a network loaded locally (e.g., via a smart card) , or installed at the time of manufacture, for example.
  • System Service requirements propose a number of requirements for managing the applications at a set- top terminal .
  • This is a section from the ATSC T3/S17 draft specification which describes application management related requirements (Section 13) . Accordingly, it would be desirable to provide set-top software for managing applications at a set- top terminal .
  • the software should provide an API for retrieving and registering new applications that are received at the terminal, e.g., via a download from a headend, and providing an identifier for each application.
  • the API should be independent of the operating system and hardware of the terminal . It would be desirable to provide an ITU-T
  • the mechanism should control starting, stopping, pausing and resuming of the applications.
  • the mechanism should enable an application to advertise its state to other applications, and allow the other applications to access the advertised state .
  • the mechanism should allow retrieving of application and resource version information.
  • the mechanism should allow accessing of application location information.
  • the mechanism should provide verification of the integrity of an application, and validation of the suitability of the application for use in the set-top terminal.
  • the mechanism should notify the user of the existence of a new application after it is registered.
  • the mechanism should provide an administrative locking or unlocking of an application.
  • the mechanism should advertise the operational state, alarm status, and availability status of an application.
  • the architecture should be compatible with Java(tm), ActiveX (tm) or an equivalent type of component based object-oriented technology.
  • the mechanism should be suitable for use with any application at a terminal, regardless of how it was received or installed.
  • the present invention provides a system having the above and other advantages .
  • the present invention provides a software architecture for managing applications in a set-top television terminal .
  • a television set-top terminal includes a computer readable medium having computer program code means, and means for executing the computer program code means to implement an Application Programming Interface (API) .
  • API Application Programming Interface
  • application data which defines applications is recovered at the terminal according to locators associated with the applications.
  • the locator may be a PID, channel number, channel name, Transport Stream ID, Service ID, a combination thereof, or something else.
  • the locator may be in the form of a Uniform Resource Locator (URL) .
  • URL Uniform Resource Locator
  • the applications are registered and installed at the terminal, and a user is notified of the presence of the applications after registration and installation thereof. Thus, the user is notified when the application is made available locally at the terminal and is ready to be invoked/started.
  • An application may use a resource, usually a device, function or a process on the receiver (e.g. tuner, modem, database, etc.)
  • a resource usually a device, function or a process on the receiver (e.g. tuner, modem, database, etc.)
  • the API enables the retrieval of the applications as downloadable software applications, or broadcast software applications.
  • the API may be independent of an operating system and hardware of the terminal.
  • the API may provide an ITU-T X.731-based mechanism for monitoring and controlling the applications .
  • the API may enable running and subsequent stopping of the applications.
  • the API may enable pausing of the applications once they are running, and subsequent resuming of the applications.
  • the API may enable particular ones of the applications to advertise their respective states to other applications .
  • the API may enable at least one of the other applications to access the advertised state of at least one of the particular advertising applications.
  • An application state may have several different values (enabled, disabled, etc.) To access a state means to have the ability to learn about the current state value .
  • the API may enable retrieval of version information associated with the applications.
  • the API may enable verification of the integrity of the applications. Integrity in this case may mean that the code that was received by the receiver is legal and valid based on the programming language specification used to code the application (e.g., Java programming language, etc.)
  • the API may enable validation of the suitability of the applications for the terminal.
  • the API may enable administrative locking and unlocking of the applications.
  • the API may enable particular ones of the applications to advertise respective alarm statuses, availability statuses, procedural statuses, operational states, administrative states and usage states thereof to other ones of the applications.
  • FIG. 1 shows package relationships and dependencies in accordance with the present invention.
  • FIG. 2 represents application-related classes and interfaces and their relationships in accordance with the present invention.
  • FIG. 3 describes those classes and interfaces related to state management in accordance with the present invention.
  • FIG. 4 depicts relationships between the utility classes and interfaces in accordance with the present invention.
  • FIG. 5 is an interaction/sequence diagram showing how an EPG application, which displays video as well as data channels with applications available on them to the user, can invoke a download and subsequent execution of the downloaded application in accordance with the present invention.
  • FIG. 6 shows a set of interactions/sequences that demonstrates how one application can be managed by an application manager and monitored by an agent in accordance with the present invention.
  • the present invention provides a software architecture for managing applications in a set-top television terminal .
  • the present invention specifies an API which satisfies the DASE Application Management System Service requirements.
  • FIGs 1-4 are class diagrams and FIGs 5 and 6 are sequence (or interaction) diagrams.
  • a class diagram represents the static structure of a system, and shows a pattern of behaviors that the system exhibits. This is accomplished by showing the existence of classes and their relationships.
  • Each class is represented by a box with three sections. The top section lists the class name. The middle section denotes a list of attributes, and the bottom section denotes a list of operations .
  • a solid or dashed line between classes denotes an association or dependency.
  • a white diamond tip denotes aggregation by reference, while a black diamond tip denotes aggregation by value.
  • a triangular arrowhead denotes a restricted navigation, e.g., inheritance of operation but not of structure.
  • a class is a template that defines a data structure, method and function calls for an object.
  • An interface defines a set of methods/function calls that can be manipulated by a class. The class provides the code for implementing an interface.
  • the proposed API addresses the following requirements :
  • the API will provide a mechanism to retrieve a downloadable or broadcast application. This is done via a registration mechanism, which can specify a URL of an application (obtained from the PSIP API or its extensions based on T3/S13 and S16 work) to be downloaded and made available.
  • ATSC T3/S13 and T3/S16 specifications define protocols for delivering applications to the receiver, signaling their presence in the transport stream and providing information about the applications.
  • the URL is used as an identifier for applications in an example embodiment, but other identifiers may be used.
  • the API will provide a mechanism to install and uninstall an application.
  • the Registration mechanism installs the application so that it can be invoked/started. 3.
  • the API will provide a mechanism to initialize (launch), start, and stop an application.
  • the Application interface provides methods to perform these actions. 4.
  • the API will provide a mechanism to pause and resume an application.
  • the Application interface provides methods to perform these actions .
  • the API will provide a mechanism for applications to maintain an access state.
  • ITU-T X.731 is an international standard which defines management states, status codes and state transitions for manageable objects (devices, resources, applications, etc.)
  • the API will provide a mechanism to retrieve version information for the application and its resources, including required APIs.
  • the Applicationlnfor ation interface allows the retrieval of the above information.
  • the API will provide a mechanism to access application location information.
  • the application location information can be represented in a URL format (to be standardized by ATSC) in the DAVIC Locator class.
  • a locator is an opaque object which encapsulates a URI (Universal Resource Identifier) of a particular resource (an application in this case) .
  • the API will provide a mechanism to verify an application's integrity and validate its correctness. For example, this may mean that it does not include viruses or will not do any damage to the receiver.
  • the JVM verifier satisfies this requirement; therefore, it is not necessary define a specific API to do so .
  • the API will provide a registration mechanism allowing the application to notify the user of its existence .
  • S13 APIs which provide information about a specific application. This information can be used to download an application by registering it with the
  • ApplicationRegistry Once registered, a user can use it.
  • This proposal consists of two main packages: org.atsc .application and org .a sc .management , and a helper package org.atsc .utility .
  • the first package includes application-specific classes and interfaces.
  • the other package represents classes and interfaces that are related to managing application states based on the ITU-T management standard. The latter is separated into its own package since it can be applied to any manageable object such as DTV receiver resources, or downloadable applications.
  • An application is free to support a subset of the defined states and status attributes as appropriate to the specific application. DASE may mandate a subset of these in order to provide for a better interoperability between applications with respect to management.
  • ATSC may define a minimal set of states and status codes that are supported by all applications. Some, more complex, applications may support more. For example, some applications may not support the "degraded" Availability Status - they either work or they don't - nothing in between.
  • FIG. 1 shows the package relationships and dependencies in accordance with the present invention.
  • the org .atsc . application package 105 uses classes and interfaces defined in the org.atsc .management package 110, org.atsc .utility package 115 and org.davic.net package 120.
  • the packages are logically related by the dashed arrows, which denote dependency.
  • FIG. 2 represents application-related classes and interfaces and their relationships in accordance with the present invention.
  • An interface is labeled by ⁇ interface>> , while those not so labeled are classes.
  • the classes include: RegistryFactory 215, Exception 220, ApplicationAvailabilityException 225, ApplicationAlreadyRegisteredException 230 , ApplicationNotRegisteredException 235, ApplicationRegistryEvent 245, and EventObject 250.
  • the interfaces include: ApplicationRegistry 205, Registry 210, ApplicationCause 240, ApplicationRegistryListener 255, StateChangeListener 260, ObjectStates 265, Application 270, and Applicationlnformation 275.
  • FIG. 3 describes those classes and interfaces related to state management in accordance with the present invention. Like-numbered elements correspond to one another in the figures.
  • the classes and interfaces include: AdministrativeState 305, OperationalState 310, UsageState 315, ObjectState 320, AlarmStatus 325, AvailabilityStatus 330, ProceduralStatus 335, ResourceStateException 340, Sourcelndicator 345, and StateChangeEvent 350.
  • FIG. 4 depicts relationships between the utility classes and interfaces in accordance with the present invention.
  • the classes and interfaces include RegistryType 405.
  • FIG. 5 is an interaction/sequence diagram showing how an EPG application, which displays video as well as data channels with applications available on them to the user, can invoke a download and subsequent execution of the downloaded application in accordance with the present invention.
  • the diagram was generated using Rational Rose(tm) software .
  • a number of example objects are provided, including "user” 505, "EPG: Application” 270' (an example of the Application interface 270 of FIG. 2), "PSIP Database” 515, “dataChannel” 520, "factory -.Registry Factory” 215, “registry application Registry” 205, “downloader”
  • the EPG retrieves the application information including the URL (Locator) , gets access to the ApplicationRegistry via the RegistryFactory and requests a registration of the new application.
  • the application locator URL
  • the registry fires (e.g., sends/emits) an event to all listeners to indicate that the new application is registered and available.
  • the EPG application listens to these events and notifies the user of the new application availability. Once the application is downloaded and installed, the user can request its execution via the registry. The registry actually starts the application.
  • the "EPG: Application” object 270' calls the “getDataApps” method from the "dataChannel” object 520;
  • the "EPG:Application” object 270' calls the “displayApps” method from the "user” object 505;
  • the "user" object 505 calls the "selectApp” method from the "EPG: Application” object 270' ;
  • the "EPG:Application” object 270' calls the “getRegistry (String) " method from the "factory : Registry Factory” object 215;
  • the "EPG:Application” object 270' calls the “registerApplication (Locator) " method from the
  • the "registry application Registry” object 205 calls the “download” method from the "downloader” object 525; 8.
  • the "EPG:Application” object 270' calls the “getApplicationlnformation (Locator) " method from the "registry application Registry” object 205; 10.
  • the "EPG:Application” object 270' calls the “displayAppinfo” method from the "user” object 505;
  • the "user" object 505 calls the "invokeApp” method from the "EPG : Application” object 270' ;
  • the "user" object 505 calls the
  • FIG. 6 shows a set of interactions/sequences that demonstrates how one application can be managed by an application manager and monitored by an agent in accordance with the present invention.
  • Agent StateChangeListener 260'' (or 270'').
  • the agent registers as a StateChangeListener to a specific application.
  • the application changes its internal states based on internal or external causes.
  • the application was suspended, which changed its OperationalState to DISABLED.
  • the application creates a StateChangeEvent and sends it to all registered listeners; in this case the agent.
  • the agent can determine the state that changed and its old and new values by interrogating the event, e.g., by calling the methods available on the StateChangeEvent object, such as getOldValue ( ) , getnewValue () , etc.
  • the above sequence may be implemented via the following example steps 1-11:
  • the "appManager: StateChange” object 260' calls the “ star ()” method from the "appl application” object 270''; 2.
  • the "appManager -.StateChange” object 260' calls the “suspendO” method from the "appl -.Application” object 270'';
  • the "appl application” object 270'' calls the “stateChange (StateChangeEvent) " method from the
  • the "agent : StateChangeListener” object 260'' calls the “getStateO” method from the "event -.StateChangeEvent” object 350',- 7.
  • the "agent : StateChangeListener” object 260'' calls the “getNewValue ( ) " method from the "event : StateChangeEvent” object 350', • 9.
  • the "appManager : StateChange” object 260' calls the “resumed " method from the
  • the "appl application” object 270'' calls the "StateChangeEvent” method from the
  • the "appl application” object 270'' calls the “stateChange (StateChangeEvent) " method from the "agent : StateChangeListener” object 260''.
  • APIs as possible are defined as interfaces rather than as classes . This provides more freedom and fewer restrictions for the API implementation. Since Java interfaces don't have constructors or static methods, some interfaces such as the ApplicationRegistry have an associated RegistryFactory class that returns the appropriate implementation of the ApplicationRegistry interface.
  • the RegistryFactory class may be based on the Factory Method pattern, which, as is known from the field of object-oriented programming, is a methodology and structure for solving a problem.
  • Section 6.1 describes the application-related packages .
  • This package includes classes and interfaces related to application lifecycle, registration and management .
  • This class represents a base class of all downloadable applications. It provides a basic application lifecycle support and additional descriptive information about the application in the form of an Applicationlnfo class.
  • This class implements the GenericStates interface to add management capability to a downloadable application.
  • This interface provides a uniform mechanism to manage any object in a standard way.
  • An Application can support a subset of these states as appropriate to the specific application.
  • the class is derived from ObjectStates. Public Operations: start () :
  • the application can acquire any needed resources, perform its initialization and start execution. If this application supports the Administrative
  • Public operations are those methods that may be called and used by other objects since they are visible outside of the object (e.g., class). In contrast, private operations are visible only to the class itself.
  • getVendor 0 String Returns the name of the application vendor or author .
  • getVersion () String
  • Version numbers use a "Dewey Decimal" syntax that consists of positive decimal integers separated by periods
  • the source is where the application came from (e.g., channel 39, HBO, CNBC, etc.)
  • This interface provides a limited access to the Application Registry. It allows other applications to get information about existing applications, to show an interest in a particular application
  • the interface is derived from Registry.
  • registerApplication applicationID : Locator
  • Locator Called to add this application from the registry.
  • the application is specified via its Locator (URL) .
  • the registry is responsible for locating the application, downloading it and notifying the caller of its availability.
  • This method is protected via the security mechanisms in order to protect unauthorized access to applications.
  • getApplications () Application!] This method allows a retrieval of all registered applications .
  • This method is protected via the security mechanisms in order to protect unauthorized access to applications.
  • startApplicatio applicationID:Locator
  • the method call returns as soon as the requested application starts executing in its own thread space .
  • This method of all registered ApplicationRegistryListeners is called by the ApplicationRegistry object when an ApplicationRegistryEvent is fired.
  • Short is one format for integers (2 bytes vs. 4 bytes) .
  • This package includes classes and interfaces related to object management. It can be applied in its entirety or as a subset as relevant to the specific managed entity. It is applicable for managing state and status attributes of DTV receiver resources as well as applications.
  • the resource is administratively prohibited from performing services for its users. This could relate to a local lockout, such as a parental lockout of certain channels or applications, but can also be used to remotely (from the headend, uplink or cable operator) "lock" the application so that the user cannot start it, e.g., if a problem with an application is detected.
  • a local lockout such as a parental lockout of certain channels or applications
  • remotely from the headend, uplink or cable operator
  • -Unlocked The resource is administratively permitted to perform the services to users. This is independent of its inherent operability.
  • -Shutting down Use of resource is administratively permitted to the existing instances of users only. The manager may at any time cause the object to revert to Unlocked state.
  • ADMIN_TYPE : short 1
  • getOperationalState () int Called to get the current value of the
  • -under repair The resource is currently being repaired. When the under repair value is present, the operational state is either disabled or enabled.
  • -critical One or more critical alarms indicating a fault have been detected in the resource, and have not been cleared.
  • the operational state of the managed object can be disabled or enabled.
  • -major- One or more major alarms indicating a fault have been detected in the resource, and have not yet been cleared.
  • the operational state of the managed object can be disabled or enabled.
  • -minor One or more minor alarms indicating a fault have been detected in the resource, and have not yet been cleared.
  • the operational state of the managed object can be disabled or enabled.
  • -alarm outstanding One or more alarms have been detected in the resource.
  • the condition may or may not be disabling. If the operational state is enabled, additional attributes, particular to the managed object class, may indicate the nature and cause of the condition and the services that are affected.
  • -in test The resource is undergoing a test procedure. If the administrative state is locked or shutting down, then normal users are precluded from using the resource and the control status attribute has the value reserved for test. Tests that do not exclude additional users can be present in any operational or administrative state but the reserved for test condition should not be present. -failed: The resource has an internal fault that prevents it from operating. The operational state is disabled.
  • -power off The resource requires power to be applied and is not powered on. For example, a fuse or other protection device is known to have removed power, or a low voltage condition has been detected. The operational state is disabled.
  • the resource requires a routine operation to be performed to place it online and make it available for use.
  • the operation may be manual or automatic, or both.
  • the operational state is disabled.
  • -off duty The resource has been made inactive by an internal control process in accordance with a predetermined time schedule. Under normal conditions the control process can be expected to reactivate the resource at some scheduled time, and it is therefore considered to be optional.
  • the operational state is enabled or disabled.
  • -dependency The resource cannot operate because some other resource on which it depends (e.g., a resource not represented by the same managed object) is unavailable. For example, a device is not accessible because its controller is powered off.
  • the operational state is disabled, -degraded: The service available from the resource is degraded in some respect, such as in speed or operating capacity. Failure of a test or an unacceptable performance measurement has established that some or all services are not functional or are degraded due to the presence of a defect.
  • the resource remains available for service, either because some services are satisfactory or because degraded service is preferable to no service at all.
  • Object-specific attributes may be defined to represent further information indicating, for example, which services are not functional and the nature of the degradation.
  • the operational state is enabled. -not installed: The resource represented by the managed object is not present, or is incomplete. For example, a plug- in module is missing, a cable is disconnected or a software module is not loaded. The operational state is disabled.
  • getAvailabilityStatus () int Called to get the current set of values of the
  • the procedural status attribute is supported only by those classes of managed objects that represent some procedure (e.g., a test process) which progresses through a sequence of phases .
  • the procedure may be required to reach certain phase for the resource to be operational and available for use (i.e., for the managed object to be enabled) . Not all phases may be applicable to every class of managed object. If the value of this attribute is an empty set, the managed object is ready, for example, the initialization is complete.
  • the resource requires initialization to be invoked by the manager before it can perform its normal functions, and this procedure has not been initiated.
  • the manager may be able to invoke such initialization through an action.
  • the terminating condition may also be present.
  • the operational state is disabled, -not initialized: The resource requires initialization before it can perform its normal functions, and this procedure has not been initiated.
  • the resource initializes itself autonomously, but the operational state may be either disabled or enabled, depending upon the managed object class definition.
  • -initializing The resource requires initialization before it can perform its normal functions, and this procedure has been initiated but is not yet complete. When this condition is present, the initialization required condition is absent, since initialization has already begun.
  • the operational state may be disabled or enabled, depending upon the managed object class definition.
  • -reporting The resource has completed some processing operation and is notifying the results of the operation, e.g., a test process is sending its results.
  • the operational state is enabled.
  • -terminating The resource is in a termination phase. If the resource does not reinitialize itself autonomously, the Initialization Required condition is also present and the operational state is disabled. Otherwise, the operational state may be either disabled or enabled, depending upon the managed object class definition.
  • PROCEDURAL_TYPE : short 16
  • This interface defines the Mask for Usage State.
  • -Active The resource is in use, but has spare operating capacity to provide additional users at this instant.
  • -Busy The resource is in use, but has no spare operating capacity to provide additional users at this instant.
  • This interface allows objects which are meant to be managed in a standard way to implement a unified interface that supports all, or a suitable subset of, states and status values.
  • the defined state and status attributes are specified by the ITU-T standard X.731 for State Management. Derived from AlarmStatus, ProceduralStatus,
  • the event parameter provides information about what state has changed.
  • the class is derived from Exception.
  • This Event is fired when a state changes its value. It is distributed to all registered StateChangeListeners . The event is derived from EventObject . Public Operations: getState () : short
  • This package provides a set of supporting and utility classes and interfaces used by other packages.
  • This interface provides a common root to all specialized registry interfaces, such as ApplicationRegistry, ResourceRegistry, etc. It is provided so that the RegistryFactory can return a base type.
  • the interface is derived from RegistryType .
  • getRegistryType () String Called to determine the type of registry implemented by the object returned by the RegistryFatory ' s method getRegistry ( ) .
  • This class provides a mechanism to create objects that implement specific Registry interfaces, such as the ApplicationRegistry.
  • RegistryFactory () Public Operations: RegistryFactory () :
  • This interface defines names for different registry types, such as an application registry, etc .
  • the present invention provides a software architecture for managing applications at a television set-top terminal.
  • Application data such as a program guide, stock ticker or the like, is recovered at the terminal according to a locator associated with the application data.
  • the application data is registered and installed at the terminal, and a user is notified of the presence of the application data after registration and installation thereof.
  • LANs local area networks
  • MANs metropolitan area networks
  • WANs wide area networks
  • internets intranets
  • intranets and the Internet, or combinations thereof .

Abstract

L'invention concerne une architecture de logiciel, permettant de gérer des applications au niveau d'un boîtier de raccordement de télévision. Une interface applicative (API) fournit un mécanisme basé sur la norme ITU-T X.731, permettant de contrôler et de commander les applications. Des applications, telles qu'un guide de programmes télévisés, un service d'informations boursières ou analogue, sont récupérées au niveau du terminal en fonction d'un dispositif de repérage associé. Les applications sont enregistrées (205) et installées au niveau du terminal, et un utilisateur est informé de la présence de ces applications après leur enregistrement. L'API (270) permet d'exécuter, de marquer une pause, de reprendre et d'arrêter les applications. L'API permet également aux applications d'avertir d'autres applications, de leur état respectif, tel qu'un état d'alarme (325), un état de disponibilité (330, un état de procédure (335), un état de fonctionnement (305), et un état d'utilisation (315).
PCT/US1999/023721 1998-10-13 1999-10-07 Gestion et duree de vie d'une application logicielle pour des applications de diffusion WO2000022816A1 (fr)

Priority Applications (6)

Application Number Priority Date Filing Date Title
KR1020017004614A KR20010080122A (ko) 1998-10-13 1999-10-07 소프트웨어 응용프로그램 라이프사이클 및 방송응용프로그램에 대한 관리
BR9914557-0A BR9914557A (pt) 1998-10-13 1999-10-07 Ciclo de vida de aplicação de software e gerenciamento para aplicações de transmissão
EP99951932A EP1119963A1 (fr) 1998-10-13 1999-10-07 Gestion et duree de vie d'une application logicielle pour des applications de diffusion
JP2000576614A JP2002527844A (ja) 1998-10-13 1999-10-07 放送アプリケーション用のソフトウエアアプリケーションライフサイクル及びマネジメント
CA002346483A CA2346483A1 (fr) 1998-10-13 1999-10-07 Gestion et duree de vie d'une application logicielle pour des applications de diffusion
AU64264/99A AU766782B2 (en) 1998-10-13 1999-10-07 Software application lifecycle and management for broadcast applications

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US10394398P 1998-10-13 1998-10-13
US60/103,943 1998-10-13

Publications (1)

Publication Number Publication Date
WO2000022816A1 true WO2000022816A1 (fr) 2000-04-20

Family

ID=22297831

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US1999/023721 WO2000022816A1 (fr) 1998-10-13 1999-10-07 Gestion et duree de vie d'une application logicielle pour des applications de diffusion

Country Status (8)

Country Link
EP (1) EP1119963A1 (fr)
JP (1) JP2002527844A (fr)
KR (1) KR20010080122A (fr)
CN (1) CN1330832A (fr)
AU (1) AU766782B2 (fr)
BR (1) BR9914557A (fr)
CA (1) CA2346483A1 (fr)
WO (1) WO2000022816A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002076101A1 (fr) * 2001-02-13 2002-09-26 Shanghai Dazheng (Group) Co., Ltd. Systeme et procede sur demande permettant la selection aleatoire de video sur demande sur un reseau tv unidirectionnel cable
EP1500267A1 (fr) * 2002-03-29 2005-01-26 Digeo, Inc. Bande de television interactive ayant des capacites de type pvr
EP2338279A2 (fr) * 2008-09-30 2011-06-29 TQTVD Software Ltda Gestionnaire de fichiers numériques et procédé de gestion de fichiers numériques dans un appareil pour la réception de télévision numérique
WO2014073912A1 (fr) * 2012-11-11 2014-05-15 엘지전자 주식회사 Procédé et appareil servant à traiter un signal de service numérique
US8798612B2 (en) 2003-09-30 2014-08-05 Kyocera Corporation Mobile communication terminal for controlling startup of application based on received message and information providing system

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100574317C (zh) * 2004-06-02 2009-12-23 华为技术有限公司 网络设备管理装置
CN104185045A (zh) * 2007-02-02 2014-12-03 索尼株式会社 信息处理设备和方法
CN102012887B (zh) * 2010-11-30 2013-02-13 广东星海数字家庭产业技术研究院有限公司 一种多硬件兼容刷卡驱动系统
CN103729240B (zh) * 2013-12-02 2017-02-22 青岛海信电器股份有限公司 应用程序控制方法

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5768539A (en) * 1994-05-27 1998-06-16 Bell Atlantic Network Services, Inc. Downloading applications software through a broadcast channel
DE19650515A1 (de) * 1996-12-05 1998-06-25 Inst Rundfunktechnik Gmbh Verfahren zum Decodieren von Zusatzdaten

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5768539A (en) * 1994-05-27 1998-06-16 Bell Atlantic Network Services, Inc. Downloading applications software through a broadcast channel
DE19650515A1 (de) * 1996-12-05 1998-06-25 Inst Rundfunktechnik Gmbh Verfahren zum Decodieren von Zusatzdaten

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
EVAIN J -P: "THE MULTIMEDIA HOME PLATFORM", EBU REVIEW- TECHNICAL,BE,EUROPEAN BROADCASTING UNION. BRUSSELS, no. 275, pages 4-10, XP000767493, ISSN: 0251-0936 *
RATH K ET AL: "Set-top box control software: a key component in digital video", PHILIPS JOURNAL OF RESEARCH,NL,ELSEVIER, AMSTERDAM, vol. 50, no. 1, pages 185-199, XP004008210, ISSN: 0165-5817 *
WALL W. E.: "An Advanced Video Platform for the Cable Industry", FOURTH INTERNATIONAL WORKSHOP ON COMMUNITY NETWORKING PROCESSING, 11 September 1997 (1997-09-11) - 12 September 1997 (1997-09-12), Atlanta, GA, USA, pages 31 - 33, XP002128740 *

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002076101A1 (fr) * 2001-02-13 2002-09-26 Shanghai Dazheng (Group) Co., Ltd. Systeme et procede sur demande permettant la selection aleatoire de video sur demande sur un reseau tv unidirectionnel cable
EP1500267A1 (fr) * 2002-03-29 2005-01-26 Digeo, Inc. Bande de television interactive ayant des capacites de type pvr
EP1500267A4 (fr) * 2002-03-29 2006-02-08 Digeo Inc Bande de television interactive ayant des capacites de type pvr
US8798612B2 (en) 2003-09-30 2014-08-05 Kyocera Corporation Mobile communication terminal for controlling startup of application based on received message and information providing system
US8995953B2 (en) 2003-09-30 2015-03-31 Kyocera Corporation Mobile communication terminal that stores accumulated communication charge for an application
US9008627B2 (en) 2003-09-30 2015-04-14 Kyocera Corporation Mobile communication terminal and information providing system
US9203634B2 (en) 2003-09-30 2015-12-01 Kyocera Corporation Mobile communication terminal, information providing system, program, and computer readable recording medium
EP2338279A2 (fr) * 2008-09-30 2011-06-29 TQTVD Software Ltda Gestionnaire de fichiers numériques et procédé de gestion de fichiers numériques dans un appareil pour la réception de télévision numérique
EP2338279A4 (fr) * 2008-09-30 2013-05-22 Tqtvd Software Ltda Gestionnaire de fichiers numériques et procédé de gestion de fichiers numériques dans un appareil pour la réception de télévision numérique
WO2014073912A1 (fr) * 2012-11-11 2014-05-15 엘지전자 주식회사 Procédé et appareil servant à traiter un signal de service numérique
US9602877B2 (en) 2012-11-11 2017-03-21 Lg Electronics Inc. Method and apparatus for processing digital service signal

Also Published As

Publication number Publication date
AU6426499A (en) 2000-05-01
CN1330832A (zh) 2002-01-09
KR20010080122A (ko) 2001-08-22
CA2346483A1 (fr) 2000-04-20
AU766782B2 (en) 2003-10-23
EP1119963A1 (fr) 2001-08-01
JP2002527844A (ja) 2002-08-27
BR9914557A (pt) 2003-01-07

Similar Documents

Publication Publication Date Title
US7487534B1 (en) Application programming interface (API) for accessing and managing resources in digital television receiver
US9473827B2 (en) Apparatus and methods for implementation of network software interfaces
US10863239B2 (en) Methods and apparatus for software provisioning of a network device
US8799723B2 (en) Methods and apparatus for event logging in an information network
RU2346407C1 (ru) Способ и устройство для выполнения обновления программного обеспечения в цифровом телевизионном принимающем устройстве
US7149889B2 (en) Proactive reboot
US20030191823A1 (en) System and method for providing customizable device capabilities to network equipment in a non-service affecting manner
EP2362316A1 (fr) Überwachung und Steuerung des Betriebs einer Vorrichtung in einem verteilten Netzwerk aus Rundfunkvorrichtungen
KR20010080210A (ko) 구성 가능한 기능을 갖는 텔레비전 셋톱박스
US20090259990A1 (en) Mobile Device Software Management Method and Apparatus
AU766782B2 (en) Software application lifecycle and management for broadcast applications
CN108600841B (zh) 一种机顶盒的参数操作方法
Peng et al. Digital television application manager
US7917921B2 (en) Control of an interactive application
US20010027464A1 (en) Operating system abstraction interface for broadband terminal platform firmware
AU2002321784A1 (en) Control of an interactive application in a data stream
US10394540B1 (en) Software incremental loader
MXPA01003617A (en) Software application lifecycle and management for broadcast applications
KR20070063571A (ko) Ｍｈｐ 애플리케이션들의 시동 시간을 감소시키기 위한시스템 및 방법
CA2200010A1 (fr) Infrastructure de gestion de processus
Hendry et al. A dynamically configurable multimedia middleware
GUIDE Green Book
KR20050059351A (ko) 디지털방송수신기의 락업정보 신고방법
KR20100081408A (ko) 방송 수신기 및 리턴 채널 상태 모니터닝 방법

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 99814369.3

Country of ref document: CN

ENP Entry into the national phase

Ref document number: 1999 64264

Country of ref document: AU

Kind code of ref document: A

AK Designated states

Kind code of ref document: A1

Designated state(s): AE AL AM AT AU AZ BA BB BG BR BY CA CH CN CU CZ DE DK EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT UA UG US UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
121 Ep: the epo has been informed by wipo that ep was designated in this application
ENP Entry into the national phase

Ref document number: 2346483

Country of ref document: CA

Ref document number: 2346483

Country of ref document: CA

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 09807050

Country of ref document: US

WWE Wipo information: entry into national phase

Ref document number: PA/a/2001/003617

Country of ref document: MX

WWE Wipo information: entry into national phase

Ref document number: 1020017004614

Country of ref document: KR

ENP Entry into the national phase

Ref document number: 2000 576614

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 64264/99

Country of ref document: AU

WWE Wipo information: entry into national phase

Ref document number: 1999951932

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 1999951932

Country of ref document: EP

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

WWP Wipo information: published in national office

Ref document number: 1020017004614

Country of ref document: KR

WWG Wipo information: grant in national office

Ref document number: 64264/99

Country of ref document: AU

WWW Wipo information: withdrawn in national office

Ref document number: 1020017004614

Country of ref document: KR

WWW Wipo information: withdrawn in national office

Ref document number: 1999951932

Country of ref document: EP