MOBILE DEVICE APPLICATION STREAMING

• US 20140215025A1
• Filed: 03/27/2014
• Published: 07/31/2014
• Est. Priority Date: 10/02/2012
• Status: Active Grant

• Current Assignee: Razer (Asia-Pacific) Pte. Ltd. (Razer Incorporated)
• Original Assignee: Nextbit Systems, Inc. (Razer Incorporated)
• Inventors: Quan, Justin, Chan, Michael A.
• Granted Patent: US 9,380,093 B2
• Time in Patent Office: Days
• US Class Current: 709/219
• CPC Class Codes: G06F 16/125 characterised by the use of retention policies retention policies for HSM systems G06F16/185
• CPC Class Codes: G06F 16/174 Redundancy elimination performed by the file system management of the data involved in backup or backup restore using de-duplication of the data G06F11/14
• CPC Class Codes: G06F 16/20 of structured data, e.g. relational data
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 16/273 Asynchronous replication or reconciliation
• CPC Class Codes: G06F 16/275 Synchronous replication
• CPC Class Codes: G06F 16/278 Data partitioning, e.g. horizontal or vertical partitioning
• CPC Class Codes: G06F 16/93 Document management systems
• CPC Class Codes: G06F 9/5038 considering the execution order of a plurality of tasks, e.g. taking priority or time dependency constraints into consideration scheduling strategies G06F9/4881 and subgroups
• CPC Class Codes: H04B 7/26 at least one of which is mobile
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04M 1/72412 using two-way short-range wireless interfaces
• CPC Class Codes: H04M 2250/10 including a GPS signal receiver
• CPC Class Codes: H04M 2250/12 including a sensor for measuring a physical value, e.g. temperature or motion
• CPC Class Codes: Y02D 10/00 Energy efficient computing, e.g. low power processors, power management or thermal management

Abstract

Technology for decomposing an application into fragments and streaming the application in fragments is disclosed herein. According to at least one embodiment, a computer-implemented method includes steps of determining multiple application fragments of a computer application, wherein each application fragment of the application fragments includes a code to present at least one interface of the computer application; storing the application fragments at a storage device; generating a resource dependency data structure, wherein for each specific application fragment of the application fragments, the resource dependency data structure includes identifications of resources that are needed for running the specific application fragment; and streaming, via a network component, at least one application fragment of the application fragments to a computing device.

Claims

1. A computer-implemented method comprising:

determining multiple application fragments of a computer application, wherein each application fragment of the application fragments includes a code to present at least one interface of the computer application;

storing the application fragments at a storage device;

generating a resource dependency data structure, wherein for each specific application fragment of the application fragments, the resource dependency data structure includes identifications of resources that are needed for running the specific application fragment; and

streaming, via a network component, at least one application fragment of the application fragments to a computing device.

2. The computer-implemented method of claim 1, further comprising:

generating a fragments relationship data structure, wherein the fragments relationship data structure includes identifications of application fragments that leads to another application fragment of the application fragments.

3. The computer-implemented method of claim 2, wherein the streaming comprises:

streaming, via a network component, an application fragment of the application fragments to a computing device, wherein the application fragment can potentially follow another application fragment currently running on the computer device based on the fragments relationship data structure.

4. The computer-implemented method of claim 1, further comprising:

for each specific application fragment of the application fragments, incorporating resources that are needed for running the specific application fragment into the specific application fragment, based on the resource dependency data structure.

5. The computer-implemented method of claim 1, further comprising:

streaming, via the network component, resources that are needed for running the application fragment to the computing device, based on the resource dependency data structure.

6. The computer-implemented method of claim 1, wherein the resources include images, icons, texts, audios, videos, 3D models, or other data included in the computer application.

7. The computer-implemented method of claim 1, wherein the determining further comprises:

running the computer application in a simulated environment of a mobile device.

8. A computer-implemented method comprising:

running, at a computing device, a first fragment as a running instance of a computer application;

receiving, from a server, a second fragment of the computer application, wherein operation of the first fragment can potentially leads to the second fragment;

receiving a signal indicating that the running instance of the computer application transitions from the first fragment to the second fragment; and

in response to the signal, launching the second fragment.

9. The computer-implemented method of claim 8, further comprising:

in response to the signal, stopping the first fragment from running.

10. The computer-implemented method of claim 8, wherein the second fragment includes resources that are needed for running the second fragment.

11. The computer-implemented method of claim 8, further comprising:

receiving a resource dependency data structure, wherein the resource dependency data structure includes identifications of resources that are needed for running fragments of the computer application.

12. The computer-implemented method of claim 11, further comprising:

receiving resources that are needed for running the second fragment, based on the resource dependency data structure.

13. The computer-implemented method of claim 8, further comprising:

receiving a fragments relationship data structure, wherein the fragments relationship data structure includes identifications of fragments that leads to another fragment of the computer application.

14. The computer-implemented method of claim 13, further comprising:

sending a request, to the server, for fragments to which the operation of the first fragment can potentially leads.

15. A server comprising:

a network component configured to communicate with a first computing device;

a processor;

a memory storing instructions which, when executed by the processor, cause the server to perform a process including;

receiving, from the first computing device, multiple fragments of the computer application based on at least one portion of a computer application, wherein each fragment of the fragments includes a code to present at least one interface of the computer application, and the fragments are generated by the first computing device by running the portion of the computer application; and

receiving, from the first computer device, a resource dependency data structure, wherein for each specific fragment of the fragments, the resource dependency data structure includes identifications of resources that are needed for running the specific fragment.

16. The server of claim 15, wherein the process further includes:

receiving a fragments relationship data structure, wherein the fragments relationship data structure includes identifications of fragments that leads to another fragment of the fragments.

17. The server of claim 15, wherein the process further includes:

receiving, from a second computing device, at least on additional fragment of the computer application.

18. The server of claim 15, wherein the process further includes:

in response to a request for the computer application from a client computing device, transmitting at least one fragment of the fragments to the client computing device.

19. The server of claim 18, wherein the process further includes:

transmitting fragments that can potentially follow the at least one fragment, based on a fragments relationship data structure.

20. The server of claim 18, wherein the transmitted fragments are selected so that the transmitted fragments are enough for the client computing device to start or continue running the computer application.

21. A computer-implemented method comprising:

running, at a computing device, a container application;

receiving, from a server, a first fragment of a computer application;

executing, at the computing device, the first fragment through a control of the container application; and

launching, at the computer device, a second fragment of the computer application received from the server by the container application when the first fragment ends its execution.

22. The computer-implemented method of claim 21, further comprising:

determining, by the container application, a second fragment of the computer application that follows the first fragment, based on a fragments relationship data structure; and

receiving, from the server, the second fragment of the computer application.

23. The computer-implemented method of claim 21, further comprising:

sending a request generated by the container application, to the server, for fragments to which an operation of the first fragment can potentially leads; and

receiving, from the server, a second fragment of the computer application.