IPC communication method

Abstract

The invention provides an IPC communication method, which comprises the following steps: a RPC interface is respectively bound according to standard interfaces of communication interfaces among modules, and the integration of a Binder calling framework layer and an Adaptive AUTOSAR standard interface is completed; and the RPC layer analyzes the protocol data after receiving the protocol data reported by the transmission layer, and distributes the data to different inter-module communication interfaces according to different protocol instructions. A better communication basis is provided for service-oriented communication and an SOA design concept; the solution of communication layer design and AP platform inter-process communication is more optimized, and communication between internal processes is simplified.

Description

technical field [0001] The invention relates to a novel IPC communication method, in particular to a novel IPC communication method based on Binder and AdaptiveATUOSAR standards. Background technique [0002] AUTOSAR is the automotive open system architecture. It mainly provides high-performance computing and communication mechanisms, and provides flexible software configuration. It is born in response to the future development of automotive electrification, networking, and intelligence. AP (Adaptive Platform) needs to be used as middleware. Support various complex application scenarios of autonomous driving, support communication between various application software modules and scheduling of system resources. [0003] As a conceptual specification, AP AUTOSAR only defines a series of standardized interfaces in its implementation, and there is no specific implementation of the underlying process, so it leaves a lot of free space for the implementation of the underlying proje...

AI Technical Summary

Problems solved by technology

[0003] As a conceptual specification, AP AUTOSAR only defines a series of standardized interfaces in its implementation, and there is no specific implementation of the underlying process, so it leaves a lot of free space for the implementation of the underlying project. Among them, the inter-process communication mechanism is very important for supporting the AP software architecture. Crucially, AP AUTOSAR provides a standardized inter-process or inter-module communication interface ARA::COM definition, including distributed service-oriented communication SOMEIP / DDS and local inter-process communication IPC, where SOMEIP / DDS is mainly used for distributed If the network-based service-oriented communication is used for local inter-process communication, the inter-process IPC mechanism provided by the platform system will be used, and the real-time performance and efficiency will be higher than those based on the network, realizing the local IPC communication. There are also many methods. The traditional IPC mechanisms include: pipelines, message queues, shared memory, sockets, signals, semaphores, etc., but these mechanisms have certain shortcomings.

Pipeline; information is copied twice, and a page-sized memory is allocated at creation time, and the size of the buffer area is relatively limited; message queue: information is copied twice, additional CPU consumption; not suitable for frequent or large-scale communication; shared memory: no need Copying, the shared buffer is directly attached to the virtual address space of the process, which is fast, but issues such as synchronization between processes and parameter transfer require multiple mechanisms to cooperate, and the control mechanism is complicated; socket: information is copied twice, as a more general Interface, low transmission efficiency, mainly used for communication between machines or across networks; semaphore: often used as a lock mechanism, mainly as a means of synchronization between processes and different threads in the same process; signal: not suitable for information Exchange, suitable for process interruption control, such as illegal memory access, killing a process, etc.

[0004] As can be seen from the above, since none of the traditional IPC (InterProcess Communication, inter-process communication) mechanisms can achieve a good balance in terms of transmission performance, stability, security, and language implementation, Binder is born with, in particular, traditional IPC There is also no layered software architecture and calling framework, and natively cannot provide support for the SOA concept and service-oriented communication of the AP AUTOSAR platform. That is to say, the traditional IPC does not naturally have the excellent ability to adapt to the AP AUTOSAR platform.

Images