Cross-Device IPC for Isolated Mobile Service Components
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing mobile devices isolate applications in separate containers, limiting inter-process communication (IPC) to a single device, preventing seamless access to services across multiple devices without significant programming effort or modification.
Innovation Solution
Implementing an inter-device IPC mechanism that extends existing intra-device IPC by using pseudo-tokens and pseudo-handlers, enabling transparent access to services across devices within a cluster group through communication service gateways, allowing existing applications to access resources with minimal modification.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If applications are isolated in separate containers for security, then data security and reliability are improved, but inter-process communication across multiple devices is prevented
Solution Approach 1:
The patent introduces a container manager as an intermediary component that mediates between isolated applications and the IPC mechanism. The container manager receives IPC tokens from applications, validates them, and translates them into appropriate access permissions, enabling cross-device communication while maintaining container isolation. This intermediary resolves the contradiction by providing a controlled interface that allows communication without breaking security boundaries.
Solution Approach 2:
The patent extends the traditional single-device IPC architecture to a multi-dimensional cross-device architecture. By introducing device identifiers, container identifiers, and service identifiers as additional dimensions, the system enables IPC tokens to be validated across multiple devices while maintaining the original container isolation model. This dimensional extension allows applications to access services on remote devices without compromising the security model.
2Adaptability or versatility
If IPC mechanism is extended across multiple devices, then service accessibility is improved, but system complexity increases
Solution Approach 1:
The patent implements a universal IPC token validation mechanism that works across multiple devices and container types. The container manager provides multi-functional capabilities by handling token generation, validation, and permission management in a unified manner. This universal approach allows the same IPC infrastructure to serve both intra-device and inter-device communication needs, reducing the need for separate complex systems.
Solution Approach 2:
The patent uses copying of container environment information and service descriptors to enable cross-device IPC. Instead of creating entirely new communication protocols for each device pair, the system copies and adapts existing IPC mechanisms to work across devices. The container manager copies service information from remote devices and presents it through the local IPC interface, simplifying the overall system architecture.
3Adaptability or versatility
If existing applications are modified to support cross-device access, then inter-device IPC capability is improved, but ease of operation deteriorates
Solution Approach 1:
The patent implements a self-service mechanism where the container manager automatically handles cross-device IPC setup and token management. Applications can request cross-device service access using standard IPC calls, and the container manager automatically manages the complexity of cross-device communication, including token validation and permission checking. This self-service approach allows applications to benefit from cross-device capability without requiring developers to understand or implement the underlying complexity.
Data Source
AI summary
A mobile device implements an inter-device inter-process communication (IPC) mechanism by which services on each device in a cluster group may be accessed by other devices in the cluster group using intra-device IPC calls. The inter-device IPC mechanism extends the existing intra-device IPC mechanism so that it may be used by existing applications across devices in the cluster group with little or no modification to the applications. A mobile device establishes pseudo-tokens for objects on the mobile device and pseudo-handlers for objects on the other devices. A mobile device may access multiple objects on other devices and may provide multiple other devices with access to a local object. Each object accessed via an inter-device IPC call is associated with a respective service adapter in a respective communication service gateway of each of the participating devices.