SYSTEM AND METHOD FOR IN-CONTEXT APPLICATIONS

• US 20120159388A1
• Filed: 12/20/2010
• Published: 06/21/2012
• Est. Priority Date: 12/20/2010
• Status: Abandoned Application

• Current Assignee: Fanhattan, Inc. (Adeia Inc.)
• Original Assignee: Fanhattan LLC
• Inventors: Chalouhi, Olivier, Ohlfs, Keith
• Application Number:
  US12/973,690
• Publication Number:
  US 20120159388A1
• Time in Patent Office: Days
• US Class Current: 715/810
• CPC Class Codes: G06F 16/435 Filtering based on additional data, e.g. user or group profiles
• CPC Class Codes: G06F 9/445 Program loading or initiating bootstrapping G06F9/4401; security arrangements for program loading or initiating G06F21/57
• CPC Class Codes: H04W 4/20 Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
• CPC Class Codes: H04W 4/50 Service provisioning or reconfiguring

Abstract

In a method and system for providing in-context applications, a context is selected by a user. Context-specific metadata is retrieved from a context data structure. At least one application identified in the context data structure is loaded for the context. A user interface that includes at least one selectable user interface element is rendered for the context. The selectable user interface element is used to select the at least one loaded application. Based on a determination that a selectable user interface element has been selected, the context-specific metadata is passed to the selected application for use in retrieving context-related data. The context-related data is received via the application.

Claims

1. A computer-implemented method, comprising:

identifying, by a processor, a context selected by a user;

retrieving, by the processor, context-specific metadata from a context data structure;

loading, by the processor, at least one application for the context, the at least one application being identified in the context data structure;

rendering a user interface for the context, the user interface including at least one selectable user interface element for selecting the at least one application;

based on a determination that the at least one selectable user interface element is selected, passing the retrieved context-specific metadata to the at least one application for use in retrieving context-related data; and

receiving the context-related data via the at least one application.

2. The computer-implemented method of claim 1, wherein the context displays at least one content item, and wherein the context-related data comprises a content item of the at least one content item.

3. The computer-implemented method of claim 1, wherein the at least one application comprises at least one plug-in application.

4. The computer-implemented method of claim 1, wherein each of the at least one application is configured to communicate with a content source.

5. The computer-implemented method of claim 1, further comprising registering the at least one application with the context.

6. The computer-implemented method of claim 1, wherein the context-specific metadata includes an identifier used by the at least one application to retrieve the context-related data.

7. The computer-implemented method of claim 6, wherein the identifier is a content identifier, and wherein the context-related data is a content item.

8. The computer-implemented method of claim 1, further comprising based on a determination that the user has selected a new context, repeating the identifying, the retrieving, the loading, the rendering, the passing, and the receiving steps for the new context.

9. The computer-implemented method of claim 1, further comprising registering the identified context.

10. A non-transitory machine-readable medium storing a set of instructions that, when executed by a processor, causes the processor to perform operations, comprising:

identifying a context selected by a user;

retrieving context-specific metadata from a context data structure;

loading at least one application for the context, the at least one application being identified in the context data structure;

rendering a user interface for the context, the user interface including at least one selectable user interface element for selecting the at least one application;

based on a determination that the at least one selectable user interface element is selected, passing the retrieved context-specific metadata to the at least one application for use in retrieving context-related data; and

receiving the context-related data via the at least one application.

11. The non-transitory machine-readable medium of claim 10, wherein the context displays at least one content item, and wherein the context-related data comprises a content item of the at least one content item.

12. The non-transitory machine-readable medium of claim 10, wherein the at least one application comprises at least one plug-in application.

13. The non-transitory machine-readable medium of claim 10, wherein each of the at least one application is configured to communicate with a content source.

14. The non-transitory machine-readable medium of claim 10, further comprising registering the at least one application with the context.

15. The non-transitory machine-readable medium of claim 10, wherein the context-specific metadata includes an identifier used by the at least one application to retrieve the context-related data.

16. The non-transitory machine-readable medium of claim 15, wherein the identifier is a content identifier, and wherein the context-related data is a content item.

17. The non-transitory machine-readable medium of claim 10, further comprising based on a determination that the user has selected a new context, repeating the identifying, the retrieving, the loading, the rendering, the passing, and the receiving steps for the new context.

18. The non-transitory machine-readable medium of claim 10, further comprising registering the identified context.

19. A system, comprising:

a processor-implemented context handler module configured to identify a context selected by a user;

a processor-implemented database interface module configured to retrieve context-specific metadata from a context data structure associated with the context identified by the processor-implemented context handler module;

a processor-implemented plug-in engine configured to load at least one application for the context, the at least one application being identified in the context data structure; and

a processor-implemented user interface rendering module configured to render a user interface for the context, the user interface including at least one selectable user interface element for selecting the at least one application,

the processor-implemented context handler module passing the retrieved context-specific metadata to the at least one application for use in retrieving context-related data based on a determination that the at least one selectable user interface element is selected.

20. The system of claim 19, wherein the context displays at least one content item, and wherein the context-related data comprises a content item of the at least one content item.

21. The system of claim 19, wherein the at least one application comprises at least one plug-in application.

22. The system of claim 19, wherein each of the at least one application is configured to communicate with a content source.

23. The system of claim 19, wherein the processor-implemented plug-in engine is further configured to register the at least one application with the context.

24. The system of claim 19, wherein the context-specific metadata includes an identifier used by the at least one application to retrieve the context-related data.

25. The system of claim 24, wherein the identifier is a content identifier, and wherein the context-related data is a content item.

26. The system of claim 19, wherein the processor-implemented context handler module is further configured to register the identified context.

27. A computer-implemented method, comprising:

generating a user interface for a context, the context associated with at least one content item;

loading at least one plug-in application in the user interface, the at least one application represented in the user interface by a corresponding at least one selectable user interface element;

responsive to a selection of a selectable user interface element, communicating with a content source over a network via the at least one application, the at least one application transmitting a content identifier and metadata associated with the at least one content item to the content source; and

receiving, by the at least one plug-in application, the at least one content item from the content source.