JP2002528971A - Television set-top box with configurable features - Google Patents

Abstract

(57) [Summary] Provide set-top software that can be developed. A software architecture framework is for a soft set-top box. Set-top software architecture (200, 1000) enables consideration of set-top applications and middleware software functions (120), independent of operating system (110) and hardware (100) I do. Various types, such as large number of users, secure access to resources, application download, registration, start, stop and monitoring, resource download, registration, start, stop and monitoring, and management of audio, video and data presentations Function can be supported.

Description

DETAILED DESCRIPTION OF THE INVENTION

This application is based on US Provisional Application No. 60 / 104,777, filed on Oct. 19, 1998.

[0002] The present invention provides a software architecture for software set-tops.
Provides a framework for its different architectural elements and Opencable Advanc
Associate with ed Set Top API Classification.

[0003] The current OpenCable API classification is summarized in Section 7 of the Detailed Description below.

The following abbreviations and terms are used: API-Application Program Interface; STSC-Advanced Television Systems Committee; STM-Asynchronous Transfer Mode CA-Conditional Access; Conditional Access; CORBA-Common Object Request Broker Architecture Request Broker Architecture; CSLIP-Connectionless Serial Line Interface Protocol
DASE-ATSC T3 / S17 Digital TV Application Software Environment (Serial Line Interface Protocol)
V application software environment); DAVIC-Digital Audio-Visual Council; DC-2-Digicipher II (tm), digital video standard proprietary to General I
nstrument (GI) Corporation (Digital Video Standard proprietary to General Instrument Corporation); DSCC—Digital Storage Media Command and Control; DTV—Digital Television; DVB -Digital Video Broadcast; DVD-Digital Video Disc; EPG-Electronic Program Guide; FTP-File Transfer Protocol; GUI- Graphical User Interface
HSSIO-High-Speed Serial I / O; I / O-Input / Output; IIOP-Internet Inter Orb Protocol; IP-Internet Protocol・ Protocol); IPG-Interactive Program Guide; ISO-International Standards Organization; JVM-Java Virtual Machine; MIB-Management Information Base; MPEG-Moving Picture Experts Group; PSIP-Program and System Information Protocol; RAM-Random Access Memory; RMI-Remote Method Invocation ); Sat-Satellite (Satellite); SI- (DVB) Service Information (Service Information); SMPTE-Society of Motion Picture a nd Television Engineers; SNMP-Simple Network Management Protocol; SODA-Indicates a security chip that is owned by General Instrument Corporation. S / PDIG-STAMP-Set Top Applications and Middleware Platform; S-vid-Video connector interface
TCP-Transmission Control Protocol; UHF-Ultra High Frequency; UML-Unified Modeling Language; v.34-Physical interface standard xDSL-High-speed Digital Subscriber Loop modem technology (high-speed digital subscriber loop modem technology).

[0005] A set-top box, also referred to as an Integrated Received Decoder (IRO) or a subscriber terminal, is a device that receives and decodes television signals for presentation on television. . The signal is transmitted by satellite broadcasting via a cable plant or by terrestrial broadcasting. The latest set-tops also support video-on-demand, pay-per-view, interactive shopping, electronic transactions, and available internet connectivity and internet telephony. Set-top functionality is enabled by special hardware and software.

Previously, set-top software with relatively simple features was small and unorganized, and was primarily concerned with minimizing required memory capacity and processing cycles. However, support for services such as data, the Internet, Internet telephony, etc. may require a large number of users, many applications, resources such as audio, video, graphics, and other data, decoding, composition, coordination and presentation. Raises new issues, including management. Existing set-top software solutions do not solve these problems.

[0007] Thus, from relatively simple functions, small, unorganized, memory and processing cycle saving software, to software with relatively complex functions, being larger, organized, memory and processing cycle intensive It is desirable to provide set-top software that can evolve in the process of evolving to. Preferably, the underlying technology underlying the next generation set-top software architecture employs Java (TM), ActiveX (tm) or an equivalent type of element-based object-oriented technology.

[0008] The technology should allow for the consideration of set-top applications and middleware independent of operating systems and hardware.

Also, reliable control access, registration, start, stop, and monitoring for a large number of users and resources, resource download, registration, start, stop, and monitoring, management, and management of audio, video, and data presentations; It would be desirable to provide a device for support of other functions.

The present invention provides a system having the above and other advantages. The company, General Instruments, calls this technology "Set-Top Application and Middleware Platform (STAMP)."

SUMMARY OF THE INVENTION The present invention provides a software architecture framework for soft set tops.

[0012] Set-top software allows for consideration of set-top applications and middleware software separately from the operating system and hardware.

The present invention provides secure administrative access to multiple users, resources, application download, registration, start, stop, and monitoring, resource download, registration, start, stop, and audio, video, and data presentation. Various types of functions can be supported, such as monitoring and management of data.

In a particular implementation, the invention is used to provide software to a television set-top terminal. The terminal includes a computer readable medium having computer program code means and means for executing the computer program code means for implementing the layered software architecture. In a layered software architecture, the application layer allows the user to interact with the terminal and the middleware supports the application by providing an application program interface (API); The operation system layer supports middleware, and the hardware layer supports the operation system layer. Furthermore, the layered software architecture enables the functions of the application layer and the configuration of the middleware layer separately from the operation system layer and the hardware layer.

[0015] The layered software architecture includes a set-top management layer that supports the application layer by configuring the management services of the terminal. The management service includes at least one of application, user, resource, and presentation management.

The set top management layer can execute a status information module to specify the status of the resources of the terminal. The status information module is ITU-T X.731
May be based on

The software architecture may further provide an application program interface (API) to provide configuration functions. The API allows the terminal to support a large number of users or to ensure access to managed resources. The API allows the terminal to download, register, start, stop, and monitor applications in the application layer. The API also allows the terminal to manage audio, video and / or other data presentations.

The software architecture also includes set-top management, presentation management, application management, user management, resource management, set-top management,
One or more of an agent and a program view assistant may be provided.

A corresponding method is also provided.

DETAILED DESCRIPTION OF THE INVENTION The present invention provides a software architecture framework for soft set tops.

FIG. 1 illustrates the evolution of the set-top terminal software architecture according to the present invention.

Set-top software is viewed as an evolutionary process that evolves from relatively simple functionality, small, unstructured, memory and processing cycle savings to relatively complex, structured, memory and processing cycle intensive. Can be Java (tm), ActiveX
(Tm) or an equivalent type of element-based object-oriented technology can be seen as the underlying technology underlying the next generation set-top software architecture.

This technique is referred to as “General Instrument Set Top Application and Middle Software Plot Form (STAMP)”. This technology allows for the consideration of set-top applications and middleware software functions independently of the operating system and hardware.

STAMP provides reliable control access to multiple users, resources, application download, registration, start, stop, and monitoring, resource download, registration, start, stop, and audio, video, data presentation, And provide equipment for monitoring and management support of other functions. This technology allows for the consideration of set-top applications and middleware software functions independently of the operating system and hardware.

STAMP is architected based on the Java API platform. Therefore, the most straightforward implementation of STAMP is to use Java. FIG. 1 illustrates the evolution of a simplified form of set-top software architecture.
The current architecture includes a hardware layer 100, an operating system layer 110, and a native application and middleware layer 120. "Native" applications and middleware are designed for use with specific operating systems and hardware environments. In the near future architecture, the application and middleware layer 120 will evolve to include a combination of proprietary applications and middleware 122 and native applications and middleware 120. In the long term future architecture, progress will be made to include only proprietary applications and middleware 122 (separate from the operating system and hardware). For example,
Applications such as browsers are written to the abstraction layer separately from the operating system and hardware environment.

The approach taken in the design of the STAMP is to use the STAMP element until it is not feasible due to performance and other conditions, where the STAMP element can be replaced by a native element.

FIG. 2 shows a detailed set-top terminal software architecture according to the present invention. The figure shows the layered architecture of STAMP's near future solution.

The architecture 200 includes a hardware layer 205, a device driver layer 210, and a real-time operation system LAO 215. The other layer 222 includes a STAMP interpolator task 222, a compiled STAMP task 225, and a native task application task 230. The next layer 232 is a native API 265 and a number of sub-layers (including STAMP element sub-layer 260, STAMP application API sub-layer 255, standard API sub-layer 250 (including standards such as DAVIC, DVB, STSC, etc.), STAMP middle Wear AP
I sub-layer 245, and a sub-layer having a STAMP interpolator task 235 and a STAMP compiler 240).

Next, a STAMP set-top management layer 270 and a layer 272 with a STAMP application 275 and a native application 280 are provided. Applet layer
285 is also given.

The layers in the software architecture exhibit a possible dependency from higher layers to lower layers. For example, if an application uses the STAMP element 260 (in order, the standard API 250 (ST
(Which can run on the AMP interpolator 235 or can be compiled with the STAMP compiler 240).

Generally, each layer is said to support or service a layer above it.

The user interacts with the set top through two top layers, an applet layer 285 and application layers 275,280. Any type of interaction with the set top is passed through the application or applet. The different strata were defined for the following reasons:

1. The top layer is entirely temporary, and contains process entities that run in applications such as browsers, are downloaded over the Internet through broadcast channels, or distributed by other means. The applet runs within the application, and thus utilizes the resources of the application and can be limited within its capabilities. The application may be a STAMP application or a native application.

2. The application is permanent or at least long-term. They are the only unit-level application processing entities and are part of the more recent upgrades via basic set-top software distribution or code download or other means. On the STAMP side, they execute as lightweight processing groups (eg, Java thread groups).

3. STAMP set-top management controls all set-top resources and multiplexes them between different set-top applications.

4. The application, applet, and management elements are a set of STAMP elements (
For example, Java Bean Bag). The different sets of elements are, for example,
Defined for different problem areas, such as graphics and networks. The advantage of using a set of elements is the uniformity of the elements, that is, it is easier to build a house than a brick of different sizes than a brick.

5. The STAMP element is created using various APIs. The top layer of the API in the software architecture consists of these APIs defined to create the appropriate abstraction for different areas such as conditional access and set-top management. S
The TAMP element can use any of the API layers, but the preferred API access layer is the following one, which is the STAMP application API layer 255.

6. The STAMP application API is defined using a standard API that defines an abstraction of common set-top functions, such as MPEG PSI, DVB SI, etc., which has development capabilities throughout the industrial sector. The STAMP application API can use any of the API layers, but the preferred API access layer is the following below, which is the standard API layer 250:

7. The standard API is STAMP middleware API 245, for example, personal Java, Java
Defined using standard Java APIs such as security APIs.

8. The STAMP middleware API is executed or compiled in an interlator (such as a JVM).

9. When the STAMP middleware API is translated, the interpolator executes one task or a group of tasks in the operation system 215.

10. The operating system 215 controls all set-top resources and enables interaction between various tasks and resources.

11. The operating system 215 uses a device driver 210 to control and communicate with various devices.

12. The lowest layer is the actual hardware.

An agent is a processing unit that enables functions for other entities. An example of an agent is "Man," which allows remote management of an IRD with a headend function, either via MPEG transport, a modem, or other methods.
agement ”(management), or the“ Personal ”(personal) agent is responsible for the user's behavior (eg, ProgramViewAssistant).
Assistant)) will affect the user's interests, such as monitoring user behavior and search for matching material.

§1. Excecute and Management Framework After starting the set-top, STAMP assumes the following sequence steps.

1. After OS (OS) starts and operates, STAMPInterpreter starts with Gi SetTop Program.

2. GI SetTop Program is a processing thread (threa
d) consists of one infinite loop that initializes and starts. The first thread that started is the "management thread", which assists all other threads. These threads also catch exceptions raised by the initialized device.

3. Application Thead (Application Thread) is a SetTop Manager
Initiated by the Thread Group (Set Top Manager Thread Group) as a result of an action.

4. Applet is started by Application.

5. SetTop Manager Thread Group is a SetTop Manager Thread Group inside or outside the interpreter.
Control all the above tasks.

6. The SetTop Manager Thread Group can stop the JVM and Set Top itself.

The Set Top Managemant Framework consists of the following management entities:

1. SetTopManager-This manages the settop, initiates all functions, forms all management services including application, user, resource and presentation management, and sets up presentation management ( It interacts closely with all audio-visual materials, forming, starting, stopping, and interacting with set-top agents that enable remote set-top management over the Internet or via transport streams. Work, form, stop, and interact with the program view assistant.

2. Presentation Manager-This is
It consists of three types of elements: a decoder, a compositor, and a presenter, forms all presentable devices (video, audio, etc.), controls all decoding, and controls audio and / or video presentation. Configure all presentable materials for presentation, display and process all presentable materials, possibly interact with events going to all registered applications, support user interface for presentation priority I do.

3. Application Manager-registering (loading) applications, maintaining a list of available applications,
Application life cycle, possibly including decryption or decompression and moving into address space, assessment of whether the application runs based on its execution attributes, start / stop / monitor application threads and allocated resources, intra-application communication It manages vehicles for events, forwards events to interested (registered) applications, and supports a user interface for application management.

4. User Manager—Manage a list of users, their priorities, and their access to set-top resources. Proof of permission / security that allows the element to operate. Users for users
Support for interface, user management, and set-top access control management.

5. Resource Manager-various resource specific APIs
Give access to all set-top resources via. Management of these resources. User interface support for resource management.

6. Set Top Agent-A Java SNMP agent with a MIB that enables error, configuration, accounting, performance, and set top security management.

7. Program View Assistant-Intelligent Agent utilizes forward chaining based on a unified algorithm. At a minimum, it enables the interaction of users with different types of presentation material, utilizing the IPG database. It supports interactive displays that can be started as an application, or assists the user in background mode with alerts, operating shortcuts, or other types of help.

The diagrams described below depict class relationships between various set-top management elements,
It is a Unified Modeling Language (UML) class diagram.

FIG. 3 is a top-level class diagram of set-top management according to the present invention. FIG. 3 uses a unified modeling language developed by Rational Software Corporation (USA). The class diagram shows the sexual structure of the system and shows the patterns of behavior exhibited by the system. 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 names. The middle section shows a list of attributes, and the lower section shows a list of operations. In the figure, only class names are shown for simplicity.

The solid line between the classes indicates the association. A solid line with a white diamond indicates a set of criteria, a black diamond indicates a set of values, and a triangular arrow indicates limited navigation, eg, inheritance of operations rather than structure.

In addition, a number may be shown next to the end of the line tangent to the class box to indicate the basicity of the relationship, eg, 0, 1,. “*” Means “or more”
For example, “0,... *” Indicates “0 or more”. "0 ... 1" is 0 or
Indicates a set of 1.

All management entities consist of processing threads (lightweight processing or tasks). All of the thread management is handled by the SetTopManager ThreadGroup 305 (which, in addition,
nager (application manager) 310, PresentationManager) (presentation manager) 315, UserManager (user manager) 32
0, divided into ResourceManager (resource manager) 325, SetTopAgent (set-top agent) 330 threadGroup (thread group).

All management entities interface with the SetTop Management Information Base (SetTopMIB) 335. Each management entity (MngmtEntity) 335 manages a portion of the MIB, while SetTopAgent 330 provides external access to the MIB (ie, SNMP, RMI, CORBA, IIOP, etc.). NmgmtEntit
y (managed entity) 335 is from Java language, Thread 360 and ThreadG
Related to both roup (thread group) 365.

An ApplicationManager (application manager) 310 controls an application registration (AppRegistry) 340, a presentation manager manages a user registration (UserRgistry) 350, and a resource manager manages a resource registration (ResourceRegistry) 355. The following subsections detail the different management entities.

The present invention provides an ITU-T X
Note that it allows for the application of generic state information modules, such as those described in the .731 standard. This standard is part of the Q3 standard adopted by the Telecommunications Management Network (TMN). The TMN standard was developed by the CCITT (now ITU-T) to achieve interconnection between various types of management systems and telecommunications facilities for the exchange of management information as a standardized interface. Provide an architecture for TMN is largely based on OSI management standards and includes:

Principles for TMN (ITU-T M.3010 and M.3020) that define the architecture; General Network Information Model (ITU-T M.3100); Management Services (ITU-T M.3200); Management function (ITU-T M.3400); Protocol profile for management interface (ITU-T Q.811, Q.812)
, Q.773): It is intended that all network telecommunication services and critical types of equipment may be managed by the TMN.

The TMN function exchanges management information according to the ITU-T X-700 series (OSI system management) standard. Each software element in the TMN layer represents itself and the resources it manages, like managed objects, in layers above it. The interaction between manager and agent is defined by CMISE / CMIP. The information architecture, the organization of the MIB, includes managed objects for specific technologies that can be improved from the ITU-T M3100, a general plate given in the general network information model.

All TMN communications are based on an agent-manager paradigm. The Q3 interface relies on an OSI management model that uses the OSI General Management Information Protocol. CMIP is used between the Common Management Information Service Elements (CMISE) to provide General Management Information Services (CMIS).

§1.1 Application Management The application manager controls a number of applications, all created based on a common application template that allows the application manager to monitor and control.

The application management API provides the system with functions related to the life cycle of the application and the consistency of the application.

Application Verification and Validation API-Application Verification and Validation gives the system the ability to TBD.

Application Life Cycle API-The Application Life Cycle API provides the system with functions for loading, starting, pausing, stopping and unloading applications.

Application Rgistration API—The application registration API provides the system with a function to register application version and application source information.

FIG. 4 is a diagram of a top-level UML class of a set-top application manager according to the present invention.

Elements corresponding to those in the other drawings are denoted by the same reference numerals.

Here, the ResourceClient (resource client) class 405 is a GenericApp
Associated with (generic application) class 410, which is associated with ModemProxy class 415, which is associated with ResourceProxy class 420.

The ResourceClient (resource client) class 405 and the ResourceProxy (
The resource client) class 420 may be from org.davic.resourece. Gene
The ricApp (generic application) class 410 may be from gi.settop.application.

A typical application implements the resource client 405 and resource proxy 420 interfaces for all resources used by an individual application 410.

All applications are managed by the application manager, but must interact with the presentation 31, the user 320 and the resource manager 325. FIG. 5 is a diagram of a UML class showing these dependencies.

FIG. 5 shows a diagram of a top-level UML class related to set-top application management according to the present invention.

The GenericApp (general application) class 410 includes a Download class 505, a WatchTV (TV viewing) class 510, and an Email (email) class 51.
5, Ticker (display) class 520, WeBrowser (web browser) class 525,
And various classes such as EPG class 530 (each may be from gi.settop.applications).

The interaction between the user and all management entities is controlled by the set-top control application (like all other applications, through the generic application 410 template, the application manager 3
Controlled by 10).

FIG. 6 is a top-level UML diagram of a set-top control application according to the present invention.

A set top control application (SetTopControlApp) 605 coordinates the interaction between the user and different set top managers 310, 315 and 325 through a set top control GUI (SetTopControlGUI) 610.

SetTopControlApp605 and SetTopControlGUI610 may be from gi.settop.applications.

§1.2 User Management The user profile API provides user-centric and account-centric functions to the system.

Billing API-The Billing API provides the system with functions for managing accounts and performing account related transactions.

Preferences API-The priority API gives the system the ability to manage user-centric characteristics.

[0092] Favorite Services API-The Preferred Services API gives the system the ability to manage user-defined sets and subsets of services.

The Security API provides the system with a function to control and manage access to applications, content, and services.

Content Control API—The content control API provides the system with the ability to control access to applications, content and services based on user-centric criteria (parent locks).

Conditional Access API—Conditional Access API provides a function to control access to services based on service restrictions and account restrictions.
Give to the system.

Authentication and Certificate Management API-The Authentication and Certificate Management API provides the system with functions for TBD.

Cryptography API—The Cryptography API provides the system with the ability to encrypt and decrypt content stored in or sent from the system and broadcast to the system.

Set-top user access control and user priority management are handled by the user manager. The user manager uses a set-top MIB as its information storage and interacts with the user through a set-top control application.

FIG. 7 shows a top-level class diagram of the set-top user manager UML according to the present invention.

The SecurityManager class 705 may be from java.lang.

§1.3 Resource Management The resource management API provides the system with the ability to measure, assign, and deallocate users of limited hardware systems and services. System Profile API-The System Profile API gives the system the ability to determine system resources and configuration information.

Synchronization API—The synchronization API gives the system the ability to synchronize different resources such as audio and video decoders.

Resource Allocation API—The resource allocation API provides hardware and service request, access, and release functions to the system.

System Test API—The system test API gives the system the ability to test hardware systems and services for external applications.

System Diagnostic API—The system diagnostic API incorporates system errors and provides the system with functions for testing and diagnostics.

FIG. 8 is a top-level class diagram of the set-top resource manager UML according to the present invention.

A GenericDevice class 805 (which may be from gi.settop.devices) is associated with an RsourceManager (resource manager) class 325. Access to all set-top resources by set-top applications is managed through the resource manager. Resource managers may use the DAVIC Resource API.

FIGS. 9 and 10 show possible set-top devices in accordance with the present invention.
It is a UML top level class diagram.

The GenericDevice class 805 may be associated with at least one of the following example classes. HardDrive 902, DiskDrive 904, RAMDisk 906, SmartCard 908, DVD 910, DC2Sat, ATACTerminal 914, MPEG 916, MPEG Vi
deo 918, MPEG / AC3Audio 920, Terminal 922, DVBSat 924, KeyB
oard (keyboard) 926, InputDevice (input device) 928, HSSIO, 930, Vide
oOut (video output) 932, AudioOut (audio output) 934, FrontPanelDisplay
(Front panel display) 936, SODA 938, IEEE1284 Parallel, UHFRemot
e (remote) 942, InfraredRemote (infrared remote) 94, IEEE1394 946, Anal
ogAuido (analog audio) 948, S / PDIG Digital Audio (digital audio) 950, Communication (communication) 952, DigitalCable (digital cable) 954
, XDSL 956, V34 958, 10Base T 960, ATM 962, SMPTEVideoOut (video output) 964, RGBVideoOut (video output) 966, and CCIR16VideoOut (video output) 968 class, each from gi.settop.devices Good.

Available resources interact through the general device concept. The device control API gives the system a function of managing devices. The media control API includes:

Tuning and Demultiplesing API-The tuning and demultiplexing API gives the system the ability to select services and streams.

Decoder API—The Decoder API gives the system the ability to decode video streams, audio streams, data streams, and the elements in these streams.

[0113] Playback Control API-The playback control API gives the system a function of managing the playback of the stream.

§1.4 Presentation Management Presentation management and the presentation API play a role in two different types of scenarios within the set top.

1. Presentation objects (graphics, video, audio) are generated as a result of application activation or application-related processing.

2. A presentation object is generated from a carousel as a result of a process of decoding data from the Internet or the like.

The presentation API and presentation manager (PM)
Similarly, both scenarios are facilitated. That is, the same object has the same way that it can be created and activated.

The presentation API gives the system the ability to display and control information, status, content, and control displays to the user.

Video Presentation API-The Video Presentation API gives the system the ability to manage the presentation of video data to the primary display surface.

Front Panel Display Manager API-The Front Panel Presentation Manager API gives the system the ability to control the information, status, and control displays on the front panel display surface.

Graphics Presentation API-The Graphics Presentation API provides the system with the ability to manage the display of graphic data on the primary display surface.

Front Management API-The Font Management API gives the system the ability to load, select, and display fonts on the main display surface.

Audio Presentation API-Audio
The presentation API gives the system the ability to manage the playback of audio data to the primary audio output.

A number of applications and applets in STAMP include GUIs. These include:

1. Installation and diagnostic screen 2. Give access to key set-top features and applications,
A set-top screen that meets the configuration screens (eg, rate priority, language priority, audio / video mode, etc.) 3. Flags and detailed information for WachTV (TV viewing) 4. IPG screen 5. Web Browse (Browser) screen 6. E-mail screen 7. Ticker (for stock price) 8. Applet Screen 9. Downloadable application screen.

All these GUIs are generated from a set of elements defined through the presentation API.

§2 Applet (Applet) Java Applet (Applet) is a Java Browser that can use Java.
It is supported on set-tops that host either the Java-enabled Native Browser. Applets are downloaded via http over the Internet or via the DSMCC Carousel Service.

§3 Application §3.1 WatchTV (TV viewing) The Watch TV system provides an environment for watching a simple broadcast television. The user modifies the channel and selects a specific channel to match the previous channel.

Watch TV with Parental Locks-The system provides a means for restricting user access to services, channels, or events. A password mechanism can override access restrictions. Access can be based on channel, event rate, event theme, or other criteria.

Watch TV with conditional Access-The system can provide a means to restrict access to events, services or channels based on the access right of the service provider's customer. it can. Access rights may be associated with service restrictions or account restrictions.

Watch TV with Alternate Audio-The system may make more than one audio stream available for a particular video stream. The user has the opportunity to select another audio stream for playback when synchronizing with the video stream.

Watch TV with Subtitling-The system may make available one or more texts or graphics that can be synchronized and superimposed on the video stream.

§3.2 Downloading Application The application download scenario describes the situation where a broadcast application or data service is brought into the system and stored.

Watch TV with Persistent Unsynchronized Data Service-The system provides a data service that is not synchronized with current audio and video streams (eg, stock tickers). Applications using data services (eg, a stock ticker graphic user interface) are already resident and only data (stock quotes) is transmitted in this scenario.

Watch TV with Persistent Synchronized Data Service-The system synchronizes to the current audio and video stream (eg, sports statistics corresponding to the player currently on the screen) Give data service to you. Applications that use data services are already resident in the system and only data is transmitted in this scenario.

Watch TV with Scheduled Download of Application—The system provides a means to schedule and download applications located in services that may not be the current service. .

Watch TV with Impulse Buy of Application—The system provides a means for the user to pay attention to available applications, and for the user to purchase and download applications. Give the means.

Watch TV with Background Application Update-The system provides a way for the user to download a background application (without disrupting the current audio and video presentation). give.

§3.3 Teleshopping A teleshopping scenario describes a situation where a user can seek information, products, or services through applications made available in the system.

Watch TV and Request Information-The system
It provides a means by which a user can request information corresponding to the video and audio broadcasts now. For example, during a car commercial, a user may request a brochure.

Watch TV and Impulse Buy—The system provides a way for users to purchase products that support the video and audio that the user is currently broadcasting. For example, during a promotion for a commemorative plate, a user may purchase the plate.

Browse and Buy from a Video-centric Catalog-The system provides a means for a user to navigate through a catalog containing graphics, video, and audio. The user can select and purchase a product or service in the catalog.

Browse and Buy from a Audio-centric Catalog-The system provides a means for a user to navigate through a catalog containing graphics and audio. The user can select and purchase a product or service in the catalog.

Browse and Buy from a Graphics-centric Catalog-The system provides a means for a user to navigate through a catalog containing graphics. The user can select and purchase a product or service in the catalog.

§3.4 Near Video on Demand The near video on demand (NVOD) scenario is a scenario where a user has multiple movies or services from a movie (or other audio-video). Describe the circumstances under which you can select a service).

Pay-per-View-The system provides a means for a user to purchase one service from many services. Interactivity is generally limited to the selection and purchase process.

Interactive Pay-per-View-The system provides a means for a user to purchase one service from multiple services. The user can "pause" the service until the next service is used.

§3.5 Gaming (Game) The game scenario enables a user to play a game via an Internet distribution service. The game may be a single game or a multiplayer game that is located entirely on the system (locally) or played over a network.

Watch TV and Local Participate-The system provides a means for users to watch TV programs and "cooperate" with local single-person applications. For example, during the "Wheel of Fortune", the user can "turn the wheel" and make his guess.

Watch TV and Multi-user Participate-The system gives users the means to watch TV number sets and to "cooperate" and compete with other users.

Single Player Game-The system provides a means for the user to play a system-based game without further remote collaborators.

Multi-user Game-The system provides a means for users to play system-based games with collaborators further away.

§3.6 Internet Access The Internet Access scenario allows a user to access Internet-based content or functions: html pages, email, chat, streaming audio, etc.

Browse the Web-The system provides a means for a user to browse (browse) a website.

Email-The system allows users to read, write,
And give a means to respond.

Chat—The system provides a means for a user to communicate in real time with other users on the Internet.

[0157] Watch TV with Internet Content-The system allows users to achieve Internet-based activities that are made available with or through audio-video services. And provide a means to watch video services simultaneously.

Browse Web with TV Content-The system provides a means for users to view audio or video services that are available from Internet-based items.

§3.7 Information on Demand The Information on Demand scenario allows the user to access the content associated with the information when he / she wants and wants to customize.

Pay-per-View News Service-The system provides a means for users to purchase audio, video, or text-centric news services. The service may provide headline content, in-depth content, edited information, or other levels of service.

Query for News Item-The system queries the user for a number of available sources for one or more "articles" defined by the user or belonging to criteria selected by the user. Give the means.

Personalized News-The system provides a means for users to create new services and make them preferred topics.

Subscription Services-The system provides a means for users to purchase and schedule audio, video, or text-centric news services.

§ 3.8 Electronic Program Guide The electronic program guide scenario allows a user to access channel, service, and event information. In general, the user may also control the system or use this information to navigate within the system.

Current Channel Now and Next-The system gives information about what services are currently available on the current channel and what services will follow.

All Channel Now and Next-The system is
Gives information about what services are now available on all known channels, and what services will follow.

All Channel Now and Future-The system will tell you what services are available now on all known channels and what services will be available at a given time in the future. Give information.

Request Review from Guide-The system provides a means for the user to ask for an example of a service. For example, a user may request a trailer for a video or demo of the application.

Purchase Event from Guide-The system provides a means for the user to purchase future events or services from within the electronic program guide.

Setup Program Reminder-The system provides a means for the user to schedule attention to future events at some time in the future.

[0171] Purchase Application from Guide-
The system provides a means for a user to purchase an application for download from an electronic program guide.

§3.9 Distance Learning A long distance learning scenario describes a virtual classroom where students and teachers are not together.

Watch TV with Chat—The system provides virtual classroom audio and video. The system provides a means for users to participate through chat with educators or other students (at different sites).

Watch TV with Text-The system provides virtual classroom audio and video. The system provides a means for users to participate through chat with educators or other students (at different sites).

§3.10 Home Banking The Home Banking scenario describes that a user can use services comparable to those available at a retail bank.

Information Retrieval-The system provides a means for users to access information belonging to banking functions and their personal accounts.

Transaction—The system provides the means by which users can perform typical retail bank electronic transactions.

Service Application-The system provides the means to apply for retail banking services, such as credit cards, loans and checks and transactions.

Counseling-The system provides a means for users to get personal financial support.

§3.11 Navigation (Navigation) A navigation scenario describes a situation in which a user operates content that can be used in services, applications, and systems.

Application Activation-The system provides a means for the user to activate (run or launch) the application.

Application Removal-The system provides a means for the user to remove an application from system memory, local storage, or remote storage associated with the system.

System Preferences-The system provides a means for the user to identify user-centric preferences that the system also relates to operation of the user interface.

Favorite Channel Setup-The system provides a means for the user to identify or configure a set or subset of available services.

§4. STAMP Component Architecture Element groups (bean bags) are defined to facilitate domain-specific (eg, IPG) application element formation sets. These sets are not separate. The Java Bean Bag is as follows:

1. GI Application System Bean Bag-The elements of this set include all beans that are common to all different sets of application elements. This is the information exchange mechanism, synchronization mechanism,
It may include a timing mechanism, a storage mechanism, and the like.

2. GI GUI Bean Bag-Elements of this set include all GUI beans that are common to all different applications. This may include lists, buttons, sliders, etc.

3. GI HotJava Bean Bag-Elements of this set include all elements that may be part of a browser.

4. GI IPG Bean Bag-The elements of this set include all elements that may be part of an IPG application.

5. GI Tuning Bean Bag-Elements of this set include all elements that may be part of a tuning application.

6. GI E-mail Bean Bag-The elements of this set include all elements that may be part of an e-mail application.

7. GI Download Bean Bag-Elements of this set include all elements that may be part of the download application.

8. GI Ticker Bean Bag-Elements of this set include all elements that may be part of an information table device application.

9. GI Game Player Bean Bag-The elements of this set include all elements that may be part of a game player application.

§5. Applications Programming Interfaces (API) The API provides a system with independent operating systems for hardware and extraction layers. This is because broadcast applications are sent to widely varying processor systems and operating systems, i.e., from set-top boxes with RISC processors and real-time operating systems, to personal computers with microprocessors and non-real-time operating systems. To be sent to the system.

All APIs are made available to native and Java applications. The following APIs are those defined by DAVIC and JavaS
It needs to be defined outside of what is standardized by oft.

§5.1 Event Management (Event Management) API The event management API provides a system having a function of transmitting and receiving messages, events, and “interrupts”.

Event Dispatch API—The Event Dispatch API provides a system with the ability to send messages, events, and “interrupts”.

User Input API-The user input API provides a system (keyboard, mouse, front panel, remote control, etc.) that has the function of receiving and sending events directed to the user.

Inter-Process Communications API-Inter-Process Communication API
Provides a system capable of sending events between messages, applications, processes, and threads.

Scheduling API-The Scheduling API provides a system with the ability to establish the time and date to trigger events and "interrupts".

§5.2 Application Utility API The Application Utility API provides a system with general-purpose functions commonly used by applications.

Math API-The Math API provides a system capable of performing mathematical routines.

Time API—The Time API provides a system with the ability to access time and date and perform common time routines.

String API-The String API provides a system with the ability to load, unload, and manipulate strings.

List API-The List API provides a system with functionality for managing lists and other general dynamic data structures.

File API-The File API provides a system with the function of performing file related operations.

Localization API-The Location API provides a system with the ability to perform general location operations.

Communications API—High-level interface to all communication and communication management elements, including dial-up networking, Internet rooting, transport streams, etc.

Object Services API-Support for information exchange between objects; this includes information models, types, associations, operations, characteristics, naming, registration, distribution, etc.

Database Service API-Support for data storage and retrieval functions, including general file system and registration.

Download Service API-Support for Download Service.

§5.3 Content Management (Content Management) API The content management API is to provide a system having functions related to the content life cycle and content maintenance.

Content Integrity API-The Content Integrity API provides a system with a function for TBD.

Content Download API-The Content Download API provides a system with the ability to store application broadcasts in the system.

Content Version Control (Content Version Control) API-Content
The version control API provides a system having a function for managing the version of stored or loaded content.

Content Storage API-The Content Storage API provides a system with the ability to store or retrieve content in the system, or with remote storage.

§5.4 System Information (System Information) API The system information API provides a system having functions related to MPEG-2 system information and a program information stream.

Event Information API—The Event Information API provides a system with a function for translating an event information system.

Channel and Service Map API-The Channel and Service Map API provides a system with the ability to translate system and service information streams.

§5.5 GI Presentation API See set-top management section. Decoder, compositor,
And the formation of presentation manager elements such as presenters, DA
Access to all required presentation subsystems including graphics, audio and video in addition to VIC and standard Java APIs, DAVIC and standard J
In addition to the ava API, it enables operations of all necessary presentation subsystems, initialization, startup, operation, shutdown, and adjustment of all presentation elements.

§5.6 GI Set Top Management API See section on Set Top Management. It provides element hookup functionality, element monitoring and control functionality, internal processing / Dimon / application initialization, startup, shutdown and coordination to handle asynchronous events and events caused by information collection. ， Enable setup application.

Operations Support API-Facilitates set-top management API and SNMP agent API via Java / non-Java interface.

§5.7 DAVIC APIs The following DAVIC APIs are supported.

1. Resource Notification API (org.davic.resource) —A standard mechanism by which applications register interest in rare resources, notice changes in these resources, and remove those resources in this environment.

2. MPEG API (org.davic.mpeg)-MPEG element API, MPEG section filter A
Includes PI and MPEG TransportStream API.

3. Tuning API (org.davic.tuning)-Tuning of network interfaces, including multiple network interfaces (local and / or remote).

4. Conditional Access API (org.davic.net.ca)-Interface-independent CA system for accessing CA functionality 5. DVB SI API (org.davic.net.ca) dvg.si)-Interface to the DVB SI database, including access to the actual transport stream through the cache.

6. ATSC PSIP API (org.davic.atsc.psip)-Interface to ATSC SI and PSI databases, including access to the actual transport stream through the cache.

7. Media Player API (org.davic.media)-Extension of Java Media Frame Network to facilitate set top 8. DSM-CC U-U API (org.davic.dsmccuu)-ISO / Executes a subset of the DSM-CC-UU API defined in IEC 13818-6.

§5.8 Standard Java API 1. Personal Java-This API is supplemented by a few new APIs designed to meet the needs of networked and embedded applications. It is a subset of JDK 1.1. Java API introduced after JDK1.1
Is not automatically part of the personal Java API. New APIs are reviewed and evaluated for validity before being added to personal Java.

The JDK1.1 package included in Personal Java is: java.applet java.awt java.awt.datetransfer java.awt.event java.awt.image java.awt.peer java.beans java.io java.lang java.lang.reflect java.net java.util 2. Java Text API-Supports internationalization.

3. The Java Security API is a framework for developers to easily and reliably include security features in their applets and applications. This feature includes cryptography with digital signature, encryption and authentication.

4. The Java Trade API brings secure purchasing and financial management to the Web.
JavaWallet is an early element that defines and implements a client-side framework for credit card, debit card, and electronic cash transactions.

5. Java Media Framework (JMF) is a unified architecture,
Specifies the message protocol and programming interfaces for media players, capture and conferencing. JMF
Will be issued as three APIs. The Java Media Player is published first,
The Media Capture and Java Media Conference API will follow. Java Media Player is an API for the synchronization, control, processing and presentation of compressed streaming and stored timed media, including video and audio.

6. Java RMI (including CORBA)-object oriented, supporting CORBA
Distributed processing API.

§6. Set-Top Software Architecture FIGS. 11 to 13 show a set-top software architecture framework according to the present invention.

The architecture 1000 corresponds to the architecture 200 of FIG. 2, but provides further details and examples for each layer.

The device driver core modules of the layer roughly correspond to the classes of FIGS. 9 and 10.

§7. Relationship to OpenCable API The following section summarizes the current OpenCable AP classification.

§7.1 Operating System <-> Network API
s Network protocols are used at all levels of the ASB to communicate with other clients, applications, and servers. Applications also make use of network protocols, many of which are
-> Called through the application API, the actual OS execution network
It is a stack. Protocols specifically dealing with application-level client-server issues will be covered in the client <-> server section.

§7.1.1 Video and Data Network / Transport Protocols These protocols are used for routing, connection establishment, control and disassembly of network packets. The industrial open standards are TCP for connection-oriented transfer, UDP for connectionless, real-time traffic transfer, and IP for packet routing. RSVP is used for network bandwidth and channel reservation. MPEG-2 is obviously suitable for video transfer.

§7.1.2 Session / Presentation Protocols These protocols are used for session maintenance and to give applications general procedures to request and receive data from content services. Is done. FTP is used for file transfer, HTTP is used for WWW access and HTML transfer, NNTP is used for news service access, and SMTP and IMAP are used for mail. However, there is no standard for chatting.

§7.1.3 Directory Service Protocols A directory is an almost headline-only distribution database designed for attribute indexes to locate, authenticate, and update network objects. It is. Emerging as a standard directory for TCP / IP networks, LDAP is a lightweight version of X.500's more complex directory access protocol. LDAP has been adopted by more than 40 large software vendors and supports access-independent data views, hierarchical storage, multiple storage schemes, rich access control, multiple database types and examples, and network replication.

§7.1.4 Data-Link, Physical, MAC Layer These APIs control the modulation, coding, and management of the data stream via the cable facility.

§ 7.1.5 Network Encryption Protocols These protocols are used for encryption and decryption of video, data and transaction schemes.

§7.1.6 Multi-user / Network Broadcast (Multi-user / Network Broadcast) It is required to efficiently broadcast a data stream via a network.

§7.2 OS <-> Application APIs The operating system provides the application with two sets of critical services at the top of the system that enable the execution of the application. Base OS services such as scheduling, virtual memory, multiple threading, etc. are provided for almost all services without much effort for programmers. Most of the APIs for these services are not visible. OS standard libraries, on the other hand, are predetermined code modules that are promoted for use by an application when performing functions supported by the OS.
For example, network applications are promoted to use the OS network library, and most applications are promoted to use the OS GUI library and the like. In essence, standard libraries are intended to maintain consistency, avoid duplication of effort, and speed up development. Sometimes, for aesthetic reasons, applications bypass certain libraries to optimize the code.

§7.2.1 Application Services and Libraries These APIs control the heart of the set-top box. Native applications (especially those written for ASBs when they require maximum performance and hardware interaction) run on OS services and libraries and are provided through these APIs .

§7.2.2 Computer Graphics These APIs control 2D and 3D drawing and presentation. Application programs use these to simplify graphic functions. They are also used to window tool kits for applications to implement a graphic user interface.

§7.2.3 Remote Execution Environments / Virtual Machines Enables applications stored on a network to be downloaded, executed, and discarded. Encapsulates the runtime environment, security model, and object model. Current competitors are platform-independent Java and window-specific ActiveX. Doing a version script includes JavaScript and VBScript.

§7.3 Operating System <-> Hardware AP
These APIs, commonly referred to as I-device drivers, allow operating systems to control various parts of the hardware. It is usually performed in software by the device manufacturer, which plugs into those operating systems via a well-defined device-driver architecture API proposed by the operating system vendor. For well-defined categories of devices, operating system vendors sometimes provide generic device drivers for all classes of devices. This generic driver provides a least common denominator function when the manufacturer's driver is not available. In other words, the Macintosh OS uses a general La
Printers that provide a ser writer driver but have their own driver available can make use of vendor / model specific mechanisms. Systems that automatically recognize devices and load the appropriate drivers are classified as plug-and-play.

§7.3.1 Hardware Abstraction Layer (HAL) APIs (Hardware Abstraction Layer) The HAL separates the hardware from the OS and makes the OS portable for any platform that supports HAL.

§7.3.2. Registry API Store format and control for local flash RAM storage.

§7.4. Operating System <-> Operating System These APIs are used when one OS is executed on top of another, as in a virtual machine, or Used when two OSs communicate with each other.
The latter case is rare and is usually handled through network protocols, although some elements and object models allow the distributed objects to communicate across the OS.

§7.4.1 Remote Execution Environments / Virtual Machines (VM) links t
o OS (remote execution environment OS / virtual machine link) Provides detailed control of the execution of virtual machines on an existing RTOS. When running proprietary VMs, or running open VMs closely with the OS and ownership, portability of VMs becomes important.

§7.4.2. Distributed Object Model Allows an application to store and exchange data with other networked applications in a common object format. Competitors are Microsoft's Distributed Element Object Model (DCOM) and Javabea
ns / CORBA (Common Object Request Broker Architecture). Remote procedure call mechanisms (ONC, DCE) also enter this API.

§7.5 Client <-> Server APIs Client-servers often pass application data through standard networking protocols, but require remote client management, authentication, software downloads, and updates. Is handled by a specific client-server API. These APIs typically tend to be closed and fragmented due to a number of potential combinations and challenges.

§7.5.1 Network Management Remote network management of all network elements §7.5.2. Software Management and Updates API to control software download and module loader .

§7.5.3. Network / Remote FileSystem Controls file storage and retrieval methods.

§7.5.4. Digital Certificate Control certification of users, vendors and products.

§7.5.5. Calendar Serve Protocols Determine the storage and interaction format for the user's calendaring and scheduling functions.

§7.5.6. Synchronization Protocols Requirements for clock synchronization and timing.

§7.5.7. Usage Data Gathering (Usage Data Gathering) API Defines methods and formats for usage data, collection, storage and transmission.

§7.5.8. Billing System APIs Defines methods and formats for billing data, collection, storage, and transmission.

§7.6 Application <-> File API Applications use a specific format that they use to store and retrieve data. With the exception of some high-visibility formats, these formats (ASCII, HTML) are often closed and subject to ownership. Note that static data, some applications also support the storage, retrieval, and execution of plug-in code modules and APIs that allow third-party vendors to configure such plug-ins To release.

§7.6.1. Text Document Storage Formats Storage formats for plain text documents.

§7.6.2. Hyperlinked Document Storage Formats A storage format for rich, hyperlinked text.

§7.6.3. Image Storage Formats Compression Formats for Images §7.6.4. 3D Graphics Document Storage Formats Storage formats for 3D data.

§7.6.5. Video Clip Storage Formats Streaming and non-streaming encoding of video clips.

§7.6.6. Audio Document Storage Formats Encoding of sound and music.

§7.6.7 Animation Document Storage Formats Animation encoding.

§7.6.8. Web / Video Integration Formats Defines libraries and methods for integrating web-based content with that provided by traditional TV. Examples including hyperlinked ads, button bars and display overlays, virtual web channels, etc.

§7.6.9. Personal Information Storage Storage of user identification information, preferences, and access control information §7.7. Client <-> Content APIs Controls the low content and delivery of content from the server to the client. It's actually a subset of the client-server API, but it's clear because vendors seek to contain it by requesting a proprietary server to distribute content.

§7.7.1. Web Data Serving A format for providing web content. Beyond standard HTTP, web servers can use proprietary serving methods (ie, active server pages).

§7.7.2. Video Data Serving A format for providing video content.

§ 7.7.3. Integrated Data Serving Provision and coordination of integrated web / data content.

§7.8. Content <-> Access APIs This set of APIs controls the distribution and delivery of content from various servers to clients. It's actually a subset of the client-server API, but it's clear because vendors seek to contain it by requesting a proprietary server to distribute content.

§7.8.1. Video Access Control Video stream access control and encryption.

§7.8.2. Data Access Control Authentication for data content transmission.

§7.9. Browser <-> Resident Engine APIs In fact, not the individual set of APIs per se, but the browser <-> resident engine interactions are actually OS <-> A subcategory of applications
It is clearly picked out because of its strategic importance and the fact that most browser vendors include this API in their products. In a well-designed operating system, resident HTML, VRML, Java, and caching engines are the services that OS provides to the application. However, most browser vendors bundle these important engines into the browser, thereby hiding and controlling these important APIs, even if they should be made public.

§7.9.1. Explicit HTML Engine Control Controls for accessing and using the HTML rendering engine once it has been separated from the browser. Alternatively, when proprietary formats are used, OS (OS) providers will provide evidence of the APIs used and provide them with rights to make them permanently free.

§7.9.2. Explicit Cache Control When the caching engine is separated from the browser, control for accessing and using it.

Thus, it will be seen that the present invention provides middleware software functionality independent of operating system and hardware, and set-top software that allows for consideration of set-top applications. .

The present invention provides reliable control access to multiple users, resources, application download, registration, start, stop and monitoring, resource download, registration, start, stop, audio, video, data presentation monitoring, Supports various types of functions such as management.

Although the present invention has been described in connection with various specific embodiments, those skilled in the art will appreciate that various modifications can be made without departing from the spirit and scope of the invention as set forth in the appended claims. It is clear that adaptations and modifications of the above can be made.

For example, while various syntax elements have been discussed herein, they are merely exemplary and any syntax can be used.

Further, the present invention relates to a cable or satellite television broadband communication network, a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), the Internet (internets), an intranet, and the Internet. ), Or any combination thereof, which is suitable for virtually using any network.

[Brief description of the drawings]

FIG. 1 illustrates the evolution of the set-top terminal software architecture according to the present invention.

FIG. 2 shows a detailed set-top terminal software architecture according to the present invention.

FIG. 3 shows a diagram of a top-level class of set-top management according to the present invention.

FIG. 4 shows a diagram of a top-level class of a set-top application according to the present invention.

FIG. 5 shows a diagram of a top-level class of set-top application management relationships according to the present invention.

FIG. 5 shows a top-level class diagram of a set-top control application according to the present invention.

FIG. 4 shows a diagram of a top-level class of set-top user management according to the present invention.

FIG. 8 shows a diagram of a top-level class of set-top resource management according to the present invention.

FIG. 9 shows a diagram of a top-level class of available set-top devices according to the present invention.

FIG. 10 shows a diagram of a top-level class of available set-top devices according to the present invention.

FIG. 11 illustrates a set-top software architecture framework according to the present invention.

FIG. 12 illustrates a set-top software architecture framework according to the present invention.

FIG. 13 illustrates a set-top software architecture framework according to the present invention.

[Procedure amendment]

[Submission date] April 20, 2001 (2001.2.40)

[Procedure amendment 1]

[Document name to be amended] Statement

[Correction target item name] Claims

[Correction method] Change

[Correction contents]

[Claims]

──────────────────────────────────────────────────続 き Continuation of front page (81) Designated country EP (AT, BE, CH, CY, DE, DK, ES, FI, FR, GB, GR, IE, IT, LU, MC, NL, PT, SE ), OA (BF, BJ, CF, CG, CI, CM, GA, GN, GW, ML, MR, NE, SN, TD, TG), AP (GH, GM, KE, LS, MW, SD, SL, SZ, TZ, UG, ZW), EA (AM, AZ, BY, KG, KZ, MD, RU, TJ, TM), 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 (71) Applicant 101 Tournament Drive Horsham, Pennsylvania, The United States of America

Claims (22)

[Claims] 1. A television set-top terminal having software, comprising: a computer readable medium having computer program code means; and a computer readable medium for implementing a layered software architecture. Means for executing the program code means; and wherein the application layer allows a user to interact with the terminal, and the middleware layer includes an application program interface (API).
), The application layer is supported, the operating system layer supports the middleware layer, the hardware layer supports the operating system layer, and the software architecture that is the layer is the operating system layer. And a terminal where the functions of the application layer and the middleware layer can be configured separately from the hardware layer. 2. The terminal according to claim 1, wherein the layered software architecture includes a set-top management layer that supports the application layer by configuring the terminal management service. Terminal. 3. The terminal of claim 2, wherein the management service includes at least one of application, user, resource, and presentation management. 4. The terminal according to claim 2, wherein the set-top management layer comprises:
Terminal where the state information module runs. 5. The terminal according to claim 4, wherein the status information module is based on an ITU-T X.731 standard. 6. The terminal of claim 1, further comprising an application program interface (API) for providing configurable functions. 7. The terminal of claim 6, wherein the API allows the terminal to support multiple users. 8. The terminal of claim 6, wherein said API enables said terminal to ensure controlled access of resources. 9. The terminal according to claim 6, wherein the API is such that the terminal executes an application of an application layer.
Terminal where you can download, register, start, stop, and monitor. 10. The terminal of claim 6, wherein the API enables the terminal to manage audio, video, and / or other data presentations. 11. The terminal according to claim 1, further comprising: a set-top manager, a presentation manager, an application manager, a user manager, a set-top agent, and a program view assistant. Terminal, including one. 12. A method for executing a layered software architecture for a television set-top terminal, the method comprising: providing a computer readable medium having computer program code means; Executing the computer program code means to implement the software architecture provided by the application layer, allowing the user to interact with the terminal; Is an application program interface (API
), The application layer is supported, the operating system layer supports the middleware layer, the hardware layer supports the operating system layer, and the software architecture that is the layer is the operating system layer. And the ability to configure the functionality of the application and middleware layers separately from the hardware layer. 13. The method of claim 12, wherein the layered software architecture includes a set top management layer that supports the application layer by configuring a management service of the method. Where way. 14. The method of claim 13, wherein the management service includes at least one of application, user, resource, and presentation management. 15. The method according to claim 13, wherein the set-top management layer comprises:
The method of executing the state information module. 16. The method according to claim 15, wherein the status information module is based on an ITU-T X.731 standard. 17. The method of claim 12, wherein said layered software architecture provides an application program interface (API) for providing configurable functions.
Where way. 18. The method according to claim 17, wherein the API enables support for a large number of users. 19. The method according to claim 17, wherein said API allows reliable control of resources. 20. The method according to claim 17, wherein said API enables downloading, registering, starting, stopping, and monitoring an application in an application layer. 21. The method according to claim 17, wherein said API enables management of audio, video and / or other data presentations. 22. The method of claim 12, wherein the layered software architecture comprises: a set-top manager, a presentation manager, an application manager, a user manager, a set-top agent. , And Program View Assistant.