KR20010080210A - Television set-top box with configurable functionality - Google Patents

Abstract

The present invention provides a software architecture framework for a soft set top box. Set top software architectures 200 and 1000 allow for consideration of set top application and middleware software functionality independent of operating system 110 and hardware 100. The invention provides for multiple users, secure controlled access to resources, application downloads, registrations, start, stops, monitoring, resource downloads, registrations, start, stops, monitoring, and management of audio, video and data presentations. Various types of functions can be supported.

Description

TELEVISION SET-TOP BOX WITH CONFIGURABLE FUNCTIONALITY}

The current open cable API classification is summarized in section 7 of the detailed description below.

The following acronyms and terms are used.

API-Application Programming Interface;

ATSC-Advanced Television Systems Committee;

ATM-Asynchronous Transfer Mode;

CA-Conditional Access;

CORBA-Common Object Request Broker Architecture;

CSLIP-Connectionless Serial Line Interface Protocol;

DASE-ATSC T3 / S17 Digital Television Application Software Environment;

DAVIC-Digital Audio-Visual Council;

DC-2-Digital Video Standard, owned by Digicipher II®, General Instruments Corporation;

DSMCC-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;

IPG-Interactive Program Guide;

IRD-Integrated Receiver Decoder;

ISO-International Standards Organization;

JVM-Java Virtual Machine;

MIB-Management Information Base;

MPEG-Moving Picture Experts Group;

PSIP-Program and System Information Protocol (for terrestrial broadcast and cable);

RAM—Random Access Memory;

RMI-Remote Method Invocation;

Sat-communication satellite;

SI-(DVB) service information;

SMPTE-Society of Motion Picture and Television Engineers;

SNMP-Simple Network Management Protocol;

SODA-represents a security chip owned by General Instruments Corporation;

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.

A set top box, also called an IRD or subscriber terminal, is a device that receives and decodes television signals for display on a television. This signal can be transmitted by satellite or via terrestrial broadcast via a cable plant. In addition, current set-tops support video on demand (VOD), pay-per-view, interactive shopping, and e-commerce, and Internet access and possibly Internet-based telephony. To make it possible. This set-top function is made possible by specific hardware and software.

Until now, set-top software, which offered relatively simple functions, was small and unstructured, and was primarily concerned with minimizing required memory capacity and processing cycles. However, support for services such as data, the Internet, Internet telephony, etc., can be secured by multiple users, managing multiple applications, managing resources, decrypting, creating, coordinating and presenting audio, video, graphics and other data. There is a new problem involving presentation. Existing set-top software solutions do not solve these problems.

Thus, a set-top that has a relatively simple function, is compact, has no structure, and can proceed in an evolutionary process from memory and processing cycle storage software to a relatively complex function, to large, organized, memory and processing cycle intensive software. It would be desirable to provide software. Preferably, the underlying technology underlying the next-generation set-top software architecture employs object-oriented technology based on Java®, Activex®, or equivalent type of component.

This technology should allow for consideration of set-top applications and middleware software features that are independent of operating system and hardware.

In addition, to provide a device and machine for security of multiple users, access control of resources, application download, registration, start, stop and monitoring and management of audio, video and data presentations and support of some additional functions. It would be desirable.

The present invention provides a system having the above and other advantages. This technique is called the general instrument "STAMP".

The present invention provides a software architecture framework on a soft set top and associates other structural components with the Opencable Advanced Set Top API classification.

1 is a diagram showing the development of a set-top terminal software structure according to the present invention,

2 illustrates a detailed set-top terminal software structure according to the present invention;

3 is a diagram illustrating a set top management high level class diagram according to the present invention;

4 is a diagram illustrating a set-top application manager high level class diagram according to the present invention;

5 is a diagram illustrating a high-level class diagram related to set-top application management according to the present invention;

6 is a diagram illustrating a high-level class diagram of a set-top control application according to the present invention;

7 is a diagram illustrating a set-top user manager high level class diagram according to the present invention;

8 is a diagram illustrating a set-top resource manager high level class diagram according to the present invention;

9 is a diagram showing a high level class diagram of an effective set-top device according to the present invention;

10 illustrates a set top software architecture framework in accordance with the present invention.

The present invention provides a software architecture framework for a soft set top.

Set-top software allows for consideration of set-top applications and middleware software features that are independent of operating system and hardware.

The present invention can support various types of functionality, such as security for controlling access to multiple users, resources, application downloads, registrations, startups, stops, and monitoring and management of audio, video, and data presentations.

In a particular implementation, the present invention is used to provide software to a television set top terminal. The terminal comprises a computer readable medium having computer program code means and means for executing the computer program code means to realize a layered software structure. In a layered software architecture, the application layer enables the user to interact with the terminal, the middleware layer supports the application layer by providing an API, the operating system layer supports the middleware layer, and the hardware layer Support the operating system layer. Moreover, the layered software architecture allows for the configuration of the functions of the application layer and the middleware layer regardless of the operating system layer and the hardware layer.

The layered software structure includes a set top management layer that supports the application program layer by configuring the management service of the terminal. Management services include management of at least one application, user, resource, and presentation.

The set top management layer implements a status information module to indicate the resource status of the terminal. The status module is based on the ITU-T X.731 standard.

Moreover, the software architecture provides an API for providing configurable functionality. The API enables the terminal to support a large number of users and to ensure controlled access of resources. The API enables the terminal to download, register, start, stop and monitor an application program layer. The API also enables the terminal to manage audio, video and or other data presentations.

The software architecture also provides one or more set top managers, presentation managers, application managers, user managers, resource managers, set top agents, and program view assistants.

Moreover, corresponding methods are also provided.

The present invention provides a software architecture framework for a soft set top.

1 illustrates the development of a set top terminal software architecture in accordance with the present invention.

Set-top software is represented as an evolutionary process with relatively simple functionality, small, unstructured, and from memory and process cycle storage software to relatively complex, large, organized, and memory and process cycle-intensive software. Lose. Object-oriented technologies based on Java®, Activex® or equivalent type components are represented as the underlying technology underlying the next generation set-top software architecture.

This technique is called general instrument STAMP. This technology allows for consideration of set-top applications and middleware software features that are independent of operating system and hardware.

STAMP provides devices and machines for securing multiple users, access to resources, downloading, registering, starting, stopping applications, and monitoring and managing audio, video and data presentations, and supporting some additional functions. do. This technology allows for consideration of set-top applications and middleware software features that are independent of operating system and hardware.

STAMP is designed based on the Java API platform. Therefore, its easiest implementation of STAMP is using Java. 1 illustrates, in simplified form, the development of a set-top software architecture. The structure includes a hardware layer 100, an operating system layer 110, a native application and middleware layer 120. These "native" applications and middleware are designed for use in specific operating systems and hardware environments. In a near future architecture, the application and middleware layer 120 is deployed to include a combination of patented application and middleware 122 and native application and middleware 120. In the far future architecture, the application and middleware layer 120 is deployed to include only patented application and middleware 122 independent of operating system and hardware. For example, applications such as browsers are recorded in an abstraction layer independent of the operating system and hardware environment.

In the case where a STAMP component can be replaced with a native component, the approach to obtaining the design of the STAMP is to use the STAMP component if it cannot be implemented due to performance or other requirements.

2 illustrates a detailed set top terminal software architecture according to the present invention. This figure shows the layered structure of the near future solution.

This structure 200 includes a hardware layer 205, a device driver layer 210, and a real-time operating system layer 215. Another layer 222 includes a STAMP interpreter task 220 and a native application task 230. The next layer 232 is a standard that includes native API 265, multiple sublayers including STAMP component sublayer 260, STAMP application API sublayer 255, DAVIC, DVD, ATSC, etc. It includes a standard API sublayer 250, a STAMP middleware API sublayer 245, and a STAMP interpreter task 235 and a STAMP compiler 240.

Next, a STAMP set top management layer 270 is provided, followed by a layer 272 having a STAMP application 275 and a native application 280. An applet layer 285 is also provided.

Hierarchies within the software structure represent possible dependencies from the top to the bottom. For example, an application running STAMP interpreter 235 or compiled with STAMP compiler 240 would use STAMP component 260 which in turn utilizes some standard API 250.

In general, each layer is instructed to support or service the layer above it.

The user interacts with the set top and applet layers 285 and application layers 275 and 280 via two top layers. Some type of interaction with the set-top is through an application or applet. The other classes are defined by the following theory.

1. The top layer runs within an application and includes a processing entity that is actually temporary, such as a browser, for example, and is downloaded or otherwise distributed over broadcast channels and the Internet. Because applets run in an application, they can use the application's resources and be limited within their capabilities. The application can be a STAMP application or a native application.

2, the application is permanent or at least long term. The application is the only unit-level application processing entity and is part of any recent upgrade, either via basic set-top software distribution, code download or other means. On the STAMP side, the application is realized as a lightweight processing group (e.g., a Java thread group).

3. STAMP set-top management controls the entire set-top resource and multiplexes them among different set-top applications.

4. Applications, applets, and management components consist of a set of STAMP components (eg, a Java bean bag). Different component sets are defined for different problem domains such as graphics, networking, and the like. An advantage of the set of components used is the uniformity of the components. In other words, it is easier to build a house out of a brick than a variable size stone.

5. STAMP components are assembled using various APIs. The top API layer in the software architecture consists of those APIs that are specified to create appropriate abstractions for other domains such as conditional access and set-top management. The STAMP component can use any API layer, but the preferred API connection layer is the next lower layer, which is the STAMP application API layer 255.

6. The STAMP application API is defined using standard APIs that define the industry-wide viable abstraction of common set-top functions such as MPEG PSI and DVB SI. The STAMP application API can use any API layer, but the preferred API connection layer is the next lower layer, which is the standard API layer 250.

7. Standard API is defined using STAMP middleware API 245, such as standard Java APIs such as Personal Java, Java Security API, and the like.

8. The STAMP middleware API runs on the interpreter (such as JVM) or compiles.

9. When the STAMP middleware API is interpreted, the interpreter executes as a task or group of tasks in the operating system 215.

10. The operating system 215 controls the entire set top resource, and enables interaction between various tasks and resources.

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

12. Lower layer 210 is actual hardware.

An agent is a processing unit that enables functionality on behalf of another entity. An example of an agent may be a "management" agent that enables the IRD to be managed remotely by some headend facility via MPEG transport, modem or other means. Alternatively, a "personal" agent may do so at the user's benefit (eg, ProgramViewAss istant) to monitor the user's behavior and search for materials that match their behavior.

§One. Execution and Management Framework

After the set top is turned on, STAMP takes the following steps.

1. After the OS is up and running, the STAMP interpreter is started from the GI set-top program.

2. A GI set-top program consists of an infinite loop that initializes and starts a single processing thread.

The first thread started is the "managing thread", which services all other threads. In addition, these threads catch exceptions caused by initialized devices.

3. The application thread is started as a result of operation by the set-top manager thread group.

4. Applets are started by applications.

5. The set-top manager thread group controls the entire task on the set-top, either inside or outside the interpreter.

6. The set-top manager thread group can halt the JVM and the set-top itself.

The set top management framework consists of the following management entities:

1. SetTopManager-controls the settop, starts and starts all functions; To form all management services including application, user, resource and presentation management; Interact closely with the presentation manager, which controls the presentation of all audiovisual materials; Establish, start, stop, and interact with set-top agents that enable remote set-top management over the Internet or transport streams; Form, start, stop, and interact with the program view assistant.

2. Presentation Manager-consists of three types of elements, decoders, compositors, and presenters; Forms the entire representable device (video, audio, etc.); Control the decryption of the entire representable material; Constitute a totally expressible control for audio and / or video presentation; Represent the entire representable material; It probably interacts with events that are processed and sent to the entire registered application; Support the user interface for presentation preferences.

3. Application Manager-Registering (loading) an application, maintaining a list of valid applications, decrypting or decompressing, moving to the address space, determining whether the application can run based on its execution attributes, and starting it. Manages the lifecycle of an application, including / stop / monitor application threads, allocated resources, media for intra-application delivery, and forwards events to registered applications; Support user interface for application management.

4. User Manager-Manages user lists, their preferences, and their access rights as to set-top resources. Verify permissions / security to enable the component to work. Support user interface for user preference, user management, and set-top access control management.

5. Resource Manager-Provides access to the entire set-top resource through several resource specific APIs. Manage their resources. Support user interface for resource management.

6. Set-top agent-A Java SNMP agent with a MIB that allows set-top failure, configuration, accounting, performance, and security management.

7. Program View Assistant—Intelligent Agent using forward inference based on a unification algorithm; Minimize the user's association with other types of presentation materials using the IPG database; It supports an interactive display that can be launched as an application, or assists the user in background mode with the help of alerts, operation shortenings, and other types of help.

The drawings discussed below are UML (Unified Modeling Language) class diagrams illustrating the class relationships between the various set-top management components.

3 illustrates a set top management high level class diagram in accordance with the present invention. 3 utilizes UML developed by National Software Corporation. The class diagram shows the static structure of the system and shows the pattern of movement the system represents. This is accomplished by indicating the existence of classes and their relationships. Each class is represented by a box with three parts. Enter the class name at the top. The middle part shows a list of attributes, and the bottom part shows a list of operations. In the drawings, only class names are shown for simplicity.

The solid line between classes represents the association. The solid line with the white diamond tip represents the set by reference, and the solid line with the black diamond tip represents the set by value. The triangular arrowheads represent limited navigation, for example, inheritance of operations but not structure.

Furthermore, the numbers such as 0 and 1 can be arbitrarily represented in contact with the end of the line touching the class box to indicate the cardinality of the relationship. "*" Represents "ideal". For example, "0 .. *" represents "0 or more". "0 ... 1" represents a set of zeros or ones.

The entire management entity consists of processing threads (lightweight processes or tasks), all of the management processing threads are ApplicationManager 310, PresentationManager 315, UserManager 320, ResourceManager 325, and SetTopAgent 330 ThreadGroup (s). Part of SetTopManager ThreadGroup 305, which is subdivided into.

The entire management entity coordinates the SetTop Management Information Base (SetTopMIB) 335. While SetTopAgent 330 provides external connectivity to the MIB (ie, SNMP, RMI, CORBA, IIOP, etc.), each management entity (MngmtEntity) 335 controls a portion of the MIB. MngmtEntity 355 is associated with Thread 360 and ThreadGroup 365 from java.lang.

The ApplicationManager 310 controls the Application Registry 340, the Presentation Manager controls the PresentationRegistry 345, the User Manager controls the UserRegistry 350, and the Resource Manager controls the ResourceRegistry; 355). The following subsection outlines other management entities in more detail.

It should be noted that the present invention enables applications of resources and comprehensive state information modules, such as modules described in the ITU-T X.731 standard, within set-top MIBs. This standard is part of the Q3 standard adopted by the Telecommunications Management Network (TMN). This TMN standard was developed by CCITT (now ITU-T) to provide a mechanism to achieve connectivity between various types of management systems and telecommunications facilities for the exchange of management information through a standardized interface. . TMN is largely based on OSI management standard and is based on the principles of TMN (ITU-T M.3010 and M.3020) defining structure, comprehensive network information model (ITU-T M.3100) and management service (ITU). -T M.3200), management functions (ITU-T M.3400), and protocol profiles for management interfaces (ITU-TQ.811, Q812, Q773).

It means that all telecommunications and telecommunications services and major types of equipment can be managed by TMN.

TMN function exchanges management information according to ITU-T X-700 series (OSI system management) standard. Each software component in the TMN layer represents itself and the resources it manages up to the upper layers, such as managed objects. The interaction between the manager and the agent is defined by the Common Management Information Service Elements (CMISE) / CMIP. The organization of the information structure and the MIB include managed objects for specific technologies that can be subdivided from the generic templates provided in ITU-T M-3100 and the Comprehensive Network Information Model.

All TMN communications are based on the agent-manager paradigm. The Q3 interface follows the OSI management model using the OSI Common Management Information Protocol. CMIP is used between CMISE to provide Common Management Information Service (CMIS).

§1.1 Application Management

The application manager controls a plurality of applications that are all configured based on a comprehensive application program template that enables monitoring and control by the application manager.

The Application Management API provides a system with application lifecycle and application integrity related functions.

Application Validation and Validation API-The Application Validation and Validation API provides a system with functionality for TBD.

Application Lifecycle API-The Application Lifecycle API provides a system with functions for loading, starting, stopping, stopping, and unloading applications.

Application Program Registration API-The Application Program Registration API provides a system with a function to register application version and application source information.

4 illustrates a set top application manager high level class diagram in accordance with the present invention.

The same numbered elements correspond to one another in the various figures.

Here, the ResourceClient class 405 is associated with GenericApp class 410, with Modem Proxy class 415, and with ResourceProxy class 420.

ResourceClient class 405 and ResourceProxy class 420 are by org.davic.reso urces. GenericApp class 410 is by gi.settop.applications.

The generic application implements a resource client 405 and resource proxy 420 interface to the entire resource used by each application 410.

The entire application must interact with the presentation 315 and the user 320 and the resource manager 325 even though it is managed only by the application manager. 5 includes UML class diagrams illustrating these dependencies.

5 is a high-level class diagram related to set-top application management according to the present invention.

GenericApp class 410 includes Download class 505, WatchTV class 510, Email class 515, Ticker class 520, WebBrowser class 525 and EPG class 530 by gi.settop.applications, respectively. Can be associated with various classes, such as

The interaction between the user and the entire management entity is accomplished via a set top control application controlled by the application manager 310 via a comprehensive application 410 template.

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

The set top control application (SetTopControlApp) 605 coordinates interactions between users via the set top control GUI 610 and other set top managers 310, 315, 320, and 325.

SetTopControlApp 605 and SetTopControlGUI 610 are by gi.settop.applications.

§1.2 User Management

The user profile API provides a system with user-centric and accounting-oriented functions.

Billing API-The Billing API provides a system with the ability to manage accounting and perform accounting transactions.

Preferred API-The Preferred API provides a system with a function to manage user-centric features.

Favorite Service API-The Favorite Service API provides a system with the ability to manage a user-defined set and subset of services.

Security APIs provide a system with the ability to control and manage access to applications, content, and services.

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

Conditional Access API-The Conditional Access API provides a system with the ability to control access to services based on service and accounting restrictions.

Authentication and attestation management API-The authentication and attestation management API provides a system with functions for TBD.

Encryption API-The Encryption API provides a system having the ability to encrypt and decrypt content provided to the system and stored on or transmitted from the system.

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

7 illustrates a set top user manager high level class diagram in accordance with the present invention.

The SecurityManager class 705 is from java.lang.

§1.3 Resource management

The resource management API provides a system having a function of determining, allocating, and releasing users of bound hardware systems and services.

System Profile API-The System Profile API provides a system with the ability to determine system resources and configuration information.

Synchronization API-The Synchronization API provides a system with the ability to synchronize heterogeneous resources such as audio and video decoders.

Resource Allocation API-The Resource Allocation API provides a system with the ability to request, access, and release hardware systems and services.

System Test API-The System Test API provides a system with functionality for external applications to test hardware systems and services.

System Diagnostic API-The System Diagnostic API provides a system with built-in tests and functions to diagnose system failures.

8 illustrates a set top resource manager high level class diagram according to the present invention.

GenericDevice class 805 by gi.settop.device is associated with ResourceManager class 325.

Access to all set-top resources by the set-top application is managed through the resource manager 325. Resource managers use the DAVIC Resource API.

9 shows a UML high level class diagram of a valid set top device according to the present invention.

GenericDevice class 805 is associated with one or more of the following example classes: HardDrive 902, DiskDrive 904, RAMDisk 906, SmartCard 908, DVD 910, DC2Sat 912, ATSCTerminal 914 , MPEG (916), MPEG Video (918), MPEG / ACAudio (920), Terminal (922), DVBSat (924), Keyboard (926), InputDevice (928), HSSIO (930), VideoOut (932), AudioOut (934), FrontPanelDisplay (936), SODA (938), IEEE1284 Parallel UHFRemote (942), InfrareRemote (944), IEEE1394 (946), AnalogAudio (948), S / PDIG Digital Audio (950), Communications (952), Digital Cable 954, XDSL 956, V34 958, 10BaseT 960, ATM 962, SMPTEVideoOut 968.

Each class is by gi.settop.devices.

Available resources are interacting through the concept of a comprehensive device. The device control API provides a system with the ability to manage devices. Media control APIs include mediation and demultiplexing APIs, decoder APIs, and playback control APIs.

The coordination and demultiplexing API provides a system with the ability to select services and streams.

Decoder API The Decoder API provides a system having the ability to decrypt video streams, audio streams, data streams and elements within those streams.

The playback control API provides a system with the ability to manage the playback of a stream.

§1.4 Presentation Management

Presentation management and presentation APIs play a role in two different types of scenarios within set-tops.

1. Representable objects (graphics, video, audio) created as a result of application activation or application related processing.

2. A representable object created as a result of decryption of data occurring through carrousels, the Internet, and the like.

The Presentation API and Presentation Manager (PM) facilitate both scenarios in the same way. That is, the same object has the same way that it can be created and activated.

The presentation API provides a user with a system having the ability to display and control the display of information, status, content and controls.

Video Presentation API-The Video Presentation API provides a system with the ability to manage the display of video data on the primary display surface.

Front Panel Display Manager API-The Front Panel Display Manager API provides a system with the ability to manage the display of information, status, and control on the front panel display.

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

Font Management API-The Font Management API provides a system with the ability to load, select, and display fonts on the primary display surface.

Audio Presentation API-The Audio Presentation API provides a system with the ability to manage the playback of audio data on the primary audio output.

Many applications and applets in STAMP have a GUI. These are,

1. With mounting & diagnostic screen;

2. a set-top option screen that provides access to key set-top features and applications and realizes a configuration screen (eg, rating preference, language preference, audio / video mode, etc.);

3. Banners and detailed information for watching TV;

4. IPG screen;

5. web browser screen;

6. Email screen;

7. ticker (eg, stock price);

8. applet screen and;

9. Include a downloadable application screen.

These entire GUIs consist of a set of components defined via the presentation API.

§2. Applet

Java applets are supported on set-tops that host either Java-enabled Java browsers or Java-enabled native browsers. Applets are downloaded via the Internet via http or via the DSMCC carousel service.

§3. Application

§3.1 Watching TV

Watching TV -This system provides a simple broadcast television viewing environment. The user can channel up, channel down, return to the previous channel, and select a particular channel.

Watch TV with Parental Lock -The system provides a means for users to restrict access to services, channels or events. The password mechanism can bypass connection restrictions. Connections are based on channels, event ratings, event themes or some other criteria.

TV viewing with conditional access -The system provides a means for restricting access to events in accordance with the access rights of users, such as services and channels or customers of service providers. Access rights belong to service or accounting restrictions.

Watch TV with alternate audio -The system makes more than one audio stream valid for a particular video stream. The user has the opportunity to select an alternate audio stream for playback in synchronization with the video stream.

TV viewing with subtitles -The system validates one or more text or graphic streams that are synchronized and overlap on the video stream.

§3.2 Downloading Application

Downloading application scenarios depict situations in which a broadcast application or data service is spawned or stored in the system.

TV viewing with ongoing unsynchronized data service -The system provides a data service that is not synchronized to current audio and video streams (eg, stock tickers). Applications utilizing data services (eg, stock ticker graphical user interfaces) already reside in the system, and only data (stock quotes) are transmitted in this scenario.

Watching TV with a Continuous Synchronized Data Service -The system provides a data service that is synchronized to the current audio and video stream (eg, sports statistics corresponding to the current player on the screen). Applications using data services already reside in the system, and only data is transmitted in this scenario.

TV viewing with scheduled downloads of applications -The system schedules applications located in services other than the current service and then provides a means of downloading.

Watching TV with Impulse Buying of Applications -The system provides a means for the user to be informed of a valid application in the background and a means for the user to acquire and download the application (stop current audio and video presentations). Without letting it happen).

§3.3 teleshopping

The teleshopping scenario depicts a situation where a user requires information, a product or a service through an application that validates the system.

TV viewing and information request -The system provides a means for the user to request information corresponding to the current broadcast video and audio. For example, while advertising a car, the user requests a brochure.

TV viewing and impulse buying -The system provides a means for users to purchase products corresponding to current broadcast video and audio. For example, a user purchases a plate while advertising a commemorative plate.

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

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

Graphic-centric catalog browsing and purchasing -The system provides a means for users 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 describes a situation in which a user may select a movie (or other audio-video service) from various similar movies or services.

Pay-per-view -The system provides a means for a user to purchase one service from various services. In general, interactivity is limited to the selection and purchasing process.

Interactive Pay-Per-View -The system provides a means for a user to purchase one service from various services. The user may "pause" the service until the next service is available.

§3.5. Gaming

Gaming scenarios allow users to play a game over a network-transfer service. Each game will be a single-user or multi-user game that is located only locally on the system or played over the network.

TV Watching and Local Participation -The system provides a means for a user to watch television programs and "match progression" with a single-user local application. For example, during the "Wheel of Fortune" the user can "turn the wheel" and guess for themselves.

TV Watching and Multi-User Participation -The system provides a means for a user to watch television programs and the "match progression" competing with other users.

Single Player Game -The system provides a means for the user to play a system-based game without additional remotely located participants.

Multi-User Games -The system provides a means for the user to play a system-based game where there are additional remotely located participants.

§3.6. Internet access

Internet access scenarios allow users to access Internet-based content or functions such as html pages, email, chat, streaming audio, and the like.

Web Browsing -The system provides a means for a user to browse a website.

Email -The system provides a means for the user to read, write, and reply to email.

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

TV viewing with Internet content -The system provides a means for a user to simultaneously watch audio and video services while performing Internet-based activities available with or through the audio-video service.

Web Browsing with TV Content -The system provides a means for a user to watch an audio or video service available from an Internet-based item.

§3.7. On-demand information

The Information on Demand scenario allows users to access relevant information content when they want to or customize it to their preferences.

Pay-per-view news service -The system provides a means for a user to obtain an audio, video, or text-based news service. This service may provide headline-level details, in-depth details, non-setters, or some other level of service.

Inquiry of News Items -The system provides a means for a user to query various available sources for one or more "articles" that meet user-defined or user-selected criteria.

Personalized News -The system provides a means for the user to tailor the news service according to the user's preferred subject.

Subscription Service -The system provides a means for a user to subscribe and schedule an audio, video, or text-based news service.

§3.8. Electronic program guide

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

Current Channel Now and Next -The system provides information on what services are currently available on the current channel and what the next service is.

All Channels Now and Next -The system provides information on what services are currently available on all known channels and what is next.

All Channels Now and Future-The system provides information on what services are currently available on all known channels and what services are available at some given time in the future.

Preview Request from Guidance -The system provides a means for the user to request a sample of the service. For example, it allows a user to request a trailer for a video or demo of an application.

Purchasing Events from Guidance -The system provides a means for the user to purchase future events or services from the electronic program announcement.

Program reminder setup -The system provides a means for the user to schedule future event notifications at a future point in time.

Purchasing an Application from the Guidance-The system provides a means for the user to purchase an application for download from the electronic program guidance.

§3.9. Distance lesson

Distance teaching scenarios describe virtual classrooms where students and teachers are not in the same location.

Watch TV with Chat -The system provides audio and video of the virtual classroom. The system provides a means for the user to join with the teacher or other students (located at other sites) via chat.

Watch TV with the test -the system provides audio and video of the virtual classroom. The system provides a means for the user to join with the teacher or other students (located at other sites) via chat.

§3.10. Home banking

The home banking scenario describes the services available to a user comparable to those available at a retail bank.

Information retrieval -The system provides a means for users to access information related to banking functions and their personal savings accounts.

Transaction -The system typically provides a means for a user to perform retail bank electronic transfers.

Service Applications -The system provides a means for users to use retail banking services such as credit cards, loans, and withdrawals.

Counseling -The system provides a means for the user to get advice on personal finance.

§3.11. navigation

Navigation scenarios describe situations in which a user activates services, applications, and content available on the system.

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

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

System Priority -provides a means for the user to identify user-centric priorities related to the operation of the system or its user interface.

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

§4. STAMP component structure

Component groups (Bean Bags) are defined to facilitate a set of domain properties (eg, IPG) application component building. These sets are NOT disjoints. Java Bean Bags are:

1. GI Application System Bean Bag-This set of components consists of all beans that are generic to all other set of application components. This includes information change mechanisms, synchronization mechanisms, timing mechanisms, storage mechanisms, and the like.

2. GI GUI Bean Bag-This set of components contains all GUI beans that are generic to all other applications; This includes lists, buttons, sliders, and so on.

3. GI HotJava Bean Bag-This set of components contains all the components that can be part of the browser.

4. GI IPG Bean Bag-This set of components includes all components that can be part of an IPG application.

5. GI Tuning Bean Bag-This set of components includes all components that can be part of a tuning application.

6. GI E-mail Bean Bag-This set of components includes all components that can be part of an email application.

7. GI Download Bean Bag-This set of components includes all components that can be part of a download application.

8. GI Ticker Bean Bag-Contains all components that may be part of an information ticker application.

9. GI Game Player Bean Bag-This set of components includes all components that may be part of a game player application.

§5. Application Programming Interface (API)

Application Programming Interfaces (APIs) provide systems with hardware and operating system independent abstraction layers. This allows broadcast applications to be delivered to the systems and operating systems of wide area change processors (from set-top boxes with RISC processors and real-time operating systems to personal computers with microprocessors and non-real-time operating systems).

All APIs can be used from native applications as well as Java applications. The following APIs need to be defined outside the scope of these APIs defined by DAVIC and standardized by JavaSoft:

§5.1. Event Management API

The Event Management API provides a system with the ability to send and receive 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 with the ability to receive and send user-initiated events (keyboard, mouse, front panel, remote control, etc.).

Inter-process communication API-inter-process communication (Inter-Process Communication) API provides a system having a function for transmitting the application, and processes, messages and events between the thread (thread).

Scheduling API -The Scheduling API provides a system with the ability to establish the time and date at which events and "interrupts" are initiated.

§5.2. Application Utility API

Application Utility APIs typically provide a system with general purpose functions used by an application.

Arithmetic API -The Math API provides a system with the ability to perform arithmetic routines.

Time API -The Time API provides a system with functions for accessing time and dates and performing normal time routines.

String API -The String API provides a system with functions for loading, unloading, and manipulating strings.

List API -The List API provides a system with the ability to manage lists and other typically active data structures.

File API -The File API provides a system with the ability to perform file-related operations.

Localization API -The Localization API typically provides a system with the functionality to perform localization operations.

Communication API -High-level interface to all communication and communication management components, including dial-up networking, the Internet, routing, transport streams, and more.

Object service API -supports information exchange between objects; This includes information models, types, relationships, behaviors, characteristics, naming, registration, classification, and so on.

Database Service API -Supports a search mechanism and data storage, including a generic file system and registration.

Download Service API -Supports Download Service.

§5.3. Content Management API

The Content Management API provides a system with content life-cycle and content integrity related functions.

Content Integrity API -The Content Integrity API provides a system with the functionality of TBD.

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

Content Version Control API -The Content Version Control API provides a system with the ability to manage versions of stored or loaded content.

Content Storage API -The Content Storage API provides a system with the ability to store and retrieve content in or remotely from the system.

§5.4. System Information API

The System Information API provides a system having MPEG-2 system information and program information stream related functions.

Event Information API -The Event Information API provides a system with the ability to decrypt the event information stream.

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

§5.5. GI Presentation API

See set-top management. Building presentation manager components such as decoders, combiners, indicators, and the like; Access to all presentation subsystems, including graphics, audio, and video, as required, in addition to DAVIC and standard Java APIs; Manipulation of all presentation subsystems as needed, in addition to DAVIC and standard Java APIs; It facilitates initialization, initiation, manipulation, stop and integration of all presentation components.

§5.6. GI Set Top Management API

See set-top management. This API provides access to components, component monitoring and control, initialization, start, stop, and integration of all internal processes / demonstration / applications; It enables set-top management applications by providing information processing as well as processing asynchronous events.

Behavior Support APIs -Facilitate set-top management APIs through the Java / Visa interface as well as the SNMP agent API

§5.7. DAVIC API

The following DAVIC APIs are supported:

1. Resource Notification API (org.davic.resources)-A standard mechanism for applications that records concerns about scarce resources and notifies the change and deletion of those resources around them.

2. MPEG API (org.davic.mpeg)-includes MPEG Component API, MPEG Section Filter API, and MPEG TransportStream API.

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

4. Conditional Connection API (org.davic.net.ca)-CA system independent interface for accessing CA functions.

5. DVB SI API (org.davic.net.dvb.si)-Interface to the DVB SI database, including access to the actual transport stream via any cache.

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

7. Media Player API (org.davic.media)-An extension of the Java Media Framework to facilitate set tops.

8. DSM-CC U-U API (davic.dsmccuu)-Run a subset of the DSM-CC-U-UAPI as defined in ISO / IEC 13818-6.

§5.8. Standard Java API

1. Personal Java-This API is a subset of the JDK 1.1 API added by a handful of new APIs designed to meet the needs of networked embedded applications. Java APIs introduced after JDK 1.1 do not automatically adapt to some PersonalJava APIs. The new API will be reviewed and evaluated for appropriateness before being added to PersonalJava.

The JDK 1.1 package included with PersonalJava is:

java.applet

java.awt

java.awt.datatransfer

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-Internationalization Support

3. The Java Security API is a developer's framework for easily and securely embedding the security features of their applets and applications. Such functions include digital signatures, encryption, and encryption methods with authentication.

4. The Java commerce API brings secure purchasing and financial management from the web. JavaWallet runs a client-side framework for credit cards, debit cards, and the electronic cache business.

5. The Java Media Framework (JMP) enumerates the integration architecture, messaging protocols, and programming interfaces for the media player, capture, and conferencing. JMF is published in three APIs. First of all, a Java media player is published; Next, the Java Media Capture and Java Media Conference APIs are published. 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)-An object-oriented separation API that supports CORBA.

§6. Set-top software architecture

10 illustrates a set top software architecture framework in accordance with the present invention.

Structure 1000 corresponds to structure 200 of FIG. 2, but provides an example for each layer in more detail.

The device driver core module of layer 210 'typically corresponds to the class of FIG.

§7. Relationship to the OpenCable API

The following section summarizes the current OpenCable API classification.

§7.1. Operating System <-> Network API

Network protocols are all used at the ASB level to communicate with other clients, applications and services. Also, even though applications use network protocols, the majority of them are actually OS-executable network stacks invoked via OS <-> application APIs. In particular, protocols dealing with application-level client server issues are covered in the client <-> server part.

§7.1.1. Video and data network / transport protocol

These protocols are used for network packet forwarding, connection establishment, control, and teardown. The industry open standard is TCP for connection-oriented transmission, UPD for release, real time call transmission, and IP for packet forwarding. RSVP is used for network bandwidth and channel reservation. MPEG-2 is best for video transmission.

§7.1.2 session / presentation protocol

These protocols are used to maintain sessions and to provide applications with the usual procedures for requesting and receiving data from content servers. FTP is used for file transfer, HTTP for WWW access and HTML transfer, NNTP for new server access, and SMTP and IMAP for mail.

§7.1.3. Directory service protocol

Directories are mostly read-only classification databases designed for attribute lookups for locating, authenticating, and updating network objects. Rapidly appearing as a standard directory for TCP / IP networks, LDAP is the standard version of X.500's more complex directory access protocol. LDAP is employed through 40 major software vendors and supports connection-independent data views, hierarchical storage, multiple storage configurations, rich access control, multiple database types and examples, and network responses.

§7.1.4 Data-Link, Physical, MAC Layer Protocols

These APIs control the modulation, encoding, and management of data streams through cable installations.

§7.1.5 Network Encryption Protocol

These protocols are used to encrypt and decrypt video, data, and processing systems.

§7.1.6 Multi-user / network broadcast protocol

Requires effective broadcasting of data streams over the network.

§7.2 OS <-> Application API

The operating system provides an application with a critical set of two services that allows the application to run on top of the system. Basic OS services, such as scheduling, virtual memory, and multi-threading, are basic services that are provided to almost any application without much effort from the programmer. The APIs for these services are not very visible. On the other hand, the OS standard library is a predetermined code module that is recommended for use when an application executes a function supported by the OS. For example, a network application is recommended to use a network library of the OS, and almost all applications use an OS. It is recommended to use a GUI library. In essence, the standard library is provided for consistency, to prevent copying, and to accelerate development. Sometimes, applications ignore certain libraries for reasons of beauty or to optimize code.

§7.2.1. Application Services and Libraries

These APIs control the center of the set-top box. Native applications (written specifically for ASBs that require maximum performance and hardware interaction) run based on the OS services and libraries provided through these APIs.

§7.2.2. Computer graphics

These APIs control the drawing and representation of 2D and 3D objects. Application programmers use them to simplify graphics functions. It is also used to launch windowing tool-kits and graphical user interfaces for applications.

§7.2.3. Remote Execution Environment / Virtual Machine

Allows applications stored on the network to be downloaded, run, and deleted. Protect the runtime environment, security model, and object model. Current competitors are platform-independent Java and Windows-based ActiveX.

§7.3. Operating System ＜-＞ Hardware API

Typically, these APIs associated with device drivers allow the operating system to control various pieces of hardware. Usually, it is implemented in software by the device manufacturer plugging them into the operating system through a well-defined device-driver structure proposed by the operating system vendor. For a well-defined category of devices, operating system vendors sometimes provide generic device drivers for a complete class of devices. These generic drivers are generic laser writer drivers for all laser printers, except that if the manufacturer's driver is not available, that is, the Macintosh OS can take advantage of the vendor / model features of their own driver enabled printers. Providing a generic Laser Writer driver) can provide the minimum functionality. Systems that automatically recognize devices and load dedicated drivers are classified as plug-and-play.

§7.3.1. Hardware Separation Layer (HAL) API

The Hardware Abstraction Layer (HAL) separates hardware from the OS and allows the OS to transport it across platforms that support HAL.

§7.3.2. Registration API

Storage format and control for local flash RAM storage.

§7.4. Operating System <-> Operating System API

These APIs are used when one OS runs on top of another, or when two OSs communicate with each other, as in the case of a virtual machine. The latter is rare, and some components and object models are usually handled via network protocols, even though separate objects can communicate across each OS.

§7.4.1. Link virtual machine (VM) to remote execution environment / OS

Control the execution details of virtual machines on existing RTOS. VM portability is significant when an exclusive VM runs, or an open VM runs in an exclusive tie to the OS.

§7.4.2. Isolated object model

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

§7.5. Client <-> Server API

Clients and servers often pass application data through standard networking protocols, but remote client management, authentication, software downloading, and updates are handled through specific client-server APIs. Usually these APIs tend to be closed or broken down due to a number of potential combinations and issues.

§7.5.1. Network management

Remote network management of all network elements.

§7.5.2. Software Management and Renewal

API to control software downloads and module loaders.

§7.5.3. Network / Remote File System

Control how files are saved and restored.

§7.5.4. Digital certification

Authentication control for users, sellers, and products.

§7.5.5. Calendar Server Protocol

Determine storage and interaction formats for user calendaring and scheduling functions.

§7.5.6. Synchronization protocol

Clock synchronization and timing requirements.

§7.5.7. Process Data Collection API

Define methods and formats for processing data collection, storage, and transmission.

§7.5.8. Billing System API

Define methods and formats for billing data collection, storage, and transmission.

§7.6. Application <-> File API

Applications use specific formats to store and restore the data they use. In the case of some exceptional high-visibility formats (ASCII, HTML), these formats are often closed and actually proprietary. In addition to static-data, some applications also release APIs that support the storage, retrieval, and execution of plug-in code modules and allow third party vendors to configure such plug-ins and the like.

§7.6.1. Text document storage format

Storage format for plain text documents.

§7.6.2. Hyperlinked document storage format

Storage format for rich hyperlinked text.

§7.6.3. Image storage format

Compressed format for images.

§7.6.4. 3D graphic document storage format

Storage format for 3D data.

§7.6.5. Video clip storage format

Encoding of streaming and non-streaming video clips.

§7.6.6. Audio document storage format

Encoding sound and music.

§7.6.7. Animation Document Storage Format

Animation encoding.

§7.6.8. Web / Video Unified Format

Definition of methods and libraries for integrating web-based content provided with traditional TV offerings. For example, hyperlinked advertisements, buttonbars and ticker overlays, virtual web channels, and the like.

§7.6.9. Save personal information

Storage of user identification information, preferences, and access control information.

§7.7. Client <-> Content API

This set of APIs controls the delivery and serving of content from various servers to clients. In practice, it is a subset of the client-server API, but it is explicitly mentioned because some vendors try to achieve lock-in by requiring a proprietary server to distribute content.

§7.7.1. Web data serving

Format for serving web content. In addition to standard HTTP, some web servers use proprietary serving methods (ie, active server pages).

§7.7.2. Video data serving

Format for serving video content.

§7.7.3. Integrated data serving

Serving and Arrangement of Integrated Web / Data Content.

§7.8. Content <-> Connection API

This set of APIs controls the delivery and serving of content from various servers to clients. In practice, it is a subset of the client-server API, but it is explicitly mentioned because some vendors try to achieve lock-in by requiring a proprietary server to distribute content.

§7.8.1. Video connection control

Access control and encryption of video streams.

§7.8.2. Data access control

Authentication for data content transfer.

§7.9. Browser <-> resident engine API

In fact, there is no separate set of APIs per second, and browser <-> resident engine interactions are actually sub-categories of OS <-> applications, and due to the fact and strategic importance of most browser vendors incorporating these APIs into their products, Appears clearly. In a well-designed operating system, resident HTML, VRML, Java, and caching engines are services that the OS provides to all target applications. However, most browser vendors bundle these important engines in their browsers to hide and control these important APIs even though they are clearly exposed.

§7.9.1. Clear HTML Engine Control

Once it is detached from the browser, it controls access to the HTML presentation engine. In addition, if a proprietary format is used, the OS provider must attach documentation that the API is used and permanently provides free rights to these APIs.

§7.9.2. Clear cache control

Once it is detached from the browser, it controls the caching engine to access and use it.

Accordingly, it can be seen that the present invention provides set-top software that recognizes consideration of set-top applications and middleware software functions independent of the operating system and hardware.

The invention provides for multiple users, secure controlled access to resources, application downloads, registrations, startups, shutdowns, monitoring, resource downloads, registrations, startups, shutdowns, monitoring, audio, video management, data presentations, and the like. It can support various types of functions.

Although the present invention has been described in connection with various specific embodiments, various modifications can be made without departing from the object and background of the present invention.

For example, while various syntax elements have been described in the present invention, this is merely an example, and any syntax may be used.

Moreover, the present invention can be used with any type of network, including cable or satellite television broadband communications networks, local area networks (LANs), wide area networks (WANs), the Internets, intranets, and the Internet, or combinations thereof. Suitable for

Claims (22)

In a television set top terminal with software, A computer readable medium having computer program code means, Means for executing said computer program code means for implementing a layered software structure, The application layer allows the user to interact with the terminal, The middleware layer supports the application layer by providing each application program interface (API), The operating system layer supports the middleware layer, The hardware layer supports the operating system layer, And wherein said layered software architecture allows configuration of the functions of said application layer and said middleware layer independently of said operating system layer and said hardware layer. 2. The terminal of claim 1, wherein the layered software structure includes a set top management layer that supports the application layer by configuring a management service of the terminal. The terminal of claim 2, wherein the management service includes at least one application program and user, resource, and presentation management. The terminal of claim 2, wherein the set top management layer executes a state information module to indicate a state of a resource of the terminal. 5. The terminal of claim 4, wherein the status information module is based on the ITU-T X.731 standard. The terminal of claim 1, further comprising an application program interface (API) for providing a configurable function. 7. The terminal of claim 6, wherein the API enables the terminal to support multiple users. 7. The terminal of claim 6, wherein the API enables the terminal to secure controlled access of resources. The terminal of claim 6, wherein the API enables the terminal to download, register, start, stop, and monitor an application program of an application layer. 7. The terminal of claim 6, wherein the API enables the terminal to manage audio, video and / or other data presentation. The method of claim 1, further comprising: Presentation Manager, Application manager, User manager, Resource manager, Set-top agents, And at least one of a program view assistant. A method for implementing a layered software structure of 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 a layered software structure, The application layer allows the user to interact with the terminal, The middleware layer supports the application layer by providing each application program interface (API), The operating system layer supports the middleware layer, The hardware layer supports the operating system layer, And wherein said layered software structure allows configuration of functions of said application layer and said middleware layer independently of said operating system layer and said hardware layer. 13. The method of claim 12, wherein the layered software structure includes a set top management layer that supports the application layer by configuring a management service of the method. The method of claim 13, wherein the management service includes at least one application and user, resource, and presentation management. 14. The method of claim 13, wherein the set top management layer executes a status information module to indicate the status of resources of the method. 16. The method of claim 15, wherein said status information module is based on the ITU-T X.731 standard. 13. The method of claim 12, wherein the layered software structure provides an application program interface (API) for providing configurable functionality. 18. The method of claim 17, wherein the API enables support of multiple users. 18. The method of claim 17, wherein the API enables secure controlled access of resources. 18. The method of claim 17, wherein the API enables downloading, registration, start, stop, and monitor application of an application of an application layer. 18. The method of claim 17, wherein the API enables management of audio, video and / or other data presentations. 13. The system of claim 12, wherein the layered software structure comprises at least one set top manager; Presentation Manager, Application manager, User manager, Resource manager, Set-top agents, Providing a program view assistant.