CUSTOM APPLICATION CONTAINER FOR MOBILE OPERATING SYSTEMS AND/OR DEVICES

• US 20130260730A1
• Filed: 03/28/2012
• Published: 10/03/2013
• Est. Priority Date: 03/28/2012
• Status: Abandoned Application

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Enterproid HK Ltd (Alphabet Inc.)
• Inventors: Toy, Andrew Jong Kein, Trewby, Alexander Allan, Zhu, David Wei, Tawileh, Nadim
• Application Number:
  US13/432,684
• Publication Number:
  US 20130260730A1
• Time in Patent Office: Days
• US Class Current: 455/418
• CPC Class Codes: H04M 1/72403 with means for local support of applications that increase the functionality
• CPC Class Codes: H04M 1/72484 wherein functions are triggered by incoming communication events

Abstract

Systems and methods for providing a custom application container for a mobile operating system are provided herein. A container that encapsulates an application layer of a mobile operating system can be provided. Thus, the container can include all applications that reside in the application layer and operate as a proxy for system calls issued by the applications to the mobile operating system. In particular, the container can intercept core service request and forward those requests to pluggable extensions relating to a core service requested by the core service request.

Claims

1. A system that utilizes a custom container, comprising:

a mobile device including a processor that executes the following computer executable components stored in a memory;

a container component that provides a container that encapsulates an application layer of a mobile operating system and interfaces to the mobile operating system, the container including;

a receiving component that receives a core service request to access a core service of the mobile operating system from an application included in the container; and

a selection component that selects an extension associated with the core service request and routes the core service request to the extension.

2. The system of claim 1, wherein the core service relates to at least one of a filesystem for the mobile operating system, network connectivity associated with the mobile operating system, a dialer for the mobile operating system, a short message service (SMS) for the mobile operating system, authentication or identity management for the mobile operating system, device management associated with the mobile operating system, or a contacts data provider.

3. The system of claim 1, wherein the extension virtualizes a core service associated with the core service request.

4. The system of claim 1, wherein the selection component selects the extension based upon a policy included in the container.

5. The system of claim 4, further comprising a customization component that can configure the policy based upon input.

6. The system of claim 5, wherein the input is received from at least one of a service provider, a company administrator, the mobile device, or a user of the mobile device.

7. The system of claim 1, the mobile device further comprising multiple personas, wherein a persona from among the multiple personas represents an operating environment for a contextual role associated with one or more users of the mobile device.

8. The system of claim 7, wherein the container component provides a distinct container for respective personas included in the mobile device.

9. A method for providing a custom container, comprising:

constructing, in a mobile device, a container that encapsulates an application layer of a mobile operating system;

receiving a core service request to access a core service of the mobile operating system from an application included in the container;

selecting an extension associated with the core service request; and

routing the core service request to the extension.

10. The method of claim 9, wherein the selecting an extension relates to selecting the extension from among multiple extensions that virtualize a core service associated with the core service request.

11. The method of claim 9, wherein the core service that is virtualized by the multiple extensions is at elast one of a filesystem for the mobile operating system, network connectivity associated with the mobile operating system, a dialer for the mobile operating system, a short message service (SMS) for the mobile operating system, authentication or identity management for the mobile operating system, device management associated with the mobile operating system, or a contacts data provider.

12. The method of claim 9, wherein the selecting an extension is based upon a policy.

13. The method of claim 12, further comprising configuring the policy based upon input received by the container.

14. The method of claim 13, further comprising receiving the input from at least one of a service provider, a company administrator, the mobile device, or a user of the mobile device.

15. A system for providing a custom container, comprising:

means for constructing, in a mobile device, a container that encapsulates an application layer of a mobile operating system;

means for receiving a core service request to access a core service of the mobile operating system from an application included in the container;

means for selecting an extension associated with the core service request; and

means for routing the core service request to the extension.

16. The system of claim 15, wherein the means for selecting an extension relates to selecting the extension from among multiple extensions that virtualize a core service associated with the core service request.

17. The method of claim 16, wherein the core service that is virtualized by the multiple extensions is at elast one of a filesystem for the mobile operating system, network connectivity associated with the mobile operating system, a dialer for the mobile operating system, a short message service (SMS) for the mobile operating system, authentication or identity management for the mobile operating system, device management associated with the mobile operating system, or a contacts data provider.

18. The method of claim 15, wherein the means for selecting an extension is based upon a policy.

19. The method of claim 18, further comprising means for configuring the policy based upon input received by the container.

20. The method of claim 19, further comprising means for receiving the input from at least one of a service provider, a company administrator, the mobile device, or a user of the mobile device.