METHOD AND A SYSTEM TO GENERATE AND MANAGE NATIVE APPLICATIONS

• US 20140109197A1
• Filed: 03/30/2012
• Published: 04/17/2014
• Est. Priority Date: 04/15/2011
• Status: Abandoned Application

• Current Assignee: Telefonica SA
• Original Assignee: Telefonica SA
• Inventors: Schneider, Michael, Coloma, Daniel Jess
• Application Number:
  US14/111,871
• Publication Number:
  US 20140109197A1
• Time in Patent Office: Days
• US Class Current: 726/4
• CPC Class Codes: G06F 21/6281 at program execution time, where the protection is within the operating system
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: H04L 63/0876 based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint

Abstract

The method comprises:

• • a) creating, an application developer, a run time based generic application;
  • b) generating a plurality of native applications for different corresponding operating systems by bundling said generic application together with a runtime for every supported operating system, or OS, said runtimes handling OS Device APIs and Network APIs; and
  • c) managing said native applications by at least their storage in a database and/or their distribution to computing devices.

The system comprising means for performing said steps b) and c) of the method of the invention.

Claims

1-14. -14. (canceled)

15. A method to generate and manage native applications, comprising:

a) creating, by an application developer, a run time based generic application;

b) generating a plurality of native applications for different corresponding operating systems by bundling said generic application together with a runtime for every supported operating system, or OS, said runtimes handling OS Device APIs; and

c) managing said native applications by at least their storage in a database and/or their distribution to computing devices;

wherein the method is characterized in that said step b) further comprises;

bundling said generic application together with a runtime handling Network APIs to use resources available in the Network; and

performing at least one of the next further actions for the generation of each of said native applications providing a security handling thereof;

adding a security framework for restricting the access to said OS Device APIs;

adding a security framework for controlling the authentication and authorization of the usage of said Network APIs; and

/or

applying at least one of a set of transformation rules including;

application signing and embedding developer credentials for Network APIs usage,

wherein said controlling of the authentication and authorization of the usage of said Network APIs is performed by means of asking, by said security framework, to an user, to provide credentials for accessing a network resource, said credentials being used to obtain an authentication code from said network resource and used in turn to access functionality of said resource by means of invoking the corresponding Network API.

16. The method according to claim 15, further comprising checking the validity of said generic application before and as a condition to start said step b).

17. The method according to claim 15, comprising creating said generic application at step a) based on runtime specifications and using only the technology runtime provides.

18. The method according to claim 15, comprising, for every of said native application generation, performing said step b) for carrying out said bundling of runtimes or said bundling of runtimes and further actions, according to a workflow.

19. The method according to claim 18, comprising starting said workflow by reading a delivered developer profile, the supported OSs, runtimes and security settings, and based on that, determining what is the workflow that the generic application should go through, said determination including the selection of the runtimes, security frameworks and transformation rules to be applied, from a plurality of runtimes, security frameworks and transformation rules, and the order of their performing.

20. The method according to claim 19, wherein the selection of said OS device APIs security frameworks depends on the level of trust of the developer.

21. The method according to claim 20, comprising adapting/customizing said security frameworks depending on computing device end-user choices.

22. The method according to claim 15, comprising, once the right native application version for the targeted computing device/platform has been installed in said computing device memory, executing for first time the native application, said execution providing the notification notifies the computing device user about the network and device APIs the application is going to use.

23. The method according to claim 22, wherein said first execution also provides the computing device user means for allowing him to customize the prompting regime linked to the network and device APIs.

24. The method according to claim 23, comprising when the native application tries to use a device API, checking whether prompting is needed, and if so, the Device APIs RT Security Framework asks the user for authorization, and in case he allows it or no prompting is needed, the API usage will be authorized and the native capability will be granted and used.

25. The method according to claim 24, comprising when the native application tries to use a network API, the security framework checking if the usage of that API has been authorized before by the end-user, and:

i) if the usage has been authorized before, the security framework already knowing a developer token as well as an authorization token, and including both in a network request that is created based on the original developer call;

ii) if the usage has not been authorized or the authorization has expired the security framework checking the usage authorization of the APIs for said user, and if the authorization is not successful rejecting the request to access the Network APIs, and if it is successful the developer request is further processed as specified in i).

26. A system to generate and manage native applications, comprising means for performing at least said steps b) and c) of the method according to claim 15.

27. The system according to claim 26, comprising at least one of the next databases for managing different information needed for implementing the method:

Runtimes Database, in which said runtimes are available;

Rules Database, in which the transformation rules are available;

Devices Database, in which information about the supported OS and devices is stored;

Developers Database, in which developer information and credentials are available; and

Applications Database, in which generic and native applications are available.

28. The system according to claim 27, further comprising an application translator unit for performing the method, further comprising for every of said native application generation, performing said step b) for carrying out said bundling of runtimes or said bundling of runtimes and further actions, according to a workflow;

and

starting said workflow by reading a delivered developer profile, the supported OSs, runtimes and security settings, and based on that, determining what is the workflow that the generic application should go through, said determination including the selection of the runtimes, security frameworks and transformation rules to be applied, from a plurality of runtimes, security frameworks and transformation rules, and the order of their performing.