Data operation method, device and medium based on zigbee
By sending register write requests and data compression to terminal devices in the Zigbee network, the problem of data loss caused by channel congestion is solved, read and write operations are optimized, and system performance and user experience are improved.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- SCHNEIDER ELECTRIC (CHINA) CO LTD
- Filing Date
- 2022-07-27
- Publication Date
- 2026-06-23
AI Technical Summary
In Zigbee networks, as the number of terminal devices increases, channel congestion leads to frequent loss of communication data, especially during data read and write operations, which causes severe interference, affecting user operating efficiency and device acceptance.
Network devices trigger terminal devices to send the required data at once by sending register write requests to the terminal devices, and compress multiple data sets as needed to optimize read and write operations.
It effectively avoids excessive occupation of channel resources and data collisions, improves the efficiency of read and write operations and system performance, and adapts to the usage scenarios of different terminal devices.
Smart Images
Figure CN117527712B_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to the field of data processing, and more specifically, to a Zigbee-based data manipulation method, apparatus, and computer-readable recording medium performed by a network device or terminal device. Background Technology
[0002] Zigbee is a low-speed, short-range wireless communication protocol. Its underlying media access layer and physical layer are based on the IEEE 802.15.4 standard. Zigbee green power, as part of the Zigbee wireless communication protocol, defines a compressed, secure, and highly optimized wireless transmission method for ultra-low-power devices.
[0003] Coordinators and terminal devices that communicate via Zigbee or Zigbee Green Power are characterized by low speed, low power consumption, low cost, reliability, and security.
[0004] With the increasing number of terminal devices, the channels shared by the terminal devices and the coordinator are becoming increasingly congested. When the congestion reaches a certain level, it leads to frequent data loss. This is particularly severe during data read and write operations on terminal devices.
[0005] Therefore, a method is needed to solve the above problems. Summary of the Invention
[0006] To address the aforementioned issues, this disclosure provides a Zigbee-based data manipulation method. According to this method, a network device can send a register write request to a terminal device, instructing the terminal device to write a corresponding trigger value. This allows the terminal device to send at least one set of data to be read at once, thereby avoiding the large number of read operations required in the prior art and ultimately preventing excessive occupation of channel resources shared by the terminal device and network devices (e.g., a coordinator).
[0007] This disclosure provides a Zigbee-based data operation method executed by a network device, comprising: in response to a data read request for reading at least one set of data from a first terminal device, sending a register write request to the first terminal device, the register write request instructing the first terminal device to write a trigger value to at least one bit in the register of the first terminal device corresponding to the at least one set of data, the trigger value being used to trigger the first terminal device to send the at least one set of data to the network device at once; and receiving the at least one set of data sent by the first terminal device in response to the trigger value.
[0008] According to an embodiment of this disclosure, the data operation method further includes: in response to a data write request for a plurality of data to the first terminal device, compressing the plurality of data, and sending the compressed plurality of data to the first terminal device.
[0009] According to an embodiment of this disclosure, before sending a register write request to the first terminal device in response to a data read request for reading at least one set of data from the first terminal device, the data operation method further includes: in response to receiving a data read request, determining whether the data read request is a data read request for reading at least one set of data from the first terminal device or a data read request for reading at least one set of data from the second terminal device.
[0010] According to an embodiment of this disclosure, when it is determined that the request to read data is a data read request to read at least one data of a second terminal device, the data operation method further includes: in response to the data read request to read at least one data of the second terminal device, sequentially sending a data read request for each of the at least one data to the second terminal device; and sequentially receiving data sent by the second terminal device according to the sequentially received data read requests.
[0011] This disclosure provides a Zigbee-based data operation method executed by a terminal device, comprising: receiving a register write request from a network device; writing a trigger value to at least one bit corresponding to at least one set of data in a register of the terminal device based on the register write request; and sending the at least one set of data to the network device at one time based on the trigger value.
[0012] According to an embodiment of this disclosure, the data operation method further includes: in response to receiving compressed multiple data from the network device, decompressing the compressed multiple data, and writing the decompressed multiple data into the terminal device.
[0013] This disclosure provides a network device, including: a first transmitting unit configured to send a register write request to the first terminal device in response to a data read request for reading at least one set of data from the first terminal device, the register write request instructing the first terminal device to write a trigger value to at least one bit in the register of the first terminal device corresponding to the at least one set of data, the trigger value being used to trigger the first terminal device to send the at least one set of data to the network device at once; and a first receiving unit configured to receive the at least one set of data sent by the first terminal device in response to the trigger value.
[0014] According to an embodiment of this disclosure, the network device further includes: a compression and transmission unit configured to compress the plurality of data in response to a data write request for the first terminal device, and to send the compressed plurality of data to the first terminal device.
[0015] According to an embodiment of this disclosure, prior to the first sending unit, the network device further includes a determining unit configured to, in response to receiving a request to read data, determine whether the request to read data is a data read request to read at least one set of data from a first terminal device or a data read request to read at least one set of data from a second terminal device.
[0016] According to an embodiment of this disclosure, when it is determined that the request to read data is a data read request to read at least one piece of data from a second terminal device, the network device further includes: a second sending unit configured to, in response to the data read request to read at least one piece of data from the second terminal device, sequentially send a data read request for each of the at least one pieces of data to the second terminal device; and a second receiving unit configured to, sequentially receive from the second terminal device data sent by the second terminal device according to the sequentially received data read requests.
[0017] This disclosure provides a terminal device, including: a receiving unit configured to receive a register write request from a network device; a writing unit configured to write a trigger value to at least one bit corresponding to at least one set of data in a register of the terminal device based on the register write request; and a sending unit configured to send the at least one set of data to the network device at one time based on the trigger value.
[0018] According to an embodiment of this disclosure, the terminal device further includes: a decompression and writing unit configured to decompress the compressed plurality of data received from the network device and write the decompressed plurality of data into the terminal device.
[0019] This disclosure provides a network device, including a processor and a memory storing computer-executable instructions that, when executed by the processor, cause the processor to perform the method described above.
[0020] This disclosure provides a terminal device, including a processor and a memory, the memory storing computer-executable instructions that, when executed by the processor, cause the processor to perform the method described above.
[0021] This disclosure provides a computer-readable recording medium storing computer-executable instructions, wherein the computer-executable instructions, when executed by a processor, cause the processor to perform the method described above.
[0022] This disclosure provides a Zigbee-based data operation method, apparatus, and computer-readable recording medium executed by a network device or a terminal device. In the method provided by this disclosure, the network device can send a register write request to the terminal device instructing the terminal device to write a corresponding trigger value. This allows the terminal device to send at least one set of data to be read at once, thereby avoiding numerous read operations as in the prior art and ultimately preventing excessive occupation of channel resources shared by the terminal device and the coordinator, thus avoiding data collisions in the air. Furthermore, since the method provided by this disclosure can execute different data operation methods for different terminal devices, it can adapt to different terminal device usage scenarios. Therefore, the method not only maximizes the optimization of read / write operations between the network device and the terminal device but also maximizes the read / write performance of the entire system, including the network device and multiple terminal devices. Attached Figure Description
[0023] To more clearly illustrate the technical solutions of the embodiments of this disclosure, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are merely some exemplary embodiments of this disclosure. For those skilled in the art, other drawings can be obtained based on these drawings without any creative effort.
[0024] Figure 1A A schematic diagram of a Zigbee-based network topology is shown;
[0025] Figure 1B A schematic diagram illustrating collisions in Zigbee-based data is shown.
[0026] Figure 2 A flowchart is shown of a Zigbee-based data manipulation method 200 performed by a network device according to an embodiment of the present disclosure;
[0027] Figure 3 A flowchart is shown of a Zigbee-based data manipulation method 300 executed by a terminal device according to an embodiment of the present disclosure;
[0028] Figure 4A A schematic diagram of an existing data reading method based on Zigbee is shown;
[0029] Figure 4BA schematic diagram of a data reading method according to an embodiment of the present disclosure is shown;
[0030] Figure 5A A schematic diagram of an existing data writing method based on Zigbee is shown;
[0031] Figure 5B A schematic diagram of a data writing method according to an embodiment of the present disclosure is shown;
[0032] Figure 6 A block diagram of a network device 600 according to an embodiment of the present disclosure is shown;
[0033] Figure 7 A block diagram of a terminal device 700 according to an embodiment of the present disclosure is shown;
[0034] Figure 8 A block diagram of another network device 800 according to an embodiment of the present disclosure is shown;
[0035] Figure 9 A block diagram of another terminal device 900 according to an embodiment of the present disclosure is shown;
[0036] Figure 10 A schematic diagram 1000 of a recording medium according to an embodiment of the present disclosure is shown. Detailed Implementation
[0037] To make the objectives, technical solutions, and advantages of the embodiments of this disclosure clearer, the technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this disclosure. All other embodiments obtained by those skilled in the art based on the described embodiments of this disclosure without creative effort are within the scope of protection of this disclosure.
[0038] Unless otherwise defined, the technical or scientific terms used in this disclosure shall have the ordinary meaning understood by one of ordinary skill in the art to which this disclosure pertains. The terms “first,” “second,” and similar terms used in this disclosure do not indicate any order, quantity, or importance, but are merely used to distinguish different components. Similarly, the terms “an,” “a,” or “the,” and similar terms do not indicate a quantity limitation, but rather indicate the presence of at least one. The terms “including,” “comprising,” or “containing,” and similar terms mean that the element or object preceding the word encompasses the elements or objects listed following the word and their equivalents, without excluding other elements or objects. The terms “connected,” “linked,” or similar terms are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. The terms “upper,” “lower,” “left,” and “right,” etc., are used only to indicate relative positional relationships, and these relative positional relationships may change accordingly when the absolute position of the described objects changes.
[0039] In existing technologies, Zigbee (including Zigbee Green Power) is a fixed-frequency wireless communication protocol. Once the network is created, it operates on the same channel until the coordinator actively changes the channel. The network topology is shown below. Figure 1A As shown.
[0040] When the number of terminal devices is small, communication is relatively smooth. However, as the number of devices increases, data collisions within the channel become more severe, leading to frequent data loss. This is especially problematic during device read / write operations, as the frequent data loss severely disrupts user operations.
[0041] As attached Figure 1B As shown, the light gray area represents the report data sent by the terminal device to the coordinator, and the dark gray area represents the data packets related to read / write (R / W) commands sent by the coordinator to the terminal device. When the channel becomes congested to a certain extent, data collisions will occur, leading to the loss of communication data (the dashed boxes and the crosses below the dashed boxes indicate that data collisions have occurred, resulting in data loss).
[0042] When users need to read and configure parameters of relevant terminal devices through the coordinator, the aforementioned interference will cause the user's operation to take a long time and have a low success rate, which will greatly reduce the user's experience and the user's acceptance of the relevant terminal devices.
[0043] To address the aforementioned issues, this disclosure provides a Zigbee-based data operation method executed by a network device. Because the method provided in this disclosure can send a register write request to the terminal device instructing it to write a corresponding trigger value, the terminal device can send at least one set of data to be read at once. This avoids the large number of read operations required in the prior art and ultimately prevents excessive occupation of channel resources shared by the terminal device and the coordinator, thus avoiding the occurrence of over-the-air data collisions.
[0044] The data manipulation methods provided in this disclosure will now be described in detail with reference to the accompanying drawings.
[0045] Figure 2 A flowchart of a Zigbee-based data manipulation method 200 performed by a network device according to an embodiment of the present disclosure is shown.
[0046] As an example, the network device could be the coordinator described above, such as a gateway. Alternatively, the network device could be any wired or wireless access point capable of reading data from and / or writing data to the end devices.
[0047] Reference Figure 2 In step S210, the network device may send a register write request to the first terminal device in response to a data read request for reading at least one set of data from the first terminal device.
[0048] The register write request can instruct the first terminal device to write a trigger value to at least one bit in the register of the first terminal device corresponding to the at least one set of data. The trigger value is used to trigger the first terminal device to send the at least one set of data to the network device at once.
[0049] According to embodiments of this disclosure, the aforementioned data read request may be initiated by the user based on actual needs, such as when the user needs to read or configure relevant data of the terminal device through a network device.
[0050] According to embodiments of this disclosure, the first terminal device can be any suitable type of terminal device.
[0051] As an example, the first terminal device can be a meter-type device, such as a voltmeter for measuring voltage, an ammeter for measuring current, a wattmeter for measuring power, a piezometer for simultaneously measuring voltage, current and power, and so on.
[0052] As another example, the first terminal device can be a sensor-type device, such as a temperature sensor for measuring temperature, a temperature and humidity sensor for measuring temperature and humidity, a speed sensor for measuring speed, and so on.
[0053] According to embodiments of this disclosure, the first terminal device can pre-group relevant data into the same group based on actual needs (e.g., service type). For example, for the aforementioned voltage-current ratio table, parameters related to voltage, current, and / or power can be pre-grouped. For instance, parameters related to the voltage of phases A, B, and C can be grouped into group 1; parameters related to the current of phases A, B, and C can be grouped into group 2; and parameters related to the power and device status of phases A, B, and C can be grouped into group 3. Then, in the first terminal device, a predetermined bit in a register (e.g., a trigger register) is associated with one of the groups 1 to 3, so that when a trigger value is written to the predetermined bit, the first terminal device can send all data within the corresponding group to the network device at once. The trigger value can be any suitable value, such as 1.
[0054] As an example, assume that group 1 is associated with the 7th bit in the trigger register, group 2 is associated with the 6th bit in the trigger register, and group 3 is associated with the 5th bit in the trigger register.
[0055] When a user wants to read some or all of the data in Groups 1, 2, and 3, the network device can send a register write request to the first terminal device, instructing the first terminal device to write a trigger value (x|0xe0) to its trigger register (where x represents a trigger register of the first terminal device, | represents an OR operation, and 0xe0 corresponds to binary 1110 0000). This trigger value (x|0xe0) sets the values of bits 7, 6, and 5 to 1. With the trigger value (x|0xe0), the first terminal device sends all the data in Groups 1, 2, and 3 to the network device at once. Specifically, the first terminal device sends parameters related to the voltage of phases A, B, and C; parameters related to the current of phases A, B, and C; and parameters related to the power and device status of phases A, B, and C. Finally, the network device selects some or all of the above parameter data as needed.
[0056] When a user wants to read some or all of the data in Group 1, the network device can send a register write request to the first terminal device, instructing the first terminal device to write a trigger value (x|0x80) (where x represents a trigger register of the first terminal device, | represents an OR operation, and 0x80 corresponds to binary 1000 0000) to its trigger register. This trigger value (x|0x80) indicates that the 7th bit is set to 1. With the trigger value (x|0x80), the first terminal device sends all the data in Group 1 to the network device at once; that is, the first terminal device sends the voltage-related parameters of phases A, B, and C to the network device all at once. Finally, the network device selects some or all of the above parameter data as needed.
[0057] Continue to refer to Figure 2 In step S220, the network device may receive the at least one set of data sent by the first terminal device in response to the trigger value.
[0058] As an example, a network device can receive three groups of data, namely group 1, group 2, and group 3, sent by a first terminal device in response to a trigger value (x|0xe0).
[0059] As another example, the network device may receive a group of data (Group 1) sent by the first terminal device in response to the trigger value (x|0x80).
[0060] According to an embodiment of this disclosure, before sending a register write request to the first terminal device in response to a data read request for reading at least one set of data from the first terminal device, the data operation method 200 may further include: in response to receiving a data read request, determining whether the data read request is a data read request for reading at least one set of data from the first terminal device or a data read request for reading at least one set of data from the second terminal device.
[0061] The aforementioned data reading request can be initiated by the user based on actual needs, such as when the user needs to read or configure relevant data on the terminal device through the network device.
[0062] Upon receiving the aforementioned request to read data, the network device needs to determine whether the request is a data read request to read at least one set of data from the first terminal device or a data read request to read at least one set of data from the second terminal device.
[0063] If it is determined that the request to read data is a data read request to read at least one set of data from the first terminal device, the network device will proceed according to the reference... Figure 2 The steps S210 and S220 are described to perform the data manipulation method.
[0064] If it is determined that the request to read data is a data read request to read at least one piece of data from the second terminal device, the data operation method 200 may further include: in response to the data read request to read at least one piece of data from the second terminal device, sequentially sending a data read request for each piece of data in the at least one piece of data to the second terminal device; and sequentially receiving data sent by the second terminal device according to the sequentially received data read requests.
[0065] As an example, the second terminal device can be any suitable type of terminal device, such as a terminal device that cannot cooperate with the network device to perform the above steps S210 and S220, such as a terminal device that cannot update its running code and therefore cannot cooperate with the network device to perform the above steps S210 and S220.
[0066] As an example, when the second terminal device is a temperature and humidity sensor, the network device can respond to data read requests for temperature and humidity data from the sensor by sequentially sending the temperature data read request and the humidity data read request to the sensor. Then, the network device first receives the temperature data sent by the temperature and humidity sensor based on the received temperature data read request, and then receives the humidity data sent by the temperature and humidity sensor based on the received humidity data read request.
[0067] According to embodiments of this disclosure, referring to Figure 2 The described data manipulation method 200 may further include, in response to a data write request for a plurality of data to the first terminal device, compressing the plurality of data and sending the compressed plurality of data to the first terminal device.
[0068] As an example, network devices can compress multiple data sets using algorithms such as Run-Length Encoding (RLE), Huffman coding, and XOR. Alternatively, network devices can compress multiple data sets by incorporating more useful data into a single communication. For instance, suppose a communication data set is 100 bits in size, but only 20 bits are actually useful in a given communication, leaving 80 bits set to 0. In this case, other useful data can be used to occupy the remaining 80 bits, thus compressing multiple data sets into a single communication. Compared to existing methods that do not compress multiple data sets, including setting the remaining 80 bits to 0, this significantly reduces the number of data interactions between the network device and the terminal device, thereby greatly reducing the time spent writing data.
[0069] As can be seen from the data operation methods provided in this disclosure, the methods provided in this disclosure execute different data operation methods for different terminal devices, thereby enabling the methods provided in this disclosure to adapt to different terminal device usage scenarios. Therefore, the network device provided in this disclosure may include a module related to the read / write task pool, which manages the read / write tasks of all terminal devices. When a read / write operation needs to be performed on a certain terminal device, the read / write strategy of the terminal device can be determined first through the device identifier (e.g., the device type identifier). Figure 2 The described steps S210 and S220 involve reading operations on the terminal device (or performing reading operations on the terminal device according to other steps included in the data operation method 200 described above), and then the data to be operated on (e.g., at least one piece of data or at least one set of data mentioned above) is obtained from the task pool according to the strategy. It is evident that the method provided by this disclosure can flexibly select read / write strategies based on the characteristics of different terminal devices. Furthermore, this approach not only maximizes the optimization of read / write operations between network devices and terminal devices but also maximizes the read / write performance of the entire system, including network devices and multiple terminal devices. In addition, since the method provided by this disclosure can execute different data operation methods for different terminal devices, it eliminates the need for all terminal devices to adopt a unified read / write strategy, thus reducing the uniformity requirements of terminal devices. This is beneficial not only for the use of older terminal devices but also for the continuous integration of new terminal devices into the interaction with network devices.
[0070] Combining description Figure 2 This disclosure describes in detail a Zigbee-based data operation method performed by a network device. The method described above can send a register write request to a terminal device, instructing the terminal device to write a corresponding trigger value. This allows the terminal device to send at least one set of data to be read at once, thereby avoiding numerous read operations as in the prior art and ultimately preventing excessive occupation of channel resources shared by the terminal device and the coordinator, thus avoiding data collisions in the air. Furthermore, since the method described above can execute different data operation methods for different terminal devices, it can adapt to different terminal device usage scenarios. Therefore, the method described above not only maximizes the optimization of read and write operations between the network device and the terminal device, but also maximizes the read and write performance of the entire system, including the network device and multiple terminal devices.
[0071] In addition to providing the aforementioned Zigbee-based data manipulation method performed by a network device, this disclosure also provides a Zigbee-based data manipulation method performed by a terminal device. The following will refer to the appendix... Figure 3 This will be explained.
[0072] Figure 3 A flowchart of a Zigbee-based data manipulation method 300 executed by a terminal device according to an embodiment of the present disclosure is shown.
[0073] According to embodiments of this disclosure, the terminal device can be any suitable type of terminal device, as described above. Figure 2 The first terminal device described.
[0074] As an example, the terminal device can be a meter-type device, such as a voltmeter for measuring voltage, an ammeter for measuring current, a wattmeter for measuring power, a piezometer for simultaneously measuring voltage, current and power, and so on.
[0075] As another example, the terminal device can be a sensor-type device, such as a temperature sensor for measuring temperature, a temperature and humidity sensor for measuring temperature and humidity, a speed sensor for measuring speed, and so on.
[0076] Reference Figure 3 In step S310, the terminal device may receive a register write request from the network device. In step S320, the terminal device may, based on the register write request, write a trigger value to at least one bit in the terminal device's register corresponding to at least one set of data.
[0077] As an example, when the terminal device is the aforementioned pressure-current rate table, the pressure-current rate table can receive a write request from the network device instructing it to write a trigger value (x|0xe0) to its trigger register. Based on this register write request, the pressure-current rate table writes the trigger value (x|0xe0) to bits 7, 6, and 5 of the register in the pressure-current rate table, that is, sets the values of bits 7, 6, and 5 to 1.
[0078] In step S330, the terminal device may send the at least one set of data to the network device at once based on the trigger value.
[0079] As an example, when the terminal device is the aforementioned pressure-current ratio meter, the pressure-current ratio meter can send three sets of data (group 1, group 2, and group 3) to the network device at once based on the aforementioned trigger value (x|0xe0). That is, it can send to the network device parameters related to the voltage of phases A, B, and C, parameters related to the current of phases A, B, and C, and parameters related to the power and equipment status of phases A, B, and C at once.
[0080] According to an embodiment of this disclosure, the data operation method 300 may further include: in response to receiving compressed data from the network device, decompressing the compressed data and writing the decompressed data into the terminal device.
[0081] As an example, a terminal device can decompress multiple compressed data sets using one of the compression algorithms corresponding to the compression method used by the network device, such as RLE, Huffman coding, or XOR. Alternatively, the terminal device can decompress multiple data sets from 100-bit communication data sets or as described below. Figure 5B The method shown is to extract multiple useful data from 60 bits of communication data to decompress multiple compressed data.
[0082] Combining description Figure 3 This disclosure describes in detail a Zigbee-based data operation method performed by a terminal device. The method described above can send at least one set of data to be read to the network device at once in response to a register write request from the network device, thereby avoiding numerous read operations as in the prior art and ultimately preventing excessive consumption of channel resources shared by the terminal device and the coordinator, thus avoiding over-the-air data collisions. This not only maximizes the optimization of read and write operations between the network device and the terminal device, but also maximizes the read and write performance of the entire system, including the network device and multiple terminal devices.
[0083] To make the data manipulation methods 200 and 300 provided in this disclosure clearer, the data manipulation methods 200 and 300 provided in this disclosure will be explained in the form of examples below.
[0084] Figure 4A A schematic diagram of an existing data reading method based on ZigBee is shown; Figure 4B A schematic diagram of a data reading method according to an embodiment of the present disclosure is shown.
[0085] Assuming no interference in the air, all communications have a 100% success rate.
[0086] Suppose we want to read the values of voltage, current, and power from the pressure-current ratio table above.
[0087] Reference Figure 4A In existing data reading methods, the reading process is as follows:
[0088] First, regarding the reading of parameters related to the voltage of phases A, B, and C, the data reading operation process is as follows:
[0089] In the first step, the terminal device sends a report to the coordinator to report the current status of the terminal device or the relevant data collected.
[0090] In the second step, the coordinator sends a command to the terminal device to read parameters related to the voltage of phase A, i.e., read A().
[0091] In step 3, the terminal device responds to the read A() command by sending a response message to the coordinator containing parameters related to the A-phase voltage, i.e., read response(). At this point, the parameters related to the A-phase voltage have been read.
[0092] After a duty cycle, the next steps are executed. The length of the duty cycle depends on the type of terminal device. For example, the duty cycle of a meter is usually in the range of seconds (e.g., 5 seconds, 10 seconds), while the duty cycle of a sensor is usually in the range of minutes (e.g., 1 minute, 2 minutes).
[0093] In step 4, the terminal device sends a report to the coordinator to report the current status of the terminal device or the relevant data collected.
[0094] In step 5, the coordinator sends a command to the terminal device to read parameters related to the B-phase voltage, i.e., read B().
[0095] In step 6, the terminal device responds to the aforementioned read B() command by sending a response message to the coordinator containing parameters related to the B-phase voltage, i.e., read response(). At this point, the parameters related to the B-phase voltage have been read.
[0096] Then, after one duty cycle, the following steps will begin.
[0097] In step 7, the terminal device sends a report to the coordinator to report the current status of the terminal device or the relevant data collected.
[0098] In step 8, the coordinator sends a command to the terminal device to read parameters related to the C-phase voltage, i.e., read C().
[0099] In step 9, the terminal device responds to the aforementioned read C() command by sending a response message to the coordinator containing parameters related to the C-phase voltage, i.e., read response(). At this point, the parameters related to the C-phase voltage have been read.
[0100] After the aforementioned nine steps plus two duty cycles, the existing data reading method can then read the voltage-related parameters for phases A, B, and C. Then, after another duty cycle, it begins reading the current or power-related parameters for phases A, B, and C. Since the steps for reading the current or power-related parameters for phases A, B, and C are similar to those for reading the voltage-related parameters, they will not be repeated here for the sake of brevity.
[0101] In other words, the existing data reading method requires 27 steps plus 8 duty cycles to read the parameters related to the voltage, current, and power of phases A, B, and C. This is very time-consuming.
[0102] Reference Figure 4B In the data reading method provided in this disclosure, the terminal device has grouped the voltage-related parameters of the three phases A, B and C into group 1, the current-related parameters of the three phases A, B and C into group 2, and the power-related parameters of the three phases A, B and C into group 3. Furthermore, the terminal device has associated group 1 with the 7th bit in the trigger register, group 2 with the 6th bit in the trigger register, and group 3 with the 5th bit in the trigger register.
[0103] Under the above circumstances, the steps for reading the voltage, current, and power values from the pressure-current ratio table are as follows:
[0104] In the first step, the terminal device sends a report to the coordinator to report the current status of the terminal device or the relevant data collected.
[0105] In step 2, the coordinator sends a command to the terminal device to write the trigger value (x|0xe0) to the corresponding bit in the trigger register (trig), i.e., write tri(x|0xe0). Figure 2 Regarding the description of step S210.
[0106] In step 3, the terminal device responds to the above write tri(x|0xe0) command by sending a successful write message (i.e., write ACK) and a report message containing parameters related to the voltage, current, and power of phases A, B, and C, namely report 1, 2, 3(). Figure 2 Regarding the description of step S220.
[0107] Thus, the data reading method provided in this disclosure can read parameters related to the voltage, current, and power of phases A, B, and C in just three steps. This significantly reduces data reading time and shortens data transmission time in the air, thereby reducing interference. Furthermore, since the data reading method provided in this disclosure uses a report format instead of the previous reading method, it further reduces data reading time and significantly improves the success rate. Therefore, according to the data reading method provided in this disclosure, users can quickly read back the current parameters of the terminal device before configuring the terminal device's parameters, reducing user waiting time and greatly improving the user experience. Additionally, it should be noted that if other data combinations need to be read, the terminal device only needs to write the corresponding bits. Therefore, compared to existing reading methods, a large number of communication interactions are eliminated. The greater the interference present in the air, the greater the performance improvement of the data reading method provided in this disclosure.
[0108] Figure 5A A schematic diagram of an existing data writing method based on Zigbee is shown; Figure 5B A schematic diagram of a data writing method according to an embodiment of the present disclosure is shown.
[0109] Assuming no air interference, all communications have a 100% success rate. Assume a single communication data payload has a maximum length of 100 bits, while the data to be written, A, B, and C, are each 60 bits in length.
[0110] Reference Figure 5A In the existing data writing method, the process is as follows:
[0111] In the first step, the terminal device sends a report to the coordinator to report the current status of the terminal device or the relevant data collected.
[0112] In the second step, the coordinator sends a command to the terminal device to write data related to A, namely write A(). In this communication, data A occupies 60 bits, and the remaining 40 bits are insufficient to hold data B or C. Therefore, this operation can only write data A.
[0113] In step 3, the terminal device responds to the write A() command by sending a successful write message (i.e., write ACK) to the coordinator. At this point, data A has been written.
[0114] After a duty cycle, the next steps are executed. The length of the duty cycle depends on the type of terminal device. For example, the duty cycle of a meter is usually in the range of seconds (e.g., 5 seconds, 10 seconds), while the duty cycle of a sensor is usually in the range of minutes (e.g., 1 minute, 2 minutes).
[0115] In step 4, the terminal device sends a report to the coordinator to report the current status of the terminal device or the relevant data collected.
[0116] In step 5, the coordinator sends a command to the terminal device to write data B, i.e., write B(). In this communication, data B occupies 60 bits, and the remaining 40 bits are insufficient to hold data C. Therefore, this operation can only write data B.
[0117] In step 6, the terminal device responds to the write B() command by sending a successful write message (i.e., write ACK) to the coordinator. At this point, data B has been written.
[0118] Then, after one duty cycle, the following steps will begin.
[0119] In step 7, the terminal device sends a report to the coordinator to report the current status of the terminal device or the relevant data collected.
[0120] In step 8, the coordinator sends a command to the terminal device to write data C, i.e., write C(), where the data C to be written in this communication data occupies 60 bits.
[0121] In step 9, the terminal device responds to the write C() command by sending a successful write message (i.e., write ACK) to the coordinator. At this point, data C has been written.
[0122] Therefore, the existing data writing method requires nine steps plus two duty cycles before data A, B, and C can be written. Since the write operation is performed one record at a time, the entire configuration process for the terminal devices is very time-consuming. For example, testing showed that configuring parameters for 14-15 terminal devices (assuming a duty cycle of 5 seconds) would take 20-30 minutes. In other words, the existing data writing method is extremely time-consuming.
[0123] Reference Figure 5B The data writing method provided in this disclosure follows the following process:
[0124] In the first step, the terminal device sends a report to the coordinator to report the current status of the terminal device or the relevant data collected.
[0125] In step 2, the coordinator compresses data A, B, and C (using the compression algorithm described above) and sends the compressed data as a single communication data message. This message contains, for example, 60 bits of data (if data A, B, and C are compressed to 20 bits each). Then, the coordinator sends a command to the terminal device to write data A, B, and C, i.e., `write A,B,C()`. Upon receiving this communication data, the terminal device decompresses the data and writes the decompressed data A, B, and C into its own memory. (See reference...) Figure 2 and Figure 3 This describes the compression and decompression of multiple data sets.
[0126] In step 3, the terminal device responds to the above write A, B, C() commands by sending a successful write message (i.e., write ACK) to the coordinator.
[0127] Thus, data A, B, and C have been written in one go. It can be seen that the data writing method provided in this disclosure replaces the previous single-write method with a combined writing approach. This not only greatly shortens the data writing time but also reduces the data transmission time in the air, thereby reducing interference.
[0128] In addition to providing the aforementioned data manipulation methods, this disclosure also provides the corresponding equipment, which will be discussed in the following sections. Figure 6 and Figure 7 This needs to be explained.
[0129] Figure 6 A block diagram of a network device 600 according to an embodiment of this disclosure is shown. The above description of the Zigbee-based data operation method performed by the network device also applies to device 600, unless otherwise explicitly stated.
[0130] Reference Figure 6 The network device 600 may include a first transmitting unit 610 and a first receiving unit 620.
[0131] The first sending unit 610 can be configured to send a register write request to the first terminal device in response to a data read request for reading at least one set of data from the first terminal device. The register write request instructs the first terminal device to write a trigger value to at least one bit in the register of the first terminal device corresponding to the at least one set of data. The trigger value is used to trigger the first terminal device to send the at least one set of data to the network device at once.
[0132] According to embodiments of this disclosure, the aforementioned data read request may be initiated by the user based on actual needs, such as when the user needs to read or configure relevant data of the terminal device through a network device.
[0133] According to embodiments of this disclosure, the first terminal device can be any suitable type of terminal device.
[0134] As an example, the first terminal device can be a meter-type device, such as a voltmeter for measuring voltage, an ammeter for measuring current, a wattmeter for measuring power, a piezometer for simultaneously measuring voltage, current and power, and so on.
[0135] As another example, the first terminal device can be a sensor-type device, such as a temperature sensor for measuring temperature, a temperature and humidity sensor for measuring temperature and humidity, a speed sensor for measuring speed, and so on.
[0136] According to embodiments of this disclosure, the first terminal device can pre-group relevant data into the same group based on actual needs (e.g., service type). For example, for the aforementioned voltage-current ratio table, parameters related to voltage, current, and / or power can be pre-grouped. For instance, parameters related to the voltage of phases A, B, and C can be grouped into group 1; parameters related to the current of phases A, B, and C can be grouped into group 2; and parameters related to the power and device status of phases A, B, and C can be grouped into group 3. Then, in the first terminal device, a predetermined bit in a register (e.g., a trigger register) is associated with one of the groups 1 to 3, so that when a trigger value is written to the predetermined bit, the first terminal device can send all data within the corresponding group to the network device at once. The trigger value can be any suitable value, such as 1.
[0137] As an example, assume that group 1 is associated with the 7th bit in the trigger register, group 2 is associated with the 6th bit in the trigger register, and group 3 is associated with the 5th bit in the trigger register.
[0138] When a user wants to read some or all of the data in Groups 1, 2, and 3, the network device can send a register write request to the first terminal device, instructing the first terminal device to write a trigger value (x|0xe0) to its trigger register (where x represents a trigger register of the first terminal device, | represents an OR operation, and 0xe0 corresponds to binary 1110 0000). This trigger value (x|0xe0) sets the values of bits 7, 6, and 5 to 1. With the trigger value (x|0xe0), the first terminal device sends all the data in Groups 1, 2, and 3 to the network device at once. Specifically, the first terminal device sends parameters related to the voltage of phases A, B, and C; parameters related to the current of phases A, B, and C; and parameters related to the power and device status of phases A, B, and C. Finally, the network device selects some or all of the above parameter data as needed.
[0139] When a user wants to read some or all of the data in Group 1, the network device can send a register write request to the first terminal device, instructing the first terminal device to write a trigger value (x|0x80) (where x represents a trigger register of the first terminal device, | represents an OR operation, and 0x80 corresponds to binary 1000 0000) to its trigger register. This trigger value (x|0x80) indicates that the 7th bit is set to 1. With the trigger value (x|0x80), the first terminal device sends all the data in Group 1 to the network device at once; that is, the first terminal device sends the voltage-related parameters of phases A, B, and C to the network device all at once. Finally, the network device selects some or all of the above parameter data as needed.
[0140] Continue to refer to Figure 6 The first receiving unit 620 can be configured to receive the at least one set of data sent by the first terminal device in response to the trigger value.
[0141] As an example, a network device can receive three groups of data, namely group 1, group 2, and group 3, sent by a first terminal device in response to a trigger value (x|0xe0).
[0142] As another example, the network device may receive a group of data (Group 1) sent by the first terminal device in response to the trigger value (x|0x80).
[0143] According to an embodiment of this disclosure, prior to the first sending unit, the network device further includes a determining unit, which can be configured to determine, in response to receiving a request to read data, whether the request to read data is a data read request to read at least one set of data from a first terminal device or a data read request to read at least one set of data from a second terminal device.
[0144] The aforementioned data reading request can be initiated by the user based on actual needs, such as when the user needs to read or configure relevant data on the terminal device through the network device.
[0145] According to an embodiment of this disclosure, when it is determined that the request to read data is a data read request to read at least one piece of data from a second terminal device, the network device further includes: a second sending unit and a second receiving unit, wherein the second sending unit can be configured to, in response to the data read request to read at least one piece of data from the second terminal device, sequentially send a data read request for each piece of the at least one piece of data to the second terminal device; the second receiving unit can be configured to, sequentially receive from the second terminal device data sent by the second terminal device according to the sequentially received data read requests.
[0146] As an example, the second terminal device can be any suitable type of terminal device.
[0147] As an example, when the second terminal device is a temperature and humidity sensor, the network device can respond to data read requests for temperature and humidity data from the sensor by sequentially sending the temperature data read request and the humidity data read request to the sensor. Then, the network device first receives the temperature data sent by the temperature and humidity sensor based on the received temperature data read request, and then receives the humidity data sent by the temperature and humidity sensor based on the received humidity data read request.
[0148] According to an embodiment of this disclosure, the network device 600 may further include: a compression sending unit, which may be configured to compress the plurality of data in response to a data write request for the first terminal device and send the compressed plurality of data to the first terminal device.
[0149] As an example, network devices can compress multiple data sets using algorithms such as Run-Length Encoding (RLE), Huffman coding, and XOR. Alternatively, network devices can compress multiple data sets by incorporating more useful data into a single communication. For instance, suppose a communication data set is 100 bits in size, but only 20 bits are actually useful in a given communication, leaving 80 bits set to 0. In this case, other useful data can be used to occupy the remaining 80 bits, thus compressing multiple data sets into a single communication. Compared to existing methods that do not compress multiple data sets, including setting the remaining 80 bits to 0, this significantly reduces the number of data interactions between the network device and the terminal device, thereby greatly reducing the time spent writing data.
[0150] As can be seen from the network device provided in this disclosure, the network device performs different data operations for different terminal devices, thereby enabling the network device to adapt to different terminal device usage scenarios. Therefore, the network device provided in this disclosure may include a module related to the read / write task pool, which manages the read / write tasks of all terminal devices. When a read / write operation is required on a certain terminal device, the read / write strategy of the terminal device can be determined first through the device identifier (e.g., the device type identifier), and then the data to be operated on (e.g., at least one of the aforementioned data or at least one set of the aforementioned data) can be obtained from the task pool according to the strategy. It is evident that the network device provided in this disclosure can flexibly select read / write strategies based on the characteristics of different terminal devices. Furthermore, this approach not only maximizes the optimization of read / write operations between the network device and the terminal device, but also maximizes the optimization of the read / write performance of the entire system, including the network device and multiple terminal devices. Furthermore, since the network device provided in this disclosure can perform different data operations for different terminal devices, the network device provided in this disclosure does not require all terminal devices to adopt a unified read and write strategy, and the uniformity requirements of terminal devices are low. This is not only beneficial for the use of old terminal devices, but also for the continuous integration of new terminal devices into the interaction with the network device.
[0151] Combining description Figure 6The network device 600 provided in this disclosure is described in detail. The network device provided in this disclosure can send a register write request to a terminal device, instructing the terminal device to write a corresponding trigger value. This allows the terminal device to send at least one set of data to be read at once, thereby avoiding a large number of read operations as in the prior art, and ultimately avoiding excessive occupation of channel resources shared by the terminal device and the coordinator, thus preventing data collisions in the air. Furthermore, since the network device provided in this disclosure can execute different data operation methods for different terminal devices, it can adapt to different terminal device usage scenarios. Therefore, the method provided in this disclosure can not only maximize the optimization of read and write operations between the network device and the terminal device, but also maximize the read and write performance of the entire system, including the network device and multiple terminal devices.
[0152] Figure 7 A block diagram of a terminal device 700 according to an embodiment of this disclosure is shown. The description above of the Zigbee-based data operation method performed by the terminal device also applies to device 700, unless otherwise explicitly stated.
[0153] According to embodiments of this disclosure, the terminal device 700 can be any suitable type of terminal device, as described above. Figure 2 The first terminal device described.
[0154] As an example, the terminal device can be a meter-type device, such as a voltmeter for measuring voltage, an ammeter for measuring current, a wattmeter for measuring power, a piezometer for simultaneously measuring voltage, current and power, and so on.
[0155] As another example, the terminal device can be a sensor-type device, such as a temperature sensor for measuring temperature, a temperature and humidity sensor for measuring temperature and humidity, a speed sensor for measuring speed, and so on.
[0156] Reference Figure 7 The terminal device 700 may include a receiving unit 710, a writing unit 720, and a sending unit 730.
[0157] The receiving unit 710 can be configured to receive a register write request from the network device. The writing unit 720 can be configured to write a trigger value to at least one bit corresponding to at least one set of data in the register of the terminal device based on the register write request.
[0158] As an example, when the terminal device is the aforementioned pressure-current rate table, the pressure-current rate table can receive a write request from the network device instructing it to write a trigger value (x|0xe0) to its trigger register. Based on this register write request, the pressure-current rate table writes the trigger value (x|0xe0) to bits 7, 6, and 5 of the register in the pressure-current rate table, that is, sets the values of bits 7, 6, and 5 to 1.
[0159] The sending unit 730 can be configured to send the at least one set of data to the network device at once based on the trigger value.
[0160] As an example, when the terminal device is the aforementioned pressure-current ratio meter, the pressure-current ratio meter can send three sets of data (group 1, group 2, and group 3) to the network device at once based on the aforementioned trigger value (x|0xe0). That is, it can send to the network device parameters related to the voltage of phases A, B, and C, parameters related to the current of phases A, B, and C, and parameters related to the power and equipment status of phases A, B, and C at once.
[0161] According to an embodiment of this disclosure, the terminal device 700 may further include: a decompression and writing unit, which may be configured to decompress the compressed plurality of data and write the decompressed plurality of data into the terminal device in response to receiving compressed plurality of data from the network device.
[0162] As an example, a terminal device can decompress multiple compressed data sets using one of the compression algorithms corresponding to the compression method used by the network device, such as RLE, Huffman coding, or XOR. Alternatively, the terminal device can also decompress multiple data sets from 100 bits of communication data or data about... Figure 5B The method shown is to extract multiple useful data from 60 bits of communication data to decompress multiple compressed data.
[0163] Combining description Figure 7 The terminal device 700 provided in this disclosure is described in detail. The terminal device provided in this disclosure can, in response to a register write request from a network device, send at least one set of data to be read to the network device at once, thereby avoiding a large number of read operations as in the prior art, and ultimately avoiding excessive occupation of channel resources shared by the terminal device and the coordinator, thus preventing the occurrence of over-the-air data collisions. This not only maximizes the optimization of read and write operations between the network device and the terminal device, but also maximizes the read and write performance of the entire system, including the network device and multiple terminal devices.
[0164] It should be noted that although the network device 600 and terminal device 700 are described above as units or modules for performing corresponding processes, those skilled in the art will understand that the processes performed by each unit or module can also be performed without any specific unit or module division in the network device 600 or terminal device 700, or without clear boundaries between the units or modules. Furthermore, the network device 600 and terminal device 700 described above are not limited to including the units or modules described above, but may also include other units or modules (e.g., storage modules, etc.) as needed, or the above modules may be combined.
[0165] In addition to the network device 600 and terminal device 700 described above, this disclosure also provides another network device 800 and terminal device 900. These will be explained below.
[0166] Figure 8 A block diagram of another network device 800 according to an embodiment of the present disclosure is shown.
[0167] See Figure 8 The network device 800 may include a processor 801 and a memory 802. Both the processor 801 and the memory 802 can be connected via a bus 803.
[0168] Processor 801 can perform various actions and processes according to the program stored in memory 802. Specifically, processor 801 can be an integrated circuit chip with signal processing capabilities. The processor can be a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), off-the-shelf programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component. It can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor, and can be based on x86 architecture or ARM architecture.
[0169] Memory 802 stores computer instructions that, when executed by processor 801, implement the aforementioned data manipulation methods. Memory 802 may be volatile memory or non-volatile memory, or may include both. Non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory may be random access memory (RAM), which serves as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct memory bus random access memory (DR RAM). It should be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.
[0170] Figure 9 A block diagram of another terminal device 900 according to an embodiment of the present disclosure is shown.
[0171] See Figure 9 The terminal device 900 may include a processor 901 and a memory 902. Both the processor 901 and the memory 902 can be connected via a bus 903.
[0172] Processor 901 can perform various actions and processes according to the program stored in memory 902. Specifically, processor 901 can be an integrated circuit chip with signal processing capabilities. The processor can be a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), off-the-shelf programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component. It can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor, and can be based on x86 architecture or ARM architecture.
[0173] Memory 902 stores computer instructions that, when executed by processor 901, implement the aforementioned data manipulation methods. Memory 902 may be volatile memory or non-volatile memory, or may include both. Non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory may be random access memory (RAM), which serves as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct memory bus random access memory (DR RAM). It should be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.
[0174] According to yet another embodiment of this disclosure, a computer-readable recording medium is also provided. Figure 10 A schematic diagram 1000 of a recording medium according to an embodiment of the present disclosure is shown.
[0175] like Figure 10 As shown, the computer recording medium 1020 stores computer-executable instructions 1010. When the computer-executable instructions 1010 are executed by a processor, the method described with reference to the above figures according to embodiments of the present disclosure can be performed. The computer-readable recording medium in the embodiments of the present disclosure may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory may be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct memory bus random access memory (DRRAM). It should be noted that the memories described herein are intended to include, but are not limited to, these and any other suitable types of memories.
[0176] It should be noted that the flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing at least one executable instruction for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.
[0177] In general, the various exemplary embodiments of this disclosure can be implemented in hardware or dedicated circuitry, software, firmware, logic, or any combination thereof. Some aspects can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device. When aspects of embodiments of this disclosure are illustrated or described as block diagrams, flowcharts, or using some other graphical representation, it will be understood that the blocks, apparatuses, systems, techniques, or methods described herein can be implemented as non-limiting examples in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.
[0178] The exemplary embodiments of this disclosure described in detail above are merely illustrative and not restrictive. Those skilled in the art will understand that various modifications and combinations can be made to these embodiments or their features without departing from the principles and spirit of this disclosure, and such modifications should fall within the scope of this disclosure.
Claims
1. A Zigbee-based data manipulation method executed by a network device, comprising: In response to a data read request for reading at least one set of data from a first terminal device, a register write request is sent to the first terminal device. The register write request instructs the first terminal device to write a trigger value to at least one bit in the register of the first terminal device corresponding to the at least one set of data. The trigger value is used to trigger the first terminal device to send the at least one set of data to the network device at once. as well as Receive the at least one set of data sent by the first terminal device in response to the trigger value.
2. The data manipulation method as described in claim 1, further comprising: In response to a data write request for multiple data items to the first terminal device, the multiple data items are compressed, and the compressed multiple data items are sent to the first terminal device.
3. The data manipulation method as described in claim 1, wherein, Before sending a register write request to the first terminal device in response to a data read request for reading at least one set of data from the first terminal device, the data operation method further includes: In response to receiving a request to read data, determine whether the request to read data is a data read request to read at least one set of data from a first terminal device or a data read request to read at least one set of data from a second terminal device.
4. The data operation method as described in claim 3, wherein, when it is determined that the request to read data is a data read request to read at least one piece of data from a second terminal device, the data operation method further includes: In response to a data read request for reading at least one piece of data from a second terminal device, a data read request for each piece of data in the at least one piece of data is sequentially sent to the second terminal device; as well as The second terminal device sequentially receives data sent by the second terminal device according to the data read requests received sequentially.
5. A Zigbee-based data manipulation method executed by a terminal device, comprising: Receive register write requests from the network device; Based on the register write request, a trigger value is written to at least one bit corresponding to at least one set of data in the register of the terminal device; as well as Based on the trigger value, at least one set of data is sent to the network device at once.
6. The data manipulation method as described in claim 5, further comprising: In response to receiving compressed data from the network device, the compressed data is decompressed and the decompressed data is written into the terminal device.
7. A network device, comprising: The first sending unit is configured to send a register write request to the first terminal device in response to a data read request for reading at least one set of data from the first terminal device. The register write request instructs the first terminal device to write a trigger value to at least one bit in the register of the first terminal device corresponding to the at least one set of data. The trigger value is used to trigger the first terminal device to send the at least one set of data to the network device at one time. as well as The first receiving unit is configured to receive the at least one set of data sent by the first terminal device in response to the trigger value.
8. The network device of claim 7, further comprising: The compression sending unit is configured to compress the plurality of data in response to a data write request to the first terminal device and send the compressed plurality of data to the first terminal device.
9. The network device of claim 7, further comprising: The determining unit is configured to, before sending a register write request to the first terminal device in response to a data read request for reading at least one set of data from the first terminal device, determine, in response to receiving a data read request, whether the data read request is a data read request for reading at least one set of data from the first terminal device or a data read request for reading at least one set of data from the second terminal device.
10. The network device of claim 9, further comprising: The second sending unit is configured to, in response to a data read request for reading at least one data of the second terminal device, sequentially send a data read request for each of the at least one data to the second terminal device when it is determined that the request for reading data is a data read request for reading at least one data of the second terminal device. as well as The second receiving unit is configured to, when determining that the request to read data is a data read request to read at least one piece of data from the second terminal device, sequentially receive data sent by the second terminal device according to the sequentially received data read requests.
11. A terminal device, comprising: The receiving unit is configured to receive register write requests from the network device; The writing unit is configured to write a trigger value to at least one bit corresponding to at least one set of data in the register of the terminal device based on the register write request. as well as The sending unit is configured to send the at least one set of data to the network device at one time based on the trigger value.
12. The terminal device as described in claim 11, further comprising: The decompression and writing unit is configured to decompress the compressed data and write the decompressed data into the terminal device in response to receiving compressed data from the network device.
13. A network device, comprising: processor, and A memory storing computer-executable instructions that, when executed by a processor, cause the processor to perform the method as described in any one of claims 1-4.
14. A terminal device, comprising: processor, and A memory storing computer-executable instructions that, when executed by a processor, cause the processor to perform the method as described in any one of claims 5-6.
15. A computer-readable recording medium storing computer-executable instructions, wherein, The computer-executable instructions, when executed by the processor, cause the processor to perform the method as described in any one of claims 1-4 and 5-6.