Run-time determination of application delivery

• US 9,753,716 B2
• Filed: 07/16/2015
• Issued: 09/05/2017
• Est. Priority Date: 03/14/2003
• Status: Expired due to Fees

• Current Assignee: Sbc Knowledge Ventures, L.P.
• Original Assignee: AT&T Intellectual Property I LP (AT&T, Inc.)
• Inventors: Gorti, Sreenivasa R.
• Primary Examiner(s): Vo, Ted T
• Application Number:
  US14/801,393
• Publication Number:
  US 20150324187A1
• Time in Patent Office: 782 Days
• Field of Search: 717101-107, 717120-122, 717171-178
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 8/76 Adapting program code to run in a different environment; Porting
• 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/30 Profiles

Abstract

Each of a first and second component version for each of a first and second component of a software application are stored. A profile of the client device is determined. The profile includes a programming language requirement for the client device, a processing capability of the client device and a display capability of the client device. Component versions are selected based on the profile of the client device. One of the selected component version for the first component and the second component of the software application is executed by an application server.

Claims

1. A method for providing a software application from a server over a communication network to a client device, the method comprising:

storing a first component version for a first component of a software application in one or more memories;

storing a second component version for the first component of the software application in the one or more memories;

storing a first component version for a second component of the software application in the one or more memories;

storing a second component version for the second component of the software application in the one or more memories;

determining, by one or more processors, a profile of the client device including a programming language requirement for the client device, a processing capability of the client device and a display capability of the client device;

selecting, by the one or more processors, based on the profile of the client device including the programming language requirement for the client device, the processing capability of the client device and the display capability of the client device, one of the first component version and the second component version for the first component of the software application;

selecting, by the one or more processors, based on the profile of the client device including the programming language requirement for the client device, the processing capability of the client device and the display capability of the client device , one of the first component version and the second component version for the second component of the software application; and

transmitting selection information from the client device to the application server over the communication network,

wherein one of the selected component versions for the first component and the second component of the software application is executed by the application server.

2. The method according to claim 1,

wherein the selected component version for the first component and the selected component version for the second component are dynamically partitioned into a first group and a second group based on the determined profile.

3. The method according to claim 2,

wherein the second group is retained at the application server.

4. The method according to claim 1, further comprising:

determining a user deployment preference for deploying the first component to the client device.

5. The method according to claim 4,

wherein the selected component version for the first component is selected also based on the determined user deployment preference for deploying the first component to the client device.

6. The method according to claim 4, further comprising:

determining whether the user deployment preference for deploying components is feasible, and

when the user deployment preference is feasible, selecting the selected component version for the first component also based on the determined user deployment preference.

7. The method according to claim 1,

wherein the profile of the client device is determined upon receipt of a launch request for the software application from a client device.

8. The method according to claim 7,

wherein the client device comprises a mobile device.

9. The method according to claim 1,

wherein the other of the selected component version for the first component and the second component of the software application is executed by the client device.

10. The method according to claim 1, further comprising:

forwarding an application manager to the client device to determine the profile of the client device.

11. The method according to claim 1, further comprising:

requesting the client device to forward the profile.

12. The method according to claim 1, further comprising:

determining whether an application component already exists on the client device prior to selecting any component version.

13. A system for providing a software application to a requesting client device, comprising:

a memory that stores instructions, and

a processor that executes the instructions, wherein, when executed by the processor, the instructions cause the system to perform a process comprising;

storing a first component version for a first component of a software application;

storing a second component version for the first component of the software application;

storing a first component version for a second component of the software application;

storing a second component version for the second component of the software application;

determining a profile of the client device including a programming language requirement for the client device, a processing capability of the client device and a display capability of the client device;

selecting, based on the profile of the client device including the programming language requirement for the client device, the processing capability of the client device and the display capability of the client device, one of the first component version and the second component version for the first component of the software application; and

selecting, based on the profile of the client device including the programming language requirement for the client device, the processing capability of the client device and the display capability of the client device , one of the first component version and the second component version for the second component of the software application;

wherein one of the selected component version for the first component and the second component of the software application is executed by an application server.

14. The system according to claim 13,

wherein the selected component version for the first component and the selected component version for the second component are dynamically partitioned into a first group and a second group based on the determined profile:

wherein the second group is retained at the application server;

wherein the first group is executed by the client device, and

wherein the application is executed using the first group and second group.

15. The system according to claim 13,

wherein the process performed by the system further comprises selecting a plurality of components as a group based on the profile.

16. The system according to claim 13,

wherein the process performed by the system further comprises iteratively selecting each of a plurality of components based on the profile.

17. The system according to claim 13,

wherein the application server determines a processor configuration of the client device to determine the processing capability.

18. The system according to claim 14,

wherein the selected component version for the first component and the selected component version for the second component are dynamically partitioned into a first group and a second group in accordance with pre-established deployment policies set prior to the software application being published and made available to the client device.

19. The system according to claim 18,

wherein the application server forwards an application manager to the client device to determine a profile of the client device.

20. The system according to claim 18,

wherein the pre-established deployment policies match profile constraints for the client device with either the first component version or the second component version for the first component so that the first component version or the second component version for the first component is selected based on the profile of the client device.