Iot data receiving apparatus
By designing highly integrated protocol communication components and sensor interfaces, the problem of protocol incompatibility in traditional IoT sensor systems has been solved, enabling a single device to access data from multiple sensors, reducing hardware costs and operational complexity, and improving the system's flexibility and scalability.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- BEIJING HEJUNCHI TECHNOLOGY CO LTD
- Filing Date
- 2026-03-27
- Publication Date
- 2026-06-05
AI Technical Summary
Traditional IoT sensor systems require the deployment of multiple dedicated receiving devices due to incompatible communication protocols, resulting in redundant hardware investment, complex wiring, difficult maintenance, high costs, and poor scalability.
Design a highly integrated and software-configurable protocol communication component that supports multiple communication protocols (such as LoRa, RS-485 industrial bus, etc.). Through dynamic adaptation and parallel support, it enables a single device to uniformly access and receive sensor data from different communication protocols, and performs unified decoding and centralized management through the sensor interface and the main control component.
It enables "one-machine access and unified processing" of multi-protocol sensor data, significantly reducing hardware deployment and maintenance costs, and improving system flexibility, scalability and data integration efficiency.
Smart Images

Figure CN122160397A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of sensor technology, and in particular to an Internet of Things (IoT) data receiving device. Background Technology
[0002] With the development of IoT and smart sensing technology in the field of power equipment condition monitoring, multi-protocol, multi-type sensor collaborative monitoring systems have emerged. This technology can collect various status parameters such as temperature, tilt, and vibration of transmission lines and power distribution equipment in real time, and realize comprehensive perception and remote monitoring of equipment operating status.
[0003] In traditional technologies, dedicated receivers are typically configured for sensors using different communication protocols. For example, an RF chip is usually optimized for a specific frequency band (e.g., 433MHz). To support another frequency band (e.g., 2.4GHz), a separate RF front-end, filter, and antenna design often needs to be added to the circuit board. This not only increases costs but also introduces technical challenges such as circuit interference, increased power consumption, and layout difficulties. Therefore, from the perspective of design simplicity and avoiding internal interference, manufacturers tend to produce single-band / single-protocol devices.
[0004] However, while this method can receive sensor data from multiple sensors, it requires configuring multiple dedicated receiving devices for sensors with different communication protocols, resulting in repeated hardware investment, complex wiring, and difficult operation and maintenance. Therefore, there is an urgent need for an IoT data receiving device that can reduce the cost of receiving sensor data. Summary of the Invention
[0005] Therefore, it is necessary to provide an IoT data receiving device that can reduce the cost of receiving sensor data, addressing the aforementioned technical problems.
[0006] In a first aspect, this application provides an Internet of Things (IoT) data receiving device, comprising:
[0007] The protocol communication component is configured as follows:
[0008] In response to a communication configuration command, the communication protocol component is configured with at least one communication protocol indicated by the communication configuration command; wherein the protocol communication component supports configuring multiple communication protocols simultaneously.
[0009] For each communication protocol, target encoded data is received from the target sensor corresponding to the communication link through the communication link corresponding to the communication protocol; wherein, the target encoded data is obtained by the target sensor encoding the collected target sensing data;
[0010] The sensor interface connects to the protocol communication components and is configured as follows:
[0011] Receive the target encoded data transmitted by the protocol communication component;
[0012] Decode each target encoded data to obtain the target sensing data corresponding to each target encoded data;
[0013] The main control component, connected to the sensor interface component, is configured as follows:
[0014] Receive the target encoded data transmitted from the sensor interface;
[0015] Perform data management on the sensor data of each target.
[0016] In some embodiments, the protocol communication component includes:
[0017] The radio frequency transceiver is configured as follows:
[0018] In response to a communication configuration command, configure the radio frequency transceiver with a long-distance communication LoRa protocol for at least one operating frequency band indicated by the communication configuration command;
[0019] For each LoRa protocol, target encoded data sent by the target sensor in the operating frequency band of the LoRa protocol is received through the communication link corresponding to the LoRa protocol.
[0020] In some embodiments, the radio frequency transceiver is a LoRa radio frequency transceiver; the LoRa radio frequency transceiver supports operating frequency bands of at least 433MHz and 2.4GHz.
[0021] In some embodiments, the protocol communication component includes:
[0022] The wired communication interface is configured as follows:
[0023] In response to a communication configuration command, configure at least one industrial protocol indicated by the communication configuration command for the wired communicator;
[0024] For each industrial protocol, target encoded data is received from the target sensor corresponding to the communication link through a communication link that matches the industrial protocol.
[0025] In some embodiments, the wired communication interface is an isolated RS-485 interface.
[0026] In some embodiments, when the master control component performs data management on the sensor data of each target, it is configured as follows:
[0027] The comparison results are obtained by comparing the sensor data of each target with the corresponding sensor threshold.
[0028] Based on the comparison results, an alarm notification is output.
[0029] In some embodiments, the protocol communication component includes:
[0030] A network communicator, connected to the main control component, is configured as follows:
[0031] In response to a communication configuration command, configure at least one network protocol corresponding to the communication configuration command for the network communicator;
[0032] Send alerts to the cloud platform corresponding to each network protocol.
[0033] In some embodiments, the IoT data receiving device further includes a display screen; when the main control component executes an output alarm notification, it is configured to:
[0034] The control display screen shows alarm alerts;
[0035] The main control component is also configured as follows:
[0036] Receive communication configuration commands triggered via the display screen, and / or receive communication configuration commands sent by the cloud platform.
[0037] In some embodiments, when the sensor interface performs decoding of the target encoded data, it is configured to:
[0038] Based on the retransmission status and reception time of each target encoded data, the different target encoded data are sorted to obtain the decoding order;
[0039] Decode each target encoded data according to the decoding order.
[0040] In some embodiments, when the sensor interface sorts different target encoded data according to the retransmission status and reception time of each target encoded data to obtain the decoding order, it is configured as follows:
[0041] For each first encoded data that is retransmitted in each target encoded data, the first encoded data is sorted according to the reception time of each first encoded data to obtain the first order;
[0042] For each second encoded data that is not retransmitted in each target encoded data, the second encoded data is sorted according to the reception time of each second encoded data to obtain the second order;
[0043] The first and second orders are concatenated to obtain the decoding order.
[0044] Secondly, this application also provides a method for receiving Internet of Things (IoT) data, including:
[0045] In response to a communication configuration command, the communication protocol component is configured with at least one communication protocol indicated by the communication configuration command; wherein the protocol communication component supports configuring multiple communication protocols simultaneously.
[0046] For each communication protocol, target encoded data is received from the target sensor corresponding to the communication link through the communication link corresponding to the communication protocol; wherein, the target encoded data is obtained by the target sensor encoding the collected target sensing data;
[0047] Decode each target encoded data to obtain the target sensing data corresponding to each target encoded data;
[0048] Perform data management on the sensor data of each target.
[0049] Thirdly, this application also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:
[0050] In response to a communication configuration command, the communication protocol component is configured with at least one communication protocol indicated by the communication configuration command; wherein the protocol communication component supports configuring multiple communication protocols simultaneously.
[0051] For each communication protocol, target encoded data is received from the target sensor corresponding to the communication link through the communication link corresponding to the communication protocol; wherein, the target encoded data is obtained by the target sensor encoding the collected target sensing data;
[0052] Decode each target encoded data to obtain the target sensing data corresponding to each target encoded data;
[0053] Perform data management on the sensor data of each target.
[0054] Fourthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, performs the following steps:
[0055] In response to a communication configuration command, the communication protocol component is configured with at least one communication protocol indicated by the communication configuration command; wherein the protocol communication component supports configuring multiple communication protocols simultaneously.
[0056] For each communication protocol, target encoded data is received from the target sensor corresponding to the communication link through the communication link corresponding to the communication protocol; wherein, the target encoded data is obtained by the target sensor encoding the collected target sensing data;
[0057] Decode each target encoded data to obtain the target sensing data corresponding to each target encoded data;
[0058] Perform data management on the sensor data of each target.
[0059] Fifthly, this application also provides a computer program product, including a computer program that, when executed by a processor, performs the following steps:
[0060] In response to a communication configuration command, the communication protocol component is configured with at least one communication protocol indicated by the communication configuration command; wherein the protocol communication component supports configuring multiple communication protocols simultaneously.
[0061] For each communication protocol, target encoded data is received from the target sensor corresponding to the communication link through the communication link corresponding to the communication protocol; wherein, the target encoded data is obtained by the target sensor encoding the collected target sensing data;
[0062] Decode each target encoded data to obtain the target sensing data corresponding to each target encoded data;
[0063] Perform data management on the sensor data of each target.
[0064] The aforementioned IoT data receiving device, through the design of a highly integrated and software-configurable protocol communication component, achieves dynamic adaptation and parallel support for multiple communication protocols (such as LoRa at different frequency bands, RS-485 industrial bus, etc.). This allows a single device to uniformly access and receive data from various sensors using different communication protocols. The sensor interface is responsible for uniformly decoding the received heterogeneous encoded data, extracting and standardizing the raw sensor data. The main control component centrally manages and intelligently processes the standardized multi-source sensor data. This solution effectively solves the problems of system complexity, high cost, and poor scalability caused by the deployment of multiple dedicated receiving devices due to protocol incompatibility in traditional monitoring systems. It achieves "one-machine access and unified processing" of multi-protocol sensor data, significantly reducing hardware deployment and maintenance costs, and improving system flexibility, scalability, and data integration efficiency. Attached Figure Description
[0065] To more clearly illustrate the technical solutions in the embodiments or related technologies of this application, the accompanying drawings used in the description of the embodiments or related technologies will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0066] Figure 1A This is an application environment diagram of an Internet of Things (IoT) data receiving device provided in this embodiment;
[0067] Figure 1B This embodiment provides a representation of target sensor information.
[0068] Figure 2 This is a flowchart illustrating the first type of IoT data receiving device provided in this embodiment;
[0069] Figure 3A This is a flowchart illustrating the second type of IoT data receiving device provided in this embodiment;
[0070] Figure 3B This embodiment provides a schematic representation of a Modbus protocol data frame structure.
[0071] Figure 4 This is a flowchart illustrating the third type of IoT data receiving device provided in this embodiment;
[0072] Figure 5A This is a flowchart illustrating the fourth type of IoT data receiving device provided in this embodiment;
[0073] Figure 5B This is a schematic diagram of a circuit board for an Internet of Things (IoT) receiver provided in this embodiment;
[0074] Figure 5C This is a schematic diagram of a communication configuration interface provided in this embodiment;
[0075] Figure 6A This is a flowchart illustrating the fifth type of IoT data receiving device provided in this embodiment;
[0076] Figure 6B This is a schematic diagram of the housing of an Internet of Things (IoT) data receiving device provided in this embodiment;
[0077] Figure 7 This is a flowchart illustrating an IoT data receiving method provided in this embodiment;
[0078] Figure 8 This is a flowchart illustrating a data decoding step provided in this embodiment;
[0079] Figure 9 This is an internal structural diagram of a computer device provided in this embodiment. Detailed Implementation
[0080] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.
[0081] The IoT data receiving device provided in this application embodiment can be applied to, for example... Figure 1AIn the application environment shown, an IoT data receiving device includes: a protocol communication component 1, configured to: configure at least one communication protocol indicated by the communication configuration command in response to a communication configuration command; wherein the protocol communication component supports simultaneous configuration of multiple communication protocols; for each communication protocol, receive target encoded data sent by a target sensor corresponding to the communication link through a communication link corresponding to the communication protocol; wherein the target encoded data is obtained by the target sensor encoding the collected target sensing data; a sensor interface 2, connected to the protocol communication component, and configured to: receive each target encoded data transmitted by the protocol communication component; decode each target encoded data to obtain target sensing data corresponding to each target encoded data; and a main control component 3, connected to the sensor interface component, and configured to: receive each target encoded data transmitted by the sensor interface; and perform data management on each target sensing data.
[0082] The protocol communication component is a collection of hardware modules and software protocols used to realize data communication with external sensors or devices. It can support the parallel dynamic configuration of multiple wired / wireless communication protocols and is responsible for receiving coded data sent by sensors according to the configured protocol.
[0083] Among them, the communication configuration command is used to instruct the protocol communication component to enable, disable or adjust the communication protocols and corresponding parameters it supports. It can be triggered by the local human-machine interface or issued by the remote cloud platform to achieve dynamic adaptation of the communication protocol.
[0084] Among them, communication protocols refer to the data transmission rules and formats agreed upon in IoT communication, including but not limited to long-range communication protocols (LoRa), industrial bus protocols, and network protocols, which are used to ensure reliable data interaction between sensors, receiving devices, and cloud platforms.
[0085] Among them, a communication link refers to a physical or logical connection channel established according to a specific communication protocol for transmitting data between a target sensor and a protocol communication component, including wireless radio frequency links, wired serial links, and network data links.
[0086] The target sensor refers to a sensing device deployed on the monitored equipment or environment to collect specific physical quantities (such as temperature, tilt, vibration) and encode and transmit the sensing data according to an agreed communication protocol; it is the data source of this device. For example... Figure 1B The target sensor information shown is intended to represent the intent of this table, which stores all the sensors used in the IoT data receiving device for testing applications.
[0087] The sensor interface refers to the hardware and software functional modules inside the device used to receive target encoded data from the protocol communication component and decode it to restore the target sensing data, thereby realizing unified access and format standardization of multi-source heterogeneous data.
[0088] Among them, target sensing data refers to the raw physical quantity data collected by the target sensor, encoded and transmitted, and then decoded and restored by the sensor interface. It reflects the real-time status information of the monitored object and is the basis for subsequent data management, analysis and alarm.
[0089] In some embodiments, in response to a communication configuration instruction, the communication protocol component establishes a communication link between itself and the target sensor corresponding to the corresponding communication protocol for each communication protocol indicated by the communication configuration instruction; and receives target encoded data sent by the corresponding target sensor through the communication link.
[0090] In some embodiments, the sensor interface receives target encoded data transmitted by the protocol communication component; for each target encoded data, the target encoded data is decoded to obtain the target sensing data corresponding to the corresponding target encoded data.
[0091] In some embodiments, the system receives target-encoded data transmitted from the sensor interface and performs data management on the target sensing data. This data management includes, but is not limited to, data storage and caching, data preprocessing and cleaning, data aggregation and statistics, threshold comparison and alarm generation, and data visualization and display.
[0092] In some embodiments, when the main control component performs data management on the sensor data of each target, it is configured to: compare each target sensor data with the corresponding sensor threshold to obtain a comparison result; and output an alarm reminder based on the comparison result.
[0093] The main control component uses a high-performance embedded microcontroller as its core, responsible for the coordinated control and data processing of various functional units within the device. The main control module runs embedded software to perform functions such as parsing sensor data, edge computing, and managing the communication protocol stack; it serves as the control center of the entire device.
[0094] It should be noted that the IoT data receiving device also has a built-in high-speed memory for caching sensor data and running edge computing algorithms. The edge processing unit, which runs on the main control CPU, includes a data processing system and can perform local fusion calculations on various types of collected data.
[0095] For example, for each target sensing data, the comparison result between the target sensing data and the corresponding sensing threshold is determined; if the comparison result indicates that the target sensing data is abnormal, an alarm is output; if the comparison result indicates that the target sensing data is normal, no alarm is required.
[0096] The aforementioned IoT data receiving device, through the design of a highly integrated and software-configurable protocol communication component, achieves dynamic adaptation and parallel support for multiple communication protocols (such as LoRa at different frequency bands, RS-485 industrial bus, etc.). This allows a single device to uniformly access and receive data from various sensors using different communication protocols. The sensor interface is responsible for uniformly decoding the received heterogeneous encoded data, extracting and standardizing the raw sensor data. The main control component centrally manages and intelligently processes the standardized multi-source sensor data. This solution effectively solves the problems of system complexity, high cost, and poor scalability caused by the deployment of multiple dedicated receiving devices due to protocol incompatibility in traditional monitoring systems. It achieves "one-machine access and unified processing" of multi-protocol sensor data, significantly reducing hardware deployment and maintenance costs, and improving system flexibility, scalability, and data integration efficiency.
[0097] In one exemplary embodiment, such as Figure 2 As shown, the protocol communication component 1 includes: a radio frequency transceiver 11, configured to: in response to a communication configuration command, configure the radio frequency transceiver with a long-distance communication LoRa protocol for at least one operating frequency band indicated by the communication configuration command; and for each LoRa protocol, receive target encoded data sent by a target sensor in the operating frequency band of the LoRa protocol through a communication link corresponding to the LoRa protocol.
[0098] A radio frequency (RF) transceiver is a hardware circuit module (chip or module) that integrates radio signal transmission and reception functions, and is the core physical component for realizing wireless communication. It is used to receive data frames sent by surrounding wireless sensor nodes, with a line-of-sight communication distance of up to hundreds of meters. The RF transceiver is a LoRa RF transceiver; the LoRa RF transceiver supports operating frequency bands of at least 433MHz and 2.4GHz.
[0099] The operating frequency band refers to the specific frequency range within which a radio frequency transceiver is configured or designed to transmit and receive radio signals. This is a fundamental parameter for channel allocation and interference avoidance in radio communication.
[0100] Among them, the LoRa protocol specifically refers to a physical layer modulation technology, the core of which is to use spread spectrum technology to achieve wireless communication over distances of several kilometers or even longer with extremely low power consumption.
[0101] In some embodiments, in response to a communication configuration command, the radio frequency transceiver configures a LoRa protocol for each operating frequency band indicated by the communication configuration command for the corresponding LoRa protocol; for each LoRa protocol, a communication link is established between the radio frequency transceiver and the target sensor corresponding to the corresponding LoRa protocol; and target encoded data is received from the target sensor through the communication link.
[0102] In the above embodiments, by configuring the RF transceiver to be responsive to commands and support the LoRa protocol in at least one operating frequency band (such as 433MHz and 2.4GHz), a single RF module can flexibly adapt to and simultaneously receive data from multiple LoRa sensors in different frequency bands. This design achieves unified access and parallel reception of LoRa protocol sensors in different operating frequency bands, avoiding hardware redundancy and increased costs associated with deploying independent RF receiving modules for different frequency bands, and enhancing the device's protocol compatibility and deployment flexibility in multi-frequency, long-distance IoT environments.
[0103] In one exemplary embodiment, such as Figure 3A As shown, the protocol communication component 1 includes: a wired communication interface 12, configured to: configure at least one industrial protocol indicated by the communication configuration command for the wired communicator in response to a communication configuration command; and for each industrial protocol, receive target encoded data sent by a target sensor corresponding to the communication link through a communication link that matches the industrial protocol.
[0104] The wired communication interface is a hardware port and its driver circuit that establishes a stable and reliable electrical connection with external devices via physical cables (such as twisted-pair cables or coaxial cables) and performs data transmission. It provides an isolated RS-485 interface (supporting industrial protocols such as MODBUS), allowing the device to be connected as a data master station to a field monitoring system. The wired communication interface is an isolated RS-485 interface.
[0105] Industrial protocols, in the context of industrial automation and control systems, are standardized communication rules and application-layer data formats designed to enable deterministic, reliable, and real-time data exchange and command control between devices from different manufacturers. Examples include Message Queuing Telemetry Transport (MQTT), Modicon Bus (Modbus), and Process Fieldbus (PROFIBUS). Figure 3B The diagram shows a schematic representation of the Modbus protocol data frame structure.
[0106] In some embodiments, the wired communication interface responds to a communication configuration instruction and configures a corresponding industrial protocol for each industrial protocol indicated by the communication configuration instruction; for each industrial protocol, it establishes a communication link between the wired communication interface and the target sensor corresponding to the corresponding industrial protocol; and receives target encoded data sent by the corresponding target sensor through the communication link.
[0107] In the above embodiments, by configuring the wired communication interface to respond to commands and dynamically support at least one industrial protocol, a single physical interface can flexibly adapt to multiple industrial fieldbus protocols, enabling data communication with wired sensors or devices using different industrial protocols. This design effectively solves the problem that traditional wired data acquisition devices cannot be compatible with multiple industrial buses due to fixed protocols and require the configuration of multiple dedicated interface modules. It significantly improves the protocol adaptability and system integration of the device in complex industrial environments, reduces hardware costs and wiring complexity, and enhances the flexibility and scalability of data access.
[0108] In one exemplary embodiment, such as Figure 4 As shown, the protocol communication component 1 includes: a network communicator 13, which is connected to the main control component and configured to: in response to a communication configuration command, configure at least one network protocol corresponding to the communication configuration command for the network communicator; and send alarm reminders to the cloud platform corresponding to each network protocol.
[0109] The network communicator refers to the collection of hardware modules and software protocols within a device responsible for bidirectional data communication with a remote cloud platform or data center via an IP network (such as a cellular network or Ethernet). It primarily handles the network layer connection for data uplink (reporting) and command downlink (receiving). It is used to upload processed data to the IoT cloud platform via industrial protocols.
[0110] Among them, network protocols are a set of layered communication rules designed to enable reliable, orderly, and efficient data exchange between applications located on different network nodes in the Internet environment based on the TCP / IP model.
[0111] In some embodiments, in response to a communication configuration instruction, a corresponding network protocol is configured for the network communicator for each network protocol indicated by the communication configuration instruction; for each network protocol, a communication link is established between the network communicator and the host computer or cloud platform corresponding to the corresponding network protocol; and an alarm notification is sent to the host computer or cloud platform corresponding to each network protocol through the communication link.
[0112] In the above embodiments, the network communicator can respond to commands and dynamically configure at least one network protocol, enabling a single device to flexibly adapt to the communication requirements of different cloud platforms or data centers, and achieve targeted and reliable uploading of alarm information. This design effectively solves the problem that traditional IoT terminals cannot connect to multiple cloud platforms due to fixed network protocols and require additional gateways for protocol conversion. It significantly improves the flexibility of alarm reporting, system integration, and cloud compatibility, reduces the complexity and deployment cost of multi-platform access, and enhances the adaptability and operational efficiency of devices in heterogeneous cloud environments.
[0113] In one exemplary embodiment, such as Figure 5A As shown, the IoT data receiving device also includes a display screen 4; when the main control component executes the output alarm reminder, it is configured to: control the display screen to display the alarm reminder; the main control component is also configured to: receive communication configuration instructions triggered by the display screen, and / or receive communication configuration instructions sent by the cloud platform.
[0114] For example, such as Figure 5B The diagram shown is a schematic of the circuit board for an IoT data receiving device.
[0115] The board displays several key components and their locations. On the left are the power input interfaces (V+ and V-), the system interface (SYS), a dual-color LED indicator (PWR), and a 485 communication interface. Slightly to the left of center is an interface marked with a ground symbol, next to which are interfaces labeled A and B; the LoRa module area and antenna location are marked in the center. On the right is a 4G module area and a network port. These components work together to enable the board to perform various communication functions. The PWR is the power interface, used to supply power to the device. The antenna location indicates the installation or connection position of the radio frequency (RF) antenna, typically used to support wireless communication such as 4G / LoRa. V+ indicates a positive voltage input or a high-level power supply terminal. The SYS system interface is used for debugging, firmware upgrades, or system configuration. The 485 communication interface is an RS-485 industrial bus interface (labeled with lines A and B), used to connect industrial sensors or devices supporting protocols such as Modbus. The 4G interface ensures 4G cellular communication and is used for mobile network connections. The network port represents an Ethernet interface (RJ45) for wired network connections, supporting TCP / IP communication.
[0116] For example, such as Figure 5CThe diagram shows a communication configuration interface that can be displayed on the screen of an IoT data receiving device. Users can set at least one communication protocol in the communication configuration interface displayed on the screen. The main control component responds to the at least one communication protocol set by the user on the screen and determines the communication configuration command according to each communication protocol. The main control component sends the corresponding communication protocol to the communication protocol component indicated by the communication configuration command, such as sending the LoRa protocol to the radio frequency transceiver for protocol configuration.
[0117] For example, the communication configuration interface can also be displayed on a cloud platform or a host computer connected to the IoT data receiving device; in response to the user setting at least one communication protocol in the communication configuration interface displayed on the cloud platform or host computer, a communication configuration instruction is determined; and the communication configuration instruction is sent to the main control component in the IoT data receiving device.
[0118] In the above embodiments, by integrating display screen control functions and a two-way command receiving mechanism into the main control component, local visual prompts for alarm information are achieved, and communication configuration commands can be flexibly issued via either a local touchscreen or a remote cloud platform. This design effectively solves the problems of unclear on-site status and reliance on dedicated tools or remote connections for parameter configuration caused by the lack of a human-machine interface in traditional IoT devices. It significantly improves the on-site operability, configuration flexibility, and ease of operation and maintenance of the devices, while enhancing the real-time performance and reliability of "cloud-edge-device" collaboration and reducing the technical threshold and cost of on-site debugging and maintenance.
[0119] In one exemplary embodiment, such as Figure 6A As shown, the IoT data receiving device also includes: a solar panel 5; and a power supply control component 6, which is connected to the solar panel and configured to: determine the power generation power of the solar panel based on the output voltage and output current of the solar panel; and determine the power supply strategy for non-power supply components in the IoT data receiving device based on the target power range to which the power generation power belongs.
[0120] In an exemplary embodiment, the IoT data receiving device further includes a battery 7 connected to a power supply control component and configured to supply power to non-power supply components in the IoT data receiving device. Correspondingly, when the power supply control component executes a power supply strategy for supplying power to power supply components in the IoT data receiving device based on a target power range to which the power generation power belongs, it is configured to: control the solar panel to supply power to non-power supply components in the IoT data receiving device according to a first power range to which the power generation power belongs; control the solar panel and battery to supply power to non-power supply components in the IoT data receiving device according to a second power range to which the power generation power belongs; and disconnect the connection with the solar panel and control the battery to supply power to non-power supply components in the IoT data receiving device according to a third power range to which the power generation power belongs.
[0121] It should be noted that, as Figure 6B The schematic diagram of the IoT data receiving device casing shown represents the mechanical structure and protective design of the device. Although it does not directly process data, this part is crucial for the reliable operation of the entire device. The casing uses high-strength materials and is supplemented with components such as sealing rings and waterproof and breathable membranes, achieving an IP65 protection rating—completely preventing dust intrusion and protecting against low-pressure water jets from all directions. This protection ensures that the device remains waterproof in outdoor rain and snow, prevents dust accumulation in dusty environments, and protects internal electronic components from corrosion damage. This module also includes mechanical structures for installation (such as clamps and bolt holes), allowing for easy and safe fixing of the device to tower legs, crossarms, or utility poles. The overall structural design fully considers factors such as high and low temperatures, wind vibration, and mechanical stress in power field environments. It has undergone rigorous type testing to meet multiple national standards (such as vibration resistance, shock resistance, and electromagnetic compatibility), and can withstand long-term environmental temperature variations from -40℃ to over +70℃, as well as strong sunlight and wind without affecting normal function.
[0122] In one exemplary embodiment, such as Figure 7 As shown, an IoT data receiving method is provided. Taking the application of this method to the IoT data receiving device in Figure 1 as an example, the method includes the following steps S701 to S704. Wherein:
[0123] S701 responds to a communication configuration instruction to configure at least one communication protocol indicated by the communication configuration instruction for a communication protocol component.
[0124] For each communication protocol, S702 receives target encoded data sent by the target sensor corresponding to the communication link through the communication link corresponding to the communication protocol.
[0125] S703 decodes the target encoded data to obtain the target sensing data corresponding to each target encoded data.
[0126] S704 manages the sensor data of each target.
[0127] In some embodiments, the method is described using the main control component 3 in FIG1 as an example, specifically including: when the target sensor is a time-series sensor, filtering the target sensing data; when the target sensor is a vibration sensor, performing time-domain feature processing and / or frequency-domain feature processing on the target sensing data to obtain target sensing features; performing data fusion processing on the target sensing data of different target sensors to obtain device status data of the target device; the target device is the device on which each target sensor is installed.
[0128] In the above embodiments, by designing a highly integrated and software-configurable protocol communication component, dynamic adaptation and parallel support for multiple communication protocols (such as LoRa at different frequency bands, RS-485 industrial bus, etc.) are achieved. This allows a single device to uniformly access and receive data from various sensors using different communication protocols. The sensor interface is responsible for uniformly decoding the received heterogeneous encoded data, extracting and standardizing the raw sensor data. The main control component centrally manages and intelligently processes the standardized multi-source sensor data. This solution effectively solves the problems of system complexity, high cost, and poor scalability caused by the deployment of multiple dedicated receiving devices due to protocol incompatibility in traditional monitoring systems. It achieves "one-machine access and unified processing" of multi-protocol sensor data, significantly reducing hardware deployment and maintenance costs, and improving system flexibility, scalability, and data integration efficiency.
[0129] In one exemplary embodiment, such as Figure 8 As shown, this embodiment refines the steps for decoding the target encoded data in the above embodiments, and provides a flowchart of the data decoding steps. Taking the application of this method to sensor interface 2 in Figure 1 as an example, the specific steps include:
[0130] S801 sorts different target encoded data according to the retransmission status and reception time of each target encoded data to obtain the decoding order.
[0131] In one optional embodiment, the retransmission status and reception time of each target encoded data are determined; target encoded data with retransmission status are sorted first according to reception time, and target encoded data without retransmission status are sorted last.
[0132] In one optional embodiment, for each first encoded data in each target encoded data that is retransmitted, the first encoded data is sorted according to the reception time of each first encoded data to obtain a first order; for each second encoded data in each target encoded data that is not retransmitted, the second encoded data is sorted according to the reception time of each second encoded data to obtain a second order; the first order and the second order are concatenated according to the order of first order first and second order last to obtain the decoding order.
[0133] For example, for each first encoded data in each target encoded data that has been retransmitted, the first encoded data is sorted according to the order of its reception time from now to the past to obtain a first order; for each second encoded data in each target encoded data that has not been retransmitted, the second encoded data is sorted according to the order of its reception time from now to the past to obtain a second order; the first order and the second order are concatenated according to the order of the first order first and the second order last to obtain the decoding order.
[0134] It should be noted that if the target encoded data is retransmitted (e.g., three times in a row), it indicates that the target encoded data may be abnormal, and therefore the IoT data receiving device should handle it first.
[0135] S802 decodes each target encoded data according to the decoding order.
[0136] In some embodiments, the target encoded data is decoded sequentially according to the decoding order.
[0137] In the above embodiments, the decoding order is determined by intelligent sorting based on the retransmission status and reception time of the target encoded data, prioritizing data with retransmissions or earlier reception times, effectively optimizing the timing arrangement and resource allocation of the decoding process. This design reduces decoding waiting time and processing congestion caused by packet collisions, delays, or out-of-order arrivals, improving decoding efficiency and system real-time performance. It also enhances the reliability and integrity of data reception in unstable wireless communication environments, avoiding data loss or processing delays, and ensuring that critical sensor information can be parsed and uploaded in a timely and orderly manner.
[0138] In some embodiments, firstly, sensors distributed at the power transmission line site (such as wireless temperature sensors) collect environmental parameters and transmit the data via 433MHz / 2.4GHz wireless signals. An IoT data receiving device installed on a pole or distribution box acquires the temperature measurement data frame through its built-in 433MHz / 2.4GHz receiving module, and the main control module parses the temperature value. Subsequently, the edge computing module processes the temperature data locally, comparing it with a preset threshold and calculating the rate of temperature change. If an abnormal temperature rise exceeding the threshold is detected, the device immediately generates an alarm message; simultaneously, it can automatically accelerate the sensor sampling interval from 5 minutes to several seconds according to preset logic to more closely monitor temperature changes. Next, the main control module encapsulates the processed key data into IoT business data messages via the MQTT protocol and sends them uplink to the cloud-based status monitoring platform. During uplink communication, the device securely publishes the MQTT messages to a designated IoT message server via its built-in 4G module or Ethernet interface; the remote platform receives the data, stores and displays it, and can further trigger corresponding operation and maintenance strategies. This device also supports bidirectional communication: the cloud platform or dispatch center can send configuration commands to the field data receiving device to adjust its ID, version number, IP address, Modbus configuration, protocol specifications, working mode, reporting frequency, or remotely upgrade the device firmware. After these downlink commands are sent to the device via the MQTT channel, the main control module parses the commands and controls the sensor interface module or communication module to perform corresponding operations. The entire communication interaction process fully demonstrates the synergy between edge intelligence and the cloud platform: the front-end device is responsible for real-time data collection and preliminary data identification, while the cloud is responsible for centralized storage, analysis, and global decision-making. The two work closely together through standardized protocols to ensure efficient and reliable transmission line status monitoring.
[0139] It should be noted that the IoT data receiving device adopts a highly integrated circuit board design, integrating multiple communication interfaces and protocols, and can simultaneously support multiple data transmission methods such as 433MHz low-power wireless, 2.4GHz, RS-485 industrial bus, and MQTT-based network communication. This multi-protocol compatibility allows the device to directly receive wireless sensor data in the 433MHz / 2.4GHz bands, connect to other field property management platforms via the RS-485 interface, and connect to the IoT platform via Ethernet or 4G cellular network, achieving unified access for different communication standards. This device is compatible with various types of sensors, including but not limited to temperature sensors, temperature and humidity sensors, switch sensors, fire early warning devices, tilt (angle) sensors, vibration sensors, etc., enabling monitoring of various status quantities such as the temperature of transmission line conductor connections, tower tilt, equipment vibration status, and conductor distribution temperature-sensitive fires. Through open sensor interface specifications, the device can simultaneously receive and process heterogeneous data from different sensors, overcoming the limitation of existing devices supporting only one sensor. This device has a built-in edge computing unit, providing local processing capabilities for on-site data. The device can preprocess and perform preliminary analysis on the raw data collected by sensors, including data filtering, anomaly detection, and statistical aggregation, and selectively upload key information according to preset strategies. Through local preprocessing, the device achieves "intelligent data upload": while ensuring timely reporting of anomalies, it reduces redundant data consuming communication bandwidth and improves upload efficiency. When an abnormal state is detected, the device can trigger multiple immediate uploads of alarm information, while for stable and normal data, it performs periodic business data uploads, thereby improving the system's response speed and timeliness to device anomalies.
[0140] It should be noted that IoT data receiving devices have the following advantages:
[0141] Improve operation and maintenance efficiency and reduce costs: By deploying this device to enable online monitoring of power transmission equipment, the frequency and reliance on manual inspections can be significantly reduced. Maintenance personnel can view the status data of line equipment in real time on a centralized monitoring platform, eliminating the need for frequent on-site inspections. This not only reduces the safety risks of power line inspections but also reduces the investment of manpower and resources, thereby significantly lowering operation and maintenance costs.
[0142] Significantly improved real-time performance and accuracy: This device enables continuous online monitoring of equipment operation status. Compared to traditional periodic temperature measurements or post-incident inspections, it can capture abnormal changes and issue early warnings immediately. For example, when a tension clamp exhibits abnormal overheating, the device can detect a sudden temperature rise within seconds and report an alarm, preventing further deterioration of the defect. This real-time sensing capability ensures the timeliness of monitoring data. Simultaneously, leveraging high-precision sensors and local edge computing, this device can filter noise interference and improve measurement accuracy, making the uploaded data more accurate and reliable. The backend system performs trend analysis and fault diagnosis based on this high-quality data, resulting in more reliable outcomes.
[0143] High compatibility and convenient system expansion: This device is multi-functional, supporting various sensors and communication protocols, allowing different types of monitoring needs to be met by a single system. This highly integrated design avoids the need for separate receivers for each sensor, reducing redundant investment and overall complexity. When adding new sensor types, simply add the corresponding sensor on-site and connect it through the device's open interface; the existing system remains compatible with the new equipment without significant modifications, demonstrating excellent compatibility and scalability. This is particularly important for building a comprehensive online monitoring platform for power transmission lines, allowing for smooth upgrades as needs expand.
[0144] With strong environmental adaptability and stable and reliable operation, this device is designed and selected according to industrial-grade standards. The entire hardware unit can operate stably within a wide temperature range of -40℃ to +85℃, with a protection rating of IP65 or higher, making it waterproof and dustproof, and adaptable to various climatic conditions such as high-altitude humidity and sandstorms. Furthermore, the circuit design incorporates protection measures against electromagnetic interference and lightning surges, ensuring long-term reliable operation under strong electromagnetic fields and high voltage environments. Based on the above design, this device can maintain a stable operating state in various complex environments, providing reliable data support for power systems around the clock and under all operating conditions.
[0145] In summary, the IoT data receiving device effectively addresses the shortcomings of traditional power transmission line status monitoring methods, achieving unified reception and intelligent processing of multi-source sensing data. While improving the real-time performance and accuracy of monitoring, it also considers the system's openness, compatibility, and field adaptability, demonstrating significant practical value and promising prospects for widespread application.
[0146] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.
[0147] In one exemplary embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 9 As shown, this computer device includes a processor, memory, input / output interfaces (I / O), and a communication interface. The processor, memory, and I / O interfaces are connected via a system bus, and the communication interface is also connected to the system bus via the I / O interfaces. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides the environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The database stores data. The I / O interfaces are used for exchanging information between the processor and external devices. The communication interface is used for communicating with external terminals via a network connection. When the computer program is executed by the processor, it implements an Internet of Things (IoT) data receiving method.
[0148] Those skilled in the art will understand that Figure 9 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.
[0149] In one embodiment, a computer device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above method embodiments.
[0150] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the steps in the above method embodiments.
[0151] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above method embodiments.
[0152] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data must comply with relevant regulations.
[0153] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments described above. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.
[0154] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.
[0155] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.
Claims
1. An Internet of Things (IoT) data receiving device, characterized in that, include: The protocol communication component is configured as follows: In response to a communication configuration command, at least one communication protocol indicated by the communication configuration command is configured for the communication protocol component; wherein the protocol communication component supports configuring multiple communication protocols simultaneously; For each communication protocol, target encoded data is received from the target sensor corresponding to the communication link through the communication link corresponding to the communication protocol; wherein, the target encoded data is obtained by the target sensor encoding the collected target sensing data; The sensor interface, connected to the protocol communication component, is configured as follows: Receive the target encoded data transmitted by the protocol communication component; Decode each target encoded data to obtain the target sensing data corresponding to each target encoded data; The main control component is connected to the sensor interface component and is configured as follows: Receive the target encoded data transmitted by the sensor interface; Perform data management on the sensor data of each target.
2. The apparatus according to claim 1, characterized in that, The protocol communication component includes: The radio frequency transceiver is configured as follows: In response to the communication configuration command, configure the radio frequency transceiver with a long-distance communication LoRa protocol for at least one operating frequency band indicated by the communication configuration command; For each LoRa protocol, target encoded data sent by the target sensor in the operating frequency band of the LoRa protocol is received through the communication link corresponding to the LoRa protocol.
3. The apparatus according to claim 2, characterized in that, The radio frequency transceiver is a LoRa radio frequency transceiver; the LoRa radio frequency transceiver supports operating frequency bands of at least 433MHz and 2.4GHz.
4. The apparatus according to claim 2, characterized in that, The protocol communication component includes: The wired communication interface is configured as follows: In response to the communication configuration command, configure the wired communicator with at least one industrial protocol indicated by the communication configuration command; For each industrial protocol, target encoded data sent by the target sensor corresponding to the communication link is received through a communication link that matches the industrial protocol.
5. The apparatus according to claim 4, characterized in that, The wired communication interface is an isolated RS-485 interface.
6. The apparatus according to any one of claims 1-5, characterized in that, When the main control component performs data management on the sensor data of each target, it is configured as follows: The comparison results are obtained by comparing the sensor data of each target with the corresponding sensor threshold. Based on the comparison results, an alarm notification is output.
7. The apparatus according to claim 6, characterized in that, The protocol communication component includes: A network communicator, connected to the main control component, is configured to: In response to the communication configuration command, configure at least one network protocol corresponding to the communication configuration command for the network communicator; Send the alarm notification to the cloud platform corresponding to each network protocol.
8. The apparatus according to claim 6, characterized in that, The IoT data receiving device also includes a display screen; when the main control component executes the output alarm notification, it is configured as follows: Control the display screen to show alarm notifications; The main control component is also configured as follows: Receive communication configuration instructions triggered by the display screen, and / or receive communication configuration instructions sent by the cloud platform.
9. The apparatus according to any one of claims 1-5, characterized in that, When the sensor interface performs decoding of the encoded data for each target, it is configured as follows: Based on the retransmission status and reception time of each target encoded data, the different target encoded data are sorted to obtain the decoding order; Decode each target encoded data according to the decoding order.
10. The apparatus according to claim 1, characterized in that, When the sensor interface sorts different target encoded data according to the retransmission status and reception time of each target encoded data to obtain the decoding order, it is configured as follows: For each first encoded data that is retransmitted in each target encoded data, the first encoded data is sorted according to the reception time of each first encoded data to obtain the first order; For each second encoded data that is not retransmitted in each target encoded data, the second encoded data is sorted according to the reception time of each second encoded data to obtain the second order; The first order and the second order are concatenated to obtain the decoding order.