Qualcomm DIAG Module Pseudo Packet Conversion for Data Sync
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data synchronization software for Qualcomm platform terminals is not well-defined, leading to high code coupling and making it difficult to extend new functions, with a mixed development mode and high risk of faults during the synchronization process.
Innovation Solution
A method and system that involves a DIAG module converting request and response packets into pseudo packets for processing by an application layer module via an OEM layer module, using serial port communication to reduce code coupling and improve clarity, allowing for easier extension of functions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the DIAG module and application layer are mixed together in the same development mode, then data synchronization can be achieved, but code coupling degree becomes extremely high and fault avoidance becomes difficult
Solution Approach 1:
The patent segments the data synchronization system into three distinct modules: DIAG module (bottom layer), OEM layer module (intermediate layer), and application layer module (upper layer). Each module has clearly defined responsibilities and interfaces, separating the previously mixed DIAG module and application layer code into independent, loosely-coupled components that can be developed, tested, and maintained separately, thereby reducing code coupling degree and improving fault avoidance.
Solution Approach 2:
The patent introduces an intermediate OEM layer module that acts as a mediator between the DIAG module and the application layer module. This intermediate layer handles packet forwarding and coordination, allowing the bottom layer and application layer to interact through well-defined interfaces without direct coupling, thus reducing code coupling degree while maintaining system reliability.
2Adaptability or versatility
If the DIAG module processes all packets directly, then data synchronization works, but it is inconvenient for extension of new functions
Solution Approach 1:
The patent segments the packet processing functionality across multiple layers: the DIAG module handles protocol-level processing, the OEM layer handles intermediate coordination, and the application layer module handles specific application logic. This segmentation allows new functions to be extended in the application layer without modifying the bottom layer, improving adaptability while maintaining clear development modes at each layer.
Solution Approach 2:
The patent adds a dimensional separation by introducing the intermediate OEM layer and organizing processing logic across multiple abstraction layers rather than in a single monolithic structure. This multi-dimensional organization allows new functions to be added at different layers independently, enhancing versatility while keeping each layer's complexity manageable and development modes clear.
Data Source
AI summary
The present disclosure discloses a method for synchronizing data between a Qualcomm platform terminal and a Personal Computer (PC) side, which comprises the following steps: the DIAG module of the Qualcomm platform terminal receives a request packet from the PC side, converts the request packet into a pseudo request packet, and transmits the pseudo request packet to an application layer module of the Qualcomm platform terminal via an Original Equipment Manufacturer (OEM) layer module of the Qualcomm platform terminal; the application layer module fills a pseudo response packet according to the pseudo request packet transmitted from the OEM layer module and then transmits the pseudo response packet to the DIAG module via the OEM layer module; and the DIAG module converts the pseudo response packet transmitted from the OEM layer module into a real response packet and then transmits the real response packet to the PC side. The present disclosure also discloses a system for synchronizing data between a Qualcomm platform terminal and a PC side. In the present disclosure, the implementations of a bottom layer and an application layer are not mixed together any more, which reduces code coupling degree, avoids the occurrence of a fault in a data synchronization process and facilitate the extension of new functions.