Content management and transformation system for digital content

• US 9,686,378 B2
• Filed: 05/09/2016
• Issued: 06/20/2017
• Est. Priority Date: 06/29/2001
• Status: Expired due to Term

• Current Assignee: Intellectual Ventures II LLC (Intellectual Ventures LLC)
• Original Assignee: Callahan Cellular LLC (Intellectual Ventures LLC)
• Inventors: Judd, David T., Brewster, Jason A., Melia, P. Michael, Lilly, David J.
• Primary Examiner(s): Nguyen, Angela
• Application Number:
  US15/150,264
• Publication Number:
  US 20160330296A1
• Time in Patent Office: 407 Days
• Field of Search: None
• CPC Class Codes: G06F 16/88 Mark-up to mark-up conversion conversion for visualization in web browsing G06F16/9577
• CPC Class Codes: G06F 16/951 Indexing; Web crawling techniques
• CPC Class Codes: G06F 16/9577 Optimising the visualization of content, e.g. distillation of HTML documents
• CPC Class Codes: G06F 3/0484 for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
• CPC Class Codes: G06F 40/117 Tagging; Marking up details of markup languages G06F40/143; Designating a block; Setting of attributes style sheets, e.g. eXtensible Stylesheet Language Transformation [XSLT], G06F40/154
• CPC Class Codes: G06F 40/14 Tree-structured documents parsing G06F40/205; validation G06F40/226
• CPC Class Codes: G06F 40/143 Markup, e.g. Standard Generalized Markup Language [SGML] or Document Type Definition [DTD]
• CPC Class Codes: G06F 40/197 Version control for software G06F8/71
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/75 Indicating network or usage conditions on the user display

Abstract

A transformation engine that enables content and information to be transformed from one format, a source format, to a format that is compatible with the requesting device, a destination format. Advantageously, various device types can access and share content via a network without concern as to the original format of the content. When a client device provides a request for content, the transformation engine identifies delivery characteristics of the client device, and identifies a source for the requested content. The transformation engine then transforms the source formatted content into a format identified through a best fit analysis of the delivery characteristics of the device.

Claims

1. A method implemented by a server, the method comprising:

receiving, by the server from a client device, an indication of an actuation of a user interface provided on the client device, wherein the client device is associated with client variables defining an environment of the client device; and

in response to receiving the indication of the actuation;

invoking, by the server, a version of an application component that is configured for the environment of the client device, wherein the invoking of the application component processes the indication of the actuation and, in response, produces interim data representing results of the application component processing the indication of the actuation;

creating, by the server, based on the determined environment of the client device and using the interim data, an updated version of the user interface for display in the environment of the client device; and

packaging, by the server, the updated version of the user interface for communication to the client device.

2. The method of claim 1,

wherein the updated version of the user interface is configured to accept first interactions that are handled locally by the client device;

and

wherein the updated version of the user interface is configured to accept second interactions that are handled through further communications with the server.

3. The method of claim 1 wherein the one or more client variables describe device display specifics of the client device.

4. The method of claim 1 wherein the one or more client variables is obtained from an HTTP request header.

5. The method of claim 1 wherein creating the updated version of the user interface using the interim data comprises encapsulating the interim data in the user interface so that a visual characteristic resulting from invoking the obtained version of the application component is displayable at the client device without invoking the obtained version of the application component again.

6. The method of claim 1 wherein the user interface is configured to be executed within a browser at the client device.

7. The method of claim 1 wherein:

the version of the application component is obtained from one of a plurality of locations accessible via a network; and

the obtaining includes querying a database that contains information about the plurality of locations.

8. The method of claim 1 wherein:

the client device is a second client device;

the user interface was (A) created in response to an interaction with a first client device different from the second client device, then (B) provided to the second client device; and

the method further includes maintaining, by the server, a state of an application corresponding to the application component, wherein the maintaining is performed between (a) the interaction involving the server and the first client device and (b) providing the user interface to the second client device, such that providing the user interface to the second client device resumes from where the interaction involving the server and the first client device left off.

9. A server comprising a processor and memory, the memory storing instructions that, responsive to execution by the processor, cause the server to perform operations including:

receiving an indication of an actuation of a user interface provided on a client device, wherein the client device is associated with client variables indicating an environment of the client device;

in response to receiving the indication of the actuation, generating an updated version of the user interface for display in the environment of the client device by invoking a version of an application component that is configured for the environment of the client device, wherein the invoking of the application component processes the indication of the actuation; and

packaging the updated version of the user interface for communication to the client device.

10. The server of claim 9 wherein the version of the application component is obtained from a data store that includes access information for each of a plurality of versions of the application component.

11. The server of claim 9,

wherein the updated version of the user interface is configured to accept first interactions that are handled locally by the client device;

and

wherein the updated version of the user interface is configured to accept second interactions that are handled through further communications with the server.

12. The server of claim 9 wherein the user interface is configured to be executed within a browser at the client device.

13. The server of claim 9 wherein the one or more client variables describe hardware characteristics of the client device.

14. The server of claim 9

wherein the client device is a second client device;

wherein the user interface was (A) created in response to an interaction with a first client device different from the second client device, then (B) provided to the second client device; and

wherein the operations further include maintaining a state of an application corresponding to the application component, wherein the maintaining is performed between (a) the interaction involving the server and the first client device and (b) providing the user interface to the second client device, such that providing the user interface to the second client device resumes from where the interaction involving the server and the first client device left off.

15. The server of claim 9 wherein the one or more client variables describe compression or decompression characteristics of the client device.

16. The server of claim 9 wherein generating an updated version of the user interface comprises encapsulating results of processing the indication of the actuation in the user interface so that a visual characteristic resulting from invoking the obtained version of the application component is displayable at the client device without invoking the obtained version of the application component again.

17. The server of claim 10 wherein the version of an application component is obtained based on data that describes a user of the client device.

18. The server of claim 17 wherein the data is a shared profile of users common to a particular domain.

19. A computer-readable storage medium that is neither a carrier wave nor a transmitted signal, the computer-readable storage medium storing instructions that, when executed by a computing system, cause the computing system to perform operations comprising:

receiving, by a server from a client device, an indication of an actuation of a control provided on the client device, wherein the client device is associated with an environment of the client device; and

in response to receiving the indication of the actuation;

invoking, by the server, a version of an application element that is configured for the environment of the client device, wherein the invoking of the application element processes the indication of the actuation and, in response, produces interim data representing results of the application component processing the indication of the actuation;

creating, by the server, based on the determined environment of the client and using the interim data, an updated version of the control for presentation in the environment of the client device; and

packaging, by the server, the updated version of the control or communication to the client device.

20. The computer-readable storage medium of claim 19 wherein the one or more client variables describe one or more of:

hardware characteristics of the client device;

a network connection that communicatively couples the server to the client device;

compression or decompression characteristics of the client device;

data that describes a user of the client device;

or

any combination thereof.