Data acquisition method and apparatus

Abstract

The present application relates to the technical field of communications, and provides a data acquisition method and apparatus, capable of enabling the delegation of a control authority for data acquisition from a higher-layer network device or application layer to a first device, such as an AIoT controller or reader, or a second device, such as an AIoT device, and capable of shortening a signaling and / or data transmission path, reducing the number of signaling and / or data interactions, and improving data acquisition efficiency. The solution comprises: a first device sends first instruction information in a first manner, wherein the first instruction information is used for instructing a second device to acquire and report first data, and the first manner comprises one or two of the following: a data acquisition period or data acquisition duration; and the first device receives the first data from the second device.

Description

Data acquisition method and device

[0001] This application claims priority to Chinese Patent Application No. 202411048172.6, filed with the State Intellectual Property Office of China on July 31, 2024, entitled “Data Acquisition Method and Apparatus”, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communications, and more particularly to a data acquisition method and apparatus. Background Technology

[0003] In current AIoT scenarios, data acquisition is typically triggered by an application function (AF). Specifically, the AF needs to send a data acquisition command (DL command) to the terminal device, such as an AIoT device. This command is first sent to the AIoT controller, which then forwards it to the reader, which in turn forwards it to the terminal device. The data acquisition commands sent include read, write, disable, and enable commands. Read commands can be used to collect sensor data from the terminal device, such as temperature and humidity. Upon receiving the data acquisition command, the terminal device acquires the data and replies to the AF, following the reverse process of sending the command.

[0004] It is evident that both issuing data acquisition commands and reporting acquired data require multiple forwardings, resulting in long signaling and / or data transmission paths and significant time consumption. Furthermore, data acquisition is triggered by the AF (Automatic Data Acquisition) and can only be triggered once for each acquisition, thus leading to low efficiency. Summary of the Invention

[0005] This application provides a data acquisition method and apparatus that can solve the problem that, for each triggering of a third device, a second device can only acquire or report data once, thereby improving data acquisition efficiency.

[0006] To achieve the above objectives, the embodiments of this application adopt the following technical solutions:

[0007] Firstly, a data acquisition method is provided. This method is applicable to a first device, which is a reader or an environmental IoT controller. The method includes: the first device sending first instruction information according to a first method, the first instruction information being used to instruct a second device to acquire or report first data; the first method including one or more of the following: a first acquisition period or a first acquisition duration; and the first device receiving the first data from the second device.

[0008] Based on this method, the first device can trigger the second device to complete data acquisition or reporting in a first manner. For example, the second device can be triggered to acquire or report data once or multiple times according to the first acquisition cycle or the first acquisition duration. This can solve the problem that the second device can only acquire or report data once for each trigger by a higher-level network device or application layer device, such as a third device. The control of data acquisition or reporting can be delegated from the higher-level network device or application layer device to the first device. This can achieve the goal of the first device controlling the second device to acquire or report data once or multiple times when the third device is triggered once. It can also effectively shorten the signaling and / or data transmission path and number of times, consume less time, and thus improve the efficiency and flexibility of data acquisition.

[0009] In some implementations, the first device sends first instruction information to the second device in a first manner, including: the first device receiving second instruction information from the third device, the second instruction information including a first acquisition period; and the first device sending the first instruction information to the second device in accordance with the first acquisition period.

[0010] Based on this scheme, the first device can periodically trigger the second device to acquire data according to the first acquisition cycle issued by a higher-level network device, such as the third device. This can achieve the goal of the second device acquiring data multiple times when the third device triggers it once, which can effectively reduce the workload of the third device and the signaling interaction overhead between the first and third devices, thereby improving the data acquisition efficiency.

[0011] Optionally, the second indication information may also include one or more of the following: a first number of cycles, a first time period, or a third stop indication, wherein the first number of cycles is the number of first acquisition cycles, the first time period is the time period to which the first acquisition cycle applies, and the third stop indication is used to indicate that data acquisition should be stopped.

[0012] Furthermore, the method also includes: the first device sending a first stop instruction to the second device, the first stop instruction being used to instruct the second device to stop data acquisition when the data acquisition time reaches a first number of cycles or exceeds a first time period.

[0013] Based on this scheme, the first device can also control the second device to stop acquiring data based on the end condition of acquiring data according to the first acquisition cycle (first cycle number, first time period), so that the second device can stop unnecessary data acquisition in time to save power consumption.

[0014] In some implementations, the first device sends a first instruction message to the second device in a first manner, including: the first device receiving a second instruction message from a third device, the second instruction message including a first acquisition duration; and the first device sending the first instruction message to the third device in accordance with the first acquisition duration.

[0015] Based on this scheme, the first device can trigger the second device to acquire data once or multiple times according to the first acquisition duration in the second instruction information issued by a higher-level network device, such as the third device. This can achieve the goal of the second device acquiring data once or multiple times when the third device triggers it once, which can effectively reduce the workload of the third device and the signaling interaction overhead between the first and third devices, thereby improving the data acquisition efficiency.

[0016] Optionally, the second indication information may further include one or more of the following: a first duration, a second time period, or a fourth stop indication; wherein the first duration is the number of the first acquisition duration, the second time period is the time period to which the first acquisition duration applies, and the fourth stop indication is used to indicate that data acquisition should be stopped.

[0017] Furthermore, the method also includes: the first device sending a second stop instruction to the second device, the second stop instruction being used to instruct the second device to stop data acquisition when the data acquisition time reaches a first duration or exceeds a second time period.

[0018] Based on this scheme, the first device can also control the second device to stop acquiring data based on the termination condition of acquiring data according to the first acquisition duration (first duration number, second time period), so that the second device can stop unnecessary data acquisition in time to save power consumption.

[0019] In some implementations, the method further includes: the first device sending first data or fourth indication information to the third device, the fourth indication information being used to indicate that the second device has acquired the first data, so as to notify the third device to read the data in a timely manner to avoid loss, thereby improving the reliability of data acquisition.

[0020] In some implementations, the first method further includes: reporting conditions; the method further includes: a first device receiving second indication information from a third device, the second indication information including reporting conditions; the first device sending second data or fourth indication information to the third device, the fourth indication information being used to indicate that the second device has obtained the second data, the second data being the data in the first data that meets the reporting conditions.

[0021] Optionally, the fourth instruction information includes one or more of the following: the requested amount of resources or data, the data type, or the identifier of the second device, so that the third device may use it.

[0022] Based on this scheme, the first device can determine whether there is second data that meets the reporting conditions in the first data reported by the second device. If so, only the second data needs to be reported; otherwise, no data needs to be reported, thus reducing the amount of data that needs to be reported and further improving data acquisition efficiency. Furthermore, when the second device obtains second data that meets the reporting conditions, it can also report a fourth indication message to notify the third device to read the data in a timely manner to prevent loss, thereby improving the reliability of data acquisition.

[0023] In some implementations, the first method further includes: reporting conditions; the method further includes: a first device receiving second indication information from a third device, the second indication information including reporting conditions; the first device sending third indication information to the third device, the third indication information indicating that no event satisfying the reporting conditions has occurred.

[0024] Based on this scheme, the first device can inform the third device that the second device has not obtained second data that meets the reporting conditions. The reporting conditions typically include the occurrence conditions of abnormal events of the second device. The failure to obtain data that meets the reporting conditions indicates that the second device is working normally. Upon receiving the third instruction information, the third device can know that the second device is working normally, and can also instruct the first device and / or the second device to discard the obtained data to reclaim storage resources.

[0025] Secondly, a data acquisition method is provided, applicable to a second device, which is an environmental IoT device. The method includes: the second device receiving first indication information from a first device, the first indication information being used to trigger the second device to acquire or report third data, the first indication information including one or more of the following: a second acquisition period, a second acquisition duration, or reporting conditions; the second device sending third data to the first device according to a second method, the second method including one or more of the following: a second acquisition period, a second acquisition duration, or reporting conditions, the third data being data acquired by the second device according to the second method.

[0026] Based on this method, the first device can trigger the second device to complete data acquisition or reporting in a second manner, such as acquiring or reporting data once or multiple times according to the second acquisition cycle or the second acquisition duration. This can solve the problem that the second device acquires or reports data once every time a higher-level network device or application-layer device, such as a third device, is triggered. The control of data acquisition or reporting can be delegated from the higher-level network device or application-layer device to the second device. This can achieve the goal of the second device completing one or more data acquisitions or reports on its own once the third device is triggered, and can effectively shorten the signaling and / or data transmission paths and times, consume less time, and thus improve the efficiency and flexibility of data acquisition.

[0027] In some implementations, the second method further includes one or more of the following: a second number of cycles or a third time period, and the first indication information further includes one or more of the following: a second number of cycles or a third time period; wherein, the second number of cycles is the number of second acquisition cycles, and the third time period is the time period to which the second acquisition cycle applies.

[0028] Based on this scheme, the second device can periodically initiate data acquisition or reporting according to the second acquisition cycle issued by the first device. This can achieve the goal of the second device acquiring data multiple times after the first device triggers it once, which can effectively reduce the workload of the first and third devices, as well as the signaling interaction overhead between the first and third devices and between the third and second devices, thereby improving data acquisition efficiency.

[0029] Optionally, the method further includes: when the data acquisition time reaches the second cycle number or exceeds the third time period, the second device stops data acquisition.

[0030] Based on this scheme, the second device can also automatically stop acquiring unnecessary data in a timely manner based on the termination condition of acquiring data according to the second acquisition cycle (second cycle number, third time period) to save power consumption.

[0031] In some implementations, the second method further includes one or more of the following: a second duration or a fourth time period, and the first indication information further includes one or more of the following: a second duration or a fourth time period; wherein, the second duration is the number of second acquisition durations, and the fourth time period is the time period to which the second acquisition duration applies.

[0032] Based on this scheme, the second device can initiate data acquisition or reporting once or multiple times according to the second acquisition duration issued by the first device. This achieves the goal of the second device acquiring data once or multiple times after the first device triggers it once, which can effectively reduce the workload of the first and third devices, as well as the signaling interaction overhead between the third and second devices, thereby improving data acquisition efficiency.

[0033] Optionally, the method further includes: when the data acquisition time reaches the second duration or exceeds the fourth time period, the second device stops acquiring data.

[0034] Based on this scheme, the second device can also automatically stop acquiring unnecessary data in a timely manner based on the termination condition of acquiring data according to the second acquisition duration (second duration number, fourth time period) to save power consumption.

[0035] In some implementations, the method further includes: the second device sending a fourth indication message to the first device, the fourth indication message indicating that the second device has acquired the third data, so as to notify the first device to read the data in a timely manner to avoid loss, thereby improving reliability.

[0036] Optionally, the fourth indication information includes one or more of the following: the number of resources or data volume requested, the data type, the process identifier, the remaining storage time or the identifier of the second device, wherein the process identifier is used to indicate the process of obtaining the third data, and the remaining storage time is used to indicate the duration for which the third data can be stored.

[0037] In some implementations, the first indication information further includes reporting conditions, and the third data is the data obtained by the second device when the reporting conditions are met, or the third data is the data in the original data obtained by the second device that meets the reporting conditions.

[0038] Based on this scheme, the second device can determine whether there is data in the raw data acquired by the second device that meets the reporting conditions. That is, the third data to be reported only includes data that meets the reporting conditions. If the reporting conditions are not met, no data will be reported, thereby reducing the amount of data to be reported and further improving the data acquisition efficiency.

[0039] In some implementations, the first indication information further includes reporting conditions; the method further includes: the second device sending a third indication information to the first device, the third indication information indicating that no event has occurred that meets the reporting conditions.

[0040] Based on this scheme, the second device can inform the first or third device that it has not obtained data that meets the reporting conditions. The reporting conditions typically include the conditions for the occurrence of abnormal events of the second device. The failure to obtain data that meets the reporting conditions indicates that the second device is working normally. Upon receiving the third instruction information, the first or third device can know that the second device is working normally and can also instruct the second device to discard the obtained data to reclaim storage resources.

[0041] In some implementations, the method further includes: the second device sending capability information of the second device to the first device, the capability information of the second device being used to determine the first indication information.

[0042] Optionally, the capability information of the second device includes one or more of the following: the data acquisition capability, counting / timing capability, or the ability to determine reporting conditions of the second device.

[0043] Based on this scheme, the second device can report its own capability information, so that the first device can customize data acquisition parameters according to the second device's capability information. This improves the accuracy of data acquisition, reduces the amount of data acquired and reported, and reduces the workload of the first device, thereby increasing data acquisition efficiency. For example, for a second device that meets the reporting conditions, the first instruction information issued by the first device may include the reporting conditions, while for a second device that does not meet the reporting conditions, the first instruction information issued by the first device may not include the reporting conditions.

[0044] In some implementations, the first device may be an environmental IoT controller, the first indication information and AC-D request information are carried in an initial message or a second message, and the third data includes the identifier of the second device. The identifier of the second device and the D-AC response information are carried in the same message to reduce the number of signaling and / or data interactions between the reader and the second device, thereby improving efficiency.

[0045] In some implementations, the first device can be a reader, the first indication information is carried in an initial message or a second message, and the third data includes the identifier of the second device. The identifier of the second device, the reader's reply information, and the AF reply information are carried in the same message to reduce the number of signaling and / or data interactions between the reader and the second device, thereby improving efficiency.

[0046] Thirdly, a data acquisition device is provided. This device is applicable to a first device, which may be a reader or an environmental IoT controller. The device includes a processing module and a transceiver module. The processing module is used to send first instruction information according to a first method, the first instruction information being used to instruct a second device to acquire or report first data. The first method includes one or more of the following: a first acquisition period or a first acquisition duration; the transceiver module is used to receive the first data from the second device.

[0047] In some implementations, the transceiver module is further configured to receive second indication information from a third device, the second indication information including a first acquisition cycle; the processing module is further configured to send the first indication information to the second device according to the first acquisition cycle.

[0048] Optionally, the second indication information may also include one or more of the following: a first number of cycles, a first time period, or a third stop indication, wherein the first number of cycles is the number of first acquisition cycles, the first time period is the time period to which the first acquisition cycle applies, and the third stop indication is used to indicate that data acquisition should be stopped.

[0049] Furthermore, the transceiver module is also used to send a first stop instruction to the second device. The first stop instruction is used to instruct the second device to stop data acquisition when the data acquisition time reaches a first number of cycles or exceeds a first time period.

[0050] In some implementations, the transceiver module is further configured to receive second indication information from a third device, the second indication information including a first acquisition duration; the first device sends the first indication information to the third device according to the first acquisition duration.

[0051] Optionally, the second indication information may further include one or more of the following: a first duration, a second time period, or a fourth stop indication; wherein the first duration is the number of the first acquisition duration, the second time period is the time period to which the first acquisition duration applies, and the fourth stop indication is used to indicate that data acquisition should be stopped.

[0052] Furthermore, the transceiver module is also used to send a second stop instruction to the second device. The second stop instruction is used to instruct the second device to stop data acquisition when the data acquisition time reaches a first duration or exceeds a second time period.

[0053] In some implementations, the transceiver module is also used to send first data or fourth indication information to a third device, wherein the fourth indication information is used to indicate that the second device has acquired the first data.

[0054] In some implementations, the first method further includes: reporting conditions; a transceiver module, further configured to receive second indication information from a third device, the second indication information including reporting conditions; the transceiver module, further configured to send second data or fourth indication information to the third device, the fourth indication information being used to indicate that the second device has obtained the second data, the second data being the data in the first data that meets the reporting conditions.

[0055] Optionally, the fourth instruction information includes one or more of the following: the requested amount of resources or data, the data type, or the identifier of the second device, so that the third device can read the first data or the second data.

[0056] In some implementations, the first method further includes: reporting conditions; a transceiver module, further configured to receive second indication information from a third device, the second indication information including reporting conditions; and the transceiver module, further configured to send third indication information to the third device, the third indication information indicating that an event satisfying the reporting conditions has not occurred.

[0057] The aforementioned transceiver module is used to implement the transceiver function. Further, the transceiver module may include a receiving module and a sending module. The sending module and receiving module are respectively used to implement the sending and receiving functions of the data acquisition device.

[0058] Optionally, the data acquisition device described in the third aspect may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the data acquisition device can perform the data acquisition method described in any implementation of the first aspect.

[0059] Furthermore, the technical effects of this data acquisition device can be referenced from the technical effects of the data acquisition method described in the first aspect, and will not be repeated here.

[0060] Fourthly, a data acquisition device is provided, suitable for a second device, which can be an environmental IoT device. The device includes a processing module and a transceiver module. The transceiver module is used to receive first indication information from a first device, the first indication information being used to trigger the device to acquire or report third data, the first indication information including one or more of the following: a second acquisition period, a second acquisition duration, or reporting conditions; the processing module is used to send third data to the first device according to a second method, the second method including one or more of the following: a second acquisition period, a second acquisition duration, or reporting conditions, the third data being data acquired by the second device according to the second method.

[0061] In some implementations, the second method further includes one or more of the following: a second number of cycles or a third time period, and the first indication information further includes one or more of the following: a second number of cycles or a third time period; wherein, the second number of cycles is the number of second acquisition cycles, and the third time period is the time period to which the second acquisition cycle applies.

[0062] Optionally, the processing module is also used to stop data acquisition when the data acquisition time reaches the second cycle number or exceeds the third time period.

[0063] In some implementations, the second method further includes one or more of the following: a second duration or a fourth time period, and the first indication information further includes one or more of the following: a second duration or a fourth time period; wherein, the second duration is the number of second acquisition durations, and the fourth time period is the time period to which the second acquisition duration applies.

[0064] Optionally, the processing module is also used to stop data acquisition when the data acquisition time reaches the second duration or exceeds the fourth time period.

[0065] In some implementations, the transceiver module is also used to send a fourth indication message to the first device, the fourth indication message being used to indicate that the second device has acquired the third data.

[0066] Optionally, the fourth indication information includes one or more of the following: the number of resources or data volume requested, the data type, the process identifier, the remaining storage time or the identifier of the second device, wherein the process identifier is used to indicate the process of obtaining the third data, and the remaining storage time is used to indicate the duration for which the third data can be stored.

[0067] In some implementations, the first indication information further includes reporting conditions, and the third data is the data obtained by the second device when the reporting conditions are met, or the third data is the data in the original data obtained by the second device that meets the reporting conditions.

[0068] In some implementations, the first indication information also includes reporting conditions; the transceiver module is further configured to send a third indication information to the first device, the third indication information indicating that no event has occurred that meets the reporting conditions.

[0069] In some implementations, the transceiver module is further configured to send the device's capability information to the first device, and the capability information of the second device is used to determine the first instruction information.

[0070] Optionally, the capability information of the second device includes one or more of the following: the data acquisition capability, counting / timing capability, or the ability to determine reporting conditions of the second device.

[0071] In some implementations, the first device may be an environmental IoT controller, the first indication information and AC-D request information are carried in an initial message or a second message, and the third data includes the identifier of the device, which is carried in the same message as the D-AC response information.

[0072] In some implementations, the first device may be a reader, the first indication information is carried in an initial message or a second message, and the third data includes the identifier of the second device. The identifier of the second device, the reader's reply information, and the AF reply information are carried in the same message.

[0073] The aforementioned transceiver module is used to implement the transceiver function. Further, the transceiver module may include a receiving module and a sending module. The sending module and receiving module are respectively used to implement the sending and receiving functions of the data acquisition device.

[0074] Optionally, the data acquisition device may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the data acquisition device can perform the data acquisition method described in the second aspect.

[0075] It should be noted that the data acquisition device can be a second device, such as an AIoT device, or a chip (system) or other component or assembly that can be set in the second device, or a device that includes the second device. This application does not limit this.

[0076] Furthermore, the technical effects of this data acquisition device can be referenced from the technical effects of the data acquisition method described in the second aspect, and will not be repeated here.

[0077] Fifthly, a data acquisition apparatus is provided. The data acquisition apparatus includes units or modules for performing any implementation of the second aspect, or includes units or modules for performing any implementation of the second aspect.

[0078] In one possible design of the fifth aspect, the data acquisition device may be the second device described in the first aspect, such as an AIoT device, or a chip (system) or other component or assembly that may be disposed in the second device.

[0079] It should be understood that the data acquisition apparatus includes modules, units, or means corresponding to the data acquisition method described in the first aspect above. These modules, units, or means can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units for performing the functions involved in the data acquisition method described above.

[0080] Furthermore, the technical effects of this data acquisition device can be referenced from the technical effects of the data acquisition method described in the first aspect, and will not be repeated here.

[0081] A sixth aspect provides a data acquisition apparatus. The apparatus includes a processor coupled to a memory for storing programs or instructions, which, when executed by the processor, cause the apparatus to perform a data acquisition method as described in any implementation of the first aspect, or to perform a data acquisition method as described in any implementation of the second aspect.

[0082] In one possible design of the sixth aspect, the data acquisition device may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the data acquisition device and other devices or equipment.

[0083] In this application, the data acquisition device may be the first device or the second device in the first aspect, or may be a chip (system) or other component or assembly disposed in the first device or the second device.

[0084] Furthermore, the technical effects of this data acquisition device can be referenced from the technical effects of the data acquisition method described in any of the implementations of the first aspect, and will not be repeated here.

[0085] In a seventh aspect, a communication system is provided. The communication system includes a first device and a second device. Optionally, the communication system may further include a third device.

[0086] Eighthly, a computer-readable storage medium is provided, storing a computer program or instructions that, when executed, cause a computer to perform a data acquisition method as described in any implementation of the first aspect, or a data acquisition method as described in any implementation of the second aspect.

[0087] Ninthly, a computer program product is provided, comprising computer program code, which, when executed on a computer, causes the computer to implement the data acquisition method described in any implementation of the first aspect, or to implement the data acquisition method described in any implementation of the second aspect. Attached Figure Description

[0088] Figure 1 is a flowchart of a data acquisition method;

[0089] Figure 2 is a schematic diagram of the structure of a communication system provided in an embodiment of this application;

[0090] Figure 3A is a flowchart illustrating a data acquisition method provided in an embodiment of this application;

[0091] Figure 3B is a flowchart illustrating another data acquisition method provided in an embodiment of this application;

[0092] Figure 4 is an example diagram of the data acquisition method shown in Figure 3A or Figure 3B;

[0093] Figure 5 is an example diagram of the AIoT controller triggering a data acquisition method according to a first data acquisition cycle provided in the embodiment of this application;

[0094] Figure 6 is an example diagram of the AIoT controller triggering a data acquisition method according to a first data acquisition duration provided in an embodiment of this application;

[0095] Figure 7 is an example of an interaction between an AIoT device and a reader when data acquisition is initiated by an AIoT controller, as provided in an embodiment of this application.

[0096] Figure 8 is another example of interaction between the AIoT device and the reader when data acquisition is initiated by the AIoT controller, as provided in an embodiment of this application.

[0097] Figure 9 is another example of interaction between the AIoT device and the reader when data acquisition is initiated by the AIoT controller, as provided in an embodiment of this application.

[0098] Figure 10 is an example diagram of how an AIoT device determines the reporting conditions according to an embodiment of this application;

[0099] Figure 11 is another example diagram of the AIoT controller determining the reporting conditions according to an embodiment of this application;

[0100] Figure 12 is another example diagram of the data acquisition method shown in Figure 3A or Figure 3B;

[0101] Figure 13 is an example diagram of a reader triggering a data acquisition method according to a second data acquisition cycle provided in an embodiment of this application;

[0102] Figure 14 is an example diagram of a reader triggering a data acquisition method according to a second data acquisition duration provided in an embodiment of this application;

[0103] Figure 15 is an example of an interaction between an AIoT device and a reader when data acquisition is initiated by the reader, as provided in an embodiment of this application.

[0104] Figure 16 is another example of interaction between the AIoT device and the reader when data acquisition is initiated by the reader, as provided in an embodiment of this application.

[0105] Figure 17 is another example of interaction between the AIoT device and the reader when data acquisition is initiated by the reader, as provided in an embodiment of this application.

[0106] Figure 18 is an example diagram of the AIoT device determining the reporting conditions according to an embodiment of this application;

[0107] Figure 19 is another example diagram showing how the reader determines the reporting conditions according to an embodiment of this application;

[0108] Figure 20 is an example diagram of reporting fourth instruction information provided in an embodiment of this application;

[0109] Figure 21 is another example diagram of another way of reporting fourth instruction information provided in an embodiment of this application;

[0110] Figure 22 is a schematic diagram of a data acquisition device provided in an embodiment of this application;

[0111] Figure 23 is a schematic diagram of another data acquisition device provided in an embodiment of this application. Detailed Implementation

[0112] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0113] First, referring to Figure 1, we will introduce the data acquisition technologies in the environmental Internet of Things.

[0114] For example, Figure 1 is a flowchart illustrating a data acquisition method. In current AIoT scenarios, data acquisition is typically triggered or initiated by an application function (AF). Specifically, as shown in Figure 1, the AF needs to send a data acquisition command (DL command) to the terminal device, such as an AIoT device. This command is first sent to the AIoT controller, which then forwards it to the reader, which in turn forwards it to the terminal device. The sent data acquisition commands include read, write, disable, and enable commands. The read command can be used to collect sensor data from the terminal device, such as temperature and humidity. After receiving the data acquisition command, the terminal device acquires the data and replies to the AF, following the reverse process of sending the data acquisition command.

[0115] It is evident that both issuing data acquisition commands and reporting acquired data require multiple forwardings, resulting in long signaling and / or data transmission paths and significant time consumption. Furthermore, data acquisition is triggered by the AF (Automatic Data Acquisition) and can only be triggered once for each acquisition, thus leading to low efficiency.

[0116] To address the aforementioned issues, embodiments of this application provide a data acquisition method that can effectively reduce the path and frequency of signaling and / or data interactions between the AF and the terminal device, thereby improving data acquisition efficiency.

[0117] Specifically, data can be acquired in the following ways:

[0118] 1. Periodic Acquisition: AF can instruct the AIoT controller or reader to trigger periodic data acquisition, such as by sending a data acquisition cycle to the AIoT controller or reader. Optionally, it can also send data type information and instructions to the AIoT controller or reader to perform periodic data acquisition. Accordingly, after receiving the above information, the AIoT controller or reader completes the data acquisition and reporting of the AIoT device according to the data acquisition cycle.

[0119] 2. Data Acquisition Based on Acquisition Duration: The AF can trigger data acquisition first and then acquire data according to the specified acquisition duration. Specifically, the AF can send the data acquisition duration to the AIoT controller or reader. Optionally, it can also send data type information and instructions to the AIoT controller or reader to acquire data according to the specified acquisition duration. Accordingly, after receiving the above information, the AIoT controller or reader begins to acquire data according to the specified acquisition duration, that is, it can acquire the AIoT device's data after triggering data acquisition or receiving a response from the AIoT device, after the specified acquisition duration.

[0120] 3. Event-Triggered Acquisition: When the AF needs to acquire data that meets certain events, it can trigger the AIoT controller or reader to acquire data according to the event trigger conditions. The AF can send the event trigger conditions to the AIoT controller or reader. Optionally, it can also send data type information, instructions to the AIoT controller or reader to acquire data according to the event trigger conditions, etc. Accordingly, after receiving the above information, the AIoT controller or reader begins to acquire data according to the event trigger conditions. For example, after acquiring data from the AIoT device, it compares it with the event trigger conditions. If the event trigger conditions are met, the data is reported to the AF; otherwise, the acquired data is discarded.

[0121] It should be noted that if the AIoT device lacks the corresponding capabilities, the AF or AIoT controller or reader can be instructed to control the AIoT device to complete data acquisition and reporting according to the data acquisition parameters. If the AIoT device has the corresponding capabilities, the AF, AIoT controller, or reader can also send the relevant data acquisition parameters, such as data acquisition cycle, data acquisition duration, and event triggering conditions, to the AIoT device, allowing the AIoT device to control data acquisition and reporting independently.

[0122] The technical solutions of this application embodiment can be applied to various communication systems, such as ambient power internet of things (AMP-IoT), narrowband internet of things (NB-IoT) systems, wireless fidelity (WiFi) systems, vehicle to everything (V2X) communication systems, device-to-device (D2D) communication systems, vehicle-to-everything (V2X) communication systems, 4th generation (4G) mobile communication systems, such as long term evolution (LTE) systems, worldwide interoperability for microwave access (WiMAX) communication systems, 5th generation (5G) mobile communication systems, such as new radio (NR) systems, and future communication systems, such as 6th generation (6G) mobile communication systems, etc.

[0123] This application will present various aspects, embodiments, or features relating to systems that may include multiple devices, components, modules, etc. It should be understood and appreciated that individual systems may include additional devices, components, modules, etc., and / or may not include all the devices, components, modules, etc. discussed in conjunction with the accompanying drawings. Furthermore, combinations of these approaches are also possible.

[0124] Furthermore, in the embodiments of this application, words such as "exemplarily" and "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as an "example" in this application should not be construed as being better or more advantageous than other embodiments or designs. Rather, the use of the word "example" is intended to present the concept in a specific manner.

[0125] In the embodiments of this application, the terms "information," "signal," "message," "channel," and "singaling" may sometimes be used interchangeably. It should be noted that, without emphasizing their distinction, they all convey the same meaning. Similarly, the terms "of," "corresponding (relevant)," and "corresponding" may sometimes be used interchangeably. It should be noted that, without emphasizing their distinction, they all convey the same meaning.

[0126] In the embodiments of this application, sometimes the subscript such as W1 may be mistakenly written as a non-subscript form such as W1. When the difference is not emphasized, the meaning they express is the same.

[0127] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0128] To facilitate understanding of the technical solutions provided in the embodiments of this application, the communication system applicable to the embodiments of this application will be described in detail first, taking the communication system shown in FIG2 as an example.

[0129] For example, Figure 2 is a schematic diagram of the architecture of a communication system provided in an embodiment of this application. As shown in Figure 2, the communication system includes a first device and a second device.

[0130] The first device can be a reader or an AIoT controller, and the second device can be a terminal device. The AIoT controller can be a core network element, such as an access and mobility management function (AMF) or a user plane function, while the terminal device can be an AIoT device, such as a smart tag, smart meter, or smart water meter.

[0131] In some implementations, the reader can be an access network device that can communicate directly with the environmental IoT controller. In other implementations, the reader can be user equipment (UE), in which case the reader can communicate with the environmental IoT controller through a base station.

[0132] The aforementioned access network equipment refers to devices located on the network side of the aforementioned communication system that have wireless transceiver capabilities, or chips or chip systems that can be installed in such devices. This access network equipment includes, but is not limited to: access points (APs) in wireless fidelity (WiFi) systems, such as home gateways, routers, servers, switches, bridges, etc.; evolved Node Bs (eNBs), radio network controllers (RNCs), Node Bs (NBs), base stations (BSs), base station controllers (BSCs), base transceiver stations (BTSs), home base stations (e.g., home evolved Node Bs, or home Node Bs, HNBs), baseband units (BBUs), wireless relay nodes, wireless backhaul nodes, transmission and reception points (TRPs or transmission points, TPs), etc., and can also be for 5G, such as New Radio (NR). In a radio (NR) system, a gNB, or a transmission point (TRP or TP), is a base station in a 5G system, one or a group of antenna panels (including multiple antenna panels), or a network node constituting a gNB or transmission point, such as a baseband unit (BBU), or a distributed unit (DU), a roadside unit (RSU) with base station functions, etc.

[0133] The aforementioned terminal device is a terminal that accesses the aforementioned communication system and has wireless transceiver capabilities, or a chip (system), component, or assembly that can be installed in the terminal. This terminal device can also be referred to as a user device, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user equipment. In the embodiments of this application, the terminal device can be an environmental IoT device (such as a water meter, electricity meter, electronic tag, etc.), a mobile phone, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical care, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc.

[0134] Optionally, the communication system may also include a third device. This third device may be an application service (AF) used to provide application services to the third device, such as acquiring data from the third device.

[0135] It should be noted that the solutions in the embodiments of this application can also be applied to other communication systems, and the corresponding names can be replaced by the names of the corresponding functions in other communication systems.

[0136] It should be understood that Figure 2 is a simplified schematic diagram for ease of understanding only, and the communication system may also include other network devices and / or other terminal devices, which are not shown in the figure.

[0137] The data acquisition method provided in the embodiments of this application will be described in detail below with reference to Figures 3A-21.

[0138] For example, Figure 3A is a schematic flowchart of a data acquisition method provided in an embodiment of this application. This data acquisition method can be applied to communication between a first device, a second device, and a third device. The first device can be an AIoT device, the second device can be an AIoT controller or reader, and the third device can be an AF (Automatic Data Acquisition). As shown in Figure 3A, the method includes the following steps:

[0139] S301, the first device sends a first instruction message to the second device according to a first method. The first instruction message is used to instruct the second device to acquire or report first data. The first method includes one or more of the following: a first acquisition period or a first acquisition duration. Accordingly, the second device receives the first instruction message and starts acquiring or reporting data.

[0140] S302, the second device sends the first data to the first device. Accordingly, the first device receives the first data.

[0141] The term "acquisition" can refer to collecting or reading data from a second device. Acquiring data from a second device can mean collecting or reading data from a second device.

[0142] In some implementations, the first acquisition period is used to indicate the time interval at which the first device triggers the second device to acquire or report data. For example, the first device may trigger the second device to acquire or report data every few minutes or every few hours. The first device triggers the second device to acquire or report data by sending a first indication message.

[0143] Based on this scheme, the first device can periodically trigger the second device to acquire data according to the first acquisition cycle in the second instruction information issued by the third device, such as the third device. This can achieve the goal of the second device acquiring data multiple times when the third device triggers it once, which can effectively reduce the workload of the third device and the signaling interaction overhead between the first and third devices, thereby improving the data acquisition efficiency.

[0144] Optionally, the parameters related to the first acquisition cycle may also include a stop condition for acquiring data according to the first acquisition cycle, such as the number of first cycles, a first time period, or a third stop indication. The number of first cycles refers to the number of first acquisition cycles, such as 100 cycles; the first time period refers to the applicable time period of the first acquisition cycle, such as 1 hour, 8 hours, or 2 days after receiving the first instruction information from the second device; and the third stop indication is used to indicate the cessation of data acquisition. For example, the first device instructs the second device to acquire or report data according to the first acquisition cycle. When the data acquisition time reaches the number of first cycles or exceeds the first time period, the first device generates a first stop indication and sends it to the second device. Upon receiving the first stop indication, the second device stops data acquisition, thus saving power by promptly stopping unnecessary data acquisition. For example, if the first acquisition cycle is 5 minutes and the number of first cycles is 100, then the first stop indication instructs the second device to acquire data every 5 minutes, and to stop acquiring data after 100 acquisitions and report the acquired data to the third device. For example, if the first acquisition cycle is 5 minutes and the first time period is 1000 minutes, then the first stop instruction is used to instruct the second device to acquire data once every 5 minutes, and to stop acquiring data after acquiring 1000 / 5 = 200 times and report the acquired data to the third device. As another example, when the third device no longer needs the second device to acquire more data, such as when the second device has acquired enough data for problem localization or risk assessment, the third device can issue a third stop instruction, instructing the first device to control the second device to stop acquiring data, thereby saving the power consumption of the second device.

[0145] Based on this scheme, the first device can also control the second device to stop acquiring data based on the end condition of acquiring data according to the first acquisition cycle (first cycle number, first time period), so that the second device can stop unnecessary data acquisition in time to save power consumption.

[0146] In some implementations, after instructing the second device to stop acquiring data after completing the data acquisition according to the first number of cycles and / or the first time period, the first device may also report the acquired data to the third device. For example, after the second device acquires the last set of data, the first device reports the acquired data to the third device.

[0147] In some implementations, the first acquisition duration is used to indicate the length of time after the first device triggers the second device to acquire data, waiting for the second device to report data. For example, the time interval between the first device sending the first instruction information to the second device and the second device reporting data can be 10 minutes, 1 hour, 1 day, etc., and this application embodiment does not limit it.

[0148] Optionally, the parameters related to the first acquisition duration may also include a stop condition for acquiring data according to the first acquisition duration, such as a first duration number, a second time period, or a fourth stop indication. The first duration number is the number of first acquisition durations, such as 50 durations; the second time period is the applicable time period for the first acquisition duration, such as 8 hours or 2 days after the first device sends the first instruction information; and the fourth stop indication is used to indicate the cessation of data acquisition. For example, the first device instructs the second device to acquire or report data according to the first acquisition duration. When the data acquisition duration reaches the first duration number or exceeds the second time period, the first device generates a second stop indication and sends it to the second device. Upon receiving the second stop indication, the second device stops data acquisition, thus saving power by promptly stopping unnecessary data acquisition. For example, if the first acquisition duration is 20 minutes and the first duration number is 100, then the second stop indication instructs the second device to acquire data every 20 minutes, and to stop acquiring data after 100 acquisitions, and then report the acquired data to the first device. For example, if the first data acquisition period is 20 minutes and the second period is 1000 minutes, then the second stop instruction instructs the second device to acquire data every 20 minutes, and to stop acquiring data after acquiring 1000 / 20 = 50 times and report the acquired data to the first device. As another example, when the third device no longer needs the second device to acquire more data, such as when the second device has acquired enough data for problem localization or risk assessment, the third device can issue a fourth stop instruction, instructing the first device to control the second device to stop acquiring data, thereby saving the power consumption of the second device.

[0149] In some embodiments, after instructing the second device to stop acquiring data after completing the data acquisition for a first duration and / or a second time period, the first device may report the acquired data to the third device. For example, after the second device acquires the last set of data, the first device reports the acquired data to the third device.

[0150] In some implementations, after issuing the first or second stop instruction, the first device may not immediately report the acquired data, such as before the third device has issued a read command and allocated resources. Instead, it may report a fourth instruction to the third device, which indicates that the second device has acquired the first data. Accordingly, upon receiving the fourth instruction, the third device can determine whether to read the data. If so, it can send a read command to the second device; otherwise, it can instruct the second device to delete or discard the acquired data.

[0151] It should be noted that the first acquisition period and the first acquisition duration can also be combined. Specifically, the first acquisition duration can be equal to or less than the first acquisition period. Optionally, when both the first acquisition duration and the first acquisition period are configured, data acquisition ends whichever comes first. For example, if the first acquisition period is 20 minutes, the first period count is 10, the first acquisition duration is 10 minutes, and the first duration count is 100, then 20*10 < 20*1000. In this case, the first device can issue a first stop instruction 200 minutes after issuing the first instruction information to instruct the second device to stop data acquisition or reporting. As another example, if the first acquisition period is 20 minutes, the first period count is 100, the first acquisition duration is 10 minutes, and the first duration count is 10, then 10*10 < 20*100. In this case, the first device can issue a second stop instruction 100 minutes after issuing the first instruction information to instruct the second device to stop data acquisition or reporting. For example, if the first acquisition cycle is 10 hours and the first acquisition duration is 1 hour, the second device can acquire one or more sets of data every 10 hours according to the first acquisition duration, such as the first 1 hour, the last 1 hour, the odd-numbered 1 hour, the even-numbered hour, etc. within each 10-hour cycle.

[0152] Optionally, the first method may also include reporting conditions, such as event triggering conditions, used by the first device to filter the raw data acquired by the second device before reporting it to the third device, thereby reducing the amount of reported data and improving data acquisition efficiency. The reporting conditions may include one or more of the following: temperature, water level, humidity, pressure, smoke concentration, gas concentration, vibration, and traffic flow, each below or above a certain threshold. It can be seen that when the reporting conditions are met, it usually indicates that one or more abnormal events have occurred. These abnormal events may negatively impact the safe and efficient operation of the system, thus posing a safety risk and requiring reporting and processing.

[0153] In some implementations, after receiving the first data acquired by the second device, the first device can determine whether there is data in the first data that meets the reporting conditions. For example, the first data includes temperature data. If the temperature reported by the second device meets the reporting conditions (temperature exceeds a temperature threshold), the first device reports the temperature data exceeding the temperature threshold to the third device. For example, if the second device does not determine whether the acquired first data meets the reporting conditions, such as if the second device does not have the ability to determine the reporting conditions, or although the second device has the ability to determine the reporting conditions but the first device does not instruct the second device to determine the reporting conditions, then the first data reported by the second device may or may not contain data that meets the reporting conditions. In this case, the first device can determine whether there is data in the first data reported by the second device that meets the reporting conditions, that is, filter out the second data that meets the reporting conditions from the first data reported by the second device and report it to the third device.

[0154] It should be noted that when there is no data that meets the reporting conditions, the first device does not need to report any data to the third device, in order to reduce the amount of data transmitted and improve efficiency.

[0155] Furthermore, if no data meets the reporting conditions, the first device can report a third indication to the third device, indicating that no event meeting the reporting conditions has occurred. In other words, the second device has not obtained data that meets the reporting conditions.

[0156] Based on this scheme, the first device can inform the third device that the second device has not obtained second data that meets the reporting conditions. The reporting conditions typically include the occurrence conditions of an abnormal event of the second device. The failure to obtain data that meets the reporting conditions indicates that the second device is operating normally. Upon receiving the third indication information, the third device can know that the second device is operating normally and can also instruct the first and / or second devices to discard the obtained data to reclaim storage resources. The third indication information can be generated by the first device based on the judgment result of the reporting conditions.

[0157] Optionally, if data meeting the reporting conditions exists, and the first or third device has not yet issued a read command or allocated resources, the first device may report a fourth indication to the third device. This fourth indication indicates that the first data acquired by the second device contains second data meeting the reporting conditions, thus notifying the third device to read it. In other words, the fourth indication indicates that data acquisition or reporting has been successfully triggered, and second data meeting the reporting conditions has been acquired. The fourth indication may be generated by the first device based on the judgment result of the reporting conditions and may include one or more of the following: the requested resource quantity or data volume, data type, and the identifier or type of the second device, in order to request the third device to allocate resources, such as time-frequency resources or data channel resources.

[0158] Based on this scheme, when the first device learns that the second device has obtained second data that meets the reporting conditions from the first data, the first device can proactively request the third device to read the second data to avoid data loss and thus improve reliability. After receiving the fourth instruction information, the third device can determine whether it needs the data. If it does, it reads the data and allocates resources for the second data; if it does not need it, it can instruct the first device to delete or discard the second data to reclaim storage resources.

[0159] The data types can include: temperature, water level, humidity, pressure, smoke concentration, gas concentration, vibration, traffic flow, and AIoT device status information (usage status: number of uses, years of use, usage records, etc.).

[0160] It should be noted that if the third device already knows the data type reported by the second device, for example, the third device can know the data type reported by the second device based on the identifier or type reported by the second device, or the third device has already indicated the data type that the second device needs to obtain, then the fourth indication information may not include the data type, so as to reduce the amount of data transmitted and improve efficiency.

[0161] In some implementations, the aforementioned first indication information can be determined based on second indication information from a higher-level network device or application-layer device, such as a third device. Therefore, optionally, before the first device sends the first indication information to the second device in S301, the method further includes:

[0162] The first device receives a second instruction from the third device. The second instruction may include one or more of the following: a first acquisition period, a first acquisition duration, or reporting conditions. That is, the second instruction may include the content of the first method.

[0163] Optionally, the second indication information may also include a stop condition for acquiring data according to the first acquisition duration, such as the first duration number, the second time period, and / or a stop condition for acquiring data according to the first acquisition cycle, such as the first cycle number, the first time period.

[0164] Accordingly, in step S301, the first device sends first instruction information to the second device in a first manner, which may include one or more of steps 1A, 1B, and 1C:

[0165] Step 1A: The first device sends a first instruction message to the second device according to a first acquisition cycle. In other words, the first device can act as the initiator or trigger of data acquisition, controlling the data acquisition process of the second device according to the first acquisition cycle. For example, after receiving the second instruction message, the first device can send the first instruction message to the second device according to the first acquisition duration. The second device can start data acquisition after receiving the first instruction message, and stop data acquisition and report upon receiving the first stop instruction, thereby saving power consumption of the second device.

[0166] Based on this scheme, the first device can periodically trigger the second device to acquire data according to the first acquisition cycle in the second instruction information issued by the third device or application layer device, such as the third device. This can achieve the goal of the second device acquiring data multiple times when the third device triggers once, which can effectively reduce the workload of the third device and the signaling interaction overhead between devices, and improve efficiency.

[0167] Furthermore, after initiating data acquisition, the first device can also determine whether the stop condition for acquiring data according to the first acquisition cycle is met, such as the data acquisition time reaching the first cycle number or exceeding the first time period. If the stop condition is met, the first device can send a first stop instruction to the second device so that the second device can promptly stop unnecessary data acquisition, thereby reducing power consumption.

[0168] Step 1B: The first device sends a first instruction message to the second device according to the first acquisition duration. In other words, the first device can act as the initiator or trigger of data acquisition, controlling the data acquisition process of the second device according to the first acquisition duration. For example, after receiving the second instruction message, the first device can send the first instruction message to the second device according to the first acquisition duration. The second device can start data acquisition after receiving the first instruction message and stop data acquisition after receiving the second stop instruction from the first device, thereby saving power consumption of the second device.

[0169] Based on this scheme, the first device can trigger the second device to acquire data according to the first acquisition duration in the second instruction information issued by the third device or application layer device, such as the third device. This can achieve the goal of the second device acquiring data multiple times with a single trigger from the third device, effectively reducing the workload of the third device and the signaling interaction overhead between devices, thereby improving efficiency.

[0170] Furthermore, after initiating data acquisition, the first device can also determine whether the stop condition for acquiring data according to the first acquisition duration is met, such as the data acquisition time having reached the first duration or the second time period. If the stop condition is met, the first device can send a second stop instruction to the second device so that the second device can promptly stop unnecessary data acquisition, thereby reducing power consumption.

[0171] Step 1C: The first device sends a first instruction message to the second device, instructing the second device to begin acquiring first data and reporting it to the first device. Then, the first device determines whether there is second data in the first data that meets the reporting conditions. If so, the first device reports the second data in the first data that meets the reporting conditions to the third device. Optionally, when the amount of data meeting the reporting conditions reaches a data volume threshold, such as when the data volume is sufficient to locate the problem of the abnormal event corresponding to the reporting conditions, an instruction to stop data acquisition can be issued to the second device to save power consumption of the second device.

[0172] Based on this scheme, the first device can use reporting conditions to filter the first data obtained by the second device, and only report the second data that meets the reporting conditions to the third device. If there is no second data that meets the reporting conditions in the first data, the first device can delete / discard the first data, that is, it does not need to report any data to the third device, so as to reduce the amount of data reported and further improve efficiency.

[0173] Optionally, the second indication information may further include a process identifier, which indicates the process for obtaining the first data. Correspondingly, the first indication information may also include the process identifier, so that the first device triggers the second device to obtain the first data in the process corresponding to the process identifier. Further, the third indication information may also include the process identifier to notify the third device that the second device has not obtained data that meets the reporting conditions in the process corresponding to the process identifier; and the fourth indication information may also include the process identifier to notify the third device that the second device has obtained second data that meets the reporting conditions in the process corresponding to the process identifier.

[0174] Based on the data acquisition method shown in Figure 3A, the first device can trigger the second device to complete data acquisition or reporting in a first manner. For example, the second device can be triggered to acquire or report data once or multiple times according to the first acquisition cycle or the first acquisition duration. This can solve the problem that the second device acquires or reports data once for each trigger by a higher-level network device or application layer device, such as a third device. The control of data acquisition or reporting can be delegated from the higher-level network device or application layer device to the first device. This can achieve the goal of the first device controlling the second device to acquire or report data once or multiple times when the third device is triggered once. It can also effectively shorten the signaling and / or data transmission path and number of times, consume less time, and thus improve the efficiency and flexibility of data acquisition.

[0175] It should be noted that if the second device possesses corresponding capabilities, such as time management / counting capabilities, the ability to determine stop conditions, and the ability to determine reporting conditions, the first device can send data acquisition parameters corresponding to the capabilities of the second device, such as the second acquisition cycle and / or the second acquisition duration, and stop conditions (such as the number of second cycles, the third time period, the number of second durations, and the fourth time period), as part of the first instruction information to the second device, allowing the second device to control the acquisition or reporting of data independently. Similarly, if the second device possesses the ability to determine reporting conditions, the first device can also send the reporting conditions as part of the first instruction information to the second device, allowing the second device to filter out data that meets the reporting conditions from the acquired raw data. Therefore, this application embodiment provides another data acquisition method, which will be described in detail below with reference to Figure 3B.

[0176] For example, Figure 3B is a schematic flowchart of another data acquisition method provided in an embodiment of this application. This data acquisition method can be applied to communication between a first device, a second device, and a third device. As shown in Figure 3B, the method includes the following steps:

[0177] S401, the first device sends a first instruction message to the second device, the first instruction message being used to instruct the second device to acquire or report third data in a second manner. Accordingly, the second device receives the first instruction message.

[0178] S402, the second device sends third data to the first device according to a second method, the second method including one or more of the following: a second acquisition period, a second acquisition duration, or reporting conditions, and the third data is data acquired or reported by the second device according to the second method. Accordingly, the first device receives the third data.

[0179] The term "acquisition" can refer to collecting or reading data from a second device. Acquiring data from a second device can mean collecting or reading data from a second device.

[0180] In some implementations, the second acquisition period is used to indicate the time interval for the second device to acquire or report data. For example, the second device may acquire or report data every few minutes, or every few hours. In this scenario, the first device may send the second acquisition period to the second device so that the second device can acquire or report data according to the second acquisition period. In this scenario, the first indication information may include the second acquisition period.

[0181] Optionally, the configuration parameters related to the second acquisition cycle may also include a stop condition for acquiring data according to the second acquisition cycle, such as the number of second cycles or a third time period. The number of second cycles refers to the number of second acquisition cycles, such as 100 cycles, and the third time period refers to the applicable time period for the second acquisition cycle, such as 1 hour, 8 hours, or 2 days after receiving the first instruction information from the second device. This stop condition is used to instruct the second device to automatically stop acquiring or reporting data; that is, the stop condition instructs the second device to automatically stop after completing the data acquisition or reporting according to the number of second cycles or the third time period, in order to save power consumption. For example, if the second acquisition cycle is 5 minutes and the number of second cycles is 100, then the second device acquires or reports data once every 5 minutes and stops after acquiring or reporting 100 times. As another example, if the second acquisition cycle is 5 minutes and the third time period is 1000 minutes, then the second device acquires or reports data once every 5 minutes and stops after acquiring or reporting 1000 / 5 = 200 times. In this scenario, the first instruction information may also include the number of second cycles or the third time period.

[0182] It should be noted that the first device can trigger the second device to acquire or report data by sending a first instruction message. This allows the first device to trigger a single data acquisition or report, while the second device completes one or more data acquisition or reporting processes, thus improving efficiency. For example, the first device can send the first instruction message only once, while the second device can acquire or report data one or more times according to a second acquisition cycle, the number of cycles, or a third time period.

[0183] In some implementations, the second acquisition duration is used to indicate the length of time the second device acquires or reports data, such as 20 minutes, 2 hours, or 2 days. In this scenario, the first device can send the second acquisition duration to the second device so that the second device can acquire or report third data based on the second acquisition duration. In this scenario, the first indication information may include the second acquisition duration.

[0184] Optionally, the configuration parameters related to the second acquisition duration may also include a stop condition for acquiring data according to the second acquisition duration, such as a second duration number or a fourth time period. The second duration number is the number of second acquisition durations, such as 50 durations, and the fourth time period is the applicable time period for the second acquisition duration, such as 8 hours or 2 days after receiving the first instruction information from the second device. This stop condition is used to instruct the second device to automatically stop acquiring or reporting data; that is, the stop condition instructs the second device to automatically stop acquiring or reporting data after completing the acquisition or reporting according to the second duration number and / or the fourth time period, in order to save power consumption. For example, if the second acquisition duration is 20 minutes and the second duration number is 100, then the second device acquires or reports data once every 20 minutes, and stops after acquiring or reporting 100 times. As another example, if the second acquisition duration is 20 minutes and the fourth time period is 1000 minutes, then the second device acquires or reports data once every 20 minutes, and stops after acquiring or reporting 1000 / 20 = 50 times. In this scenario, the first instruction information may also include a second duration or a fourth time period.

[0185] It should be noted that the first device can trigger the second device to acquire or report data by sending a first instruction message, and the second device can complete the task once or multiple times after the first device triggers it, thereby improving efficiency. For example, the first device can send the first instruction message only once, and the second device can acquire or report data once or multiple times according to the second acquisition duration, the second duration number, or the fourth time period.

[0186] In some embodiments, after the second device stops automatically according to the above-described stopping conditions, it can report the acquired data to the first or third device. For example, after the second device acquires the last set of data, it reports the acquired data to the first or third device.

[0187] In some implementations, after the second device automatically stops acquiring data according to the aforementioned stopping conditions, the second device may not immediately report the acquired data. For example, if the first or third device has not yet issued a read command or allocated resources, the second device may report a fourth indication message to the first or third device. This fourth indication message indicates that the second device has acquired the third data. Correspondingly, upon receiving the fourth indication message, the first or third device can determine whether to read the third data. If so, it can send a read command to the second device; otherwise, it can instruct the second device to delete or discard the acquired third data to reclaim storage resources.

[0188] It should be noted that the second acquisition period and the second acquisition duration can also be combined. Specifically, the second acquisition duration can be equal to or less than the second acquisition period. When both the second acquisition duration and the second acquisition period are configured simultaneously, data acquisition or reporting can be stopped immediately regardless of which stop condition is met. For example, if the second acquisition period is 20 minutes, the second period count is 100, the second acquisition duration is 10 minutes, and the second duration count is 10, then 10*10 < 20*100, and the second device can automatically stop data acquisition or reporting 100 minutes after the first instruction information is issued. As another example, if the second acquisition period is 20 minutes, the second period count is 100, the second acquisition duration is 10 minutes, and the second duration count is 10, then 10*10 < 20*100, and the second device can automatically stop data acquisition or reporting 100 minutes after receiving the first instruction information. For example, the second acquisition cycle is 10 hours, the second acquisition duration is 1 hour, and the second device can acquire or report one or more sets of data with a duration of 1 hour every 10 hours, such as the first 1 hour, the last 1 hour, odd-numbered 1 hours, even-numbered hours, etc. within each 10-hour cycle.

[0189] Optionally, the second method may also include reporting conditions, such as event triggering conditions, used to filter the raw data acquired by the second device before reporting, thereby reducing the amount of reported data and improving data acquisition efficiency. The reporting conditions may include one or more of the following: temperature, water level, humidity, pressure, smoke concentration, gas concentration, vibration, and traffic flow, each below or above a certain threshold. It can be seen that when the reporting conditions are met, it usually indicates that one or more abnormal events have occurred. These abnormal events may negatively impact the safe and efficient operation of the environmental IoT, potentially posing safety risks and requiring reporting and processing.

[0190] In some implementations, the second device can independently determine whether the acquired raw data contains data that meets the reporting conditions. In this scenario, the first indication information may include the reporting conditions. If no data meets the reporting conditions, no data needs to be reported to the first device. If data meets the reporting conditions, only the data meeting the conditions can be reported to the first device, thereby reducing the amount of data transmitted along the data reporting path and improving efficiency. In other words, in this case, the third data reported by the second device can be data that meets the reporting conditions. After receiving the third data, the first device can directly report it to the third device, thereby reducing the workload of the first device and improving efficiency.

[0191] In some implementations, if the raw data acquired by the second device does not contain data that meets the reporting conditions, the second device may send a third indication message to the first or third device. This third indication message indicates that no event meeting the reporting conditions has occurred, meaning the second device has not acquired data that meets the reporting conditions. Accordingly, the first device receives the third indication message. This third indication message may be generated by the second device based on the judgment result of the reporting conditions.

[0192] Based on this scheme, the second device can inform the first or third device that it has not obtained data that meets the reporting conditions. The reporting conditions typically include the conditions for the occurrence of abnormal events of the second device. The failure to obtain data that meets the reporting conditions indicates that the second device is working normally. Upon receiving the third instruction information, the first or third device can know that the second device is working normally, and can also instruct the second device to delete or discard the obtained invalid data in order to reclaim storage resources.

[0193] In some implementations, if the second device has acquired the third data and the first or third device has allocated corresponding resources, the second device can immediately report the acquired third data to the first or third device. For example, if the third data is acquired according to the second acquisition cycle or the second acquisition duration, it can be reported according to the second acquisition cycle or the second acquisition duration, such as reporting each acquisition as it is acquired, or reporting all at once after data acquisition stops. Another example is that if the third data is acquired according to the second acquisition cycle and reporting conditions, it can be reported according to the second acquisition cycle and reporting conditions, such as reporting the third data in each cycle, or reporting all at once after data acquisition stops. Yet another example is that if the third data is acquired according to reporting conditions, it can be reported according to the reporting conditions, such as reporting once after acquiring a certain amount of third data, or reporting all at once after data acquisition stops. This application does not limit the reporting method of the third data in its embodiments.

[0194] In other implementations, after the second device obtains the third data, it may not report it immediately. For example, if the first or third device does not allocate resources for the third data, it may first report a fourth indication message to the first or third device. The fourth indication message is used to indicate that the second device has obtained the third data, so as to notify the first or third device to read it, so as to avoid data loss and improve reliability.

[0195] Optionally, the fourth instruction information may include one or more of the following: the requested quantity or amount of resources or data, the data type, the identifier or type of the second device, so as to request the first or third device to allocate resources, such as time-frequency resources, data channel resources, etc.

[0196] The data types can include: temperature, water level, humidity, pressure, smoke concentration, gas concentration, vibration, traffic flow, and status information of the second equipment (usage status: number of uses, years of use, usage records, etc.).

[0197] It should be noted that if the first device already knows the data type reported by the second device, for example, if the first device has already determined the data type reported by the second device based on the identifier or device type reported by the second device, or if the first device has already indicated the data type that the second device needs to obtain, then the fourth indication information may not include the data type of the third data, in order to reduce the amount of data transmitted and improve efficiency.

[0198] Accordingly, after receiving the fourth instruction information, the first or third device can determine whether to read the third data acquired by the second device. If so, the first or third device can send resource configuration information (such as time-frequency resource and data channel resource configuration information) to the second device. Optionally, the resource configuration information can be determined with reference to the content of the fourth instruction information.

[0199] In some implementations, the fourth indication information may be determined and reported by the second device based on one or more of the second acquisition cycle, the second acquisition duration, and the reporting conditions. For example, the first indication information includes the second acquisition duration and the reporting conditions. The second device may determine whether there is data in the acquired raw data that meets the reporting conditions during each second acquisition duration. If so, it generates and reports a fourth indication information during each second acquisition duration. Alternatively, the second device may determine whether there is data in the acquired raw data that meets the reporting conditions after stopping data acquisition according to the second acquisition duration. If so, it generates and reports a fourth indication information. This application does not limit the implementation method of generating and reporting the fourth indication information.

[0200] Based on this scheme, when the second device acquires data (such as data that meets the reporting conditions, or data acquired according to the second acquisition cycle or the second acquisition duration), the first device can proactively request the first or third device to read the data to avoid data loss and thus improve reliability. Correspondingly, after receiving the fourth instruction information, the first device can determine whether it needs the data. If needed, it reads the data and allocates resources; if not needed, it can instruct the second device to delete or discard the data to reclaim storage resources. Alternatively, after receiving the fourth instruction information, the first device can also forward the fourth instruction information to the third device, which then determines whether to read the information. After receiving the fourth instruction information, the third device determines whether it needs the data. If needed, it allocates resources to read the data; if not needed, it can instruct the second device through the first device to delete or discard the data to reclaim storage resources.

[0201] In some implementations, the aforementioned first indication information can be determined based on second indication information from a higher-level network device or application-layer device, such as a third device. Therefore, optionally, before the first device sends the first indication information to the second device in S401, the method further includes:

[0202] The first device receives a second instruction from the third device. The second instruction may include one or more of the following: a second acquisition period, a second acquisition duration, or reporting conditions. That is, the second instruction includes the content of the second method.

[0203] Optionally, the second indication information may also include a stop condition for acquiring data according to a second acquisition duration, such as a second duration number, a fourth time period, and / or a stop condition for acquiring data according to a second acquisition cycle, such as a second cycle number, a third time period.

[0204] Accordingly, S401 and S402 can be specifically implemented as step 2:

[0205] Step 2: The first device sends a first instruction message to the second device, wherein the first instruction message includes one or more of the following: a second acquisition period, a second acquisition duration, or reporting conditions. Accordingly, after receiving the first instruction message, the second device begins to acquire data according to the second method, and then reports the acquired third data to the first device, until the stop condition is met and it automatically stops acquiring data.

[0206] Specifically, step 2, where the first device sends the first indication information to the second device, may include steps 2A and / or 2B or 2C:

[0207] Step 2A: The first device sends a first instruction message to the second device, wherein the first instruction message includes a second acquisition period. In other words, when the second device has time management capabilities, the first device can also send the second acquisition period to the second device, which can then control the data acquisition process according to the second acquisition period.

[0208] Based on this scheme, the first device can send the second acquisition cycle in the second instruction information issued by the application layer device, such as the third device, to the second device. The second device can acquire data according to the second acquisition cycle, which can achieve the purpose of the third device triggering once and the second device acquiring multiple times. This can effectively reduce the workload of the first device and the signaling interaction overhead between the first device and the third device, thereby improving efficiency.

[0209] Furthermore, the second instruction information may also include a stop condition for acquiring data according to the second acquisition cycle, such as the second cycle number or a third time period. Accordingly, the second device can acquire data according to the second acquisition cycle after receiving the first instruction information, and automatically stop acquiring data according to the second cycle number or the third time period.

[0210] Based on this scheme, the first device can send the second instruction information issued by the third device, along with the stop conditions for acquiring data according to the second acquisition cycle (such as the second cycle number or the third time period), to the second device. After the second device starts acquiring data according to the second acquisition cycle, it can determine whether the stop condition is met. If it is met, it can stop acquiring data automatically, so as to stop unnecessary data acquisition in time and reduce power consumption.

[0211] Step 2B: The first device sends a first instruction message to the second device, wherein the first instruction message includes a second acquisition duration. In other words, when the second device has time management capabilities, the first device can also send the second acquisition duration to the second device, which can then control the data acquisition process itself based on the second acquisition duration.

[0212] Based on this scheme, the first device can send the second acquisition duration in the second instruction information issued by the third device to the second device. The second device can acquire data according to the second acquisition duration, which can achieve the purpose of the third device triggering once and the second device acquiring multiple times. This can effectively reduce the workload of the first device and the signaling interaction overhead between the first device and the third device, thereby improving efficiency.

[0213] Furthermore, the second instruction information may also include a stop condition for acquiring data according to the second acquisition duration, such as a second duration number or a fourth time period. Accordingly, after receiving the first instruction information, the second device can acquire data according to the second acquisition duration and automatically stop the data acquisition process according to the second duration number or the fourth time period to save power consumption.

[0214] Based on this scheme, the first device can send the stop condition for acquiring data according to the second acquisition duration (such as the second acquisition duration number or the fourth time period) in the second instruction information issued by the third device to the second device. After the second device starts acquiring data according to the second acquisition duration, it can determine whether the stop condition is met. If it is met, it will stop acquiring data automatically so as to stop unnecessary data acquisition in time and reduce power consumption.

[0215] In step 2C, the first device sends a first instruction message to the second device, which includes reporting conditions. Upon receiving the first instruction message, the second device begins acquiring data and determines whether there is third data in the acquired raw data that meets the reporting conditions. If so, the third data meeting the reporting conditions is reported to the second device; otherwise, no data is reported. Optionally, when the second device determines that the number of third data meeting the reporting conditions reaches a data volume threshold, if the data volume is sufficient to locate the abnormal event corresponding to the reporting conditions, the second device can automatically stop data acquisition to save power.

[0216] Based on this scheme, when the second device has the ability to judge the reporting conditions, the first device can also instruct the second device to first use the reporting conditions to filter the acquired raw data, and only report the data that meets the reporting conditions to the first device. If there is no data that meets the reporting conditions, it will not be reported, so as to reduce the amount of data reported and further improve the data acquisition efficiency.

[0217] Optionally, the second indication information may further include a process identifier, which indicates the process for obtaining the third data. Correspondingly, the first indication information may also include the process identifier, so that the second device obtains the third data in the process corresponding to the process identifier. Further, the third indication information may also include the process identifier to notify the first or third device that the second device has not obtained data that meets the reporting conditions in the process corresponding to the process identifier; and the fourth indication information may also include the process identifier to notify the first or third device that the second device has obtained third data that meets the reporting conditions in the process corresponding to the process identifier.

[0218] It should be noted that the first indication information can also be determined based on the capabilities of the second device. In some implementations, the method further includes:

[0219] The second device sends its capability information to the first device, which indicates the capabilities of the second device. Correspondingly, the first device receives the capability information from the second device.

[0220] Optionally, the capability information of the second device includes one or more of the following: the data acquisition capability, counting / timing capability, or the ability to determine reporting conditions of the second device.

[0221] The data acquisition capability can include the maximum amount of data that the second device can acquire, the maximum data cache size, and the maximum duration of the data that can be acquired. The counting / timing capability can be understood as the second device having time management capabilities, which can be used by the first or third device to determine the second acquisition cycle and / or the second acquisition duration and the stopping conditions. The ability to judge the reporting conditions refers to the second device's ability to judge whether one or more physical quantities, such as temperature, humidity, and air pressure, are greater than or less than the corresponding threshold, which can be used by the first or third device to determine the reporting conditions.

[0222] It should be noted that the second device can proactively report its own capability information, or it can report its own capability information when it receives a capability query request from a higher-level device or an application-layer device. This application embodiment does not impose any restrictions on this.

[0223] Based on this scheme, the second device can report its own capability information, so that the first device can customize data acquisition parameters for the second device according to its capability information. This improves the accuracy of data acquisition, reduces the amount of data acquired and reported, and also reduces the workload of the first device in filtering data, thereby improving data acquisition efficiency. For example, for a second device that meets the reporting conditions, the first instruction information issued by the first device may include the reporting conditions, while for a second device that does not meet the reporting conditions, the first instruction information issued by the first device may not include the reporting conditions.

[0224] In some implementations, the first device is an environmental IoT controller, and the signaling and / or data interaction between the first and second devices can be forwarded by a reader. Between the second device and the reader, the first indication information and the AC-D request information are carried in an initial message or a second message (Msg2). The AC-D request information may include configuration parameters indicating that the environmental IoT controller has successfully triggered the second device to acquire data. For example, the third data includes the identifier of the second device, which is carried in the same message as the D-AC response information. The D-AC response information is a recovery message for the AC-D request information, reducing the number of signaling and / or data interactions between the reader and the second device, thereby improving efficiency. The AC-D request information and D-AC response information are the interaction signaling between the second device and the environmental IoT controller, which is invisible to the reader and only needs to be forwarded directly.

[0225] In other implementations, the first device is a reader, and the first indication information is carried in an initial message or a second message. Correspondingly, the first device is a reader, and the third data includes the identifier of the second device. The identifier of the second device, along with the reader's response information and the AF response information, are carried in the same message to reduce the number of signaling and / or data interactions between the reader and the second device, thereby improving efficiency.

[0226] Based on the data acquisition method shown in Figure 3B, the first device can instruct the second device to complete data acquisition or reporting in a second manner, such as acquiring data once or multiple times according to the second acquisition cycle or the second acquisition duration. It does not require higher-level network devices or application layer devices, such as a third device, to trigger data acquisition. The control of data acquisition can be delegated from higher-level network devices or application layer devices to the second device. This can achieve the goal of the second device acquiring or reporting once or multiple times when the first or third device triggers the data acquisition once. It can also shorten the signaling and / or data transmission path, reduce the time consumption, and thus improve the efficiency and flexibility of data acquisition.

[0227] It should be noted that the two data acquisition methods shown in Figures 3A and 3B can also be used in combination. For example, based on the data acquisition method shown in Figure 3A, the reporting conditions can be sent to a second device with the ability to determine the reporting conditions. This allows the second device to acquire the original data (first data) and then report the second data that meets the reporting conditions to the first device, instead of reporting the original data itself. In this case, the first device can directly report to the third device without needing to determine whether the second data reported by the second device meets the reporting conditions, thus reducing the workload of the first device and improving efficiency.

[0228] The technical solutions provided in the embodiments of this application are explained in detail below with reference to several examples.

[0229] For example, Figure 4 is an example diagram of the data acquisition method shown in Figure 3A or Figure 3B. The first device can be the AIoT controller in Figure 4, the second device can be the AIoT device in Figure 4, and the third device can be the AF in Figure 4.

[0230] As shown in Figure 4, the data acquisition process may include an initial triggering phase and either a repeated triggering phase 1 or a repeated triggering phase 2. The initial triggering phase is initiated by the AF, repeated triggering phase 1 is initiated by the AIoT controller and controls the second device to complete data acquisition or reporting according to the first method, and repeated triggering phase 2 is initiated by the AIoT controller and the AIoT device controls the data acquisition or reporting itself. These will be explained below.

[0231] During the initial triggering phase, AF can send downlink commands (DL commands) to AIoT devices through the AIoT controller and reader.

[0232] First, the AF sends a downlink command to the AIoT controller. In addition, the AF can also send a second indication to the AIoT controller. This second indication may include one or more of the following: the data type to be acquired, the first or second acquisition duration, the first or second acquisition cycle, the third or fourth stop indication, reporting conditions (such as event triggering conditions), and the AIoT device ID. The second indication can also be used to indicate the data type, data volume, and process identifier of the data to be acquired.

[0233] In some implementations, corresponding to the repeated triggering phase 1, the second indication information is used to instruct the AIoT controller to trigger the AIoT device to acquire or report data according to the first method. The first method may include one or more of the first acquisition duration, the first acquisition cycle, and the reporting conditions mentioned above. Optionally, the second indication information may also include a data acquisition stop condition, such as a first cycle number or a first time period, and / or a first duration number or a second time period, etc., for the AIoT controller to instruct the AIoT device to stop data acquisition. Then, the AIoT controller can trigger the AIoT device to acquire or report first data according to the first method through the reader. Afterwards, the AIoT device acquires data after receiving the downlink command and the first indication information, and replies to the AF in response to the downlink command, and replies to the AIoT controller in response to the first indication information or the downlink command. The reply message may include data content (temperature, water level, humidity, pressure, smoke concentration, gas concentration, vibration, traffic flow, AIoT device status information (usage status: number of uses, years of use, usage records, etc.)), the identification information of the AIoT device, etc. After receiving the first data, the AIoT controller can directly report it to the AF (Automatic Feedback Array). Alternatively, it can determine whether there is second data in the first data that meets the reporting conditions. If there is, the second data is reported; otherwise, no data is reported. Optionally, if there is no second data, the AIoT controller can report a third indication to the AF. If the second data exists, or if the second indication does not carry reporting conditions and the first data exists, the AIoT controller can also report a fourth indication to the AF, so that the AF can read the data after receiving the fourth indication.

[0234] In other implementations, corresponding to the repeated triggering stage 2, for AIoT devices with corresponding capabilities, such as timing / counting capabilities and the ability to determine reporting conditions, the second indication information can be used to instruct the AIoT device to acquire and report data according to the second method. The second method may include one or more of the aforementioned second acquisition duration, second acquisition cycle, and reporting conditions. Optionally, the second indication information may also include a data acquisition stop condition, such as a second cycle number or a third time period, and / or a second duration number or a fourth time period, etc., used to allow the AIoT device to automatically stop data acquisition after the AIoT controller instructs the AIoT device to start data acquisition or reporting. Then, the AIoT controller can send a first indication information carrying some or all of the parameters related to the second method to the AIoT device to trigger the second device to start data acquisition. Afterward, the second device acquires and reports data according to the second method. Subsequently, after receiving the downlink command and the first indication information, the AIoT device acquires the third data and replies to the AF in response to the downlink command, and to the AIoT controller in response to the first indication information or the downlink command. The reply message may include the third or fourth indication information, data content (temperature, water level, humidity, pressure, smoke concentration, gas concentration, vibration, traffic flow, AIoT device status information (usage status: number of uses, years of use, usage records, etc.)), and the AIoT device's identifier. The third data can be the raw data acquired by the AIoT device or data filtered from the acquired raw data based on reporting conditions.

[0235] In the repeated triggering phase 1, when the AIoT device lacks the management capabilities of the first method, such as timing / counting capabilities or the ability to determine reporting conditions, the AIoT controller can, according to the first method, send a downlink command (DL command) and / or a first indication information to the AIoT device via a reader to instruct the AIoT device to start data acquisition and reporting. The first indication information can be determined based on the second indication information. For scenarios triggered according to the first acquisition cycle or the first acquisition duration, and without configured reporting conditions, the AIoT controller can directly report the first data received from the AIoT device, or send a fourth indication information to the AF, waiting for the AF to read or instruct it to discard the data. For scenarios with configured reporting conditions, after receiving the first data reported by the AIoT device, the AIoT controller determines whether there is second data in the first data that meets the reporting conditions. If not, the AIoT controller can choose not to report the data and can also report the generated third indication information to the AF. If it exists, the AIoT controller can report the second data that meets the reporting conditions to the AF, or report the generated fourth indication information to the AF.

[0236] In the repeated triggering phase 2, when the AIoT device possesses the management capability of the second method, the AIoT controller can send a downlink command (DL command) and a first indication information to the AIoT device via a reader. The first indication information can be determined based on the second indication information. Accordingly, the AIoT device independently controls data acquisition and reporting according to the first method. For scenarios triggered according to the second acquisition cycle or the second acquisition duration, and without configured reporting conditions, the AIoT device can directly report the acquired third data to the AIoT controller or AF, or send a fourth indication information to the AIoT controller or AF, waiting for the AF to read or instruct it to discard. For scenarios with configured reporting conditions, the AIoT device can determine whether there is data in the acquired raw data that meets the reporting conditions. If not, the AIoT device can choose not to report data and can also report the generated third indication information to the AIoT controller or AF. If it does exist, the AIoT device can report the third data that meets the reporting conditions to the AIoT controller, or the AIoT device can also report the generated fourth indication information to the AF via the reader and the AIoT controller.

[0237] For example, Figure 5 is an example diagram of the AIoT controller triggering a data acquisition method according to a first acquisition cycle provided in an embodiment of this application. As shown in Figure 5, the AIoT controller can periodically trigger the AIoT device to acquire data and report it through the reader according to the first acquisition cycle.

[0238] For example, Figure 6 is an example diagram of the AIoT controller triggering a data acquisition method according to a first acquisition duration provided in an embodiment of this application. As shown in Figure 6, the AIoT controller can trigger the AIoT device to collect data and report it once or multiple times through the reader according to the first acquisition duration.

[0239] During the initial triggering phase and the repeated triggering phase described above, the AIoT device can complete the triggering and reporting of data acquisition through multiple interactions with the reader. The following explanation uses three example interaction diagrams between the AIoT device and the reader, shown in Figures 7-9, to illustrate this.

[0240] As shown in Figure 7, after receiving the downlink signaling (including AC-D request information) and the first indication information from the AIoT controller, the reader can send an initial message to the AIoT device. After receiving the initial message, the AIoT device replies with a random number ID to the reader. After receiving the random number ID, the reader sends a second message (Msg2) to the AIoT device. After receiving the second message, the AIoT device replies with its own device ID to the reader. After receiving the device ID, the reader sends AC-D request information (including the first indication information) to the AIoT device. After receiving the AC-D request information, the AIoT device obtains the first data according to the first indication information. After obtaining the data, it sends D-AC information (including the first data) to the reader. After receiving the D-AC information, the reader forwards it to the AIoT controller, thus completing one data acquisition and reporting process.

[0241] As shown in Figure 8, the second message and the AC-D request information can be merged into one message to reduce the number of signaling interactions between the AIoT device and the reader, thereby improving efficiency.

[0242] Similarly, as shown in Figure 9, AC-D request information can also be carried in the initial message for transmission to reduce the number of signaling interactions between AIoT devices and readers, thereby improving efficiency.

[0243] Similarly, as shown in Figure 9, the D-AC response information (including the first data) and the ID of the AIoT device can be transmitted in a single message to reduce the number of data interactions between the AIoT device and the reader, thereby improving efficiency.

[0244] It should be noted that the AIoT controller and AIoT devices with reporting condition judgment capabilities can determine whether the acquired data meets the reporting conditions. When the reporting conditions are met, the AIoT device can report the data or fourth indication information that meets the reporting conditions to the AIoT controller or AF; or when the reporting conditions are not met, the AIoT device can report the third indication information to the AIoT controller or AF. Similarly, when the reporting conditions are met, the AIoT controller can report the data or fourth indication information that meets the reporting conditions to the AF; or when the reporting conditions are not met, the AIoT controller can report the third indication information to the AF.

[0245] For example, Figure 10 is an example diagram of the AIoT device determining the reporting conditions according to an embodiment of this application, and Figure 11 is another example diagram of the AIoT controller determining the reporting conditions according to an embodiment of this application.

[0246] As shown in Figure 10, when an AIoT device has the ability to determine reporting conditions, it can determine whether there is data in the acquired third data that meets the reporting conditions. If not, the AIoT device sends a third indication message to the AIoT controller through the reader, and the AIoT controller forwards the message directly to the AF after receiving it. If the data exists, the AIoT device reports the third data that meets the reporting conditions to the AIoT controller, and the AIoT controller forwards the data to the AF after receiving it.

[0247] As shown in Figure 11, when the AIoT device lacks the ability to determine the reporting conditions, it can report the collected raw data (first data) to the AIoT controller. The AIoT controller then determines whether there is second data in the first data that meets the reporting conditions. If not, the AIoT controller sends a third indication message to the AF; if it does, the AIoT controller filters out the second data that meets the reporting conditions from the first data and reports it to the AF.

[0248] Figure 12 is another example diagram of the data acquisition method shown in Figure 3A or Figure 3B. One difference between Figure 12 and Figure 4 is that the trigger or initiator of data acquisition in repeated triggering phases 1 and 2 is changed from the AIoT controller to the reader. In other words, the data acquisition or reporting functions performed by the AIoT controller in Figure 4 are performed by the reader in the scenario shown in Figure 12.

[0249] For example, referring to Figures 5 and 13, the trigger or initiator of data acquisition according to the data acquisition cycle (such as the first acquisition cycle and the second acquisition cycle) changes from the AIoT controller to the reader. Referring to Figures 6 and 14, the trigger or initiator of data acquisition according to the data acquisition duration (such as the first acquisition duration and the second acquisition duration) changes from the AIoT controller to the reader. Referring to Figures 11 and 19, and Figures 10 and 18, the trigger or initiator of data acquisition according to the reporting conditions changes from the AIoT controller to the reader, and the executor of determining whether there is a second data that meets the reporting conditions in the first data reported by the AIoT device changes from the AIoT controller to the reader.

[0250] Another difference between Figure 12 and Figure 4 is that the interaction process between the AIoT device and the reader is different. Figures 15-17 are three example diagrams of the interaction between the AIoT device and the reader when data acquisition is initiated by the reader, as provided in the embodiments of this application.

[0251] Compared to Figure 7, in Figure 15, the reader does not need to receive AC-D request information from the AIoT controller, nor does it need to reply with D-AC response information to the AIoT controller. Correspondingly, the AIoT device does not need to collect data based on the AC-D request information, nor generate and report D-AC response information. In other words, in Figure 15, the first indication information is not part of the AC-D request information, and the first data reported by the AIoT device can be reported to the reader as part of the reader's response information.

[0252] Optionally, as shown in Figure 16, the second message and the first indication information can be combined into a single message. Similarly, as shown in Figure 15, the first indication information can also be carried in the initial message for transmission, thereby reducing the number of signaling interactions between the AIoT device and the reader and improving efficiency.

[0253] Similarly, as shown in Figures 16 and 17, the reader's response information (including the first data) and the AIoT device's identifier and AF response information can be transmitted in a single message to reduce the number of data interactions between the AIoT device and the reader, thereby improving efficiency.

[0254] For the specific implementation of other content in the example shown in Figure 12, please refer to the relevant content of the embodiment shown in Figure 4, which will not be repeated here.

[0255] It should be noted that readers and AIoT devices with reporting condition judgment capabilities can determine whether the acquired data meets the reporting conditions. When the reporting conditions are met, the AIoT device can report the data or fourth indication information that meets the conditions to the reader or AF; or when the reporting conditions are not met, the AIoT device can report the third indication information to the reader or AF. Similarly, when the reporting conditions are met, the reader can report the data or fourth indication information that meets the reporting conditions to the AF; or when the reporting conditions are not met, the reader can report the third indication information to the AF.

[0256] It should be noted that, in addition to reporting data or third and fourth indication information during the data acquisition process, other processes can be reused for reporting. For example, when the AIoT device has already acquired data, but because higher-level network devices or application-layer devices, such as the AF, have not issued a read command, and the AIoT device's data cache has exceeded the cache threshold, or no read command has been received for a period of time after data acquisition stopped, the AIoT device can reuse other processes, such as the random access process, to report the fourth indication information to the reader, AIoT controller, or AF.

[0257] For example, Figures 20 and 21 are two example diagrams of AIoT devices reporting the fourth indication information in the random access procedure according to embodiments of this application. As shown in Figures 20 and 21, the fourth indication information and the identifier of the AIoT device can be carried in the same message of the random access procedure for reporting, so as to reduce the number of interactions between the AIoT device and the reader and improve efficiency.

[0258] Optionally, after receiving the fourth instruction information, the reader may choose to perform one of the following processing:

[0259] The reader allocates appropriate resources to AIoT devices to complete the acquisition and reporting of data;

[0260] The reader does not need to allocate resources. Instead, it forwards the fourth instruction information to the AIoT controller or AF, which then determines whether the collected data needs to be reported. If so, the reader can be instructed to allocate resources to the AIoT device and complete the data reporting step by step. If not, the AIoT device can discard the collected data, with later collected data overwriting earlier collected data.

[0261] The reader determines for itself whether AIoT data reporting is necessary. If so, it allocates resources to complete the data reporting; otherwise, it can instruct the AIoT device to discard the collected data.

[0262] It should be noted that in this example, after the AIoT device receives the data acquisition command and executes the data acquisition, it does not receive a data acquisition instruction from the reader, AIoT controller, or AF. Therefore, the AIoT device sends a fourth indication message to indicate that the data acquisition has been completed. Furthermore, it can report the process identifier and the storage duration of the third data. The process identifier indicates which data process the data belongs to, and the storage duration of the third data indicates how long the third data can still be stored, instructing the reader, AIoT controller, or AF to read the data as soon as possible.

[0263] It should be noted that Figures 20 and 21 illustrate the interaction process between the AIoT device and the reader using examples. It is easy to understand that if the trigger or initiator of data acquisition is the AIoT controller, the reader can forward the received fourth instruction information to the AIoT controller, which then allocates resources based on the fourth instruction information to complete operations such as data acquisition and reporting.

[0264] In some implementations, AIoT devices can also report their own capability information to the reader or AIoT controller, such as the AIoT device's data acquisition capabilities (e.g., data cache size, amount of data that can be acquired, or maximum data acquisition duration), counting / timing capabilities, or reporting condition judgment capabilities. The reported capability information can be proactively reported by the AIoT device, or it can be reported based on requests from higher-level devices or application-level devices, such as the reader, AIoT controller, or AF. This application's embodiments do not impose such limitations.

[0265] Once the higher-level device receives the capability information of the AIoT device, it can customize data acquisition parameters for the AIoT device based on the capability information. These data acquisition parameters can be reflected in the second instruction information issued by the AF and / or in the first instruction information issued by the reader or AIoT controller.

[0266] Furthermore, after the AIoT devices report their capability information, the AF and / or AIoT controller and / or reader can group the AIoT devices according to their capabilities (AIoT devices in the same group have the same or similar capabilities), and issue data acquisition parameters matching the capabilities of each AIoT device group to different AIoT device groups. For example, AIoT device groups with higher capabilities can be instructed to undertake more work, such as instructing AIoT device groups with reporting condition judgment capabilities to filter the acquired data according to the reporting conditions, and report the data that meets the reporting conditions to the reader or AIoT controller, and report a third indication information (indication information for not triggering the reporting conditions) when the reporting conditions are not met. Another example is that for AIoT device groups with counting / timing capabilities, they can be instructed to report the timestamp of the acquired data.

[0267] The data acquisition method provided by the embodiments of this application has been described in detail above with reference to Figures 3A-21. The data acquisition apparatus used to perform the data acquisition method provided by the embodiments of this application is described in detail below with reference to Figures 22 and 23.

[0268] This invention provides a data acquisition apparatus. The apparatus includes units or modules for performing the first device function in the data acquisition method provided in the above-described method embodiments.

[0269] In one possible design, the data acquisition device can be the first device described in the above method embodiments, or a chip (system) or other component or assembly that can be disposed in the single device.

[0270] It should be understood that the data acquisition device may include modules, units, or means corresponding to the data acquisition method described in the above method embodiments. These modules, units, or means may be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units for performing the functions involved in the above data acquisition method.

[0271] For example, FIG22 is a schematic diagram of the structure of a data acquisition device provided in an embodiment of this application. As shown in FIG22, the data acquisition device 2200 includes a processing module 2201 and a transceiver module 2202. For ease of explanation, FIG22 only shows the main components of the data acquisition device.

[0272] In some embodiments, the data acquisition device 2200 may be adapted to the communication system shown in FIG2 to perform the function of the first device in the data acquisition method shown in FIG3A.

[0273] The device 2200 is applicable to a first device, which may be a reader or an environmental IoT controller. The device 2200 includes a processing module 2201 and a transceiver module 2202.

[0274] The processing module 2201 is used to send first instruction information according to a first method. The first instruction information is used to instruct the second device to acquire or report first data. The first method includes one or more of the following: a first acquisition period or a first acquisition duration.

[0275] The transceiver module 2202 is used to receive first data from the second device.

[0276] In some implementations, the transceiver module 2202 is also used to receive second indication information from a third device, the second indication information including a first acquisition cycle;

[0277] The processing module 2201 is also used to send first instruction information to the second device according to the first acquisition cycle.

[0278] Optionally, the second indication information may also include one or more of the following: a first number of cycles, a first time period, or a third stop indication, wherein the first number of cycles is the number of first acquisition cycles, the first time period is the time period to which the first acquisition cycle applies, and the third stop indication is used to indicate that data acquisition should be stopped.

[0279] Furthermore, the transceiver module 2202 is also used to send a first stop instruction to the second device. The first stop instruction is used to instruct the second device to stop data acquisition when the data acquisition time reaches a first number of cycles or exceeds a first time period.

[0280] In some implementations, the transceiver module 2202 is further configured to receive second indication information from a third device, the second indication information including a first acquisition duration; the first device sends the first indication information to the third device according to the first acquisition duration.

[0281] Optionally, the second indication information may further include one or more of the following: a first duration, a second time period, or a fourth stop indication; wherein the first duration is the number of the first acquisition duration, the second time period is the time period to which the first acquisition duration applies, and the fourth stop indication is used to indicate that data acquisition should be stopped.

[0282] Furthermore, the transceiver module 2202 is also used to send a second stop instruction to the second device. The second stop instruction is used to instruct the second device to stop data acquisition when the data acquisition time reaches a first duration or exceeds a second time period.

[0283] In some implementations, the transceiver module 2202 is also used to send first data or fourth indication information to a third device, wherein the fourth indication information is used to indicate that the second device has obtained the first data.

[0284] In some implementations, the first method further includes: reporting conditions; the transceiver module 2202 is also used to receive second indication information from the third device, the second indication information including reporting conditions; the transceiver module 2202 is also used to send second data or fourth indication information to the third device, the fourth indication information being used to indicate that the second device has obtained the second data, the second data being the data in the first data that meets the reporting conditions.

[0285] Optionally, the fourth instruction information includes one or more of the following: the requested amount of resources or data, the data type, or the identifier of the second device, so that the third device can read the first data or the second data.

[0286] In some implementations, the first method further includes: reporting conditions; the transceiver module 2202 is also configured to receive second indication information from the third device, the second indication information including reporting conditions; the transceiver module 2202 is also configured to send third indication information to the third device, the third indication information indicating that an event that meets the reporting conditions has not occurred.

[0287] The data acquisition device 2200 may be an AIoT controller, such as an AMF or UPF, or a chip (system) or other component or assembly that can be set in the AIoT controller. Alternatively, the data acquisition device 2200 may be a reader, such as a base station (BS) or user equipment (UE), or a chip (system) or other component or assembly that can be set in the reader. This application does not limit the scope of the application.

[0288] In other embodiments, the data acquisition device 2100 may be adapted to the communication system shown in FIG2 to perform the function of the second device in the data acquisition method shown in FIG3B.

[0289] The transceiver module 2202 is used to receive first indication information from the first device. The first indication information is used to trigger the device 2200 to acquire or report third data. The first indication information includes one or more of the following: second acquisition period, second acquisition duration, or reporting conditions.

[0290] The processing module 2201 is used to send third data to the first device in accordance with the second method. The second method includes one or more of the following: a second acquisition period, a second acquisition duration, or a reporting condition. The third data is the data of the second device acquired by the second device in accordance with the second method.

[0291] In some implementations, the second method further includes one or more of the following: a second number of cycles or a third time period, and the first indication information further includes one or more of the following: a second number of cycles or a third time period; wherein, the second number of cycles is the number of second acquisition cycles, and the third time period is the time period to which the second acquisition cycle applies.

[0292] Optionally, the processing module 2201 is also used to stop data acquisition when the data acquisition time reaches the second cycle number or exceeds the third time period.

[0293] In some implementations, the second method further includes one or more of the following: a second duration or a fourth time period, and the first indication information further includes one or more of the following: a second duration or a fourth time period; wherein, the second duration is the number of second acquisition durations, and the fourth time period is the time period to which the second acquisition duration applies.

[0294] Optionally, the processing module 2201 is also used to stop data acquisition when the data acquisition time reaches the second duration or exceeds the fourth time period.

[0295] In some implementations, the transceiver module 2202 is also used to send a fourth indication message to the first device, the fourth indication message being used to indicate that the second device has acquired the third data.

[0296] Optionally, the fourth indication information includes one or more of the following: the number of resources or data volume requested, the data type, the process identifier, the remaining storage time or the identifier of the second device, wherein the process identifier is used to indicate the process of obtaining the third data, and the remaining storage time is used to indicate the duration for which the third data can be stored.

[0297] In some implementations, the first indication information further includes reporting conditions, and the third data is the data obtained by the second device when the reporting conditions are met, or the third data is the data in the original data obtained by the second device that meets the reporting conditions.

[0298] In some implementations, the first indication information also includes reporting conditions; the transceiver module 2202 is also used to send a third indication information to the first device, the third indication information indicating that no event has occurred that meets the reporting conditions.

[0299] In some implementations, the transceiver module 2202 is further configured to send capability information of the device 2200 to the first device, and the capability information of the second device is used to determine the first instruction information.

[0300] Optionally, the capability information of the second device includes one or more of the following: the data acquisition capability, counting / timing capability, or the ability to determine reporting conditions of the second device.

[0301] In some implementations, the first device may be an environmental IoT controller, the first instruction information and AC-D request information are carried in an initial message or a second message, and the third data includes the identifier of the device 2200, which is carried in the same message as the D-AC response information.

[0302] In some implementations, the first device may be a reader, the first indication information is carried in an initial message or a second message, and the third data includes the identifier of the second device. The identifier of the second device, the reader's reply information, and the AF reply information are carried in the same message.

[0303] The data acquisition device 2200 can be an AIoT device, such as a smart water meter, smart electricity meter, smart tag, etc., or it can be a chip (system) or other component or assembly that can be set in an AIoT device. This application does not limit this.

[0304] It should be noted that the transceiver module 2202 described above is used to implement the transceiver function. Further, the transceiver module 2202 may include a receiving module and a sending module. The sending module and receiving module are respectively used to implement the sending and receiving functions of the data acquisition device 2200.

[0305] Optionally, the data acquisition device 2200 may further include a storage module storing programs or instructions. When the processing module 2201 executes the program or instructions, the data acquisition device 2200 can perform the functions of the first device in the data acquisition method provided in the above method embodiments.

[0306] Furthermore, the technical effects of the data acquisition device 2200 can be referred to the technical effects of the data acquisition method provided in the above method embodiments, and will not be repeated here.

[0307] For example, FIG23 is a schematic diagram of another data acquisition device provided in an embodiment of this application. This data acquisition device can be the first device or the second device described above, or it can be a chip (system) or other component or assembly that can be disposed in the first device or the second device. As shown in FIG23, the data acquisition device 2300 may include a processor 2301. Optionally, the data acquisition device 2300 may further include a memory 2302 and / or a transceiver 2303. The processor 2301 is coupled to the memory 2302 and the transceiver 2303, for example, they can be connected via a communication bus.

[0308] The following section, with reference to Figure 23, provides a detailed description of each component of the data acquisition device 2300:

[0309] The processor 2301 is the control center of the data acquisition device 2300. It can be a single processor or a collective term for multiple processing elements. For example, the processor 2301 can be one or more central processing units (CPUs), application-specific integrated circuits (ASICs), or one or more integrated circuits configured to implement the embodiments of this application, such as one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs).

[0310] Optionally, the processor 2301 can perform various functions of the data acquisition device 2300 by running or executing software programs stored in the memory 2302 and calling data stored in the memory 2302.

[0311] In a specific implementation, as one example, processor 2301 may include one or more CPUs, such as CPU0 and CPU1 shown in FIG23.

[0312] In a specific implementation, as one embodiment, the data acquisition device 2300 may also include multiple processors, such as processors 2301 and 2304 shown in FIG. 23. Each of these processors may be a single-core processor (single-CPU) or a multi-core processor (multi-CPU). Here, a processor may refer to one or more devices, circuits, and / or processing cores used to process data (e.g., computer program instructions).

[0313] The memory 2302 is used to store the software program that executes the solution of this application, and is controlled by the processor 2301 to execute it. The specific implementation method can be referred to the above method embodiment, and will not be repeated here.

[0314] Optionally, the memory 2302 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. The memory 2302 may be integrated with the processor 2301 or may exist independently and be coupled to the processor 2301 through the interface circuit of the data acquisition device 2300 (not shown in FIG. 23). This application embodiment does not specifically limit this.

[0315] Transceiver 2303 is used for communication with other devices or equipment.

[0316] Optionally, transceiver 2303 may include a receiver and a transmitter (not shown separately in Figure 23). The receiver is used to implement the receiving function, and the transmitter is used to implement the transmitting function.

[0317] Optionally, the transceiver 2303 can be integrated with the processor 2301 or exist independently and be coupled to the processor 2301 through the interface circuit of the data acquisition device 2300 (not shown in Figure 23). This application embodiment does not specifically limit this.

[0318] It should be noted that the structure of the data acquisition device 2300 shown in Figure 23 does not constitute a limitation on the data acquisition device. The actual data acquisition device may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0319] Furthermore, the technical effects of the data acquisition device 2300 can be referred to the technical effects of the data acquisition method described in the above method embodiments, and will not be repeated here.

[0320] This application provides a communication system. The communication system includes a single device and a second device. Optionally, the communication system may further include a third device.

[0321] It should be understood that the processor in the embodiments of this application can be a central processing unit (CPU), or it can be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor.

[0322] It should also be understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can 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. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of random access memory (RAM) are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate synchronous DRAM (DDR SDRAM), enhanced synchronous DRAM (ESDRAM), synchronous linked DRAM (SLDRAM), and direct rambus RAM (DR RAM).

[0323] The above embodiments can be implemented, in whole or in part, by software, hardware (such as circuits), firmware, or any other combination thereof. When implemented using software, the above embodiments can be implemented, in whole or in part, in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more sets of available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. A semiconductor medium can be a solid-state drive.

[0324] It should be understood that the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. A and B can be singular or plural. Additionally, the character " / " in this article generally indicates an "or" relationship between the preceding and following related objects, but it can also represent an "and / or" relationship. Please refer to the context for a more accurate understanding.

[0325] In this application, "at least one" means one or more, and "more than one" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0326] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0327] Those skilled in the art will 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, or a combination of computer software and electronic hardware. 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.

[0328] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0329] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0330] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0331] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0332] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0333] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A data acquisition method, characterized in that, The method, applicable to a first device, which is a reader or an environmental IoT controller, includes: The first device sends a first instruction information according to a first method. The first instruction information is used to instruct the second device to acquire or report first data. The first method includes one or more of the following: a first acquisition period or a first acquisition duration. The first device receives the first data from the second device.

2. The data acquisition method according to claim 1, characterized in that, The first device sends a first instruction message to the second device in a first manner, including: The first device receives second indication information from the third device, the second indication information including the first acquisition period; The first device sends the first indication information to the third device according to the first acquisition cycle.

3. The data acquisition method according to claim 2, characterized in that, The second indication information also includes one or more of the following: a first number of cycles, a first time period, or a third stop indication, wherein the first number of cycles is the number of the first acquisition cycles, the first time period is the time period to which the first acquisition cycle applies, and the third stop indication is used to indicate that data acquisition should be stopped.

4. The data acquisition method according to claim 3, characterized in that, Also includes: The first device sends a first stop instruction to the second device. The first stop instruction is used to instruct the second device to stop data acquisition when the data acquisition time reaches the first number of cycles or exceeds the first time period.

5. The data acquisition method according to claim 1, characterized in that, The first device sends a first instruction message to the second device in a first manner, including: The first device receives a second indication information from the third device, the second indication information including the first acquisition duration; The first device sends the first instruction information to the third device according to the first acquisition duration.

6. The data acquisition method according to claim 5, characterized in that, The second indication information also includes one or more of the following: a first duration, a second time period, or a fourth stop indication; Wherein, the first duration number is the number of the first acquisition durations, the second time period is the time period to which the first acquisition durations apply, and the fourth stop indication is used to indicate the cessation of data acquisition.

7. The data acquisition method according to claim 6, characterized in that, Also includes: The first device sends a second stop instruction to the second device. The second stop instruction is used to instruct the second device to stop data acquisition when the data acquisition time reaches the first duration or exceeds the second time period.

8. The data acquisition method according to any one of claims 2-7, characterized in that, Also includes: The first device sends the first data or the fourth indication information to the third device, wherein the fourth indication information is used to indicate that the second device has obtained the first data.

9. The data acquisition method according to claim 1, characterized in that, The method further includes: The first device receives a second indication from the third device, the second indication including reporting conditions; The first device sends second data or fourth indication information to the third device. The fourth indication information is used to indicate that the second device has obtained the second data, which is the data in the first data that meets the reporting conditions.

10. The data acquisition method according to claim 8 or 9, characterized in that, The fourth indication information includes one or more of the following: the requested amount of resources or data, the data type, or the identifier of the second device.

11. The data acquisition method according to claim 1, characterized in that, The method further includes: The first device receives second indication information from the third device, the second indication information including the reporting conditions; The first device sends a third indication message to the third device, the third indication message indicating that no event has occurred that meets the reporting conditions.

12. A data acquisition method, characterized in that, Applicable to a second device, which is an environmental IoT device, the method includes: The second device receives a first indication information from the first device. The first indication information is used to trigger the second device to acquire or report third data. The first indication information includes one or more of the following: a second acquisition period, a second acquisition duration, or a reporting condition. The second device sends the third data to the first device in a second manner, the second manner including one or more of the following: the second acquisition period, the second acquisition duration, or the reporting conditions, and the third data is the data of the second device acquired by the second device in accordance with the second manner.

13. The data acquisition method according to claim 12, characterized in that, The second method further includes one or more of the following: a second number of cycles, or a third time period; the first indication information further includes one or more of the following: the second number of cycles, or the third time period. Wherein, the second cycle number is the number of the second acquisition cycles, and the third time period is the time period to which the second acquisition cycle applies.

14. The data acquisition method according to claim 13, characterized in that, Also includes: When the data acquisition time reaches the second cycle number or exceeds the third time period, the second device stops acquiring data.

15. The data acquisition method according to claim 12, characterized in that, The second method further includes one or more of the following: a second duration or a fourth time period, and the first indication information further includes one or more of the following: the second duration or the fourth time period; Wherein, the second duration number is the number of the second acquisition durations, and the fourth time period is the time period to which the second acquisition durations apply.

16. The data acquisition method according to claim 15, characterized in that, Also includes: When the data acquisition time reaches the second duration or exceeds the fourth time period, the second device stops acquiring data.

17. The data acquisition method according to any one of claims 12-16, characterized in that, Also includes: The second device sends a fourth indication message to the first device, the fourth indication message being used to indicate that the second device has acquired the third data.

18. The data acquisition method according to claim 17, characterized in that, The third data is the data obtained by the second device when the reporting conditions are met.

19. The data acquisition method according to claim 17 or 18, characterized in that, The fourth indication information includes one or more of the following: the number of resources or data volume requested, the data type, the process identifier, the remaining storage time, or the identifier of the second device. The process identifier is used to indicate the process of obtaining the third data, and the remaining storage time is used to indicate the duration for which the third data can be stored.

20. The data acquisition method according to any one of claims 12-16, characterized in that, The first indication information also includes the reporting conditions; The method further includes: The second device sends a third indication message to the first device, the third indication message indicating that no event has occurred that meets the reporting conditions.

21. The data acquisition method according to any one of claims 12-20, characterized in that, Also includes: The second device sends its capability information to the first device. The capability information of the second device includes one or more of the following: the second device's data acquisition capability, counting / timing capability, or the ability to determine reporting conditions.

22. The data acquisition method according to any one of claims 12-21, characterized in that, The first device is the environmental IoT controller, and the first indication information and AC-D request information are carried in the initial message or the second message.

23. The data acquisition method according to any one of claims 12-21, characterized in that, The first device is the environmental IoT controller, and the third data includes the identifier of the second device, which is carried in the same message as the D-AC response information.

24. The data acquisition method according to any one of claims 12-21, characterized in that, The first device is a reader, and the first indication information is carried in an initial message or a second message.

25. The data acquisition method according to any one of claims 12-21, characterized in that, The first device is a reader, and the third data includes the identifier of the second device. The identifier of the second device, the reader's reply information, and the AF reply information are carried in the same message.

26. A data acquisition method, characterized in that, include: The second device sends a fourth indication message to the first device, the fourth indication message being used to indicate that the second device has acquired the third data, the third data being the data acquired by the second device after receiving the data acquisition instruction from the first device; The fourth indication information includes one or more of the following: a first indication of obtaining the third data, the requested resource quantity or data volume, data type, process identifier, remaining storage time or the identifier of the second device, wherein the process identifier is used to indicate the process information for obtaining the third data, and the remaining storage time is used to indicate the duration for which the third data can be stored.

27. A data acquisition method, characterized in that, include: The first device receives a second instruction from the third device, the second instruction including reporting conditions; The first device receives first data from the second device; The first device sends second data or fourth indication information to the third device. The fourth indication information is used to indicate that the second device has obtained the second data, which is the data in the first data that meets the reporting conditions.

28. The data acquisition method according to claim 27, characterized in that, The fourth indication information includes one or more of the following: the requested amount of resources or data, the data type, or the identifier of the second device.

29. The data acquisition method according to claim 27 or 28, characterized in that, The method further includes: The first device sends a third indication message to the third device, the third indication message indicating that no event has occurred that meets the reporting conditions.

30. A data acquisition device, characterized in that, include: A processor coupled to a memory storing a program or instructions that, when executed by the processor, cause the device to perform the data acquisition method as described in any one of claims 1-29.

Images