Embedded Device Data Inspection System

Abstract

This invention proposes an embedded device data detection system, which includes a near-field sensing module and a main control processing unit connected to the near-field sensing module; it also includes a network communication module connected to the main control processing unit; and M clients connected to the network communication module. When the near-field sensing module successfully reads a valid chip ID, the main control processing unit immediately triggers a push event, without waiting for client queries, and directly sends the chip ID information in a predefined format to all currently connected clients through the established TCP connection. This invention adopts an event-driven model, transmitting data only when a real identification event occurs, effectively reducing invalid communication traffic and improving the overall system efficiency and stability.

Description

Technical Field

[0001] This invention relates to the field of intelligent technology, and in particular to an embedded device data detection system. Background Technology

[0002] In intelligent identification, industrial automation, and Internet of Things (IoT) systems, it is often necessary to use a fixedly installed base station device to perform contactless identification of nearby electronic chips (such as RFID tags, NFC chips, etc.) and transmit the identification results to a remote computer or control terminal in real time. Such systems typically consist of two parts: a near-field sensing module, used to read the chip's unique identifier (ID); and a network communication module, used to send the ID to the host computer software or server.

[0003] Currently, network communication between base stations and computers can employ various modes. From a transmission protocol perspective, common choices include TCP and UDP: TCP provides reliable, ordered connections, suitable for scenarios with high data integrity requirements; UDP, on the other hand, features low latency and connectionlessness, suitable for broadcast or multicast applications that tolerate a small amount of packet loss. From a role architecture perspective, a base station can be configured either as a TCP / UDP Server (listening for and accepting external connections) or as a TCP / UDP Client (actively connecting to a specified remote host).

[0004] However, in practical applications, most existing base station equipment has significant limitations in network communication design. For example, when the base station acts as a client, the IP address and port of the target server must be pre-configured. Once the network topology changes or the server is relocated, the equipment needs to be reconfigured, resulting in poor flexibility. When using the UDP protocol, although broadcasting or one-way transmission can be achieved, the lack of connection status and retransmission mechanisms makes it difficult to guarantee the reliable delivery of critical identification events (such as high-security access control card swiping).

[0005] On the other hand, even if some base stations support TCP Server mode, their communication logic still largely adopts a "passive response" mechanism: that is, they only return the currently cached chip ID after receiving a query command from the client. This polling-based interaction method has inherent defects—if the chip only briefly passes through the sensing area (such as a workpiece on a high-speed conveyor belt) and the client does not initiate a query, the identification event will be missed; if the polling frequency is increased to avoid missing, it will significantly increase network traffic and CPU overhead, affecting the overall system efficiency.

[0006] More importantly, very few existing base stations can achieve "event-driven proactive push" in TCP Server mode: that is, once the near-field module detects a valid chip entering the sensing range, it immediately and proactively sends the chip's ID to all connected clients through the established TCP connection, without waiting for any requests. This "sensing as notification" mechanism has significant advantages for application scenarios with high real-time and reliability requirements (such as contactless attendance, production line workstation triggering, and real-time asset tracking), but it has not yet been effectively implemented.

[0007] In summary, the existing technology has at least the following problems:

[0008] Rigid communication roles: Base stations, as clients, need to preset server addresses, making deployment inflexible; as servers, they rely heavily on polling and cannot proactively notify.

[0009] Protocol selection and scenario mismatch: UDP lacks reliability guarantees, and TCP is passively used, wasting its connection advantages;

[0010] Lack of event-driven capability: It is unable to proactively push the ID through the established TCP connection the moment the chip approaches, resulting in insufficient real-time performance or excessive system overhead.

[0011] To address the aforementioned problems, this invention proposes a novel working mode in which the base station acts as a TCP server: when the chip approaches and is successfully identified, the base station immediately uses the established TCP connection to proactively push the chip ID to one or more clients, thereby achieving a highly real-time, highly reliable, and loosely coupled identification event notification mechanism. Summary of the Invention

[0012] The present invention aims to at least solve the technical problems existing in the prior art, and in particular, innovatively proposes an embedded device data detection system.

[0013] To achieve the above-mentioned objectives of the present invention, the present invention provides an embedded device data detection system, including a near-field sensing module and a main control processing unit connected to the near-field sensing module;

[0014] It also includes a network communication module connected to the main control processing unit;

[0015] It also includes M clients connected to the network communication module; M is a positive integer greater than or equal to 1, namely the 1st client, the 2nd client, the 3rd client, ..., the Mth client;

[0016] When the near-field sensing module successfully reads a valid chip ID, the main control processing unit immediately triggers a push event. Without waiting for client queries, it directly sends the chip ID information in a predefined format to all currently connected clients through the established TCP connection.

[0017] In a preferred embodiment of the present invention, the chip ID information includes an ID number or an ID number, a timestamp, and a signal strength.

[0018] In a preferred embodiment of the present invention, the predefined format includes JSON, a custom binary frame, or plain text.

[0019] In a preferred embodiment of the present invention, the target chip includes RFID, NFC or other contactless radio frequency chips;

[0020] The main control processing unit includes a microcontroller, an embedded processor, or an integrated SoC chip;

[0021] The network communication module includes an Ethernet and / or Wi-Fi module.

[0022] This invention also discloses a method for detecting data in an embedded device, comprising the following steps:

[0023] S1, The network communication module establishes TCP connections with M clients;

[0024] S2, the near-field sensing module determines whether it has sensed and read the target chip:

[0025] If the near-field sensing module successfully reads a valid chip ID, the main control processing unit immediately triggers a push event and executes the next step;

[0026] If the near-field sensing module fails to read a valid chip ID, proceed to step S2;

[0027] S3 sends the read chip ID to M clients in a predefined format;

[0028] In a preferred embodiment of the present invention, the network communication module in step S1 includes an Ethernet and / or Wi-Fi module.

[0029] In a preferred embodiment of the present invention, the target chip in step S2 includes RFID, NFC or other contactless radio frequency chips.

[0030] In a preferred embodiment of the present invention, the predefined format in step S3 includes JSON, a custom binary frame, or plain text.

[0031] The present invention also discloses a computer system, comprising:

[0032] processor;

[0033] Memory used to store processor-executable instructions;

[0034] The processor is configured to implement the embedded device data detection method when executing the executable instructions.

[0035] The present invention also discloses a computer-readable storage medium, comprising:

[0036] A memory on which computer programs are stored;

[0037] A processor is configured to execute the program in the memory to implement the embedded device data detection method.

[0038] In summary, by adopting the above technical solutions, this invention uses an event-driven model, transmitting data only when a real event is identified, effectively reducing invalid communication traffic and improving the overall efficiency and stability of the system.

[0039] Additional aspects and advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. Attached Figure Description

[0040] The above and / or additional aspects and advantages of the present invention will become apparent and readily understood from the description of the embodiments taken in conjunction with the following drawings, in which:

[0041] Figure 1 This is a schematic block diagram illustrating the connection of the present invention. Detailed Implementation

[0042] Embodiments of the present invention are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present invention, and should not be construed as limiting the present invention.

[0043] This invention discloses an embedded device data detection system, such as... Figure 1 As shown, it includes a near-field sensing module and a main control processing unit connected to the near-field sensing module;

[0044] It also includes a network communication module connected to the main control processing unit;

[0045] The near-field sensing module is used to wirelessly detect and read the unique identification information of electronic chips within a short range (typically a few centimeters to tens of centimeters). This module can be based on RFID (such as ISO / IEC 14443, ISO / IEC 15693), NFC, or other contactless radio frequency technologies, and includes an antenna coil, a radio frequency transceiver, and a baseband decoding circuit. When a target chip enters its electromagnetic induction area, the module automatically activates and reads the chip ID.

[0046] Main control processing unit: Used to receive and parse the read chip ID data. This unit can be a microcontroller (MCU), an embedded processor (such as the ARM Cortex series), or an integrated SoC chip, with built-in firmware to perform event judgment, data encapsulation, and network scheduling logic.

[0047] Network communication module: This module integrates an Ethernet controller or Wi-Fi module and supports the standard TCP / IP protocol stack. It is configured to run a TCP Server service, listening on a preset port (e.g., 8899) and waiting for connection requests from external TCP clients (such as management software on a PC). Once a connection is established, it will be maintained as a persistent connection by the main control unit until the client actively disconnects or a timeout occurs.

[0048] It also includes M clients (computers) connected to the network communication module; M is a positive integer greater than or equal to 1, namely the 1st client, the 2nd client, the 3rd client, ..., the Mth client;

[0049] When the near-field sensing module successfully reads a valid chip ID, the main control processing unit sends the chip ID information in a predefined format (a 24-byte hexadecimal byte stream) to all currently connected clients through the established TCP connection.

[0050] When the near-field sensing module successfully reads a valid chip ID, the main control processing unit sends the chip ID information in a predefined format (a 68-byte hexadecimal byte stream) to all currently connected clients through the established TCP connection.

[0051] Here is an example of a message sent by the sensing module:

[0052] BB 02 22 00 3D D5 30 00 02 00 10 71 00 00 52 9B 09 40 B4 02 C4 CA 4238 A0 B9 23 82 0D CC 50 9A 6F 75 84 9B C8 1E 72 8D 9D 4C 2F 63 6F 06 7F 89 CC14 86 2C EC CB C8 7E 4B 5C E2 FE 28 30 8F D9 EB 98 D7 7E

[0053] BB 02 22: This is the packet identifier, 3 bytes in length;

[0054] 00 3D: This is the packet length in hexadecimal. 0x3D indicates 61 bytes (D5 30 ~ EB 98), with a length of 2 bytes.

[0055] D5 30 00: Can be ignored; length 3 bytes, content may vary;

[0056] 02 00 ~ 8F D9: Card number, a total of 56 bytes;

[0057] EB 98: Card CRC;

[0058] D7: Checksum, sum all bytes except the first byte BB, and only the lower 8 bits of the result are taken;

[0059] 7E: End symbol;

[0060] This invention also discloses a method for detecting data in an embedded device, comprising the following steps:

[0061] S1, the network communication module establishes TCP connections with M clients; when M is 4, the connections could be as follows: Client 1 connects to the Ethernet module via Ethernet, and Clients 1, 2, and 3 connect to the Wi-Fi module via Wi-Fi; Clients 1 and 2 connect to the Ethernet module via Ethernet, and Clients 2 and 4 connect to the Wi-Fi module via Wi-Fi; or Clients 1, 2, 3, and 4 connect to the Wi-Fi module via Wi-Fi, etc.; this depends on the communication method established between the clients and the network communication module.

[0062] S2, the near-field sensing module determines whether it has sensed and read the target chip:

[0063] If the near-field sensing module successfully reads a valid chip ID, the main control processing unit immediately triggers a push event and executes the next step;

[0064] If the near-field sensing module fails to read a valid chip ID, proceed to step S2;

[0065] S3, sends the read chip ID to M clients in a predefined format; specifically including the following steps:

[0066] S31, generate a chip ID code from the read chip ID number; use a QR code generator to generate a chip ID code (21×21 QR code) from the chip ID number;

[0067] S32, generate the chip ID number using the numbers 0 and 1 from the chip ID code; treat the black squares in the chip ID code as 1 and the white squares as 0, and extract them in order from top to bottom and from left to right to obtain the chip ID number; in this step, if the number of digits of the chip ID number is not a multiple of eight, then add 0 or 1 to the beginning of the chip ID number to make it a multiple of eight.

[0068] For example, the obtained 21×21 chip ID number is 000000000000100000111000100000000000000001010010100110110001001010000001011010000001011001001011001010000100011100101000001011110010010000111001001000001101110010010000110111001100101000010000110111001100101000010011011110111011101011000010010 011011110010000001111001110010100011011001110101000010111101100011011011110000011001111111000001100111111110001001110011000001010010000110001011001110110011001011111001000011111110010110101101011111100101000001100001000111111011001;

[0069] Adding a 0 to the beginning of the chip ID number results in: 000000100000000000010000011100010000000000000000010100101001101100010010010100000010110100000001011001001100101001000010001110001010 00001011100100100011100000100000110111001100101000010011010011011110111010110000100100110111100100000111100111001010001101110101001100001011 1101100011011110000011001111111100010011100110000010100100001100010110011101100110010111110010000111111001000011111110010110101110111000101111111000101000 001100001000111111011001; the corresponding hexadecimal is 020010710000529B0940B402C4CA4238A0B923820DCC509A6F75849BC81E728D9D4C2F636F067F89CC14862CECCBC87E4B5CE2FE28308FD9;

[0070] S33 sends the chip ID number to M clients.

[0071] After the client receives the data, the following steps are also included:

[0072] First, after any client receives the chip ID number, it proceeds to the next step;

[0073] The second step is to generate an M×M (21×21) grid based on the number of digits in the chip ID number; then, write the binary chip ID number into the M×M grid in a top-to-bottom, left-to-right order; in this step, if... If it is not an integer, then the first QM×M bits of the binary chip ID number need to be removed;

[0074] ,

[0075] in, Let M be the value of M in the M×M grid;

[0076] It is a round-down operator;

[0077] The square root of the algorithm;

[0078] The number of bits in the chip ID number received in the first step;

[0079] The third step is to change the color of the M×M squares to obtain the chip ID code; in this step, the squares with a value of 1 are changed to black squares, and the squares with a value of 0 are changed to white squares.

[0080] The fourth step is to obtain the chip ID number from the chip ID code. This is done by scanning the chip ID code with a QR code scanner to generate the chip ID number.

[0081] The present invention also discloses a computer system, comprising:

[0082] processor;

[0083] Memory used to store processor-executable instructions;

[0084] The processor is configured to implement the embedded device data detection method when executing the executable instructions.

[0085] The present invention also discloses a computer-readable storage medium, comprising:

[0086] A memory on which computer programs are stored;

[0087] A processor is configured to execute the program in the memory to implement the embedded device data detection method.

[0088] 1. Enables real-time proactive push notifications for chip recognition events, significantly improving response speed.

[0089] Existing technologies mostly rely on client polling to obtain chip IDs, which carries the risk of event omissions or delays. This invention, upon detecting a chip's proximity by the base station, immediately pushes the ID information to the client via an established TCP connection, eliminating the need to wait for query requests. This reduces event notification latency to milliseconds, making it particularly suitable for scenarios with high real-time requirements, such as high-speed production lines and seamless access.

[0090] 2. Adopts a standard TCP Server architecture, offering strong compatibility and easy integration.

[0091] The base station operates as a TCP server, conforming to a general network programming model. Any host computer software that supports standard Socket communication (such as Python, C#, and Java applications) can directly connect and receive data without the need for dedicated drivers or proprietary protocol parsing, significantly reducing system integration difficulty and development costs.

[0092] 3. Avoid high-frequency polling to reduce network and computing resource overhead.

[0093] Traditional polling mechanisms require clients to send requests periodically, continuously consuming bandwidth and CPU resources even when no chip is present. This invention employs an event-driven model, transmitting data only when a real event occurs, effectively reducing unnecessary communication traffic and improving overall system efficiency and stability.

[0094] 4. Supports concurrent reception by multiple clients, enhancing system scalability and flexibility.

[0095] The base station can maintain multiple TCP client connections simultaneously and push the same ID information to all connections synchronously when the chip identifies the device. This capability facilitates "one source, multiple uses"—for example, the same identification event can be received simultaneously by the monitoring platform, database recording module, and alarm system, without the need to deploy multiple readers or intermediate forwarding services.

[0096] 5. High communication reliability ensures that critical events are not lost.

[0097] Compared to UDP broadcast or one-way transmission, this invention is based on the connection-oriented characteristics of the TCP protocol and has data confirmation, retransmission and order guarantee mechanisms to ensure that the chip ID can still be delivered to the client completely and accurately in complex network environments, meeting the needs of high-reliability application scenarios such as access control and payment.

[0098] 6. Flexible deployment, no need to preset server address

[0099] When the base station acts as a server, it only needs to be configured with a local listening port, and clients can connect proactively. Compared to solutions where the base station acts as a client and requires pre-writing the server IP and port, this invention is more suitable for dynamic IP, DHCP, or cloud server environments, facilitating rapid on-site deployment and subsequent maintenance.

[0100] 7. Simple structure, reducing reliance on intermediate devices

[0101] By integrating near-field identification, event judgment, and TCP push functions into a single base station device, no additional gateways, protocol converters, or middleware are required, simplifying the system topology and reducing hardware costs and the number of failure points.

[0102] Although embodiments of the invention have been shown and described, those skilled in the art will understand that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the claims and their equivalents.

Claims

1. An embedded device data detection system, characterized by, It includes a near-field sensing module and a main control processing unit connected to the near-field sensing module; It also includes a network communication module connected to the main control processing unit; It also includes M clients connected to the network communication module; M is a positive integer greater than or equal to 1, namely the 1st client, the 2nd client, the 3rd client, ..., the Mth client; When the near-field sensing module successfully reads a valid chip ID, the main control processing unit immediately triggers a push event. Without waiting for client queries, it directly sends the chip ID information in a predefined format to all currently connected clients through the established TCP connection.

2. The system of claim 1, wherein, Chip ID information includes ID number or ID number, timestamp, and signal strength.

3. The system of claim 1, wherein, Predefined formats include JSON, custom binary frames, or plain text.

4. The system of claim 1, wherein, The target chips include RFID, NFC, or other contactless radio frequency chips; The main control processing unit includes a microcontroller, an embedded processor, or an integrated SoC chip; The network communication module includes an Ethernet and / or Wi-Fi module.

5. An embedded device data detection method, characterized by, Includes the following steps: S1, The network communication module establishes TCP connections with M clients; S2, the near-field sensing module determines whether it has sensed and read the target chip: If the near-field sensing module successfully reads a valid chip ID, the main control processing unit immediately triggers a push event and executes the next step; If the near-field sensing module fails to read a valid chip ID, proceed to step S2; S3 sends the read chip ID to M clients in a predefined format.

6. The embedded device data detection method according to claim 5, characterized in that, In step S1, the network communication module includes an Ethernet and / or Wi-Fi module.

7. The embedded device data detection method according to claim 5, characterized in that, In step S2, the target chip includes RFID, NFC, or other contactless radio frequency chips.

8. The embedded device data detection method according to claim 5, characterized in that, In step S3, the predefined formats include JSON, custom binary frames, or plain text.

9. A computer system, characterized in that, include: processor; Memory used to store processor-executable instructions; The processor is configured to implement the embedded device data detection method according to any one of claims 5 to 8 when executing the executable instructions.

10. A computer-readable storage medium, characterized in that, include: A memory on which computer programs are stored; A processor for executing the program in the memory to implement the embedded device data detection method according to any one of claims 5 to 8.

Images