Communication method and communication apparatus

Abstract

The present application relates to the field of communications, and discloses a communication method and a communication apparatus, which can be applied to a communication scenario of an ambient Internet of Things. The communication method comprises: sending a command request NAS PDU to an Internet of Things device; and if no command response NAS PDU from the Internet of Things device is received, performing at least one of the following: triggering an inventory service for the Internet of Things device, triggering a command service for the Internet of Things device, and sending first Internet of Things device information and a response failure cause to an AIOTF network element. The method can, when an Internet of Things device fails to respond, increase the success rate of a response of the Internet of Things device, and improve the service quality of a command service.

Description

Communication methods and communication devices

[0001] This application claims priority to Chinese Patent Application No. 202510392767.1, filed with the State Intellectual Property Office of China on March 28, 2025, entitled "A Method, Terminal and System for Inter-Node Communication Processing", and Chinese Patent Application No. 202510578982.0, filed with the State Intellectual Property Office of China on May 6, 2025, entitled "Communication Method and Communication Device", the entire contents of which are incorporated herein by reference. Technical Field

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

[0003] In IoT communication systems, to improve the sustainability and performance of wireless communication and reduce its power consumption, low-power ambient internet of things (AIoT) technology has been introduced. This includes IoT devices, AIoT readers, and AIoT functions (AIOTF) network elements. An AIoT reader is responsible for communication between IoT devices and radio access network (RAN) devices, or between IoT devices and core network (CN) devices. The AIoT reader can communicate with IoT devices, for example, reading data from them and sending the communication results to core network or RAN devices. AIOTF network elements are used to manage the AIoT system and provide AIoT-related services and capabilities.

[0004] After the AIOTF network element sends a message to the IoT device through the AIoT reader, in abnormal communication scenarios, such as when the IoT device runs out of power, malfunctions, or the signal is blocked between the IoT device and the AIoT reader, the IoT device may fail to respond. Neither the AIoT reader nor the AIOTF network element will perform any further processing, and communication between the AIOTF network element and the IoT device will fail. Summary of the Invention

[0005] This application provides a communication method and a communication device to improve the success rate of IoT device responses and enhance the service quality and reliability of command services in the event of IoT device response failure.

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

[0007] Firstly, a communication method is provided. This method can be executed by an AIoT reader, or by a component (such as a circuit, chip, or chip system) configured in the AIoT reader, or by a logic module or software capable of implementing all or part of the functions of the AIoT reader. This application does not limit the scope of this method. The following description uses an AIoT reader as an example.

[0008] The method includes: sending a command request for a non-access stratum protocol data unit (NAS PDU) to an IoT device; if no command response NAS PDU is received from the IoT device, then performing at least one of the following: triggering an inventory service for the IoT device, triggering a command service for the IoT device, and sending first IoT device information and a response failure reason to the AIOTF network element of the environment IoT function, wherein the first IoT device information is used to instruct the IoT device when the AIoT reader communicates with the AIOTF network element.

[0009] The communication method provided in this application embodiment, for command services, in the event of an IoT device failure to respond, triggers an AIoT reader or AIOTF network element to execute an inventory service or command service on the IoT device that failed to respond, attempting to restore communication with the IoT device that failed to respond, which helps to improve the success rate of IoT device responses and improve the service quality of command services.

[0010] In one possible implementation, triggering an inventory service for an IoT device includes sending a reader-to-device (R2D) message to the IoT device, the R2D message including second IoT device information used to instruct the IoT device when the AIoT reader communicates with the IoT device.

[0011] The second IoT device information indicates the IoT device that failed to respond, that is, it triggers the execution of inventory service for the single IoT device that failed to respond, instead of performing inventory service for all IoT devices, thereby reducing the power consumption of IoT devices, AIoT readers, and AIOTF network elements and saving signaling overhead.

[0012] In one possible implementation, triggering the execution of a command service on an IoT device includes: sending an R2D message to the IoT device, the R2D message including a command request NAS PDU and second IoT device information, the second IoT device information being used to instruct the IoT device when the AIoT reader communicates with the IoT device.

[0013] The second IoT device information indicates the IoT device that failed to respond, that is, it triggers the execution of command service for the single IoT device that failed to respond, instead of executing command service for all IoT devices, thereby reducing the power consumption of IoT devices, AIoT readers, and AIOTF network elements and saving signaling overhead.

[0014] In one possible implementation, the second IoT device information is the IoT device's access stratum (AS) identifier or inventory result NAS PDU.

[0015] Regarding the AS identifier, since AIoT readers and IoT devices communicate through the AIoT AS layer, and different IoT devices have different AS identifiers, both IoT devices and AIOTF network elements can identify IoT devices based on the AS identifier. Regarding the inventory result NAS PDU, because IoT devices have a NAS layer, the inventory result NAS PDU can be parsed to obtain the IoT device identifier, thus identifying the IoT device. For the AIoT reader, when performing the inventory service before executing command services, the AIoT reader can obtain and cache the inventory result NAS PDU from the IoT device. If the AIoT reader receives an inventory result NAS PDU from the IoT device during command service execution, it can match it with the cached inventory result NAS PDU of the IoT device. If a match is found, the corresponding IoT device can be identified.

[0016] In one possible implementation, after sending the first IoT device information and the response failure reason to the AIOTF network element, the method further includes: receiving a command request NAS PDU and the first IoT device information from the AIOTF network element.

[0017] After an IoT device sends a response failure reason to the AIOTF network element, the AIOTF network element triggers the execution of a command service for the IoT device. The command service can be triggered for a single IoT device (e.g., the IoT device that failed to respond) using the first IoT device information, eliminating the need to execute command services for all IoT devices. This reduces power consumption and signaling overhead for the IoT device, AIoT reader, and AIOTF network element. Because the AIOTF network element has a NAS layer, it can parse NAS PDUs (e.g., inventory NAS PDUs, command response NAS PDUs) to obtain the IoT device identifier. However, the AIoT reader lacks a NAS layer and cannot parse NAS PDUs (e.g., inventory result NAS PDUs, command response NAS PDUs) to obtain the IoT device identifier. Therefore, the AIoT reader cannot determine the IoT device based on the IoT device identifier; instead, it needs to use the first IoT device information to identify the IoT device.

[0018] In one possible implementation, the first IoT device information is identified by the Next Generation Application Protocol (NGAP).

[0019] The NGAP identifier can be a RAN NGAP device ID, a CN NGAP device ID, or an AIOTF NGAP device ID. It should be noted that the NGAP identifier sent by the AIoT reader to the AIOTF network element may not be the same as the NGAP identifier sent by the AIOTF network element to the AIoT reader, but they can be bound together. For example, the NGAP identifier sent by the AIoT reader to the AIOTF network element may be the RAN NGAP device ID, while the NGAP identifier sent by the AIOTF network element to the AIoT reader may be the core network NGAP device ID or the AIOTF NGAP device ID. For simplicity, this application does not distinguish between NGAP identifiers. Regarding the NGAP identifier, the AIoT reader and the AIOTF network element communicate through the NGAP layer, and different IoT devices correspond to different NGAP identifiers. Therefore, both the AIoT reader and the AIOTF network element can identify IoT devices based on the NGAP identifier.

[0020] In one possible implementation, the method further includes: receiving service level information from an AIOTF network element, the service level information being used to indicate the reliability level of the command service; and performing at least one of the following based on the service level information: triggering an inventory service for the IoT device, triggering a command service for the IoT device, and sending first IoT device information and a response failure reason to the AIOTF network element.

[0021] Service level information indicates that the higher the reliability level of the command service, the more operations are performed, the higher the success rate of IoT device responses, and the higher the service quality of the command service. Conversely, the lower the reliability level of the command service, the fewer operations IoT devices, AIoT readers, and AIOTF network elements perform, and the lower the power consumption.

[0022] In one possible implementation, at least one of the following is performed based on the service level information: triggering an inventory service for the IoT device, triggering a command service for the IoT device, and sending first IoT device information and a response failure reason to the AIOTF network element, including: if the service level information indicates that the reliability level of the command service is low, then sending the first IoT device information and a response failure reason to the AIOTF network element; if the service level information indicates that the reliability level of the command service is medium, then triggering an inventory service for the IoT device, or triggering a command service for the IoT device; if the service level information indicates that the reliability level of the command service is high, then triggering an inventory service for the IoT device, and triggering a command service for the IoT device.

[0023] Service level information indicates that the higher the reliability level of the command service, the more operations are performed, the higher the success rate of IoT device responses, and the higher the service quality of the command service. Conversely, the lower the reliability level of the command service, the fewer operations IoT devices, AIoT readers, and AIOTF network elements perform, and the lower the power consumption.

[0024] In one possible implementation, before sending a command request NAS PDU to the IoT device, the method further includes: sending an inventory report message to the AIOTF network element, the inventory report message including information about the first IoT device. This is to inform the AIOTF network element of the information about the first IoT device in advance.

[0025] Secondly, a communication method is provided. This method can be executed by an AIOTF network element, or by a component (such as a circuit, chip, or chip system) configured in the AIOTF network element, or by a logic module or software capable of implementing all or part of the functions of the AIOTF network element. This application does not limit this approach. The following description uses an AIOTF network element as an example.

[0026] The method includes: sending a command request NAS PDU to an AIoT reader; in response to receiving first IoT device information and a response failure reason from the AIoT reader, or in response to not receiving first IoT device information and a command response NAS PDU from the AIoT reader within a preset time, performing at least one of the following: triggering an inventory service for the IoT device, triggering a command service for the IoT device, and sending an IoT device identifier and a response failure indication message to the application function AF network element.

[0027] In one possible implementation, triggering an inventory service for an IoT device includes: sending an inventory request message to an AIoT reader, the inventory request message including the IoT device identifier.

[0028] In one possible implementation, triggering the execution of a command service on an IoT device includes sending a command request message to an AIoT reader, the command request message including a command request NAS PDU and information about the first IoT device.

[0029] In one possible implementation, the first IoT device information is a next-generation application protocol identifier.

[0030] In one possible implementation, the method further includes sending service level information to the AIoT reader, the service level information being used to indicate the reliability level of the command service.

[0031] In one possible implementation, before sending a command request NAS PDU to the AIoT reader, the method further includes: receiving an inventory report message from the AIoT reader, the inventory report message including information about the first IoT device.

[0032] The second aspect and any of its implementations are implementations of the AIOTF network elements corresponding to the first aspect and any of its implementations. The explanations, supplements and descriptions of the beneficial effects of the first aspect and any of its implementations also apply to the second aspect and any of its implementations, and will not be repeated here.

[0033] Thirdly, a communication method is provided, which can be executed by an AIoT reader, or by a component (such as a circuit, chip, or chip system) configured in the AIoT reader, or by a logic module or software capable of implementing all or part of the functions of the AIoT reader. This application does not limit this approach. The following description uses an AIoT reader as an example.

[0034] The method includes: receiving a command request NAS PDU and first IoT device information from an AIOTF network element, the first IoT device information being used to instruct the IoT device when the AIoT reader communicates with the AIOTF network element; and sending a command request NAS PDU and second IoT device information to the IoT device, the second IoT device information being used to instruct the IoT device when the AIoT reader communicates with the IoT device.

[0035] In the command service process, IoT devices do not need to parse the command request NAS PDU in the R2D message to obtain the IoT device identifier and determine whether the R2D message was sent to them. Instead, they can determine that the R2D message was sent to them based on the second IoT device information in the R2D message, thereby reducing the power consumption of IoT devices.

[0036] In one possible implementation, the method further includes: receiving a command response NAS PDU from an IoT device and information about the second IoT device; and sending the command response NAS PDU and information about the first IoT device to the AIOTF network element.

[0037] An AIoT reader can bind information about a first IoT device and information about a second IoT device. That is, the AIoT reader can determine the information about a second IoT device through the information about the first IoT device, or determine the information about a first IoT device through the information about the second IoT device, based on the binding relationship between the two.

[0038] In one possible implementation, before receiving the command request NAS PDU and the first IoT device information from the AIOTF network element, the method further includes: sending an inventory report message to the AIOTF network element, the inventory report message including the first IoT device information.

[0039] In one possible implementation, the first IoT device information is a next-generation application protocol identifier.

[0040] The NGAP identifier can be a RAN NGAP device ID, a CN NGAP device ID, or an AIOTF NGAP device ID. It should be noted that the NGAP identifier sent by the AIoT reader to the AIOTF network element may not be the same as the NGAP identifier sent by the AIOTF network element to the AIoT reader, but they can be bound together. For example, the NGAP identifier sent by the AIoT reader to the AIOTF network element may be the RAN NGAP device ID, while the NGAP identifier sent by the AIOTF network element to the AIoT reader may be the core network NGAP device ID or the AIOTF NGAP device ID. For simplicity, this application does not distinguish between NGAP identifiers. Regarding the NGAP identifier, the AIoT reader and the AIOTF network element communicate through the NGAP layer, and different IoT devices correspond to different NGAP identifiers. Therefore, both the AIoT reader and the AIOTF network element can identify IoT devices based on the NGAP identifier.

[0041] In one possible implementation, the second IoT device information is the IoT device's access layer identifier or inventory result NAS PDU.

[0042] Regarding the AS identifier, since AIoT readers and IoT devices communicate through the AIoT AS layer, and different IoT devices have different AS identifiers, both IoT devices and AIOTF network elements can identify IoT devices based on the AS identifier. Regarding the inventory result NAS PDU, because IoT devices have a NAS layer, the inventory result NAS PDU can be parsed to obtain the IoT device identifier, thus identifying the IoT device. For the AIoT reader, when performing the inventory service before executing command services, the AIoT reader can obtain and cache the inventory result NAS PDU from the IoT device. If the AIoT reader receives an inventory result NAS PDU from the IoT device during command service execution, it can match it with the cached inventory result NAS PDU of the IoT device. If a match is found, the corresponding IoT device can be identified.

[0043] Fourthly, a communication method is provided, which can be executed by an AIOTF network element, or by a component (such as a circuit, chip, or chip system) configured in the AIOTF network element, or by a logic module or software capable of implementing all or part of the functions of the AIOTF network element. This application does not limit this approach. The following description uses an AIOTF network element as an example.

[0044] The method includes: sending a command request NAS PDU and first IoT device information to an AIoT reader, the first IoT device information being used to instruct the IoT device when the AIoT reader communicates with an AIOTF network element; and receiving a command response NAS PDU and first IoT device information from the AIoT reader.

[0045] In one possible implementation, sending a command request to the AIoT reader to request the NAS PDU and the first IoT device information further includes: receiving an inventory report message from the AIoT reader, the inventory report message including the first IoT device information.

[0046] In one possible implementation, the first IoT device information is a next-generation application protocol identifier.

[0047] The fourth aspect and any of its implementations are implementations of the AIOTF network elements corresponding to the second aspect and any of its implementations. The explanations, supplements and descriptions of the beneficial effects of the first aspect and any of its implementations also apply to the second aspect and any of its implementations, and will not be repeated here.

[0048] Fifthly, a communication device is provided, comprising a communication module. The communication module is used to send a command request NAS PDU to an Internet of Things (IoT) device. If no command response NAS PDU is received from the IoT device, at least one of the following is performed: triggering an inventory service on the IoT device; triggering a command service on the IoT device; sending first IoT device information and a response failure reason to an AIoT Function (AIOTF) network element, wherein the first IoT device information is used to instruct the IoT device when the AIoT reader communicates with the AIOTF network element.

[0049] In one possible implementation, the communication module is used to send an R2D message to an IoT device, the R2D message including second IoT device information, the second IoT device information being used to instruct the IoT device when the AIoT reader communicates with the IoT device.

[0050] In one possible implementation, the communication module is used to send an R2D message to an IoT device. The R2D message includes a command request NAS PDU and second IoT device information. The second IoT device information is used to instruct the IoT device when the AIoT reader communicates with the IoT device.

[0051] In one possible implementation, the second IoT device information is the IoT device's access layer identifier or inventory result NAS PDU.

[0052] In one possible implementation, the communication module is used to receive a command request NAS PDU and the first IoT device information from the AIOTF network element after sending the first IoT device information and the response failure reason to the AIOTF network element.

[0053] In one possible implementation, the first IoT device information is a next-generation application protocol identifier.

[0054] In one possible implementation, the communication module is used to receive service level information from the AIOTF network element, the service level information being used to indicate the reliability level of the command service; and to perform at least one of the following based on the service level information: triggering an inventory service for the IoT device, triggering a command service for the IoT device, and sending first IoT device information and a response failure reason to the AIOTF network element.

[0055] In one possible implementation, the communication module is configured to send first IoT device information and a response failure reason to the AIOTF network element if the service level information indicates that the reliability level of the command service is low; if the service level information indicates that the reliability level of the command service is medium, trigger an inventory service to be performed on the IoT device, or trigger a command service to be performed on the IoT device; if the service level information indicates that the reliability level of the command service is high, trigger an inventory service to be performed on the IoT device, and trigger a command service to be performed on the IoT device.

[0056] In one possible implementation, the communication module is used to send an inventory report message to the AIOTF network element before sending a command request NAS PDU to the IoT device. The inventory report message includes information about the first IoT device.

[0057] Sixthly, a communication device is provided, comprising a communication module. The communication module is configured to send a command request NAS PDU to an AIoT reader; in response to receiving first IoT device information and a response failure reason from the AIoT reader, or in response to not receiving first IoT device information and a command response NAS PDU from the AIoT reader within a preset time, perform at least one of the following: triggering an inventory service for the IoT device, triggering a command service for the IoT device, and sending an IoT device identifier and a response failure indication message to the application function AF network element.

[0058] In one possible implementation, the communication module is used to send an inventory request message to the AIoT reader, the inventory request message including the IoT device identifier.

[0059] In one possible implementation, the communication module is used to send a command request message to the AIoT reader, the command request message including a command request NAS PDU and information about the first IoT device.

[0060] In one possible implementation, the first IoT device information is a next-generation application protocol identifier.

[0061] In one possible implementation, the communication module is used to send service level information to the AIoT reader, the service level information being used to indicate the reliability level of the command service.

[0062] In one possible implementation, the communication module is configured to receive an inventory report message from the AIoT reader before sending a command request NAS PDU to the AIoT reader. The inventory report message includes information about the first IoT device.

[0063] In a seventh aspect, a communication device is provided, comprising a communication module. The communication module is configured to receive a command request NAS PDU and first IoT device information from an AIOTF network element, the first IoT device information being used to instruct the IoT device when an AIoT reader communicates with the AIOTF network element; and to send a command request NAS PDU and second IoT device information to the IoT device, the second IoT device information being used to instruct the IoT device when the AIoT reader communicates with the IoT device.

[0064] In one possible implementation, the communication module is used to receive command response NAS PDU from the IoT device and information from the second IoT device; and to send command response NAS PDU and information from the first IoT device to the AIOTF network element.

[0065] In one possible implementation, the communication module is used to send an inventory report message to the AIOTF network element, the inventory report message including information about the first IoT device.

[0066] In one possible implementation, the first IoT device information is a next-generation application protocol identifier.

[0067] In one possible implementation, the second IoT device information is the IoT device's access layer identifier or inventory result NAS PDU.

[0068] Eighthly, a communication device is provided, comprising a communication module. The communication module is used to send a command request NAS PDU and first IoT device information to an AIoT reader, the first IoT device information being used to instruct the IoT device when the AIoT reader communicates with an AIOTF network element; and to receive a command response NAS PDU and the first IoT device information from the AIoT reader.

[0069] In one possible implementation, the communication module is used to receive inventory report messages from the AIoT reader, the inventory report messages including information about the first IoT device.

[0070] In one possible implementation, the first IoT device information is a next-generation application protocol identifier.

[0071] The fifth and sixth aspects are device-side implementations corresponding to the first and second aspects, and the seventh and eighth aspects are device-side implementations corresponding to the third and fourth aspects. The explanations, supplements, and descriptions of beneficial effects regarding the first aspect and any of its embodiments, and the third aspect and any of its embodiments, also apply to the fifth to eighth aspects and any of their embodiments, and will not be repeated here.

[0072] A ninth aspect provides a communication device including a processor. The processor is coupled to a memory and can be used to execute instructions or data in the memory to implement the methods of the first aspect, the third aspect, and any implementation thereof. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, and the processor is coupled to the communication interface.

[0073] In one implementation, the communication interface may be a transceiver, or an input / output interface.

[0074] In another implementation, the communication device is a chip configured in a network device. When the communication device is a chip configured in a network device, the communication interface can be an input / output interface.

[0075] In a tenth aspect, a communication device is provided, including a processor. The processor is coupled to a memory and can be used to execute instructions or data in the memory to implement the methods of the second aspect, the fourth aspect, and any implementation thereof described above. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, and the processor is coupled to the communication interface.

[0076] In one implementation, the communication interface may be a transceiver, or an input / output interface.

[0077] In another implementation, the communication device is a chip configured in a terminal device. When the communication device is a chip configured in a terminal device, the communication interface can be an input / output interface.

[0078] Eleventhly, a processor is provided, comprising: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive signals through the input circuit and transmit signals through the output circuit, causing the processor to execute the method of any possible implementation of the first to fourth aspects described above.

[0079] In specific implementation, the processor can be one or more chips, the input circuit can be input pins, the output circuit can be output pins, and the processing circuit can be transistors, gate circuits, flip-flops, and various logic circuits. The input signal received by the input circuit can be received and input by, for example, but not limited to, a receiver, and the signal output by the output circuit can be, for example, but not limited to, output to and transmitted by a transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, which is used as both the input circuit and the output circuit at different times. This application does not limit the specific implementation of the processor and various circuits.

[0080] In a twelfth aspect, a communication device is provided, comprising a processor and a memory. The processor is configured to read instructions stored in the memory, receive signals via a receiver, and transmit signals via a transmitter to execute the methods of any possible implementation of the first to fourth aspects described above.

[0081] Optionally, the processor may be one or more, and the memory may be one or more.

[0082] In a thirteenth aspect, a computer program product is provided, the computer program product comprising: a computer program (also referred to as code or instructions), which, when the computer program is run, causes a computer to perform the methods in any of the possible implementations of the first to fourth aspects described above.

[0083] In a fourteenth aspect, a computer-readable storage medium is provided that stores a computer program (also referred to as code or instructions) that, when run on a computer, causes the computer to perform the methods of any possible implementation of the first to fourth aspects described above.

[0084] In a fifteenth aspect, embodiments of this application provide a chip system including one or more processors for calling and executing instructions stored in memory, causing the methods in any of the possible implementations of the first to fourth aspects to be executed. The chip system may be composed of chips or may include chips and other discrete devices.

[0085] The chip system may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.

[0086] In a sixteenth aspect, a communication system is provided, including the aforementioned communication devices, such as an AIoT reader and an AIOTF network element. Optionally, the communication system may further include other devices that communicate with the AIoT reader and the AIOTF network element.

[0087] The technical effects of aspects nine through sixteen refer to the technical effects of aspect one and any of its embodiments, and aspect three and any of its embodiments, and will not be repeated here. Attached Figure Description

[0088] Figure 1 is a schematic diagram of the architecture of a communication system provided in an embodiment of this application;

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

[0090] Figure 3 is a schematic diagram of the structure of a RAN device provided in an embodiment of this application;

[0091] Figure 4 is a schematic diagram of the structure of a core network element provided in an embodiment of this application;

[0092] Figure 5 is a schematic diagram of the structure of an Internet of Things (IoT) device provided in an embodiment of this application;

[0093] Figure 6 is a schematic diagram of a control plane protocol stack of topology 1 provided in an embodiment of this application;

[0094] Figure 7 is a schematic diagram of the control plane protocol stack of another topology 1 provided in the embodiment of this application;

[0095] Figure 8 is a schematic diagram of a control plane protocol stack for a topology 2 provided in an embodiment of this application;

[0096] Figure 9 is a schematic diagram of a user plane protocol stack of topology 2 provided in an embodiment of this application;

[0097] Figure 10 is a schematic diagram of an inventory service process provided in an embodiment of this application;

[0098] Figure 11 is a schematic diagram of a command service flow provided in an embodiment of this application;

[0099] Figure 12 is a schematic diagram of the first communication method provided in the embodiment of this application;

[0100] Figure 13 is a schematic diagram of the second communication method provided in the embodiments of this application;

[0101] Figure 14 is a schematic diagram of the third communication method provided in the embodiments of this application;

[0102] Figure 15 is a schematic diagram of the fourth communication method provided in the embodiments of this application;

[0103] Figure 16 is a schematic diagram of the fifth communication method provided in the embodiments of this application;

[0104] Figure 17 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0105] Figure 18 is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

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

[0107] First, some concepts involved in this application will be described.

[0108] The terms "first" and "second" used in the embodiments of this application are only used to distinguish features of the same type and should not be construed as indicating relative importance, quantity, order, etc.

[0109] The terms "exemplary" or "for example" used in the embodiments of this application are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0110] The technical solutions provided in this application can be applied to various communication systems, such as: Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, sidelink communication systems, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication systems, non-terrestrial network (NTN) communication systems, 5th generation (5G) mobile communication systems, new radio access technology (NR), future communication systems, and 5G Advanced communication systems. Among these, 5G mobile communication systems may include non-standalone (NSA) and / or standalone (SA) networking. The technical solutions provided in this application can also be applied to future communication systems. This application does not limit this application. The terms "system" and "network" in the embodiments of this application are often used interchangeably, and the described technologies can be used not only for the systems and radio technologies mentioned above, but also for other systems and radio technologies.

[0111] Figure 1 is a schematic diagram of the architecture of a communication system applied in an embodiment of this application. The communication system 100 may include: the 5th generation (5G) cellular network in the communication system mainly includes: user equipment (UE) 101, radio access network (RAN) equipment 102, data network (DN) 104, and core network elements. The core network elements include user plane function (UPF) network elements 103, access management function (AMF) network elements 105, session management function (SMF) network elements 106, authentication server function (AUSF) network elements 107, policy control function (PCF) network elements 108, application function (AF) network elements 109, network slice selection function (NSSF) network elements 110, unified data management (UDM) network elements 111, network exposure function (NEF) network elements 112, and network repository function. Network element 113 (NRF). Each network element can function as a device running proprietary hardware, or a software instance running on proprietary hardware, or a virtual function instantiated on a suitable platform, such as an implementation on a cloud infrastructure.

[0112] The main functions of each device are described in detail below.

[0113] UE 101 may include various handheld devices, in-vehicle devices, wearable devices, computing devices, or other processing devices connected to a wireless modem with wireless communication capabilities; it may also include subscriber units, cellular phones, smartphones, wireless data cards, personal digital assistant (PDA) computers, tablet computers, wireless modems, handheld devices, laptop computers, cordless phones, wireless local loop (WLL) stations, machine-type communication (MTC) terminals, mobile stations (MS), terminal devices, or relay subscriber equipment, etc. Relay subscriber equipment may, for example, be a 5G residential gateway (RG).

[0114] RAN equipment 102 may include various types of base stations, such as macro base stations, micro base stations (also known as "small stations"), relay stations, access points, and distributed unit-control units (DU-CUs). Additionally, these base stations can also be radio controllers in cloud radio access network (CRAN) scenarios, or network equipment in relay stations, access points, vehicle-mounted devices, wearable devices, or future public land mobile network (PLMN) networks. RAN equipment 102 may also include broadband network gateways (BNGs), aggregation switches, and non-3GPP access equipment.

[0115] RAN device 102 is used for functions such as radio resource management, uplink and downlink data classification, quality of service (QoS) management, data compression and encryption, signaling processing with control plane network elements, and data forwarding with user plane function network elements on the air interface side. This application embodiment does not limit the specific form and structure of RAN device 102. For example, in systems employing different radio access technologies, the name of the RAN device 102 with base station functions may differ. For example, a base station can be an evolved universal terrestrial radio access network (E-UTRAN) device in LTE, such as an evolved NodeB (eNB or e-NodeB), or a next-generation radio access network (NG-RAN) device (such as a gNB) in a 5G system.

[0116] UPF element 103 is used for packet routing and forwarding, as well as QoS processing or billing information statistics for user plane data. The transmission resources and scheduling functions that provide services to the UE in UPF element 103 are managed and controlled by SMF element 106.

[0117] DN 104 is used for networks that provide data transmission services to users. For example, DN 104 can be a carrier service network, the Internet, or a third-party service network.

[0118] AMF element 105 is used for user access and mobility management, including processing UE 101's access requests, mobility management, and radio resource allocation.

[0119] SMF element 106 is used for session management functions, such as tunnel maintenance, IP address allocation and management, UP function selection, policy enforcement and quality of service (QoS) control, billing data collection, roaming, etc.

[0120] AUSF element 107 is used for authentication servers and storing keys.

[0121] PCF network element 108 is used for user control policy management, including QoS control, service access control, etc.

[0122] AF element 109 is used to provide services to the 3GPP network, such as influencing service routing and interacting with PCF for policy control.

[0123] NSSF element 110 is used for network slice selection.

[0124] UDM network element 111 is used for user subscription data management, roaming control, etc.

[0125] The NEF element 112 is used to securely expose 5G network capabilities to third-party applications, providing standardized API interfaces for external applications to access network services, ensuring that external entities can only access authorized network functions and data, and enabling conversion between internal network protocols and external APIs.

[0126] NRF element 113 is used for service discovery and registration, enabling various network elements in the core network to dynamically discover and communicate with each other.

[0127] The communication system 100 may also include devices in the AIoT system, such as IoT device 114 and AIOTF network element 115, as detailed in the following description of the AIoT system.

[0128] Figure 2 is a schematic diagram of the structure of a UE provided in an embodiment of this application. Taking UE 101 as a mobile phone as an example, UE 101 may include: radio frequency (RF) circuit 210, memory 220, other input devices 230, display screen 240, sensor 250, audio circuit 260, I / O subsystem 270, processor 280, and power supply 290, etc. Those skilled in the art will understand that the structure shown in the figure does not constitute a limitation on UE 101, and may include more or fewer components than shown, or combine some components, or split some components, or have different component arrangements. Those skilled in the art will understand that display screen 240 belongs to user interface (UI), and display screen 240 may include display panel 241 and touch panel 242. Although not shown, UE 101 may also include functional modules or devices such as camera and Bluetooth module, which will not be described in detail here.

[0129] Furthermore, the processor 280 is connected to the RF circuit 210, memory 220, audio circuit 260, I / O subsystem 270, and power supply 290. The I / O subsystem 270 is connected to other input devices 230, display screen 240, and sensor 250. The RF circuit 200 can be used to receive and transmit signals during information transmission or calls; specifically, after receiving downlink information from network devices, it sends it to the processor 280 for processing. The memory 220 can be used to store software programs and modules. The processor 280 executes various functional applications and data processing of the UE 101 by running the software programs and modules stored in the memory 220, such as executing the methods involved in the embodiments of this application.

[0130] Other input devices 230 can be used to receive input digital or character information, and generate keyboard signal input related to user settings and function control of UE 101. Display screen 240 can be used to display information input by the user or information provided to the user, as well as various menus of UE 101, and can also accept user input. Sensor 250 can be a light sensor, motion sensor, or other sensor. Audio circuit 260 provides an audio interface between the user and UE 101. I / O subsystem 270 is used to control external input / output devices, which may include other device input controllers, sensor controllers, and display controllers. Processor 280 is the control center, connecting various parts of UE 101 through various interfaces and lines. It executes various functions of UE 101 and processes data by running or executing software programs and / or modules stored in memory 220, and by calling data stored in memory 220. Power supply 290 (e.g., a battery) is used to power the above components. The power supply can be logically connected to processor 280 through a power management system, thereby enabling the management of charging, discharging, and power consumption.

[0131] Figure 3 is a schematic diagram of a RAN device provided in an embodiment of this application. Taking RAN device 102 as a base station as an example, RAN device 102 may include an indoor baseband unit (BBU) 301 and a remote radio unit (RRU) 302. The RRU 302 is connected to the antenna system (i.e., antenna) 303. BBU 301 and RRU 302 can be disassembled and used as needed. BBU 301 may include a processor 3011, a memory 3012, and a bus system 3013. The processor 3011 and memory 3012 of BBU 301 are interconnected through the bus system 3013. The bus system may be a peripheral component interconnection standard bus or an extended industrial standard structure bus, etc. The bus may be divided into address bus, data bus, control bus, etc. For ease of illustration, only one line is used in the figure, but it does not mean that there is only one bus or one type of bus. RRU 302 may include RF circuitry 3021, which is interconnected with BBU 301 via optical fiber and with antenna 303 via coaxial cable. Processor 3011 executes various functional applications and data processing of RAN device 102 by running computer instructions stored in memory 3012, such as the methods described in the embodiments of this application.

[0132] Figure 4 is a schematic diagram of the structure of a core network element (e.g., an AIOTF network element) provided in an embodiment of this application. Taking the core network element 400 as a network device as an example, the core network element 400 may include at least one processor 401, a communication line 402, a memory 403, and at least one communication interface 404. The processor 401 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of the program of this application. The communication line 402 may include a path for transmitting information between the above components. The communication interface 404, using any transceiver-like device, is used to communicate with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area network (WLAN), etc. The memory 403 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. The memory may exist independently and be connected to the processor via communication line 402. The memory may also be integrated with the processor. The memory 403 is used to store computer execution instructions (which may be referred to as application code) for executing the scheme of this application, and its execution is controlled by the processor 401. The processor 401 is used to execute computer execution instructions stored in the memory 403, thereby performing the methods involved in the embodiments of this application.

[0133] Figure 5 is a schematic diagram of the structure of an Internet of Things (IoT) device provided in an embodiment of this application. Taking IoT device 114 as a tag device as an example, IoT device 114 may include a processing module 501, a communication module 502, and an energy harvesting module 503. The processing module 501 is used for data preprocessing and controlling the IoT device 114 to go into sleep mode or power on. The communication module 502 is used for communication via backscatter or a simplified radio frequency protocol. The energy harvesting module 503 is used to convert energy sources such as radio frequency, light energy, heat energy, and kinetic energy in the environment into electrical energy to power the processing module 501 and the communication module 502.

[0134] The Internet of Things (IoT) system includes IoT device 114, AIOTF network element 115, and AIoT reader 116 as shown in Figure 1. IoT device 114 can be an AIoT device. AIoT devices operate by collecting and utilizing various energy sources in the environment (including but not limited to radio waves, light energy, kinetic energy, and heat energy), improving the sustainability and performance of wireless communication and reducing its power consumption. AIoT devices can be applied in various scenarios, such as smart buildings, asset tracking, agriculture, and smart homes. Specifically, AIoT devices can be smart switches, smart locks, smart meters, sensor-based devices for monitoring machine status and environmental conditions, building automation and control equipment, and tagging devices. In these scenarios, the communication needs of AIoT devices are generally simple, such as simply reporting asset information or sending very little sensor data.

[0135] AIoT devices typically collect ambient energy that can only generate a very small amount of electrical energy, requiring them to be simpler and more energy-efficient. Therefore, AIoT devices need to achieve low-power computing and low-power communication. Based on their energy storage and signal transmission capabilities, the following three types of AIoT devices are defined:

[0136] Device type 1a has a peak power consumption of approximately 1 microwatt, energy storage capabilities, and an initial sampling frequency offset (SFO) of up to 10X ppm. The device does not internally include R2D or device-to-reader (D2R) signal amplification functions. D2R transmission in this device is achieved through backscattering of an externally provided carrier.

[0137] Device type 1b, with peak power consumption not exceeding several hundred microwatts, features energy storage capabilities, a maximum SFO of 10Xppm, and internal R2D and / or D2R signal amplification. D2R transmission in this device is achieved through backscattering of an externally provided carrier.

[0138] Device type 2 has a peak power consumption of no more than several hundred microwatts, energy storage capabilities, and a maximum SFO of 10X ppm. The device includes internal R2D and / or D2R signal amplification functions. The D2R transmission of this device is generated autonomously within the device itself.

[0139] It should be noted that the above only uses three device types as examples to illustrate the types of AIoT devices. Other device types may also exist in actual applications.

[0140] The AIoT reader 116 can be referred to as an AIoT reader / writer, AIoT reader / writer device, tag reader / writer device, etc. The AIoT reader 116 can use wireless communication to read and write to the IoT device 114, thereby achieving target identification and data exchange. Taking the IoT device 114 as a tag device as an example, the AIoT reader 116 provides energy excitation to the tag device by sending an excitation signal and transmitting commands. The tag device sends a response to the AIoT reader 116 through a reflected signal. In this way, the AIoT reader 116 can identify the tag device's identification information and perform read and write operations on the tag device. The AIoT reader 116 can be a RAN device 102 (corresponding to topology 1 shown in Figure 6 or Figure 7) or a UE 101 (corresponding to topology 2 shown in Figure 8 or Figure 9).

[0141] AIOTF network element 115 is a core network element used to manage the AIoT system and provide AIoT-related services and capabilities. AIOTF network element 115 can register as an available network function element with the NRF network element. AIOTF network element 115 can select RAN device 102 as the AIOTF reader (corresponding to topology 1), or select UE 101 as the AIOTF reader, and send the selected UE list to the RAN device (corresponding to topology 2). The AIOTF network element 115 sending the selected UE list to the RAN device is only applicable to options based on radio resource control (RRC).

[0142] Figure 6 is a schematic diagram of the control plane protocol stack of one topology 1 provided in an embodiment of this application; Figure 7 is a schematic diagram of the control plane protocol stack of another topology 1 provided in an embodiment of this application; Figure 7 adds the protocol stack of the AMF network element compared to Figure 6. The IoT device includes the AIoT data layer, the AIoT non-access stratum (NAS) layer, and the AIoT access stratum (AS) layer. The RAN device, acting as an AIoT reader, includes the AIoT AS layer, the next generation application protocol (NGAP) layer, and lower layers. The AIoT AS layer includes the media access control (MAC) layer and the physical (PHY) layer. In Figure 6, the AIOTF network element includes the NAS layer, the NGAP layer, the service based interface (SBI) layer, and lower layers. In Figure 7, the AIOTF network element includes the NAS layer, the SBI layer, and lower layers. The NEF network element includes the SBI layer and the API layer. The AF network element includes the AIoT data layer, the API layer, and lower layers. The AMF network element includes the NAS layer, the SBI layer, and lower layers. RAN equipment, AMF network elements, AIOTF network elements, and NEF network elements serve as relays for AIoT data.

[0143] For AIoT systems, the AIoT AS layer is used for low-power communication. The NGAP layer includes all or part of the NGAP functions of traditional AMF network elements and RAN equipment, providing low-power radio control signaling for AIoT and optimizing registration and mobility management processes. The SBI layer enables service-oriented calls to core network functions, such as interaction between AIOTF network elements and AMF and NEF network elements. The API layer exposes device management, data acquisition, and other capabilities to industry applications.

[0144] Figure 8 is a schematic diagram of a control plane protocol stack for topology 2 provided in an embodiment of this application. The IoT device includes an AIoT data layer, an AIoT NAS layer, and an AIoT AS layer. The UE, acting as an AIoT reader, includes the AIoT AS layer, radio resource control (RRC) layer, packet data convergence protocol (PDCP) layer, radio link control (RLC) layer, MAC layer, and PHY layer. The RAN device includes the RRC layer, PDCP layer, RLC layer, MAC layer, PHY layer, AIoT reader control layer, NGAP layer, and lower layers. The AMF network element includes the NGAP layer, SBI layer, and lower layers. The AIOTF network element includes the NAS layer, SBI layer, and lower layers. The NEF network element includes the SBI layer and API layer. The AF network element includes the AIoT data layer, API layer, and lower layers. The UE, RAN device, AMF network element, AIOTF network element, and NEF network element act as relays for AIoT data.

[0145] The AIoT reader control layer coordinates the interaction between the AIoT reader and IoT devices, the core network, and upper-layer applications. The functions of other layers are described above and will not be repeated here.

[0146] Figure 9 is a schematic diagram of a user plane protocol stack for Topology 2 provided in an embodiment of this application. The IoT device includes an AIoT data layer, an AIoT NAS layer, and an AIoT AS layer. The UE, acting as an AIoT reader, includes an AIoT AS layer, an AIoT UE reader control layer, an IP transmission layer, a PDU layer, and a UU AS layer. The RAN device includes an air interface access layer (UU AS), a user plane tunneling protocol (GPRS tunnel protocol-user plane, GTP-U) layer, and lower layers. The UPF network element includes a PDU layer, a GTP-U layer, and lower layers. The AIOTF network element includes a NAS layer, an AIoT UE reader control layer, an IP transmission layer, an SBI layer, and lower layers. The NEF network element includes an SBI layer and an API layer. The AF network element includes an AIoT data layer, an API layer, and lower layers. The UE, RAN device, UPF network element, AIOTF network element, and NEF network element act as relays for AIoT data.

[0147] The AIoT UE reader control layer is used for the discovery, management, signaling, and data transmission of IoT devices. The IP transport layer is used for protocol selection and adaptation and routing optimization. The PDU layer is used for data encapsulation optimization and reliability control. The UU AS layer is used to control the backscatter communication of IoT devices and manage the radio frequency connections of IoT devices. The GTP-U layer is used for data tunnel encapsulation and quality of service (QoS) assurance. The functions of other layers are described above and will not be repeated here.

[0148] AIoT services include inventory services and command services. Inventory services must be executed before command services. Inventory services are a fundamental service in the AIoT system, used to discover or identify IoT devices 114 within the coverage area of ​​AIoT reader 116. Command services include read, write, disable, and enable services. The read service is used to read information from IoT device 114. The write service is used to write information to IoT device 114. The disable service instructs IoT device 114 to permanently or temporarily disable its ability to transmit radio frequency. The enable service enables temporarily disabled IoT device 114. For example, when IoT device 114 is a sensor, the AF network element can acquire sensor data through the read service.

[0149] The AIOTF network element 115 can send the following auxiliary information to the AIoT reader 116: the AIoT service type, the approximate number of IoT devices 114 receiving the AIoT command request message, and the approximate size of the response message for the AIoT command request message. It should be noted that if the AIOTF network element 115 selects multiple AIoT readers 116, the AIOTF network element 115 can provide each AIoT reader 116 with the approximate number of IoT devices 114 receiving the AIoT command request message.

[0150] AIOTF network element 115 can determine AIoT aggregation assistance information based on AIoT command request messages and operator policies, and send the AIoT aggregation assistance information to AIoT reader 116. The AIoT aggregation assistance information assists AIoT reader 116 in aggregating responses from multiple IoT devices 114. The AIoT aggregation assistance information may include time intervals; AIoT reader 116 can aggregate responses from multiple IoT devices 114 according to these time intervals and send them to AIOTF network element 115 until the AIoT service is completed.

[0151] Figure 10 is a schematic diagram of an inventory service process provided in an embodiment of this application. The inventory service process 1000 includes S1001-S1007.

[0152] S1001, the AIOTF network element sends an inventory request message (including the associated identifier, optionally including the IoT device identifier) ​​to the AIoT reader.

[0153] Accordingly, the AIoT reader receives inventory request messages from the AIOTF network element. These inventory request messages are NGAP layer messages. A correlation ID, generated by the AIOTF network element, identifies a service operation request from the AF network element. This service operation request triggers the AIOTF network element to send an inventory request message to the AIoT reader. The correlation ID associates the information sent by the AIOTF network element to the AIoT reader in response to the service operation request with the information received by the AIOTF network element from the AIoT reader (e.g., the execution result of the service operation request). The AIOTF network element can then use the correlation ID to feed back the information received from the AIoT reader to the AF network element.

[0154] S1002, The AIoT reader sends a paging message (optionally, including the IoT device identifier) ​​to the IoT device.

[0155] Accordingly, IoT devices receive paging messages from the AIoT reader. The paging message is used to page the IoT device. When the paging message includes the IoT device identifier, it is used to page that IoT device. When the paging message does not include the IoT device identifier, it is used to page all IoT devices within the coverage area of ​​the AIoT reader.

[0156] S1003, The AIoT reader sends reader-to-device (R2D) messages (e.g., R2D trigger messages) to IoT devices.

[0157] Accordingly, the IoT device receives R2D messages (e.g., R2D trigger messages) from the AIoT reader. These R2D messages (e.g., R2D trigger messages) are R2D transmission signals that trigger random access, used to trigger the IoT device to perform inventory services.

[0158] S1004. The IoT device sends an RN16 message (including RN16) to the AIoT reader.

[0159] An RN16 message contains a 16-bit random number, abbreviated as RN16.

[0160] S1005, the AIoT reader sends MSG2 messages (including RN16) to IoT devices.

[0161] The MSG2 message is the second message sent by the AIoT reader to the IoT device. The MSG2 message includes RN16 to enable the IoT device to establish reliable communication with the AIoT reader.

[0162] S1006. The IoT device sends a device-to-reader (D2R) message (including inventory results NAS PDU) to the AIoT reader.

[0163] Accordingly, the AIoT reader receives D2R messages from IoT devices. The D2R message includes the IoT device inventory result NAS PDU, which contains the IoT device identifier.

[0164] S1007, the AIoT reader sends an inventory report message (including the association identifier, AIoT reader identifier, and inventory result NAS PDU) to the AIOTF network element.

[0165] Accordingly, the AIOTF network element receives inventory report messages from the AIoT reader. These inventory report messages are NGAP layer messages. They include an association identifier, an AIoT reader identifier, and an inventory result NAS PDU. The AIOTF network element can determine the service operation request from the AF network element corresponding to the inventory result NAS PDU based on the association identifier, and thus send the IoT device identifier from the inventory result NAS PDU to the AF network element. The AIOTF network element determines which AIoT reader sent the inventory report message based on the AIoT reader identifier.

[0166] It should be noted that the inventory report message received by the AIOTF network element may include inventory results replied by at least one IoT device.

[0167] Figure 11 is a schematic diagram of a command service flow provided in an embodiment of this application. An inventory service needs to be executed before the command service can be executed. The command service flow 1100 includes S1101-S1104.

[0168] S1101, the AIOTF network element sends a command request message (including the association identifier and command request NAS PDU) to the AIoT reader and starts the AIoT NAS timer.

[0169] Accordingly, the AIoT reader receives command request messages from the AIOTF network element. The command request message includes a correlation ID and a command request NAS PDU. The command request NAS PDU indicates the type of command service to be performed on the IoT device, such as read service, write service, disable service, and enable service. The correlation ID is generated by the AIOTF network element and is used to identify the service operation request from the AF network element. The service operation request triggers the AIOTF network element to send a command request message to the AIoT reader. The correlation ID can be used to associate the information sent by the AIOTF network element to the AIoT reader triggered by the service operation request with the information received by the AIOTF network element from the AIoT reader (e.g., the execution result of the service operation request). The AIOTF network element can then use the correlation ID to feed back the information received from the AIoT reader to the AF network element.

[0170] S1102, The AIoT reader sends R2D messages (including command request NAS PDU) to IoT devices.

[0171] Accordingly, the IoT device receives an R2D message from the AIoT reader. The R2D message includes a command request NAS PDU.

[0172] S1103. The IoT device sends D2R messages (including command response NAS PDU) to the AIoT reader.

[0173] Accordingly, the AIoT reader receives D2R messages from IoT devices. These D2R messages include NAS Command Response (NAS PDUs). The NAS PDU indicates the result of the IoT device executing a command service. For example, for a read service, the result refers to the data returned by the IoT device. For a write service, the result indicates whether the write service was successful. For a disable service, the result indicates whether the IoT device was successfully disabled. For an enable service, the result indicates whether the IoT device was successfully enabled.

[0174] S1104. The AIoT reader sends a command response message (including the association identifier and command response NAS PDU) to the AIOTF network element.

[0175] Accordingly, the AIOTF network element receives command response messages from the AIoT reader. The command response message includes an association identifier and a command response NAS PDU.

[0176] In normal communication scenarios, when an AIOTF network element receives a command response message, it associates the received command response NAS PDU with the sent command request NAS PDU based on the association identifier. If this indicates that the IoT device has responded normally to the command request NAS PDU, the AIoT NAS timer is turned off to end the command service process. The AIOTF network element can also determine the service operation request of the AF network element corresponding to the command response NAS PDU based on the association identifier, and thus can send the command response NAS PDU to the AF network element.

[0177] In abnormal communication scenarios, such as when an IoT device runs out of power, malfunctions, or signal obstruction occurs between the IoT device and the AIoT reader, the AIoT reader may be unable to receive D2R messages (including command response NAS PDUs) from the IoT device. Consequently, the AIoT reader cannot send command response messages (including command response NAS PDUs) to the AIOTF network element, resulting in both the AIoT reader and the AIOTF network element failing to receive command response NAS PDUs, and thus preventing the execution of steps S1103-S1104. In step S1101, the AIOTF network element, in addition to sending command request messages, also starts an AIoT NAS timer. If no command response message is received after the AIoT NAS timer expires, the AIOTF network element terminates the command service process. Existing communication protocols do not specify how the AIoT reader and AIOTF network element should handle such abnormal communication scenarios, leading to communication failure between the AIOTF network element and the IoT device.

[0178] In view of this, embodiments of this application provide a communication method for command services. After an AIoT reader sends a command request NAS PDU to an IoT device, if the AIoT reader or AIOTF network element cannot receive a command response NAS PDU, i.e., the IoT device fails to respond, the AIoT reader or AIOTF network element triggers an inventory service or command service to the IoT device that failed to respond, attempting to resume communication with the IoT device that failed to respond. This helps to improve the success rate of IoT device responses and improve the service quality and reliability of command services.

[0179] Figure 12 is a schematic diagram of the first communication method provided in the embodiment of this application. The AIOTF network element in Figure 12 can be the AIOTF network element in Figure 1, or it can refer to a device (e.g., processor, chip, or chip system) within the AIOTF network element. The AIoT reader in Figure 12 can be the AIoT reader in Figure 1, or it can refer to a device (e.g., processor, chip, or chip system) within the AIoT reader. The IoT device in Figure 12 can be the IoT device in Figure 1, or it can refer to a device (e.g., processor, chip, or chip system) within the IoT device. As shown in Figure 12, the communication method 1200 includes the following steps S1201-S1206:

[0180] S1201, the AIOTF network element sends a command request message (including the association identifier and command request NAS PDU, and optionally, service level information and first IoT device information) to the AIoT reader, and starts the AIoT NAS timer.

[0181] This step can also be described as follows: the AIOTF network element sends an association identifier and a command request NAS PDU to the AIoT reader; correspondingly, the AIoT reader receives the association identifier and command request NAS PDU from the AIOTF network element. This application embodiment does not limit the message name carrying the information, nor does it limit whether multiple pieces of information are carried in one message or multiple messages.

[0182] Optionally, the command request message may also include service level information, which indicates the reliability level of the command service, such as low, medium, or high. This can also be described as: the AIOTF network element sends service level information to the AIoT reader, and the AIoT reader receives the service level information from the AIOTF network element. The service level information can be an identifier of the AF network element or a quality of service (QoS) related identifier, such as a QoS flow identifier or service priority.

[0183] Optionally, the command request message may also include information about the first IoT device. This can also be described as: the AIOTF network element sends the first IoT device information to the AIoT reader, and correspondingly, the AIoT reader receives the first IoT device information from the AIOTF network element. The first IoT device information is generated by the AIoT reader, and the first IoT device information stored by the AIOTF network element may actually come from the AIoT reader or be generated by the AIOTF network element itself. For example, when performing an inventory service before executing the command service, the inventory report message sent by the AIoT reader to the AIOTF network element as described in S1007 may include the first IoT device information, thus informing the AIOTF network element of the first IoT device information in advance. It should be noted that since the inventory report message received by the AIOTF network element may include inventory results replied by at least one IoT device, there will also be at least one piece of first IoT device information corresponding to each IoT device.

[0184] The first IoT device information is used when the AIoT reader communicates with the AIOTF network element. Both the AIoT reader and the AIOTF network element can use this first IoT device information to identify the IoT device. As shown in Figure 6, because the AIOTF network element has a NAS layer, it can parse NAS PDUs (e.g., inventory NAS PDUs, command response NAS PDUs) to obtain the IoT device identifier. However, the AIoT reader does not have a NAS layer and cannot parse NAS PDUs (e.g., inventory result NAS PDUs, command response NAS PDUs) to obtain the IoT device identifier. Therefore, the AIoT reader cannot identify the IoT device based on the IoT device identifier and needs to use the first IoT device information to determine the IoT device.

[0185] For example, the first IoT device information is an NGAP identifier or another identifier generated by the AIoT reader (or the base station where the AIoT reader is located) to indicate the IoT device. The NGAP identifier can be a RAN NGAP device ID, a core network NGAP device ID, or an AIOTF NGAP device ID. It should be noted that the NGAP identifier sent by the AIoT reader to the AIOTF network element and the NGAP identifier sent by the AIOTF network element to the AIoT reader may not be the same, but they can be bound together. For example, the NGAP identifier sent by the AIoT reader to the AIOTF network element may be the RAN NGAP device ID, and the NGAP identifier sent by the AIOTF network element to the AIoT reader may be the core network NGAP device ID or the AIOTF NGAP device ID. For simplicity, this application embodiment does not distinguish between NGAP identifiers. Regarding NGAP identifiers, AIoT readers and AIOTF network elements communicate through the NGAP layer. Furthermore, different IoT devices have different NGAP identifiers, so both AIoT readers and AIOTF network elements can identify IoT devices based on their NGAP identifiers.

[0186] When the command request message includes information about the first IoT device, it can trigger the execution of command services for a single IoT device (such as an IoT device that failed to respond), instead of executing command services for all IoT devices. This reduces the power consumption of IoT devices, AIoT readers, and AIOTF network elements, and saves signaling overhead.

[0187] The other details of this step are the same as in S1101 and will not be repeated here.

[0188] S1202, The AIoT reader sends an R2D message (including a command request NAS PDU, and optionally, information about the second IoT device) to the IoT device.

[0189] This step can also be described as follows: the AIoT reader sends a command request NAS PDU to the IoT device, and the IoT device receives the command request NAS PDU from the AIoT reader.

[0190] Optionally, the R2D message may also include information about a second IoT device. This can also be described as: the AIoT reader sends information about a second IoT device to the IoT device, and the IoT device receives this information from the AIoT reader.

[0191] The second IoT device information is used when the AIoT reader communicates with the IoT device. Both the AIoT reader and the IoT device can identify the IoT device based on this second IoT device information. As shown in Figure 6, because the IoT device has a NAS layer, it can encapsulate the IoT device identifier in a NAS PDU (e.g., a disk-based NAS PDU, a command response NAS PDU) and send it out, or parse a received NAS PDU to obtain the IoT device identifier. However, the AIoT reader does not have a NAS layer and cannot parse NAS PDUs (e.g., disk-based NAS PDUs, command response NAS PDUs) to obtain the IoT device identifier. Therefore, the AIoT reader cannot identify the IoT device based on the IoT device identifier, but needs to use the second IoT device information. Furthermore, the IoT device does not need to parse the command request NAS PDU in the R2D message to obtain the IoT device identifier to determine if the R2D message was sent to it. Instead, it can determine that the R2D message was sent to it based on the second IoT device information in the R2D message, thereby reducing the power consumption of the IoT device.

[0192] For example, the second IoT device information is an AS identifier, a stored NAS PDU, or other identifier generated by the AIoT reader to indicate the IoT device. Regarding the AS identifier, since the AIoT reader and the IoT device communicate through the AIoT AS layer, and different IoT devices have different AS identifiers, both the IoT device and the AIOTF network element can determine the IoT device based on the AS identifier. Regarding the stored NAS PDU, for the IoT device, on the one hand, the IoT device can generate a stored NAS PDU; on the other hand, as shown in Figure 6, since the IoT device has a NAS layer, it can parse the stored NAS PDU to obtain the IoT device identifier, thereby identifying the IoT device. For the AIoT reader, when performing the stored service before executing the command service, in S1007, the AIoT reader can obtain and cache the stored NAS PDU from the IoT device. If the AIoT reader receives a stored NAS PDU from the IoT device during the command service, it can match it with the cached stored NAS PDU of the IoT device. If a match is found, the corresponding IoT device can be identified.

[0193] Furthermore, the AIoT reader can bind information about a first IoT device and information about a second IoT device. This means the AIoT reader can determine the second IoT device information based on the binding relationship between the two information, or vice versa. Thus, when the AIoT reader receives information about a first IoT device from an AIOTF network element, it can send information about a second IoT device to the IoT device; conversely, when the AIoT reader receives information about a second IoT device from an IoT device, it can send information about a first IoT device to the AIOTF network element. In other words, messages transmitted between the AIoT reader and the AIOTF network element include information about the first IoT device, and messages transmitted between the AIoT reader and the IoT device include information about the second IoT device, thereby enabling communication between the IoT device and the AIOTF network element via the AIoT reader.

[0194] The other details of this step are the same as in S1102 and will not be repeated here.

[0195] S1203. The IoT device sends a D2R message to the AIoT reader (including a command response NAS PDU, and optionally, information about the second IoT device).

[0196] This step can also be described as follows: the IoT device sends a command response NAS PDU to the AIoT reader, and the AIoT reader receives the command response NAS PDU from the IoT device accordingly.

[0197] Optionally, the D2R message may also include information about a second IoT device. This can be described as follows: the IoT device sends information about a second IoT device to the AIoT reader, and the AIoT reader receives the information about the second IoT device from the IoT device.

[0198] The other details of this step are the same as those in S1103, and will not be repeated here.

[0199] S1204. In response to receiving a D2R message from an IoT device, the AIoT reader sends a command response message (including the association identifier, first IoT device information, and command response NAS PDU) to the AIOTF network element.

[0200] This step can also be described as follows: In response to receiving a command response NAS PDU from an IoT device, the AIoT reader sends the association identifier, the first IoT device information, and the command response NAS PDU to the AIOTF network element.

[0201] The other details of this step are the same as those in S1104 and will not be repeated here.

[0202] S1205. In response to not receiving a D2R message from the IoT device, the AIoT reader performs at least one of the following: triggers an inventory service for the IoT device, triggers a command service for the IoT device, and sends a command response message (including the association identifier, the first IoT device information, and the reason for the response failure) to the AIOTF network element.

[0203] This step can also be described as follows: In response to the failure to receive a command response NAS PDU from the IoT device, i.e., the IoT device response fails, at least one of the following is executed: triggering the inventory service for the IoT device, triggering the command service for the IoT device, and sending the association identifier, the first IoT device information, and the reason for the response failure to the AIOTF network element.

[0204] After sending an R2D message, the AIoT reader expects to receive a D2R message from the IoT device on a preset time-frequency resource. If no D2R message is received from the IoT device on the preset time-frequency resource, it can be determined that no D2R message has been received from the IoT device. Alternatively, after sending an R2D message, the AIoT reader starts a timer. If no D2R message is received from the IoT device after the timer expires, it can also be determined that no D2R message has been received from the IoT device.

[0205] The AIoT reader triggers an inventory service for IoT devices that fail to respond, and / or the IoT device triggers a command service for the same IoT device that failed to respond. This can attempt to restore communication with the failed IoT device, helping to improve the success rate of the IoT device's response and enhance the service quality and reliability of the command service. The AIoT reader sends the first IoT device information and the reason for the response failure to the AIOTF network element, enabling the AIOTF network element to determine which IoT device failed to respond and for what reason. The AIoT reader sends an association identifier to the AIOTF network element, which can then determine the service operation request from the AF network element corresponding to the first IoT device information and the reason for the response failure based on the association identifier. The AIOTF network element can then send the IoT device identifier and response indication information to the AF network element.

[0206] As shown in Figure 6, because the AIoT reader lacks a NAS layer, it cannot obtain the IoT device identifier by parsing the command response NAS PDU in the D2R message. Therefore, the AIoT reader cannot determine whether it has received a D2R message from an IoT device based on the IoT device identifier. In this embodiment, the AIoT reader can determine whether it has received a D2R message from an IoT device using one of the following three methods:

[0207] Method 1: The AIoT reader sends R2D messages to different IoT devices on different time-frequency resources and receives D2R messages on the corresponding time-frequency resources. After sending an R2D message to an IoT device on a certain time-frequency resource, if the AIoT reader does not receive a D2R message on the corresponding time-frequency resource, it can be determined that a D2R message from that IoT device has not been received.

[0208] Method 2: When the second IoT device information in the D2R message is an AS identifier, the AIoT reader can determine that a D2R message from an IoT device has been received based on the AS identifier in the D2R message. After sending an R2D message, if no D2R message including a certain AS identifier is received on the corresponding time-frequency resource, it can be determined that no D2R message from the corresponding IoT device has been received.

[0209] Method 3: When the second IoT device information in the D2R message is a disk inventory result NAS PDU, during the disk inventory service performed before executing the command service, in S1007, the AIoT reader can obtain and cache the disk inventory result NAS PDU from the IoT device. If the AIoT reader receives a disk inventory result NAS PDU from the IoT device in this step, it can match it with the cached disk inventory result NAS PDU of the IoT device. If a match is found, the corresponding IoT device can be identified. After sending the R2D message, if no D2R message including the disk inventory result NAS PDU is received on the corresponding time-frequency resource, so that the disk inventory result NAS PDU matches the cached disk inventory result NAS PDU of the IoT device, it can be determined that no D2R message from that IoT device has been received.

[0210] An AIoT reader can perform at least one of the following actions based on local policies or service level information: trigger an inventory service for IoT devices, trigger a command service for IoT devices, or send an association identifier and response failure reason to the AIOTF network element. Local policies refer to directly configuring what operations the AIoT reader should perform. Service level information indicates that the higher the reliability level of the command service, the more operations are performed, the higher the success rate of IoT device responses, and the higher the service quality of the command service. Conversely, the lower the reliability level of the command service, the fewer operations are performed by the IoT device, AIoT reader, and AIOTF network element, resulting in lower power consumption. An example of service level information is shown below:

[0211] If the service level information indicates that the reliability level of the command service is low, the AIoT reader does not need to trigger the inventory service or the command service for the IoT device. Instead, it can send the association identifier, the first IoT device information, and the reason for the failure to the AIOTF network element.

[0212] If the service level information indicates that the reliability level of the command service is medium, the AIoT reader can trigger an inventory service for the IoT device, or trigger a command service for the IoT device. Optionally, it can send the association identifier, the first IoT device information, and the reason for the response failure to the AIOTF network element.

[0213] If the service level information indicates that the reliability level of the command service is high, the AIoT reader triggers an inventory service for the IoT device and also triggers a command service for the IoT device. Optionally, the AIoT reader may send the association identifier, the first IoT device information, and the reason for the response failure to the AIOTF network element.

[0214] In this embodiment, the AIoT reader triggering the inventory service for the IoT device refers to executing S1003-S1006, and optionally, S1007 can also be executed. If the AIoT reader receives a D2R message from the IoT device in S1006, S1007 can be executed; alternatively, S1007 can be omitted, and command service can continue to be executed, i.e., S1202-S1206, to complete the command service process. Furthermore, the R2D message (e.g., R2D trigger message) sent by the AIoT reader to the IoT device in S1003 includes second IoT device information. The second IoT device information indicates the IoT device that failed to respond, i.e., triggering the inventory service for a single IoT device that failed to respond, eliminating the need to execute the inventory service for all IoT devices, thereby reducing the power consumption of the IoT devices, AIoT reader, and AIOTF network elements, and saving signaling overhead.

[0215] In this embodiment, the AIoT reader triggers the execution of command services to IoT devices, specifically steps S1202-S1206. The command response message sent by the AIoT reader to the AIOTF network element in S1204 and in S1205 includes first IoT device information; the R2D message sent by the AIoT reader to the IoT device in S1202 and the D2R message sent by the IoT device to the AIoT reader in S1203 includes second IoT device information. Both the first and second IoT device information indicate the IoT device that failed the response, thus triggering command services for a single IoT device that failed the response. This avoids executing command services for all IoT devices, thereby reducing power consumption of the IoT devices, AIoT reader, and AIOTF network element, and saving signaling overhead.

[0216] Optionally, the command response message may also include operation indication information. This can be described as follows: the AIoT reader sends operation indication information to the AIOTF network element, and correspondingly, the AIOTF network element receives operation indication information from the AIoT reader. The operation indication information is used to indicate whether the AIoT reader triggers the execution of command services to the IoT device, and whether it triggers the execution of inventory services to the IoT device. If the AIoT reader does not send operation indication information to the AIOTF network element, it indicates that the AIoT reader has neither triggered the execution of command services to the IoT device nor triggered the execution of inventory services to the IoT device.

[0217] For example, the data type of the operation indication information can be a two-bit bit string. The first bit indicates whether the AIoT reader triggers a command service to the IoT device; for example, a first bit of 1 indicates that the AIoT reader triggers a command service to the IoT device, and a first bit of 0 indicates that the AIoT reader does not trigger a command service to the IoT device. The second bit indicates whether the AIoT reader triggers an inventory service to the IoT device; for example, a second bit of 1 indicates that the AIoT reader triggers an inventory service to the IoT device, and a second bit of 0 indicates that the AIoT reader does not trigger an inventory service to the IoT device.

[0218] The response failure reason is used to indicate why the IoT device failed to respond. The data type of the response failure reason can be an enumeration or an integer. For example, the possible values ​​and meanings of the response failure reason are shown in Table 1:

[0219] Table 1

[0220] S1206. In response to receiving a command response message including the first IoT device information and the reason for the response failure, or in response to not receiving a command response message including the first IoT device information and the command response NAS PDU within a preset time, the AIOTF network element performs at least one of the following: triggers the execution of an inventory service for the IoT device, triggers the execution of a command service for the IoT device, and sends the IoT device identifier and response failure indication information to the AF network element.

[0221] This step can also be described as follows: In response to receiving the first IoT device information and the reason for the response failure from the AIoT reader, or in response to not receiving the first IoT device information and command response NAS PDU from the AIoT reader within a preset time, i.e., the IoT device response fails, the AIOTF network element performs at least one of the following: triggers an inventory service for the IoT device, triggers a command service for the IoT device, or sends the IoT device identifier and response failure indication information to the AF network element. The preset time refers to the preset time after the AIOTF network element sends the command request message (or command request NAS PDU) to the AIoT reader IoT device, i.e., the timing period of the AIoT NAS timer.

[0222] Based on the first IoT device information and the reason for the response failure, the AIOTF network element can determine which IoT device failed to respond and for what reason. The AIOTF network element triggers an inventory service for the IoT device, and / or triggers a command service for the IoT device, which can attempt to restore communication with the failed IoT device, helping to improve the success rate of IoT device responses and the quality of service of the command service. The AIOTF network element sends the IoT device identifier and response failure indication information to the AF network element, enabling the AF network element to determine which IoT device failed to respond based on the IoT device identifier and response failure indication information, thereby adjusting the state of that IoT device, such as enabling the IoT device.

[0223] In one possible implementation, the AIOTF network element can perform at least one of the following actions based on local policies or service level information: triggering an inventory service for the IoT device, triggering a command service for the IoT device, and sending the IoT device identifier and response failure indication information to the AF network element. Local policies refer to directly configuring what operations the AIOTF network element should perform. Service level information indicates that the higher the reliability level of the command service, the higher the success rate of the IoT device response and the higher the service quality of the command service. Conversely, the lower the reliability level of the command service, the fewer operations the IoT device, AIoT reader, and AIOTF network element perform, resulting in lower power consumption. An example is shown below:

[0224] If the service level information indicates that the reliability level of the command service is low, the AIOTF network element does not need to trigger the inventory service or the command service for the IoT device. The AIOTF network element can send the IoT device identifier and response failure indication information to the AF network element.

[0225] If the service level information indicates that the reliability level of the command service is medium, the AIOTF network element can trigger an inventory service for the IoT device, or trigger a command service for the IoT device. Optionally, the AIOTF network element can send the IoT device identifier and response failure indication information to the AF network element.

[0226] If the service level information indicates that the reliability level of the command service is high, the AIOTF network element triggers an inventory service for the IoT device and also triggers a command service for the IoT device. Optionally, the AIOTF network element AIoT reader can send the IoT device identifier and response failure indication information to the AF network element.

[0227] In another possible implementation, the AIOTF network element may also receive operation instruction information from the AIoT reader. The AIOTF network element can then perform at least one of the following actions based on the operation instruction information: triggering an inventory service for the IoT device, triggering a command service for the IoT device, or sending the IoT device identifier and response failure indication information to the AF network element. An example is shown below:

[0228] If the AIOTF network element receives an operation instruction from the AIoT reader, and the operation instruction instructs the AIoT reader to trigger an inventory service for the IoT device but does not trigger a command service for the IoT device, indicating the command service process has ended, then the AIOTF network element will shut down the AIoT NAS timer. Optionally, the AIOTF network element can also send the IoT device identifier and response failure indication information to the AF network element.

[0229] If the AIOTF network element receives an operation instruction from the AIoT reader, and the operation instruction instructs the AIoT reader to trigger a command service to the IoT device but fails to trigger an inventory service, indicating a restart of the command service process, the AIOTF network element will reset the AIoT NAS timer. Optionally, the AIOTF network element can also send the IoT device identifier and response failure indication information to the AF network element.

[0230] If the AIOTF network element receives an operation instruction from the AIoT reader, and the operation instruction instructs the AIoT reader to trigger command service execution and inventory service execution for the IoT device, indicating a restart of the inventory service process and command service process, then the AIOTF network element resets the AIoT NAS timer. Optionally, the AIOTF network element can also send the IoT device identifier and response failure indication information to the AF network element.

[0231] If the AIOTF network element does not receive operation instructions from the AIoT reader, or if the AIOTF network element receives operation instructions from the AIoT reader and the operation instructions indicate that the AIoT reader has not triggered either the command service or the inventory service for the IoT device, then the AIOTF network element may perform at least one of the following actions based on local policies or service level information: trigger the inventory service for the IoT device, trigger the command service for the IoT device, or send the IoT device identifier and response failure indication information to the AF network element. See the preceding description for details, which will not be repeated here.

[0232] In this embodiment, the AIOTF network element triggering the inventory service for the IoT device refers to executing S1001-S1007. The inventory request message sent by the AIOTF network element to the AIoT reader in S1001, and the paging message sent by the AIoT reader to the IoT device in S1002, include an IoT device identifier. The R2D message (e.g., an R2D trigger message) sent by the AIoT reader to the IoT device in S1003 includes second IoT device information. The IoT device identifier and the second IoT device information indicate the IoT device that failed to respond, thus triggering the inventory service for a single IoT device that failed to respond. This avoids performing the inventory service for all IoT devices, thereby reducing the power consumption of the IoT device, AIoT reader, and AIOTF network element, and saving signaling overhead.

[0233] In this embodiment, the AIOTF network element triggers the execution of command services to IoT devices, specifically steps S1201-S1206. The command request message sent by the AIOTF network element to the AIoT reader in S1201, the command response message sent by the AIoT reader to the AIOTF network element in S1204, and the command response message sent by the AIoT reader to the AIOTF network element in S1205 include first IoT device information. The R2D message sent by the AIoT reader to the IoT device in S1202, and the D2R message sent by the IoT device to the AIoT reader in S1203, include second IoT device information. Both the first and second IoT device information indicate the IoT device that failed to respond, thus triggering command services for a single IoT device that failed to respond. This avoids executing command services for all IoT devices, thereby reducing the power consumption of the IoT devices, AIoT reader, and AIOTF network element, and saving signaling overhead.

[0234] It should be noted that at least one of S1205 and S1206 can be executed. For example, if the following of S1205 is executed, S1206 can be omitted: The AIoT reader executes at least one of the following: triggers an inventory service for the IoT device, triggers a command service for the IoT device. As another example, if the following of S1205 is executed, S1206 can be omitted: The AIoT reader sends a command response message to the AIOTF network element. As yet another example, if S1205 is not executed, the following of S1206 can be executed: In response to not receiving a command response message including the first IoT device information and the command response NAS PDU within a preset time, the AIOTF network element executes at least one of the following: triggers an inventory service for the IoT device, triggers a command service for the IoT device, and sends the IoT device identifier and response failure indication information to the AF network element.

[0235] The communication method provided in this application embodiment, for command services, in the event of an IoT device failure to respond, triggers an AIoT reader or AIOTF network element to execute an inventory service or command service on the IoT device that failed to respond, attempting to restore communication with the IoT device that failed to respond, which helps to improve the success rate of IoT device responses and improve the service quality of command services.

[0236] The above communication method will be explained below with specific examples.

[0237] Figure 13 is a schematic diagram of the second communication method provided in the embodiments of this application. The AIOTF network element in Figure 13 can be the AIOTF network element in Figure 1, or it can refer to a device (e.g., a processor, chip, or chip system) within the AIOTF network element. The AIoT reader in Figure 13 can be the AIoT reader in Figure 1, or it can refer to a device (e.g., a processor, chip, or chip system) within the AIoT reader. The IoT device in Figure 13 can be the IoT device in Figure 1, or it can refer to a device (e.g., a processor, chip, or chip system) within the IoT device. As shown in Figure 13, the communication method 1300 includes the following steps S1301-S1304:

[0238] S1301, the AIOTF network element sends a command request message (including the association identifier and command request NAS PDU, and optionally, the first IoT device information) to the AIoT reader, and starts the AIoT NAS timer.

[0239] This step is described in accordance with S1201 and will not be repeated here.

[0240] S1302, The AIoT reader sends an R2D message (including a command request NAS PDU, and optionally, information about a second IoT device) to the IoT device.

[0241] This step is described in S1202 and will not be repeated here.

[0242] S1303. In response to not receiving a D2R message from an IoT device, the AIoT reader sends a command response message (including the association identifier, the first IoT device information, and the reason for the response failure) to the AIOTF network element.

[0243] This step is described in accordance with S1205 and will not be repeated here.

[0244] S1304. In response to receiving a command response message including information about the first IoT device and the reason for the response failure, the AIOTF network element performs at least one of the following: triggers an inventory service for the IoT device, triggers a command service for the IoT device, and sends the IoT device identifier and response failure indication information to the AF network element.

[0245] This step is described in accordance with S1206 and will not be repeated here.

[0246] In this embodiment, when an IoT device fails to respond, in response to receiving a command response message including first IoT device information and a reason for response failure, the AIOTF network element determines which IoT device failed and for what reason, based on the first IoT device information and the reason for response failure. The AIOTF network element triggers an inventory service for the IoT device that failed to respond, and / or triggers a command service for the IoT device that failed to respond, which can attempt to restore communication with the IoT device that failed to respond, helping to improve the success rate of IoT device responses and improve the service quality of the command service. The AIOTF network element sends an IoT device identifier and response failure indication information to the AF network element, enabling the AF network element to determine which IoT device failed to respond based on the IoT device identifier and the reason for response failure, thereby adjusting the state of the IoT device, such as enabling the IoT device.

[0247] Figure 14 is a schematic diagram of the third communication method provided in the embodiments of this application. The AIOTF network element in Figure 14 can be the AIOTF network element in Figure 1, or it can refer to a device (e.g., processor, chip, or chip system) within the AIOTF network element. The AIoT reader in Figure 14 can be the AIoT reader in Figure 1, or it can refer to a device (e.g., processor, chip, or chip system) within the AIoT reader. The IoT device in Figure 14 can be the IoT device in Figure 1, or it can refer to a device (e.g., processor, chip, or chip system) within the IoT device. As shown in Figure 14, the communication method 1400 includes the following steps S1401-S1403:

[0248] S1401, the AIOTF network element sends a command request message (including the association identifier and command request NAS PDU, and optionally, service level information) to the AIoT reader, and starts the AIoT NAS timer.

[0249] This step is the same as step S1201, and will not be repeated here.

[0250] S1402, The AIoT reader sends an R2D message (including a command request NAS PDU, and optionally, information about a second IoT device) to the IoT device.

[0251] This step is the same as step S1202, and will not be repeated here.

[0252] S1403. In response to not receiving a D2R message from the IoT device, the AIoT reader performs at least one of the following: triggers an inventory service for the IoT device, or triggers a command service for the IoT device.

[0253] This step is the same as step S1205, and will not be repeated here.

[0254] In this implementation, if an IoT device fails to respond, the IoT device triggers an inventory service for the failed IoT device, and / or triggers a command service for the failed IoT device. This can attempt to restore communication with the failed IoT device, which helps improve the success rate of the IoT device's response and enhances the service quality of the command service.

[0255] Figure 15 is a schematic diagram of the fourth communication method provided in the embodiments of this application. The AIOTF network element in Figure 15 can be the AIOTF network element in Figure 1, or it can refer to a device (e.g., processor, chip, or chip system) within the AIOTF network element. The AIoT reader in Figure 15 can be the AIoT reader in Figure 1, or it can refer to a device (e.g., processor, chip, or chip system) within the AIoT reader. The IoT device in Figure 15 can be the IoT device in Figure 1, or it can refer to a device (e.g., processor, chip, or chip system) within the IoT device. As shown in Figure 15, the communication method 1500 includes the following steps S1501-S1503:

[0256] S1501, the AIOTF network element sends a command request message (including the association identifier and command request NAS PDU, and optionally, the first IoT device information) to the AIoT reader, and starts the AIoT NAS timer.

[0257] This step is described in accordance with S1201 and will not be repeated here.

[0258] S1502, The AIoT reader sends an R2D message (including a command request NAS PDU, and optionally, information about a second IoT device) to the IoT device.

[0259] This step is described in S1202 and will not be repeated here.

[0260] S1503. In response to not receiving a command response message including the first IoT device information and the command response NAS PDU within a preset time, the AIOTF network element performs at least one of the following: triggers the execution of an inventory service for the IoT device, triggers the execution of a command service for the IoT device, and sends the IoT device identifier and response failure indication information to the AF network element.

[0261] This step is described in accordance with S1206 and will not be repeated here.

[0262] In this implementation, in the event of an IoT device failure to respond, in response to an AIoT NAS timer timeout, the AIOTF network element triggers an inventory service for the failed IoT device, and / or, the AIOTF network element triggers a command service for the failed IoT device. This can attempt to restore communication with the failed IoT device, helping to improve the success rate of IoT device responses and enhance the service quality of the command service. The AIOTF network element sends the IoT device identifier and response failure indication information to the AF network element, enabling the AF network element to determine which IoT device failed based on the IoT device identifier and the reason for the response failure. This allows the AF network element to adjust the state of the failed IoT device, such as enabling it.

[0263] Figure 16 is a schematic diagram of the fifth communication method provided in the embodiments of this application. The AIOTF network element in Figure 16 can be the AIOTF network element in Figure 1, or it can refer to a device (e.g., processor, chip, or chip system) within the AIOTF network element. The AIoT reader in Figure 16 can be the AIoT reader in Figure 1, or it can refer to a device (e.g., processor, chip, or chip system) within the AIoT reader. The IoT device in Figure 16 can be the IoT device in Figure 1, or it can refer to a device (e.g., processor, chip, or chip system) within the IoT device. As shown in Figure 16, the communication method 1600 includes the following steps S1601-S1606:

[0264] S1601, the AIOTF network element sends an inventory request message (including the associated identifier, optionally including the IoT device identifier) ​​to the AIoT reader.

[0265] This step is described in accordance with S1001 and will not be repeated here.

[0266] S1602, The AIoT reader sends a paging message to the IoT device (optionally, including the IoT device identifier).

[0267] This step is the same as S1002 and will not be repeated here.

[0268] S1603, the AIoT reader sends R2D messages (e.g., R2D trigger messages) to IoT devices.

[0269] This step is described in accordance with S1003 and will not be repeated here.

[0270] S1604. The IoT device sends an RN16 message (including RN16) to the AIoT reader.

[0271] This step is described in accordance with S1004 and will not be repeated here.

[0272] S1605, the AIoT reader sends MSG2 messages (including RN16) to IoT devices.

[0273] This step is described in accordance with S1005 and will not be repeated here.

[0274] S1606. The IoT device sends a D2R message (including inventory results NAS PDU) to the AIoT reader.

[0275] This step is described in accordance with S1006 and will not be repeated here.

[0276] S1607, the AIoT reader sends an inventory report message (including the association identifier, AIoT reader identifier, and inventory result NAS PDU) to the AIOTF network element.

[0277] This step is described in accordance with S1007 and will not be repeated here.

[0278] S1608 and AIOTF network elements send command request messages (including association identifier and command request NAS PDU, as well as information on the first IoT device) to the AIoT reader and start the AIoT NAS timer.

[0279] This step is described in accordance with S1201 and will not be repeated here.

[0280] S1609, the AIoT reader sends R2D messages (including command request NAS PDU, and also includes information about the second IoT device) to IoT devices.

[0281] This step is described in S1202 and will not be repeated here.

[0282] S1610, The IoT device sends a D2R message (including a command response NAS PDU and information about the second IoT device) to the AIoT reader.

[0283] This step is described in accordance with S1203 and will not be repeated here.

[0284] S1611. In response to receiving a D2R message from an IoT device, the AIoT reader sends a command response message (including the association identifier, first IoT device information, and command response NAS PDU) to the AIOTF network element.

[0285] This step is described in accordance with S1204 and will not be repeated here.

[0286] S1612. In response to not receiving a D2R message from an IoT device, the AIoT reader sends a command response message (including the association identifier, the first IoT device information, and the reason for the response failure) to the AIOTF network element.

[0287] This step is described in accordance with S1205 and will not be repeated here.

[0288] S1613. In response to receiving a command response message including information about the first IoT device and the reason for the response failure, the AIOTF network element performs at least one of the following: triggers an inventory service for the IoT device, or triggers a command service for the IoT device.

[0289] This step is described in accordance with S1206 and will not be repeated here.

[0290] This implementation combines an inventory service process and a command service process. It explains how the AIOTF network element obtains the first IoT device information through the inventory service process. In the command service process, the IoT device does not need to parse the command request NAS PDU in the R2D message to obtain the IoT device identifier to determine whether the R2D message was sent to it. Instead, it can determine whether the R2D message was sent to it based on the second IoT device information in the R2D message, thereby reducing the power consumption of the IoT device. Furthermore, in response to receiving a command response message including the first IoT device information and the reason for the response failure, the AIOTF network element determines which IoT device failed to respond and for what reason, based on the first IoT device information and the reason for the response failure. The AIOTF network element triggers an inventory service for the IoT device that failed to respond, and / or triggers a command service for the IoT device that failed to respond, which can attempt to restore communication with the IoT device that failed to respond, helping to improve the success rate of IoT device responses and improve the service quality of the command service.

[0291] Figure 17 is a schematic diagram of a communication device provided in an embodiment of this application. The communication device 1700 may include a communication module 1710. The communication module 1710 can implement corresponding communication functions, which can be internal communication functions of the communication device 1700 or communication functions between the communication device 1700 and other devices. Optionally, the communication module 1710 may also be referred to as a communication interface or a transceiver module. Optionally, the communication device 1700 further includes a processing module 1720. The processing module 1720 can implement corresponding processing functions.

[0292] Optionally, the communication device 1700 further includes a storage module 1730, which can be used to store instructions and / or data; the processing module 1720 can read the instructions and / or data in the storage module 1730 so that the communication device 1700 can implement the aforementioned method embodiment.

[0293] In one possible design, the communication device 1700 may correspond to the AIoT reader in the above method embodiments, or to a component (such as a circuit, chip, or chip system) configured in the AIoT reader. The communication device 1700 may be used to perform the steps or processes performed by the AIoT reader in any of the above method embodiments.

[0294] For example, the communication module 1710 is used to send a command request NAS PDU to an IoT device. If no command response NAS PDU is received from the IoT device, at least one of the following is performed: triggering an inventory service to the IoT device, triggering a command service to the IoT device, and sending first IoT device information and a response failure reason to the AIOTF network element, wherein the first IoT device information is used to instruct the IoT device when the AIoT reader communicates with the AIOTF network element.

[0295] In one possible implementation, the communication module 1710 is used to send an R2D message to an IoT device, the R2D message including second IoT device information, the second IoT device information being used to instruct the IoT device when the AIoT reader communicates with the IoT device.

[0296] In one possible implementation, the communication module 1710 is used to send an R2D message to an IoT device. The R2D message includes a command request NAS PDU and second IoT device information, which is used to instruct the IoT device when the AIoT reader communicates with the IoT device.

[0297] In one possible implementation, the second IoT device information is the IoT device's access layer identifier or inventory result NAS PDU.

[0298] In one possible implementation, the communication module 1710 is configured to receive a command request NAS PDU and the first IoT device information from the AIOTF network element after sending the first IoT device information and the response failure reason to the AIOTF network element.

[0299] In one possible implementation, the first IoT device information is a next-generation application protocol identifier.

[0300] In one possible implementation, the communication module 1710 is used to receive service level information from the AIOTF network element, the service level information being used to indicate the reliability level of the command service; and to perform at least one of the following based on the service level information: triggering an inventory service for the IoT device, triggering a command service for the IoT device, and sending first IoT device information and a response failure reason to the AIOTF network element.

[0301] In one possible implementation, the communication module 1710 is configured to send first IoT device information and a response failure reason to the AIOTF network element if the service level information indicates that the reliability level of the command service is low; if the service level information indicates that the reliability level of the command service is medium, trigger an inventory service to be performed on the IoT device, or trigger a command service to be performed on the IoT device; if the service level information indicates that the reliability level of the command service is high, trigger an inventory service to be performed on the IoT device, and trigger a command service to be performed on the IoT device.

[0302] In one possible implementation, the communication module 1710 is used to send an inventory report message to the AIOTF network element before sending a command request NAS PDU to the IoT device. The inventory report message includes information about the first IoT device.

[0303] In one possible design, the communication device 1700 may correspond to the AIOTF network element in the above method embodiments, or a component (such as a circuit, chip, or chip system) configured in the AIOTF network element. The communication device 1700 can be used to perform the steps or processes performed by the AIOTF network element in any of the above method embodiments.

[0304] For example, the communication module 1710 is used to send a command request NAS PDU to the AIoT reader; in response to receiving the first IoT device information and the reason for the response failure from the AIoT reader, or in response to not receiving the first IoT device information and the command response NAS PDU from the AIoT reader within a preset time, it performs at least one of the following: triggering an inventory service for the IoT device, triggering a command service for the IoT device, and sending the IoT device identifier and the response failure indication information to the application function AF network element.

[0305] In one possible implementation, the communication module 1710 is used to send an inventory request message to the AIoT reader, the inventory request message including the IoT device identifier.

[0306] In one possible implementation, the communication module 1710 is used to send a command request message to the AIoT reader, the command request message including a command request NAS PDU and information about the first IoT device.

[0307] In one possible implementation, the first IoT device information is a next-generation application protocol identifier.

[0308] In one possible implementation, the communication module 1710 is used to send service level information to the AIoT reader, the service level information being used to indicate the reliability level of the command service.

[0309] In one possible implementation, the communication module 1710 is configured to receive an inventory report message from the AIoT reader before sending a command request NAS PDU to the AIoT reader. The inventory report message includes information about the first IoT device.

[0310] In one possible design, the communication device 1700 may correspond to the AIoT reader in the above method embodiments, or to a component (such as a circuit, chip, or chip system) configured in the AIoT reader. The communication device 1700 may be used to perform the steps or processes performed by the AIoT reader in any of the above method embodiments.

[0311] For example, the communication module 1710 is used to receive a command request NAS PDU and first IoT device information from an AIOTF network element, the first IoT device information being used to instruct the IoT device when the AIoT reader communicates with the AIOTF network element; and to send a command request NAS PDU and second IoT device information to the IoT device, the second IoT device information being used to instruct the IoT device when the AIoT reader communicates with the IoT device.

[0312] In one possible implementation, the communication module 1710 is used to receive command response NAS PDU from the Internet of Things (IoT) device and information about the second IoT device; and to send command response NAS PDU and information about the first IoT device to the AIOTF network element.

[0313] In one possible implementation, the communication module 1710 is used to send an inventory report message to the AIOTF network element, the inventory report message including information about the first Internet of Things device.

[0314] In one possible implementation, the first IoT device information is a next-generation application protocol identifier.

[0315] In one possible implementation, the second IoT device information is the IoT device's access layer identifier or inventory result NAS PDU.

[0316] In one possible design, the communication device 1700 may correspond to the AIOTF network element in the above method embodiments, or a component (such as a circuit, chip, or chip system) configured in the AIOTF network element. The communication device 1700 can be used to perform the steps or processes performed by the AIOTF network element in any of the above method embodiments.

[0317] For example, the communication module 1710 is used to send a command request NAS PDU and first IoT device information to the AIoT reader, the first IoT device information being used to instruct the IoT device when the AIoT reader communicates with the AIOTF network element; and to receive a command response NAS PDU and first IoT device information from the AIoT reader.

[0318] In one possible implementation, the communication module 1710 is used to receive an inventory report message from the AIoT reader, the inventory report message including information about the first IoT device.

[0319] In one possible implementation, the first IoT device information is a next-generation application protocol identifier.

[0320] Figure 18 is a schematic diagram of another communication device provided in an embodiment of this application. The communication device 1800 may be an AIoT reader or network device implementing the above methods, including chips, chip systems, or processors. The communication device 1800 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0321] As shown in Figure 18, the communication device 1800 may include one or more processors 1810, which may also be referred to as processing units or processing modules, and can implement certain control functions. The processor 1810 can be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, while the central processing unit can be used to control the communication device 1800 (e.g., a base station, baseband chip, user, user chip), execute software programs, and process data from the software programs.

[0322] In an alternative design, the processor 1810 may also store instructions and / or data, which can be executed by the processor 1810 to cause the communication device 1800 to perform the methods described in the above method embodiments.

[0323] In another alternative design, the communication device 1800 may include a communication interface 1820 for implementing receiving and transmitting functions. For example, the communication interface 1820 may be a transceiver circuit, interface, interface circuit, or transceiver. The transceiver circuit, interface, interface circuit, or transceiver for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, interface circuit, or transceiver may be used for reading and writing code / data, or it may be used for transmitting or relaying signals.

[0324] Optionally, the communication device 1800 may include one or more memories 1830, which may store instructions that can be executed on the processor 1810, causing the communication device 1800 to perform the methods described in the above method embodiments. Optionally, the memories 1830 may also store data. Optionally, the processor 1810 may also store instructions and / or data. The processor 1810 and the memories 1830 may be provided separately or integrated together.

[0325] It should be understood that, in one possible design, the steps in the method embodiments provided in this application can be implemented by integrated logic circuits in the processor's hardware or by instructions in software form. The steps of the methods disclosed in the embodiments of this application can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are not provided here.

[0326] In one implementation, the communication device 1800 may correspond to the AIoT reader in the above method embodiments and may be used to execute the various steps and / or processes executed by the AIoT reader in the above method embodiments. The processor 1810 may be used to execute instructions stored in the memory 1830, and when the processor 1810 executes the instructions stored in the memory, the processor 1810 is used to execute the various steps and / or processes of the above method embodiments corresponding to the AIoT reader.

[0327] In another implementation, the communication device 1800 may correspond to the AIOTF network element in the above method embodiments, and may be used to execute the various steps and / or processes executed by the AIOTF network element in the above method embodiments. The processor 1810 may be used to execute instructions stored in the memory 1830, and when the processor 1810 executes the instructions stored in the memory, the processor 1810 is used to execute the various steps and / or processes of the above method embodiments corresponding to the AIOTF network element.

[0328] It should be understood that the aforementioned processor can be one or more chips. For example, the processor can be a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), a system-on-chip (SoC), a central processing unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chips.

[0329] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0330] According to the method provided in the embodiments of this application, this application also provides a processor, including: an input circuit, an output circuit, and a processing circuit. The processing circuit is used to receive signals through the input circuit and transmit signals through the output circuit, causing the processor to execute the method described in the embodiments of this application.

[0331] In specific implementation, the processor can be one or more chips, the input circuit can be input pins, the output circuit can be output pins, and the processing circuit can be transistors, gate circuits, flip-flops, and various logic circuits. The input signal received by the input circuit can be received and input by, for example, but not limited to, a receiver, and the signal output by the output circuit can be, for example, but not limited to, output to and transmitted by a transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, which is used as both the input circuit and the output circuit at different times. This application does not limit the specific implementation of the processor and various circuits.

[0332] According to the method provided in the embodiments of this application, this application also provides a chip system, which includes one or more processors for calling and executing instructions stored in memory, thereby causing the method described in the embodiments of this application to be executed. The chip system may be composed of chips or may include chips and other discrete devices.

[0333] The chip system may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.

[0334] According to the method provided in the embodiments of this application, this application also provides a communication system, which includes the aforementioned network device, AIoT reader, and AIOTF network element.

[0335] According to the method provided in the embodiments of this application, this application also provides a computer program product, which includes: computer program code, which, when run on a computer, causes the computer to execute the various steps or processes executed by the network device, AIoT reader, or AIOTF network element in any of the foregoing method embodiments.

[0336] According to the method provided in the embodiments of this application, this application also provides a computer-readable storage medium storing program code. When the program code is run on a computer, it causes the computer to execute the various steps or processes performed by the network device, AIoT reader, or AIOTF network element in any of the foregoing method embodiments.

[0337] The computer-readable storage medium may be the aforementioned volatile memory or non-volatile memory, or it may include both volatile memory and non-volatile memory.

[0338] In the embodiments of this application, the terms and English abbreviations are exemplary examples given for ease of description and should not be construed as limiting the application in any way. This application does not preclude the possibility of defining other terms that can achieve the same or similar functions in existing or future agreements.

[0339] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated.

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

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

[0342] In summary, the above description is merely a preferred embodiment of the technical solution of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A communication method, characterized in that, The method, applied to an environmental IoT (AIoT) reader, includes: Send a command request to an IoT device for a Non-Access Stratum Protocol Data Unit (NAS PDU); In response to the absence of a command response NAS PDU from the IoT device, at least one of the following is performed: triggering an inventory service for the IoT device, triggering a command service for the IoT device, and sending first IoT device information and a response failure reason to the AIOTF network element, wherein the first IoT device information is used to instruct the IoT device when the AIoT reader communicates with the AIOTF network element.

2. The method according to claim 1, characterized in that, The triggering of the inventory service for the IoT device includes: An R2D message is sent to the IoT device, the R2D message including second IoT device information, the second IoT device information being used to instruct the IoT device when the AIoT reader communicates with the IoT device.

3. The method according to claim 1 or 2, characterized in that, The triggering of the command service to the IoT device includes: Send an R2D message to the IoT device, the R2D message including the command request NAS PDU and second IoT device information, the second IoT device information being used to instruct the IoT device when the AIoT reader communicates with the IoT device.

4. The method according to claim 2 or 3, characterized in that, The second IoT device information is the access layer identifier or inventory result NAS PDU of the IoT device.

5. The method according to any one of claims 1-4, characterized in that, After sending the first IoT device information and the reason for the response failure to the AIOTF network element of the environmental IoT function, it also includes: Receive command request NAS PDU and the first IoT device information from the AIOTF network element.

6. The method according to any one of claims 1-5, characterized in that, The first IoT device information is a next-generation application protocol identifier.

7. The method according to any one of claims 1-6, characterized in that, Also includes: Receive service level information from the AIOTF network element, the service level information being used to indicate the reliability level of the command service; Based on the service level information, perform at least one of the following: trigger an inventory service for the IoT device, trigger a command service for the IoT device, and send the first IoT device information and the reason for the failure to the AIOTF network element.

8. The method according to claim 7, characterized in that, The step of performing at least one of the following based on the service level information includes: triggering an inventory service for the IoT device, triggering a command service for the IoT device, and sending first IoT device information and a response failure reason to the AIOTF network element, including: If the service level information indicates that the reliability level of the command service is low, then the first IoT device information and the reason for the failure are sent to the AIOTF network element. If the service level information indicates that the reliability level of the command service is medium, then an inventory service is triggered for the IoT device, or a command service is triggered for the IoT device. If the service level information indicates that the reliability level of the command service is high, then an inventory service is triggered for the IoT device, and a command service is triggered for the IoT device.

9. The method according to any one of claims 1-8, characterized in that, Before sending a command to the IoT device to request a Non-Access Stratum Protocol Data Unit (NAS PDU), the following steps are also included: An inventory report message is sent to the AIOTF network element, and the inventory report message includes the information of the first IoT device.

10. A communication method, characterized in that, The method, applied to AIOTF network elements for environmental Internet of Things (IoT) functions, includes: Send a command request to the AIoT reader for a Non-Access Stratum Protocol Data Unit (NAS PDU); In response to receiving the first IoT device information and response failure reason from the AIoT reader, or in response to not receiving the first IoT device information and command response NAS PDU from the AIoT reader within a preset time, perform at least one of the following: trigger the execution of inventory service on the IoT device, trigger the execution of command service on the IoT device, and send the IoT device identifier and response failure indication information to the application function AF network element.

11. The method according to claim 10, characterized in that, The triggering of the inventory service for the IoT device includes: Send an inventory request message to the AIoT reader, the inventory request message including the IoT device identifier.

12. The method according to claim 10 or 11, characterized in that, The triggering of the command service to the IoT device includes: Send a command request message to the AIoT reader. The command request message includes the command request NAS PDU and the information of the first IoT device.

13. The method according to any one of claims 10-12, characterized in that, The first IoT device information is a next-generation application protocol identifier.

14. The method according to any one of claims 10-13, characterized in that, Also includes: Service level information is sent to the AIoT reader, which indicates the reliability level of the command service.

15. The method according to any one of claims 10-14, characterized in that, Before sending a command request for a Non-Access Stratum Protocol Data Unit (NAS PDU) to the AIoT reader for the environment, the following is also included: Receive an inventory report message from the AIoT reader, the inventory report message including the information of the first IoT device.

16. A communication method, characterized in that, The method, applied to an environmental IoT (AIoT) reader, includes: The device receives a Command Request Non-Access Stratum Protocol Data Unit (NAS PDU) and first IoT device information from an AIOTF network element. The first IoT device information is used to instruct the IoT device when the AIoT reader communicates with the AIOTF network element. The command request NAS PDU and second IoT device information are sent to the IoT device, the second IoT device information being used to instruct the IoT device when the AIoT reader communicates with the IoT device.

17. The method according to claim 16, characterized in that, Also includes: Receive command response NAS PDU from the IoT device and information from the second IoT device; Send the command response NAS PDU and the information of the first IoT device to the AIOTF network element.

18. The method according to claim 16 or 17, characterized in that, Before receiving the command request non-access stratum protocol data unit (NAS PDU) and the first IoT device information from the AIOTF network element, the following is also included: An inventory report message is sent to the AIOTF network element, and the inventory report message includes the information of the first IoT device.

19. The method according to any one of claims 16-18, characterized in that, The first IoT device information is a next-generation application protocol identifier.

20. The method according to any one of claims 16-19, characterized in that, The second IoT device information is the access layer identifier or inventory result NAS PDU of the IoT device.

21. A communication method, characterized in that, The method, applied to AIOTF network elements for environmental Internet of Things (IoT) functions, includes: Send a command request to the AIoT reader for a Non-Access Layer Protocol Data Unit (NAS PDU) and first IoT device information, wherein the first IoT device information is used to instruct the IoT device when the AIoT reader communicates with the AIOTF network element. Receive command response NAS PDU and information about the first IoT device from the AIoT reader.

22. The method according to claim 21, characterized in that, Sending a command to the environmental IoT AIoT reader to request a Non-Access Stratum Protocol Data Unit (NAS PDU) and information about the first IoT device also includes: Receive an inventory report message from the AIoT reader, the inventory report message including the information of the first IoT device.

23. The method according to claim 21 or 22, characterized in that, The first IoT device information is a next-generation application protocol identifier.

24. A communication device, characterized in that, The device includes a processor and a memory, wherein the memory stores instructions, and when the processor executes the instructions, the communication device performs the method as described in any one of claims 1-9, or performs the method as described in any one of claims 10-15, or performs the method as described in any one of claims 16-20, or performs the method as described in any one of claims 21-23.

25. A computer-readable storage medium having a computer program or instructions stored thereon, characterized in that, When the computer program or instructions are executed, they cause the computer to perform the method as described in any one of claims 1-9, or to perform the method as described in any one of claims 10-15, or to perform the method as described in any one of claims 16-20, or to perform the method as described in any one of claims 21-23.

Images