Android IPC Service Mediator for Application Communication

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current inter-process communication methods on Android systems, such as the Binder and SOCKET mechanisms, are inadequate for creating system-level applications with unique characteristics, leading to tight coupling, low transmission efficiency, and difficulties in integrating third-party applications, which impedes software development and user experience.

Innovation Solution

An inter-process communication method based on an application layer where frame encapsulation applications are created as clients and a daemon process IPC Service is used as a server, allowing applications to register and communicate through a virtualized service, enabling simpler and more efficient communication among system-level and user applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the SOCKET mechanism is used for inter-process communication, then module coupling is reduced and independent modules can implement independent resource interfaces, but transmission efficiency decreases and system complexity increases due to port number management requirements

Engineering Contradiction:

Improvemodule independenceVSAvoidtransmission efficiency

Core Design Contradiction:

Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent introduces an IPC Service as an intermediary component that mediates communication between applications. The IPC Service manages port number allocation and routing, acting as a mediator that reduces the communication overhead between modules while maintaining the benefits of reduced coupling. This resolves the contradiction by providing efficient routed communication without requiring direct port management between all application pairs.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Productivity

If the Binder mechanism is used for inter-process communication, then real-time communication among multiple processes is improved, but system coupling becomes excessively tight and system reliability decreases

Engineering Contradiction:

Improvereal-time communication efficiencyVSAvoidsystem reliability

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The patent segments the communication architecture by introducing the IPC Service as a separate layer between applications and the Binder mechanism. This segmentation isolates applications from direct dependencies on the Binder service, so that when the Binder service fails, individual applications can be restarted without bringing down the entire system. This resolves the reliability issue while maintaining real-time communication capabilities through the segmented architecture.

Inventive Principle:

Principle #1Segmentation

3Adaptability or versatility

If third-party applications are integrated using the SOCKET mechanism, then application functionality is extended, but port number assignment becomes complex and development difficulty increases

Engineering Contradiction:

Improveapplication integration capabilityVSAvoidsoftware development ease

Core Design Contradiction:

Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The IPC Service implements self-service functionality by automatically allocating port numbers to applications upon registration. Third-party applications simply register with the IPC Service without needing to manually request or manage port numbers. The IPC Service autonomously handles port assignment and configuration, resolving the development complexity while maintaining integration capability.

Inventive Principle:

Principle #25Self-service

4Adaptability or versatility

If system applications need to communicate with third-party applications using SOCKET mechanism, then communication flexibility is achieved, but system applications need to obtain port numbers which impedes software platform development

Engineering Contradiction:

Improvecommunication flexibilityVSAvoidport number management complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The IPC Service acts as an intermediary that abstracts away port number management from both system and third-party applications. Applications communicate with the IPC Service using simplified interfaces, and the IPC Service handles the complex port number routing and management in the background. This resolves the contradiction by providing communication flexibility through the intermediary while hiding the port management complexity.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS9923992B2Inter-process communication method based on application layer of android and basic application communication system

Publication Date: 2018.03.20 SHENZHEN SKYWORTH RGB ELECTRONICS CO LTD

AI summary

Disclosed in the present invention are an inter-process communication method based on an application layer of Android and a basic application communication system. In accordance with a client/server communication mode, frame encapsulation applications for the mutual communication between system-level applications and user applications are created and virtualized as a client side; a daemon process IPC Service is created and virtualized as a server side; registration and binding of the IPC Service are completed through the applications, so as to achieve mutual communication among every application. Through the adoption of the technical solution of the present invention, a special communication mechanism can be rapidly and safely built during the inter-process communication of every application.