Adaptive deployment of applications for mobile devices

Patent metadata

Field	Value
Publication number	US-10599414-B2
Application number	US-201615340296-A
Country	US
Kind code	B2
Filing date	Nov 1, 2016
Priority date	Nov 7, 2005
Publication date	Mar 24, 2020
Grant date	Mar 24, 2020

Abstract

A method of installing an application on a mobile user device is disclosed. A request for the application is received. Information is received related to the mobile user device on which the application is to be installed. A version of an application is determined to send in response to the request for the application and the information related to the mobile user device. The application version is sent to the mobile user device. Information is received related to the performance of the application version. Adapted application determination information is stored related to at least a portion of the received information.

First claim

What is claimed is:

1. A method comprising:
receiving, by a processor, a request from a user of a mobile device for installing a version of an application on the mobile device;
transmitting, by the processor, a network request to the mobile device in response to receiving the request;
receiving, by the processor, a response to the network request from the mobile device, the response including a unique identification of the mobile device and resource description framework (RDF) information of the mobile device;
creating, by the processor, a metadata signature for the mobile device by parsing the response of the mobile device, the metadata signature including at least one feature present on the mobile device based at least in part on said RDF information;
retrieving, by the processor, a configuration of software components from an application component data store based on mapping the metadata signature to the configuration of software components, the configuration of software components being selected from multiple software components that can be assembled into variations of the application, the multiple software components providing functionality executed by the mobile device;
compiling, by the processor, the configuration of software components into a device version of the application, the compilation comprising adding the configuration of software components to a predefined application template and compiling the application template and software components into an application binary; and
communicating, by the processor, the device version of the application to the mobile device.

2. The method of claim 1 , further comprising:
assigning, by the processor, a user identifier for the user of the mobile device; and
transmitting, by the processor, a customized pointer for the application to be installed on the mobile device, the customized pointer comprising the user identifier.

3. The method of claim 1 , wherein creating, by the processor, the metadata signature for the mobile device comprising:
determining, based on the interrogation, if fundamental requirements are available on the mobile device.

4. The method of claim 1 , wherein interrogating, by the processor, the mobile device upon receiving the request comprising:
sending a request for metadata to the mobile device; and
receiving the metadata from the mobile device.

5. The method of claim 4 , wherein creating, by the processor, the metadata signature for the mobile device comprising:
parsing information from the received metadata for creating the metadata signature.

6. The method of claim 5 , wherein the parsed information comprises carrier information for the mobile user device.

7. The method of claim 5 , wherein the parsed information comprises a feature of the mobile user device.

8. The method of claim 5 , wherein the parsed information comprises a specification of a resource available on the mobile user device.

9. The method of claim 5 , wherein the parsed information comprises an error message relating to a failed prior deployment of the application.

10. The method of claim 5 , wherein the parsed information comprises application state information from a prior version of the application.

11. The method of claim 1 , further comprising:
determining, by the processor, if the mobile device is known or unknown based on existence of an entry for the metadata signature of the mobile device in a device database;
loading, by the processor, a corresponding device template that comprises the configuration of software components predetermined as currently optimal for the mobile device if it is determined that the mobile device is known; and
adding, by the processor, the configuration of software components based on the metadata signature if it is determined that the mobile device is unknown.

12. The method of claim 1 , wherein the version of the application comprises a customized compiled executable file customized for execution on the mobile device.

13. A system comprising:
a processor; and
a memory coupled with the processor, wherein the memory comprising instructions for:
receiving a request from a user of a mobile device for installing a version of an application on the mobile device;
transmitting a network request to the mobile device in response to receiving the request;
receiving a response to the network request from the mobile device, the response including a unique identification of the mobile device and resource description framework (RDF) information of the mobile device;
creating, based on the interrogation, a metadata signature for the mobile device by parsing the response of the mobile device, the metadata signature including at least one feature present on the mobile device based at least in part on said RDF information;
retrieving a configuration of software components from an application component data store based on mapping the metadata signature to the configuration of software components, the configuration of software components being selected from multiple software components that can be assembled into variations of the application, the multiple software components providing functionality executed by the mobile device;
compiling the configuration of software components into a device version of the application, the compilation comprising adding the configuration of software components to a predefined application template and compiling the application template and software components into an application binary; and
communicating the device version of the application to the mobile device.

14. The system of claim 13 , wherein the memory further comprising instructions for:
assigning a user identifier for the user of the mobile device; and
transmitting a customized pointer for the application to be installed on the mobile device, the customized pointer comprising the user identifier.

15. The system of claim 13 , wherein creating the metadata signature for the mobile device comprising:
determining, based on the interrogation, if fundamental requirements are available on the mobile device.

16. The system of claim 13 , wherein interrogating the mobile device upon receiving the request comprising:
sending a request for metadata to the mobile device; and
receiving the metadata from the mobile device.

17. The system of claim 16 , wherein creating the metadata signature for the mobile device comprising:
parsing information from the received metadata for creating the metadata signature.

18. The system of claim 17 , wherein the parsed information comprises carrier information for the mobile device.

19. The system of claim 13 , wherein the memory further comprising instructions for:
determining if the mobile device is known or unknown based on existence of an entry for the metadata signature of the mobile device in a device database;
loading a corresponding device template that comprises the configuration of software components predetermined as currently optimal for the mobile device if it is determined that the mobile device is known; and
adding the configuration of software components based on the metadata signature if it is determined that the mobile device is unknown.

20. The system of claim 13 , wherein the version of the application comprises a customized compiled executable file customized for execution on the mobile device.

21. A non-transitory computer readable-medium comprising processor-executable instructions for:
receiving a request from a user of a mobile device for installing a

Assignees

• Oath Inc

Inventors

• Byrnes Sean N
• Vanrenen Gabriel J
• Harris Karl B

Classifications

• H04L41/0816 Primary

  the condition being an adaptation, e.g. in response to network events · CPC title

• H04L67/303

  Terminal profiles · CPC title

• H04W4/50

  Service provisioning or reconfiguring · CPC title

• H04L67/02

  based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title

• G06F8/61

  Installation · CPC title