Abstract: A system may receive application data in a client-incompatible format and convert at least a portion of the application data into an alternate client-compatible format. In one example, the incompatible format may comprise Enhanced Binary Interchange Format (EBIF) while a client-compatible format may include a web format such as JavaScript, XML or HTML. Interactions (e.g., commands and user input) associated with the application may be received and converted. The interactions may then be processed using the application.

Abstract: Systems and methods for providing one or more secure services are disclosed. One method can comprise authenticating and/or authorizing a user device to receive a security token. A request for information can be processed using the security token to facilitate the secure provision of services to the user device.

Abstract: Systems and methods for providing one or more secure services are disclosed. One method can comprise authenticating and/or authorizing a user device to receive a security token. A request for information can be processed using the security token to facilitate the secure provision of services to the user device.

Abstract: A system may receive application data in a client-incompatible format and convert at least a portion of the application data into an alternate client-compatible format. In one example, the incompatible format may comprise Enhanced Binary Interchange Format (EBIF) while a client-compatible format may include a web format such as JavaScript, XML or HTML. Interactions (e.g., commands and user input) associated with the application may be received and converted. The interactions may then be processed using the application.

Abstract: Systems and methods for providing one or more secure services are disclosed. One method can comprise authenticating and/or authorizing a user device to receive a security token. A request for information can be processed using the security token to facilitate the secure provision of services to the user device.

Abstract: A system may receive application data in a client-incompatible format and convert at least a portion of the application data into an alternate client-compatible format. In one example, the incompatible format may comprise Enhanced Binary Interchange Format (EBIF) while a client-compatible format may include a web format such as JavaScript, XML or HTML. Interactions (e.g., commands and user input) associated with the application may be received and converted. The interactions may then be processed using the application.

Abstract: A system may receive application data in a client-incompatible format and convert at least a portion of the application data into an alternate client-compatible format. In one example, the incompatible format may comprise Enhanced Binary Interchange Format (EBIF) while a client-compatible format may include a web format such as JavaScript, XML or HTML. Interactions (e.g., commands and user input) associated with the application may be received and converted. The interactions may then be processed using the application.

Abstract: A user interface allows for blending of television program choices from which a viewer may select, the blending representing options for linear and non-linear programming presented together within a single hierarchy of a designated category. The blending may further include managed content relevant to the designated category, where desired. Such designated categories may include television programming categories and/or content categories. The options for linear and non-linear programming may be presented together within a single screen of the user interface.

Abstract: A system may receive application data in a client-incompatible format and convert at least a portion of the application data into an alternate client-compatible format. In one example, the incompatible format may comprise Enhanced Binary Interchange Format (EBIF) while a client-compatible format may include a web format such as JavaScript, XML or HTML. Interactions (e.g., commands and user input) associated with the application may be received and converted. The interactions may then be processed using the application.

Abstract: iTV content is created and deployed using a server component adapted to allow content developers to create applications according to an authoring specification that describes a framework for same; a transport component configured to optimize and deliver the applications to one or more clients; and a client component adapted to render the applications through a television so as to permit user interaction therewith. The authoring specification provides for the presentation of content through one or more templates defined therein, allowing application definition and behavior to remain common across multiple client device types, middleware platforms, and/or iTV operating environments.

Abstract: A user interface allows for blending of television program choices from which a viewer may select, the blending representing options for linear and non-linear programming presented together within a single hierarchy of a designated category. The blending may further include managed content relevant to the designated category, where desired. Such designated categories may include television programming categories and/or content categories. The options for linear and non-linear programming may be presented together within a single screen of the user interface.

Abstract: A user interface allows for blending of television program choices from which a viewer may select, the blending representing options for linear and non-linear programming presented together within a single hierarchy of a designated category. The blending may further include managed content relevant to the designated category, where desired. Such designated categories may include television programming categories and/or content categories. The options for linear and non-linear programming may be presented together within a single screen of the user interface.

Abstract: A system may receive application data in a client-incompatible format and convert at least a portion of the application data into an alternate client-compatible format. In one example, the incompatible format may comprise Enhanced Binary Interchange Format (EBIF) while a client-compatible format may include a web format such as JavaScript, XML or HTML. Interactions (e.g., commands and user input) associated with the application may be received and converted. The interactions may then be processed using the application.

Abstract: A user interface allows for blending of television program choices from which a viewer may select, the blending representing options for linear and non-linear programming presented together within a single hierarchy of a designated category. The blending may further include managed content relevant to the designated category, where desired. Such designated categories may include television programming categories and/or content categories. The options for linear and non-linear programming may be presented together within a single screen of the user interface.

Abstract: A user interface by which network operators, programmers, broadcasters and advertisers can deploy and make accessible libraries of available content and allow viewers of iTV services to customize the presentation and content of the information being presented thereto includes one or more screens each having one or more navigable and selectable elements through which the viewers are permitted to customize presentation and content of iTV application environments other than those associated with the user interface.

Abstract: A user interface by which network operators, programmers, broadcasters and advertisers can deploy and make accessible libraries of available content and allow viewers of iTV services to customize the presentation and content of the information being presented thereto includes one or more screens each having one or more navigable and selectable elements through which the viewers are permitted to customize presentation and content of iTV application environments other than those associated with the user interface.

Abstract: A system may receive application data in a client-incompatible format and convert at least a portion of the application data into an alternate client-compatible format. In one example, the incompatible format may comprise Enhanced Binary Interchange Format (EBIF) while a client-compatible format may include a web format such as JavaScript, XML or HTML. Interactions (e.g., commands and user input) associated with the application may be received and converted. The interactions may then be processed using the application.

Abstract: One or more computing devices may be configured to identify information corresponding to a program change request associated with a multi-program data transmission. The information may comprise at least a link to a desired program within the multi-program data transmission. The one or more computing devices may communicate the link to the desired program to a client device over a specified time period. After the time period, the one or more computing devices may communicate the desired program to the client device using a single program data transmission. The single program data transmission may be derived from the multi-program data transmission.

Abstract: A method and system are disclosed for acquiring and transforming existing content (e.g., Hyper Text Markup Language HTML content) for display and execution on multiple platforms and architectures. In one embodiment, capture templates are created to harvest content from disparate content sources on multiple platforms. Data is extracted from the content from the disparate content sources using the created capture templates that drives extracting process. A standardized data stream is generated from the extracted data. The standardized data stream is provided for display on one or more different type of platforms.

Abstract: A user interface allows for blending of television program choices from which a viewer may select, the blending representing options for linear and non-linear programming presented together within a single hierarchy of a designated category. The blending may further include managed content relevant to the designated category, where desired. Such designated categories may include television programming categories and/or content categories. The options for linear and non-linear programming may be presented together within a single screen of the user interface.