Data interaction method and system for radio frequency transceiver

Through protocol type hash recognition and a unified frame structure RF transceiver method, the compatibility and power consumption problems of RF transceivers in multi-protocol hybrid deployment are solved, and efficient and stable data interaction is achieved.

CN120358291BActive Publication Date: 2025-08-15HANGZHOU ZHONGKE YIXIN MICROELECTRONICS TECHNOLOGY CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202510821776.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2025-06-19
Publication Date
2025-08-15
Estimated Expiration
2045-06-19

AI Technical Summary

Technical Problem

When existing RF transceivers support multiple communication protocols, their hardware resource occupancy is high and their protocol switching is complex, and they cannot efficiently support multi-protocol converged communication, resulting in limited terminal resources, sensitive power consumption and frequent timing conflicts.

Method used

The protocol type hash recognition mechanism is adopted to identify protocol types through hash functions, build a unified frame structure and perform security verification, and realize cross-protocol parsing and uploading.

Benefits of technology

It improves the compatibility and resolution efficiency of the RF transceiver, reduces power consumption, and improves the stability and operation efficiency of the system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN120358291B_ABST
    Figure CN120358291B_ABST
Patent Text Reader

Abstract

The present invention relates to the field of Internet of Things data interaction technology, and in particular to a data interaction method and system for a radio frequency transceiver, wherein the method comprises: extracting a leading bit sequence in a wireless data frame and performing protocol identification using a hash function; loading a field parsing state machine according to the protocol type and constructing an original field vector; generating a unified frame structure through a mapping function; performing protocol security verification based on the unified frame structure; and performing interaction adaptation control and frame submission control. Compared with the prior art that is customized for a single protocol or lacks a unified parsing and control mechanism, the technical problem of difficulty in achieving stable and flexible data interaction is particularly addressed in scenarios of Internet of Things terminals that need to support a mixed deployment of multiple protocols such as LoRa, ZigBee, and BLE. The present invention improves the compatibility of radio frequency transceivers by introducing a protocol type hash identification mechanism, unified frame structure semantic mapping, and protocol behavior adaptive scheduling control.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of Internet of Things data interaction, and in particular to a data interaction method and system for a radio frequency transceiver. Background Art

[0002] Currently, low-power IoT terminals are widely used in scenarios such as environmental monitoring, smart agriculture, and intelligent security. They typically need to support multiple communication protocols, such as LoRa, ZigBee, and BLE, to meet diverse communication needs, including long-distance transmission, local area networking, and close-range interaction. However, due to significant differences in the physical layer modulation schemes, frame structures, and security mechanisms of different protocols, existing RF transceivers typically adopt a "single-protocol-dedicated" or "multiple-protocol parallel independent processing" approach. This results in high hardware resource utilization, complex protocol switching, and inconsistent data structures, making it difficult to efficiently support multi-protocol converged communications. For example, in existing technologies, the preamble, MHDR, and MIC fields in the LoRa frame structure cannot be directly adapted to the field semantics of ZigBee or BLE. Upper-layer applications must process data from each protocol separately, increasing parsing complexity and communication power consumption. In resource-constrained terminals, frequent switching between protocols can also cause timing conflicts and energy waste. Existing technologies cannot fully meet the converged communication requirements of dynamic multi-protocol perception, parsing consistency, and energy constraints. Therefore, there is an urgent need for a radio frequency data transmission and reception interaction method that can still achieve structured parsing, security verification and unified upload of multiple communication protocol data frames under the conditions of limited terminal resources and power consumption sensitivity, so as to improve the system's compatibility, parsing efficiency and operating energy efficiency. Summary of the Invention

[0003] In response to the above-mentioned technical deficiencies, the purpose of the present invention is to propose a data interaction method for a radio frequency transceiver, aiming to solve the technical problem that the existing technology is customized for a single protocol or lacks a unified parsing and control mechanism, especially in the IoT terminal scenario where it is necessary to support a mixed deployment of multiple protocols such as LoRa, ZigBee, and BLE, making it difficult to achieve stable and flexible data interaction.

[0004] In order to solve the above technical problems, the present invention adopts the following technical solution: The present invention provides a data interaction method of a radio frequency transceiver.

[0005] The data interaction method of the radio frequency transceiver includes:

[0006] Step S10: After the receiving path of the radio frequency transceiver terminal receives the wireless data frame, the leading bit sequence B[0:k] of the first k bits used for protocol identification in the wireless data frame is extracted, and the protocol candidate index value is calculated based on the leading bit sequence B[0:k] using a preset hash function H(·) , according to the candidate index value of the protocol Search for matching items in the pre-set protocol mapping table and output the protocol type P;

[0007] Step S20: Load the field parsing finite state machine corresponding to the protocol according to the protocol type P , and generate a field list , according to the field list Sequentially extract the protocol fields and construct the protocol original field vector ;

[0008] Step S30: Using a preset mapping function The protocol raw field vector Mapped to a unified abstract frame structure to obtain a protocol-independent unified data frame object ;

[0009] Step S40: Unify the data frame object according to the protocol type P Perform protocol security verification based on

[0010] Step S50: After the protocol security verification is passed, interactive adaptation control and frame submission control are executed to obtain cross-protocol parsing data, and the cross-protocol parsing data is adaptively uploaded to the corresponding business layer.

[0011] Preferably, in step S10, the preset hash function H(·) includes CRC-16, BKDR Hash, JenkinsHash or FNV-1a function, which is used to adapt to the real-time protocol identification requirements of low-power embedded devices; the output protocol type P ∈ {LoRa, ZigBee, BLE}, where LoRa is a long-distance, low-rate communication protocol based on spread spectrum modulation, ZigBee is a low-power, short-distance communication protocol that supports networking and confirmation mechanisms, and BLE is a short-range Bluetooth communication protocol.

[0012] Preferably, in step S20, the field list The formula is: ,in, For the protocol type P Valid fields, including AdvA of BLE protocol, SrcAddr of ZigBee protocol and DevAddr of LoRa protocol, The total number of valid fields in the protocol type P; field parsing finite state machine Used to support the state jump of optional fields, variable-length fields and nested fields in protocol type P; protocol original field vector It includes address field vector, frame control field vector, payload field vector, frame check code field vector and special field vector.

[0013] Preferably, in step S30, the data frame object is unified The formula is: ,in, To unify the length of the data frame object; It is a standard field in a unified frame, including source node address, frame type field, payload field and security check field; mapping function Used to perform field renaming, zero padding, and word length alignment operations.

[0014] Preferably, in step S40, according to the protocol type P, the unified data frame object The steps for performing protocol security verification based on the protocol include:

[0015] Unified DataFrame Object The formula is: ,in, To unify the length of the data frame object; It is a standard field in a unified frame, including the source node address, frame type field, payload field, and security check field;

[0016] According to the unified data frame object The security verification field in the protocol type P calls the security verification function Verify P ( ), calculate the security verification result flag , ;

[0017] When the security verification result flag = 1, the protocol security verification is judged to be passed, otherwise it is judged to be failed.

[0018] Preferably, in step S50, after the protocol security verification is passed, the steps of executing interactive adaptation control and frame submission control to obtain cross-protocol parsing data specifically include:

[0019] According to the protocol type , call the behavior adaptation function to generate the processing action identifier of the current data frame , ,in, Used to indicate , execute ACK frame response and set retransmission window; Used to indicate ,Based on the connection status maintenance, the data is buffered into the GATT queue and waited for the business layer to pull; Used to indicate Skip the feedback process and schedule to sleep;

[0020] The processing action identifier when generating the current data frame After that, calculate the protocol switching cost function , and switch the cost function according to the protocol Determine whether to perform cross-protocol forwarding processing; wherein, ,in, For the slave agreement Switch to Protocol The energy consumed, For the slave agreement Switch to Protocol The time consumed, For the slave agreement Switch to Protocol Delay weight factor of the switching process;

[0021] Preset cost threshold ,like , it enters the protocol forwarding buffer queue, suspends forwarding, and waits for the scheduling window to be reallocated. Otherwise, cross-protocol forwarding processing is executed immediately to obtain cross-protocol parsed data.

[0022] Preferably, in step S50, the step of adaptively uploading the cross-protocol parsed data to the corresponding business layer specifically includes:

[0023] Get the protocol type P from the cross-protocol parsing data; if LoRa, upload cross-protocol parsing data to the remote MQTT / HTTP gateway; if ZigBee, forwards cross-protocol parsed data to the coordinator; if BLE, sends BLE attribute notifications to mobile terminals through preset GATT services;

[0024] After uploading, the execution will return to receive the feedback content and decide whether to clear the buffer or start the protocol reset based on the feedback content.

[0025] The present invention also provides a data interaction system of a radio frequency transceiver, comprising:

[0026] The protocol identification module is used to extract the leading bit sequence B[0:k] of the first k bits used for protocol identification in the wireless data frame after the wireless data frame is received by the receiving path of the radio frequency transceiver terminal, and calculate the protocol candidate index value based on the leading bit sequence B[0:k] using a preset hash function H(·) , according to the candidate index value of the protocol Search for matching items in the pre-set protocol mapping table and output the protocol type P;

[0027] Field parsing module, used to load the field parsing finite state machine corresponding to the protocol type P , and generate a field list , according to the field list Extract the protocol fields sequentially and construct the protocol original field vector ;

[0028] Field mapping module, used to pass preset mapping functions The protocol raw field vector Mapped to a unified abstract frame structure to obtain a protocol-independent unified data frame object ;

[0029] Protocol verification module, used to unify data frame objects according to protocol type P Perform protocol security verification based on

[0030] The interaction and submission module is used to perform interaction adaptation control and frame submission control after the protocol security verification is passed, obtain cross-protocol parsing data, and adaptively upload the cross-protocol parsing data to the corresponding business layer.

[0031] The present invention also provides a data interaction device for a radio frequency transceiver, comprising: a memory, a processor, and a data interaction program for the radio frequency transceiver stored in the memory and runnable on the processor. When the data interaction program for the radio frequency transceiver is executed by the processor, a data interaction method for the radio frequency transceiver is implemented.

[0032] The present invention also provides a computer program product, including a data interaction program for a radio frequency transceiver, wherein the data interaction program for the radio frequency transceiver implements the data interaction method for the radio frequency transceiver when executed by a processor.

[0033] The beneficial effects of the present invention are: compared with the existing technology that is customized for a single protocol or lacks a unified parsing and control mechanism, especially in the IoT terminal scenario where multiple protocols such as LoRa, ZigBee, BLE need to be supported, the technical problem of difficulty in achieving stable and flexible data interaction is solved. The present invention improves the compatibility of RF transmission and reception by introducing a protocol type hash identification mechanism, a unified frame structure semantic mapping, and protocol behavior adaptive scheduling control. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0035] Figure 1 The present invention is a flow chart of a data interaction method of a radio frequency transceiver.

[0036] Figure 2 The present invention is a structural diagram of a data interaction device of a radio frequency transceiver. DETAILED DESCRIPTION

[0037] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of the present invention.

[0038] Example 1: Figure 1 FIG. 1 is a flow chart of a data interaction method for a radio frequency transceiver according to the present invention, and provides a first embodiment of a data interaction method for a radio frequency transceiver according to the present invention.

[0039] In the first embodiment, the data interaction method of the radio frequency transceiver includes:

[0040] Step S10: After the receiving path of the radio frequency transceiver terminal receives the wireless data frame, the leading bit sequence B[0:k] of the first k bits used for protocol identification in the wireless data frame is extracted, and the protocol candidate index value is calculated based on the leading bit sequence B[0:k] using a preset hash function H(·) , according to the candidate index value of the protocol Search for matching items in the pre-set protocol mapping table and output the protocol type P;

[0041] It should be noted that in step S10, the preset hash function H(·) includes CRC-16, BKDR Hash, Jenkins Hash or FNV-1a function, which is used to adapt to the real-time protocol identification requirements of low-power embedded devices; the output protocol type P ∈ {LoRa, ZigBee, BLE}, where LoRa is a long-distance, low-rate communication protocol based on spread spectrum modulation, ZigBee is a low-power, short-distance communication protocol that supports networking and confirmation mechanisms, and BLE is a short-range Bluetooth communication protocol.

[0042] It can be understood that the hash function recognition mechanism effectively avoids the parsing delay caused by serial decoding of each protocol frame header through compression calculation and index matching, improves the terminal's recognition speed and resource utilization efficiency for multiple wireless protocol frames, and is suitable for IoT scenarios that require rapid judgment of protocol types and switching of working modes.

[0043] It should be understood that although the protocol set in this embodiment is {LoRa, ZigBee, BLE}, the protocol identification mechanism is not limited to these three types of protocols, but can also be extended to other low-power communication protocols with distinguishable frame header features, such as NB-IoT, Thread or UWB protocols, by simply adding corresponding hash features in the protocol mapping table.

[0044] For example, in a type of remote environmental monitoring terminal, the device periodically reports sensor data through the LoRa protocol by default. When on-site maintenance personnel approach with a BLE controller, the device can identify the BLE broadcast frame and switch the communication mode in milliseconds, automatically entering the local configuration channel, thereby achieving seamless switching between remote reporting and near-field maintenance, significantly improving system intelligence and user operation experience.

[0045] Step S20: Load the field parsing finite state machine corresponding to the protocol according to the protocol type P , and generate a field list , according to the field list Extract the protocol fields sequentially and construct the protocol original field vector ;

[0046] It should be noted that in step S20, the field list The formula is: ,in, For the protocol type P Valid fields, including AdvA of BLE protocol, SrcAddr of ZigBee protocol and DevAddr of LoRa protocol, The total number of valid fields in the protocol type P; field parsing finite state machine Used to support the state jump of optional fields, variable-length fields and nested fields in protocol type P; protocol original field vector It includes address field vector, frame control field vector, payload field vector, frame check code field vector and special field vector.

[0047] It can be understood that the field extraction mechanism based on the finite state machine can effectively be compatible with the problems of variable field length, different field order and inconsistent field type in different communication protocols, thereby improving the flexibility and versatility of the data decoding process and reducing the coupling of the parsing code and the complexity of protocol switching.

[0048] It should be understood that the construction method of the state list FSM(P) is not only applicable to protocols with fixed or semi-fixed frame structures such as BLE, ZigBee, and LoRa, but also to subsequent protocols that support extended fields or optional parameter structures, such as NB-IoT, Wi-SUN, or Thread protocols, which can be adapted by simply extending the state transition description.

[0049] For example, in an intelligent traffic monitoring device, the terminal uploads road condition data over a long period of time via the LoRa protocol by default. When entering a high-density urban area, it automatically identifies and switches to the ZigBee network structure. Under the control of the FSM(P), it quickly extracts the SrcAddr and MAC Payload fields, completes scenario-adaptive communication switching, and ensures the correct parsing and reporting of protocol fields.

[0050] Step S30: Using a preset mapping function The protocol raw field vector Mapped to a unified abstract frame structure to obtain a protocol-independent unified data frame object ;

[0051] It should be noted that, in step S30, the unified data frame object The formula is: ,in, To unify the length of the data frame object; It is a standard field in a unified frame, including source node address, frame type field, payload field and security check field; mapping function Used to perform field renaming, zero padding, and word length alignment operations.

[0052] It is understandable that the mapping function In the process of implementing protocol field vector format conversion, the processing consistency of different protocol frame structures in the same terminal is significantly improved through field semantic alignment, bit width unification and naming standardization operations, avoiding logical branches and redundant parsing code caused by differences in field structures in upper-layer business processing.

[0053] It should be understood that the unified data frame object The abstract structure is not only applicable to common protocols such as LoRa, ZigBee, and BLE, but its field set has good versatility and can be extended to wireless protocols with similar frame semantic structures, including UWB and NB-IoT, thereby improving maintainability and protocol expansion capabilities.

[0054] For example, in a smart meter terminal, if the device needs to support both local networking based on ZigBee and remote upload communication based on LoRa, this method can be used to map the function The SrcAddr in ZigBee and the DevAddr in LoRa are uniformly mapped into a unified frame field, so that the upper-layer metering system only needs to process standardized fields and does not need to be aware of the differences in the underlying communication protocols, thereby improving integration efficiency and protocol decoupling capabilities.

[0055] Step S40: Unify the data frame object according to the protocol type P Perform protocol security verification based on

[0056] It should be noted that in step S40, according to the protocol type P, the unified data frame object Based on the steps of performing protocol security verification, specifically including: unifying data frame objects The formula is: ,in, To unify the length of the data frame object; It is a standard field in the unified frame, including the source node address, frame type field, payload field and security check field; according to the unified data frame object The security verification field in the protocol type P calls the security verification function Verify P ( ), calculate the security verification result flag , ; When the security verification result flag = 1, the protocol security verification is judged to be passed, otherwise it is judged to be failed.

[0057] As can be understood, this solution maps multi-protocol security fields to standard locations in a unified frame structure, enabling security verification functions to process data frames from different protocols using a consistent input format. This avoids the cumbersome process of setting up separate security verification entry points, parsing paths, and field offsets for each protocol, as is traditionally done. This unified verification mechanism can significantly reduce code redundancy, instruction cache switching, and operating power consumption, particularly in resource-constrained, low-power devices that require dynamic protocol switching, thereby improving system responsiveness and stability after protocol switching.

[0058] It should be understood that although this embodiment takes the three mainstream protocols of LoRa (MIC), ZigBee (FCS), and BLE (CRC) as examples, the unified frame structure and abstract verification mechanism can be applied to other communication protocols that support tail check bits or embedded authentication mechanisms, such as Thread, NB-IoT, UWB, etc., and have good adaptability and scalability.

[0059] For example, in one type of smart meter reading terminal, the device uses the LoRa protocol to upload electricity usage data during daily operation, but temporarily switches to BLE connection mode for local configuration when maintenance personnel approach. The unified security verification mechanism described in this invention reuses the same verification module during protocol switching to verify the consistency of data from different protocols, eliminating the need to dynamically switch decoding logic or load different protocol drivers. This achieves the goal of "unified security policy + fast switching + energy-saving operation."

[0060] Step S50: After the protocol security verification is passed, interactive adaptation control and frame submission control are executed to obtain cross-protocol parsing data, and the cross-protocol parsing data is adaptively uploaded to the corresponding business layer.

[0061] It should be noted that in step S50, after the protocol security verification is passed, the interactive adaptation control and frame submission control are executed to obtain the cross-protocol parsing data, which specifically includes: , call the behavior adaptation function to generate the processing action identifier of the current data frame , ,in, Used to indicate , execute ACK frame response and set retransmission window; Used to indicate ,Based on the connection status maintenance, the data is buffered into the GATT queue and waited for the business layer to pull; Used to indicate Skip the feedback process and schedule to enter sleep mode; generate the processing action identifier of the current data frame After that, calculate the protocol switching cost function , and switch the cost function according to the protocol Determine whether to perform cross-protocol forwarding processing; wherein, ,in, For the slave agreement Switch to Protocol The energy consumed, For the slave agreement Switch to Protocol The time consumed, For the slave agreement Switch to Protocol Delay weight factor of the switching process; preset cost threshold ,like , then enter the protocol forwarding buffer queue, suspend forwarding, and wait for the scheduling window to be reallocated. Otherwise, cross-protocol forwarding processing is immediately executed to obtain cross-protocol parsing data. In step S50, the step of adaptively uploading the cross-protocol parsing data to the corresponding business layer specifically includes: obtaining the protocol type P from the cross-protocol parsing data; if LoRa, upload cross-protocol parsing data to the remote MQTT / HTTP gateway; if ZigBee, forwards cross-protocol parsed data to the coordinator; if BLE sends BLE attribute notifications to the mobile terminal through the preset GATT service; after uploading, it will return to receive the execution feedback content and decide whether to clear the buffer or initiate a protocol reset based on the feedback content.

[0062] As can be understood, this solution establishes an on-demand dynamic routing mechanism between protocol switching and data reporting by introducing a protocol behavior abstraction function and a cost function evaluation mechanism. This effectively avoids the power consumption and communication conflicts caused by the rigid protocol path switching and indiscriminate forwarding in traditional systems. In particular, in scenarios where low-power IoT devices frequently need to switch between BLE local configuration and LoRa remote reporting, dynamic decisions can be made regarding whether to switch immediately or to delay caching, significantly improving system operating efficiency and power-consumption adaptability.

[0063] For example, in a smart manhole cover monitoring scenario, the terminal defaults to using LoRa for periodic remote data reporting. When maintenance personnel connect to the terminal via BLE on-site via their mobile phone, the system quickly identifies and adapts the protocol, immediately switching to a BLE connection state and buffering the maintenance command into the GATT channel. Once successful, it returns to the LoRa state. Using a cost function to determine whether to immediately switch from BLE to LoRa, the system intelligently selects "upload later" or "forward immediately," thus achieving a cross-protocol, secure, and energy-efficient intelligent interaction process.

[0064] Embodiment 2: Furthermore, the present invention provides a data interaction system for a radio frequency transceiver, which utilizes a data interaction method for a radio frequency transceiver in the aforementioned embodiment, and can solve the technical problem of data interaction for a radio frequency transceiver. Compared to the prior art, the data interaction system for a radio frequency transceiver provided by the present invention has the same beneficial effects as the data interaction method for a radio frequency transceiver provided in the aforementioned embodiment. Other technical features of the data interaction system for a radio frequency transceiver are the same as those disclosed in the aforementioned embodiment and are not further elaborated here.

[0065] Example 3: The present invention provides a data exchange device for a radio frequency transceiver, please refer to Figure 2A data interaction device for a radio frequency transceiver includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the data interaction method for a radio frequency transceiver described in the first embodiment above. The data interaction device for a radio frequency transceiver in the embodiments of the present invention may include, but is not limited to, mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. The data interaction device for a radio frequency transceiver is merely an example and should not limit the functionality or scope of use of the embodiments of the present invention. A data exchange device for a radio frequency transceiver may include a processor 1001 (e.g., a central processing unit (CPU) or graphics processing unit (GPU)). The processor 1001 can perform various appropriate actions and processes based on programs stored in a read-only memory (ROM) 1002 or programs loaded from a storage device 1003 into a random access memory (RAM) 1004. RAM 1004 also stores various programs and data required for the operation of the data exchange device for the radio frequency transceiver. Processor 1001, ROM 1002, and RAM 1004 are interconnected via a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems may be connected to I / O interface 1006: input devices 1007, such as a touch screen, touchpad, keyboard, mouse, image sensor, microphone, accelerometer, gyroscope, etc.; output devices 1008, such as a liquid crystal display (LCD), speaker, vibrator, etc.; storage device 1003, such as a magnetic tape or hard disk; and communication device 1009. The communication device 1009 can allow a data exchange device of a radio frequency transceiver to communicate wirelessly or wired with other devices to exchange data. Although the figure shows a data exchange device of a radio frequency transceiver with various systems, it should be understood that it is not required to implement or have all of the systems shown. More or fewer systems may be implemented or have alternatively.

[0066] Example 4: The present invention also provides a computer program product, including a computer program. When executed by a processor, the computer program implements the steps of the aforementioned method for data interaction between a radio frequency transceiver. The computer program product provided by the present invention can solve the technical problem of data interaction between a radio frequency transceiver. Compared with the prior art, the beneficial effects of the computer program product provided by the present invention are the same as those of the method for data interaction between a radio frequency transceiver provided in the aforementioned embodiment, and are not further elaborated here.

[0067] In particular, according to the embodiments disclosed in the present invention, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, the embodiments disclosed in the present invention include a computer program product comprising a computer program carried on a computer-readable medium, the computer program comprising program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network via a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processor 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present invention are performed.

[0068] It should be understood that the various parts disclosed in the present invention can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in any appropriate manner in any one or more embodiments or examples.

[0069] Obviously, those skilled in the art may make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if such changes and modifications fall within the scope of the claims and their equivalents, the present invention is intended to include such changes and modifications.

Claims

1. A data interaction method for a radio frequency transceiver, characterized in that: Methods include: Step S10: After the receiving path of the radio frequency transceiver terminal receives the wireless data frame, the leading bit sequence B[0:k] of the first k bits used for protocol identification in the wireless data frame is extracted, and the protocol candidate index value is calculated based on the leading bit sequence B[0:k] using a preset hash function H(·) , according to the candidate index value of the protocol Search for matching items in the pre-set protocol mapping table and output the protocol type P; Step S20: Load the field parsing finite state machine corresponding to the protocol according to the protocol type P , and generate a field list , according to the field list Sequentially extract the protocol fields and construct the protocol original field vector ; Step S30: Using a preset mapping function The protocol raw field vector Mapped to a unified abstract frame structure to obtain a protocol-independent unified data frame object ; Step S40: Unify the data frame object according to the protocol type P Perform protocol security verification based on Step S50: After the protocol security verification is passed, interactive adaptation control and frame submission control are executed to obtain cross-protocol parsed data, and the cross-protocol parsed data is adaptively uploaded to the corresponding business layer; After the protocol security verification is passed, interactive adaptation control and frame submission control are executed to obtain cross-protocol parsing data, which specifically includes: According to the protocol type , call the behavior adaptation function to generate the processing action identifier of the current data frame , ,in, Used to indicate , execute ACK frame response and set retransmission window; Used to indicate ,Based on the connection status maintenance, the data is buffered into the GATT queue and waited for the business layer to pull; Used to indicate Skip the feedback process and schedule to sleep; The processing action identifier when generating the current data frame After that, calculate the protocol switching cost function , and switch the cost function according to the protocol Determine whether to perform cross-protocol forwarding processing; wherein, ,in, For the slave agreement Switch to Protocol The energy consumed, For the slave agreement Switch to Protocol The time consumed, For the slave agreement Switch to Protocol Delay weight factor of the switching process; Preset cost threshold ,like , it enters the protocol forwarding buffer queue, suspends forwarding, and waits for the scheduling window to be reallocated. Otherwise, cross-protocol forwarding processing is executed immediately to obtain cross-protocol parsed data.

2. The data interaction method of a radio frequency transceiver according to claim 1, characterized in that: In step S10, the preset hash function H(·) includes CRC-16, BKDR Hash, Jenkins Hash or FNV-1a function, which is used to adapt to the real-time protocol identification requirements of low-power embedded devices; the output protocol type P ∈ {LoRa, ZigBee, BLE}, where LoRa is a long-distance, low-rate communication protocol based on spread spectrum modulation, ZigBee is a low-power, short-distance communication protocol that supports networking and confirmation mechanisms, and BLE is a short-range Bluetooth communication protocol.

3. The data interaction method of a radio frequency transceiver according to claim 1, wherein: In step S20, the field list The formula is: ,in, For the protocol type P Valid fields, including AdvA of BLE protocol, SrcAddr of ZigBee protocol and DevAddr of LoRa protocol, The total number of valid fields in the protocol type P; field parsing finite state machine Used to support the state jump of optional fields, variable-length fields and nested fields in protocol type P; protocol original field vector It includes address field vector, frame control field vector, payload field vector, frame check code field vector and special field vector.

4. The data interaction method of a radio frequency transceiver according to claim 1, wherein: In step S30, the data frame object is unified The formula is: ,in, To unify the length of the data frame object; It is a standard field in a unified frame, including source node address, frame type field, payload field and security check field; mapping function Used to perform field renaming, zero padding, and word length alignment operations.

5. The data interaction method of a radio frequency transceiver according to claim 1, wherein: In step S40, according to the protocol type P, the unified data frame object The steps for performing protocol security verification based on the protocol include: Unified DataFrame Object The formula is: ,in, To unify the length of the data frame object; It is a standard field in a unified frame, including the source node address, frame type field, payload field, and security check field; According to the unified data frame object The security verification field in the protocol type P calls the security verification function Verify P ( ), calculate the security verification result flag , ; When the security verification result flag = 1, the protocol security verification is judged to be passed, otherwise it is judged to be failed.

6. The data interaction method of a radio frequency transceiver according to claim 1, wherein: In step S50, the step of adaptively uploading the cross-protocol parsed data to the corresponding business layer specifically includes: Get the protocol type P from the cross-protocol parsing data; if LoRa, upload cross-protocol parsing data to the remote MQTT / HTTP gateway; if ZigBee, forwards cross-protocol parsed data to the coordinator; if BLE, sends BLE attribute notifications to mobile terminals through preset GATT services; After uploading, the execution will return to receive the feedback content and decide whether to clear the buffer or start the protocol reset based on the feedback content.

7. A data interaction system for a radio frequency transceiver, applied to a data interaction method for a radio frequency transceiver according to any one of claims 1 to 6, characterized in that: The data interaction system of the radio frequency transceiver includes: The protocol identification module is used to extract the leading bit sequence B[0:k] of the first k bits used for protocol identification in the wireless data frame after the wireless data frame is received by the receiving path of the radio frequency transceiver terminal, and calculate the protocol candidate index value based on the leading bit sequence B[0:k] using a preset hash function H(·) , according to the candidate index value of the protocol Search for matching items in the pre-set protocol mapping table and output the protocol type P; Field parsing module, used to load the field parsing finite state machine corresponding to the protocol type P , and generate a field list , according to the field list Extract the protocol fields sequentially and construct the protocol original field vector ; Field mapping module, used to pass preset mapping functions The protocol raw field vector Mapped to a unified abstract frame structure to obtain a protocol-independent unified data frame object ; Protocol verification module, used to unify data frame objects according to protocol type P Perform protocol security verification based on The interaction and submission module is used to perform interaction adaptation control and frame submission control after the protocol security verification is passed, obtain cross-protocol parsing data, and adaptively upload the cross-protocol parsing data to the corresponding business layer.

8. A data exchange device for a radio frequency transceiver, characterized in that: The data interaction device of the radio frequency transceiver includes: a memory, a processor, and a data interaction program of the radio frequency transceiver stored in the memory and executable on the processor. When the data interaction program of the radio frequency transceiver is executed by the processor, a data interaction method of the radio frequency transceiver according to any one of claims 1 to 6 is implemented.

9. A computer program product, characterized in that The computer program product includes a data interaction program for a radio frequency transceiver, and when the data interaction program for the radio frequency transceiver is executed by a processor, the data interaction method for a radio frequency transceiver according to any one of claims 1 to 6 is implemented.

Citation Information

Patent Citations

  • Method for realizing cross-modal data protocol conversion on FPGA (Field Programmable Gate Array) and FPGA

    CN118069653A

  • Communication device and communication control device for enabling operation of control protocol for one network on other types of networks

    US20020169886A1