Computing system for providing software components on demand to a mobile device

• US 8,312,451 B2
• Filed: 05/15/2009
• Issued: 11/13/2012
• Est. Priority Date: 11/15/2006
• Status: Active Grant

• Current Assignee: Univirtua Ireland Limited
• Original Assignee: Univirtua Ireland Limited
• Inventors: Poole, Joseph Timothy, Beckles, Rohan Nathaniel
• Primary Examiner(s): Nguyen, Phillip H
• Application Number:
  US12/467,026
• Publication Number:
  US 20090282403A1
• Time in Patent Office: 1,278 Days
• Field of Search: 717/171, 717/173, 717/176, 717/178, 717/168, 717/174
• US Class Current: 717/178
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416

Abstract

A computing system includes a computer network, a server connected thereto, and a client device for communicating with the server over the computer network. The client device runs an application shell software module providing a dynamically configurable application in a piecemeal manner by individually downloading and running a plurality of software components that are individually stored on the computer network and downloaded/run when needed. The server receives a request for available software components from the application shell software module, controls a search of an index for available software components and transmits a response to the application shell software module providing details of available software components. The application shell software module receives details of available software components from the server, retrieves a selected software component from the location identified by location data for the selected software component, and starts and stops the selected software component within the application shell software module in accordance with received data.

Claims

1. A computing system comprising:

a computer network;

a server connected to the computer network; and

a client device operable for communicating with said server over said computer network;

wherein said client device comprises at least one processor that executes an application shell software module that provides a dynamically configurable application in a piecemeal manner by individually downloading and loading a plurality of software components into the application shell software module, each software component being individually stored on the computer network and being downloaded and run by the client device when needed and being discarded from the client device after being run;

wherein said server receives, from the application shell software module, a request for available software components, controls a search of an index for available software components and transmits a response to said application shell software module providing details of available software components that were not identified in the received request, including, for each software component;

i) identification data identifying the software component;

ii) location data identifying a location from which the software component can be obtained; and

iii) start and stop data identifying how to start and stop the software component;

wherein said application shell software module;

i) receives said details of available software components from said server;

ii) retrieves a selected software component from the location identified by said location data for the selected software component; and

iii) starts and stops the selected software component within the application shell software module in accordance with the received start and stop data.

2. The system according to claim 1, wherein said software components are stored in different locations within a common store connected to said computer network.

3. The system according to claim 1, wherein said application shell is operable to transmit a text string request for available software components and wherein said server is operable:

i) to receive said text string request for available software components from the application shell software module;

ii) to parse the text string request and to generate a query using the text in the request; and

iii) to control the search of said index for available software components using the query.

4. The system according to claim 1, wherein said server is operable to transmit a text string response to said application shell software module providing details of available software components, including, for each software component:

i) text identifying the software component; and

ii) text identifying a location from which the software component can be obtained;

wherein said application shell software module is operable;

i) to receive said text string response;

ii) to parse the received text string response to obtain the text identifying the available software components and the text identifying the locations of the available software components; and

iii) to retrieve and run a selected software component using the text identifying the location of the selected software component.

5. A client device comprising:

a processor that executes an application shell software module that provides a dynamically configurable application in a piecemeal manner by individually downloading and loading a plurality of software components into the application shell software module, each software component being individually stored on the computer network and being downloaded and run by the client device when needed and being discarded from the client device after being run; and

wherein said application shell software module;

i) sends a request for available software components to a remote server so that the remote server can control a search of an index for available software components;

ii) receives from the remote server details of available software components that were not identified in the sent request which details include, for each software component;

a) identification data identifying the software component;

b) location data identifying a location from which the software component can be obtained; and

c) start and stop data identifying how to start and stop the software component;

iii) retrieves a selected software component from the location identified by said location data for the selected software component; and

iv) starts and stops the selected software component within the application shell software module in accordance with the received start and stop data.

6. The client device according to claim 5, wherein said application shell software module is operable:

iv) to start the component and, once the component is no longer required, to stop the component in accordance with the start and stop data.

7. The client device according to claim 6, wherein said start and stop data causes said application shell software module to remove the software component from the memory of the client device.

8. The client device according to claim 5, wherein said application shell software module comprises a request generator for constructing and sending said request to said server from information obtained from a configuration file containing configuration information for or about said client device.

9. The client device according to claim 5, wherein said application shell software module comprises:

a response receiver for receiving said server'"'"'s response and for populating a component data table for each available software component with the corresponding details for the software component data contained within the response.

10. The client device according to claim 5, wherein said application shell software module comprises:

a code provider for retrieving the selected component; and

an application container in which the retrieved software component is run.

11. The client device according to claim 5, wherein said application shell software module is a Java object.

12. The client device according to claim 5, wherein said software components are single-purpose units of code that each perform a specific function.

13. The client device according to claim 5, wherein each software component is operable to implement a substantially different part of the dynamically configurable application'"'"'s functionality, that part being small in relation to the overall size of the dynamically configurable application.

14. The client device according to claim 5, wherein said application shell software module is operable:

to identify, to a user, the available software components for user selection in accordance with the received data identifying the available software components;

in response to receiving a user selection of a software component, to retrieve the selected software component from the location identified by said location data; and

to start and stop the retrieved software module in accordance with the start and stop data.

15. The client device according to claim 5, wherein said client device is a smart telephone.

16. The client device according to claim 5, wherein said application shell is operable to retrieve said software components by downloading them from said location using a standard download protocol.

17. The client device according to claim 5, wherein said client device is battery powered and comprises solid state memory only.

18. The client device according to claim 5, wherein said software components are retrieved and run in volatile memory only.

19. The client device according to claim 5, wherein said client device comprises a plurality of application shells, each associated with a respective different server on said network, and wherein, when the client device is running one of said application shells, the client device is operable to communicate with the corresponding server associated with that application shell.

20. The client device according to claim 5, wherein said application shell is operable to provide multiple dynamically configurable applications, each associated with a respective server, and wherein said client device is operable to connect to a selected one of said servers in dependence upon a selected one of said dynamically configurable applications.

21. A non-transitory computer program product comprising at least one computer-readable medium having computer implementable instructions embodied thereon, the computer implementable instructions being configured to be executable by a processor to:

execute an application shell software module that provides a dynamically configurable application in a piecemeal manner by individually downloading and loading a plurality of software components into the application shell software module, each software component being individually stored on a computer network and being downloaded and run by a client device when needed and being discarded from the client device after being run;

send, via the processor, a request for available software components to a remote server so that the remote server can control a search of an index for available software components;

receive, from the remote server, details of available software components that were not identified in the sent request, which details include for each software component;

a) identification data identifying the software component;

b) location data identifying a location from which the software component can be obtained; and

c) start and stop data identifying how to start and stop the software component;

retrieve a selected software component from the location identified by said location data for the selected software component; and

start and stop the selected software component within the application shell software module in accordance with the received start and stop data.

22. A server comprising a processor that is operable to:

receive, from an application shell software module running on a client device, a request for available software components, wherein the application software module being executed to provide a dynamically configurable application in a piecemeal manner by individually downloading and loading a plurality of software components into the application shell software module, each software component individually stored on a computer network and being downloaded and run by the client device when needed and being discarded from the client device after being run,

control a search of an index for available software components that are not identified in the received request, and

transmit a response to said application shell software module providing details of available software components, including, for each software component;

i) identification data identifying the software component;

ii) location data identifying a location from which the software component can be obtained; and

iii) start and stop data identifying how the application shell software module can start and stop the software component, so that the application shell software module can retrieve a selected software component from the location identified by said location data for the selected software component and can start and stop the selected software component within the application shell software module in accordance with the received start and stop data for the selected software component.

23. The server according to claim 22, wherein said index is stored in a repository and wherein said server comprises:

a query generator for translating said received request for said available software components into a query suitable for use in querying said index in said repository;

a repository provider for searching said index in said repository for said available software components using said query; and

a response generator for generating said response from search results obtained from said repository provider.

24. The server according to claim 22, wherein said server comprises a repository admin provider for maintaining said index of said software components.

25. The server according to claim 24, wherein said repository admin provider is operable to maintain said index by updating said index to include new components.

26. The server according to claim 24, wherein said repository admin provider is operable to maintain said index by updating said index to remove legacy software components.

27. The server according to claim 22, wherein said available software components are the subset of all possible software components determined in dependence upon data contained in the received request.

28. The server according to claim 27, wherein said server is operable to identify said subset of available software components by matching data received in the request with data stored for each software component in the index.

29. The server according to claim 22, wherein the location of each software component is identified by a Uniform Resource Locator.

30. The server according to claim 22, wherein said index comprises a plurality of descriptors, each descriptor being associated with a respective one of a plurality of software components and comprising a plurality of descriptor nodes each hiving a plurality of attribute key-value pairs relating to the associated software component;

wherein said search of the index is performed by matching attribute key-value pairs defined within said received request with the attribute key-value pairs of each descriptor; and

wherein the server is operable to provide, in said response, details of software components for which a match is found between the attribute key-value pairs of the request and the attribute key-value pairs of the associated descriptor.

31. The server according to claim 22, wherein said index comprises a plurality of descriptor Java objects, each descriptor object being associated with a respective one of a plurality of software components and having a plurality of associated attribute Java objects each defining an attribute key-value pair relating to the associated software component;

wherein said search of the index is performed by matching attribute key-value pairs defined within said received request with the attribute Java objects associated with each descriptor Java object; and

wherein the server is operable to provide, in said response, details of software components for which a match is found between the attribute key-value pairs of the request and the attribute Java objects of the associated descriptor Java object.

32. The server according to claim 22, wherein said server is operable to determine user subscription data for the user of the client device and is operable to control the search of said index so that said response does not include details of available software components for which the user has not subscribed.

33. A non-transitory computer program product comprising at least one computer-readable medium having computer implementable instructions embodied thereon, the computer implementable instructions being configured to be executable by a processor to:

receive, from an application shell software module running on a client device, a request for available software components, wherein the application shell software module being executed to provide a dynamically configurable application in a piecemeal manner by individually downloading and loading a plurality of software components into the application shell software module, each software component individually stored on a computer network and being downloaded and run by the client device when needed and being discarded from the client device after being run,

control, via the processor, a search of an index for available software components that are not identified in the received request, and

transmit, via the processor, a response to said application shell software module providing details of available software components, including, for each software component;

i) identification data identifying the software component;

ii) location data identifying a location from which the software component can be obtained; and

iii) start and stop data identifying how the application shell software module can start and stop the software component, so that the application shell software module can retrieve a selected software component from the location identified by said location data for the selected software component and can start and stop the selected software component within the application shell software module in accordance with the received start and stop data for the selected software component.