Linux Protocol Stack Data Transmission via Intermediate Service Module
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing protocol stack systems for Linux-based systems face challenges in ensuring seamless data transmission between the protocol stack and driver chip controllers, particularly across different Bluetooth chips, leading to compatibility issues and difficulties in data exchange.
Innovation Solution
A method is introduced where an intermediate service module is interposed between the protocol stack and the driver chip controller, utilizing specific interface functions to facilitate data transmission through IPC communication via HIDL, enabling bidirectional data exchange and improving driver compatibility by pre-registering VHCI and hwbinder nodes in the kernel.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If an intermediate service module is introduced between the protocol stack and driver chip controller, then data transmission compatibility is improved, but system complexity increases
Solution Approach 1:
An intermediate service module is introduced between the protocol stack and driver chip controller to facilitate data transmission. This mediator handles the communication protocol conversion and data format transformation, enabling compatible data exchange between different Bluetooth chip controllers and the protocol stack without requiring direct integration.
2Adaptability or versatility
If bidirectional data transmission is implemented through IPC communication, then data exchange capability is improved, but communication overhead increases
Solution Approach 1:
The patent replaces direct memory-to-memory data copying with IPC (Inter-Process Communication) mechanism. The intermediate service module uses standardized IPC calls to transmit data between the protocol stack and driver chip controller, enabling bidirectional communication while maintaining clean process boundaries and improved modularity.
3Adaptability or versatility
If VHCI and hwbinder nodes are pre-registered in the kernel, then driver compatibility is improved, but kernel configuration complexity increases
Solution Approach 1:
The VHCI and hwbinder nodes are pre-registered in the kernel before the actual data transmission occurs. This preliminary registration establishes the communication pathways and interface definitions in advance, allowing the intermediate service module to immediately use these pre-configured nodes for data exchange without requiring complex runtime configuration.
Data Source
AI summary
The disclosure provides a method, a computer device and a storage medium for protocol stack data transmission based on Linux® system. The method of the protocol stack data transmission based on Linux® system comprises: a kernel sending a first notification to an intermediate service module in response to the kernel detecting that a protocol stack sends first data to a driver chip controller; wherein the first notification is used to instruct the intermediate service module to receive the first data and forward the first data to the driver chip controller.