Application support for network devices

US10983765B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-10983765-B2
Application numberUS-201816007739-A
CountryUS
Kind codeB2
Filing dateJun 13, 2018
Priority dateMar 23, 2012
Publication dateApr 20, 2021
Grant dateApr 20, 2021

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

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.

First claim

Opening claim text (preview).

The invention claimed is: 1. A method comprising: receiving, by a first device compatible with a first format, data in the first format, the data relating to an interactive application; based on the data, generating an interface in a second format, the interface corresponding to an output of the interactive application; sending the interface in the second format to a second device that is compatible with the second format and that is incompatible with the first format; receiving, by the first device and from the second device, user input in the second format; converting, by the first device, the user input from the second format to the first format; and executing a function of the interactive application using the converted user input in the first format. 2. The method of claim 1 , wherein the interactive application corresponds to a multi-user interactive application configured to receive input from multiple devices. 3. The method of claim 1 , comprising: generating an updated interface corresponding to an output of the interactive application, wherein the updated interface comprises page changes based on the user input. 4. The method of claim 1 , wherein the first format comprises Enhanced Binary Interchange Format (EBIF), and wherein the second format comprises Extensible Markup Language (XML) or hypertext markup language (HTML). 5. The method of claim 1 , comprising: receiving notification of a key event from the second device; determining whether the key event corresponds to the function of the interactive application; and after determining that the key event corresponds to the function of the interactive application, executing a second function of the interactive application using the key event. 6. The method of claim 1 , comprising: receiving, from the second device and in the second format, a command corresponding to a user interaction or an event, wherein the second format comprises Extending Markup Language (XML) or hypertext markup language (HTML); converting the command into the first format wherein the first format comprises Enhanced Binary Interchange Format (EBIF); and inputting the command into the interactive application. 7. The method of claim 1 , comprising: receiving code in the second format from a third device; and generating, based on the received code in the second format, the interface corresponding to the output of the interactive application. 8. The method of claim 1 , comprising: sending the interface to a third device different from the first device and the second device; receiving a modified interface from the third device, wherein a focus of the modified interface has been set on an element of the interface; and sending the modified interface in the second format to the second device. 9. The method of claim 8 , comprising: sending, to the third device, instructions to control the focus of the modified interface, wherein the instructions comprise a command to bring the element of the interface to a foreground of the interface. 10. The method of claim 8 , comprising: sending, to the third device, a request for the interactive application to receive the focus of the modified interface, wherein the request comprises a content-rendering device identifier, a transaction identifier, and a command; and receiving, from the third device, a response to the request, wherein the response indicates whether the interactive application has the focus of the modified interface. 11. The method of claim 8 , comprising: receiving a pre-defined interface module in the second format, wherein the pre-defined interface module corresponds to one or more interface elements in the output of the interactive application. 12. The method of claim 1 , comprising: sending, to a display device different from the second device, video content associated with the interactive application; and receiving, from the second device and after initiating the sending the video content, a request for the interactive application. 13. A system comprising: a first device compatible with a first format, and a second device that is compatible with a second format and that is incompatible with the first format, wherein the first device is configured to: receive, in the first format, data relating to an interactive application; based on the data, generate an interface in the second format, wherein the interface corresponds to an output of the interactive application; send the interface in the second format to the second device; receive, from the second device, user input in the second format; convert the user input from the second format into the first format; and execute a function of the interactive application using the converted user input in the first format; and wherein the second device is configured to send the user input in the second format. 14. The system of claim 13 , wherein the first device is configured to: receive, by the interactive application, input from multiple devices, wherein the interactive application corresponds to a multi-user interactive application configured to receive the input from the multiple devices. 15. The system of claim 13 , wherein the first device is configured to: generate an updated interface corresponding to an output of the interactive application, wherein the updated interface comprises page changes based on the user input. 16. The system of claim 13 , wherein the first device is configured to: receive data in an Enhanced Binary Interchange Format (EBIF) as part of receiving the data in the first format, and receive data in an Extensible Markup Language (XML) or a hypertext markup language (HTML) as part of receiving the user input in the second format. 17. One or more non-transitory computer-readable media storing executable instructions that, when executed by at least one processor, cause: receiving data in a first format, the data relating to an interactive application; generating, based on the data, an interface in a second format, the interface corresponding to an output of the interactive application; sending the interface in the second format to a second device that is compatible with the second format and that is incompatible with the first format; receiving, from the second device, user input in the second format; converting the user input from the second format into the first format; and executing a function of the interactive application using the converted user input in the first format. 18. The one or more non-transitory computer-readable media of claim 17 , wherein the instructions, when executed, cause: receiving, by the interactive application, input from multiple devices, wherein the interactive application corresponds to a multi-user interactive application configured to receive the input from the multiple devices. 19. The one or more non-transitory computer-readable media of claim 17 , wherein the instructions, when executed, cause: generating an updated interface corresponding to an output of the interactive application, wherein the updated interface comprises page changes based on the user input. 20. The one or more non-transitory computer-readable media of claim 17 , wherein the instructions, when executed, cause: receiving data in an Enhanced Binary Interchange Format (EBIF) as part of receiving the data in the first format, and receiving data in an Extensible Markup Language (XML) or a hypertext markup language (HTML) as part of receiving the user input in the second format.

Assignees

Inventors

Classifications

  • G06F8/38Primary

    for implementing user interfaces · CPC title

  • Remote windowing, e.g. X-Window System, desktop virtualisation (protocols for virtual reality H04L67/131) · CPC title

  • Protocols for interworking; Protocol conversion · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US10983765B2 cover?
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 inpu…
Who is the assignee on this patent?
Comcast Cable Comm Llc, Comcast Cable Communications Ffc
What technology area does this patent fall under?
Primary CPC classification G06F8/38. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Apr 20 2021 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).