A method and related apparatus for copying datasets

Abstract

This application discloses a data collection method and related apparatus. The method includes: if a data collection instruction is received from an IoT server, sending a wake-up frame and a data collection instruction frame carrying relevant information of the host device to multiple slave devices; wherein, the relevant information includes multiple contention reporting windows; if a data collection data frame is received from a target slave device among the multiple slave devices, sending a data collection response frame to the target slave device according to the slave network identifier of the target slave device carried in the data collection data frame; if a contention reporting data frame carrying the slave network identifier is received from the target slave device in response to the data collection response frame based on multiple contention reporting windows, sending a contention reporting response frame to the target slave device; if the contention reporting response frame carries the slave network identifier, it is determined that the target host device has successfully collected data from the target slave device. In this method, the slave devices do not need to remain in a wake-up state continuously, reducing the power consumption of the slave devices and saving power.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method and related apparatus for data collection. Background Technology

[0002] With the widespread application of long-range wireless communication technology and the continuous development of IoT technology, more and more smart devices are realizing IoT through long-range wireless communication control systems. Currently, master devices and slave devices are connected via long-range wireless communication. Typically, slave devices autonomously upload data to the master device via long-range wireless communication, and the master device then uploads the acquired data to the IoT server via mobile communication.

[0003] However, the aforementioned method of slave devices autonomously uploading data to the host device via long-distance wireless communication often requires the slave devices to remain in a constantly awake state so that they can frequently upload data autonomously. This leads to a sharp increase in the power consumption of the slave devices, which not only wastes the power of the slave devices but also results in a poor user experience. Summary of the Invention

[0004] In view of this, embodiments of this application provide a method and related apparatus for data collection, which eliminates the need for the slave device to remain in a constantly awake state, thereby reducing the power consumption of the slave device, saving power, and improving the user experience of the slave device.

[0005] In a first aspect, embodiments of this application provide a method for data copying, applied to a target host device, the method comprising:

[0006] If a data collection instruction is received from the IoT server, a wake-up frame and a data collection instruction frame are sent to multiple slave devices; the data collection instruction frame carries relevant information about the target host device, including multiple competing reporting windows;

[0007] If a data collection data frame is received from a target slave device among the plurality of slave devices, a data collection response frame is sent to the target slave device according to the slave network identifier of the target slave device carried in the data collection data frame;

[0008] If a contention reporting data frame is received from the target slave device in response to the data collection response frame based on the multiple contention reporting windows, a contention reporting response frame is sent to the target slave device; the contention reporting data frame carries the slave network identifier;

[0009] If the contention reporting response frame carries the slave network identifier, it is determined that the target host device has successfully collected data for the target slave device.

[0010] Optionally, the method further includes:

[0011] If no contention reporting data frame is received within multiple consecutive contention reporting cycles, it is determined that the target host device has failed to collect data from the target slave device; the contention reporting cycle includes the multiple contention reporting windows.

[0012] Optionally, the method further includes:

[0013] If a data collection instruction is received from the IoT server, the wake-up frame and data collection instruction frame are sent to the target slave device.

[0014] If a contention reporting data frame is received from the target slave device based on the multiple contention reporting windows, a contention reporting response frame is sent to the target slave device.

[0015] If the contention reporting response frame carries the slave network identifier, it is determined that the target host device has successfully copied data to the target slave device.

[0016] Optionally, the method further includes:

[0017] If the contention reporting data frame is not received within the first preset time period, the point-reading instruction frame is sent to the target slave device again; the first preset time period represents the uplink time period of the contention reporting window, and the uplink time period represents the reception time period of the contention reporting data frame;

[0018] If the target master device fails to receive the contention reporting data frame within the first preset time period after sending the copy instruction frame a first preset number of times, it is determined that the copying of the target slave device by the target master device has failed.

[0019] Optionally, the method further includes:

[0020] If an active reporting data frame is received from the target slave device, an active reporting response frame is sent to the target slave device according to the slave network identifier carried in the active reporting data frame.

[0021] Secondly, embodiments of this application provide a data copying method applied to a target slave device, the method comprising:

[0022] Receive multiple wake-up frames and multiple data collection instruction frames sent by multiple host devices; the multiple data collection instruction frames carry relevant information of the multiple host devices, and the relevant information includes multiple contention reporting windows;

[0023] After being woken up by the wake-up frame, the target host device is determined from the multiple host devices based on the relevant information of the multiple host devices;

[0024] Send a data collection frame to the target host device; the data collection frame carries the slave network identifier of the target slave device;

[0025] If a data collection response frame is received from the target host device based on the slave network identifier in response to the data collection data frame, a contention reporting data frame is sent to the target host device based on the multiple contention reporting windows of the target host device; the contention reporting data frame carries the slave network identifier.

[0026] If a contention reporting response frame is received from the target host device in response to the contention reporting data frame, and the contention reporting response frame carries the slave network identifier, it is determined that the target host device has successfully collected data from the target slave device.

[0027] Optionally, determining the target host device from the plurality of host devices based on relevant information of the plurality of host devices includes:

[0028] Within a second preset time period, the signal quality of the multiple host devices is recorded based on their relevant information; the second preset time period represents the reception time period of the wake-up frame and the data collection instruction frame.

[0029] From the plurality of host devices, the host device with the highest signal quality is determined as the target host device.

[0030] Optionally, sending contention reporting data frames to the target host device based on multiple contention reporting windows of the target host device includes:

[0031] Randomly select a target contention reporting window from among the multiple contention reporting windows of the target host device;

[0032] The contention reporting data frame is sent to the target host device through the target contention reporting window.

[0033] Optionally, the method further includes:

[0034] If the contention reporting response frame is not received or the contention reporting response frame does not carry the slave network identifier, it is determined that the target host device has failed to collect data for the target slave device.

[0035] Optionally, the method further includes:

[0036] Receive the wake-up frame and copy instruction frame sent by the target host device;

[0037] The point copy instruction frame is parsed to obtain the parsing result;

[0038] If the parsing result indicates that the point-to-point instruction frame corresponds to the target slave device, the contention reporting data frame is sent to the target host device based on the multiple contention reporting windows of the target host device;

[0039] If a contention reporting response frame is received from the target host device in response to the contention reporting data frame, and the contention reporting response frame carries the slave network identifier, it is determined that the target host device has successfully copied data from the target slave device.

[0040] Optionally, the method further includes:

[0041] If the contention reporting response frame is not received within the third preset time period, the contention reporting data frame is sent to the target host device again based on the multiple contention reporting windows of the target host device; the third preset time period represents the downlink time period of the contention reporting window, and the downlink time period represents the reception time period of the contention reporting response frame;

[0042] If, after sending the contention reporting data frame a second preset number of times, no contention reporting response frame is received within the third preset time period, it is determined that the target host device has failed to perform a copy operation on the target slave device.

[0043] Optionally, the method further includes:

[0044] Send an active reporting data frame to the target host device; the active reporting data frame carries the slave network identifier;

[0045] If an active reporting response frame is received from the target host device based on the slave network identifier in response to the active reporting data frame, it is determined that the target slave device has successfully reported to the target host device.

[0046] Optionally, the method further includes:

[0047] If the active reporting response frame is not received within the fourth preset time period, an active reporting data frame is sent to the target host device again; the fourth preset time period represents the time period for receiving the active reporting data frame.

[0048] If, after sending the active reporting data frame a third preset number of times, no active reporting response frame is received within the fourth preset time period, a candidate host device is determined from the multiple host devices based on the relevant information of the multiple host devices.

[0049] Send an active reporting data frame to the candidate host device;

[0050] If an active reporting response frame is received from the candidate host device in response to the active reporting data frame, it is determined that the target slave device has successfully made an active report to the candidate host device.

[0051] Thirdly, embodiments of this application provide a data collection device applied to a target host device, the device comprising: a first sending unit and a first determining unit;

[0052] The first sending unit is configured to send a wake-up frame and a data collection instruction frame to multiple slave devices if it receives a data collection instruction sent by an IoT server; the data collection instruction frame carries relevant information about the target host device, and the relevant information includes multiple competing reporting windows;

[0053] The first sending unit is further configured to, if it receives a data collection data frame sent by a target slave device among the plurality of slave devices, send a data collection response frame to the target slave device according to the slave network identifier of the target slave device carried in the data collection data frame;

[0054] The first sending unit is further configured to send a competition reporting response frame to the target slave device if it receives a competition reporting data frame sent by the target slave device in response to the data collection response frame based on the plurality of competition reporting windows; the competition reporting data frame carries the slave network identifier;

[0055] The first determining unit is configured to determine that the target host device has successfully collected data from the target slave device if the contention reporting response frame carries the slave network identifier.

[0056] Fourthly, embodiments of this application provide a data collection device applied to a target slave device, the device comprising: a receiving unit, a second determining unit, and a second sending unit;

[0057] The receiving unit is configured to receive multiple wake-up frames and multiple data collection instruction frames sent by multiple host devices; the multiple data collection instruction frames carry relevant information of the multiple host devices, and the relevant information includes multiple contention reporting windows;

[0058] The second determining unit is used to determine the target host device from the plurality of host devices based on the relevant information of the plurality of host devices after being woken up by the wake-up frame;

[0059] The second sending unit is used to send a data collection frame to the target host device; the data collection frame carries the slave network identifier of the target slave device;

[0060] The second sending unit is further configured to, if it receives a data collection response frame sent by the target host device in response to the data collection data frame based on the slave network identifier, send a contention reporting data frame to the target host device based on multiple contention reporting windows of the target host device; the contention reporting data frame carries the slave network identifier;

[0061] The second determining unit is further configured to determine that the target host device has successfully collected data from the target slave device if it receives a competition reporting response frame sent by the target host device in response to the competition reporting data frame, and the competition reporting response frame carries the slave network identifier.

[0062] Fifthly, embodiments of this application provide a computer device, the computer device including a processor and a memory:

[0063] The memory is used to store program code and transmit the program code to the processor;

[0064] The processor is used to execute the data copying method described in the first or second aspect above according to the instructions in the program code.

[0065] In a sixth aspect, embodiments of this application provide a computer-readable storage medium for storing program code, which, when executed by a processor, is used to perform the data copying method described in the first or second aspect above.

[0066] Compared with the prior art, this application has at least the following advantages:

[0067] Using the technical solution of this application embodiment, if a data collection instruction is received from an IoT server, a wake-up frame and a data collection instruction frame carrying relevant information of the host device are sent to multiple slave devices; wherein, the relevant information includes multiple competing reporting windows; if a data collection data frame is received from a target slave device among the multiple slave devices, a data collection response frame is sent to the target slave device according to the slave network identifier of the target slave device carried in the data collection data frame; if a competing reporting data frame carrying the slave network identifier is received from the target slave device in response to the data collection response frame based on multiple competing reporting windows, a competing reporting response frame is sent to the target slave device; if the competing reporting response frame carries the slave network identifier, it is determined that the target host device has successfully collected data from the target slave device.

[0068] As can be seen, after receiving the data collection command from the IoT server, the target host device first wakes up the target slave device by sending a wake-up frame, and then the target slave device uploads data to the target slave device, thus enabling the target host device to collect data from the target slave device. In this method, the slave device does not need to remain in a constantly awake state; it is only awakened upon receiving the wake-up frame from the target host device. This reduces the power consumption of the slave device, saves power, and improves the user experience of the slave device. Attached Figure Description

[0069] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the description of the embodiments of this application will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0070] Figure 1 This is a schematic diagram of the system framework involved in one application scenario in the embodiments of this application;

[0071] Figure 2 Signaling interaction diagram of a data collection method provided in an embodiment of this application;

[0072] Figure 3 This is a schematic diagram of the structure of a data copying device provided in an embodiment of this application;

[0073] Figure 4 This is a schematic diagram of a data copying device provided in an embodiment of this application. Detailed Implementation

[0074] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present application.

[0075] Currently, master and slave devices connect via long-range wireless communication. Typically, the slave device autonomously uploads data to the master device via long-range wireless communication, and the master device then uploads the acquired data to the IoT server via mobile communication. However, research has found that this method of slave devices autonomously uploading data to the master device via long-range wireless communication often requires the slave device to remain constantly awake to frequently upload data. This leads to a sharp increase in the power consumption of the slave device, wasting its battery and resulting in a poor user experience.

[0076] To address this issue, in this embodiment, if a data collection instruction is received from an IoT server, a wake-up frame and a data collection instruction frame carrying relevant information about the host device are sent to multiple slave devices; wherein, the relevant information includes multiple competing reporting windows; if a data collection data frame is received from a target slave device among the multiple slave devices, a data collection response frame is sent to the target slave device based on the slave network identifier of the target slave device carried in the data collection data frame; if a competing reporting data frame carrying the slave network identifier is received from the target slave device in response to the data collection response frame based on multiple competing reporting windows, a competing reporting response frame is sent to the target slave device; if the competing reporting response frame carries the slave network identifier, it is determined that the target host device has successfully collected data from the target slave device.

[0077] As can be seen, after receiving the data collection command from the IoT server, the target host device first wakes up the target slave device by sending a wake-up frame, and then the target slave device uploads data to the target slave device, thus enabling the target host device to collect data from the target slave device. In this method, the slave device does not need to remain in a constantly awake state; it is only awakened upon receiving the wake-up frame from the target host device. This reduces the power consumption of the slave device, saves power, and improves the user experience of the slave device.

[0078] For example, one scenario in the embodiments of this application can be applied to, such as Figure 1 In the scenario shown, which includes multiple host devices and multiple slave devices, any one host device acts as the target host device 101, and together with the target slave device 102 among the multiple slave devices, executes the implementation method provided in this application embodiment, which enables the target host device 101 to copy data from the target slave device 102.

[0079] First, in the above application scenarios, although the action descriptions of the implementation methods provided in this application are executed by the target host device 101 and the target slave device 102, the implementation methods of this application are not limited in terms of the execution subject, as long as the actions disclosed in the implementation methods provided in this application are executed.

[0080] Secondly, the above scenario is only one example provided by the embodiments of this application, and the embodiments of this application are not limited to this scenario.

[0081] The following description, in conjunction with the accompanying drawings, details the specific implementation of the data copying method and related apparatus in the embodiments of this application.

[0082] First, in conjunction with the appendix Figure 2 From the perspective of interaction between the target host device and the target slave device, the specific implementation of the data copying method in the embodiments of this application will be described in detail through examples.

[0083] See Figure 2 The diagram illustrates the signaling interaction of a data collection method according to an embodiment of this application. In this embodiment, the method is applied to a slave device, and the method may include, for example, the following steps:

[0084] Step 201: If the target host device receives the data collection instruction sent by the IoT server, it sends a wake-up frame and a data collection instruction frame to multiple slave devices; the data collection instruction frame carries relevant information about the target host device, including multiple competing reporting windows.

[0085] Typically, slave devices autonomously upload data to the host device via long-distance wireless communication, and the host device then uploads the acquired data to the IoT server via mobile communication. However, research has found that this method of slave devices autonomously uploading data to the host device via long-distance wireless communication often requires the slave devices to remain constantly awake to frequently upload data. This leads to a sharp increase in the power consumption of the slave devices, wasting their battery power and resulting in a poor user experience.

[0086] Therefore, in this embodiment of the application, in order to avoid the slave device constantly being kept awake and frequently uploading data autonomously, resulting in a sharp increase in the power consumption of the slave device, wasting the power of the slave device and causing a poor user experience, the IoT server can send a data collection command to the target host device. After receiving the data collection command sent by the IoT server, the target host device can send a wake-up frame to the target slave device to wake up the target slave device first, and then the target slave device can upload data to the target slave device.

[0087] Specifically, after receiving the data collection command from the IoT server, the target host device needs to send wake-up frames to multiple slave devices to wake them up, and also needs to send data collection command frames to the multiple slave devices to notify them that data collection is required. The data collection command frame carries relevant information about the host device so that the slave devices can clearly identify the target host device information; this information also includes multiple competing reporting windows of the target host device.

[0088] The relevant information of the target host device may include, for example, the target host device's host network identifier (NetID), short identifier (ShortID), received signal strength indicator (RSSI), and signal-noise ratio (SNR), etc.

[0089] Step 202: After the target slave device is woken up by the wake-up frame, the target host device is determined from the multiple host devices based on the relevant information of the multiple host devices.

[0090] In this embodiment of the application, after the target host device sends a wake-up frame and a data collection instruction frame to multiple slave devices in step 201, since the multiple slave devices include the target slave device, the target slave device can also receive wake-up frames and data collection instruction frames sent by other host devices besides the target host device. After the target slave device is woken up by the wake-up frame, the target slave device needs to compare the multiple host devices through the relevant information of the multiple host devices carried by the multiple data collection instruction frames, and determine the target host device from the multiple host devices so that the target host device can subsequently perform data collection for the target slave device.

[0091] In the specific implementation of step 202, considering that the target slave device has a limited time to receive the wake-up frame and the data collection instruction frame, it is designated as the second preset time period. Therefore, firstly, the target slave device needs to record the signal quality of multiple master devices within the second preset time period using relevant information from multiple master devices. Then, the target slave device needs to compare the signal quality of multiple master devices and determine the master device with the highest signal quality as the target master device. Therefore, in an optional embodiment of this application, step 202 may include, for example, the following steps 2021-2022:

[0092] Step 2021: The target slave device records the signal quality of multiple master devices based on the relevant information of multiple master devices within a second preset time period; the second preset time period represents the reception time period of the wake-up frame and the collection instruction frame.

[0093] Step 2022: The target slave device determines the master device with the highest signal quality from among multiple master devices as the target master device.

[0094] Step 203: The target slave device sends a data collection frame to the target master device; the data collection frame carries the slave network identifier of the target slave device.

[0095] In this embodiment of the application, after the target slave device determines the target host device from multiple host devices in step 202, the target slave device needs to send a data collection frame carrying the slave network identifier of the target slave device to the target host device in response to the data collection instruction frame sent by the target host device, indicating that the target slave device is ready to upload data to the target host device.

[0096] Step 204: If the target host device receives a data collection frame sent by the target slave device among multiple slave devices, it sends a data collection response frame to the target slave device according to the slave network identifier of the target slave device carried in the data collection frame.

[0097] In this embodiment of the application, after the target slave device sends the data collection frame to the target host device in step 203, the target host device can receive the data collection frame sent by the target slave device. Thereafter, the target host device can send a data collection response frame to the target slave device in response to the data collection frame sent by the target slave device through the slave network identifier carried in the data collection frame, indicating that the target host device responds to the data collection frame sent by the target slave device.

[0098] Step 205: If the target slave device receives the collection response frame sent by the target master device, it sends a contention reporting data frame to the target master device based on the multiple contention reporting windows of the target master device; the contention reporting data frame carries the slave network identifier.

[0099] In this embodiment of the application, after the target host device sends a data collection response frame to the target slave device in step 204, the target slave device can receive the data collection response frame sent by the target host device. Thereafter, the target slave device can send a competitive reporting data frame carrying the slave network identifier of the target slave device to the target host device through multiple competitive reporting windows included in the relevant information of the target host device, indicating that the target slave device is uploading data to the target host device.

[0100] In the specific implementation of step 205, to avoid conflicts and collisions between the target slave device and other slave devices uploading data to the target host device, the target slave device can randomly select one of the multiple competing reporting windows of the target host device as the target competing reporting window, so as to send competing reporting data frames to the target host device through the target competing reporting window. Therefore, in an optional embodiment of this application, step 205 may include, for example, the following steps 2051-2052:

[0101] Step 2051: The target slave device randomly selects a target competitive reporting window from the multiple competitive reporting windows of the target master device.

[0102] Step 2052: The target slave device sends a contention reporting data frame to the target master device through the target contention reporting window.

[0103] Step 206: If the target host device receives a contention report data frame sent by the target slave device, it sends a contention report response frame to the target slave device.

[0104] In this embodiment of the application, after the target slave device sends a contention reporting data frame to the target host device in step 205, the target host device can receive the contention reporting data frame sent by the target slave device. Subsequently, the target host device can send a contention reporting response frame to the target slave device in response to the contention reporting data frame sent by the target slave device through the slave network identifier carried in the contention reporting data frame, indicating that the target host device responds to the contention reporting data frame sent by the target slave device.

[0105] Furthermore, in this embodiment, multiple contention reporting windows of the target host device constitute a contention reporting cycle. The target host device has multiple contention reporting cycles, corresponding to the target host device being able to receive contention reporting data frames sent by the target slave device, and the target host device may not receive contention reporting data frames sent by the target slave device. If no contention reporting data frames are received from the target slave device in multiple consecutive contention reporting cycles, then the target host device cannot perform data collection for the target slave device in this data collection process, that is, the data collection for the target slave device by the target host device fails. Therefore, in an optional embodiment of this application, the method may further include the following step A: if the target host device does not receive contention reporting data frames in multiple consecutive contention reporting cycles, it is determined that the data collection for the target slave device by the target host device has failed; the contention reporting cycle includes multiple contention reporting windows.

[0106] As an example, if the target host device does not receive a competition reporting data frame sent by the target slave device within two consecutive competition reporting cycles, it is determined that the target host device has failed to collect data from the target slave device.

[0107] Step 207: If the target slave device receives a contention reporting response frame sent by the target master device, and the contention reporting response frame carries the slave network identifier, it is determined that the target master device has successfully collected data for the target slave device.

[0108] In this embodiment of the application, after the target host device sends a contention reporting response frame to the target slave device in step 206, the target slave device can receive the contention reporting response frame sent by the target host device. If the contention reporting response frame carries the slave network identifier of the target slave device, then the target host device achieves data collection for the target slave device in this data collection process, that is, the target host device successfully collects data for the target slave device.

[0109] Correspondingly, if the target host device successfully collects data from the target slave device, the target host device also needs to send a data reporting frame to the IoT server, indicating that the target host device is uploading data to the IoT server.

[0110] Furthermore, in this embodiment, corresponding to the target slave device receiving a contention reporting response frame sent by the target master device, the target slave device may not receive a contention reporting response frame sent by the target master device. Alternatively, corresponding to the contention reporting response frame carrying the slave network identifier of the target slave device, the contention reporting response frame may not carry the slave network identifier of the target slave device. This situation indicates that the data collection process cannot be completed by the target master device for the target slave device, that is, the data collection by the target master device for the target slave device has failed. Therefore, after step 205, in an optional embodiment of this application, the method may further include, for example, the following step B: if the target slave device does not receive a contention reporting response frame or the contention reporting response frame does not carry the slave network identifier, it is determined that the data collection by the target master device for the target slave device has failed.

[0111] Furthermore, in this embodiment of the application, during the aforementioned data collection process, data loss may occur when the slave device uploads data to the host device. In this case, the host device can perform data point recording on the slave device to compensate for the data loss. Specifically, the IoT server can search for the slave device that needs data point recording and find the host device that the slave device is uploading data to. The following example shows how to find the target host device:

[0112] An IoT server can send a data collection command to the target host device. After receiving the data collection command from the IoT server, the target host device can send a wake-up frame and a data collection command frame to the target slave device. The target slave device can be woken up by the wake-up frame first, and then parse the data collection command frame. If the parsing result indicates that the data collection command frame corresponds to the target slave device, the slave device can send a competitive reporting data frame to the target host device through multiple competitive reporting windows, indicating that the target slave device is uploading data to the target host device. The target host device can receive the contention reporting data frame sent by the target slave device. Subsequently, the target host device can use the slave network identifier carried in the contention reporting data frame to send a contention reporting response frame to the target slave device, indicating that the target host device is responding to the contention reporting data frame sent by the target slave device. The target slave device can receive the contention reporting response frame sent by the target host device. If the contention reporting response frame carries the slave network identifier of the target slave device, then the data point copying by the target host device for the target slave device is successfully completed during this data point copying process; that is, the data point copying by the target host device for the target slave device is successful. Therefore, in an optional embodiment of this application, the method may further include, for example, the following steps C-G:

[0113] Step C: If the target host device receives the data collection instruction sent by the IoT server, it sends a wake-up frame and a data collection instruction frame to the target slave device.

[0114] Step D: The target slave device parses the point-to-point copy command frame to obtain the parsing result.

[0115] Step E: If the parsing result indicates that the copy instruction frame corresponds to the target slave device, the target slave device sends a contention reporting data frame to the target master device based on the multiple contention reporting windows of the target master device.

[0116] Step F: If the target host device receives a contention report data frame sent by the target slave device, it sends a contention report response frame to the target slave device.

[0117] Step G: If the target slave device receives a contention reporting response frame sent by the target master device in response to the contention reporting data frame, and the contention reporting response frame carries the slave network identifier, it is determined that the target master device has successfully copied the data from the target slave device.

[0118] Furthermore, in this embodiment, considering that the contention reporting window is divided into an uplink time period and a downlink time period, and the uplink time period is used for the target host device to receive contention reporting data frames, the time for the target host device to receive contention reporting data frames is also limited, denoted as the first preset time period. After the target host device sends the point-copying instruction frame to the target slave device in step C, if the target host device does not receive the contention reporting data frame within the first preset time period, it needs to send the point-copying instruction frame to the target slave device again. Based on this, the number of times the target host device continuously sends the point-copying instruction frame to the target slave device is also limited, denoted as the first preset number of times. If the target host device still does not receive the contention reporting data frame within the first preset time period after continuously sending the point-copying instruction frame to the target slave device the first preset number of times, then the data point-copying by the target host device for the target slave device cannot be achieved in this data point-copying process; that is, the data point-copying by the target host device for the target slave device fails. Therefore, in an optional embodiment of this application, after step C, the method may further include, for example, the following steps H-I:

[0119] Step H: If the target host device does not receive the contention reporting data frame within the first preset time period, it sends the point copying instruction frame to the target slave device again; the first preset time period represents the uplink time period of the contention reporting window, and the uplink time period represents the reception time period of the contention reporting data frame.

[0120] Step 1: If the target host device does not receive a contention report data frame within the first preset time period after sending the point-reading instruction frame a first preset number of times, it is determined that the point-reading of the target slave device by the target host device has failed.

[0121] The first preset number of times can be, for example, 3 times. Of course, the first preset number of times can also be other times greater than or equal to 2, which is not limited in this embodiment.

[0122] Similarly, in this embodiment, the aforementioned downlink time period is used for the target host device to send a contention reporting response frame. That is, the time for the target slave device to receive the contention reporting response frame is also limited, denoted as the third preset time period. After the target slave device sends a contention reporting data frame to the target host device in step E, if the target slave device does not receive a contention reporting response frame within the third preset time period, it needs to send a contention reporting data frame to the target host device again. Furthermore, the number of times the target slave device continuously sends a contention reporting data frame to the target host device is also limited, denoted as the second preset number of times. If the target host device continuously sends a data point copying instruction frame to the target slave device for the second preset number of times, and still does not receive a contention reporting response frame within the third preset time period, then the data point copying process cannot be performed by the target host device for the target slave device, i.e., the data point copying by the target host device for the target slave device fails. Therefore, in an optional embodiment of this application, after step E, the method may further include the following steps J-K:

[0123] Step J: If the target slave device does not receive a contention reporting response frame within the third preset time period, a contention reporting data frame is sent to the target master device again based on the multiple contention reporting windows of the target master device; the third preset time period represents the downlink time period of the contention reporting window, and the downlink time period represents the reception time period of the contention reporting response frame;

[0124] Step K: If the target slave device does not receive a competition reporting response frame within a third preset time period after sending a competition reporting data frame a second preset number of times, it is determined that the target master device has failed to copy data from the target slave device.

[0125] The second preset number of times can be, for example, 3 times. Of course, the second preset number of times can also be other times greater than or equal to 2, which is not limited in this embodiment.

[0126] Furthermore, in certain specific situations, such as at a preset time point or after the target slave device generates alarm data, the target slave device can actively upload data to the target host device so that the target host device can obtain the data from the target slave device in a timely manner. That is, the target slave device can send an active reporting data frame carrying the slave network identifier of the target slave device to the target host device, and the target host device can receive the active reporting data frame sent by the target slave device. Subsequently, the target host device can use the slave network identifier carried in the active reporting data frame to send an active reporting response frame to the target slave device in response to the active reporting data frame sent by the target slave device, indicating that the target host device is responding to the active reporting data frame sent by the target slave device. If the target slave device can receive the active reporting response frame sent by the target host device, then the active reporting by the target slave device to the target host device is successful. Therefore, in an optional implementation of this application embodiment, the method may further include steps L-N as follows:

[0127] Step L: The target slave device sends an active reporting data frame to the target master device; the active reporting data frame carries the slave network identifier.

[0128] Step M: If the target host device receives an active reporting data frame sent by the target slave device, it sends an active reporting response frame to the target slave device according to the slave network identifier carried in the active reporting data frame.

[0129] Step N: If the target slave device receives an active reporting response frame sent by the target master device based on the slave network identifier for the active reporting data frame, it is determined that the target slave device has successfully actively reported to the target master device.

[0130] Furthermore, in this embodiment, considering that the time for the target slave device to receive the active reporting response frame is also limited, it is denoted as the fourth preset time period; after the target slave device sends the active reporting data frame to the target master device in step L, if the target slave device does not receive the contention reporting response frame within the fourth preset time period, it needs to send the active reporting data frame to the target master device again. Based on this, the number of times the target slave device can continuously send the active reporting data frame to the target master device is also limited, denoted as the third preset number of times; if the target slave device still does not receive the active reporting response frame within the fourth preset time period after continuously sending the active reporting data frame to the target master device the third preset number of times, the target slave device can also determine alternative master devices different from the target master device from among the multiple master devices based on the relevant information of multiple master devices. Similarly, the target slave device can send an active reporting data frame to the alternative master device. The alternative master device can receive the active reporting data frame and send an active reporting response frame to the target slave device, indicating that the alternative master device is responding to the active reporting data frame sent by the target slave device. If the target slave device can receive the active reporting response frame sent by the alternative master device, then the target slave device has successfully made an active report to the alternative master device. Therefore, after step L, in an optional embodiment of this application, the method may further include, for example, the following steps O-R:

[0131] Step O: If the target slave device does not receive the active reporting response frame within the fourth preset time period, it sends the active reporting data frame to the target master device again; the fourth preset time period represents the reception time period of the active reporting data frame.

[0132] Step P: If the target slave device does not receive an active reporting response frame within a fourth preset time period after sending the active reporting data frame a third preset number of times, a candidate master device is determined from the multiple master devices based on the relevant information of the multiple master devices.

[0133] The third preset number of times can be, for example, 3 times. Of course, the third preset number of times can also be other times greater than or equal to 2, which is not limited in this embodiment.

[0134] Step Q: The target slave device sends an active reporting data frame to the alternative master device.

[0135] Step R: If the target slave device receives an active reporting response frame from the alternative master device in response to the active reporting data frame, it is determined that the target slave device has successfully reported to the alternative master device.

[0136] Through the various implementation methods provided in this embodiment, if a data collection instruction is received from the IoT server, a wake-up frame and a data collection instruction frame carrying relevant information of the host device are sent to multiple slave devices; wherein, the relevant information includes multiple competing reporting windows; if a data collection data frame is received from the target slave device among the multiple slave devices, a data collection response frame is sent to the target slave device according to the slave network identifier of the target slave device carried in the data collection data frame; if a competing reporting data frame carrying the slave network identifier is received from the target slave device in response to the data collection response frame based on multiple competing reporting windows, a competing reporting response frame is sent to the target slave device; if the competing reporting response frame carries the slave network identifier, it is determined that the target host device has successfully collected data from the target slave device.

[0137] As can be seen, after receiving the data collection command from the IoT server, the target host device first wakes up the target slave device by sending a wake-up frame, and then the target slave device uploads data to the target slave device, thus enabling the target host device to collect data from the target slave device. In this method, the slave device does not need to remain in a constantly awake state; it is only awakened upon receiving the wake-up frame from the target host device. This reduces the power consumption of the slave device, saves power, and improves the user experience of the slave device.

[0138] Secondly, in conjunction with the appendix Figure 3 From the perspective of the target host device, another embodiment will be used to explain in detail the specific implementation of the data collection device in the embodiments of this application.

[0139] See Figure 3 This illustration shows a schematic diagram of a data collection device according to an embodiment of this application. In this embodiment, it is applied to a target host device, and the device may specifically include, for example, a first sending unit 301 and a first determining unit 302;

[0140] The first sending unit 301 is used to send a wake-up frame and a data collection instruction frame to multiple slave devices if it receives a data collection instruction sent by the IoT server; the data collection instruction frame carries relevant information of the target host device, including multiple competing reporting windows;

[0141] The first sending unit 301 is further configured to, if it receives a data collection data frame sent by a target slave device among multiple slave devices, send a data collection response frame to the target slave device according to the slave network identifier of the target slave device carried in the data collection data frame;

[0142] The first sending unit 301 is further configured to send a competitive reporting response frame to the target slave device if it receives a competitive reporting data frame sent by the target slave device based on multiple competitive reporting windows in response to the collection and reading response frame; the competitive reporting data frame carries the slave network identifier;

[0143] The first determining unit 302 is used to determine that the target host device has successfully collected data from the target slave device if the contention report response frame carries the slave network identifier.

[0144] In an optional embodiment of this application, the first determining unit 302 is further configured to determine that the target host device has failed to collect data from the target slave device if no competitive reporting data frame is received within multiple consecutive competitive reporting cycles; the competitive reporting cycle includes multiple competitive reporting windows.

[0145] In an optional embodiment of this application, the first sending unit 301 is further configured to send a wake-up frame and a copy instruction frame to the target slave device if a copy instruction is received from the Internet of Things server.

[0146] The first sending unit 301 is further configured to send a competition reporting response frame to the target slave device if it receives a competition reporting data frame sent by the target slave device based on multiple competition reporting windows;

[0147] The first determining unit 302 is also used to determine that the target host device has successfully copied data to the target slave device if the response frame reported by the contention carries the slave network identifier.

[0148] In an optional embodiment of this application, the first sending unit 301 is further configured to send a point-copying instruction frame to the target slave device again if no contention reporting data frame is received within a first preset time period; the first preset time period represents the uplink time period of the contention reporting window, and the uplink time period represents the reception time period of the contention reporting data frame.

[0149] The first determining unit 302 is further configured to determine that the target master device has failed to perform point copying on the target slave device if no competing reporting data frame is received within a first preset time period after sending the point copying instruction frame a first preset number of times.

[0150] In an optional embodiment of this application, the first sending unit 301 is further configured to, if it receives an active reporting data frame sent by the target slave device, send an active reporting response frame to the target slave device according to the slave network identifier carried in the active reporting data frame.

[0151] Through the various implementation methods provided in this embodiment, if a data collection instruction is received from the IoT server, a wake-up frame and a data collection instruction frame carrying relevant information of the host device are sent to multiple slave devices; wherein, the relevant information includes multiple competing reporting windows; if a data collection data frame is received from the target slave device among the multiple slave devices, a data collection response frame is sent to the target slave device according to the slave network identifier of the target slave device carried in the data collection data frame; if a competing reporting data frame carrying the slave network identifier is received from the target slave device in response to the data collection response frame based on multiple competing reporting windows, a competing reporting response frame is sent to the target slave device; if the competing reporting response frame carries the slave network identifier, it is determined that the target host device has successfully collected data from the target slave device.

[0152] As can be seen, after receiving the data collection command from the IoT server, the target host device first wakes up the target slave device by sending a wake-up frame, and then the target slave device uploads data to the target slave device, thus enabling the target host device to collect data from the target slave device. In this method, the slave device does not need to remain in a constantly awake state; it is only awakened upon receiving the wake-up frame from the target host device. This reduces the power consumption of the slave device, saves power, and improves the user experience of the slave device.

[0153] Then, combined with the appendix Figure 4 From the perspective of the target slave device, another embodiment will be used to explain in detail the specific implementation of the data collection device in the embodiments of this application.

[0154] See Figure 4 This illustration shows a schematic diagram of another data collection device according to an embodiment of this application. In this embodiment, it is applied to a target slave device, and the device may specifically include, for example, a receiving unit 401, a second determining unit 402, and a second sending unit 403;

[0155] The receiving unit 401 is used to receive multiple wake-up frames and multiple data collection instruction frames sent by multiple host devices; the multiple data collection instruction frames carry relevant information of multiple host devices, including multiple competing reporting windows;

[0156] The second determining unit 402 is used to determine the target host device from the multiple host devices based on the relevant information of the multiple host devices after being woken up by the wake-up frame.

[0157] The second sending unit 403 is used to send a data collection frame to the target host device; the data collection frame carries the slave network identifier of the target slave device.

[0158] The second sending unit 403 is further configured to, if it receives a collection response frame sent by the target host device according to the slave network identifier for the collection data frame, send a competitive reporting data frame to the target host device based on the multiple competitive reporting windows of the target host device; the competitive reporting data frame carries the slave network identifier;

[0159] The second determining unit 402 is further configured to determine that the target host device has successfully collected data from the target slave device if it receives a competition reporting response frame sent by the target host device in response to the competition reporting data frame, and the competition reporting response frame carries the slave network identifier.

[0160] In one optional embodiment of this application, the second determining unit 402 includes: a recording subunit and a determining subunit;

[0161] The recording subunit is used to record the signal quality of multiple host devices based on relevant information of multiple host devices within a second preset time period; the second preset time period represents the reception time period of the wake-up frame;

[0162] The determination subunit is used to determine the target host device from among multiple host devices, corresponding to the host device with the highest signal quality.

[0163] In one optional embodiment of this application, the second sending unit 403 includes: a selection subunit and a sending subunit;

[0164] Select sub-unit, used to randomly select the target contention reporting window from multiple contention reporting windows of the target host device;

[0165] The sending subunit is used to send contention reporting data frames to the target host device through the target contention reporting window.

[0166] In an optional embodiment of this application, the second determining unit 402 is further configured to:

[0167] If no contention reporting response frame is received or the contention reporting response frame does not carry the slave network identifier, it is determined that the target master device has failed to collect data from the target slave device.

[0168] In one optional embodiment of this application, the apparatus further includes: a parsing unit;

[0169] The receiving unit 401 is also used to receive the wake-up frame and the copy instruction frame sent by the target host device;

[0170] The parsing unit is used to parse the copy instruction frame to obtain the parsing result;

[0171] The second sending unit 403 is also used to send a competitive reporting data frame to the target master device based on the multiple competitive reporting windows of the target master device if the parsing result indicates that the point copy instruction frame corresponds to the target slave device.

[0172] The second determining unit 402 is further configured to determine that the target host device has successfully copied data from the target slave device if it receives a competition reporting response frame sent by the target host device in response to the competition reporting data frame, and the competition reporting response frame carries the slave network identifier.

[0173] In an optional embodiment of this application, the second sending unit 403 is further configured to send a contention reporting data frame to the target host device again based on the multiple contention reporting windows of the target host device if no contention reporting response frame is received within a third preset time period; the third preset time period represents the downlink time period of the contention reporting window, and the downlink time period represents the reception time period of the contention reporting response frame.

[0174] The second determining unit 402 is further configured to determine that the target host device has failed to read data from the target slave device if no competition reporting response frame is received within a third preset time period after sending a second preset number of competition reporting data frames.

[0175] In an optional embodiment of this application, the second sending unit 403 is further configured to send an active reporting data frame to the target host device; the active reporting data frame carries the slave network identifier;

[0176] The second determining unit 402 is further configured to determine that the target slave device has successfully reported to the target host device if it receives an active reporting response frame sent by the target host device according to the slave network identifier for the active reporting data frame.

[0177] In an optional embodiment of this application, the second sending unit 403 is further configured to send an active reporting data frame to the target host device again if no active reporting response frame is received within a fourth preset time period; the fourth preset time period represents the reception time period of the active reporting data frame.

[0178] The second determining unit 402 is further configured to determine a candidate host device from multiple host devices based on relevant information of multiple host devices if no active reporting response frame is received within a fourth preset time period after sending an active reporting data frame a third preset number of times.

[0179] The second sending unit 403 is also used to send an active reporting data frame to the alternative host device;

[0180] The second determining unit 402 is further configured to determine that the target slave device has successfully submitted an active report to the candidate master device if it receives an active report response frame sent by the candidate master device in response to the active report data frame.

[0181] Through the various implementation methods provided in this embodiment, the target slave device receives multiple wake-up frames and multiple data collection instruction frames carrying relevant information of multiple host devices from multiple host devices; wherein, the relevant information includes multiple contention reporting windows; after the target slave device is woken up by the wake-up frame, it determines the target host device from the multiple host devices according to the relevant information of the multiple host devices; the target slave device sends a data collection frame carrying the slave network identifier of the target slave device to the target host device; if the target slave device receives a data collection response frame sent by the target host device according to the slave network identifier for the data collection frame, it sends a contention reporting data frame carrying the slave network identifier to the target host device based on the multiple contention reporting windows of the target host device; if the target slave device receives a contention reporting response frame sent by the target host device for the contention reporting data frame, and the contention reporting response frame carries the slave network identifier, it is determined that the target host device has successfully collected data for the target slave device.

[0182] As can be seen, the target master device uses a wake-up frame to first wake up the target slave device, and then the target slave device uploads data to the target slave device, thus enabling the target master device to copy data from the target slave device. In this method, the slave device does not need to remain in a wake-up state; it is only woken up upon receiving the wake-up frame from the target master device. This reduces the power consumption of the slave device, saves power, and improves the user experience of the slave device.

[0183] Furthermore, embodiments of this application also provide a computer device, which includes a processor and a memory:

[0184] The memory is used to store program code and transfer the program code to the processor;

[0185] The processor is used to execute the data copying method of the above embodiments according to the instructions in the program code.

[0186] This application also provides a computer-readable storage medium for storing program code, which, when executed by a processor, is used to perform the data copying method described in the above embodiments.

[0187] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatus disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the description is relatively simple; relevant parts can be referred to the method section.

[0188] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0189] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. The terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0190] The above description is merely a preferred embodiment of this application and is not intended to limit the application in any way. Although this application has disclosed preferred embodiments above, it is not intended to limit the application. Any person skilled in the art can make many possible variations and modifications to the technical solutions of this application using the methods and techniques disclosed above, or modify them into equivalent embodiments with equivalent changes, without departing from the scope of the technical solutions of this application. Therefore, any simple modifications, equivalent changes, and modifications made to the above embodiments based on the technical essence of this application without departing from the content of the technical solutions of this application shall still fall within the protection scope of the technical solutions of this application.

Claims

1. A method of data set copying, characterized by, The application is applied to a target host device, and comprises: If a set-copying instruction sent by an Internet of Things server is received, a wake-up frame and a set-copying instruction frame are sent to a plurality of slave devices; the set-copying instruction frame carries relevant information of the target host device, and the relevant information comprises a plurality of competitive reporting windows; If a set-copying data frame sent by a target slave device in the plurality of slave devices is received, a set-copying response frame is sent to the target slave device according to a slave network identifier of the target slave device carried by the set-copying data frame; If a competitive reporting data frame sent by the target slave device based on the plurality of competitive reporting windows is received in response to the set-copying response frame, a competitive reporting response frame is sent to the target slave device; the competitive reporting data frame carries the slave network identifier; If the competitive reporting response frame carries the slave network identifier, it is determined that the target host device succeeds in set copying for the target slave device.

2. The method of claim 1, wherein, The method further comprises: If the competitive reporting data frame is not received in a plurality of continuous competitive reporting periods, it is determined that the target host device fails in set copying for the target slave device; the competitive reporting period comprises the plurality of competitive reporting windows.

3. The method of claim 1, wherein, The method further comprises: If a point-copying instruction sent by the Internet of Things server is received, the wake-up frame and the point-copying instruction frame are sent to the target slave device; If the competitive reporting data frame sent by the target slave device based on the plurality of competitive reporting windows is received, a competitive reporting response frame is sent to the target slave device; If the competitive reporting response frame carries the slave network identifier, it is determined that the target host device succeeds in point copying for the target slave device.

4. The method of claim 3, wherein, The method further comprises: If the competitive reporting data frame is not received in a first preset time period, the point-copying instruction frame is sent to the target slave device again; the first preset time period represents an uplink time period of the competitive reporting window, and the uplink time period represents a receiving time period of the competitive reporting data frame; If the competitive reporting data frame is not received in the first preset time period after the point-copying instruction frame is sent for a first preset number of times, it is determined that the target host device fails in point copying for the target slave device.

5. The method of claim 1, wherein, The method further comprises: If an active reporting data frame sent by the target slave device is received, an active reporting response frame is sent to the target slave device according to the slave network identifier carried by the active reporting data frame.

6. A method of data set copying, characterized by The application is applied to a target slave device, and comprises: A plurality of wake-up frames and a plurality of set-copying instruction frames sent by a plurality of host devices are received; the plurality of set-copying instruction frames carry relevant information of the plurality of host devices, and the relevant information comprises a plurality of competitive reporting windows; After being woken up by the wake-up frame, a target host device is determined from the plurality of host devices according to the relevant information of the plurality of host devices; A set-copying data frame is sent to the target host device; the set-copying data frame carries a slave network identifier of the target slave device; if the target master device sends a competition report data frame according to the slave network identifier, the competition report data frame is sent to the target master device based on a plurality of competition report windows of the target master device; the competition report data frame carries the slave network identifier; if the competition report response frame is received and the competition report response frame carries the slave network identifier, it is determined that the target master device is successful in the group copy for the target slave device.

7. The method of claim 6, wherein, The target master device is determined from the plurality of master devices according to the related information of the plurality of master devices, including: The signal quality of the plurality of master devices is recorded according to the related information of the plurality of master devices within a second preset time period; the second preset time period represents a receiving time period of the wake-up frame and the group copy instruction frame; The master device corresponding to the highest signal quality is determined as the target master device from the plurality of master devices.

8. The method of claim 6, wherein, The competition report data frame is sent to the target master device based on a plurality of competition report windows of the target master device, including: A target competition report window is randomly selected from the plurality of competition report windows of the target master device; The competition report data frame is sent to the target master device through the target competition report window.

9. The method of claim 6, wherein, The method further includes: If the competition report response frame is not received or the competition report response frame does not carry the slave network identifier, it is determined that the target master device fails in the group copy for the target slave device.

10. The method of claim 6, wherein, The method further includes: The wake-up frame and the point copy instruction frame sent by the target master device are received; The point copy instruction frame is parsed to obtain a parsing result; If the parsing result indicates that the point copy instruction frame corresponds to the target slave device, the competition report data frame is sent to the target master device based on a plurality of competition report windows of the target master device; If the competition report response frame is received and the competition report response frame carries the slave network identifier, it is determined that the target master device is successful in the point copy for the target slave device.

11. The method of claim 10, wherein, The method further includes: If the competition report response frame is not received within a third preset time period, the competition report data frame is sent to the target master device again based on a plurality of competition report windows of the target master device; the third preset time period represents a downlink time period of the competition report window, and the downlink time period represents a receiving time period of the competition report response frame; If the competition report response frame is not received within the third preset time period after the competition report data frame is sent for a second preset number of times, it is determined that the target master device fails in the point copy for the target slave device.

12. The method of claim 6, wherein, The method further includes: An active report data frame is sent to the target master device; the active report data frame carries the slave network identifier; If the active reporting response frame sent by the target master device according to the slave network identifier is received, it is determined that the target slave device actively reports successfully to the target master device.

13. The method of claim 12, wherein, The method further comprises: If the active reporting response frame is not received within a fourth preset time period, an active reporting data frame is sent to the target master device again; the fourth preset time period represents a receiving time period of the active reporting data frame; If the active reporting response frame is not received within the fourth preset time period after the active reporting data frame is sent for a third preset number of times, a backup master device is determined from the plurality of master devices according to the related information of the plurality of master devices; An active reporting data frame is sent to the backup master device; If the active reporting response frame sent by the backup master device for the active reporting data frame is received, it is determined that the target slave device actively reports successfully to the backup master device.

14. An apparatus for copying a data set, characterized by Applied to a target master device, comprising a first sending unit and a first determining unit; If the set copy instruction frame is received, the target master device is determined according to the slave network identifier carried by the set copy data frame. The first sending unit is further configured to, if the set copy data frame sent by a target slave device in the plurality of slave devices is received, send a set copy response frame to the target slave device according to the slave network identifier of the target slave device carried by the set copy data frame. The first sending unit is further configured to, if the competitive reporting data frame sent by the target slave device for the set copy response frame based on the plurality of competitive reporting windows is received, send a competitive reporting response frame to the target slave device; the competitive reporting data frame carries the slave network identifier. The first determining unit is configured to, if the competitive reporting response frame carries the slave network identifier, determine that the target master device successfully sets and copies the target slave device.

15. An apparatus for copying a data set, characterized by Applied to a target slave device, comprising a receiving unit, a second determining unit and a second sending unit; The receiving unit is configured to receive a plurality of wake-up frames and a plurality of set copy instruction frames sent by a plurality of master devices; the plurality of set copy instruction frames carry related information of the plurality of master devices, and the related information comprises a plurality of competitive reporting windows. The second determining unit is configured to, after being woken up by the wake-up frame, determine a target master device from the plurality of master devices according to the related information of the plurality of master devices. The second sending unit is configured to send a set copy data frame to the target master device; the set copy data frame carries a slave network identifier of the target slave device. The second sending unit is further configured to, if the set copy response frame sent by the target master device for the set copy data frame according to the slave network identifier is received, send a competitive reporting data frame to the target master device based on the plurality of competitive reporting windows of the target master device; the competitive reporting data frame carries the slave network identifier. The second determining unit is further configured to determine that the target master device is successful in the set copy for the target slave device set if a competition report response frame sent by the target master device for the competition report data frame is received and the competition report response frame carries the slave network identifier.

16. A computer device, comprising: The computer device comprises a processor and a memory: The memory is configured to store program code and transmit the program code to the processor; The processor is configured to execute instructions in the program code to perform the method for data set copy according to any one of claims 1-13.

17. A computer-readable storage medium, characterized in that, The computer readable storage medium is configured to store program code, and the program code is configured to be executed by the processor to perform the method for data set copy according to any one of claims 1-13.

Images