SYSTEM AND METHOD FOR INCORPORATING A DECLARATIVE USER INTERFACE FRAMEWORK INTO A GLOBALLY EXECUTABLE MHP

(GEM) PROFILE

BACKGROUND OF THE INVENTION

Field of the Invention

[1001] This invention relates to interactive television systems. More particularly, the invention relates to systems and methods for a user interface for an interactive Internet Protocol television system.

Description of the Related Art

[1002] The user interface is an interactive television service provider's primary point of contact with the viewer-subscriber. A user interface is typically displayed on a television screen or computer monitor, and a viewer can manipulate an input device, such as a mouse or an infrared remote control to interact with the controls.

[1003] Developers and providers of Internet Protocol television (IPTV) systems are often concerned with providing customized, user-friendly, attractive, and interesting user interfaces. User interface customization is sometimes referred to as "branding," and is the process of customizing the look and feel of applications while maintaining the same functionality. Branding is an important requirement for some interactive television applications. The ability to easily support customization is a strong requirement among some service providers.

[1004] A user interface "theme" refers to the smaller scale customization within a given brand, such as changing the look of buttons, the background images, colors, and fonts, etc. Typically only one brand will be deployed at a time, while multiple themes may be concurrently deployed. Themes are generally globally defined and stored and provide a way to quickly change the look of the user interface at a single location application and quickly have the change propagate to the user interface of all applications.

[1005] Interactive television systems are generally developed based on an interlocking set of middleware standards. The European Digital Video Broadcasting Project (DVB) developed the Multimedia Home Platform (MHP), which provides a basic model for how applications behave and how they, and any associated files, can be made available for use by receivers. MHP incorporates an application model from the JavaTV digital television specification developed by Sun Microsystems (and, in fact, includes the JavaTV application programming interfaces (APIs)).

[1006] The Globally Executable MHP (GEM) standard was developed from MHP to provide a standard that could have worldwide applicability and, in particular, in North America and Japan. The OpenCable Application Platform (OCAP) was developed to provide a common basis for digital cable interactivity standards for the United States industry. OCAP is based in large part on MHP and GEM.

[1007] GEM applications rely on the HAVi user interface library from the Home Audio Video Interface organization. While HAVi supports user interface look customization at the programming level, it is not readily accessible for user interface designers and content developers. In particular, HAVi look customization requires Java programming and, as such, is relatively complex and requires a relatively long period to develop.

SUMMARY OF THE INVENTION

[1008] Embodiments of the present invention relate to providing a declarative user interface framework (DUIF) in an Internet Protocol television system. In some embodiments, the DUIF framework is provided in conjunction with a HAVi user interface framework. Embodiments of the present invention provide for interoperability between the two frameworks. In addition, embodiments of the present invention provide for supporting multiple customizations in a single code base and for updating theme support dynamically.

[1009] A method in accordance with embodiments of the present invention includes providing a first graphical user interface framework; providing a second graphical user interface framework; and selectively choosing to provide a graphical user interface using said first framework or said second framework responsive to an application download. In some embodiments, the selectively choosing includes specifying between the first or second graphical user interface framework using signaling accompanying the application download. In some embodiments of the present invention, the first graphical user interface framework is a declarative user interface framework (DUIF) and the second graphical user interface framework is a HAVi framework.

[1010] A system according to embodiments of the present invention includes device middleware including a declarative user interface framework; and a portal application configured to initialize said declarative graphical user interface framework, said portal application further including a plurality of user interface resources and markup files made available to the declarative user interface framework. In some embodiments, the portal application is configured to selectively choose to provide a graphical user interface using the DUIF framework or a HAVi framework.

[1011] A program product stored on one or more computer readable devices in accordance with embodiments of the present invention includes code executable to selectively choose to provide a graphical user interface using said first framework or said second framework responsive to an application download. In some embodiments, the program product further includes code executable to specify between said first or said second graphical user interface framework responsive to signaling accompanying said application download.

BRIEF DESCRIPTION OF THE DRAWINGS

[1012] The present invention may be better understood, and its numerous objects, features, and advantages made apparent to those skilled in the art by referencing the accompanying drawings. The use of the same reference symbols in different drawings indicates similar or identical items.

[1013] FIG. 1 illustrates an exemplary system according to an embodiment of the present invention..

[1014] FIG. 2 illustrates an exemplary declarative user interface framework for use with a system in accordance with embodiments of the present invention.

[1015] FIG. 3A and FIG. 3B are flowcharts illustrating operation of embodiments of the present invention.

[1016] FIG. 4 is a diagram illustrating an embodiment of the present invention.

[1017] FIG. 5 is a diagram illustrating an embodiment of the present invention.

[1018] FIG. 6 is a flowchart illustrating operation of an embodiment of the present invention.

[1019] FIG. 7 is a flowchart illustrating operation of an embodiment of the present invention.

[1020] FIG. 8A-FIG. 8B illustrate an exemplary media distribution system that may be used in with a layered user interface system according to embodiments of the present invention.

[1021] FIG. 9A- FIG. 9B is a diagrammatic representation of a device and system that may be used to implement methods according to embodiments of the present invention..

DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION

[1022] Turning now to the drawings and, with particular attention to FIG. 1 , a diagram schematically illustrating an embodiment of the present invention is shown and generally identified by the reference numeral 100. In particular, the system 100 illustrates an exemplary system that may be used, e.g., in conjunction with a media distribution system, as will be explained in greater

detail below. In particular, the system 100 provides an improved system for delivering user interfaces to an interactive television system, such as an Internet Protocol (IPTV) system. The system 100 may be particularly suited to execute in conjunction with the middleware of such a system and, more particularly, to the middleware of a system implementing a GEM middleware such as the OCAP middleware. An exemplary IPTV system will be discussed more particularly with reference to FIGS. 7A-7B and FIGS. 8A-8B.

[1023] As illustrated, the system 100 includes a portal application 102, HAVi user interface framework 104, declarative user interface framework 106, and an application manager 108. In some embodiments, the portal application 102 implements a menu for service and/or application selection. It is generally similar to the MHP navigator application. It is noted, however, that while in some embodiments, the portal application is the coordinator, in other embodiments, another unbound application may be used. In other embodiments, an extension to the application manager may be suitably configured for coordination.

[1024] The HAVi user interface framework 104 may implement one or more HAVi graphical user interface application programming interfaces (APIs). The declarative user interface framework 106 may implement a DUIF as shown in FIG. 2. The DUIF 106 includes a markup language 202 and a library 204. In some embodiments, the library 204 implements individual user interface skins or themes. A DUIF 106 according to some embodiments may have scripting built into the markup language. Still others may also have custom extension capabilities in scripting as well as in user interface markup. In some embodiments, in order to make the DUIF accessible to all applications, it is placed in the system middleware.

[1025] Returning to FIG. 1 , one or more bound applications 112 and unbound applications 110 may operate in the system. Bound, or service- bound applications 112 are downloaded applications associated with a particular service or set of services. For example, a bound service might be a stock ticker application running in association with a particular television

channel. Typically, bound applications are downloaded every time the user wants to use the services and are deleted or halted when the service is no longer operating. Signaling associated with bound applications includes an Application Information Table (AlT) that can identify the application's name, version, priority, status, type (Java or Html), location of the stream containing the application's classes and data files, the base directory, the name of the main class, and the location of an icon for the application.

[1026] An application manager 108 typically handles bound applications. In particular, e.g., receiving the AIT information and launching the application. The application manager 108 further communicates to launch the HAVi Gui, as will be explained in greater detail below.

[1027] Unbound applications 110 are downloaded applications that are not associated with a service. Thus, they can be active regardless of the service(s) currently running. Unbound applications are loaded under the control of a JavaTV service selection API (not shown) created and maintained by the portal application 102. Application signaling for an unbound application is handled via an Extended Application Information Table (XAIT) which, for present purposes, is generally similar to the AIT. It is noted that the portal application 102 is itself an unbound application.

[1028] As will be discussed in greater detail below, aspects of the present invention relate to providing for interoperability of the HAVi and DUIF frameworks. This is particularly important, since multiple applications may be running at the same time, and some may or may not use the DUIF framework 106. In particular, as will be explained in greater detail below, in some embodiments, the portal application 102 is used to coordinate between applications to ensure user interface interoperability.

[1029] In some embodiments of the present invention, interaction of the HAVi and DUIF interfaces depends on whether the application is a bound application or an unbound one. As will be explained in greater detail below, in the case of unbound applications, for example, the portal application 102 can handle application launching, etc. In this case, the portal application 102 is

configured to accept signaling (e.g., a suitably modified XAIT) indicting whether the particular application employs the HAVi or DUIF framework for its GUI needs.

[1030] In the case of bound applications, as will be explained in greater detail below, the application manager 108 handles application launching and may be configured to notify the portal application 102 of bound application launching. In some embodiments, the HAVI framework is the default GUI and this information is sufficient to let the portal application 102 know that an application is to use the HAVI framework. In other embodiments, the AIT can contain information indicating whether the application is to use the HAVi or DUIF GUI frameworks.

[1031] In either the case of the bound or unbound applications, the portal application 102 can "hide" the HAVi or DUIF application containers as needed, as will be explained in greater detail below.

[1032] Turning now to FIG. 3A, a flowchart 300 illustrating operation of embodiment of the present invention is shown. The particular arrangement of elements in the flowchart 300 is not meant to imply a fixed order to the elements; embodiments can be practiced in any order that is practicable. More particularly, the flowchart 300 of FIG. 3A illustrates exemplary handling of unbound applications according to an embodiment of the present invention.

[1033] In a process step 302, a client device (such as a set top box) including, for example, a portal application 102 receives signaling from, e.g., a service or content provider. In a process step 304, the portal application 102 launches or causes a launch of the service selection API (not shown). In a step 306, the portal application service selection API determines if the application is to use a HAVi or a DUIF user interface. If the HAVi interface is to be used, the portal application 102 "hides" the DUIF, in a process step 308. In a process step 310, the portal application 102 can launch the application with HAVi.

[1034] Back in process step 306, if HAVi is not to be used, then in a process step 312, the portal application 102 "shows" the DUIF framework 106 and, in a process step 314, launches the application with the DUIF framework 106. In some embodiments, a service specific parameter may be included in the application signaling information and is passed to the service to help the launcher application decide what content to display inside the DUIF.

[1035] Turning now to FIG. 3B, a flowchart 350 illustrating operation of embodiment of the present invention is shown. The particular arrangement of elements in the flowchart 350 is not meant to imply a fixed order to the elements; embodiments can be practiced in any order that is practicable. More particularly, the flowchart 350 of FIG. 3B illustrates exemplary handling of bound applications according to an embodiment of the present invention.

[1036] Initially, in a process step 352, the client receives signaling information from the server, in a manner similar to that discussed above. In a process step 354, the application manager 108 informs the portal application 102 that a bound application is being received. In a step 356, the bound application launches. In a step 358, the portal application 102 "hides" the DUIF framework 106 so that the HAVi can be used. It is noted that, in some embodiments, the signaling information could also include HAVI or DUIF selection information, as in the unbound case. Embodiments of the present invention thus require only minimal changes to the application manager 108, requiring only that it be configured to inform the portal application 102 of the launch of the bound application.

[1037] Advantageously, embodiments of the present invention allow for a flexibility in customization management, i.e., management of interface "brands." In particular, embodiments of the present invention allow for a common base user interface code and separate resource groupings for particular customizations.

[1038] An example if this is illustrated in FIG. 4. Shown is a user interface resource lookup unit 402 and a plurality of user interface customizations/brands 404a, 404b. Each brand 404a, 404b includes a

plurality of user interface resources 406a, 406b, 406c and 408a, 408b, respectively. User interface resources can include, for example, DUlF markup files, image files used by the markup, localized text properties files, and any additional resource files such as, for example, short sound or video clips.

[1039] As illustrated, in some embodiments of the present invention, resources for each customization are grouped into its own directory. The user interface resource lookup 402 can be told which customization is operational and thus provide a variety of user interface options.

[1040] For example, the customization 404a could be a given provider, say, Verizon. Customization 404b could be another provider, such as SBC. Exemplary resources could be specified in a path not including the customization part, such as, e.g., /dtv/dtv.html and /common/images/logo.png. The actual resource is located in the respective customization folder. If, for example, the customization was Verizon, then the resource lookup getResource(/dtv/dtv.html) will fetch the resource from /verizon/dtv/dtv.html. If the customization is switched to SBC, then accessing the same dtv screen (say from a hotkey or from a button in a GUI menu) will load from /sbc/dtv/dtv.html. Thus, the current customization is a variable that may change over time and is used to form the full resource path to find the resource.

[1041] One aspect of embodiments of the present invention relates to placing the DUIF framework in middleware (i.e., bundled in the GEM middleware stack), but having resources placed in the portal application 102. In this way, user interface themes can be updated without requiring a reboot of the associated client set top box (as would be required in a middleware update).

[1042] This is illustrated schematically with reference to the system 500 of FIG. 5. Shown in FIG. 5 is middleware 501 , which in certain embodiments is a GEM middleware stack. Also shown is DUIF framework 502 (generally similar to DUIF framework 106), which is part of the middleware stack, and a

portal application 504 (generally similar to portal application 102). The portal application 504 is an application program separate from the middleware stack and may include user interface resources 506a-506c. As noted above, user interface resources can include, for example, DUIF markup files, image files used by the markup, localized text properties files, and any additional resource files such as, for example, short sound or video clips.

[1043] Also shown are one or more application programs 508, 510. The application programs 508, 510 may be application programs related to services, such as those discussed above. Thus, the portal application 504 interfaces to provide the resources 506a-506c to the applications. In this way, all theme-able components are able to access theme resources and all applications are able to access the theme-able components via the common interface exposed through DUIF in the middleware. Dynamic updateability of themes is thus accomplished via the portal application. In this way, themes and related markup files themselves can be downloaded to the device as updates to the portal application without affecting the middleware stack and without requiring a reboot of the device.

[1044] Turning now to FIG. 6A, a flowchart 600 illustrating operation of embodiment of the present invention is shown. The particular arrangement of elements in the flowchart 600 is not meant to imply a fixed order to the elements; embodiments can be practiced in any order that is practicable.

[1045] Initially, in a step 602, a globally executable multimedia home platform (MHP) (GEM) stack is installed in, for example, a set top box (STB). In a step 604, the portal application may be loaded. In a step 606, the portal application can initialize the DUIF framework. Finally, in a step 608, the portal application can make resources available to the DUIF framework and other applications.

[1046] Turning now to FIG. 7, a flowchart 700 illustrating operation of embodiment of the present invention is shown. The particular arrangement of elements in the flowchart 700 is not meant to imply a fixed order to the elements; embodiments can be practiced in any order that is practicable.

[1047] In a process step 702, a new theme/portal application update may be downloaded to the corresponding device. In a process step 704, the portal application receives the update. In a process step 706, the portal application installs the update and makes it available to the DUIF framework and other applications.

[1048] As discussed above, embodiments of the present invention are suited to an internet protocol media distribution system. FIG. 8A depicts a representative environment according to the invention. Central to Fig. 8A is a network with ATM network backbone 800. This ATM network is capable of fiber data rates of OC3, OC12, OC48, OC192 or as is available in the art. A plurality of content providers place information onto ATM network 800. Typical sources of content served include broadcast information 802, Internet information 804, telenetwork 806, broadcast content 808, and video 810.

[1049] In a representative central plant, a plurality of ATM switches 812 interface with network 800 to receive and distribute data from the various content sources. Information flows from ATM switches 812 via a plurality of paths 813 to a plurality of DSL modems 814. DSL modems 814 connect via DSL twisted pair lines 818 to a plurality of modems 816 in various subscribers residences or establishments. From a representative modem 816, there can be attached a telephone 820 and/or a television set which may include and associated set top box 822, and/or a computer 824. The system of embodiments of the present invention may thus be operable on or in association with devices such as telephone 820, television with set top box 822, and/or computer 824.

[1050] FIG. 8B depicts an overview of a digital programming content distribution system according to a particular embodiment of the present invention. One or more central channel server(s) 880 collect(s) information about available programming services distributed from a multiplicity of content providers 860. In a preferable embodiment, this information is multicast by the content providers using the session announcement protocol. Channel server 880 maintains a channel list database 870 which tracks available

content channel offerings and a subscriber database 880, which contains subscriber identifications and permitted channels for each subscriber. Subscribers 890 interact with central channel server 880 to obtain programming content information, and with content providers 160 to obtain programs. In related embodiments, the channel server 880 and content providers 860 may be co-located on the same machine, or may reside on separate machines.

[1051] In related embodiments, subscriber database 880 and channel list database 870 may be co-located on the same machine, or may reside on separate machines. Thus, the figure is exemplary only.

[1052] In a representative embodiment, the invention may be practiced using a set top box or control system with the basic subsystems and functions depicted in FIG. 9A. In the representative system of FIG. 9A, a settop or control unit 10 includes bus 12, which is shown schematically as a single bus, but can also be a number of buses such as a local bus and one or more expansion buses (e.g., ADB, SCSI, ISA, EISA, MCA, NuBus, or PCI), which interconnect subsystems such as a central processor 14, which may be an 80x89, 98xxx, RISC, Pentium family, or other suitable microprocessor family, system memory 19, which may be RAM, ROM, or a combination thereof, input/output (I/O) controller 18, an external device such as a serial port 28, such as a USB port, and parallel port 32, detachable keyboard 30, mouse 29, fixed disk drive 32, which may be a hard disk drive or an optical drive or a CD- ROM or DVD-ROM drive or other suitable medium; and a floppy disk drive 33 operative to receive a floppy disk.

[1053] Network connections are usually established through a device such as a network adapter 44 attached to one of the buses or a modem on a serial port. Network adapters may include 10 Base T, 100 Base T, optical, ATM, DSL, or other network formats.

[1054] MPEG decoder 39 and Audio subsystem 42 coupled via bus 12 provide multimedia capability. Many other devices can be connected, such as fax 38 connected via serial port 28, touch screen 40 connected directly, infrared peripheral support 34 or printer 20, connected through parallel port 22. Other devices or subsystems (not shown) may be connected in a similar manner. Also, it is not necessary for all of the devices shown in FIG. 8A to be present to practice the invention. The devices and subsystems may be interconnected in different ways from that shown in FIG. 8A without impairing the operation of the system. Source code to implement processing functions in accordance with the present invention may be operably disposed in system memory 16 or stored on storage media such as fixed disk 32 or floppy disk 33.

[1055] Video interface 33 may be any standard video format, such as S- video. Various forms of user input devices may be used with the set top box. For example, a touch screen allows a user to point to objects on the screen to select the object and to move the selected object by pointing to a second position on the screen. Alternatively, an infrared or other coupled handheld control unit may be interfaced with the unit allowing the user to interact with the unit, make changes, and indicate preferences. Various buttons and controls may be displayed on the screen for activation by using the mouse, touch screen, or a remote control via infrared IF 34.

[1056] Operatively disposed in memory 19, or resident on fixed disk 32, operating system software may be PSOS ₁ DOS, UNIX, WINDOWS95, WINDOWS CE, WINDOWS XP, or other operating systems known in the art. Executing concurrently and cooperatively with operating system software 910 (FIG. 9B), IP Multicast capable TCP/IP software 912 manages the flow of information into and out of the set top unit over the network interface 44. A JAVA enabled Internet browser 914, such as Netscape Navigator Microsoft Explorer or their equivalent in the art provide a web-browser user interface to networked resources through TCP/IP software 912. Client control code 919 implements functions specific to the set top box operation, such as the

processes depicted herein, including, e.g., the portal application, etc. Output to the users set is provided by user interface 918 in conjunction with Video Interface Code 920. Other clients 922 such as Email, facsimile, video conferencing applications or voice mail may also be supported. In a related embodiment, the functions of the set top unit are integrated into a television, forming an Internet capable, interactive "Smart Television." In a related embodiment, the functions of the set top unit are integrated into a personal computer, forming an Internet-capable, interactive "Workstation Television."

[1057] As used herein, whether in the above description or the following claims, the terms "comprising," "including," "carrying," "having," "containing," "involving," and the like are to be understood to be open-ended, that is, to mean including but not limited to. Only the transitional phrases "consisting of ¹¹ and "consisting essentially of," respectively, shall be considered exclusionary transitional phrases, as set forth, with respect to claims, in the United States Patent Office Manual of Patent Examining Procedures (Eighth Edition, August 2001 as revised October 2005), Section 2111.03.

[1058] Any use of ordinal terms such as "first," "second," "third," etc., in the claims to modify a claim element does not by itself connote any priority, precedence, or order of one claim element over another, or the temporal order in which acts of a method are performed. Rather, unless specifically stated otherwise, such ordinal terms are used merely as labels to distinguish one claim element having a certain name from another element having a same name (but for use of the ordinal term).

[1059] The above described preferred embodiments are intended to illustrate the principles of the invention, but not to limit the scope of the invention. Various other embodiments and modifications to these preferred embodiments may be made by those skilled in the art without departing from the scope of the present invention.