Data acquisition method and communication apparatus

Abstract

A data acquisition method and a communication apparatus. A core network element and a reader / writer can send first information to an Internet of Things device by means of downlink signaling sent before the Internet of Things device registers with the core network element, so as to instruct the Internet of Things device to acquire sensing data, such that the Internet of Things device can start acquisition of the sensing data before registering with the core network element, helping to advance the time when the Internet of Things device reports the sensing data, thereby improving the efficiency of the core network element in acquiring sensing data of tags.

Description

Data collection method and communication device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on September 28, 2023, with application number 202311292266.3 and invention name “A Data Acquisition Method and Communication Device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communications, and more particularly, to a data acquisition method and a communication device. Background Art

[0003] Currently, the mainstream application scenarios for IoT (Internet of Things) devices (such as passive or semi-passive tags) include the following: 1) Logistics and warehousing: including inventory and tracking, and monitoring the transport environment and status of high-value goods (such as vaccines); and 2) Industrial manufacturing: including environmental and equipment status monitoring. With technological advancements and environmental protection requirements, the IoT is poised for even larger-scale deployment, with projections of covering hundreds of billions of devices in the future.

[0004] IoT devices can have sensing capabilities and collect sensor data through sensors. After registering with a network, the network can send a request to the device to obtain sensor data. The device, in response to the network's request, initiates sensor data collection and reports it to the network upon completion. However, this method is inefficient in obtaining sensor data from IoT devices.

[0005] Summary of the Invention

[0006] The present application provides a data acquisition method and a communication device to improve the efficiency of a network in acquiring sensor data of an Internet of Things device.

[0007] In a first aspect, a data collection method is provided. The method can be performed by an IoT device. Unless otherwise specified, "IoT device" can refer to the IoT device itself or a device that supports the IoT device in performing the function. Optionally, the IoT device can be a tag. The tag can be a passive tag, a semi-passive tag, or an active tag.

[0008] The method includes: a first Internet of Things device receives first information from a reader / writer, where the first information is used to instruct the first Internet of Things device to collect sensor data, and the first information is carried in downlink signaling sent before the first Internet of Things device is registered with a core network element; the first Internet of Things device collects first sensor data based on the first information; and the first Internet of Things device sends the first sensor data to the reader / writer.

[0009] It should be noted that before the first IoT device registers with the core network element, the first information may include: before the first IoT device sends a registration request message and during the first IoT device's registration with the core network element. In other words, the first information may be carried in downlink signaling before the registration request message or in downlink signaling during the first IoT device's registration with the core network element.

[0010] The downlink signaling preceding the registration request message includes at least one of the following: a first excitation signal, a first selection command, and downlink signaling during a first random access process. The first excitation signal is used to power the IoT device to be inventoried, the first selection command is used to select the IoT device to be inventoried, and the first IoT device is one of the IoT devices to be inventoried. The downlink signaling during the first IoT device's registration process with a core network element includes at least one of the following: a first registration message or downlink signaling during a first security authentication process. The first registration message indicates that the first IoT device has successfully registered with the core network element.

[0011] Based on the above method, the reader can send first information to the first IoT device via downlink signaling sent before the first IoT device registers with the core network element, instructing the first IoT device to collect sensor data. This allows the first IoT device to start collecting sensor data before registering with the core network element. Compared to starting sensor data collection based on a data read request message from the core network element after successful registration, starting sensor data collection before registering with the core network element helps advance the time when the first IoT device reports sensor data, thereby improving the efficiency of the core network element in acquiring sensor data from the tag.

[0012] Furthermore, when the reader carries the first information in the downlink signaling during the first excitation signal, the first selection command, or the first random access process, all IoT devices within the reader's range that are to be inventoried can pre-collect sensor data based on the first information. This allows each IoT device to report sensor data earlier, further improving the efficiency of core network elements in acquiring sensor data.

[0013] In combination with the first aspect, in some possible implementations, the downlink signaling in the random access process includes a query command and / or a confirmation command; and / or the first registration message is a registration response message or a registration acceptance message; and / or the downlink first signaling in the first security authentication process includes an authentication pass message and / or an authentication request message.

[0014] In combination with the first aspect or any implementation thereof, in some other possible implementations, the first information is carried in the first excitation signal, the first selection command, or the downlink signaling in the first random access process; the first sensing data is carried in the second registration message, the uplink signaling in the first security authentication process, or the uplink signaling related to service transmission, and the second registration message is used to request registration with the core network network element.

[0015] Compared to starting the collection of sensor data based on the data reading request message of the core network network element after successful registration, the first Internet of Things device collects sensor data based on the first excitation signal, the first selection command or the first information in the downlink signaling during the first random access process, which helps to advance the time for the first Internet of Things device to report the sensor data, thereby improving the efficiency of the core network network element in obtaining the sensor data of the tag.

[0016] In combination with the first aspect or any implementation thereof, in some other possible implementations, the first information is carried in the first registration message or the downlink signaling in the first security authentication process; the first sensing data is carried in the uplink signaling related to the service transmission.

[0017] Compared to starting the collection of sensor data based on the data reading request message of the core network network element after successful registration, the first Internet of Things device collects sensor data based on the first registration message or the first information in the downlink signaling during the first security authentication process, which helps to advance the time for the first Internet of Things device to report sensor data, thereby improving the efficiency of the core network network element in obtaining the sensor data of the tag.

[0018] In combination with the first aspect or any implementation manner thereof, in some other possible implementation manners, the method further includes: the first Internet of Things device receives second information from the reader / writer, and the second information is used to instruct the first Internet of Things device to report sensor data; the first Internet of Things device sends the first sensor data to the reader / writer, including: the first Internet of Things device sends the first sensor data to the reader / writer based on the second information; wherein, the first information is carried in the first excitation signal, the first selection command, the downlink signaling in the first random access process, or the downlink signaling in the first security authentication process, and the second information is carried in the first registration message.

[0019] Based on the above method, the first Internet of Things device can report the first sensor data based on the reporting indication information on the network side.

[0020] In combination with the first aspect or any implementation manner thereof, in some other possible implementation manners, after sending the first sensor data, the method further includes: the first Internet of Things device receives the first information from the reader / writer; the first Internet of Things device collects and caches second sensor data based on the first information; the first Internet of Things device receives second information, the second information is used to instruct the first Internet of Things device to report sensor data, the second information is carried in a second excitation signal, a second selection command, or a downlink signaling in a second random access process, the second excitation signal is used to power the Internet of Things device to be inventoryed, and the second selection command is used to select the Internet of Things device to be inventoryed; the first Internet of Things device sends the second sensor data to the reader / writer based on the second information, the second sensor data is carried in a third registration message, and the third registration message is used to request registration with the core network element; after sending the second sensor data, the first Internet of Things device receives the first information from the reader / writer.

[0021] Based on the above method, after sending the first sensor data, the first Internet of Things device can collect the second sensor data based on the first information received again. When the core network network element instructs the first Internet of Things device to report the sensor data again, the first Internet of Things device can directly report the second sensor data collected in advance, which helps to improve the efficiency of the core network network element in obtaining sensor data.

[0022] In combination with the first aspect or any implementation thereof, in some other possible implementations, the method further includes: the first Internet of Things device receives third information from the reader / writer, the third information is used to instruct the first Internet of Things device to send feedback information when the sensor data collection is not completed, and the feedback information is used to instruct to maintain the communication connection with the first Internet of Things device.

[0023] Based on the above method, before the collection of the first sensor data is completed, the communication connection between the first Internet of Things device and the network side is always maintained. Once the collection of the first sensor data is completed, the first Internet of Things device can report it to the core network network element in a timely manner, which helps to improve the efficiency of the core network network element in obtaining sensor data.

[0024] In combination with the first aspect or any implementation thereof, in some other possible implementations, the third information and the first information are carried in the same signaling; or, the first information is carried in the first excitation signal, the first selection command, the downlink signaling in the first random access process, or the downlink signaling in the first security authentication process, and the third information is carried in the first registration message.

[0025] In combination with the first aspect or any implementation manner thereof, in some other possible implementation manners, the third information is further used to indicate a period for sending the feedback information.

[0026] In combination with the first aspect or any implementation thereof, in some other possible implementations, the method further includes: before the collection of the first sensor data is completed, the first Internet of Things device sends one or more feedback information to the reader / writer.

[0027] In combination with the first aspect or any implementation thereof, in some other possible implementations, the first Internet of Things device completes the collection of the first sensor data after a first period of time; the first Internet of Things device sends the first sensor data to the reader / writer, including: the first Internet of Things device re-establishes a communication connection with the reader / writer, and sends the first sensor data to the reader / writer on the communication connection.

[0028] Based on the above method, the network side can maintain a communication connection with the first IoT device within a preset time period, which can avoid waiting for a long time for a certain IoT device to report sensor data, help other IoT devices to access the network in time, and help improve the efficiency of core network elements in obtaining sensor data.

[0029] In combination with the first aspect or any implementation thereof, in some other possible implementations, the method further includes: the first Internet of Things device receives fourth information from the reader / writer, and the fourth information is used to indicate the first duration.

[0030] In combination with the first aspect or any implementation thereof, in some other possible implementations, the fourth information and the first information are carried in the same signaling; or, the first information is carried in the first excitation signal, the first selection command, the downlink signaling in the first random access process, or the downlink signaling in the first security authentication process, and the fourth information is carried in the first registration message.

[0031] A second aspect provides a data collection method that can be performed by a core network element. Unless otherwise specified, "core network element" can refer to the core network element itself or a device that supports the core network element in implementing the function. A core network element is a network element responsible for IoT device management, such as a tag management function (TMF).

[0032] The method includes: a core network network element receives a data request message from an application function network element, where the data request message is used to request sensor data of an Internet of Things device to be inventoried, and the Internet of Things device to be inventoried includes a first Internet of Things device; the core network network element sends first information to a reader / writer based on the data request message, where the first information is used to instruct the first Internet of Things device to collect sensor data, and the first information is carried in downlink signaling sent before the first Internet of Things device is registered with the core network network element; the core network network element receives first sensor data of the first Internet of Things device from the reader / writer; and the core network network element sends the first sensor data to the application function network element.

[0033] For the description before the first IoT device registers with the core network element, reference may be made to the first aspect.

[0034] In a second aspect, downlink signaling preceding the registration request message includes a first inventory request message, where the inventory request message is used to request an inventory of the IoT device to be inventoried. Downlink signaling during the registration process of the first IoT device with the core network element includes at least one of the following: a first registration message, or downlink signaling during a first security authentication process, where the first registration message is used to indicate that the first IoT device has successfully registered with the core network element.

[0035] Based on the above method, the core network element can send first information to the reader / writer through downlink signaling sent before the first IoT device registers with the core network element, thereby instructing the first IoT device to collect sensor data, so that the first IoT device can start collecting sensor data before registering with the core network element. Compared to starting sensor data collection based on a data read request message from the core network element after successful registration, starting sensor data collection before registering with the core network element helps to advance the time when the first IoT device reports sensor data, thereby improving the efficiency of the core network element in acquiring sensor data from the tag.

[0036] Furthermore, when the core network element carries the first information in the first inventory request message, the reader can support the reader in carrying the first information in the downlink signaling during the first excitation signal, the first selection command, or the first random access process. This allows all IoT devices to be inventoried within the reader range to collect sensor data in advance based on the first information. This allows each IoT device to report sensor data earlier, further improving the efficiency of the core network element in acquiring sensor data.

[0037] In combination with the second aspect, in some possible implementations, the first registration message is a registration response message or a registration acceptance message; and / or, the downlink signaling in the first security authentication process includes an authentication pass message and / or an authentication request message.

[0038] In combination with the second aspect or any implementation thereof, in some other possible implementations, the first information is carried in the first inventory request message; the first sensor data is carried in the second registration message, the uplink signaling in the first security authentication process, or the uplink signaling related to service transmission, and the second registration message is used to request registration with the core network network element.

[0039] In combination with the second aspect or any implementation thereof, in some other possible implementations, the first information is carried in the first registration message or the downlink signaling in the first security authentication process; the first sensing data is carried in the uplink signaling related to the service transmission.

[0040] In combination with the second aspect or any implementation thereof, in some other possible implementations, the method further includes: the core network network element sends second information to the reader / writer, and the second information is used to instruct the first Internet of Things device to report sensor data; wherein, the first information is carried in the first inventory request message, and the second information is carried in the first registration message.

[0041] In combination with the second aspect or any implementation manner thereof, in some other possible implementation manners, the data request message includes periodic information, and the periodic information is used to indicate the period of inventorying the IoT device to be inventoried; the first information and the first sensor data are transmitted within the first period; the method also includes: within the second period, the core network network element sends the first information to the reader / writer through a second inventory request message or a fourth registration message, and the fourth registration message is used to indicate that the first IoT device has been successfully registered with the core network network element.

[0042] In combination with the second aspect or any implementation manner thereof, in some other possible implementation manners, the data request message includes period information, and the period information is used to indicate the period of inventorying the IoT device to be inventoried; the first information and the first sensor data are transmitted within the first period; the method also includes: after receiving the first sensor data, within the first period, the core network network element sends the first information to the reader / writer; within the second period, the core network network element sends second information to the reader / writer through a second inventory request message, and the second information is used to instruct the first IoT device to report sensor data; the core network network element receives the second sensor data of the first IoT device from the reader / writer, and the second sensor data is carried in a third registration message, and the third registration message is used to request registration with the core network network element; after receiving the second sensor data, the core network network element sends the first information to the reader / writer.

[0043] In combination with the second aspect or any implementation manner thereof, in some other possible implementation manners, the data request message includes a first data volume, and the first data volume is the data volume that triggers the core network network element to report the sensor data to the application function network element; the core network network element sends the first sensor data to the application function network element, including: when the sensor data cached in the core network network element reaches the first data volume, the core network network element sends the sensor data cached by the core network network element to the application function network element, and the sensor data cached by the core network network element includes the first sensor data.

[0044] In combination with the second aspect or any implementation thereof, in some other possible implementations, the data request message includes indication information, and the indication information is used to indicate the signaling carrying the first information; the core network network element sends the first information to the reader / writer according to the data request message, including: the core network network element sends the first information to the reader / writer in the signaling indicated by the indication information according to the data request message.

[0045] In combination with the second aspect or any implementation thereof, in some other possible implementations, the method further includes: the core network network element sends third information to the reader / writer, the third information is used to instruct the first Internet of Things device to send feedback information when the sensor data collection is not completed, and the feedback information is used to instruct to maintain the communication connection with the first Internet of Things device.

[0046] In combination with the second aspect or any implementation thereof, in some other possible implementations, the third information and the first information are carried in the same signaling; or, the first information is carried in the first inventory request message or the downlink signaling in the first security authentication process, and the third information is carried in the first registration message.

[0047] In combination with the second aspect or any implementation thereof, in some other possible implementations, the third information is further used to indicate a period for sending the feedback information.

[0048] In combination with the second aspect or any implementation thereof, in some other possible implementations, the method further includes: within a first time period, the core network network element does not receive the first sensor data from the reader / writer; after the first time period, the core network network element disconnects the communication connection for the first Internet of Things device and sends fifth information to the reader / writer, the fifth information being used to indicate the inventory of the next Internet of Things device; the core network network element receives the first sensor data of the first Internet of Things device from the reader / writer, including: the core network network element re-establishes a communication connection with the first Internet of Things device and receives the first sensor data on the communication connection.

[0049] In combination with the second aspect or any implementation thereof, in some other possible implementations, the method further includes: the core network element starts a first timer, and the timing duration of the first timer is the first duration.

[0050] In combination with the second aspect or any implementation thereof, in some other possible implementations, before the core network element sends the fifth information to the reader / writer, the method further includes: the core network element receives the sixth information from the reader / writer, and the sixth information is used to request an inventory of the next IoT device.

[0051] In combination with the second aspect or any implementation thereof, in some other possible implementations, the method further includes: the core network element sending fourth information to the reader / writer, where the fourth information is used to indicate the first duration.

[0052] In combination with the second aspect or any implementation thereof, in some other possible implementations, the fourth information and the first information are carried in the same signaling; or, the first information is carried in the first inventory request message or the downlink signaling in the first security authentication process, and the fourth information is carried in the first registration message.

[0053] The terms or features in the second aspect or its implementation that are the same as those in the first aspect or its implementation can refer to the first aspect or its implementation, and the technical effects of the second aspect or its implementation can refer to the technical effects in the first aspect or its implementation, and will not be repeated in the second aspect.

[0054] On the third aspect, a data collection method is provided, which can be executed by an application function network element. Unless otherwise specified, "application function network element" can refer to the application function network element itself, or it can refer to a device that can support the application function network element to implement this function.

[0055] The method includes: an application function network element determines a data request message, where the data request message is used to request sensor data of an Internet of Things device to be inventoried, and the data request message includes one or more of the following information: period information, cached data volume, or indication information, where the period information is used to indicate a period for inventorying the Internet of Things device to be inventoried, the cached data volume is a data volume that triggers a core network element to report sensor data to the application function network element, and the indication information is used to indicate signaling that carries first information, where the first information is used to instruct a first Internet of Things device to collect sensor data, and the first Internet of Things device belongs to the Internet of Things device to be inventoried; and the application function network element sends the data request message to the core network element.

[0056] Based on the above method, the application function network element can provide the designated core network element with at least one of the periodic information for inventory, the amount of data that triggers reporting of sensor data, or the signaling for sending the first information, which can make the inventory more flexible.

[0057] In conjunction with the third aspect, in some possible implementations, the signaling carrying the first information is downlink signaling sent before the first IoT device is registered with the core network element. For a detailed description, please refer to the second aspect.

[0058] Fourthly, a data collection method is provided. The method can be performed by a reader / writer. Unless otherwise specified, "reader / writer" can refer to the reader / writer itself or a device that supports the reader / writer to perform the function. The reader / writer can be integrated into access network equipment, relay equipment, terminal equipment, etc., or it can be a dedicated reader / writer, without limitation.

[0059] The method includes: a reader / writer receives first information from a core network element, where the first information is used to instruct a first Internet of Things device to collect sensor data; the reader / writer sends the first information to the first Internet of Things device; the reader / writer receives first sensor data from the first Internet of Things device; and the reader / writer sends the first sensor data to the core network element; wherein the first information is carried in downlink signaling sent before the first Internet of Things device registers with the core network element.

[0060] For the description before the first IoT device registers with the core network element, reference may be made to the first aspect.

[0061] The downlink signaling received by the reader before the registration request message can refer to the second aspect, and the downlink signaling sent by the reader before the registration request message can refer to the first aspect. The downlink signaling received by the reader during the registration process of the first IoT device with the core network element can refer to the second aspect, and the downlink signaling sent by the reader during the registration process of the first IoT device with the core network element can refer to the first aspect.

[0062] In combination with the fourth aspect, in some possible implementations, the downlink signaling in the random access process includes a query command and / or a confirmation command; the downlink first signaling in the first security authentication process includes an authentication pass message and / or an authentication request message.

[0063] In combination with the fourth aspect or any implementation thereof, in some other possible implementations, the first information received by the reader is carried in the first inventory request message; the first information sent by the reader is carried in the first excitation signal, the first selection command, or the downlink signaling in the first random access process; the first sensing data is carried in the second registration message, the uplink signaling in the first security authentication process, or the uplink signaling related to service transmission, and the second registration message is used to request registration with the core network network element.

[0064] In combination with the fourth aspect or any implementation thereof, in some other possible implementations, the first information is carried in the downlink signaling of the first registration message or the first security authentication process; the first sensing data is carried in the uplink signaling related to the service transmission.

[0065] In combination with the fourth aspect or any implementation manner thereof, in some other possible implementation manners, the method further includes: the reader / writer receives second information from the core network network element, the second information being used to instruct the first Internet of Things device to report sensor data; the reader / writer sends the second information to the first Internet of Things device; wherein, the first information received by the reader / writer is carried in the first inventory request message, the first information sent by the reader / writer is carried in the first excitation signal, the first selection command, the downlink signaling in the first random access process or the downlink signaling in the first security authentication process, and the second information is carried in the first registration message.

[0066] In combination with the fourth aspect or any implementation manner thereof, in some other possible implementation manners, after sending the first sensor data, the method further includes: the reader / writer receives the first information from the core network network element and sends the first information to the first Internet of Things device; the reader / writer receives second information from the core network network element, the second information is used to instruct the first Internet of Things device to report sensor data, and the second information is carried in a second inventory request message; the reader / writer sends the second information to the first Internet of Things device through a second excitation signal, a second selection command, or downlink signaling in a second random access process, the second excitation signal is used to power the Internet of Things device to be inventoried, and the second selection command is used to select the Internet of Things device to be inventoried; the reader / writer receives the third registration message from the first Internet of Things device, the third registration message is used to request registration with the core network network element, and the third registration message includes the second sensor data; the reader / writer sends the third registration message to the core network network element; after sending the third registration message, the reader / writer receives the first information from the core network network element and sends the first information to the first Internet of Things device.

[0067] In combination with the fourth aspect or any implementation thereof, in some other possible implementations, the method further includes: the reader / writer receives third information from the core network network element, the third information is used to instruct the first Internet of Things device to send feedback information when the sensor data collection is not completed, and the feedback information is used to instruct to maintain the communication connection with the first Internet of Things device; the reader / writer sends the third information to the first Internet of Things device.

[0068] In combination with the fourth aspect or any implementation manner thereof, in some other possible implementation manners, the third information and the first information are carried in the same signaling; or, the first information received by the reader is carried in the first inventory request message, the first information sent by the reader is carried in the first excitation signal, the first selection command, and the downlink signaling in the first random access process, and the third information is carried in the first registration message.

[0069] In combination with the fourth aspect or any implementation thereof, in some other possible implementations, the third information is further used to indicate a period for sending the feedback information.

[0070] In combination with the fourth aspect or any implementation thereof, in some other possible implementations, the method further includes: the reader / writer receives one or more feedback information from the first Internet of Things device, and sends the one or more feedback information to the core network network element.

[0071] In combination with the fourth aspect or any implementation manner thereof, in some other possible implementation manners, the method further includes: within a first time period, the reader / writer does not receive the first sensor data from the reader / writer; after the first time period, the reader / writer disconnects the communication connection with the first Internet of Things device, and receives fifth information from the core network network element, the fifth information being used to indicate the inventory of the next Internet of Things device; the reader / writer receives the first sensor data from the first Internet of Things device, including: the reader / writer re-establishes a communication connection with the first Internet of Things device, and receives the first sensor data on the communication connection.

[0072] In combination with the fourth aspect or any implementation thereof, in some other possible implementations, the method further includes: the core network network element starts a first timer, and the timing duration of the first timer is the first duration; before receiving the fifth information, the reader / writer sends sixth information to the core network network element, and the sixth information is used to request an inventory of the next IoT device.

[0073] In combination with the fourth aspect or any implementation thereof, in some other possible implementations, the method further includes: the reader / writer receives fourth information sent from the core network element, and the fourth information is used to indicate the first duration.

[0074] In combination with the fourth aspect or any implementation thereof, in some other possible implementations, the method further includes: the reader / writer sending the fourth information to the first Internet of Things device.

[0075] The terms or features in the fourth aspect or its implementation methods that are the same as those in the first aspect or its implementation methods can refer to the first aspect or its implementation methods, and the technical effects of the fourth aspect or its implementation methods can refer to the technical effects in the first aspect or its implementation methods, and will not be repeated in the fourth aspect.

[0076] In a fifth aspect, a communication device is provided, which is configured to execute the method provided by any of the above aspects or implementations thereof. Specifically, the device may include units and / or modules, such as a processing unit and / or a transceiver unit, configured to execute the method provided by any of the above aspects or implementations thereof.

[0077] In one implementation, the apparatus is an IoT device, a core network element, an application function element, or a reader / writer. When the apparatus is an IoT device, a core network element, an application function element, or a reader / writer, the transceiver unit may be a transceiver, an input / output interface, or a communication interface; and the processing unit may be at least one processor. Optionally, the transceiver is a transceiver circuit. Optionally, the input / output interface is an input / output circuit.

[0078] In another implementation, the device is a chip, chip system, or circuit used in an IoT device, a core network element, an application function element, or a reader / writer. When the device is a chip, chip system, or circuit used in an IoT device, a core network element, an application function element, or a reader / writer, the transceiver unit may be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip, chip system, or circuit; and the processing unit may be at least one processor, processing circuit, or logic circuit.

[0079] In a sixth aspect, a communication device is provided, which includes: a memory for storing programs; and at least one processor for executing computer programs or instructions stored in the memory to execute the method provided by any one of the above aspects or its implementation.

[0080] In one implementation, the device is an Internet of Things device, a core network element, an application function network element, or a reader / writer.

[0081] In another implementation, the device is a chip, chip system or circuit used in an Internet of Things device, a core network element, an application function network element or a reader / writer.

[0082] In a seventh aspect, a communication device is provided, comprising: at least one processor and a communication interface, wherein the at least one processor is configured to retrieve a computer program or instruction stored in a memory through the communication interface to execute the method provided by any one of the above aspects or implementations thereof. The communication interface may be implemented in hardware or software.

[0083] In one implementation, the device further includes the memory.

[0084] In an eighth aspect, a processor is provided for executing the methods provided in the above aspects.

[0085] For the operations such as sending and acquiring / receiving involved in the processor, unless otherwise specified, or if they do not conflict with their actual functions or internal logic in the relevant descriptions, they can be understood as operations such as processor output, reception, and input, or as sending and receiving operations performed by the radio frequency circuit and antenna. This application does not limit this.

[0086] In a ninth aspect, a computer-readable storage medium is provided, which stores a program code for execution by a device, wherein the program code includes a method for executing any one of the above aspects or its implementation.

[0087] In a tenth aspect, a computer program product comprising instructions is provided, which, when run on a computer, enables the computer to execute the method provided by any one of the above aspects or its implementation.

[0088] In an eleventh aspect, a chip is provided, comprising a processor and a communication interface, wherein the processor reads instructions stored in a memory through the communication interface and executes the method provided by any of the above aspects or implementations thereof. The communication interface may be implemented in hardware or software.

[0089] Optionally, as an implementation method, the chip also includes a memory, in which a computer program or instruction is stored, and the processor is used to execute the computer program or instruction stored in the memory. When the computer program or instruction is executed, the processor is used to execute the method provided by any of the above aspects or its implementation methods.

[0090] When the method provided in this application is executed by a chip, this application does not limit the number of chips that implement the method. For example, the method can be executed by one chip or by two or more chips. Furthermore, when the number of chips implementing the method of this application is two or more, the chip manufacturers are not limited and can be the same manufacturer or different manufacturers.

[0091] In the twelfth aspect, a communication system is provided, comprising at least one of the Internet of Things devices, core network elements, application function network elements or readers / writers described above.

[0092] In a thirteenth aspect, a computer program is provided, which, when executed on a computer, enables the method provided by any one of the above aspects or its implementation to be executed. BRIEF DESCRIPTION OF THE DRAWINGS

[0093] FIG1 is a schematic diagram of a network architecture to which an embodiment of the present application can be applied.

[0094] FIG2 is a schematic flow chart of tag sensor data collection and reading.

[0095] FIG3 is a schematic flow chart of a data collection method 300 provided in this application.

[0096] FIG4 is a schematic flow chart of a data collection method 400 provided in this application.

[0097] FIG5 is a schematic flow chart of a data collection method 500 provided in this application.

[0098] FIG6 is a schematic flow chart of a data collection method 600 provided in this application.

[0099] FIG7 is a schematic structural diagram of a device provided in an embodiment of the present application.

[0100] FIG8 is another schematic structural diagram of the device provided in an embodiment of the present application.

[0101] FIG9 is a schematic diagram of a chip system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0102] To facilitate understanding of the embodiments of the present application, the following explanations are made before introducing the embodiments of the present application.

[0103] "Indication" includes direct indication (also known as explicit indication) and implicit indication. Direct indication of information A refers to the inclusion of information A; implicit indication of information A refers to the indication of information A through the correspondence between information A and information B, as well as the direct indication of information B. The correspondence between information A and information B can be predefined, pre-stored, pre-burned, or pre-configured. Information C is used to determine information D, including situations where information D is determined solely based on information C or based on information C and other information. Furthermore, information C can also be used to determine information D indirectly, for example, when information D is determined based on information E, and information E is determined based on information C. "Network element A sends information A to network element B" can be understood as network element B being the destination of information A or an intermediate network element in the transmission path between the destination and the network element, and can include direct or indirect transmission of information to network element B. "Network element B receives information A from network element A" can be understood as network element A being the source of information A or an intermediate network element in the transmission path between the source and the network element, and can include direct or indirect receipt of information from network element A. Information may undergo necessary processing between the source and destination of information transmission, such as format changes, but the destination can still understand the valid information from the source. The various numerical numbers such as "first," "second," and so on are merely distinctions for ease of description and are not intended to limit the scope of the embodiments of this application, for example, to distinguish between different messages or different information. "Pre-definition" can be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in the device, and this application does not limit its specific implementation. The "protocol" involved may refer to a standard protocol in the communications field, such as the Long Term Evolution (LTE) protocol, the New Radio (NR) protocol, and related protocols used in future communications systems, but this application does not limit this. Words such as "exemplary," "for example," "exemplarily," and "as (another) example" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as an "example" in this application should not be construed as preferred or advantageous over other embodiments or designs. The terms "including," "comprising," "having," and their variations all mean "including but not limited to," unless otherwise specifically emphasized. "At least one" means one or more, and "a plurality" means two or more. "At most one" means one or zero. "And / or" describes the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items.For example, at least one of a, b, and c can represent: a, or b, or c, or a and b, or a and c, or b and c, or a, b, and c. A, b, and c can each be single or multiple. Phrases such as "when," "in the case of," "if," and "if" all imply that the device will perform a corresponding action under certain objective circumstances. They do not limit the time, do not require the device to perform a judgment action during implementation, and do not imply any other limitations.

[0104] In the embodiments of the present application, "uplink signaling" may refer to signaling sent from a terminal device (such as an IoT device) to a network (such as a reader or core network element), and "downlink signaling" may refer to signaling sent from a network (such as a reader or core network element) to a terminal device (such as an IoT device). For example, the downlink of downlink signaling refers to the direction in which signaling is sent: from the application function network element to the core network element, then to the access network device, and then to the IoT device; the uplink of uplink signaling refers to the direction in which signaling is sent: from the IoT device to the access network device, to the core network element, and then to the application function network element. Downlink signaling or uplink signaling is not necessarily end-to-end (i.e., IoT device to application function network element), but can be in the corresponding direction, such as from the IoT device to the core network element or access network device.

[0105] In addition, the network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field can know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0106] A communication system to which the embodiments of the present application can be applied is described below.

[0107] The embodiments of the present application can be applied to scenarios where traditional radio frequency identification (RFID) systems are optimized, or to scenarios where tags are counted via mobile communication systems, without limitation. The following describes the technical solution of the present application using the scenario where tags are counted via mobile communication systems as an example.

[0108] The embodiments of the present application can be applied to various mobile communication systems. For example: long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system, public land mobile network (PLMN), fifth generation (5G) system, sixth generation (6G) system or future communication system. The 5G system in the present application includes a non-standalone (NSA) 5G mobile communication system or a standalone (SA) 5G mobile communication system. The embodiments of the present application can also be applied to non-terrestrial network (NTN) communication systems such as satellite communication systems. The embodiments of the present application can also be applied to device-to-device (D2D) communication systems, sidelink (SL) communication systems, machine-to-machine (M2M) communication systems, machine type communication (MTC) systems, Internet of Things (IoT) communication systems, vehicle-to-everything (V2X) communication systems, uncrewed aerial vehicle (UAV) communication systems, or other communication systems.

[0109] Exemplarily, FIG1 shows a network architecture to which embodiments of the present application may be applied.

[0110] Figure 1 is a schematic diagram of a network architecture to which an embodiment of the present application can be applied. The network architecture may include: tags, access network equipment, tag management functions (TMFs) and application functions (AFs). Tags can interact with TMFs through access network equipment. Access network equipment and TMFs can communicate through interfaces. TMFs can communicate with AFs directly or through network exposure functions (NEFs). Optionally, the network architecture may also include: unified data management (UDM) network elements and unified data repositories (UDRs), etc. TMFs can communicate with UDMs or UDRs through interfaces. The dotted lines and dotted boxes in Figure 1 represent optional network elements and optional connections.

[0111] The following is a brief description of the network elements or devices involved in FIG1 .

[0112] 1. Tags

[0113] In the embodiments of the present application, the tag may also be referred to as a terminal, a terminal device, a user equipment (UE), an access terminal, a user unit, a user station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent, a user device, an Internet of Things terminal, an Internet of Things device, or an Internet of Things terminal device, etc. The terminal may be a passive Internet of Things terminal or a tag. The terminal may be a passive device, which may be a passive tag that can collect energy through backscattering technology to send and receive messages. Passive tags include but are not limited to radio frequency identification (RFID), Bluetooth, Zigbee and other non-powered terminal tags. The terminal may also be a semi-passive device or an active device. The active device may be a device with wireless transceiver function, such as a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical, 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, a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal in a 5G mobile communication system or a terminal in a future evolution network, etc. Wearable devices, also known as wearable smart devices, are a general term for wearable devices developed by applying wearable technology to intelligently design everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into clothing or accessories. Wearable devices are more than just hardware devices; they deliver powerful functionality through software support, data interaction, and cloud-based interaction.In a broad sense, wearable smart devices include those that are fully functional, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0114] It should be noted that the device for realizing the function of the tag can be a tag, or it can be a device that can support the tag to realize the function, such as a chip system, which can be installed in the tag or used in combination with the tag. In the embodiment of the present application, the chip system can be composed of a chip, or it can include a chip and other discrete devices. In the embodiment of the present application, only the device for realizing the function of the tag is used as an example for description, and does not limit the solution of the embodiment of the present application.

[0115] 2. Access network equipment

[0116] In the embodiments of the present application, the access network device, which may also be referred to as an access device or network device, manages wireless resources, provides access services to user devices, and forwards user device data between the user device and the core network. The access network device can also be understood as a base station in the network. The reader / writer involved in the embodiments of the present application can be deployed in the access network device. In other words, the access network device has reader / writer capabilities, that is, the ability to inventory tags.

[0117] Exemplarily, the access network device in the embodiment of the present application may be any communication device with wireless transceiver functions for communicating with user equipment. The access network equipment includes but is not limited to: evolved Node B (eNB), radio network controller (RNC), Node B (NB), base station controller (BSC), base transceiver station (BTS), home evolved NodeB (HeNB, or home Node B, HNB), baseband unit (BBU), access point (AP) in wireless fidelity (WIFI) system, wireless relay node, wireless backhaul node, transmission point (TP) or transmission and reception point (TRP), etc., and can also be a 5G mobile communication system, such as a gNB in ​​an NR system, or a transmission point (TRP or TP), one or a group of (including multiple antenna panels) antenna panels of a base station in a 5G mobile communication system, or it can also be a network node constituting a gNB or a transmission point, such as a baseband unit (BBU) or a distributed unit (DU), etc.

[0118] In some deployments, the access network device may include a CU, a DU, or both a CU and a DU, or a device comprising a control plane CU node (central unit-control plane (CU-CP)), a user plane CU node (central unit-user plane (CU-UP)), and a DU node. For example, the access network device may include a gNB-CU-CP, a gNB-CU-UP, and a gNB-DU. The CU (or CU-CP and CU-UP) implements some functions of the access network device, while the DU implements some functions of the access network device. For example, the CU is responsible for processing non-real-time protocols and services, implementing the functions of the radio resource control (RRC) and packet data convergence protocol (PDCP) layers. The DU is responsible for processing physical layer protocols and real-time services, implementing the functions of the radio link control (RLC), media access control (MAC), and physical (PHY) layers. The AAU implements some physical layer processing functions, RF processing, and active antenna-related functions. The information of the RRC layer is generated by the CU, and will eventually be encapsulated by the PHY layer of the DU to become PHY layer information, or converted from PHY layer information. Therefore, under this architecture, high-level signaling such as RRC layer signaling can also be considered to be sent by the DU, or sent by the DU+AAU. It can be understood that the access network device can be a device including one or more of the CU node, DU node, and AAU node. In addition, the CU can be divided into an access network device in the access network, and the CU can also be divided into an access network device in the core network (CN), and this application does not limit this.

[0119] In different systems, CU (or CU-CP and CU-UP), DU or RU may also have different names, but those skilled in the art can understand their meanings. For example, in the ORAN system, CU may also be called O-CU (Open CU), DU may also be called O-DU, CU-CP may also be called O-CU-CP, CU-UP may also be called O-CU-UP, and RU may also be called O-RU. Any unit of CU (or CU-CP, CU-UP), DU and RU in this application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0120] It should be noted that the device for implementing the functions of the access network device can be the access network device; it can also be a device that can support the access network device to implement the functions, such as a chip system, hardware circuit, software module, or hardware circuit and software module. The device can be installed in the access network device or used in conjunction with the access network device. In the embodiments of the present application, only the device for implementing the functions of the access network device is used as an example to illustrate, and does not constitute a limitation on the solutions of the embodiments of the present application.

[0121] The access network device and / or tag can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on the water surface; it can also be deployed on aircraft, balloons and satellites in the air. The embodiments of this application do not limit the scenarios in which the access network device and the tag are located. In addition, the tag and the access network device can be a hardware device, or it can be a software function running on dedicated hardware, a software function running on general-purpose hardware, such as a virtualized function instantiated on a platform (for example, a cloud platform), or an entity including dedicated or general-purpose hardware devices and software functions. This application does not limit the specific form of the tag and the access network device.

[0122] In addition, in order to support artificial intelligence (AI) technology in wireless networks, AI nodes may also be introduced into the network. Optionally, the AI ​​node can be deployed in one or more of the following locations in the communication system: access network equipment, tags, or core network elements, or the AI ​​node can be deployed separately, for example, in a location other than any of the above devices, such as a host or cloud server in an over-the-top (OTT) system. The AI ​​node can communicate with other devices in the communication system, and the other devices can be, for example, one or more of the following: access network equipment, tags, or core network elements.

[0123] 3. TMF

[0124] The TMF is primarily responsible for managing tags, such as for tag inventory and access management. The TMF can be an independent network element, or it can be co-located or deployed with other network elements, such as the access and mobility management function (AMF) network element, user plane function (UPF), UDM, or UDR. The co-location of the TMF with the AMF, UPF, UDM, or UDR can be understood as improving other network elements so that they have the functions of the TMF. For example, improving the AMF, UPF, UDM, or UDR so that the AMF, UPF, UDM, or UDR has the functions of the TMF can also be understood as, in addition to having functions such as tag inventory and access management, the TMF can also have the functions of the AMF, UPF, UDM, or UDR. For example, the TMF can assume the functions of tag mobility management, tag user data transmission, tag mobility management, unified tag data management, or tag data caching.

[0125] 4.AF

[0126] AF can be an application function of a third party or operator. It is an interface for the mobile communication system to obtain external application data and is mainly used to convey the requirements of the application side to the network side.

[0127] 5. NEF

[0128] The NEF is primarily used to expose the services and capabilities of the 3rd Generation Partnership Project (3GPP) network functions to the AF, and also allows the AF to provide information to the 3GPP network functions. The NEF is an optional network element.

[0129] 6. UDM

[0130] The UDM is primarily used to generate 3GPP authentication and key agreement (AKA) certificates, handle user IDs, provide access authorization based on contract information, manage service network function (NF) registration, manage contract information, and manage other related data. The UDM is an optional network element; for example, the TMF can be responsible for the unified management of tag data.

[0131] 7. UDR

[0132] The UDR is primarily used by the UDM to store and retrieve contract data, the Policy Control Function (PCF) network element to store and retrieve policy data, store and use structured data for capability exposure, and store application data for application detection. The UDM is an optional network element; for example, the TMF can be used to cache label data.

[0133] In the network architecture shown in Figure 1, each network element may communicate with each other through an interface. The interface between each network element may be a physical interface, a logical interface, a protocol interface, or a service-oriented interface, which is not limited in this application.

[0134] It should be understood that the network architecture shown above is only an exemplary illustration, and the network architecture applicable to the embodiments of the present application is not limited to this. Any network architecture that can realize the functions of the above-mentioned network elements is applicable to the embodiments of the present application.

[0135] It should also be understood that the functions or network elements such as TMF, NEF, UDM, UDR, AF, etc. shown in Figure 1 can be understood as network elements used to implement different functions, for example, they can be combined into network slices as needed. These network elements can be independent devices, or they can be integrated into the same device to implement different functions, or they can be network elements in hardware devices, or they can be software functions running on dedicated hardware, or they can be virtualized functions instantiated on a platform (for example, a cloud platform). This application does not limit the specific form of the above network elements.

[0136] It should also be understood that the above naming is defined only to facilitate the distinction between different functions and should not constitute any limitation to this application. This application does not exclude the possibility of adopting other naming in 6G networks and other future networks. For example, in a 6G network, some or all of the above network elements may continue to use the terminology used in 5G, or may adopt other names.

[0137] FIG2 is a schematic flow chart of tag sensor data collection and reading.

[0138] Step 201: AF sends a data request message to TMF. Correspondingly, TMF receives the data request message from AF.

[0139] The data request message is used to notify the TMF to read the sensor data of the tag. The data request message usually carries information related to data reading. The information related to data reading can include one or more of the following: data reading area information, tag identification range, or tag type. The tag identification is information that can uniquely identify the tag, such as the tag identifier (TID) or electronic product code (EPC).

[0140] Step 202: TMF sends an inventory request message to the reader according to the data request message. Correspondingly, the reader receives the inventory request message from TMF.

[0141] The inventory request message is used to request the reader to perform an inventory on the tags. The inventory request message may carry information about the tags to be inventoried, such as the tag identification range, tag type, etc.

[0142] The TMF may send an inventory request message to one or more readers / writers, and the one or more readers / writers may be determined based on the area information of the data read carried in the data request message.

[0143] It should be noted that a reader / writer is a device that reads and / or writes information to tags. A reader / writer may also be referred to as a card reader, a read / write device, a readout device, a scanner, a reader head, a communicator, a reader, an interpreter, or any device with read and / or write functions. A reader / writer can be integrated into access network equipment, relay equipment, or terminal equipment, or it can be a dedicated reader / writer, without limitation.

[0144] In step 203, the reader sends an excitation signal to the tags within the reader's coverage area based on the inventory request message. The tags within the reader's coverage area receive the excitation signal, which powers the tags. After powering, the tags have the energy to send information or data to the reader.

[0145] Step 204: The reader sends a selection command to the tags within the coverage of the reader. Correspondingly, the tags within the coverage of the reader receive the selection command sent by the reader.

[0146] The select command is used to select the tags to be counted.

[0147] Exemplarily, the select command may include conditions that the tags must meet, and the tags to be counted are those that meet the conditions in the select command. Thus, upon receiving the select command, tags within the reader's coverage area can be matched to determine whether they meet the conditions in the select command. The select command is used to select tags, selecting one or more tags within the range using a tag ID range. If the tag or tags successfully match the tag identification range in step 201, then the tag or tags' identifications fall within the tag identification range. The tag ID can be the tag's EPC code, the tag's TID, or another tag ID for unique tag identification. For example, if the select command carries a TID range, the tag can determine whether the value in its TID storage area is within the TID range. If the value in the tag's TID storage area is within the TID range, then the tag is selected or successfully matched and is a tag to be counted. If the value in the tag's TID storage area is not within the TID range, then the tag is not selected or the match fails and is not a tag to be counted.

[0148] Step 205: The tag performs matching according to the selection command and performs a random access process with the reader if the matching is successful.

[0149] The embodiments of the present application do not limit the specific implementation of random access. In one possible implementation, the reader sends a query command (query) to the tag. The query command can carry a Q value, which is used for the tag to randomly generate a random value in the range of (0, 2^Q–1) according to probability; after receiving the query command, the tag generates a random value according to probability. The tag with a random value of 0 replies to the reader with the random number RN16 it generated; after receiving the random number, the reader replies to the tag with an acknowledgment (ACK) command, which can carry the random number; the tag compares the random number sent and the random number received. When the two random numbers are consistent, the tag random access is successful. The query command can also be a repeated query command (QueryRep) or a query adjustment command (QueryAdjust).

[0150] Step 206: The tag that has successfully random accessed sends a registration request message to the TMF through the reader. Correspondingly, the TMF receives the registration request message from the tag.

[0151] The registration request message is used to register with TMF, and the registration request message carries a tag identifier.

[0152] Optionally, in step 207, the tag that has successfully random access and the TMF perform a security authentication process.

[0153] Step 208: TMF sends a registration acceptance message to the tag via the reader / writer, and the tag receives the registration acceptance message from TMF, wherein the registration acceptance message is used to indicate that the registration is successful.

[0154] If the tag and TMF perform the security authentication process, TMF will send a registration acceptance message to the tag if the security authentication is successful.

[0155] In step 209, the TMF sends a data read request message to the tag via the reader / writer, and the tag receives the data read request message from the TMF. The data read request message can be used to request reading of the sensor data of the tag.

[0156] Step 210: The tag collects sensor data according to the data read request message.

[0157] Step 211: After the sensor data collection is completed, the tag sends a data read response message to the TMF via the reader, and the TMF receives the data read response message from the tag, wherein the data read response message includes the sensor data collected by the tag.

[0158] Step 212: TMF sends the tag identification and corresponding sensor data to AF. Correspondingly, AF receives the tag identification and sensor data from TMF.

[0159] As shown in the process flow in Figure 2, the tag's sensor data collection is controlled by TMF commands. That is, the tag will only start collecting sensor data after receiving a data read request message from the TMF. However, collecting sensor data takes time. If all tags to be counted wait until all tags receive a data read request message before starting collection, the AF's sensor data acquisition efficiency will be very low.

[0160] In response to the above problems, the present application provides a data collection method and a communication device to improve the efficiency of the network in acquiring sensor data of tags.

[0161] The following describes the method embodiments of the present application.

[0162] FIG3 is a schematic flow chart of a data collection method 300 provided in this application.

[0163] Method 300 can be performed by an IoT device, a reader / writer, a core network element, and an AF. Unless otherwise specified, "IoT device," "reader / writer," "core network element," or "AF" may refer to an IoT device, a reader / writer, a core network element, or the AF itself, or may refer to a device that can support the IoT device, reader / writer, core network element, or AF to implement this function. For the sake of convenience, the following text will uniformly use IoT devices, readers / writers, core network elements, or AFs for description.

[0164] The IoT device may be the tag described above. The core network element is the network element responsible for managing IoT devices, such as the TMF described above. The reader / writer may be integrated into access network equipment, relay equipment, or terminal equipment, or may be a dedicated reader / writer, without limitation.

[0165] Method 300 includes at least part of the following.

[0166] Step 301: The AF sends a data request message to a core network element. Correspondingly, the core network element receives the data request message from the AF.

[0167] Data request messages are used to request sensor data from IoT devices to be inventoried or to notify core network elements to read sensor data from IoT devices to be inventoried. Data request messages typically carry information related to data retrieval. This information may include one or more of the following: the region where data is to be retrieved, the range of IoT device identifiers, or the type of IoT device. For example, if the IoT device is a tag, the tag identifier is information that uniquely identifies it, such as a TID or EPC.

[0168] Step 302: The core network element sends first information to the reader / writer according to the data request message. Correspondingly, the reader / writer receives the first information from the core network element.

[0169] The first information is used to instruct a first IoT device to collect sensor data. The first IoT device is an IoT device to be inventoried.

[0170] The embodiments of the present application do not limit the manner in which the core network element sends the first information.

[0171] In one possible implementation, the first information may be carried in downlink signaling sent before the first IoT device registers with a core network element. This process may include sending a registration request message before the first IoT device sends the registration request message and during the registration process. In other words, the first information may be carried in downlink signaling before the registration request message or during the registration process.

[0172] The downlink signaling before the registration request message includes a first inventory request message. The first inventory request message is used to request the reader to perform an inventory on the IoT devices to be inventoried. The first inventory request message can carry information about the IoT devices to be inventoried, such as the range of IoT device identifiers, the type of IoT devices, etc. The downlink signaling during the registration process of the first IoT device to the core network element includes at least one of the following: a first registration message, or downlink signaling during the first security authentication process. The first registration message is used to indicate that the first IoT device has successfully registered with the core network element. Exemplarily, the first registration message can be a registration acceptance message or a registration response message. The first security authentication process is a process in which the first IoT device performs security authentication with the core network element. Exemplarily, the downlink signaling during the first security authentication process can include an authentication pass message and / or an authentication request message, wherein the authentication pass message is used to indicate that the first IoT device has passed the security authentication, and the authentication request message includes security materials used for security authentication, so that the first IoT device can authenticate the core network element.

[0173] In addition, the core network element can send an inventory request message to one or more readers. The one or more readers can be determined based on the data collection area information carried in the data collection request message. The following is explained using one of the one or more readers as an example.

[0174] Step 303: After receiving the first information, the reader sends the first information to the first IoT device. Correspondingly, the first IoT device receives the first information from the reader.

[0175] The first information is used to instruct the first Internet of Things device to collect sensor data.

[0176] The embodiments of the present application do not limit the manner in which the reader sends the first information.

[0177] In one possible implementation, the first information is carried in downlink signaling sent before the first IoT device registers with the core network element. For a description of "before the first IoT device registers with the core network element," refer to step 303.

[0178] In step 303, the downlink signaling before the registration request message includes at least one of the following: a first excitation signal, a first selection command, and downlink signaling in the first random access process. The first excitation signal is used to power the IoT device to be inventoried. In one embodiment, the first excitation signal is a background carrier. The first selection command is used to select the IoT device to be inventoried. The first random access process is the process of the first IoT device accessing the reader / writer. Exemplarily, the downlink signaling in the first random access process includes one or more of a query command, a repeated query command, a query adjustment command, or a confirmation command. The downlink signaling in the process of the first IoT device registering with the core network element includes at least one of the following: a first registration message, or downlink signaling in the first security authentication process. The first registration message includes a registration acceptance message or a registration response message. The downlink signaling in the first security authentication process includes an authentication pass message and / or an authentication request message.

[0179] As an example, when a core network element sends first information via a first inventory request message, the reader can carry the first information in the downlink signaling during the first excitation signal, the first selection command, or the first random access process based on the first inventory request message, so that after receiving the first information, the first IoT device collects sensor data based on the first information. The first excitation signal, the first selection command, or the downlink signaling during the first random access process will be sent simultaneously to the IoT devices to be inventoried within the reader range. When there are multiple IoT devices to be inventoried, all of the multiple IoT devices will collect sensor data based on the first information.

[0180] As another example, when the core network element sends the first information through the first registration message or the downlink signaling in the first security authentication process, the reader can correspondingly send the first information to the first Internet of Things device through the first registration message or the downlink signaling in the first security authentication process. Since the signaling interaction in the registration process or the security authentication process is between the first Internet of Things device and the network (such as the reader or the core network element), the first Internet of Things device that receives the first registration message or the downlink signaling in the first security authentication process will collect sensor data based on the first information. For example, after the first Internet of Things device randomly accesses the reader, the first Internet of Things device starts the registration process or the first security authentication process, thereby receiving the first registration message or the downlink signaling in the first security authentication process, and collecting sensor data based on the first information therein.

[0181] Step 304: The first IoT device collects first sensor data based on the first information.

[0182] In step 305 , the first IoT device sends first sensing data to the reader / writer. Correspondingly, the reader / writer receives the first sensing data from the first IoT device.

[0183] The embodiments of the present application do not limit the manner in which the first IoT device sends the first sensor data.

[0184] In one possible implementation, when the first information is carried in the first excitation signal, the first selection command, or downlink signaling during the first random access process, the first sensing data may be carried in the second registration message, uplink signaling during the first security authentication process, or uplink signaling related to service transmission. The second registration message is used to request registration with a core network element. Exemplarily, the second registration message is a registration request message.

[0185] As an example, when the first IoT device successfully accesses the network randomly, the first IoT device also completes the collection of the first sensor data. The first IoT device can carry the first sensor data in the second registration message. This method can be applicable to the case where the first IoT device and the core network element do not require security authentication, and can also be applicable to the case where the first IoT device and the core network element do require security authentication, without limitation. The case where the first IoT device and the core network element do not require security authentication can refer to: in the current inventory, the first IoT device and the core network element do not require security authentication. For example, in the previous inventory process, the first IoT device was registered with the core network element and completed the security authentication between the core network element and the core network element. The core network element still retains the relevant information of the first IoT device. In this case, when the first IoT device is inventoried again, the security authentication process can be omitted. The case where the first IoT device and the core network element do not require security authentication can also refer to: the first IoT device and the core network element themselves do not require security authentication.

[0186] As another example, when the first Internet of Things device successfully accesses randomly, the first Internet of Things device completes the collection of the first sensor data in the first security authentication process. In this case, the first Internet of Things device can carry the first sensor data in the uplink signaling (such as an authentication request message or an authentication pass message) in the first security authentication process.

[0187] As another example, the first IoT device completes the collection of the first sensor data after the registration process. In this case, the first IoT device can carry the first sensor data in the uplink signaling related to the service transmission.

[0188] In another possible implementation, when the first information is carried in the first registration message or in downlink signaling in the first security authentication process, the first sensing data may be carried in uplink signaling related to service transmission.

[0189] Step 306: The reader sends the first sensing data to the core network element. Correspondingly, the core network element receives the first sensing data from the reader.

[0190] The embodiments of the present application do not limit the manner in which the reader sends the first sensor data. The manner in which the reader transmits the first sensor data corresponds to the manner in which the first IoT device transmits the first sensor data. Exemplarily, the reader forwards the signaling carrying the first sensor data received from the first IoT device to the core network network element. For example, when the first IoT device receives the second registration message, the uplink signaling in the first security authentication process, or the uplink signaling related to service transmission, the reader forwards the received second registration message, the uplink signaling in the first security authentication process, or the uplink signaling related to service transmission to the core network network element, thereby sending the first sensor data to the core network network element.

[0191] Step 307: The core network element sends the first sensing data to the AF. Correspondingly, the AF receives the first sensing data from the core network element.

[0192] In method 300, the core network element and the reader can send first information to the first IoT device via downlink signaling sent before the first IoT device registers with the core network element, instructing the first IoT device to collect sensor data. This allows the first IoT device to initiate sensor data collection before registering with the core network element. Compared to initiating sensor data collection in response to a data read request message from the core network element after successful registration, initiating sensor data collection before registering with the core network element helps advance the time at which the first IoT device reports sensor data, thereby improving the efficiency of the core network element in acquiring sensor data from the IoT device.

[0193] Furthermore, when the core network element sends the first information via a first inventory request message, the reader can, based on the first inventory request message, carry the first information in the downlink signaling during the first excitation signal, first selection command, or first random access process. This allows all IoT devices to be inventoried within the reader's range to collect sensor data in advance based on the first information. This advances the time for each IoT device to report sensor data, further improving the efficiency of the core network element in acquiring sensor data from IoT devices.

[0194] In an embodiment of the present application, the first Internet of Things device may proactively report the first sensor data after the first sensor data collection is completed, or may report the first sensor data after the first sensor data collection is completed based on a reporting instruction from a core network element. In the case where the first Internet of Things device reports the first sensor data with a reporting instruction, the core network element may further send a second message to the reader / writer, where the second message is used to instruct the first Internet of Things device to report the sensor data; after receiving the second message, the reader / writer may send the second message to the first Internet of Things device; and the first Internet of Things device may report the first sensor data based on the received second message. The second information and the first information may be carried in the same signaling or in different signaling, without limitation. For example, both the first information and the second information are carried in the first registration message. For another example, the first information is carried in the first excitation signal, the first selection command, the downlink signaling in the first random access process, or the downlink signaling in the first security authentication process, and the second information is carried in the first registration message.

[0195] In an embodiment of the present application, when the first IoT device reports the first sensor data, the core network element may further send a third message to the reader. The third message is used to instruct the first IoT device to send feedback information when the sensor data collection is not completed. The feedback information is used to instruct the first IoT device to maintain the communication connection with the first IoT device. After receiving the third message, the reader may send the third message to the first IoT device. Subsequently, if the first IoT device has not completed the collection of the first sensor data when the second message is received, the first IoT device may send feedback information to the reader. The reader may maintain the communication connection with the first IoT device based on the received feedback information. The reader may also send the feedback information to the core network element, so that the core network element maintains the communication connection with the first IoT device based on the received feedback information. In this way, before the collection of the first sensor data is completed, the communication connection between the first IoT device and the network side is always maintained. Once the collection of the first sensor data is completed, the first IoT device can report to the core network element in a timely manner, which helps improve the efficiency of the core network element in obtaining sensor data.

[0196] The third information and the first information may be carried in the same signaling or in different signaling, without limitation. For example, both the first information and the third information may be carried in the first registration message. For another example, the first information may be carried in the first excitation signal, the first selection command, the downlink signaling in the first random access process, or the downlink signaling in the first security authentication process, and the third information may be carried in the first registration message.

[0197] Furthermore, before completing the collection of the first sensor data, the first IoT device may send one or more pieces of feedback information. Optionally, the third information further indicates a period for sending the feedback information. Thus, the first IoT device may periodically send feedback information according to the period indicated by the third information to maintain a communication connection with the network.

[0198] In an embodiment of the present application, for the first IoT device, the network side can maintain a timer. During the operation of the timer, the network side maintains a communication connection with the first IoT device. After the timer times out, the network side disconnects the communication connection with the first IoT device and starts to inventory the next IoT device. In this case, if the first IoT device completes the collection of the first sensor data after the timer times out, the first IoT device executes a random access process and a registration process to re-establish a communication connection with the network side, and transmits the first sensor data through the newly established communication connection. This can avoid waiting for a long time for a certain IoT device to report sensor data, helps other IoT devices to access the network in a timely manner, and helps to improve the efficiency of the core network network elements in acquiring sensor data.

[0199] As an example, the core network element maintains the above-mentioned timer. For example, after sending the second information or the first information, the core network element starts the first timer, and the timing duration of the first timer is the first duration. If the core network element receives the first sensor data from the reader within the first duration, then after receiving the first sensor data, the core network element sends the fifth information to the reader, and the fifth information is used to indicate the inventory of the next IoT device. Accordingly, the reader starts to inventory the next IoT device according to the fifth information. If the core network element does not receive the first sensor data from the reader within the first duration, the core network element disconnects the communication connection with the first IoT device and sends the fifth information to the reader, and the fifth information is used to indicate the inventory of the next IoT device. Accordingly, the reader starts to inventory the next IoT device according to the fifth information.

[0200] As another example, the above-mentioned timer is maintained by the reader. For example, after receiving the second information or the first information, the reader starts the first timer, and the timing duration of the first timer is the first duration. If the reader receives the first sensor data within the first duration, then after sending the first sensor data to the core network element, the reader can send the sixth information to the core network element. The sixth information is used to request an inventory of the next IoT device. Correspondingly, the core network element sends the fifth information to the reader based on the sixth information. The fifth information is used to instruct the inventory of the next IoT device. If the reader does not receive the first sensor data within the first duration, the reader disconnects the communication connection with the first IoT device and sends the sixth information to the core network element. The sixth information is used to request an inventory of the next IoT device. Correspondingly, the core network element disconnects the communication connection with the first IoT device based on the sixth information and sends the fifth information to the reader. The fifth information is used to instruct the inventory of the next IoT device.

[0201] Optionally, the network side may also provide the first duration of the timer to the first IoT device. For example, the reader or core network element sends fourth information to the first IoT device, and the fourth information is used to indicate the first duration. In this way, when the collection of the first sensor data is completed within the first duration, the first IoT device directly reports the first sensor data; when the collection of the first sensor data is completed after the first duration, the first IoT device re-establishes a communication connection with the network side and reports the first sensor data through the established communication connection. The fourth information and the first information can be carried in the same signaling or in different signaling without limitation. For example, both the first information and the fourth information are carried in the first registration message. For another example, the first information is carried in the first excitation signal, the first selection command, the downlink signaling in the first random access process, or the downlink signaling in the first security authentication process, and the fourth information is carried in the first registration message.

[0202] In an embodiment of the present application, the data request message sent by the AF to the core network element may further include periodic information, which is used to indicate the period for taking inventory of the IoT devices to be inventoried. In this way, the core network element can periodically take inventory of the IoT devices to be inventoried based on the periodic information.

[0203] In one possible implementation, during a first cycle, the core network element sends first information to the first IoT device and receives first sensor data reported by the first IoT device; during the next inventory cycle (recorded as the second cycle), the core network element initiates a new round of inventory process, and the inventory process during the second cycle is the same as the inventory process during the first cycle. For example, based on the cycle information, the core network element again sends the first information to the reader / writer via a second inventory request message or a fourth registration message during the second cycle, wherein the fourth registration message is used to indicate that the first IoT device has successfully registered with the core network element; after receiving the first information, the reader / writer sends the first information to the first IoT device via a second excitation signal, a second selection command, downlink signaling during the second random access process, a fourth registration message, or downlink signaling during the second security authentication process. Among them, the description of the second inventory request message, the fourth registration message, the second excitation signal, the second selection command, the downlink signaling in the second random access process, or the downlink signaling in the second security authentication process can refer to the first inventory request message, the first registration message, the first excitation signal, the first selection command, the downlink signaling in the first random access process, or the downlink signaling in the first security authentication process.

[0204] In another possible implementation, during a first cycle, the core network element sends a first message to the first IoT device, receives the first sensor data reported by the first IoT device, and after receiving the first sensor data, sends the first message to the first IoT device via a reader / writer. After receiving the first message, the first IoT device can collect the second sensor data. During the next inventory cycle (recorded as the second cycle), the core network element sends a second message to the reader / writer via a second inventory request message. The second message is used to instruct the first IoT device to report the sensor data. After receiving the second inventory request, the reader / writer sends the second message to the first IoT device via a second excitation signal, a second selection command, or downlink signaling during a second random access process. After receiving the second message, the first IoT device sends a third registration message based on the second message. The third registration message is used to request registration with the core network element. The third registration message includes the second sensor data. The reader / writer sends the third registration message to the core network element. After receiving the third registration message, the core network element sends the first message to the first IoT device via the reader / writer. In this way, in one cycle, the core network network element can again instruct the first Internet of Things device to collect sensor data after receiving the corresponding sensor data. In this way, in the next cycle, the core network network element can directly instruct the first Internet of Things device to report the second sensor data collected in advance, which helps to improve the efficiency of the core network network element in obtaining sensor data.

[0205] It should be noted that in the above approach, the core network element may not send the second information to the first IoT device, but rather the first IoT device may proactively report the second sensor data. For example, during the second period, upon receiving a registration acceptance message or a registration response message, the first IoT device may directly report the collected second sensor data.

[0206] It should also be noted that the embodiments of the present application do not limit the manner in which the first IoT device collects sensor data based on the newly received first information after transmitting the first sensor data. For example, the first IoT device may continuously collect sensor data and continuously update the sensor data. For another example, the first IoT device may continuously collect sensor data and cache all sensor data. For another example, the first IoT device may collect sensor data once and cache the data.

[0207] In an embodiment of the present application, the data request message sent by the AF to the core network element may further include a first data volume, where the first data volume is the data volume that triggers the core network element to report the sensor data to the AF. For example, when the first sensor data of 50 tags is collected, the TMF uniformly sends the first sensor data of the 50 tags to the AF. In this case, the core network element sending the first sensor data to the application function element may include: when the sensor data cached in the core network element reaches the first data volume, the core network element sending the sensor data cached in the core network element to the AF, where the sensor data cached in the core network element includes the first sensor data.

[0208] In an embodiment of the present application, the data request message sent by the AF to the core network element may further include indication information, where the indication information is used to indicate signaling carrying the first information. In this case, the core network element sending the first information to the reader / writer based on the data request message includes: the core network element sending the first information to the reader / writer in signaling indicated by the indication information based on the data request message.

[0209] In an embodiment of the present application, the core network element may also report only updated sensor data to the AF. For example, in a first cycle, the sensor data reported by the first IoT is data A, and in a second cycle, the sensor data reported by the first IoT is data B. Compared to data B, only the first part of data A is updated. In this case, the core network element may report the first part of data B to the AF.

[0210] 4 , the technical solution of the present application will be described in detail by taking the example of carrying the first information in the inventory request message and the selection command and carrying the sensor data in the service-related uplink signaling.

[0211] The label, TMF, collection indication information, service reporting message, data collection request message, and reporting indication information in Figure 4 can respectively correspond to the Internet of Things device, core network network element, first information, service-related uplink signaling, data request message, and second information in method 300.

[0212] FIG4 is a schematic flow chart of a data collection method 400 provided in this application.

[0213] Step 401: AF sends a data request message to TMF. Correspondingly, TMF receives the data request message from AF.

[0214] The data request message is used to notify the TMF to read the sensor data of the tag. The detailed description of step 401 can refer to step 301.

[0215] Step 402: The TMF sends an inventory request message to the reader according to the data request message. Correspondingly, the reader receives the inventory request message from the TMF.

[0216] The inventory request message is used to request the reader to perform an inventory of the tags. The inventory request message may carry information about the tags to be inventoried, such as the tag identification range and tag type. Furthermore, in the implementation of this application, the inventory request message may also carry collection instruction information, which is used to instruct the tags to collect sensor data.

[0217] The TMF may send an inventory request message to one or more readers / writers, and the one or more readers / writers may be determined based on the data collection area information carried in the data collection request message.

[0218] In step 403, the reader sends an excitation signal to the tags within the reader's coverage area based on the inventory request message. In response, the tags within the reader's coverage area receive the excitation signal, which powers the tags. After powering, the tags have the energy to send information or data to the reader.

[0219] In method 400 , tag # 1 is within the coverage range of the reader.

[0220] Step 404: The reader sends a selection command to the tags within the coverage of the reader. Correspondingly, the tags within the coverage of the reader receive the selection command sent by the reader.

[0221] The select command is used to select the tags to be counted.

[0222] For example, the selection command may include conditions that the tags need to meet, and the tags to be counted are those that meet the conditions in the selection command. In this way, after receiving the selection command, tags within the reader's coverage area can be matched to determine whether they meet the conditions in the selection command. Taking the selection command carrying a TID range as an example, the tag can determine whether the value in its TID storage area is within the TID range. If the value in the tag's TID storage area is within the TID range, the tag is selected or matched successfully and is among the tags to be counted. If the value in the tag's TID storage area is not within the TID range, the tag is not selected or the match fails and is not among the tags to be counted.

[0223] In addition, the selection command may also carry collection instruction information, which is used to instruct the tag to collect sensor data. In this way, the tag can start collecting sensor data after the matching is successful.

[0224] Step 405 : The tag performs matching according to the selection command and immediately starts sensor data collection if the matching is successful.

[0225] If multiple tags within the coverage of the reader are matched successfully, these multiple tags will start collecting sensor data.

[0226] Step 406: The successfully matched tag performs a random access process with the reader.

[0227] The embodiments of the present application do not limit the specific implementation of random access. In one possible implementation, the reader sends a query command to the tag, which can carry a Q value, which is used by the tag to generate a random value according to probability; after receiving the query command, the tag with a random value of 0 replies with a random number RN16 to the reader; after receiving the random number, the reader replies with an acknowledgment (ACK) command to the tag, which can carry the random number; the tag compares the random number it sent with the random number it received, and when the two random numbers are consistent, the tag successfully completes random access. The query command can also be a repeated query command or a query adjustment command.

[0228] The method 400 takes label #1 as an example of a label for which random access is successful.

[0229] Step 407: Tag #1 sends a registration request message to TMF via the reader / writer. Correspondingly, TMF receives the registration request message from tag #1.

[0230] The registration request message is used to register with the TMF, and the registration request message carries the identifier of label #1.

[0231] Optionally, in step 408 , tag # 1 and TMF perform a security authentication process.

[0232] Step 409: TMF sends a registration acceptance message #1 to the reader / writer. Correspondingly, the reader / writer receives the registration acceptance message #1 from TMF.

[0233] The registration acceptance message #1 is used to indicate that the tag #1 is successfully registered.

[0234] Optionally, the registration acceptance message #1 may also carry reporting indication information, where the reporting indication information is used to instruct the tag #1 to report the sensing data.

[0235] If the tag and TMF perform a security authentication process, the TMF sends a registration acceptance message #1 to the tag if the security authentication is successful.

[0236] In one possible implementation, a timer #1 can be maintained in TMF. During the operation of timer #1, TMF maintains a communication connection with tag #1. After timer #1 expires or times out, TMF no longer maintains a communication connection with tag #1, and TMF can instruct the reader to inventory the next tag, and the reader no longer powers tag #1. In this case, if tag #1 wants to communicate with the network side, tag #1 needs to re-execute the random access process. This can avoid waiting for a long time for a tag to report sensor data, and helps other tags to join the network in time. Optionally, TMF can carry duration information #1 in the registration acceptance message #1. Duration information #1 is used to indicate the timing duration of timer #1 so that the reader can provide it to tag #1.

[0237] In another possible implementation, the TMF can provide duration information #2 to the reader via registration acceptance message #1. Duration information #2 indicates the duration of the communication connection with tag #1, or the duration of communication with tag #1. The reader can then maintain a timer #2 based on duration information #2, with the duration of timer #2 being the duration indicated by duration information #2. While timer #2 is running, the reader maintains a communication connection with tag #1 and continues to power tag #1. Upon expiration or timeout of timer #2, the reader discontinues the communication connection with tag #1, discontinues powering tag #1, and notifies the TMF that it can inventory the next tag. In this case, if tag #1 wishes to communicate with the network, it must re-execute the random access process. This avoids waiting for a tag to report sensor data, facilitating timely network access for other tags.

[0238] In another possible implementation, the TMF can include indication information #1 in the Registration Accept message #1. Indication information #1 instructs tag #1 to send feedback information even if sensor data collection is not yet complete. This feedback information indicates that sensor data collection is not yet complete. In this way, the reader and TMF can maintain a communication connection with tag #1 based on the feedback information from tag #1 and keep powering tag #1. Optionally, the Registration Accept message #1 can also include periodic information #1, which indicates the period for sending feedback information.

[0239] In step 410, the reader sends a registration acceptance message #2 to tag #1. Accordingly, tag #1 receives the registration acceptance message #2 from the reader.

[0240] The registration acceptance message #2 is used to indicate that the registration of tag #1 is successful.

[0241] Optionally, the registration acceptance message #2 carries reporting indication information, and the reporting indication information is used to instruct the tag #1 to report the sensing data.

[0242] In one possible implementation, when the registration acceptance message #1 carries duration information #1, the reader can carry duration information #1 in the registration acceptance message #2, so that tag #1 can report the sensor data according to duration information #1. For example, tag #1 completes the collection of sensor data within the duration indicated by duration information #1. In this case, the communication connection between tag #1 and the reader and TMF still exists, and tag #1 can directly report the sensor data to TMF through the reader without random access again. For another example, tag #1 completes the collection of sensor data after the duration indicated by duration information #1. In this case, the communication connection between tag #1 and the reader and TMF no longer exists. If tag #1 wants to report the sensor data, it needs to perform random access again, that is, it needs to wait for the reader to take inventory of tag #1 next time.

[0243] In another possible implementation, when Registration Accept Message #1 carries Duration Information #2, the reader can maintain a Timer #2 based on Duration Information #2. Timer #2's duration is the duration indicated by Duration Information #2. While Timer #2 is running, the reader maintains a communication connection with Tag #1 and continues to power Tag #1. Upon expiration or timeout of Timer #2, the reader discontinues the communication connection with Tag #1, discontinues powering Tag #1, and sends a notification to the TMF indicating that the next tag is ready for inventory.

[0244] Optionally, the reader can provide duration information #2 to tag #1 via registration acceptance message #2, so that tag #1 can report sensor data based on duration information #2. For example, tag #1 completes the collection of sensor data within the duration indicated by duration information #2. In this case, the communication connection between tag #1, the reader and TMF still exists, and tag #1 can directly report sensor data to TMF through the reader without random access again. For another example, tag #1 completes the collection of sensor data after the duration indicated by duration information #2. In this case, the communication connection between tag #1, the reader and TMF no longer exists. If tag #1 wants to report sensor data, it needs to perform random access again, that is, it needs to wait for the reader to take inventory of tag #1 next time.

[0245] In another possible implementation, when Registration Accept Message #1 carries Indication Information #1, the reader may carry Indication Information #1 in Registration Accept Message #2. Indication Information #1 instructs Tag #1 to send feedback information even if sensor data collection has not yet completed. Optionally, Registration Accept Message #2 may also carry Periodic Information #2, which indicates the period for sending feedback information. When Registration Accept Message #1 carries Periodic Information #1, Periodic Information #2 can be determined based on Periodic Information #1, e.g., if Periodic Information #2 is the same as Periodic Information #1. The reader may also determine Periodic Information #2 on its own.

[0246] Optionally, in step 411, when the registration acceptance message #2 carries indication information #1 and tag #1 has not yet completed sensor data collection, tag #1 sends feedback information to the reader, or in other words, the reader receives feedback information from tag #1. The feedback information indicates that sensor data collection has not yet been completed.

[0247] Tag #1 may send one or more feedback messages to the reader to maintain the communication connection between tag #1 and the reader until the sensor data collection is completed. In one possible implementation, if registration acceptance message #2 carries period information #2, tag #1 may send feedback messages according to the period indicated by period information #2.

[0248] Step 412: Tag #1 completes sensor data collection.

[0249] In step 413, tag #1 sends a service report message to the TMF via the reader / writer, and the TMF receives the service report message from the tag, wherein the service report message includes sensor data.

[0250] In one possible implementation, when the registration acceptance message #2 carries reporting indication information, tag #1 can report the sensor data according to the reporting indication information. When the registration acceptance message #2 does not carry reporting indication information, tag #1 determines on its own whether to report the collected sensor data.

[0251] In one possible implementation, when registration acceptance message #2 carries duration information #1 or duration information #2, tag #1 can report sensor data based on duration information #1 or duration information #2. For example, tag #1 completes sensor data collection within the duration indicated by duration information #1 or duration information #2. In this case, the communication connection between tag #1 and the reader and TMF still exists, and tag #1 can directly report sensor data to the TMF through the reader without the need for random access again. For another example, tag #1 completes sensor data collection after the duration indicated by duration information #1 or duration information #2. In this case, the communication connection between tag #1 and the reader and TMF no longer exists. If tag #1 wants to report sensor data, it needs to perform random access again, that is, it needs to wait for the reader to perform the next inventory of tag #1. Figure 4 shows the situation where tag #1 completes sensor data collection within the duration indicated by duration information #1 or duration information #2.

[0252] Optionally, in step 414, if tag #1 does not receive a service acceptance message indicating successful reception of the sensor data within a preset time, tag #1 may again send a service reporting message to the TMF through the reader / writer, where the service reporting message includes the sensor data.

[0253] Optionally, in step 415, the TMF sends a service acceptance message to tag #1 through the reader / writer, indicating that the sensing data has been successfully received. Accordingly, tag #1 receives the service acceptance message from the TMF.

[0254] Step 416: After receiving the sensor data from tag #1, TMF sends the tag #1 identifier and the corresponding sensor data to AF. Correspondingly, AF receives the tag #1 identifier and the sensor data from TMF.

[0255] In step 417, the TMF sends a command to the reader to take inventory of the next tag. Correspondingly, the reader receives the command from the TMF.

[0256] Step 418: Repeat steps 406 to 417 until all tags are counted.

[0257] 5 , the technical solution of the present application will be described in detail by taking the example of carrying the first information in the inventory request message and the selection command and carrying the sensor data in the registration request message.

[0258] The label, TMF, collection indication information, service reporting message, data collection request message, and reporting indication information in Figure 5 can respectively correspond to the Internet of Things device, core network network element, first information, service-related uplink signaling, data request message, and second information in method 300.

[0259] FIG5 is a schematic flow chart of a data collection method 500 provided in this application.

[0260] Step 501: The AF sends a data collection request message to the TMF. Correspondingly, the TMF receives the data collection request message from the AF. The data collection request message is used to notify the TMF to read the data of the tag.

[0261] In step 502, the TMF sends an inventory request message to the reader based on the data collection request message. The reader receives the inventory request message from the TMF. The inventory request message requests the reader to perform an inventory of the tags. The inventory request message may carry information about the tags to be inventoried, such as the tag ID range and tag type. Furthermore, the inventory request message may carry collection instruction information, which instructs the tags to collect sensor data. Step 502 is similar to step 402 and will not be described in detail here.

[0262] Step 503: The reader sends an excitation signal to the tags within the coverage of the reader according to the inventory request message. Correspondingly, the tags within the coverage of the reader receive the excitation signal sent by the reader, so that the tags are powered.

[0263] In step 504, the reader sends a select command to the tags within its coverage area. In response, the tags within the reader receive the select command. The select command is used to select the tags to be counted. Furthermore, the select command may also carry collection instructions, which instruct the tags to collect sensor data.

[0264] Step 505 : The tag performs matching according to the selection command and immediately starts sensor data collection if the matching is successful.

[0265] Step 506: The successfully matched tag performs a random access process with the reader.

[0266] Steps 501 to 506 may refer to steps 401 to 406 and will not be described in detail.

[0267] Method 500 takes label #1 as an example of a label for which random access is successful.

[0268] When tag #1 completes random access, two situations may occur depending on whether tag #1 completes the collection of sensor data. The two situations are respectively introduced below.

[0269] Case 1: When tag #1 completes random access, tag #1 has already completed the collection of sensor data.

[0270] In this case, steps 507 to 509 may be performed.

[0271] Step 507 , tag #1 has completed sensor data collection.

[0272] The embodiments of the present application do not limit the specific time at which Tag #1 completes sensor data collection; as long as Tag #1 is in a state where sensor data collection is complete when Tag #1 completes random access, it is sufficient. For example, Tag #1 completes sensor data collection during the random access process. For another example, Tag #1 completes sensor data collection after the random access process but before sending a registration request message.

[0273] Step 508: Tag #1 sends a registration request message to TMF via the reader / writer. Correspondingly, TMF receives the registration request message from Tag #1.

[0274] The registration request message is used to register with the TMF, and the registration request message carries the identifier and sensor data of tag #1.

[0275] Step 509: TMF sends a registration acceptance message to tag #1 through the reader box. Correspondingly, the tag receives the registration acceptance message from TMF.

[0276] The registration acceptance message is used to indicate that tag #1 has been successfully registered and the sensor data has been successfully received.

[0277] Case 2: When tag #1 completes random access, tag #1 has not yet completed the collection of sensor data.

[0278] In this case, steps 510 to 517 may be performed.

[0279] In step 510, tag #1 sends a registration request message to TMF via the reader / writer. Correspondingly, TMF receives the registration request message from tag #1.

[0280] The registration request message is used to register with the TMF. The registration request message carries the identifier of tag #1 but does not carry sensor data.

[0281] In step 511, the TMF sends a Registration Acceptance message #1 to the reader. In response, the reader receives Registration Acceptance message #1 from the TMF. Registration Acceptance message #1 indicates that tag #1 has successfully registered. Optionally, Registration Acceptance message #1 may carry one or more of: reporting indication information, duration information #1, duration information #2, indication information #1, or cycle information #1.

[0282] In step 512, the reader sends a registration acceptance message #2 to tag #1. In response, tag #1 receives registration acceptance message #2 from the reader. Registration acceptance message #2 indicates that tag #1 has successfully registered. Optionally, registration acceptance message #2 may include one or more of reporting indication information, duration information #1, duration information #2, indication information #1, or period information #2.

[0283] Optionally, in step 513, when the registration acceptance message #2 carries indication information #1 and tag #1 has not yet completed sensor data collection, tag #1 sends feedback information to the reader, or in other words, the reader receives feedback information from tag #1. The feedback information indicates that sensor data collection has not yet been completed.

[0284] Step 514 , tag #1 completes sensor data collection.

[0285] In step 515, tag #1 sends a service report message to TMF via the reader / writer, and TMF receives the service report message from the tag, wherein the service report message includes sensor data.

[0286] Optionally, in step 516, if tag #1 does not receive a service acceptance message indicating successful reception of the sensor data within a preset time, tag #1 may again send a service reporting message to the TMF through the reader / writer, where the service reporting message includes the sensor data.

[0287] Optionally, in step 517, the TMF sends a service acceptance message to tag #1 through the reader / writer, indicating that the sensing data has been successfully received. Accordingly, tag #1 receives the service acceptance message from the TMF.

[0288] Steps 510 to 517 may refer to steps 407 and 409 to 415 and will not be described in detail.

[0289] After tag #1 completes reporting of the sensing data, steps 518 to 520 may be executed.

[0290] Step 518: After receiving the sensor data from tag #1, TMF sends the tag #1 identifier and the corresponding sensor data to AF. Correspondingly, AF receives the tag #1 identifier and the sensor data from TMF.

[0291] In step 519, the TMF sends a command to the reader to take inventory of the next tag. Correspondingly, the reader receives the command from the TMF.

[0292] Step 520: Repeat steps 506 to 519 until all tags are counted.

[0293] It should be noted that method 500 can be applied to scenarios where security authentication between the tag and the TMF is not required. For example, a scenario where the tag has already completed registration with the TMF and has already performed security authentication with the TMF before registration is completed. Another example is a scenario where the TMF trusts the tag.

[0294] 6 , the first inventory and the second inventory of tags will be described in detail by taking the example of the AF providing the TMF with the first information or the second information in the registration acceptance message.

[0295] The label, TMF, collection indication information, service reporting message, data collection request message, and reporting indication information in Figure 6 can respectively correspond to the Internet of Things device, core network network element, first information, service-related uplink signaling, data request message, and second information in method 300.

[0296] FIG6 is a schematic flow chart of a data collection method 600 provided in this application.

[0297] Step 601: AF sends a data collection request message to TMF. Correspondingly, TMF receives the data collection request message from AF.

[0298] The data collection request message is used to notify the TMF to read the tag data. The data collection request message typically carries information related to the data collection. This information may include one or more of the following: the data collection area, the tag identifier range, or the tag type. The tag identifier is information that uniquely identifies the tag, such as the TID or EPC.

[0299] Optionally, the information related to data collection may also include one or more of cycle information #2, cached data volume, or indication information #2. Cycle information #2 is used to indicate the cycle for initiating the inventory process, or to indicate the cycle for collecting the latest sensor data. The cached data volume is the amount of data that triggers the TMF to report sensor data to the AF. For example, if the cached data volume is the sensor data of one tag, the TMF promptly reports the sensor data of a single tag to the AF after obtaining it. Another example is if the cached data volume is the sensor data of a preset number of tags, the TMF collectively reports the sensor data of the preset number of tags to the AF after obtaining it. Indication information #2 is used to indicate the method for issuing the collection indication information. The collection indication information is used to indicate the sensor data of a tag set. The method for issuing the collection indication information may refer to the timing of sending the collection indication information or the message or command used to carry the collection indication information. For example, the collection indication information may be carried in an inventory request message or in a registration acceptance message. Method 600 takes the collection indication information carried in a registration acceptance message as an example.

[0300] Step 602: TMF sends an inventory request message to the reader according to the data collection request message. Correspondingly, the reader receives the inventory request message from TMF. The inventory request message is used to request the reader to perform an inventory on the tags.

[0301] In step 603, the reader sends an excitation signal to the tags within the coverage of the reader according to the inventory request message. Correspondingly, the tags within the coverage of the reader receive the excitation signal sent by the reader, so that the tags are powered.

[0302] In step 604, the reader sends a selection command to the tags within the reader's coverage, and the tags within the reader's coverage receive the selection command sent by the reader. The selection command is used to select the tags to be counted.

[0303] Step 605: The tag performs matching according to the selection command and performs a random access process with the reader if the matching is successful.

[0304] Step 606: The tag that has successfully random accessed sends a registration request message to the TMF via the reader. Correspondingly, the TMF receives the registration request message from the tag. The registration request message is used to register with the TMF and carries the tag identifier.

[0305] Optionally, in step 607, the tag that has successfully random access and the TMF perform a security authentication process.

[0306] Steps 602 to 607 can refer to steps 202 to 207 and will not be described in detail. In steps 602 to 607, since the inventory request message and the selection command do not carry collection indication information, the tag performs a normal random access or registration process. Method 600 uses Tag #1 as an example of a tag that successfully performs random access.

[0307] Step 608: TMF sends a registration acceptance message #3 to the reader, and the reader receives the registration acceptance message #3 from TMF. The registration acceptance message #3 indicates that the tag #1 has been successfully registered.

[0308] Registration Accept message #3 carries collection instruction information, which is used to instruct the tag to collect sensor data. In one possible implementation, when the data collection request message in step 601 carries instruction information #2, and instruction information #2 is used to indicate that the registration accept message should carry the collection instruction information, the TMF carries the collection instruction information in the registration accept message based on instruction information #2.

[0309] Optionally, Registration Accept Message #3 may also carry reporting instruction information, which is used to instruct Tag #1 to report sensor data. Optionally, Registration Accept Message #3 may also carry one or more of Duration Information #1, Duration Information #2, Indication Information #1, or Period Information #1. For a detailed description, please refer to Step 409.

[0310] If the tag and TMF perform a security authentication process, the TMF sends a registration acceptance message #3 to the tag if the security authentication is successful.

[0311] In step 609, the reader sends a registration acceptance message #4 to tag #1. In response, tag #1 receives the registration acceptance message #4 from the reader. Registration acceptance message #4 indicates that tag #1 has successfully registered. Registration acceptance message #4 may also carry collection instruction information, which instructs the tag to collect sensor data.

[0312] Optionally, the registration acceptance message #4 may also carry reporting indication information, where the reporting indication information is used to instruct the tag #1 to report the sensing data.

[0313] Optionally, the registration acceptance message #4 may also carry one or more of duration information #1, duration information #2, indication information #1, or period information #2. For a detailed description, please refer to step 410.

[0314] Step 610: Tag #1 completes sensor data collection.

[0315] In step 611, tag #1 sends a service report message to TMF via the reader / writer, and TMF receives the service report message from the tag, wherein the service report message includes sensor data.

[0316] In one possible implementation, tag #1 actively reports the sensor data to the reader after completing the data collection.

[0317] In another possible implementation, if the registration acceptance message #4 includes reporting indication information, then the tag #1 can report the sensing data to the reader / writer after the sensing data collection is completed according to the reporting indication information.

[0318] Optionally, in step 612, if tag #1 does not receive a service acceptance message indicating successful reception of the sensor data within a preset time, tag #1 may again send a service reporting message to the TMF through the reader / writer, where the service reporting message includes the sensor data.

[0319] Optionally, in step 613, the TMF sends a service acceptance message to tag #1 through the reader / writer, indicating that the sensing data has been successfully received. Accordingly, tag #1 receives the service acceptance message from the TMF.

[0320] Step 614: After receiving the sensor data from tag #1, TMF sends the tag #1 identifier and the corresponding sensor data to AF. Correspondingly, AF receives the tag #1 identifier and the sensor data from TMF.

[0321] In one possible implementation, when the data collection request message in step 601 carries a cached data volume, the TMF sends the sensor data of tag #1 to the AF based on the cached data volume. For example, if the cached data volume is the sensor data of one tag, the TMF may send the identifier of tag #1 and the corresponding sensor data to the AF after receiving the sensor data of tag #1. For another example, if the cached data volume is the sensor data of a preset number of tags, the TMF may send the sensor data of the preset number of tags to the AF after receiving the sensor data of the preset number of tags, where the sensor data of the preset number of tags includes the sensor data of tag #1.

[0322] Optionally, in step 615, TMF sends instruction information #3 to tag #1 via the reader / writer, and tag #1 receives instruction information #3 from TMF. Instruction information #3 is used to instruct tag #1 to continuously collect and cache sensor data.

[0323] Optionally, in step 616, tag #1 sends a response message to TMF via the reader / writer, and accordingly, TMF receives the response message from tag #1, wherein the response message is used to indicate that tag #1 has successfully received indication message #3.

[0324] It should be noted that steps 615-616 are only one way to enable tag #1 to continue collecting and caching sensor data for a period of time. Alternatively, tag #1 can, based on a built-in policy, continue collecting and caching sensor data after receiving the collection instruction information carried in the registration accept message until the TMF notifies tag #1 to stop collecting and caching sensor data. Alternatively, after receiving the collection instruction information carried in the registration accept message, tag #1 can default to continuing collecting and caching sensor data until the TMF notifies tag #1 to stop collecting and caching sensor data.

[0325] Step 617 , tag #1 continues to collect and cache sensor data.

[0326] Since tag #1 continuously caches the sensor data, when tag #1 needs to be counted again later, tag #1 can carry the sensor data in the registration request message.

[0327] Optionally, the inventory of the next tag may be continued, and steps 605 to 617 may be repeated until all tags are fully inventoried.

[0328] TMF can then inventory the tags again, and the specific process can be as follows.

[0329] Optionally, in step 618, the AF sends a data collection request message to the TMF, and correspondingly, the TMF receives the data collection request message from the AF, wherein the data collection request message is used to notify the TMF to read the data of the tag.

[0330] It should be noted that step 618 is only one way to trigger another inventory of tags. In another way, when the data collection request message in step 601 carries cycle information #2, TMF can regularly start the inventory of tags according to the cycle indicated by cycle information #2.

[0331] In step 619, the TMF sends an inventory request message to the reader based on the data collection request message. The reader receives the inventory request message from the TMF. The inventory request message requests the reader to perform an inventory of the tags. The inventory request message can carry information about the tags to be inventoried, such as the tag identification range and tag type. Furthermore, the inventory request message can carry reporting instructions, which instruct the tags to report the collected sensor data.

[0332] In step 620, the reader sends an excitation signal to the tags within the coverage of the reader according to the inventory request message. Correspondingly, the tags within the coverage of the reader receive the excitation signal sent by the reader, so that the tags are powered.

[0333] In step 621, the reader sends a select command to the tags within its coverage area. In response, the tags within the reader receive the select command. The select command is used to select tags to be counted. Furthermore, the select command may also carry reporting instructions, which instruct the tags to report collected sensor data.

[0334] Step 622: The successfully matched tag performs a random access process with the reader.

[0335] Method 600 takes label #1 as an example of a label for which random access is successful.

[0336] Since tag #1 continuously caches the sensor data, when tag #1 needs to be counted again later, tag #1 can carry the sensor data in the registration request message, as follows.

[0337] In step 623, tag #1 sends a registration request message to TMF via the reader. In response, TMF receives the registration request message from tag #1. The registration request message is used to register with TMF and carries the tag #1's identification and sensor data.

[0338] In step 624, TMF sends a registration acceptance message to tag #1 via the reader box. Accordingly, the tag receives the registration acceptance message from TMF, indicating that tag #1 has successfully registered and received sensor data.

[0339] Step 625 , tag #1 continues to collect and cache sensor data.

[0340] In step 626, after receiving the sensor data from tag #1, the TMF sends the tag #1 identifier and the corresponding sensor data to the AF. Correspondingly, the AF receives the tag #1 identifier and sensor data from the TMF. Step 626 can refer to step 614 and will not be described in detail.

[0341] The inventory of the next tag can be continued subsequently, and steps 622 to 626 are repeated until all tags are counted.

[0342] Optionally, when the tag is counted for the last time, TMF can send indication information #4 to the tag through the reader after receiving the sensor data from the tag. Instruction information #4 is used to instruct the tag to stop collecting sensor data. In this case, the tag can stop collecting sensor data.

[0343] The above describes in detail the method embodiment provided by the present application in conjunction with Figures 3 to 6 , and the following describes the device embodiment of the present application in conjunction with Figures 7 to 9 .

[0344] It is understood that, in order to implement the functions in the above embodiments, the apparatuses in Figures 7 to 9 include hardware structures and / or software modules corresponding to the functions. Those skilled in the art should readily appreciate that, in conjunction with the various exemplary units and method steps described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software.

[0345] Figures 7 and 8 are schematic diagrams of possible devices provided in embodiments of the present application. These devices can be used to implement the functions of IoT devices, core network elements, AFs, or readers in the above method embodiments, thereby also achieving the beneficial effects of the above method embodiments.

[0346] As shown in FIG7 , the device 10 includes a transceiver unit 11 and a processing unit 12 .

[0347] When the apparatus 10 is used to implement the functions of the IoT device in the above-mentioned method embodiments, the transceiver unit 11 is used to execute the transceiver steps of the IoT device, such as steps 303, 305, 403, 404, 406, 407, 410, 411, 413, 414, 415, 503, 504, 506, 508, 509, 510, 512, 513, 515, 516, 517, 603, 604, 606, 607, 609, 611, 612, 613, 615, 616, 620, 621, 622, 623 or 624, and the processing unit 12 is used to execute the processing steps of the IoT device, such as steps 304, 405, 412, 505, 507, 514, 610, 617 or 626, etc.

[0348] When the device 10 is used to implement the functions of the reader / writer in the above-mentioned method embodiments, the transceiver unit 11 is used to execute the transceiver steps of the reader / writer, such as steps 303, 305, 302, 306, 402, 403, 404, 406, 407, 408, 409, 410, 411, 413, 414, 415, 417, 502, 503, 504, 506, and 508. , 509, 510, 511, 512, 513, 515, 516, 517, 519, 602, 603, 604, 605, 606, 607, 608, 609, 611, 612, 613, 614, 615, 616, 619, 620, 621, 622, 623 or 624, the processing unit 12 is used to execute the processing steps of the reader / writer.

[0349] When the device 10 is used to implement the functions of the core network network element in the above-mentioned method embodiments, the transceiver unit 11 is used to execute the transceiver steps of the core network network element, such as steps 301, 302, 306, 307, 401, 402, 407, 408, 409, 413, 414, 415, 416, 417, 501, 502, 508, 509, 510, 511, 515, 516, 517, 518, 519, 601, 602, 606, 607, 608, 611, 612, 613, 614, 615, 616, 618, 619, 623, 623, 624 or 625, and the processing unit 12 is used to execute the processing steps of the core network network element.

[0350] When the device 10 is used to implement the AF function in the above-mentioned method embodiments, the transceiver unit 11 is used to execute the AF transceiver steps, such as steps 301, 307, 401, 416, 501, 518, 601, 614, 618 or 625, and the processing unit 12 is used to execute the AF processing steps.

[0351] For a more detailed description of the transceiver unit 11 and the processing unit 12 , please refer to the relevant description in the above method embodiment, which will not be described again here.

[0352] As shown in FIG8 , apparatus 20 includes a processing circuit 21. Processing circuit 21 is coupled to a memory 23, which is used to store instructions. When apparatus 20 is used to implement the method described above, processing circuit 21 is used to execute the instructions in memory 23 to implement the functions of processing unit 12 described above.

[0353] Optionally, the device 20 further includes a memory 23 .

[0354] Optionally, the apparatus 20 further includes an interface circuit 22. This interface circuit can be referred to as a communication interface. The processing circuit 21 and the interface circuit 22 are coupled to each other. It will be appreciated that the interface circuit 22 can be a transceiver or an input / output interface. When the apparatus 20 is used to implement the method described above, the processing circuit 21 is used to execute instructions to implement the functions of the processing unit 12, and the interface circuit 22 is used to implement the functions of the transceiver unit 11.

[0355] Optionally, the device 20 may be an IoT device, a core network element, an AF, or a reader / writer.

[0356] Optionally, the device 20 may be a chip applied to an IoT device, a core network element, an AF, or a reader / writer.

[0357] Exemplarily, when device 20 is a chip applied to an IoT device, a core network element, an AF, or a reader / writer, the chip implements the functions of the IoT device, the core network element, the AF, or the reader / writer in the above-mentioned method embodiments. The chip receives information from other modules (such as a radio frequency module or antenna) in the IoT device, the core network element, the AF, or the reader / writer, where the information is sent by other devices to the IoT device, the core network element, the AF, or the reader / writer; or the chip sends information to other modules (such as a radio frequency module or antenna) in the IoT device, the core network element, the AF, or the reader / writer, where the information is sent by the IoT device, the core network element, the AF, or the reader / writer to other devices.

[0358] 9 is a schematic diagram of a chip system 30 provided in an embodiment of the present application. The chip system 30 (or also referred to as a processing system) includes a logic circuit 31 and an input / output interface 32.

[0359] The logic circuit 31 may be a processing circuit in the chip system 30. The logic circuit 31 may be coupled to a storage unit and call instructions in the storage unit so that the chip system 30 can implement the methods and functions of the various embodiments of the present application. The input / output interface 32 may be an input / output circuit in the chip system 30, outputting information processed by the chip system 30 or inputting data or signaling information to be processed into the chip system 30 for processing.

[0360] As a solution, the chip system 30 is used to implement the operations performed by the IoT device, core network element, AF or reader / writer in the above various method embodiments.

[0361] For example, the logic circuit 31 is used to implement the processing-related operations performed by the Internet of Things device, core network network element, AF or reader / writer in the above method embodiment; the input / output interface 32 is used to implement the sending and / or receiving-related operations performed by the Internet of Things device, core network network element, AF or reader / writer in the above method embodiment.

[0362] The present application also provides a communication device, comprising a processing circuit coupled to a memory, the memory being used to store computer programs or instructions and / or data, and the processing circuit being used to execute the computer programs or instructions stored in the memory, or to read data stored in the memory, to perform the methods described in the above method embodiments. Optionally, there are one or more processing circuits. Optionally, the communication device includes a memory. Optionally, there are one or more memories. Optionally, the memory is integrated with the processing circuit or provided separately.

[0363] The present application also provides a chip, including a processing circuit, which is coupled to a memory, the memory is used to store computer programs or instructions, and the processing circuit is used to execute the computer programs or instructions stored in the memory to implement the methods performed by the Internet of Things device, core network network element, AF or reader in the above-mentioned method embodiments.

[0364] The present application also provides a computer-readable storage medium on which computer instructions are stored for implementing the methods executed by the Internet of Things device, core network network element, AF or reader / writer in the above-mentioned method embodiments.

[0365] The present application also provides a computer program product comprising instructions, which, when executed by a computer, implement the methods performed by an IoT device, a core network element, an AF, or a reader / writer in the above-mentioned method embodiments.

[0366] The present application also provides a communication system, which includes at least one of the Internet of Things device, core network element, AF or reader / writer in the above embodiments.

[0367] The explanation of the relevant contents and beneficial effects of any of the above-mentioned devices can be referred to the corresponding method embodiments provided above, which will not be repeated here.

[0368] It is understood that the processing circuit in the embodiments of the present application can be a processor or a circuit in a processor for performing processing operations. The processor can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor can be a microprocessor or any conventional processor.

[0369] The method steps in the embodiments of the present application can be implemented by hardware or by a processor executing software instructions. The software instructions can be composed of corresponding software modules, and the software modules can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disk, mobile hard disk, compact disc read-only memory (CD-ROM) or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and storage medium can be located in an ASIC. In addition, the ASIC can be located in an IoT device, a core network element, an AF or a reader / writer. Of course, the processor and storage medium can also exist as discrete components in an IoT device, a core network element, an AF or a reader / writer.

[0370] In the above embodiments, all or part of the embodiments may be implemented using software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are performed in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device, or other programmable device. The computer program or instructions may be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions may be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium may be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; an optical medium, such as a digital video disk; or a semiconductor medium, such as a solid-state drive.

[0371] In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0372] Unless otherwise indicated, all technical and scientific terms used in the embodiments of the present application have the same meaning as those generally understood by those skilled in the art of the technical field of the application. The terms used in this application are only for the purpose of describing specific embodiments and are not intended to limit the scope of the application. It should be understood that the above are for illustration, and the examples above are only for helping those skilled in the art to understand the embodiments of the present application, rather than limiting the application embodiments to the specific numerical values ​​or specific scenarios illustrated. Those skilled in the art can obviously carry out various equivalent modifications or changes based on the examples given above, and such modifications and changes also fall within the scope of the embodiments of the present application.

Claims

1. A data collection method, characterized in that: The method comprises: The first Internet of Things device receives first information from the reader / writer, where the first information is used to instruct the first Internet of Things device to collect sensor data, and the first information is carried in a first excitation signal, a first selection command, a downlink signaling in a first random access process, a first registration message, or a downlink signaling in a first security authentication process, and the first registration message is used to indicate that the first Internet of Things device has successfully registered with a core network element; The first IoT device collects first sensor data according to the first information; The first Internet of Things device sends the first sensing data to the reader / writer.

2. The method according to claim 1, characterized in that The downlink signaling in the first random access process includes a query command and / or a confirmation command; and / or, The first registration message is a registration acceptance message or a registration response message; and / or, The downlink signaling in the first security authentication process includes an authentication success message and / or an authentication request message.

3. The method according to claim 1 or 2, characterized in that: The first information is carried in the first excitation signal, the first selection command, or downlink signaling in the first random access process; The first sensing data is carried in a second registration message, uplink signaling in the first security authentication process, or uplink signaling related to service transmission, and the second registration message is used to request registration with the core network element.

4. The method according to claim 1 or 2, characterized in that: The first information is carried in the first registration message or in downlink signaling in the first security authentication process; The first sensing data is carried in uplink signaling related to service transmission.

5. The method according to any one of claims 1 to 4, characterized in that The method further includes: the first IoT device receiving second information from the reader / writer, where the second information is used to instruct the first IoT device to report sensor data; The first IoT device sends the first sensor data to the reader / writer, including: the first IoT device sends the first sensor data to the reader / writer according to the second information; The first information is carried in the first excitation signal, the first selection command, the downlink signaling in the first random access process, or the downlink signaling in the first security authentication process, and the second information is carried in the first registration message.

6. The method according to any one of claims 1 to 5, characterized in that After sending the first sensing data, the method further includes: The first Internet of Things device receives the first information from the reader; The first IoT device collects and caches second sensor data according to the first information; The first IoT device receives second information, where the second information is used to instruct the first IoT device to report sensor data, and the second information is carried in a second excitation signal, a second selection command, or downlink signaling in a second random access process, where the second excitation signal is used to power the IoT device to be counted, and the second selection command is used to select the IoT device to be counted; The first IoT device sends a third registration message to the reader / writer according to the second information, where the third registration message is used to request registration with the core network element, and the third registration message includes the second sensing data; After sending the second sensing data, the first Internet of Things device receives the first information from the reader / writer.

7. The method according to any one of claims 1 to 6, characterized in that The method further comprises: The first Internet of Things device receives third information from the reader / writer, where the third information is used to instruct the first Internet of Things device to send feedback information when the sensor data collection is not completed, and the feedback information is used to instruct to maintain a communication connection with the first Internet of Things device.

8. The method according to claim 7, characterized in that The third information and the first information are carried in the same signaling; or, The first information is carried in the first excitation signal, the first selection command, the downlink signaling in the first random access process, or the downlink signaling in the first security authentication process, and the third information is carried in the first registration message.

9. The method according to any one of claims 1 to 6, characterized in that The first Internet of Things device completes the collection of the first sensor data after a first period of time; The first Internet of Things device sends the first sensor data to the reader / writer, including: the first Internet of Things device re-establishes a communication connection with the reader / writer, and sends the first sensor data to the reader / writer on the communication connection.

10. The method according to any one of claims 1 to 9, characterized in that The first excitation signal is used to power the IoT device to be counted, the first selection command is used to select the IoT device to be counted, and the first IoT device belongs to the IoT device to be counted.

11. A data collection method, characterized in that: The method comprises: The core network element receives a data request message from the application function element, where the data request message is used to request sensor data of an IoT device to be inventoried, where the IoT device to be inventoried includes a first IoT device; The core network element sends first information to the reader / writer according to the data request message, where the first information is used to instruct the first Internet of Things device to collect sensor data, and the first information is carried in a first inventory request message, a first registration message, or a downlink signaling in a first security authentication process, where the first registration message is used to indicate that the first Internet of Things device has successfully registered with the core network element; The core network element receives the first sensor data of the first Internet of Things device from the reader / writer; The core network element sends the first sensing data to the application function network element.

12. The method according to claim 11, characterized in that The first registration message is a registration acceptance message or a registration response message; and / or, The downlink signaling in the first security authentication process includes an authentication success message and / or an authentication request message.

13. The method according to claim 11 or 12, characterized in that: The first information is carried in the first inventory request message; The first sensing data is carried in a second registration message, uplink signaling in the first security authentication process, or uplink signaling related to service transmission, and the second registration message is used to request registration with the core network element.

14. The method according to claim 11 or 12, characterized in that: The first information is carried in the first registration message or in downlink signaling in the first security authentication process; The first sensing data is carried in uplink signaling related to service transmission.

15. The method according to any one of claims 11 to 14, characterized in that The method further comprises: The core network element sends second information to the reader / writer, where the second information is used to instruct the first IoT device to report sensor data; The first information is carried in the first inventory request message, and the second information is carried in the first registration message.

16. The method according to any one of claims 11 to 15, characterized in that The data request message includes period information, where the period information is used to indicate a period for taking inventory of the IoT device to be taken inventory; the first information and the first sensing data are transmitted within a first period; The method further comprises: In the second cycle, the core network network element sends the first information to the reader / writer through a second inventory request message or a fourth registration message, and the fourth registration message is used to indicate that the first Internet of Things device has been successfully registered with the core network network element.

17. The method according to any one of claims 11 to 15, characterized in that The data request message includes period information, where the period information is used to indicate a period for taking inventory of the IoT device to be taken inventory; the first information and the first sensing data are transmitted within a first period; The method further comprises: After receiving the first sensing data, the core network element sends the first information to the reader / writer within the first period; In the second cycle, the core network network element sends second information to the reader / writer through a second inventory request message, where the second information is used to instruct the first IoT device to report sensor data; the core network network element receives second sensor data of the first IoT device from the reader / writer, where the second sensor data is carried in a third registration message, and the third registration message is used to request registration with the core network network element; after receiving the second sensor data, the core network network element sends the first information to the reader / writer.

18. The method according to any one of claims 11 to 17, characterized in that The data request message includes a first data amount, where the first data amount is a data amount that triggers the core network element to report the sensor data to the application function network element; The core network network element sends the first sensor data to the application function network element, including: when the sensor data cached in the core network network element reaches the first data volume, the core network network element sends the sensor data cached by the core network network element to the application function network element, and the sensor data cached by the core network network element includes the first sensor data.

19. The method according to any one of claims 11 to 18, characterized in that The method further comprises: The core network element sends third information to the reader / writer, where the third information is used to instruct the first Internet of Things device to send feedback information when the sensor data collection is not completed, and the feedback information is used to instruct to maintain the communication connection with the first Internet of Things device.

20. The method according to claim 19, characterized in that The third information and the first information are carried in the same signaling; or, The first information is carried in the first inventory request message or in downlink signaling in the first security authentication process, and the third information is carried in the first registration message.

21. The method according to any one of claims 11 to 20, characterized in that The method further includes: within a first time period, the core network element does not receive the first sensing data from the reader; after the first time period, the core network element disconnects the communication connection for the first IoT device and sends fifth information to the reader, the fifth information being used to instruct to take inventory of the next IoT device; The core network network element receives the first sensor data of the first Internet of Things device from the reader / writer, including: the core network network element re-establishes a communication connection with the first Internet of Things device, and receives the first sensor data on the communication connection.

22. A data collection method, characterized in that: The method comprises: The application function network element determines a data request message, where the data request message is used to request sensor data of the Internet of Things device to be inventoried, and the data request message includes one or more of the following information: period information, cached data volume, or indication information, where the period information is used to indicate a period for inventorying the Internet of Things device to be inventoried, the cached data volume is a data volume for triggering a core network network element to report sensor data to the application function network element, and the indication information is used to indicate signaling that carries first information, where the first information is used to instruct a first Internet of Things device to collect sensor data, and the first Internet of Things device belongs to the Internet of Things device to be inventoried; The application function network element sends the data request message to the core network element.

23. The method according to claim 22, characterized in that The signaling carrying the first information is an inventory request message, a registration message, or downlink signaling in a security authentication process, and the registration message is used to indicate that the first Internet of Things device has successfully registered with the core network element.

24. A data collection method, characterized in that: include: The reader receives first information from a core network element, where the first information is used to instruct a first Internet of Things device to collect sensor data; The reader / writer sends the first information to the first Internet of Things device; The reader / writer receives first sensor data from the first IoT device; The reader / writer sends the first sensing data to the core network element; wherein the first information is carried in the downlink signaling sent before the first Internet of Things device is registered with the core network element.

25. The method according to claim 24, characterized in that The first information received by the reader is carried in a first inventory request message; The first information sent by the reader is carried in a first excitation signal, a first selection command, or downlink signaling in a first random access process; The first sensing data is carried in a second registration message, uplink signaling in a first security authentication process, or uplink signaling related to service transmission, and the second registration message is used to request registration with the core network element.

26. The method according to claim 24 or 25, characterized in that The first information is carried in a first registration message or a downlink signaling in a first security authentication process; The first sensing data is carried in uplink signaling related to service transmission.

27. The method according to any one of claims 24 to 26, characterized in that The method further comprises: The reader / writer receives second information from the core network element, where the second information is used to instruct the first IoT device to report sensor data; The reader / writer sends the second information to the first Internet of Things device; wherein the first information received by the reader / writer is carried in a first inventory request message, the first information sent by the reader / writer is carried in a first excitation signal, a first selection command, a downlink signaling in a first random access process, or a downlink signaling in a first security authentication process, and the second information is carried in a first registration message.

28. The method according to any one of claims 24 to 27, characterized in that After sending the first sensing data, the method further includes: The reader receives the first information from the core network element, and sends the first information to the first Internet of Things device; The reader / writer receives second information from the core network element, where the second information is used to instruct the first IoT device to report sensor data, and the second information is carried in a second inventory request message; The reader / writer sends the second information to the first IoT device through a second excitation signal, a second selection command, or downlink signaling in a second random access process, wherein the second excitation signal is used to power the IoT device to be counted, and the second selection command is used to select the IoT device to be counted; The reader / writer receives a third registration message from the first IoT device, where the third registration message is used to request registration with the core network element, and the third registration message includes second sensor data; The reader / writer sends the third registration message to the core network element; After sending the third registration message, the reader receives the first information from the core network element and sends the first information to the first Internet of Things device.

29. The method according to any one of claims 24 to 28, characterized in that The method further comprises: The reader receives third information from the core network element, where the third information is used to instruct the first IoT device to send feedback information when the sensor data collection is not completed, and the feedback information is used to instruct to maintain a communication connection with the first IoT device; The reader / writer sends the third information to the first Internet of Things device.

30. The method according to claim 29, characterized in that The third information and the first information are carried in the same signaling; or, the first information received by the reader is carried in a first inventory request message, the first information sent by the reader is carried in a first excitation signal, a first selection command, and a downlink signaling in a first random access process, and the third information is carried in a first registration message.

31. The method according to claim 29 or 30, characterized in that The third information is also used to indicate a period for sending the feedback information.

32. The method according to any one of claims 29 to 31, characterized in that The method further comprises: The reader / writer receives one or more feedback information from the first IoT device, and sends the one or more feedback information to the core network element.

33. The method according to any one of claims 24 to 28, characterized in that The method further comprises: Within a first time period, the reader / writer does not receive the first sensing data from the reader / writer; After the first time period, the reader / writer disconnects the communication connection with the first IoT device, and receives fifth information from the core network element, where the fifth information is used to instruct to take inventory of the next IoT device; The reader receives the first sensor data from the first IoT device, including: The reader / writer re-establishes a communication connection with the first IoT device and receives the first sensing data over the communication connection.

34. The method according to claim 33, characterized in that The method further comprises: The core network element starts a first timer, where the timing duration of the first timer is the first duration; Before receiving the fifth information, the reader / writer sends sixth information to the core network element, where the sixth information is used to request an inventory of the next IoT device.

35. The method according to claim 33 or 34, characterized in that The method further comprises: The reader / writer receives fourth information from the core network element, where the fourth information is used to indicate the first duration.

36. The method according to any one of claims 33 to 35, characterized in that The method further comprises: The reader / writer sends the fourth information to the first Internet of Things device.

37. A communication system, characterized in that: Includes at least one of the following devices: A communication device for performing the method according to any one of claims 1 to 10; A communication device for performing the method according to any one of claims 11 to 21; or, A communication device for performing the method according to any one of claims 22 to 23; or, A communication device for performing the method according to any one of claims 24 to 36.

38. A communication device, characterized in that: The method comprises a module or a unit for executing the method as claimed in any one of claims 1 to 36.

39. A communication device, characterized in that: include: A processing circuit and a memory, the memory being used to store a computer program or instructions, the processing circuit being used to execute the computer program or the instructions stored in the memory, so that the apparatus performs the method according to any one of claims 1 to 36.

40. The device according to claim 39, characterized in that The device is a chip.

41. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program or instructions, and when the computer program or instructions are executed on a computer, the computer is caused to execute the method according to any one of claims 1 to 36.

42. A computer program product, characterized in that The computer program product comprises instructions for performing the method of any one of claims 1 to 36.

Images