Terminal equipment and method for intelligently identifying communication protocol

Abstract

The invention discloses a terminal device and method for intelligently identifying a communication protocol, and relates to the technical field of industrial automation and communication, the terminal device for intelligently identifying the communication protocol mainly comprises a data acquisition module, a feature matching module and a dynamic verification module; the data acquisition module is used for capturing and preprocessing original communication data to obtain an effective data packet; the feature matching module is used for performing feature extraction and matching according to the effective data packets to obtain candidate protocols; and the dynamic verification module is used for carrying out protocol confirmation and identification result output according to the candidate protocols. By implementing the terminal equipment and the method for intelligently identifying the communication protocol provided by the invention, the adaptation efficiency can be improved, and the operation and maintenance cost can be reduced.

Description

Technical Field

[0001] This invention relates to the fields of industrial automation and communication technology, and more specifically, to a terminal device and method for intelligently identifying communication protocols. Background Technology

[0002] The fragmentation of communication protocols in production environments is a significant issue, creating "protocol barriers." These barriers include both conventional protocols like Modbus RTU and PROFINET, as well as vendor-customized proprietary protocols, and the coexistence of old and new equipment (older sensors only support basic protocols, while smart devices use newer protocols like TSN), resulting in high interconnectivity barriers. Traditional protocol adaptation relies on manual parameter configuration, which is error-prone and inefficient. Fixed conversion gateways operate on a "one-to-one" model, requiring new purchases for any new devices, leading to soaring costs. Furthermore, traditional solutions cannot adapt in real-time to dynamic changes in operating conditions and network environments, often causing communication interruptions or production accidents. Therefore, existing technologies suffer from interconnectivity barriers, low adaptation efficiency, and high maintenance costs due to fragmented industrial equipment protocols. Breaking down these barriers, improving adaptation efficiency, and reducing maintenance costs are urgent technical challenges that need to be addressed. Summary of the Invention

[0003] The purpose of this invention is to provide a terminal device and method for intelligently identifying communication protocols, which can improve adaptation efficiency and reduce operation and maintenance costs.

[0004] This invention provides a terminal device for intelligently identifying communication protocols, including a data acquisition module, a feature matching module, and a dynamic verification module. The data acquisition module is used for capturing and preprocessing raw communication data to obtain valid data packets. The feature matching module is used for extracting and matching features based on the valid data packets to obtain candidate protocols. The dynamic verification module is used for confirming the protocol and outputting the identification result based on the candidate protocols.

[0005] The present invention also provides a method for intelligently identifying communication protocols, which utilizes the aforementioned terminal device for intelligently identifying communication protocols to perform communication protocol identification.

[0006] The terminal device and method for implementing the intelligent identification communication protocol provided by the present invention have the following beneficial effects: This invention focuses on the management of equipment communication protocols in industrial production environments, aiming at the needs of equipment interconnection, data connectivity, and flexible production in smart manufacturing scenarios. Addressing the problems of interconnection barriers, low adaptation efficiency, and high maintenance costs caused by fragmented industrial equipment protocols, the invention employs a data acquisition module to capture and preprocess raw communication data to obtain effective data packets; a feature matching module to extract and match features from the effective data packets to obtain candidate protocols; and a dynamic verification module to confirm and output the protocol identification results based on the candidate protocols.

[0007] This invention features an automatic identification function that can scan connected devices in real time. Through protocol feature library matching and deep learning algorithms, it can quickly identify various protocols and versions, such as Modbus, PROFINET, and custom proprietary protocols, without manual intervention. Its dynamic adaptation function can sense changes in operating conditions (load, accuracy) and network (bandwidth, interference), automatically adjusting protocol parsing parameters to ensure stable communication. Furthermore, its multi-protocol conversion function supports cross-protocol data interaction, uniformly converting data from different protocol formats into a standardized format (such as OPC UA), thus establishing seamless data links between devices.

[0008] This invention can be applied to specific areas such as Industrial Internet of Things (IIoT), R&D of smart terminal devices, and multi-protocol identification and conversion, providing intelligent protocol management support for the digital upgrade of industrial systems. Attached Figure Description

[0009] The present invention will be further described below with reference to the accompanying drawings and embodiments. In the accompanying drawings: Figure 1 This is a block diagram of the terminal device for intelligent identification communication protocol provided by the present invention. Detailed Implementation

[0010] To provide a clearer understanding of the technical features, objectives, and effects of the present invention, specific embodiments of the present invention will now be described in detail with reference to the accompanying drawings.

[0011] Figure 1 A schematic diagram of a terminal device for intelligent identification of communication protocols according to this embodiment is shown. In this embodiment, the terminal device for intelligent identification of communication protocols includes a data acquisition module, a feature matching module, and a dynamic verification module; the data acquisition module is used for capturing and preprocessing raw communication data to obtain valid data packets; the feature matching module is used for extracting and matching features based on the valid data packets to obtain candidate protocols; the dynamic verification module is used for confirming the protocol and outputting the identification result based on the candidate protocols.

[0012] In one exemplary embodiment, the data acquisition module includes an initialization unit and a data acquisition unit; the initialization unit is used to load a protocol feature library and configure hardware interface parameters; the data acquisition unit is used to acquire raw communication data using multiple interfaces, preprocess the raw communication data, and obtain valid data packets.

[0013] In one exemplary embodiment, the protocol feature library includes fieldbus protocols, industrial Ethernet protocols, communication middleware and general protocols, wireless industrial protocols, proprietary vendor protocols, and emerging protocols.

[0014] As an exemplary embodiment, the fieldbus protocol includes at least one of the following protocols: PROFIBUS protocol, MODBUS RTU / ASCII protocol, CAN protocol, DeviceNet protocol, Foundation Fieldbus protocol, HART protocol, and CC-Link protocol.

[0015] As an exemplary embodiment, the industrial Ethernet protocol includes at least one of the following protocols: PROFINET protocol, EtherNet / IP protocol, MODBUS TCP-MODBUS protocol, EtherCAT protocol, POWERLINK protocol, SERCOS III protocol, and CC-Link IE protocol.

[0016] As an exemplary embodiment, the communication middleware and general protocol include at least one of the following protocols: OPC UA protocol, MQTT protocol, BACnet protocol, and DNP3 protocol.

[0017] As an exemplary embodiment, the wireless industrial protocol includes at least one of the following protocols: WirelessHART protocol, ISA100.11a protocol, WIA-PA protocol, and Zigbee protocol.

[0018] As an exemplary embodiment, the proprietary vendor protocol includes at least one of the following protocols: FINS protocol, S7 Communication protocol, MELSEC Protocol protocol, and R-Link protocol.

[0019] As an exemplary embodiment, the emerging protocol includes at least one of the following protocols: TSN protocol, 5G-Advanced / 6G protocol, OPC UA PubSub-OPC UA protocol, and DDS protocol.

[0020] In one exemplary embodiment, the multiple interfaces include a serial interface, an Ethernet interface, and a wireless interface, wherein the wireless interface includes a WiFi interface and a 4G interface. The collection of raw communication data includes passive listening mode and active probing mode. The passive listening mode is a data packet actively sent by the real-time listening device, and the active probing mode sends a general probing command to trigger the device to send back data. The preprocessing includes noise filtering and data integrity verification; the noise filtering includes removing invalid data frames generated by electromagnetic interference, and the invalid data frames include data with abnormal frame length or incorrect check bits; the data integrity verification verifies the integrity of the physical layer frame, including verifying the start bit and stop bit of the serial port data.

[0021] In one exemplary embodiment, the data acquisition unit is also used for data cache management to prevent data loss caused by sudden surges in network data volume.

[0022] In one exemplary embodiment, the feature matching module includes a feature extraction unit, a basic matching unit, and a weighted matching unit; the feature extraction unit is used to extract frame structure features, instruction code features, and communication interaction features; the basic matching unit is used for full feature comparison and matching determination; the weighted matching unit is used to obtain candidate protocols based on the frame structure features, instruction code features, communication interaction features, and preset weights in the protocol feature library.

[0023] In one exemplary embodiment, the frame structure features include a start identifier, end identifier, checksum method, frame length, field composition, and checksum bit position of the data frame; the instruction code features include a function code field, special identifier, instruction code value range, and bit width; the communication interaction features include interaction mode, timing features, and port features; the timing features include data frame interval and request-response delay; and the port features include the communication port number.

[0024] In one exemplary embodiment, the full feature comparison includes traversing the protocol feature library and comparing the extracted features with the core features of the protocol in the protocol feature library field by field; the core features include frame structure, instruction code range, and verification algorithm; the matching determination includes a complete match determination and a partial overlap determination; the complete match determination includes: if the core features are completely matched, skip the weight matching stage and proceed to instruction verification; the partial overlap determination includes: if the core features are not completely matched, mark it as a partial feature overlap and proceed to weight matching.

[0025] In one exemplary embodiment, the weight matching unit is configured to: calculate a feature matching score based on the frame structure features, instruction code features, communication interaction features, and preset weights in the protocol feature library; filter protocols whose feature matching scores are not less than a preset matching threshold, sort them from high to low scores, and generate a candidate protocol list, wherein the candidate protocol list includes candidate protocols.

[0026] As an exemplary embodiment, the matching threshold is 60.

[0027] In one exemplary embodiment, the dynamic verification module includes an instruction verification unit and a result output unit; the instruction verification unit is used to generate a verification instruction according to the verification instruction set in the candidate protocol, perform response verification according to the verification instruction, and obtain an identification result; the result output unit is used to output logs and identification results.

[0028] In one exemplary embodiment, the identification result includes a protocol type and communication parameters, the communication parameters including baud rate, data bits, and parity bits; the log includes a confidence index of the identification result for each identification, raw data, feature matching score, verification instructions, and responses.

[0029] This embodiment provides a method for intelligently identifying communication protocols, which utilizes the aforementioned terminal device for intelligently identifying communication protocols to perform communication protocol identification.

[0030] In some embodiments, the terminal device of the above-described intelligent identification communication protocol can also be implemented in the following ways.

[0031] In this embodiment, the terminal device for intelligent identification of communication protocols includes the following: (I) Hardware Layer: Multi-dimensional Data Capture Architecture The terminal hardware adopts a "dual-port mirroring + edge computing module" design to ensure lossless collection of raw communication data.

[0032] 1. Port Adapter Module: Equipped with industrial interfaces such as RJ45 Ethernet port and RS485 serial port, supporting connection to CNC equipment with different communication links. Through hardware level adaptive technology, it automatically matches the communication level standard of the equipment (such as TTL / RS232), eliminating the need for manual interface mode switching.

[0033] 2. Data Mirroring Unit: Equipped with a built-in industrial Ethernet switch chip, it supports port mirroring, enabling real-time replication of bidirectional communication data packets between the device and the host computer, avoiding delays or interference with the original communication link. Simultaneously, it employs hardware-level data caching (up to 1GB capacity) to handle sudden data surges in the workshop network and prevent data packet loss.

[0034] 3. Edge preprocessing module: Equipped with an ARM Cortex-A9 processor, it performs preliminary filtering on the captured raw data, removing invalid data frames caused by electromagnetic interference (such as data with abnormal frame length or incorrect check bits), and retaining only valid data packets that conform to the basic format of the communication protocol, thereby reducing the pressure on subsequent software analysis.

[0035] (II) Software Layer: Three-Level Progressive Recognition Algorithm The core software adopts a three-level algorithm architecture of "feature extraction - multi-dimensional matching - dynamic verification", which is combined with the built-in protocol feature library to achieve intelligent recognition.

[0036] 1. Level 1: Precise Extraction of Key Features: By parsing valid data packets, three types of core features are automatically extracted. Regarding frame structure features, the start identifier (e.g., Modbus's 0x01 slave address), end identifier (e.g., CR / LF), and checksum method (e.g., CRC16) of the data frame are identified. Regarding instruction code features, the function code field in the data packet is located (e.g., the "ReadNode" service instruction code in OPC UA, and the "%" program start character in the DNC protocol). Regarding communication interaction features, the interaction sequence between the device and the host computer is recorded (e.g., Modbus's "request-response" mode, MTConnect's "subscribe-push" mode) and communication port (e.g., the commonly used Modbus port 502).

[0037] 2. Secondary Stage: Multi-dimensional Feature Matching: Constructing a matching model based on "basic features + weight optimization". In the basic feature matching stage, the extracted features are compared with the terminal's built-in protocol feature library (containing 20+ mainstream CNC protocol features). If the core features such as frame structure and instruction code are completely matched (e.g., conforming to the 8-bit slave address + 1-bit function code format of Modbus RTU), the protocol type is directly output. If the features partially overlap (e.g., a custom protocol based on Modbus with modified check bits), weight optimization matching is initiated. Different weights are assigned to features such as frame structure, instruction code, and interaction timing (frame structure accounts for 40%, instruction code accounts for 35%, and interaction timing accounts for 25%). The comprehensive matching score is calculated, and a candidate protocol list is selected.

[0038] 3. Level Three: Dynamic Command Verification: For the candidate protocol list, the terminal automatically generates standard verification commands. For example, if the candidate protocol is Modbus, a 0x03 read holding register command is sent to the device; if it is OPC UA, a node read request is sent. If the device returns response data that conforms to the candidate protocol format (e.g., a Modbus response frame containing correct register data and checksum), the final protocol type is locked; if no valid response is received, the terminal automatically switches to the next candidate protocol for repeated verification until the protocol is confirmed or a message "Private protocol features need to be added" is displayed.

[0039] (III) Output and Adaptation Layer: Automatic Configuration of Protocol Parameters After recognition is complete, the terminal outputs the protocol type (e.g., "Modbus RTU"), communication parameters (baud rate 9600, data bits 8, stop bits 1), and adaptation suggestions via the LCD screen and Ethernet interface. Simultaneously, it supports integration with MES / DNC systems, pushing the recognition results to the system via the OPCUA protocol. The system can automatically configure the communication link based on these results, enabling rapid integration of the CNC equipment with the host system.

[0040] In some embodiments, the terminal device of the above-described intelligent identification communication protocol can also be implemented in the following ways.

[0041] In this embodiment, the terminal device for intelligent identification of communication protocols includes the following: I. Overall Development Framework Setup (I) Hardware selection and underlying environment setup Core hardware selection: Main control module: Select an industrial-grade MCU / MPU (such as STM32H743, RK3568) that supports multiple serial ports (RS232 / 485), Ethernet, WiFi / 4G to meet the multi-protocol communication interface requirements of CNC equipment; Communication module: integrates serial-to-Ethernet module and isolated RS485 transceiver (such as ADM2483), adapting to the mainstream physical layer interface of CNC equipment; Storage module: Configure Flash (≥128MB) storage protocol feature library, match model parameters, and SD card extended storage identification log; Power supply module: adopts wide voltage (9-36V) industrial-grade power supply, suitable for the power supply environment of the workshop.

[0042] Setting up the underlying software environment: Embedded system: A real-time operating system based on FreeRTOS / Linux (depending on the main controller selection) is built to ensure the real-time performance of communication data acquisition; Driver development: Complete the development of hardware drivers for serial ports, Ethernet, GPIO, etc., to realize data transmission and reception and interface status detection functions; Development toolchain: Set up the GCC / Keil compilation environment and configure debugging tools (such as J-Link and Wireshark).

[0043] (II) Construction of Protocol Feature Library Feature library design: Structured storage: Protocol features are defined using JSON / binary format, with fields including "protocol name", "physical layer type", "frame structure features", "instruction code range", "interaction timing template", "verification instruction set", and "weight configuration". Mainstream CNC Protocol Feature Input: This section analyzes over 20 mainstream CNC protocols (Modbus RTU / TCP, FANUC FOCAS, OPC UA, MTConnect, Siemens Profinet, etc.) and extracts their core features. Frame structure: such as Modbus RTU frame = slave address (8 bits) + function code (8 bits) + data field (N bits) + CRC check (16 bits); Instruction codes: such as Modbus 0x03 (read holding register), 0x06 (write single register); Interaction timing: such as Modbus request-response timeout (default 1s), OPC UA subscription period; Verification instruction set: Preset standard verification instructions for each protocol (such as Modbus 0x03 instruction frame: 01 03 00 0000 01 84 0A).

[0044] Feature library fixation and updates: Burn the feature library to the terminal Flash, reserve an OTA upgrade interface, and support remote updates of the protocol feature library; Design a private protocol feature supplementation interface to support manual input of custom protocol features.

[0045] II. Development of Multi-Dimensional Feature Matching Module (I) Communication Data Acquisition and Feature Extraction Data collection: After the terminal is started, it automatically scans all communication interfaces (serial port / Ethernet), listens for data packets actively sent by the CNC equipment, or sends a general polling command (such as a 0x00 broadcast frame) to the equipment to trigger the equipment to send back data; The raw data is preprocessed: noise data is filtered, physical layer frame integrity is verified (such as start / stop bit verification of serial port data), and valid data frames are extracted.

[0046] Feature extraction: Frame structure characteristics: parsing the length of the data frame, field separators, check bit positions / algorithms (such as CRC16, LRC), and address segment length; Instruction code characteristics: Extract the function code / instruction code field from the frame and record its numerical range and bit width; Interaction timing characteristics: statistical data frame sending interval, request-response delay, and frame sending frequency.

[0047] (ii) Basic Feature Matching Full feature comparison: Traverse the protocol feature library and compare the extracted features with the "core features" of the protocols in the library field by field; Judgment rule: If the core features such as frame structure, command code, and verification algorithm match 100% (e.g., the data frame fully conforms to the Modbus RTU frame format and the command code is within the Modbus function code range), the protocol type is directly output, and the weight matching stage is skipped. Example: The acquired frame data "01 03 00 00 00 01 84 0A" is parsed as an 8-bit slave address + 8-bit function code + data field + 16-bit CRC checksum, which perfectly matches the Modbus RTU feature in the feature library and is directly identified as the Modbus RTU protocol.

[0048] Determination of partially overlapping features: If the core features do not match completely (e.g., the frame structure conforms to Modbus but the verification algorithm is custom, or the instruction codes partially overlap), it is marked as "features partially overlapped", triggering the weight optimization matching process.

[0049] (III) Weight Optimization Matching Weight configuration loading: Load preset weights (frame structure 40%, instruction code 35%, interaction timing 25%) from the feature library, and support adjusting the weight parameters according to the actual scenario; Feature matching score calculation: Frame structure score: Compare sub-features such as frame length, field composition, and check bit position. A perfect match scores 40 points, while a partial match is scored based on the degree of overlap (e.g., 80% overlap of frame structures scores 32 points). Instruction code score: Compare the instruction code value and bit width, and the matching degree × 35 points (e.g., if the instruction codes overlap by 70%, the score is 24.5 points). Interaction timing score: Compare data frame interval, delay and protocol template, matching degree × 25 points (e.g., 90% timing overlap gets 22.5 points). Overall score = Frame structure score + Instruction code score + Interaction timing score; Candidate protocol list generation: Filter protocols with a comprehensive score ≥ a threshold (e.g., 60 points), sort them from highest to lowest score, and generate a candidate protocol list (keeping a maximum of the top 3 candidate protocols).

[0050] III. Development of Dynamic Instruction Verification Module (a) Verification instruction generation Candidate Protocol Parsing: Reads the "Verification Instruction Set" of the first protocol in the candidate protocol list; Command frame assembly: Automatically generate standard verification command frames according to the protocol format and adapt them to the device physical layer interface (e.g., generate RTU frames for serial port protocol and TCP / UDP packets for Ethernet protocol). Example: When the candidate protocol is Modbus RTU, generate a "Read Holding Register" instruction frame: slave address (default 01) + function code (03) + start register address (0000) + number of registers (0001) + CRC check; Example: When the candidate protocol is OPCUA, generate a node read request (such as reading the node value "ns=1;s=Temperature").

[0051] (ii) Command sending and response verification Command sent: Send verification commands to CNC equipment, set response timeout (configurable, default 1-3s), and adapt to the interaction timing of different protocols; Response data reception and parsing: Monitor device response data and parse response frame format, checksum, and data content; Verification rules: The response frame structure conforms to the candidate protocol format (e.g., the Modbus response frame contains slave address + function code + data field + CRC check). The response data logic is valid (e.g., Modbus register read response contains the correct register value and has no exception code). Protocol lock or switch: If the response data meets the verification rules, the protocol is locked as the final identification result, and the protocol type and communication parameters (such as baud rate and IP address) are output. If no response is received within the timeout period or the response data is invalid, the system will automatically switch to the next protocol in the candidate protocol list and repeat the "instruction generation-sending-verification" process. If all candidate protocols fail to be verified, the terminal will prompt "Private protocol features need to be added" and save the collected raw data and feature matching scores for manual supplementation of the feature library.

[0052] (III) Abnormal Handling Communication timeout handling: Set multi-level timeout thresholds to avoid excessive time consumption for single protocol verification (e.g., verification timeout for each candidate protocol ≤ 3s, total verification time ≤ 10s). Invalid response filtering: Filter out noisy responses and abnormal code responses (such as Modbus function code 0x83 indicating an instruction error) to avoid misjudgment; Interface anomaly handling: When a communication interface failure is detected (such as serial port disconnection or Ethernet disconnection), the verification process is paused and an interface anomaly is indicated.

[0053] IV. Terminal Function Integration and Testing (a) Functional integration Module linkage: Integrate the "data acquisition", "feature matching" and "dynamic verification" modules, and design a state machine to manage the recognition process (initialization → data acquisition → feature extraction → basic matching → weight matching → instruction verification → result output); Results output and interaction: Local output: The recognition result and communication parameters are displayed on the LCD screen, and indicator lights (red and green) indicate recognition success or failure; Remote output: Supports uploading recognition results and logs to the server via Ethernet / 4G, and provides an API interface for host computer to call; Log recording: Records the raw data, feature matching score, verification instructions and responses for each recognition, facilitating troubleshooting.

[0054] (II) Testing and Optimization Laboratory testing: Set up a simulated testing environment: Use CNC protocol simulators (such as Modbus Slave, OPC UA server) to simulate devices with different protocols and verify the recognition accuracy; Boundary testing: Test the recognition performance of custom-modified protocols (such as Modbus with modified check bits) and multi-protocol mixed scenarios; Performance testing: Verify the terminal's recognition response time (target ≤10s) and the stability of simultaneous recognition across multiple interfaces.

[0055] On-site joint debugging: On-site testing of actual CNC equipment (FANUC, Siemens, Mitsubishi, etc.) in the workshop was conducted to verify physical layer compatibility and anti-interference capabilities. Optimize the feature library (supplementing equipment-specific features), adjust weight parameters, and optimize timeout thresholds based on on-site test results; Iterative optimization: Collect and identify failure cases to supplement the private protocol feature library; Optimize the matching algorithm to improve the recognition accuracy of some overlapping feature scenes; Fixed bugs in the communication interface and command verification process.

[0056] V. Mass Production and Deployment Adaptation Hardware mass production optimization: Complete PCB board-level optimization and electromagnetic compatibility (EMC) testing to adapt to the electromagnetic environment of industrial sites; Software burning: Burn the stable firmware to the terminal and configure the factory default parameters (such as feature library, weight, timeout). Deployment Guide Compilation: Provides operation manuals for terminal installation, interface integration, and feature library updates, adapting to deployment scenarios of different CNC equipment.

[0057] The embodiments of the present invention have been described above with reference to the accompanying drawings. However, the present invention is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of the present invention without departing from the spirit and scope of the claims. All of these forms are within the protection scope of the present invention.

Claims

1. A terminal device for intelligently identifying communication protocols, characterized in that, It includes a data acquisition module, a feature matching module, and a dynamic verification module; the data acquisition module is used to capture and preprocess raw communication data to obtain valid data packets; the feature matching module is used to extract and match features based on the valid data packets to obtain candidate protocols; the dynamic verification module is used to confirm the protocol and output the recognition result based on the candidate protocols.

2. The intelligent protocol-identifying end device of claim 1, wherein, The data acquisition module includes an initialization unit and a data acquisition unit; the initialization unit is used to load the protocol feature library and configure the hardware interface parameters; the data acquisition unit is used to collect raw communication data using multiple interfaces, preprocess the raw communication data, and obtain valid data packets.

3. The terminal device for intelligent identification communication protocol according to claim 2, characterized in that, The protocol feature library includes fieldbus protocols, industrial Ethernet protocols, communication middleware and general protocols, wireless industrial protocols, proprietary vendor protocols, and emerging protocols.

4. The terminal device for intelligent identification communication protocol according to claim 2, characterized in that, The various interfaces include a serial interface, an Ethernet interface, and a wireless interface, wherein the wireless interface includes a WiFi interface and a 4G interface. The collection of raw communication data includes passive monitoring mode and active probing mode. The passive monitoring mode is a data packet actively sent by the real-time monitoring device, and the active probing mode sends a general probing command to trigger the device to send back data. The preprocessing includes noise filtering and data integrity verification. The noise filtering includes removing invalid data frames generated by electromagnetic interference, including data with abnormal frame length or incorrect check bits; the data integrity verification is to verify the integrity of the physical layer frame, including verifying the start and stop bits of the serial port data.

5. The terminal device for intelligent identification communication protocol according to claim 1, characterized in that, The feature matching module includes a feature extraction unit, a basic matching unit, and a weighted matching unit. The feature extraction unit is used to extract frame structure features, instruction code features, and communication interaction features. The basic matching unit is used for full feature comparison and matching determination. The weighted matching unit is used to obtain candidate protocols based on the frame structure features, instruction code features, communication interaction features, and preset weights in the protocol feature library.

6. The terminal device for intelligent identification communication protocol according to claim 5, characterized in that, The frame structure features include the start identifier, end identifier, check method, frame length, field composition, and check bit position of the data frame; the instruction code features include the function code field, special identifier, instruction code value range, and bit width; the communication interaction features include the interaction mode, timing features, and port features. The timing features include data frame interval and request-response delay, and the port features include communication port number.

7. The terminal device for intelligent identification communication protocol according to claim 5, characterized in that, The full feature comparison includes traversing the protocol feature library and comparing the extracted features with the core features of the protocol in the protocol feature library field by field; the core features include frame structure, instruction code range, and verification algorithm; the matching determination includes complete matching determination and partial overlap determination. The complete match determination includes: if the core features are completely matched, skip the weight matching stage and proceed to instruction verification; the partial overlap determination includes: if the core features are not completely matched, mark them as partially overlapping features and proceed to weight matching.

8. The terminal device for intelligent identification communication protocol according to claim 5, characterized in that, The weighted matching unit is configured to calculate a feature matching score based on the frame structure features, instruction code features, communication interaction features, and preset weights in the protocol feature library. filter Protocols with feature matching scores not less than a preset matching threshold are sorted from high to low to generate a candidate protocol list, which includes candidate protocols.

9. The terminal device for intelligent identification communication protocol according to claim 1, characterized in that, The dynamic verification module includes an instruction verification unit and a result output unit; the instruction verification unit is used to generate a verification instruction according to the verification instruction set in the candidate protocol, perform response verification according to the verification instruction, and obtain the recognition result; the result output unit is used to output logs and recognition results.

10. A method for intelligently identifying communication protocols, characterized in that, Communication protocol identification is performed using a terminal device with intelligent communication protocol identification as described in any one of claims 1 to 9.

Images