Cross-Environment Communication Framework

• US 20120084791A1
• Filed: 08/24/2011
• Published: 04/05/2012
• Est. Priority Date: 10/01/2010
• Status: Active Grant

• Current Assignee: Z124 LLC (Flexis)
• Original Assignee: IMERJ LLC (Flex, Ltd.)
• Inventors: Chincisan, Octavian, Hancila, Cristian, Benedek, Laszlo Csaba, Russello, Anthony
• Granted Patent: US 9,098,437 B2
• Time in Patent Office: Days
• US Class Current: 719/313
• CPC Class Codes: G06F 13/14 Handling requests for interconnection or transfer
• CPC Class Codes: G06F 13/4068 Electrical coupling
• CPC Class Codes: G06F 13/4282 on a serial bus, e.g. I2C bus, SPI bus on daisy chain buses G06F13/4247
• CPC Class Codes: G06F 2009/45575 Starting, stopping, suspending or resuming virtual machine instances
• CPC Class Codes: G06F 9/4411 Configuring for operating with peripheral devices; Loading of device drivers
• CPC Class Codes: G06F 9/4418 Suspend and resume; Hibernate and awake
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files
• CPC Class Codes: G06F 9/45533 Hypervisors; Virtual machine monitors
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications

Abstract

A mobile computing device with a mobile operating system and desktop operating system running concurrently and independently on a shared kernel without virtualization. The mobile operating system provides a user experience for the mobile computing device that suits the mobile environment. The desktop operating system provides a full desktop user experience when the mobile computing device is docked to a secondary terminal environment. Applications of the desktop operating system communicate with applications and services of the mobile operating system through a cross-environment communication framework. The cross-environment communication framework may include interfaces to remotable objects allowing processes in the mobile operating system and processes in the desktop operating system to share memory in a thread-safe manner. The mobile computing device may be a smartphone running the Android mobile operating system and a full desktop Linux distribution on a modified Android kernel.

Claims

1. A method for communicating between a service of a mobile operating system and an application of a desktop operating system over an inter-process communication channel, the method comprising:

requesting, by the application of the desktop operating system, to bind to a remotable interface of the service of the mobile operating system;

receiving, by the application of the desktop operating system, a remotable object from the service of the mobile operating system, the remotable object instantiated by the service of the mobile operating system in response to the request by the desktop operating system;

sending, by the application of the desktop operating system, a call to the remotable object; and

receiving, by the application of the desktop operating system, a return from the call to the remotable object from the service of the mobile operating system.

2. The method of claim 1, wherein the mobile operating system and the desktop operating system run concurrently on a shared kernel.

3. The method of claim 2, wherein an inter-process communication driver of the shared kernel marshals the first parcel object to the process space of the service of the mobile operating system.

4. The method of claim 3, wherein the desktop operating system includes an inter-process communication library of the mobile operating system compiled against user libraries of the desktop operating system, the inter-process communication library comprising base classes for the remotable object.

5. The method of claim 1, wherein the call to the remotable object includes a first parcel object.

6. The method of claim 1, wherein the call to the remotable object includes an action to be performed by the service of the mobile operating system.

7. The method of claim 6, wherein the mobile operating system returns a second parcel object after performing the action of the call to the remotable object.

8. The method of claim 1, wherein the call to the remotable object includes a reference to a shared memory space.

9. The method of claim 1, wherein the call to the remotable object includes a file descriptor.

10. A method for communicating between a first application of a mobile operating system and a second application of a desktop operating system, the method comprising:

receiving, by a remote communication service of the mobile operating system, a request by the first application to bind to the remote communication service;

instantiating, in response to the request by the first application, a remotable object;

passing the remotable object from the remote communication service to the first application;

receiving, by the remote communication service of the mobile operating system, a request by the second application to bind to the remote communication service through an inter-process communication channel; and

passing the remotable object from the remote communication service to the second application.

11. The method of claim 10, wherein the mobile operating system and the desktop operating system run concurrently on a shared kernel.

12. The method of claim 10, further comprising the steps of:

receiving, by the remote communication service of the mobile operating system, a call to the remotable object from the first application, the call including a first parcel object.

13. The method of claim 12, wherein the call to the remotable object comprises a synchronous call.

14. The method of claim 12, wherein the call to the remotable object comprises an asynchronous call.

15. The method of claim 12, further comprising the steps of:

returning, by the remote communication service of the mobile operating system, a second parcel object in response to receiving the call to the remotable object.

16. The method of claim 12, wherein the first parcel object includes a reference to a shared memory space.

A mobile computing device including a computer readable medium storing instructions for a physical processor, the instructions, when executed, causing the processor to perform steps comprising:

receiving, by a service of a mobile operating system, a request to bind to the service by an application of a desktop operating system;

instantiating, by the service of the mobile operating system, a remotable object in response to the request to bind to the service by the application of the desktop operating system;

sending, by the service of the mobile operating system, the remotable object through an inter-process communication channel to the application of the desktop operating system;

receiving, by the service of the mobile operating system, a call to the remotable object by the application of the desktop operating system, the call to the remotable object including an action to be performed by the service; and

returning, from the service of the mobile operating system, a reference to the remotable object in response to receiving the call to the remotable object.

17. The mobile computing device of claim 17, wherein the instructions, when executed, further cause the processor to perform steps comprising:

running the mobile operating system in a first execution environment on a shared kernel; and

concurrently running the desktop operating system in a second execution environment on the shared kernel;

18. The mobile computing device of claim 17, wherein the action includes invoking a remotable method of the service.

19. The mobile computing device of claim 17, wherein the service is a bound service.