Software Application Delivery and Launching System

• US 20120215831A1
• Filed: 02/22/2011
• Published: 08/23/2012
• Est. Priority Date: 02/22/2011
• Status: Active Grant

• Current Assignee: Julian Michael Urbach
• Original Assignee: Julian Michael Urbach
• Inventors: Urbach, Julian Michael
• Granted Patent: US 10,114,660 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06F 9/44526 Plug-ins; Add-ons
• CPC Class Codes: G06F 9/44573 Execute-in-place [XIP]
• CPC Class Codes: G06F 9/44584 Portable applications, i.e. making applications self-contained, e.g. U3 standard
• CPC Class Codes: G06F 9/44594 Unloading
• CPC Class Codes: G06F 9/4484 Executing subprograms

Abstract

One embodiment allocates a first virtual memory; receives executable code of a first piece of software; writes the executable code of the first piece of software directly into the first virtual memory; marks the first virtual memory as executable; executes the executable code of the first piece of software directly from the first virtual memory; and downloads and executes executable code of a second piece of software as facilitated by the executable code of the first piece of software.

Claims

1. A method, comprising:

allocating, by a first computing device, a first virtual memory;

receiving, by the first computing device, executable code of a first piece of software;

writing, by the first computing device, the executable code of the first piece of software directly into the first virtual memory;

marking, by the first computing device, the first virtual memory as executable;

executing, by the first computing device, the executable code of the first piece of software directly from the first virtual memory; and

downloading and executing, by the first computing device, executable code of a second piece of software as facilitated by the executable code of the first piece of software.

2. The method recited in claim 1, further comprising loading one or more shared libraries needed by the executable code of the first piece of software.

3. The method recited in claim 1, further comprising de-allocating the first virtual memory after the execution of the executable code of the first piece of software is completed so that there is no trace of the executable code of the first piece of software on the first computing device.

4. The method recited in claim 1, wherein downloading and executing the executable code of the second piece of software as facilitated by the executable code of the first piece of software comprises:

receiving the executable code of the second piece of software;

extracting the executable code of the second piece of software from the data stream;

allocating a second virtual memory;

writing the executable code of the second piece of software directly into the second virtual memory;

marking the second virtual memory as executable; and

executing the executable code of the second piece of software directly from the second virtual memory.

5. The method recited in claim 4, further comprising:

validating the executable code of the second piece of software;

loading one or more first shared libraries needed by the executable code of the second piece of software existing on the first computing device; and

downloading one or more second shared libraries needed by the executable code of the second piece of software from a second computing device.

6. The method recited in claim 4, further comprising de-allocating the second virtual memory after the execution of the executable code of the second piece of software is completed so that there is no trace of the executable code of the second piece of software on the first computing device.

7. The method recited in claim 4, further comprising determining the second piece of software based on an operating system of the first computing device.

8. The method recited in claim 4, wherein:

the executable code of the first piece of software is received from a second computing device; and

the executable code of the second piece of software is received from a third computing device.

9. The method recited in claim 4, wherein the executable code of the first piece of software and the executable code of the second piece of software are both received from a second computing device.

10. The method recited in claim 4, wherein the executable code of the second piece of software is embedded in a data stream.

11. A first system, comprising:

a memory comprising instructions executable by one or more processors; and

one or more processors coupled to the memory and operable to execute the instructions, the one or more processors being operable when executing the instructions to;

allocate a first virtual memory;

receive executable code of a first piece of software;

write the executable code of the first piece of software directly into the first virtual memory;

mark the first virtual memory as executable;

execute the executable code of the first piece of software directly from the first virtual memory; and

download and execute executable code of a second piece of software as facilitated by the executable code of the first piece of software.

12. The system recited in claim 11, wherein the one or more processors are further operable when executing the instructions to load one or more shared libraries needed by the executable code of the first piece of software.

13. The system recited in claim 11, wherein the one or more processors are further operable when executing the instructions to de-allocate the first virtual memory after the execution of the executable code of the first piece of software is completed so that there is no trace of the executable code of the first piece of software on the first computing device.

14. The system recited in claim 11, wherein downloading and executing the executable code of the second piece of software as facilitated by the executable code of the first piece of software comprises:

receive the executable code of the second piece of software;

extract the executable code of the second piece of software from the data stream;

allocate a second virtual memory;

write the executable code of the second piece of software directly into the second virtual memory;

mark the second virtual memory as executable; and

execute the executable code of the second piece of software directly from the second virtual memory.

15. The system recited in claim 14, wherein the one or more processors are further operable when executing the instructions to:

validate the executable code of the second piece of software;

load one or more first shared libraries needed by the executable code of the second piece of software existing on the first computing device; and

download one or more second shared libraries needed by the executable code of the second piece of software from a second computing device.

16. The system recited in claim 14, wherein the one or more processors are further operable when executing the instructions to de-allocate the second virtual memory after the execution of the executable code of the second piece of software is completed so that there is no trace of the executable code of the second piece of software on the first computing device.

17. The system recited in claim 14, wherein the one or more processors are further operable when executing the instructions to determine the second piece of software based on an operating system of the first computing device.

18. The system recited in claim 14, wherein:

the executable code of the first piece of software is received from a second computing device; and

the executable code of the second piece of software is received from a third computing device.

19. The system recited in claim 14, wherein the executable code of the first piece of software and the executable code of the second piece of software are both received from a second computing device.

20. The system recited in claim 14, wherein the executable code of the second piece of software is embedded in a data stream.

21. One or more computer-readable storage media embodying software operable when executed by a first computer system to:

allocate a first virtual memory;

receive executable code of a first piece of software;

write the executable code of the first piece of software directly into the first virtual memory;

mark the first virtual memory as executable;

execute the executable code of the first piece of software directly from the first virtual memory; and

download and execute executable code of a second piece of software as facilitated by the executable code of the first piece of software.

22. The media recited in claim 21, wherein the software is further operable when executed by the first computer system to load one or more shared libraries needed by the executable code of the first piece of software.

23. The media recited in claim 21, wherein the software is further operable when executed by the first computer system to de-allocate the first virtual memory after the execution of the executable code of the first piece of software is completed so that there is no trace of the executable code of the first piece of software on the first computing device.

24. The media recited in claim 21, wherein downloading and executing the executable code of the second piece of software as facilitated by the executable code of the first piece of software comprises:

receive the executable code of the second piece of software;

extract the executable code of the second piece of software from the data stream;

allocate a second virtual memory;

write the executable code of the second piece of software directly into the second virtual memory;

mark the second virtual memory as executable; and

execute the executable code of the second piece of software directly from the second virtual memory.

25. The media recited in claim 24, wherein the software is further operable when executed by the first computer system to:

validate the executable code of the second piece of software;

load one or more first shared libraries needed by the executable code of the second piece of software existing on the first computing device; and

download one or more second shared libraries needed by the executable code of the second piece of software from a second computing device.

26. The media recited in claim 24, wherein the software is further operable when executed by the first computer system to de-allocate the second virtual memory after the execution of the executable code of the second piece of software is completed so that there is no trace of the executable code of the second piece of software on the first computing device.

27. The media recited in claim 24, wherein the software is further operable when executed by the first computer system to determine the second piece of software based on an operating system of the first computing device.

28. The media recited in claim 24, wherein:

the executable code of the first piece of software is received from a second computing device; and

the executable code of the second piece of software is received from a third computing device.

29. The media recited in claim 24, wherein the executable code of the first piece of software and the executable code of the second piece of software are both received from a second computing device.

30. The media recited in claim 24, wherein the executable code of the second piece of software is embedded in a data stream.