A communication method and apparatus

Abstract

A communication method and device are used to determine a permanent identifier of an AIoT terminal in the case of repeated temporary identifiers of the AIoT terminal. The method comprises: a first device sending a first request, the first request being used to request inventory one or more environmental Internet of Things devices; the first device receiving a first temporary identifier and first verification information of a first environmental Internet of Things device, the one or more environmental Internet of Things devices comprising the first environmental Internet of Things device, the first verification information being used to verify the identity of the first environmental Internet of Things device; the first device obtaining an identity verification result of the first environmental Internet of Things device according to the first verification information; and the first device determining a permanent identifier of the first environmental Internet of Things device corresponding to the first temporary identifier according to the identity verification result of the first environmental Internet of Things device.

Description

Technical Field

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

[0002] In the Ambient Internet of Things (AIoT), some network nodes can obtain energy and communicate using methods such as solar, radio frequency, wind, hydro, or tidal power. Terminals in an AIoT network can be called AIoT terminals or tags. AIoT terminals can provide their identifiers (IDs) to the network through an inventory process. To avoid exposing the permanent identifier of the AIoT terminal, a temporary identifier is provided to the access network during the inventory process. The access network then provides this temporary identifier to the core network, which determines the permanent identifier based on the temporary identifier. The temporary identifier is obtained from the permanent identifier of the AIoT terminal.

[0003] Currently, when temporary identifiers are generated by AIoT terminals, there are scenarios where different AIoT terminals generate the same temporary identifier, which affects the accuracy of inventory. Therefore, efforts are needed to improve the accuracy of inventory results. Summary of the Invention

[0004] This application provides a communication method and apparatus for determining the permanent identifier of an AIoT terminal when the temporary identifier of the AIoT terminal is repeated.

[0005] Firstly, a communication method is provided. This method can be implemented by a first device or a component within the first device, which may also be referred to as a communication apparatus or network element. The first device is, for example, an environmental Internet of Things (IoT) functional network element. The components in this application may include, for example, at least one of a chip, chip system, processor, transceiver, processing unit, or transceiver unit. Taking the first device as the executing entity as an example, the method can be implemented through the following steps:

[0006] A first device sends a first request, which is used to request the inventory of one or more environmental IoT devices; the first device receives a first temporary identifier and first verification information of a first environmental IoT device, wherein the one or more environmental IoT devices include the first environmental IoT device, and the first verification information is used to verify the identity of the first environmental IoT device; the first device obtains the identity verification result of the first environmental IoT device based on the first verification information; the first device determines the permanent identifier of the first environmental IoT device corresponding to the first temporary identifier based on the identity verification result of the first environmental IoT device.

[0007] Based on the method described in the first aspect, the first temporary identifier of the first environmental IoT device may correspond to multiple permanent identifiers. The first device can verify the identity of the first environmental IoT device based on the first verification information, and determine the permanent identifier of the first environmental IoT device from multiple permanent identifiers based on the identity verification result, so as to improve the accuracy of the inventory results.

[0008] Among them, environmental IoT devices are, for example, AIoT terminals.

[0009] In one possible implementation, before determining the permanent identifier of the first environmental IoT device corresponding to the first temporary identifier based on the authentication result of the first environmental IoT device, the method further includes: the first device determining that the permanent identifier corresponding to the first temporary identifier includes a first permanent identifier and a second permanent identifier, and the permanent identifier of the first environmental IoT device corresponding to the first temporary identifier is the first permanent identifier or the second permanent identifier.

[0010] Based on this implementation, the first device can obtain the aforementioned authentication result when the first temporary identifier of the first environmental IoT device corresponds to the first permanent identifier and the second permanent identifier, and determine the permanent identifier of the first environmental IoT device based on the authentication result. Therefore, the above method can be triggered under appropriate circumstances to determine the permanent identifier of the first environmental IoT device.

[0011] In one possible implementation, obtaining the authentication result of the first environmental IoT device based on the first verification information includes: the first device sending a first verification request to the second device, the first verification request including the first verification information and the first permanent identifier, the first verification request being used to request verification of the identity of the first environmental IoT device based on the first verification information and the first permanent identifier; the first device receiving a first verification response, the first verification response including the authentication result.

[0012] Based on this implementation, the first device can send a first verification request to the second device, requesting the second device to verify the identity of the first environmental IoT device based on the first verification information and the first permanent identifier, in order to obtain the identity verification result. Correspondingly, the second device can verify the identity of the first environmental IoT device based on the first verification information and the first permanent identifier, thereby determining the identity verification result for the first environmental IoT device based on the first verification information. This allows for a reasonable determination of the identity verification result, thus improving the accuracy of determining the permanent identifier in the first verification information.

[0013] In one possible implementation, obtaining the authentication result of the first environmental IoT device based on the first verification information includes: the first device sending a second verification information request to the second device, the second verification information request including the first permanent identifier and verification information input parameters, the first verification information being determined based on the verification information input parameters, and the second verification information request being used to request the second verification information; the first device receiving the second verification information, the second verification information being determined based on the key of the first environmental IoT device and the verification information input parameters, the key of the first environmental IoT device being determined based on the first permanent identifier; and the first device determining the authentication result based on the first verification information and the second verification information.

[0014] Based on this implementation, the first device can send a second verification information request to the second device to request the second verification information, so that the first device can obtain the authentication result based on the first verification information and the second verification information. Correspondingly, the second device can determine and send the second verification information to the first device based on the verification information input parameters and the first permanent identifier. The first device determines the authentication result of the first IoT device based on the first verification information, thus enabling a reasonable determination of the authentication result and improving the accuracy of determining the permanent identifier of the first verification information.

[0015] Optionally, in the above first verification request and / or second verification information request, the first permanent identifier can also be replaced with a first temporary identifier. Alternatively, the first device can send a verification request to the second device, which includes the first temporary identifier and first verification information of the first environmental IoT device; this verification request can refer to the description of the first verification request. Alternatively, the first device can send a verification information request to the second device, which includes the first temporary identifier and first verification information of the first environmental IoT device; this verification information request can refer to the description of the second verification information request. The second device can store, maintain, or parse the correspondence between the temporary identifier and the permanent identifier of the environmental IoT device, and upon receiving the verification request, determine the first permanent identifier corresponding to the first temporary identifier based on the first temporary identifier. Then, the second device can determine the verification result by referring to the verification method after receiving the above first verification request. Similarly, the verification information request can include the first temporary identifier and verification information input parameters; the second device can, upon receiving the verification information request, determine the first permanent identifier corresponding to the first temporary identifier based on the first temporary identifier and the correspondence between the temporary identifier and the permanent identifier of the environmental IoT device. The second device can then refer to the verification method after receiving the second verification information request to determine and provide the second verification information to the first device, so that the first device can determine the verification result based on the first verification information and the second verification information.

[0016] In one possible implementation, determining the permanent identifier of the first environmental IoT device corresponding to the first temporary identifier based on the authentication result of the first environmental IoT device includes: determining the first permanent identifier as the permanent identifier of the first environmental IoT device when the authentication result of the first environmental IoT device indicates that the authentication of the first environmental IoT device is successful.

[0017] Based on this implementation method, when the authentication result of the first environmental IoT device corresponding to the first permanent identifier and the first verification information indicates that the first environmental IoT device has passed the authentication, the first permanent identifier can be determined as the permanent identifier of the first environmental IoT device, and the accurate determination of the permanent identifier of the first environmental IoT device can be achieved.

[0018] In one possible implementation, the first device may also send a second verification request to the second device. The second verification request includes the first verification information and the second permanent identifier. The second verification request is used to request verification of the identity of the first environmental IoT device based on the first verification information and the second permanent identifier. The first device may also receive a second verification response, which is used to indicate the verification result of the first environmental IoT device's identity verification failure.

[0019] Based on this implementation, the first device can send a second verification request to the second device, requesting the second device to verify the identity of the first environmental IoT device based on the first verification information and the second permanent identifier, thereby obtaining the authentication result. Correspondingly, the second device can determine the verification result based on the first verification information and the second permanent identifier, and send a second verification response to the first device. The second verification response can indicate the verification failure result. Therefore, if the authentication result of the first environmental IoT device based on the first verification information and the second permanent identifier indicates a verification failure, it can be determined that the second permanent identifier is not the permanent identifier of the first environmental IoT device, thus avoiding the determination of an incorrect permanent identifier for the first environmental IoT device.

[0020] In one possible implementation, the first device may also send a third verification information request to the second device. The third verification information request includes the second permanent identifier and verification information input parameters. The first verification information is determined based on the verification information input parameters. The third verification information request is used to request third verification information. The first device may also receive the third verification information, which is determined based on the second permanent identifier and the verification information input parameters. The first device may also determine that the authentication of the first environmental IoT device has failed based on the first verification information and the third verification information.

[0021] Based on this implementation, the first device can send a third verification information request to the second device to request third verification information. Correspondingly, the second device can determine and send the third verification information to the first device based on the verification information input parameters and the second permanent identifier. Then, the first device determines that the authentication of the first environmental IoT device has failed, i.e., the authentication result is verification failure, based on the first verification information corresponding to the second permanent identifier. Therefore, when the authentication result for the first environmental IoT device based on the first verification information indicates that the first environmental IoT device has failed, it can be determined that the second permanent identifier is not the permanent identifier of the first environmental IoT device, thus avoiding the determination of an incorrect permanent identifier for the first environmental IoT device.

[0022] Optionally, at least two of the first verification request, the second verification information request, or the third verification information request can be carried in the same message.

[0023] In one possible implementation, determining that the permanent identifier corresponding to the first temporary identifier includes a first permanent identifier and a second permanent identifier includes: a first device determining, based on the first temporary identifier and an identifier correspondence, that the permanent identifier corresponding to the first temporary identifier includes a first permanent identifier and a second permanent identifier, wherein the identifier correspondence includes a correspondence between multiple temporary identifiers and multiple permanent identifiers, wherein the multiple temporary identifiers include the first temporary identifier, and the multiple permanent identifiers include the first permanent identifier and the second permanent identifier.

[0024] Based on this implementation method, the first device can determine the permanent identifier corresponding to the first temporary identifier according to the identifier correspondence relationship, so as to accurately determine the permanent identifier corresponding to the first temporary identifier.

[0025] In one possible implementation, the first device may further send a temporary identifier request to the second device, the temporary identifier request including a temporary identifier input parameter, the temporary identifier request being used to request obtaining a temporary identifier corresponding to the temporary identifier input parameter; the first device may also receive a temporary identifier response from the second device, the temporary identifier response including the first temporary identifier and the first permanent identifier, the first device may also store a correspondence between the first temporary identifier and the first permanent identifier, the identifier correspondence including the correspondence between the first temporary identifier and the first permanent identifier; or, the first device may further send a temporary identifier request to the second device, the temporary identifier request including the first permanent identifier and the temporary identifier input parameter, the temporary identifier request being used to request obtaining the first permanent identifier and a temporary identifier corresponding to the temporary identifier input parameter; the first device may also receive a temporary identifier response from the second device, the temporary identifier response including the first temporary identifier, the first device may also store a correspondence between the first temporary identifier and the first permanent identifier, the identifier correspondence including the correspondence between the first temporary identifier and the first permanent identifier.

[0026] Based on this implementation method, the first device can obtain the identifier correspondence through the second device, so as to realize the flexible determination of the identifier correspondence.

[0027] In one possible implementation, the first temporary identifier is determined by a first algorithm based on the permanent identifier and temporary identifier input parameters of the first environmental IoT device; the first verification information is determined by a second algorithm based on the key of the first environmental IoT device and verification information input parameters, wherein the key of the first environmental IoT device is determined based on the permanent identifier of the first environmental IoT device; wherein the temporary identifier input parameters and the verification information input parameters include at least one different parameter; and / or, the first algorithm and the second algorithm are different.

[0028] Based on this implementation, there is a correlation between the first environmental IoT device, the first temporary identifier, and the first verification information. Only the permanent identifier of the first environmental IoT device can ensure that the verification result of the first environmental IoT device for the first verification information is successful. Therefore, if the identity of the first environmental IoT device is verified through the first verification information or the second verification information, it can be determined that the first permanent identifier is the permanent identifier of the first environmental IoT device.

[0029] In one possible implementation, after determining that the first permanent identifier is the permanent identifier of the first environmental IoT device, the first device may send the first permanent identifier, or other identifiers of the first environmental IoT device that the third device can recognize, to the third device.

[0030] The third device can be an application function, such as an application server. For example, the above method can be executed during the inventory process to determine the permanent identifier of the first environmental IoT device and report the permanent identifier or other identifiers that the third device can recognize.

[0031] Secondly, a communication method is provided. This method can be implemented by a first device or a component within the first device, which may also be referred to as a communication device or network element. The first device is, for example, an environmental IoT functional network element. The components in this application may include, for example, at least one of a chip, chip system, processor, transceiver, processing unit, or transceiver unit. Taking the first device as the executing entity as an example, the method can be implemented through the following steps: the first device sends a first request, the first request being used to request inventory of one or more environmental IoT devices; the first device receives a first temporary identifier of a first environmental IoT device, the one or more environmental IoT devices including the first environmental IoT device; when the permanent identifier corresponding to the first temporary identifier includes at least two permanent identifiers, the first device determines a second temporary identifier based on the first permanent identifier among the at least two permanent identifiers; the first device sends a first operation request to the first environmental IoT device, the first operation request including the second temporary identifier, the first operation request being used to request the environmental IoT device corresponding to the second temporary identifier to perform a first operation; the first device determines the first permanent identifier as the permanent identifier of the first environmental IoT device based on the response information of the first operation request.

[0032] Based on the method shown in the second aspect, when the first temporary identifier of the first environmental IoT device corresponds to multiple permanent identifiers, the first device can request the first environmental IoT device to perform a first operation through the second temporary identifier corresponding to the first permanent identifier, and determine the first permanent identifier as the permanent identifier of the first environmental IoT device based on the response information of the first environmental IoT device performing the first operation, so as to achieve reasonable determination of the permanent identifier of the first environmental IoT device and improve the accuracy of inventory results.

[0033] In one possible implementation, determining the first permanent identifier as the permanent identifier of the first environmental IoT device based on the response information of the first operation request includes: determining the first permanent identifier as the permanent identifier of the first environmental IoT device upon receiving the response information of the first operation request.

[0034] Based on this implementation, the first device can determine the first permanent identifier as the permanent identifier of the first environmental IoT device upon receiving the response information of the first operation request. The first response information can be sent when the first environmental IoT device performs the first operation; that is, the response information indicates that the second temporary identifier in the first operation request is the temporary identifier corresponding to the first environmental IoT device, or in other words, the temporary identifier is determined based on the permanent identifier of the first environmental IoT device.

[0035] In one possible implementation, the response information to the first operation request can indicate whether the first environmental IoT device performs the first operation. For example, the response information to the first operation request includes information indicating success or information indicating failure. Wherein, if the response information includes information indicating success, the first device can determine that the first permanent identifier is a permanent identifier of the first environmental IoT device. If the response information includes information indicating failure, then the first permanent identifier is determined not to be a permanent identifier of the first environmental IoT device.

[0036] In one possible implementation, the first temporary identifier is determined by a first algorithm based on the permanent identifier of the first environmental IoT device and the first temporary identifier input parameters, and the second temporary identifier is determined by a third algorithm based on the first permanent identifier and the second temporary identifier input parameters; wherein the first temporary identifier input parameters are different from the second temporary identifier input parameters; and / or, the first algorithm is different from the third algorithm.

[0037] Based on this implementation, the temporary input parameters used to determine the first temporary identifier are different from the temporary input parameters used to determine the second temporary identifier, and / or the algorithm used to determine the first temporary identifier is different from the algorithm used to determine the second temporary identifier. Therefore, the first environmental IoT device can only perform the first operation when it requests the first environmental IoT device to perform the first operation based on the temporary identifier determined by the permanent identifier of the first environmental IoT device. That is, the first environmental IoT device will send a response message for the first operation request, or send a response message instructing the first environmental IoT device to perform the first operation, only when it requests the first environmental IoT device to perform the first operation based on the temporary identifier determined by the permanent identifier of the first environmental IoT device.

[0038] In one possible implementation, the first operation request may also include the second temporary identifier input parameter and / or the indication information of the third algorithm.

[0039] Based on this implementation, the second temporary identifier input parameters and / or the indication information of the third algorithm can be indicated through the first request, so there is no need to indicate the second temporary identifier input parameters and / or the third algorithm through additional signaling, thereby reducing the indication overhead.

[0040] In one possible implementation, the first device may further determine a third temporary identifier based on the second permanent identifier among the at least two permanent identifiers; the first device may further send a second operation request to the first environmental IoT device, the second operation request including the third temporary identifier, the third operation request being used to request the environmental IoT device corresponding to the third temporary identifier to perform a first operation; the first device may further determine, based on the response information of the second operation request, that the second permanent identifier is not a permanent identifier of the first environmental IoT device.

[0041] Based on this implementation, when the first temporary identifier of the first environmental IoT device corresponds to multiple permanent identifiers, the first device can request the first environmental IoT device to perform a first operation through the third temporary identifier corresponding to the second permanent identifier, and determine that the second permanent identifier is not a permanent identifier of the first environmental IoT device based on the response information of the second operation request, thereby avoiding the determination of an incorrect permanent identifier of the first environmental IoT device.

[0042] In one possible implementation, determining that the second permanent identifier is not a permanent identifier of the first environmental IoT device based on the response information of the second operation request includes: the first device can determine that the second permanent identifier is not a permanent identifier of the first environmental IoT device even if it has not received the response information of the second operation request.

[0043] Based on this implementation, the first device can determine that the second permanent identifier is not a permanent identifier of the first environmental IoT device if it does not receive a response to the second operation request. In one possible implementation, the response to the second operation request can instruct the first environmental IoT device not to perform the first operation; for example, the response to the second operation request includes information indicating that the operation failed.

[0044] In one possible implementation, the first temporary identifier is determined by a first algorithm based on the permanent identifier of the first environmental IoT device and the first temporary identifier input parameters, and the third temporary identifier is determined by a fourth algorithm based on the second permanent identifier and the third temporary identifier input parameters; wherein the first temporary identifier input parameters are different from the third temporary identifier input parameters; and / or, the first algorithm is different from the fourth algorithm.

[0045] Based on this implementation, the temporary input parameters used to determine the first temporary identifier are different from the temporary input parameters used to determine the third temporary identifier, and / or the algorithm used to determine the first temporary identifier is different from the algorithm used to determine the third temporary identifier. Therefore, the first environmental IoT device can only perform the first operation when it requests the first environmental IoT device to perform the first operation based on the temporary identifier determined by the permanent identifier of the first environmental IoT device. That is, the first environmental IoT device will send a response information for the first operation request, or send a response information instructing the first environmental IoT device to perform the first operation, only when it requests the first environmental IoT device to perform the first operation based on the temporary identifier determined by the permanent identifier of the first environmental IoT device.

[0046] In one possible implementation, the second operation request may also include the third temporary identifier input parameter and / or the indication information of the fourth algorithm.

[0047] Based on this implementation, the third temporary identifier input parameters and / or the indication information of the fourth algorithm can be indicated by the first request, so there is no need to indicate the third temporary identifier input parameters and / or the fourth algorithm through additional signaling, thereby reducing the indication overhead.

[0048] In one possible implementation, the first operation is an inventory operation. Therefore, the response information of the first operation may carry a temporary identifier of the first environmental IoT device, such as a second temporary identifier.

[0049] Thirdly, a communication method is provided. This method can be implemented by a first device or a component within the first device, which may also be referred to as a communication apparatus or network element. The first device is, for example, an environmental Internet of Things (IoT) functional network element. The components in this application may include, for example, at least one of a chip, chip system, processor, transceiver, processing unit, or transceiver unit. Taking the first device as the executing entity as an example, the method can be implemented through the following steps:

[0050] The first device obtains a first temporary identifier input parameter, which is used to determine a first temporary identifier for the first environmental IoT device. If the first temporary identifier corresponds to a permanent identifier, the first device sends the first temporary identifier input parameter.

[0051] Based on this implementation, the first device can send the first temporary identifier input parameter when it is determined that the temporary identifier of the first environmental IoT device does not correspond to multiple permanent identifiers. This allows the environmental IoT device to determine the temporary identifier based on the first temporary identifier input parameter, thus avoiding the environmental IoT device determining a temporary identifier corresponding to multiple permanent identifiers and preventing the temporary identifiers of multiple environmental IoT devices from being duplicated.

[0052] In one possible implementation, the method further includes: if the first temporary identifier corresponds to at least two permanent identifiers, the first device determines a fourth temporary identifier input parameter, the fourth temporary identifier input parameter being used to determine the fourth temporary identifier of the first AIoT terminal. If the fourth temporary identifier corresponds to one permanent identifier, the AIoTF sends the fourth temporary identifier input parameter to the first AIoT terminal.

[0053] Therefore, when the temporary identifier of an AIoT terminal corresponds to multiple permanent identifiers, the temporary identifier input parameter can be updated until the temporary identifier of the AIoT terminal, determined according to the updated temporary identifier input parameter, corresponds to a single permanent identifier.

[0054] Fourthly, a communication device is provided. The device can implement the methods described in any one of the first to third aspects and any possible implementation thereof. The device possesses the functions of the first device described above. The device is, for example, an environmental Internet of Things (IoT) functional network element, or a functional module or component (such as a chip) within an environmental IoT functional network element.

[0055] In one optional implementation, the device may include modules corresponding one-to-one with the methods / operations / steps / actions described in any one of the first to third aspects and any possible implementations thereof. These modules may be hardware circuits, software, or a combination of hardware circuits and software. In another optional implementation, the device includes a processing unit (sometimes also called a processing module) and a transceiver unit (sometimes also called a communication unit, transceiver module, communication module, etc.). The transceiver unit is capable of both sending and receiving functions. When the transceiver unit performs the sending function, it may be called a sending unit (sometimes also called a sending module); when it performs the receiving function, it may be called a receiving unit (sometimes also called a receiving module). The sending unit and the receiving unit may be the same functional module, referred to as the transceiver unit, which performs both sending and receiving functions; or, the sending unit and the receiving unit may be different functional modules, with the transceiver unit being a collective term for these functional modules.

[0056] For example, when the apparatus is used to perform the method described in any one of the first to third aspects, the apparatus may include a communication unit and a processing unit.

[0057] Fifthly, embodiments of this application also provide a communication device, including a processor for executing a computer program (or computer-executable instructions) stored in a memory, which, when executed, causes the device to perform the method as described in any one of the first to third aspects and any possible implementation thereof.

[0058] In one possible implementation, the processor and memory are integrated together;

[0059] In another possible implementation, the memory is located outside the communication device.

[0060] The communication device also includes a communication interface for communicating with other devices, such as sending or receiving data and / or signals. Exemplarily, the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface.

[0061] A sixth aspect provides a computer-readable storage medium for storing a computer program or instructions that, when executed, cause the method described in any of the first to third aspects and any possible implementation thereof, and the method shown in any possible implementation thereof, to be implemented.

[0062] In a seventh aspect, a computer program product containing instructions is provided, which, when run on a computer, enables the method described in any one of the first to third aspects and any possible implementation thereof to be implemented.

[0063] Eighthly, embodiments of this application also provide a communication device for performing the method described in any one of the first to third aspects and any possible implementation thereof.

[0064] Ninthly, a chip system is provided, comprising logic circuitry (or, as understood, a processor, which may include logic circuitry, etc.), and further comprising input / output interfaces. The input / output interfaces can be used to input messages or to output messages. The input / output interfaces can be the same interface, i.e., the same interface can implement both sending and receiving functions; or, the input / output interface includes an input interface and an output interface, the input interface being used to implement the receiving function, i.e., to receive messages; and the output interface being used to implement the sending function, i.e., to send messages. The logic circuitry can be used to perform operations other than the sending and receiving functions in the methods described in any of the first to third aspects and any possible implementations thereof; the logic circuitry can also be used to transmit messages to the input / output interfaces or to receive messages from other communication devices from the input / output interfaces. The chip system can be used to implement the methods described in any of the first to third aspects and any possible implementations thereof. The chip system can be composed of chips or can include chips and other discrete devices.

[0065] Optionally, the chip system may also include a memory, which can be used to store instructions, and the logic circuits can call the instructions stored in the memory to implement the corresponding functions.

[0066] In a tenth aspect, a communication method is provided, which may include the method implemented by a first device as shown in the first aspect and any possible implementation thereof, or the method implemented by a first device as shown in the second aspect and any possible implementation thereof.

[0067] Eleventhly, a communication system is provided, which may include a first device and a second device for implementing the methods shown in the first aspect and its possible implementations. Optionally, the system may further include a first environmental IoT device.

[0068] The technical effects brought about by aspects four through eleven above can be found in the descriptions of the beneficial effects of the corresponding solutions in aspects one through two above, and will not be repeated here. Attached Figure Description

[0069] Figure 1 This is a schematic diagram of an exemplary wireless communication system architecture;

[0070] Figures 2 to 7 These are schematic flowcharts of the communication methods provided in the embodiments of this application;

[0071] Figure 8 and Figure 9 These are schematic diagrams of the communication devices provided in the embodiments of this application. Detailed Implementation

[0072] This application can be applied to mobile communication systems or mobile network systems. The network architecture and service scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new service scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0073] The following explanations of some terms used in the embodiments of this application are provided to facilitate understanding by those skilled in the art.

[0074] 1. AIoT Network Architecture

[0075] AIoT networks can also be called environmentally powered IoT networks, environmental energy networks, or other names. In AIoT networks, some network nodes can obtain energy and communicate through solar, radio frequency, wind, hydro, or tidal power. Specifically, network nodes in an environmental IoT architecture can include AIoT terminals, readers, network elements, or servers.

[0076] In this context, the AIoT terminal can be an IoT device. The AIoT terminal can be in the form of a tag, or it can be a mobile phone, tablet, computer with wireless transceiver capabilities, wearable device, vehicle, urban aerial transportation (such as drones, helicopters, etc.), ship, robot, robotic arm, smart home device, or other terminal forms, without limitation. The AIoT terminal can also be called an environmental IoT device, AIoT device, or AIoT tag, etc. For ease of description, this application embodiment uses an AIoT terminal as an example for illustration.

[0077] For example, the application scenarios of AIoT networks may include, but are not limited to, the following scenarios:

[0078] (1) Warehouse, transportation or material management. In this scenario, AIoT tags can be embedded or affixed to goods and stored in warehouses, shopping malls, etc. During the logistics process, the relevant information of the goods is automatically collected by the reader. As a result, the managers can quickly query the information of the goods in the system, reduce the risk of loss or theft, improve the speed of goods handover, improve the accuracy, and prevent cross-selling and counterfeiting.

[0079] (2) Fixed Asset Management: Places with large assets or valuable items, such as libraries, art galleries, and museums, require complete management procedures or rigorous protection measures. When there are abnormal changes in the storage information of books or valuable items, the system should be able to notify the administrator immediately so that the relevant situation can be handled.

[0080] AIoT networks can be integrated with 4G mobile communication systems, 5G mobile communication systems, or future-oriented evolution systems, without specific limitations.

[0081] As an example, such as Figure 1 The diagram illustrates an AIoT network architecture. The server can be an application for AIoT services or an application server. Figure 1 In the architecture shown, the AIoT terminal can function as a terminal device. The AIoT function (AIoTF) network element and the Ambient Data Management (ADM) network element can be deployed in the core network.

[0082] The reader can serve as an access network device. The access network device can be a radio access network (RAN) device, such as a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next-generation NodeB (gNB) in a 5G mobile communication system, a base station in a future mobile communication system, or an access node in a wireless fidelity (WiFi) system. It can also be a module or unit that performs some of the functions of a base station, such as a central unit (CU) or a distributed unit (DU). The RAN device can be a macro base station, a micro base station, an indoor station, a relay node, or a donor node. The embodiments of this application do not limit the specific technology or device form used in the RAN device.

[0083] Optionally, the reader can also be used as a terminal to access the wireless access network. In this case, the AIoT terminal can access the network through the reader.

[0084] Optionally, network elements in the core network may also include unified data management (UDM) network elements, unified data repository (UDR) network elements, application function (AF) network elements, network exposure function (NEF) network elements, or access and mobility management function (AMF) network elements. It should be understood that AF network elements can also be deployed by third parties.

[0085] 2. AIoT terminals

[0086] AIoT devices are those that do not require batteries or have limited energy storage. AIoT devices can draw power from the environment to communicate with network devices, intermediate nodes, auxiliary nodes, or other terminal devices.

[0087] For example, AIoT terminals can include two types: Type 1 and Type 2. Type 1 AIoT terminals have an output power consumption of approximately 1 microwatt (μW), some energy storage capacity, but no downlink or uplink signal amplification capability. Type 1 terminals can only transmit information through backscattering of an externally provided carrier wave and cannot generate signals themselves.

[0088] Type 2 AIoT terminals have peak power not exceeding several hundred μW, possess energy storage capabilities, and can amplify downlink and / or uplink signals. Type 2 AIoT terminals can generate signals themselves or reflect signals through an external carrier.

[0089] AIoT terminals can also be other types of devices. For example, they may include devices without energy storage capabilities, and there are no restrictions on this. In this embodiment, "energy storage" can also be understood as energy storage.

[0090] In this application embodiment, the communication device used to implement the AIoT terminal function can be a terminal device or a device capable of supporting the terminal device to implement the function, such as a chip system. This device can be installed in the terminal device. In the technical solutions provided in this application embodiment, the terminal device is used as an example to describe the technical solutions provided in this application embodiment.

[0091] 3. Reader

[0092] Readers can conduct contactless two-way data communication via radio frequency (RF) to establish connections with devices, thereby achieving target identification and data exchange. Readers can also serve as access network devices to provide services to AIoT terminals. For example, readers can function as base stations, pole stations, micro base stations, macro base stations, etc. Furthermore, readers can also be terminal devices, such as mobile phones, IoT devices, and handheld readers.

[0093] 4. Network elements in an AIoT network can be deployed in the core network.

[0094] As an example, network elements in an AIoT network may include AIoTF network elements. These network elements can be deployed in the core network. AIoTF network elements are used to manage the Internet of Things (IoT) environment. Specifically, AIoTF network elements can be used to manage the access control and mobility of AIoT terminals. These network elements can be standalone network elements, or they can be logical network elements; for example, AIoTF can be co-located with access network devices, AMF (Access and Mobility Management Function), or other network elements. AIoTF can also be referred to as an access and mobility management device, access and mobility management function entity, access and mobility management function network element, mobility management device, mobility management network element, or mobility management entity, etc.

[0095] As another example, environmental IoT data management can include ADM network elements. ADM network elements can be used to handle tasks such as authentication and access for environmental IoT device identifiers. ADM can also be referred to as a key storage network element, unified data management device, unified data management network element, data management device, or unified data management entity, etc.

[0096] An ADM network element can be a standalone network element. Alternatively, an ADM network element can be a logical network element; for example, an ADM can be co-located with a UDM, UDR, or other network elements.

[0097] It is understood that network elements in an AIoT network are not limited to the examples above.

[0098] In the case where the reader acts as an access network device, communication between the reader and the AIoTF can be achieved through the N2 interface. When the reader acts as a terminal device, communication between the reader and the AIoTF can be achieved through the non-access stratum (NAS).

[0099] 5. The server can be used to support third-party management of AIoT terminals and / or trigger AIoT terminals to perform operations.

[0100] As an example, the server can be an AF (Application Controller) or a part of the AF's functionality or components. That is, the AF can act as an application or application server for AIoT services, and the AF can communicate with the AIoTF (Application Controller) through the NEF (Application Controller).

[0101] It is understood that the aforementioned network element or function can be a network component in a hardware device, a software function running on dedicated hardware, or a virtualization function instantiated on a platform (e.g., a cloud platform). As one possible implementation method, the aforementioned network element or function can be implemented by a single device, multiple devices working together, or a functional module within a single device; this application does not specifically limit this.

[0102] by Figure 3 Taking the AIoT network architecture shown as an example, the AF can request the AIoTF to perform an inventory operation through the AIoTF. This inventory operation, also known as a checklist, can be used to inventory the existing tag information or to collect or acquire tag identification information. To avoid exposing the permanent identifiers of AIoT terminals, the AIoT terminals can report temporary identifiers to the AIoTF during the inventory process. The AIoTF can then convert the temporary identifier of the AIoT terminal into a permanent identifier or another identifier that the AF can recognize, and send the converted identifier to the AF.

[0103] Currently, when temporary identifiers are generated by AIoT terminals, there are scenarios where different AIoT terminals generate the same temporary identifier. When temporary identifiers are duplicated across multiple AIoT terminals, the accuracy of inventory results decreases.

[0104] To address the aforementioned technical problems, this application provides a communication method for accurately determining the permanent identifier of an AIoT terminal when multiple AIoT terminals have duplicate temporary identifiers, thereby improving the accuracy of inventory results. This method can be executed by a first device. The actions of the first device can also be implemented by modules or chips within the first device. The first device can be an AIoTF or other network element or node.

[0105] In this communication method, a first device can send an inventory request, causing a first AIoT terminal to provide the first device with a first temporary identifier and first verification information upon receiving the inventory request. The first verification information can be used to verify the identity of the first AIoT terminal. If the first temporary identifier corresponds to multiple permanent identifiers, the first device can verify the identity of the first AIoT terminal based on the first verification information and determine the permanent identifier of the first AIoT terminal from among the multiple permanent identifiers based on the authentication result, thereby achieving a reasonable determination of the permanent identifier of the first AIoT terminal.

[0106] The first device can be an AIoTF, or a module or component within an AIoTF. The following explanation uses an AIoTF as the first device.

[0107] The following is combined with Figure 2 The flowchart shown describes the communication method provided in this application. Figure 2 As shown, the method may include the following steps:

[0108] S101: AIoTF sends a first request, which is used to request the inventory of one or more AIoT terminals.

[0109] Accordingly, one or more AIoT terminals can receive the first request.

[0110] The first request can be an inventory request. An inventory request can be used to request an inventory of AIoT terminals.

[0111] In one possible example of S101, the AIoTF can send a first request to one or more readers, and the one or more readers can send a second request, which can be used to inventory one or more AIoT terminals. The readers can send the second request to one or more AIoT terminals. For example, the second request can be sent via broadcast, multicast, or single-wave transmission. In this example, the first request and the second request are different messages; their contents can be the same or different, and this application does not specifically limit this.

[0112] In the case where the reader is an access network device, the reader communicates with the AIoTF via the N2 interface; that is, the AIoTF can send a first request to one or more readers via N2 messages. In the case where the reader is a terminal, the reader communicates with the AIoTF via NAS; that is, the AIoTF can send a first request to one or more readers via NAS messages.

[0113] In another possible example, the AIoTF can send the first request, where the reader does not need to read or parse the content of the first request message. Correspondingly, the AIoT terminal can receive this broadcast first request. Alternatively, in this example, the first request is sent by the AIoTF to one or more AIoT terminals. As an example, the first request can be carried in a paging message.

[0114] S102: The first AIoT terminal sends the first temporary identifier and the first verification information of the first AIoT terminal.

[0115] Accordingly, AIoTF receives the first temporary identifier and first authentication information of the first AIoT terminal. One or more AIoT terminals include the first AIoT terminal.

[0116] The first temporary identifier and the first verification information can be carried in a message sent from the first AIoT terminal to the reader, and then the reader can carry the first temporary identifier and the first verification information in another message and send that other message to the AIoTF. Alternatively, the reader can also transmit the first temporary identifier and the first verification information transparently to the AIoTF. For example, the first temporary identifier and the first verification information can be carried in a NAS message, and the reader does not need to read or parse the first temporary identifier and the first verification information in the NAS message.

[0117] In this application, the temporary identifier of the AIoT terminal can be used to identify the AIoT terminal in communication between the AIoT terminal and the reader. And / or, the temporary identifier of the AIoT terminal can be used to identify the AIoT terminal in communication between the AIoT terminal and the AIoTF. For example, the temporary identifier of the AIoT terminal can be determined based on the permanent identifier of the AIoT terminal. The permanent identifier of the AIoT terminal can be used to uniquely identify the AIoT terminal in the core network. For example, the permanent identifier of the AIoT terminal can be a subscription permanent identifier (SUPI). Alternatively, the permanent identifier of the AIoT terminal can be an AIoT device permanent identifier. For example, the AIoT device permanent identifier can be an N-bit numeric string, where N is a positive integer. For example, when N equals 8, the AIoT device permanent identifier can be 12345678.

[0118] The first verification information can be used to verify the identity of the first AIoT terminal. Specifically, the first verification information can be used to verify the authenticity of the identity corresponding to the identifier of the first AIoT terminal, and the first verification information can be used to verify whether the permanent identifier of the first AIoT terminal belongs to the first AIoT terminal. For example, the first verification information can be response information (RES) used to verify the identity of the first AIoT terminal. Exemplarily, the response information can also be represented as a token or authentication token. Unless otherwise specified, RES can represent the verification information generated by the AIoT terminal.

[0119] The first temporary identifier and its determination method are explained below.

[0120] In this application, the first temporary identifier is determined by a first algorithm based on the permanent identifier of the first AIoT terminal and the first temporary identifier input parameters. The first temporary identifier input parameters can be one or more of the following: a random number, a shared key, etc. In this application, the random number included in the temporary identifier input parameters can be called the temporary identifier random number. In this application, the random number can also be called the freshness parameter.

[0121] The random number may include a first random number determined by the AIoTF and / or a second random number determined by the AIoT terminal. Optionally, the first random number determined by the AIoTF may be included in the first request sent by the AIoTF in S101, or carried in the same message as the first request; the first random number determined by the AIoTF may also be carried in other messages sent by the AIoTF to the first AIoT terminal. Additionally, the first AIoT terminal may generate a second random number to determine the first temporary identifier. Furthermore, the first AIoT terminal may send the second random number determined by the AIoT terminal to the AIoTF, for example, in S102, the first AIoT terminal may also send the second random number determined by the AIoT terminal to the AIoTF. That is, in S102, the first AIoT terminal may send the second random number, the first temporary identifier, and the first verification information to the AIoTF, wherein the first temporary identifier may be generated based on the second random number. For ease of distinction, the random number used to determine the temporary identifier can be called the temporary identifier random number. For example, the first temporary identifier random number refers to the random number determined by AIoTF to determine the temporary identifier, and the second temporary identifier random number refers to the random number determined by the AIoT terminal to determine the temporary identifier.

[0122] The shared key can be a shared key between the core network and the first AIoT terminal. Optionally, it can be assumed that the first AIoT terminal and the core network have already been configured with a shared key. The first AIoT terminal and the core network can each be configured with the same shared key. For example, the core network may be configured with shared keys for one or more AIoT terminals, including the shared key of the first AIoT terminal.

[0123] As one example, the ADM is configured to use a shared key to calculate the temporary identifier; in this case, the AIoTF can obtain the first temporary identifier from the ADM. As another example, the AIoTF is configured to use a shared key to calculate the temporary identifier; in this case, the AIoTF can calculate and obtain the first temporary identifier.

[0124] As an example of determining the first temporary identifier, the first AIoT terminal can determine the first temporary identifier based on its own permanent identifier and the first temporary identifier input parameter after obtaining the first temporary identifier input parameter. For example, the first AIoT terminal can use its own permanent identifier and the first temporary identifier input parameter as input, and determine the output result through a hash algorithm; this output result is the first temporary identifier.

[0125] Referring to the process of determining the first temporary identifier of the first AIoT terminal, the AIoT terminal and / or AIoTF can obtain the temporary identifiers of other AIoT terminals.

[0126] The following example, using RES as the first verification information, illustrates the first verification information and its determination method.

[0127] The first verification information is determined by the second algorithm based on the key of the first AIoT terminal and the first verification information input parameters.

[0128] The key of the first AIoT terminal can be a long-term key of the first AIoT terminal. This long-term key can be considered as a credential used by the first AIoT terminal for authentication. The long-term key used for authentication and the shared key used to generate the temporary identifier can be the same or different, without specific limitations.

[0129] The first verification information input parameter can be a random number, or one or more other parameters, without specific limitations. The random number in the verification information input parameter can also be called the verification information random number. This random number can include a first random number determined by the AIoTF and / or a second random number determined by the AIoT terminal. For ease of distinction, the random number used to determine the verification information can be called the verification information random number. For example, the first verification information random number refers to the random number determined by the AIoTF for determining the verification information, and the second verification information random number refers to the random number determined by the AIoT terminal for determining the verification information.

[0130] For the same AIoT terminal, the temporary identifier random number and the verification information random number can be the same or different. For example, the first verification information random number can be the same as or different from the first temporary identifier random number, and the second verification information random number can be the same as or different from the second temporary identifier random number. The method for determining the first verification information random number obtained by the first AIoT terminal can refer to the method for obtaining the first temporary identifier random number, and the method for determining the second verification information random number obtained by the AIoTF can refer to the method for obtaining the second temporary identifier random number, which will not be repeated here.

[0131] For the first AIoT terminal, its key is known. Therefore, after obtaining the first authentication information input parameters, the first AIoT terminal can determine the RES based on its key and the authentication information input parameters. For example, the first AIoT terminal can determine the RES using a hash algorithm based on its key and the authentication information input parameters.

[0132] It is understood that the temporary identifier input parameters and the verification information input parameters may differ, and / or the first algorithm and the second algorithm may differ. The temporary identifier input parameters and the verification information input parameters may differ, meaning they include at least one different parameter. For example, the temporary identifier input parameters may include more parameter types than the verification information input parameters; for instance, the temporary identifier input parameters may include a random number and a shared key, while the verification information input parameters may only include a random number. Or, the temporary identifier random number included in the temporary identifier input parameters may differ from the verification information random number included in the verification information input parameters. The first algorithm and the second algorithm may differ; for example, the first algorithm and the second algorithm may be different hash algorithms. Therefore, if the identity of the first AIoT terminal is verified based on the first verification information, it can be proven that the permanent identifier belongs to the first AIoT terminal.

[0133] Optionally, upon receiving the first request, the first AIoT terminal may send a first temporary identifier and first verification information to the AIoTF in response to the first request. This application does not limit the timing at which the first AIoT terminal determines the first temporary identifier and / or the first verification information. For example, the first AIoT terminal may have already determined the first temporary identifier and / or the first verification information before receiving the first request. Alternatively, the first AIoT terminal may determine the first temporary identifier and / or the first verification information after receiving the first request, for example, if the first request includes temporary identifier input parameters and / or verification information input parameters, or if the first AIoT terminal triggers the determination of the first temporary identifier and / or the first verification information based on the first request.

[0134] Optionally, the parameters generated by the core network elements in the first temporary identifier input parameter and / or the first verification information input parameter in this application can be shared, i.e., configured at the terminal group level. For example, the first temporary identifier input parameter and / or the first verification information input parameter are applicable to an AIoT terminal group, which includes one or more AIoT terminals, and the one or more AIoT terminals include the first AIoT terminal.

[0135] S103: AIoTF obtains the authentication result of the first AIoT terminal based on the first authentication information.

[0136] The authentication result of the first AIoT terminal based on the first verification information can refer to the authentication result of the first AIoT terminal obtained based on the first verification information, that is, the authentication result of the first AIoT terminal corresponding to the first verification information.

[0137] The authentication result can be determined based on the authentication result of the first authentication information.

[0138] The first permanent identifier will be introduced below.

[0139] In this application, the first permanent identifier can be one of at least two permanent identifiers corresponding to the first temporary identifier. For example, the first temporary identifier may correspond to at least two permanent identifiers, which include the first permanent identifier and the second permanent identifier, and optionally may also include other permanent identifiers. The first permanent identifier and the second permanent identifier belong to different AIoT terminals.

[0140] Optionally, upon receiving the first temporary identifier in S102, the AIoTF may execute S103 and S104 if it determines that the first temporary identifier corresponds to at least two permanent identifiers. It should be understood that the AIoTF may also obtain the aforementioned first verification information from the AIoT terminal if it determines that the first temporary identifier corresponds to at least two permanent identifiers.

[0141] The AIoTF can store, manage, and / or maintain the correspondence between temporary and permanent identifiers of AIoT terminals. After receiving the first temporary identifier of the first AIoT terminal in S102, the AIoTF can determine the permanent identifier corresponding to the first temporary identifier based on the first temporary identifier and the aforementioned correspondence. Where the permanent identifier corresponding to the first temporary identifier includes at least a first permanent identifier and a second permanent identifier, S103 and S104 can be executed to determine the permanent identifier of the first AIoT terminal. In other words, the AIoTF can at least store, manage, and / or maintain a first correspondence and a second correspondence, where the first correspondence includes the correspondence between the first temporary identifier and the first permanent identifier of the first AIoT terminal, and the second correspondence may include the correspondence between the first temporary identifier and the second permanent identifier of the first AIoT terminal. The case where the permanent identifier corresponding to the first temporary identifier includes at least a first permanent identifier and a second permanent identifier is a case of temporary identifier collision, meaning that the same temporary identifier corresponds to the permanent identifier of more than one AIoT terminal. Therefore, the corresponding AIoT terminal cannot be determined solely by the first temporary identifier.

[0142] In this application, the first permanent identifier is used as an example to illustrate the use of the first permanent identifier of the first AIoT terminal.

[0143] The following example, using the correspondence between the first temporary identifier and the first permanent identifier of the first AIoT terminal, illustrates how AIoTF obtains the correspondence between the first temporary identifier and the permanent identifier of the AIoT terminal.

[0144] One possible implementation is that, after determining the first temporary identifier of the first AIoT terminal, AIoTF can store the correspondence between the first temporary identifier and the first permanent identifier of the first AIoT terminal. In this application, the correspondence between the temporary identifier and the permanent identifier of the AIoT terminal can be referred to as the identifier correspondence.

[0145] The AIoTF can determine the first temporary identifier based on the first permanent identifier and the first temporary identifier input parameters. The first temporary identifier input parameters can be found in section A102. Optionally, the AIoTF can determine the first temporary identifier through the ADM, that is, the ADM can determine and send the first temporary identifier of the first AIoT terminal to the AIoTF based on the first permanent identifier and the first temporary identifier input parameters of the first AIoT terminal.

[0146] As an example, the AIoTF can send a first permanent identifier and a first temporary identifier input parameters to the ADM to request the ADM to determine the first temporary identifier. After receiving the first temporary identifier from the ADM, the AIoTF can determine the correspondence between the first temporary identifier and the first permanent identifier of the first AIoT terminal. For example, the first permanent identifier and the first temporary identifier input parameters can be carried in the temporary identifier request sent by the AIoTF to the ADM, and the first temporary identifier from the ADM can be carried in the temporary identifier response.

[0147] Furthermore, AIoTF can also perform the calculation process to determine the first temporary identifier based on the first permanent identifier and the first temporary identifier input parameters. Refer to the description of the first AIoT terminal's calculation of the first temporary identifier; it will not be repeated here. After determining the first temporary identifier through calculation, AIoTF can store the correspondence between the first temporary identifier and the first permanent identifier of the first AIoT terminal.

[0148] Another possible implementation is that the AIoTF can send a first temporary identifier input parameter to the ADM, enabling the ADM to determine the first temporary identifier based on the first permanent identifier and the first temporary identifier input parameter. The AIoTF can also receive and store the correspondence between the first temporary identifier and the first permanent identifier from the first AIoT terminal of the ADM. For example, the first temporary identifier input parameter can be carried in the temporary identifier request sent by the AIoTF to the ADM, and the first temporary identifier and the first permanent identifier from the ADM can be carried in the temporary identifier response.

[0149] Specifically, the AIoTF can send the target device information of the first AIoT terminal and the first temporary identifier input parameter to the ADM, and receive the first temporary identifier and the first permanent identifier from the ADM. The target device information of the first AIoT terminal can be used to filter, indicate, and / or determine that the AIoT terminal to which the first temporary identifier input parameter applies is the first AIoT terminal. Optionally, the target device information can be determined based on information such as the permanent identifier or type of the first AIoT terminal, and can be used to filter the first AIoT terminal from multiple AIoT terminals. Therefore, the ADM can determine the permanent identifier of the first AIoT terminal based on the target device information, and further determine the first temporary identifier of the first AIoT terminal based on the permanent identifier and the first temporary identifier input parameter.

[0150] The following example, using RES as the first verification information, illustrates how AIoTF obtains the authentication result of the first AIoT terminal based on the first verification information.

[0151] In step S103, during the process of obtaining the verification result, the second verification information, denoted as XRES, can be determined based on the temporary identifier input parameter corresponding to RES and the permanent identifier corresponding to the first temporary identifier. RES and XRES are then compared, and the authentication result is obtained based on the comparison result. In one implementation, the comparison result is used as the authentication result; for example, a successful comparison means successful authentication of the permanent identifier.

[0152] Specifically, AIoTF can perform the above verification through ADM to obtain the verification result. That is, XRES can be determined by ADM, and the verification result can be obtained by comparing RES and XRES. Here, RES is determined based on the first verification information input parameters. For example, if the first permanent identifier is the permanent identifier of the first AIoT terminal, RES is determined based on the key of the first AIoT terminal and the first verification information input parameters using a second algorithm. XRES can be determined based on the key of the AIoT terminal corresponding to the first permanent identifier and the verification information input parameters corresponding to the first permanent identifier using a second algorithm.

[0153] Where the first permanent identifier is the permanent identifier of the first AIoT terminal, the key of the first AIoT terminal is the same as the key of the AIoT terminal corresponding to the first permanent identifier, the first verification information input parameters are the same as the verification information input parameters corresponding to the first permanent identifier, and the second algorithm used to determine RES and the second algorithm used to determine XRES are the same; therefore, RES and XRES are the same. Where the first permanent identifier is not the permanent identifier of the first AIoT terminal, the key of the first AIoT terminal may be different from the key of the AIoT terminal corresponding to the first permanent identifier, and the first verification information input parameters may be different from the verification information input parameters corresponding to the first permanent identifier; therefore, RES and XRES are different.

[0154] In this application, AIoTF and / or ADM can compare RES with XRES and determine the verification result based on the comparison result. If RES and XRES are the same, the authentication result indicates that the first AIoT terminal has been successfully authenticated, or that the first AIoT terminal has passed authentication; that is, the first permanent identifier is the permanent identifier of the first AIoT terminal. If RES and XRES are different, the authentication result indicates that the first AIoT terminal has failed authentication, or that the first AIoT terminal has not passed authentication; that is, the first permanent identifier is not the permanent identifier of the first AIoT terminal.

[0155] One possible implementation is that the ADM compares RES with XRES to obtain the authentication result, and then the ADM sends a first verification response to the AIoTF to indicate the authentication result. For example, the first verification response may contain the authentication result of the first AIoT terminal.

[0156] For example, AIoTF can send a first authentication request to ADM, which may include a first permanent identifier and RES, requesting ADM to determine the authentication result based on RES and the first permanent identifier. Correspondingly, ADM can determine the second authentication information (XRES) corresponding to the first permanent identifier, determine the authentication result based on RES and XRES, and send a first authentication response corresponding to the RES to AIoTF to indicate the authentication result. For example, the first authentication response may include the aforementioned authentication result. Specifically, the method for determining the XRES corresponding to the first permanent identifier is, for example, ADM determines the key of the AIoT terminal corresponding to the first permanent identifier and the first authentication information input parameters, and determines the XRES based on the key of the AIoT terminal corresponding to the first permanent identifier and the first authentication information input parameters.

[0157] Optionally, in this implementation, the first verification request may also carry the first verification information input parameter corresponding to RES. RES is determined based on the first verification information input parameter. For example, after determining the verification information input parameter corresponding to the AIoT terminal, the AIoTF can send the verification information input parameter to the AIoT terminal and store the verification information input parameter. Therefore, upon receiving the first temporary identifier and RES from the first AIoT terminal, the AIoTF can determine the first verification information input parameter corresponding to RES from the locally stored verification information input parameters.

[0158] Alternatively, the ADM can store the verification information input parameters of the AIoT terminal. Correspondingly, the first verification request may not carry the first verification information input parameters; instead, the ADM obtains the verification information input parameters after receiving the first verification request. One example is that there is a correspondence between the AIoTF and the verification information input parameters, meaning that the verification information input parameters sent by the AIoTF to different AIoT terminals are all the first verification information input parameters. Alternatively, after receiving the first verification request, the ADM can request the verification information input parameters corresponding to the first permanent identifier from the AIoTF, causing the AIoTF to send the verification information input parameters corresponding to the first permanent identifier to the ADM according to the request.

[0159] After determining the key of the AIoT terminal corresponding to the first permanent identifier and the first verification information input parameters, the ADM can further determine XRES using the second algorithm based on the AIoT terminal's key and the first verification information input parameters. Specifically, when the first permanent identifier is the permanent identifier of the first AIoT terminal, the key of the AIoT terminal corresponding to the first permanent identifier is the same as the key of the first AIoT terminal, and the second algorithm used to determine XRES is the same as the second algorithm used by the first AIoT terminal to determine RES. Therefore, the calculated XRES is the same as RES. When RES and XRES are the same, it can be proven that the key of the first AIoT terminal used to calculate RES is the same as the key of the AIoT terminal used to calculate XRES, which means it can be proven that the permanent identifier of the first AIoT terminal is the same as the first permanent identifier. Conversely, when RES and XRES are different, it can be proven that the permanent identifier of the first AIoT terminal is not the first permanent identifier.

[0160] Furthermore, ADM can determine the authentication result of the first AIoT terminal based on the first authentication information according to REX and XRES. Where RES and XRES are the same, the authentication result can be used to indicate successful authentication, and correspondingly, AIoTF can determine that the permanent identifier of the first AIoT terminal is the first permanent identifier based on the authentication result. Where RES and XRES are different, the authentication result can be used to indicate authentication failure, and correspondingly, AIoTF can determine that the permanent identifier of the first AIoT terminal is not the first permanent identifier based on the authentication result.

[0161] Another possible implementation is to obtain the authentication result by comparing RES with XRES using AIoTF.

[0162] For example, the AIoTF can send a second verification information request to the ADM to request XRES. This request may carry a first permanent identifier. Optionally, the second verification information request may also include the first verification information input parameter corresponding to RES. The second verification information request can also be called a request for second verification information, or a message or request for requesting second verification information. Here, RES is determined based on the first verification information input parameter. The method for determining the first verification information input parameter can be found in the description of the previous implementation and will not be repeated here. Optionally, the second verification information request may not carry the first verification information input parameter corresponding to the first permanent identifier; the corresponding method for the ADM to determine the first verification information input parameter can be found in the description of the previous implementation.

[0163] Accordingly, upon receiving the second verification information request, the ADM determines the second verification information (XRES) corresponding to the first permanent identifier. Specifically, the ADM can determine the key of the first AIoT terminal corresponding to the first permanent identifier based on the first permanent identifier, and determine the XRES using the second algorithm based on the key of the AIoT terminal corresponding to the first permanent identifier and the first verification information input parameters. Where the first permanent identifier is the permanent identifier of the first AIoT terminal, the key of the AIoT terminal corresponding to the first permanent identifier is the same as the key of the first AIoT terminal, and the second algorithm used to determine the XRES is the same as the second algorithm used by the first AIoT terminal to determine the RES; therefore, the calculated XRES is the same as the RES.

[0164] Furthermore, the ADM can also send XRES to the AIoTF, so the AIoTF can determine the authentication result of the first AIoT terminal based on the RES and the XRES from the ADM, according to the first authentication information. Wherein, if RES and XRES are the same, the authentication result can be used to indicate successful authentication. Conversely, if RES and XRES are different, the authentication result can be used to indicate authentication failure.

[0165] The first verification information input parameter in the first verification request or the second verification information request can also be replaced with the verification information input parameter corresponding to the first permanent identifier, depending on the circumstances.

[0166] In one scenario, there is a correspondence between the AIoTF and the verification information input parameters. That is, the verification information input parameters sent by the AIoTF to different AIoT terminals are the first verification information input parameters. For example, the verification information input parameters sent by the AIoTF to the AIoT terminal corresponding to the first permanent identifier are the first verification information input parameters. Similarly, the verification information input parameters sent by the AIoTF to the AIoT terminal corresponding to the second permanent identifier are the first verification information input parameters. In this case, the first verification request or the second verification information request can carry the first verification information input parameters, and the ADM can determine XRES using the second algorithm based on the key corresponding to the first permanent identifier and the first verification information input parameters. Alternatively, if the first verification request or the second verification information request does not contain the first verification information input parameters, the ADM can store the correspondence between the AIoTF and the first verification information input parameters, and determine the first verification information input parameters corresponding to the AIoTF based on this correspondence upon receiving the aforementioned request.

[0167] In another scenario, the verification information input parameters sent by AIoTF to different AIoTF terminals can be different. In this case, the first verification information input parameter in the first verification request or the second verification information request can be replaced with the verification information input parameter corresponding to the first permanent identifier. Subsequently, ADM can determine XRES based on the public key corresponding to the first permanent identifier and the verification information input parameter corresponding to the first permanent identifier using the second algorithm. The method of comparing RES with XRES and determining the authentication result remains unchanged. Alternatively, if the first verification request or the second verification information request does not contain the verification information input parameter corresponding to the first permanent identifier, ADM can store the correspondence between the first permanent identifier and the verification information input parameters, and determine the verification information input parameter corresponding to the first permanent identifier based on this correspondence after receiving the aforementioned request. For example, after sending the verification information input parameters to the AIoT terminal, AIoTF can send the correspondence between the permanent identifier of the AIoT terminal and the verification information input parameters to ADM.

[0168] In one possible embodiment, the AIoTF may also determine that the second permanent identifier is not a permanent identifier of the first AIoT terminal. For example, before the AIoTF sends the aforementioned first verification request or second verification information request, optionally, the AIoTF may also determine that the second permanent identifier is not a permanent identifier of the first AIoT terminal.

[0169] One way to determine that the second permanent identifier is not a permanent identifier of the first AIoT terminal is as follows: The AIoTF can send a second verification request to the ADM. This second verification request may include the RES and the second permanent identifier. Therefore, the second verification request can be used to request the ADM to authenticate the first AIoT terminal based on the RES and the second permanent identifier. Accordingly, the ADM can determine the authentication result based on the RES and the second permanent identifier, and send the second verification response corresponding to the RES to the AIoTF. Specifically, the ADM can determine the corresponding key and the second verification information input parameters corresponding to the second permanent identifier based on the second permanent identifier. The second verification request may also include the first verification information input parameters corresponding to the RES. Alternatively, the ADM can determine the first verification information input parameters corresponding to the RES after receiving the second verification request. The method for determining the first verification information input parameters corresponding to the RES can be found in the description of the corresponding scheme for the first verification request or the second verification information request, and will not be repeated here.

[0170] After determining the key corresponding to the second permanent identifier and the first verification information input parameters, the ADM can further determine XRES' using a second algorithm based on the key corresponding to the second permanent identifier and the first verification information input parameters. XRES' can be recorded as the third verification information. Where the second permanent identifier is not the permanent identifier of the first AIoT terminal, the key corresponding to the second permanent identifier is different from the key used by the first AIoT terminal to determine RES; therefore, XRES' and RES are different. When XRES' and RES are different, the ADM can determine that the authentication of the first AIoT terminal has failed and send a second verification response to the AIoTF to indicate that the authentication of the first AIoT terminal has failed. For example, the second verification response can indicate the authentication result of the first AIoT terminal's failed authentication. Correspondingly, after receiving the second verification response, the AIoTF can determine that the second permanent identifier is not the permanent identifier of the first AIoT terminal.

[0171] In the above method, the authentication result can be determined by comparing RES and XRES' using ADM.

[0172] Another way to determine that the second permanent identifier is not a permanent identifier of the first AIoT terminal is, for example, that the AIoTF can send a third verification information request to the ADM to request third verification information. The third verification information request can also be called a request for third verification information, or a message or request for requesting third verification information. This third verification information request may contain the second permanent identifier.

[0173] Optionally, the third verification information request may also include the first verification information input parameters corresponding to RES, or the ADM may determine the first verification information input parameters corresponding to RES after receiving the third verification information request. The method for determining the first verification information input parameters corresponding to RES can be found in the description of the corresponding schemes for the first verification request or the second verification information request, and will not be repeated here.

[0174] Accordingly, upon receiving the third verification information request, the ADM determines the third verification information (XRES') corresponding to the second permanent identifier. Specifically, the ADM can determine the corresponding key based on the second permanent identifier, and determine XRES' using the second algorithm based on the key of the AIoT terminal corresponding to the second permanent identifier and the first verification information input parameters. After determining XRES', the ADM can send XRES' to the AIoTF. Upon receiving XRES', the AIoTF compares RES with XRES' to obtain the authentication result. If the second permanent identifier is not the permanent identifier of the first AIoT terminal, the key of the AIoT terminal corresponding to the second permanent identifier is different from the key used by the first AIoT terminal to determine RES. Therefore, XRES' and RES are different, meaning the authentication result can indicate that the authentication of the first AIoT terminal has failed. Thus, the AIoTF can determine that the second permanent identifier is not the permanent identifier of the first AIoT terminal.

[0175] In the above method, AIoTF can compare RES and XRES' to determine the authentication result.

[0176] Optionally, if the AIoTF determines that the second permanent identifier is not a permanent identifier of the first AIoT terminal, it may request the ADM to verify whether the first permanent identifier is a permanent identifier of the first AIoT terminal. For example, after determining that the second permanent identifier is not a permanent identifier of the first AIoT terminal based on the implementation of the second verification request or the third verification information request, the AIoTF may send the aforementioned first verification request or second verification information request to the ADM to verify whether the first permanent identifier is a permanent identifier of the first AIoT terminal and obtain the aforementioned verification result.

[0177] Alternatively, AIoTF can verify in parallel whether the first permanent identifier is the permanent identifier of the first AIoT terminal, and verify whether the second permanent identifier is the permanent identifier of the first AIoT terminal. For example, AIoTF can carry the aforementioned first verification request or second verification information request, as well as the aforementioned second verification request and third verification information request, in the same message sent to ADM. As another example, AIoTF can simultaneously trigger or send the aforementioned first verification request or second verification information request, as well as carry the aforementioned second verification request and third verification information request.

[0178] The first verification information input parameter in the second verification request or the third verification information request can also be replaced with the verification information input parameter corresponding to the second permanent identifier. The method for determining the verification information input parameter corresponding to the second permanent identifier can be found in the aforementioned explanation of the method for determining the verification information input parameter corresponding to the first permanent identifier, and will not be repeated here.

[0179] Another possible implementation is that, after receiving the first temporary identifier and RES of the first AIoT terminal, the AIoTF sends a third verification request (such as a third verification request) to the ADM. This verification request includes the first temporary identifier and RES of the first AIoT terminal. This verification request can also be understood as requesting the permanent identifier of the first AIoT terminal. The ADM can store or calculate the correspondence between the temporary identifiers and permanent identifiers of the AIoT terminal, and therefore can determine at least two permanent identifiers corresponding to the first temporary identifier based on the first temporary identifier and the correspondence, including the first permanent identifier and the second permanent identifier.

[0180] Furthermore, the ADM can determine the XRES corresponding to the first permanent identifier based on the first permanent identifier, and compare RES with XRES to determine the first authentication result, and / or determine the XRES' corresponding to the second permanent identifier based on the second permanent identifier to determine the second authentication result. The method for determining the XRES corresponding to the first permanent identifier can be found in the description of verifying whether the first permanent identifier is the first AIoT terminal based on the first authentication request or the second authentication information request; the method for determining the XRES' corresponding to the second permanent identifier can be found in the description of verifying whether the second permanent identifier is the first AIoT terminal based on the second authentication request or the third authentication information request, and will not be repeated here. The method for determining the first authentication result based on RES and XRES can be found in the description of determining the authentication result based on RES and XRES in the aforementioned implementation, and the method for determining the second authentication result based on RES and XRES' can be found in the description of determining whether the authentication of the first AIoT terminal is successful based on RES and XRES' in the aforementioned implementation, and will not be repeated here.

[0181] One example is that the ADM can also send a third authentication response corresponding to the third authentication request to the AIoTF, which may include a first permanent identifier and its corresponding first authentication result, and a second permanent identifier and its corresponding second authentication result. For example, the first authentication result may indicate successful authentication, and accordingly, the AIoTF can determine from the third authentication response that the first permanent identifier corresponding to the first authentication result is the permanent identifier of the first AIoT terminal. Alternatively, the first authentication result can be considered as an example of the authentication result of the first AIoT terminal based on the first authentication information in S103. Furthermore, the second authentication result may indicate authentication failure, and accordingly, the AIoTF can determine that the second permanent identifier corresponding to the first authentication result is not the permanent identifier of the first AIoT terminal.

[0182] Another example is that, after determining the first authentication result based on RES and XRES, the ADM can determine that the first permanent identifier is the permanent identifier of the first AIoT terminal based on the first authentication result. The ADM can also send a third authentication response to the AIoTF, which carries the permanent identifier of the first AIoT terminal, i.e., the first permanent identifier. Optionally, the third authentication response may also include the first authentication result.

[0183] The third verification request can also be replaced by a fourth verification information request. This request can be used to request verification information for all permanent identifiers corresponding to the first temporary identifier, such as the second verification information XRES corresponding to the first permanent identifier and the verification information XRES' corresponding to the second permanent identifier. The fourth verification information request may include the first temporary identifier. Accordingly, the ADM can determine the first permanent identifier and the second permanent identifier based on the first temporary identifier, and determine the corresponding XRES based on the first permanent identifier, and the corresponding XRES' based on the second permanent identifier. Subsequently, the ADM can send XRES and XRES' to the AIoTF, so that the AIoTF determines the first authentication result based on RES and XRES; and / or, determines the second authentication result based on RES and XRES'. The methods for determining the first and second authentication results are not detailed here. The first authentication result can be used as an example of the authentication result of the first AIoT terminal based on the first verification information in S103.

[0184] It is understandable that when the multiple permanent identifiers corresponding to the first temporary identifier include permanent identifiers other than the first permanent identifier and the second permanent identifier, AIoTF can refer to the above method of verifying whether the first permanent identifier is the permanent identifier of the first AIoT terminal, or refer to the above method of verifying whether the second permanent identifier is the permanent identifier of the first AIoT terminal, to verify whether the multiple permanent identifiers are the permanent identifiers of the first AIoT terminal, until the permanent identifier of the first AIoT terminal is determined.

[0185] S104: AIoTF determines the permanent identifier of the first AIoT terminal corresponding to the first temporary identifier based on the authentication result.

[0186] As explained in S103, if the authentication of the first AIoT terminal is performed based on the first permanent identifier, and the authentication result obtained based on the first verification information indicates successful authentication, the AIoTF can determine that the permanent identifier of the first AIoT terminal is the first permanent identifier. Conversely, if the authentication result obtained based on the first verification information indicates failed authentication, the AIoTF can determine that the permanent identifier of the first AIoT terminal is not the first permanent identifier.

[0187] In one possible embodiment, after determining the permanent identifier of the first AIoT terminal, the AIoTF may also send the permanent identifier to the AF. Alternatively, the AIoTF may send the identifier of the first AIoT terminal that the AF can recognize to the AF, wherein the identifier of the first AIoT terminal that the AF can recognize can be converted to and from the permanent identifier of the first AIoT terminal. As an example, the identifier of the AIoT terminal that the AF can recognize may be an identifier that can be made public to a third-party AF, such as a generic public subscription identifier (GPSI) or other identifiers, which are not specifically limited here. For example, the inventory reply message may carry the GPSI, and optionally, the inventory reply message may also include the first permanent identifier.

[0188] It should be understood that S103 and S104 are optional for cases where AMD determines the permanent identifier of the first AIoT terminal.

[0189] In this implementation, after determining the permanent identifier of the first AIoT terminal, the ADM can send the permanent identifier of the first AIoT terminal to the AIoTF, so the AIoTF can receive the permanent identifier of the first AIoT terminal from the ADM. In this case, steps S103 and S104 do not need to be executed. Optionally, the AIoTF can also send the permanent identifier of the first AIoT terminal to the AF.

[0190] Alternatively, after determining the permanent identifier of the first AIoT terminal, the ADM can determine the identifier of the first AIoT terminal that the AF can recognize based on the permanent identifier, and send the identifier of the first AIoT terminal that the AF can recognize to the AIoTF. In this case, it is not necessary to execute S103 and S104. Optionally, the AIoTF can also send the identifier of the first AIoT terminal that the AF can recognize to the AF.

[0191] The following is based on Figure 3 For example, this describes the process by which the AIoTF determines the permanent identifier of the first AIoT terminal when it receives a storage request from the AF and determines that the temporary identifier of the first AIoT terminal being stored corresponds to multiple permanent identifiers. In this process, the AIoTF can base its determination on... Figure 2 The communication method shown determines the permanent identifier of the first AIoT terminal.

[0192] S201: AF sends a first service request to AIoTF via NEF to request inventory of one or more AIoT terminals.

[0193] The first service request may carry at least one of the following: AF identifier, service type, or target device information.

[0194] (1) The AF identifier can be used to indicate the AF.

[0195] An AF can be considered the inventory requester. For example, an AF could be a third-party server. AF can also be replaced by other devices.

[0196] (2) The service type can be used to indicate the type of the first service. For the first service request, the service type can be an inventory operation. Additionally, for other service requests, the service type can also be a command operation. Command operations include read operations, write operations, and deactivation operations. A read operation involves reading data from the tag. A write operation involves writing data to the tag. A deactivation operation involves deactivating or deactivating the tag.

[0197] (3) Target device information, also known as device screening information, can be used to screen AIoT terminals. When the first service request includes target device information, the first service request can be used to request an inventory of AIoT terminals that match the target device information.

[0198] For example, target device information may include regional location information, device group information, and / or device identification information.

[0199] Regional location information can indicate the region where the AIoT terminal requesting inventory is located. Device group information can be used to indicate the device group of the AIoT terminal requesting inventory. Device identification information can be used to indicate that the device currently requesting inventory is a specific device, such as an AIoT terminal.

[0200] Furthermore, the first service request can also be used to request an inventory check for a single AIoT terminal. For example, the first service request may carry the permanent identifier of the AIoT terminal, or other identifiers that the AF can recognize. Additionally, when checking multiple AIoT terminals, the first service request may also carry the permanent identifiers of all AIoT terminals, or other identifiers that the AF can recognize.

[0201] This can be understood as the AF being able to determine the information of the AIoT terminal that needs to be paged or stored, and carrying one or more of the following information in the first service request: regional location information, device group information, and device identification information, to indicate the information of the AIoT terminal that needs to be paged or stored.

[0202] Optionally, after receiving the first service request, AIoTF can send a response message to AF.

[0203] S202: AIoTF sends a second service request to the reader to request the inventory of one or more AIoT terminals.

[0204] The second service request can be sent to one or more readers.

[0205] Optionally, the second service request may include AIoT device identification information. This AIoT device identification information can be determined based on the target device information. For example, AIoTF can configure or store a mapping between target device information and AIoT device identification information; therefore, the AIoT device identification information corresponding to the target device information in the first service request can be determined based on this mapping.

[0206] The AIoT device identification information can correspond to one or more AIoT terminals, indicating that the inventory request is for those terminals. For example, the same AIoT device identification information can be assigned to one or more AIoT terminals, thus indicating one or more AIoT terminals through this information. Accordingly, the one or more AIoT terminals corresponding to the AIoT device identification information can perform an inventory operation in response to the first request.

[0207] For example, AIoT device identification information may include MASK information. For instance, the permanent identifier of an AIoT terminal is 8 bits, while the MASK can be less than 8 bits. For example, the MASK might be ****1234, where "*" indicates the first four bits are empty; this MASK corresponds to an AIoT terminal whose permanent identifier ends in 1234.

[0208] When carrying AIoT device identification information, the second service request can be sent to the reader corresponding to the AIoT device identification information. That is, the second service request can be sent to the reader connected to the AIoT terminal corresponding to the AIoT device identification information, thereby reducing system power consumption.

[0209] Furthermore, when carrying AIoT device identification information, the second service request can be used to request the inventory of the AIoT terminal corresponding to the AIoT device identification information. If the AIoT terminal receiving the second service request corresponds to the AIoT identification information, the inventory operation can be performed; otherwise, if the AIoT terminal receiving the second service request does not correspond to the AIoT identification information, the inventory operation will not be performed.

[0210] Optionally, the second service request may not carry AIoT device identification information, that is, it does not limit the scope of AIoT terminals to be inventoried. In this case, it can be assumed that the AIoT terminal receiving the inventory request can perform the inventory operation.

[0211] Optionally, if the reader is an access network device, the second service request in S202 can be carried in the N2 message. If the reader is a terminal device, the second service request in S202 can be carried in the NAS message.

[0212] In one possible embodiment, the second service request may carry input parameters for determining a temporary identifier of the AIoT terminal, and / or input parameters for determining AIoT verification information. For example, the second service request may carry a first temporary identifier input parameter, which can be used by the first AIoT terminal to determine a first temporary identifier. As another example, the second service request may carry a first verification information input parameter, which can be used by the first AIoT terminal to determine first verification information.

[0213] Optionally, upon receiving the second service request, the reader may send a response to the second service request to the AIoTF.

[0214] S203: The reader sends a broadcast message, which is used to inventory AIoT terminals.

[0215] The broadcast message can be a paging message, or a message similar to a paging message used to trigger AIoT terminals to access the network.

[0216] For example, a broadcast message could be a broadcast inventory request for inventorying unspecified AIoT terminals.

[0217] Optionally, if the second service request includes AIoT device identification information, the broadcast message may include the AIoT device identification information in order to page the AIoT terminal corresponding to the AIoT device identification information.

[0218] Optionally, the broadcast message may include input parameters for determining a temporary identifier. These input parameters may be applicable to one or more AIoT terminals. For example, the broadcast message may carry filter information for the AIoT terminal identifier, which corresponds to one or more AIoT terminals. The filter information may include, for example, AIoT device identification information, such as mask information.

[0219] Correspondingly, after receiving a broadcast message, the AIoT terminal responds to the broadcast message by randomly accessing the reader.

[0220] This can be understood as follows: the second service request in S202 can be seen as an example of one implementation of the first request in S101. Alternatively, S202 can be considered an example of one implementation of S101. In other words, the description of the second service request in S202 can be applied to the first request in S101. Furthermore, the combination of S202 and S203 can be considered as one implementation of S101.

[0221] S204: After accessing the reader through a random access procedure, the first AIoT terminal sends an inventory reply message to the AIoTF through the reader. The inventory reply message contains a first temporary identifier and first verification information.

[0222] Accordingly, AIoTF receives the inventory reply message and obtains the first temporary identifier and the first verification information. The first verification information can be RES.

[0223] The method by which the first AIoT terminal determines the first temporary identifier and the first verification information can be found in the description in S102, and will not be repeated here. The first temporary identifier input parameter used to determine the first temporary identifier and / or the first verification information input parameter used to determine the first verification information can be carried in the broadcast message.

[0224] Optionally, if the broadcast message includes AIoT device identification information, the AIoT terminal can determine whether to initiate random access based on the AIoT device identification information. For example, if the MASK carried in the broadcast message is ****1234, after receiving the broadcast message, the AIoT terminal identified as 12341234 will initiate random access, while the AIoT terminal identified as 12341235 will not initiate random access.

[0225] S204 is explained using the example of the first AIoT terminal initiating random access. Here, it does not restrict whether other AIoT terminals besides the first AIoT terminal can initiate random access.

[0226] Optionally, the inventory reply message can be a NAS message sent by the first AIoT terminal to the AIoTF. Alternatively, the inventory reply message can be a combination of a message sent by the first AIoT terminal to the reader carrying a first temporary identifier and first verification information, and a message sent by the reader to the AIoTF carrying a first temporary identifier and first verification information. That is, the message sent by the first AIoT terminal to the reader and the message sent by the reader to the AIoTF can be different messages.

[0227] It can be considered that, in S204, the step of the first AIoT terminal sending a storage reply message to the AIoTF can be regarded as... Figure 2 An exemplary implementation of S102 in the process.

[0228] S205: When the first temporary identifier corresponds to at least two permanent identifiers, AIoTF verifies the identity of the first AIoT terminal based on the first verification information and the at least two permanent identifiers respectively, and determines the permanent identifier of the first AIoT terminal from the at least two permanent identifiers based on the identity verification result.

[0229] Taking the example that at least two permanent identifiers are a first permanent identifier and a second permanent identifier, S205 includes at least the following steps S205-1a to S205-3a:

[0230] S205-1a: The AIoTF sends a first verification request to the ADM. The first verification request includes a first permanent identifier and first verification information, which is used to request the ADM to authenticate the first AIoT terminal based on the first permanent identifier and the first verification information. In other words, the first verification request can be used to verify whether the first permanent identifier is a permanent identifier of the first AIoT terminal.

[0231] S205-2a: The ADM determines the authentication result of the first AIoT terminal based on the first permanent identifier and the first authentication information, and the authentication result may indicate or be used to determine that the first permanent identifier is a permanent identifier of the first AIoT terminal.

[0232] The method for determining the verification result can be found in the description of the implementation method of ADM verifying the identity of the first AIoT terminal based on the first permanent identifier and RES in the first verification information in S103, which will not be repeated here.

[0233] S205-3a: The ADM sends the authentication result of the first AIoT terminal based on the first authentication information to the AIoTF. Accordingly, the AIoTF can determine the first permanent identifier as the permanent identifier of the first AIoT terminal based on the authentication result. Optionally, the authentication result can be carried in the first authentication response corresponding to the first authentication request.

[0234] The steps S205-1a to S205-3a above are illustrated by the example of the AIoTF sending a first verification request carrying a first permanent identifier and first verification information to the ADM, and the ADM performing authentication of the first AIoT terminal based on the first verification request. These steps S205-1a to S205-3a can also be replaced by the AIoTF sending a second verification information request carrying the first permanent identifier and first verification information input parameters to the ADM, and the ADM providing second verification information to the AIoTF based on the second verification information request, so that the AIoTF determines the authentication result based on the first and second verification information. The implementation of the latter can be found in the description of the implementation method of the ADM receiving the second verification information in S103, and will not be repeated here.

[0235] Optionally, S205 may also include the following steps S205-1b to S205-3b:

[0236] S205-1b: The AIoTF sends a second authentication request to the ADM. The second authentication request includes a second permanent identifier and first authentication information, and is used to request the ADM to authenticate the first AIoT terminal based on the second permanent identifier and the first authentication information. Alternatively, the first authentication request can be used to verify whether the second permanent identifier is a permanent identifier of the first AIoT terminal.

[0237] S205-2b: The ADM determines that the first AIoT terminal has failed to authenticate the first authentication information based on the second permanent identifier and the first authentication information.

[0238] The verification method can be found in the description of the implementation method of ADM verifying the identity of the first AIoT terminal based on the second permanent identifier and RES in the third verification information in S103, which will not be repeated here.

[0239] S205-3b: The ADM sends a second authentication response corresponding to the second authentication request to the AIoTF to indicate that the authentication of the first AIoT terminal failed. Accordingly, the AIoTF can determine, based on the second authentication response, that the second permanent identifier is not the permanent identifier of the first AIoT terminal.

[0240] Specifically, steps S205-1b to S205-3b can be performed before S205-1a, S205-2a, or S205-3a, or steps S205-1b to S205-3b can be performed in parallel with steps S205-1a to S205-3a.

[0241] The above steps S205-1b to S205-3b are illustrated by taking the example of the AIoTF sending a second authentication request carrying the second permanent identifier and the first authentication information to the ADM, and the ADM performing authentication of the first AIoT terminal based on the second authentication request. These steps S205-1b to S205-3b can also be replaced by the AIoTF sending a third authentication information request carrying the second permanent identifier and the first authentication information input parameters to the ADM, and the ADM providing third authentication information to the AIoTF based on the third authentication information request, so that the AIoTF determines the authentication result based on the first authentication information and the third authentication information. The implementation of the latter can be found in the description of the implementation method of the ADM receiving the response to the third authentication information request in S103, and will not be repeated here.

[0242] The above S205, or S205-1a to S205-3a, can be considered as Figure 2 An exemplary implementation of S103 to S104.

[0243] S206: The AIoTF sends an inventory reply message to the AF via the NEF. This message may include the permanent identifier of the first AIoT terminal and / or the identifier of the first AIoT terminal that the AF can recognize.

[0244] According to S205-1a to S205-3a, if it is determined that the first permanent identifier is the permanent identifier of the first AIoT terminal, the inventory reply message may include the first permanent identifier.

[0245] Additionally, the AIoTF can determine the identifier of the first AIoT terminal that the AF can recognize based on the first permanent identifier; that is, the inventory reply message can contain the identifier of the first AIoT terminal that the AF can recognize. The identifier of the first AIoT terminal that the AF can recognize is, for example, the GPSI of the first AIoT terminal.

[0246] above Figure 3This application provides an implementation of the communication method provided in its embodiments when inventory is triggered by an AIoTF. This implementation should not be construed as encompassing all implementations of the communication method shown in this application. For example, inventory can also be initiated by the AIoTF according to certain configurations or strategies. Furthermore, inventory can be triggered by other network elements besides the AIoTF, including but not limited to the AMF or SMF.

[0247] Optional, Figure 3 During the process, AIoTF can also store, manage, and / or maintain a list of temporary identifiers, which may contain the correspondence between temporary and permanent identifiers of AIoT terminals. This correspondence between temporary and permanent identifiers of AIoT terminals in the list can be determined after AIoTF determines the correspondence between AIoT terminals and input parameters. The method for determining the correspondence between temporary and permanent identifiers can be found in the explanation of this method in S103; here, only a combination of... Figure 3 The process will be used as an example to introduce when to determine the correspondence, without repeating the explanation of how to determine the correspondence.

[0248] For example, the correspondence between the AIoT terminal and the input parameters can be determined after the AIoTF sends the second service request in S202, or after the AIoTF receives the response information of the second service request, or after receiving the inventory reply message in S204.

[0249] For example, if the temporary identifier of the first AIoT terminal is determined at least based on a random number determined by the first AIoT terminal, then in S204, the inventory reply message may also carry the random number, so that the AIoTF can determine the temporary identifier of the first AIoT terminal at least based on the random number. Therefore, the AIoTF can determine the correspondence between the temporary identifier and the permanent identifier of the first AIoT terminal after S204.

[0250] It is understandable that if the first service request is used to request the inventory of a single AIoT terminal, the temporary identifier list stored in AIoTF will at least contain the correspondence between the temporary identifier and the permanent identifier of that AIoT terminal. If the first service request is used to inventory multiple AIoT terminals, the temporary identifier list may contain the correspondence between the temporary identifiers and the permanent identifiers of multiple AIoT terminals.

[0251] For example, if the target device information in the first service request includes device group information, and the device group indicated by the group information contains multiple AIoT terminals, the temporary identifier list can contain the correspondence between the temporary identifiers and permanent identifiers of the multiple AIoT terminals. In this example, the second service request sent by the AIoTF can be used to request inventory of multiple AIoT terminals in the group of devices. The process of determining the temporary identifiers of the multiple AIoT terminals can use the same or different input parameters, which is not specifically limited in this application. For example, multiple AIoT terminals can use the same first temporary identifier random number, which is determined by the AIoTF. Alternatively, multiple AIoT terminals can use different second temporary identifier random numbers; for example, different AIoT terminals determine their own second temporary identifier random numbers.

[0252] This application embodiment also provides another communication method to support AIoTF in determining the permanent identifier of an AIoT terminal when the temporary identifier of a first AIoT terminal corresponds to multiple permanent identifiers. In this communication method, when the first temporary identifier corresponds to multiple permanent identifiers, AIoTF can regenerate temporary identifiers corresponding to multiple permanent identifiers based on the multiple permanent identifiers, and request the first AIoT terminal to perform an operation (such as an inventory operation or other operations) through the temporary identifiers corresponding to the multiple permanent identifiers respectively. The permanent identifier of the first AIoT terminal is determined from the multiple permanent identifiers based on the response result of the operation request. The response result of the operation request can indicate whether the operation was successful or failed. Since the AIoT terminal only responds to the temporary identifier corresponding to its own permanent identifier to perform the operation, if the response result indicates that the operation was successful, it means that the permanent identifier corresponding to the temporary identifier is the permanent identifier of the first AIoT terminal. If the response result indicates that the operation failed, it means that the permanent identifier corresponding to the temporary identifier is not the permanent identifier of the first AIoT terminal.

[0253] The following is combined with Figure 4 The flowchart shown describes the communication method provided in this application. Figure 4 As shown, the method may include the following steps:

[0254] S301: AIoTF sends a first request, which is used to request the inventory of one or more AIoT terminals.

[0255] S301 can be found in the description in S101, and will not be repeated here.

[0256] S302: The first AIoT terminal sends the first temporary identifier.

[0257] The difference between S302 and S102 is that the first AIoT terminal does not need to send the first verification information.

[0258] The first temporary identifier can be carried in a message sent from the first AIoT terminal to the reader, and then the reader can carry the first temporary identifier in another message and send that other message to the AIoTF. Alternatively, the reader can also transmit the first temporary identifier transparently to the AIoTF, for example, by carrying the first temporary identifier in a NAS message, without the reader needing to read or parse the first temporary identifier in the NAS message.

[0259] The method for determining the first temporary identifier can be found in the description in S102, and will not be repeated here.

[0260] S303: In the case where the first temporary identifier corresponds to multiple permanent identifiers, AIoTF determines the second temporary identifier based on the first permanent identifier among the multiple permanent identifiers.

[0261] Optionally, the plurality of permanent identifiers may include a first permanent identifier, a second permanent identifier, and optionally other permanent identifiers. The first permanent identifier and / or the second permanent identifier can be found in the description in S103, and will not be repeated here.

[0262] In S303, the second temporary identifier may be determined based on the first permanent identifier. Specifically, the second temporary identifier may be determined based on the second temporary identifier input parameters through a third algorithm. Wherein, the second temporary identifier input parameters are different from the first temporary identifier input parameters, and / or, the third algorithm is different from the first algorithm used to determine the first temporary identifier, to ensure that the first temporary identifier and the second temporary identifier are different.

[0263] The second temporary identifier input parameters may include, for example, a random number, and optionally, other parameters such as a shared key, without specific limitations. The random number may include a random number determined by AIoTF and / or a random number determined by the AIoT terminal.

[0264] Specifically, at least one parameter in the second temporary identifier input parameters differs from the parameter in the first temporary identifier input parameters. For example, the second temporary identifier input parameters may include a second temporary identifier random number, while the first temporary identifier input parameters may include a first temporary identifier random number, wherein the first temporary identifier random number and the second temporary identifier random number are different random numbers. Furthermore, the third algorithm differs from the first algorithm; for example, the third algorithm and the first algorithm are different hash algorithms.

[0265] The method for determining the second temporary identifier can be found in the description of the method for generating the first temporary identifier. For example, AIoTF can use the second permanent identifier and the second temporary identifier as input parameters, and determine the output result through a hash algorithm. This output result is the second temporary identifier, where the hash algorithm is the third algorithm.

[0266] S304: AIoTF sends a first operation request to the first AIoT terminal.

[0267] The first operation request includes a second temporary identifier, which is used to request the AIoT terminal corresponding to the second temporary identifier to perform a first operation. The first operation may also include the second temporary identifier input parameters and / or indication information of a third algorithm.

[0268] Accordingly, the first AIoT terminal receives the first operation request.

[0269] The first operation request (or second temporary identifier) ​​can be carried in a message sent by the AIoTF to the reader, and then the reader can carry the first operation request (or second temporary identifier) ​​in another message and send that other message to the first AIoT terminal. Alternatively, the reader can also transmit the first operation request (or second temporary identifier) ​​transparently to the first AIoT terminal. For example, the first operation request (or second temporary identifier) ​​can be carried in a NAS message sent by the AIoTF to the first AIoT terminal, and the reader does not need to read or parse the first operation request (or second temporary identifier) ​​in the NAS message.

[0270] Optionally, the first operation request can be a disk entry request or other operation requests, and this application does not specifically limit it. In the following description, the first operation request is a disk entry request, that is, the first operation is a disk entry operation.

[0271] S305: Optional, the first AIoT terminal performs the first operation based on the second temporary identifier.

[0272] In step S305, the first AIoT terminal can determine whether the first operation request is an operation request targeting the first AIoT terminal based on the second temporary identifier and the permanent identifier of the first AIoT terminal. If the first operation request is an operation targeting the first AIoT terminal, the first AIoT terminal can execute the first operation.

[0273] Specifically, the first AIoT terminal can determine a temporary identifier based on the second temporary identifier input parameter and the permanent identifier of the first AIoT terminal using a third algorithm. If the temporary identifier is the same as the second temporary identifier, it can be proven that the operation request is for the first AIoT terminal, and therefore the first AIoT terminal can perform the first operation. Conversely, if the temporary identifier is different from the second temporary identifier, it can be proven that the operation request is not for the first AIoT terminal, and therefore the first AIoT terminal does not perform the first operation.

[0274] Optionally, the first AIoT terminal can obtain the second temporary identifier input parameter from the first operation request. Alternatively, the second temporary identifier input parameter can be considered to be a default setting between the first AIoT terminal and the AIoTF, or determined through previous messages. For example, the AIoTF can also carry the second temporary identifier input parameter in the first request, thus allowing the first AIoT terminal to obtain the second temporary identifier input parameter from the first request.

[0275] Optionally, the third algorithm can be determined by the indication information of the third algorithm in the first operation request. Alternatively, the third algorithm can be a default algorithm, in which case the first operation request does not need to carry the indication information of the third algorithm. Furthermore, the indication information of the third algorithm can also be carried in the first request or other messages; this application does not specifically limit this.

[0276] S306: The first AIoT terminal sends a response message to the AIoTF for the first operation request.

[0277] Accordingly, AIoTF receives the response information.

[0278] The response information can be carried in a message sent from the first AIoT terminal to the reader, and then the reader can carry the first operation request (or the second temporary identifier) ​​in another message and send that other message to the AIoTF. Alternatively, the reader can also transmit the response information transparently to the AIoTF. For example, the response information can be carried in a NAS message sent from the first AIoT terminal to the AIoTF, and the reader does not need to read or parse the response information in the NAS message.

[0279] It is understandable that, for inventory operations, the response information may carry a temporary identifier of the first AIoT terminal, such as a second temporary identifier. Alternatively, it can be considered that, for inventory operations, the first operation includes the first AIoT terminal sending its temporary identifier to the AIoTF; therefore, S305 and S306 can be the same action.

[0280] S307: AIoTF determines the first permanent identifier as the permanent identifier of the first AIoT terminal based on the response information of the first operation request.

[0281] In one possible example, the first AIoT terminal sends a response to the first operation request upon successful execution of the first operation. That is, if the first permanent identifier is the permanent identifier of the first AIoT terminal, the first AIoT terminal sends the response to the first operation request to the AIoTF. Accordingly, upon receiving this response, the AIoTF can determine that the first permanent identifier is the permanent identifier of the first environmental IoT device.

[0282] Another possible example is that the response information may include information indicating whether the first operation was successful. That is, the first AIoT terminal will send a response message regardless of whether the first permanent identifier is a permanent identifier of the first AIoT terminal. Specifically, if the first permanent identifier is a permanent identifier of the first AIoT terminal, the response information may include information indicating that the first operation was successful; if the first permanent identifier is not a permanent identifier of the first AIoT terminal, the response information may include information indicating that the first operation failed. In this example, the AIoTF can determine that the first permanent identifier is a permanent identifier of the first AIoT terminal if the response information to the first operation request includes information indicating that the first operation was successful; conversely, the AIoTF can determine that the first permanent identifier is not a permanent identifier of the first AIoT terminal if the response information to the first operation request includes information indicating that the first operation failed.

[0283] Optionally, prior to S307, the AIoTF may also determine a third temporary identifier based on the second permanent identifier, and request the first AIoT terminal to perform the first operation through the third temporary identifier. Referring to the description in S305 to S306, if the second permanent identifier is not a permanent identifier of the first AIoT terminal, the first AIoT terminal does not send a response to the second operation request, or the response to the second operation request sent carries information indicating that the second operation has failed. Accordingly, the AIoTF may determine that the second permanent identifier is not a permanent identifier of the first AIoT terminal if it does not receive a response to the second operation request, or if it determines that the response to the second operation request carries information indicating that the second operation has failed.

[0284] For example, if the AIoTF determines that the second permanent identifier is not a permanent identifier of the first AIoT terminal, it can execute steps S305 to S307 to determine whether the first permanent identifier is a permanent identifier of the first AIoT terminal. Alternatively, the AIoTF can determine whether the first permanent identifier is a permanent identifier of the first AIoT terminal and whether the second permanent identifier is a permanent identifier of the first AIoT terminal in parallel. The AIoTF can carry the aforementioned first operation request and second operation request in the same message sent to the first AIoT terminal.

[0285] In one possible implementation, the third temporary identifier can be determined by a fourth algorithm based on the second permanent identifier and the third temporary identifier input parameters. Specifically, the third temporary identifier input parameters differ from the first temporary identifier input parameters, and / or the fourth algorithm differs from the first algorithm. In other words, the method for generating the third temporary identifier differs from the method for generating the first temporary identifier. Furthermore, the second temporary identifier input parameters differ from the third temporary identifier input parameters, and / or the third algorithm differs from the fourth algorithm. Again, the method for generating the third temporary identifier differs from the method for generating the fourth temporary identifier.

[0286] The process of determining the second temporary identifier input parameter and / or the third temporary identifier input parameter can be similar to the process of determining the first temporary identifier input parameter. The third and fourth algorithms are similar to the first algorithm and will not be described again.

[0287] The following is based on Figure 5 For example, this describes the process by which the AIoTF determines the permanent identifier of the first AIoT terminal when it receives a storage request from the AF and determines that the temporary identifier of the first AIoT terminal being stored corresponds to multiple permanent identifiers. In this process, the AIoTF can base its determination on... Figure 4 The communication method shown determines the permanent identifier of the first AIoT terminal.

[0288] S401: AF sends a first service request to AIoTF via NEF to request inventory of one or more AIoT terminals.

[0289] Optionally, after receiving the first service request, AIoTF can send a response message to AF.

[0290] The above S401 can be found in [reference]. Figure 3 The description of S201 in the process will not be repeated here.

[0291] S402: AIoTF sends a second service request to the reader to request the inventory of one or more AIoT terminals.

[0292] Optionally, upon receiving the second service request, the reader may send a response to the second service request to the AIoTF.

[0293] The above S402 can be found in [reference]. Figure 3 The description of S202 in the process will not be repeated here.

[0294] S403: The reader sends a broadcast message, which is used to inventory AIoT terminals.

[0295] Correspondingly, after receiving a broadcast message, the AIoT terminal responds to the broadcast message by randomly accessing the reader.

[0296] The above S403 can be found in [reference]. Figure 3 The description of S203 in the process will not be repeated here.

[0297] This can be understood as follows: the second service request in S402 can be seen as an example of an implementation of the first request in S301. Alternatively, S402 can be seen as an example of an implementation of S302. In other words, the description of the second service request in S402 can be applied to the first request in S201. Furthermore, the combination of S402 and S403 can be considered as an implementation of S101.

[0298] S404: After accessing the reader through a random access procedure, the first AIoT terminal sends an inventory reply message to the AIoTF through the reader. The inventory reply message contains a first temporary identifier.

[0299] Accordingly, AIoTF receives the inventory reply message and obtains the first temporary identifier.

[0300] The method by which the first AIoT terminal determines the first temporary identifier can be referred to in S102, and will not be repeated here.

[0301] S404 can be found in the description of S204, and the repetitions will not be repeated here. The difference between S404 and S204 is that the inventory reply message in S404 may not carry RES.

[0302] It can be considered that, in S404, the step of the first AIoT terminal sending a disk inventory reply message to the AIoTF can be regarded as... Figure 4 An exemplary implementation of S302 in the process.

[0303] S405: When the first temporary identifier corresponds to at least two permanent identifiers, the AIoTF reads the temporary identifiers corresponding to the at least two permanent identifiers respectively, requests the first AIoT terminal to perform an inventory operation based on the temporary identifiers corresponding to the at least two permanent identifiers, and determines the permanent identifier of the first AIoT terminal from the at least two permanent identifiers based on the result of the inventory operation.

[0304] Taking the example that at least two permanent identifiers are a first permanent identifier and a second permanent identifier, S405 includes at least the following steps 405-1a to S405-3a:

[0305] S405-1a: AIoTF determines the second temporary identifier based on the first permanent identifier and the second temporary identifier input parameters through a third algorithm.

[0306] The method for determining the second temporary identifier can be found in the description in S303.

[0307] S405-1a can be considered as Figure 4 An exemplary implementation of S303.

[0308] S405-2a: The AIoTF sends a first operation request to the first AIoTF terminal. The first operation request is used to request the AIoT terminal corresponding to the second temporary identifier to perform an inventory operation. The first operation request includes the second temporary identifier.

[0309] Optionally, the first operation request may also include a second temporary identifier input parameter and / or a third algorithm. For example, if the second temporary identifier input parameter and / or the third algorithm are determined by AIoTF, the first operation request may carry the second temporary identifier input parameter and / or the third algorithm. The second temporary identifier input parameter and / or the third algorithm may also be carried in the second service request, without specific limitation.

[0310] S405-2a can be considered as Figure 4 An exemplary implementation of S304.

[0311] S405-3a: When the second temporary identifier is the temporary identifier of the first AIoT terminal, that is, when the first permanent identifier is the permanent identifier of the first AIoT terminal, the first AIoT terminal sends a response message of the first operation request to the AIoTF, which includes the second temporary identifier.

[0312] Referring to the description in S305, the first AIoT terminal can determine whether the first operation request is an inventory operation request for the first AIoT terminal based on the second temporary identifier and the permanent identifier of the first AIoT terminal. If the first operation request is an operation for the first AIoT terminal, the first AIoT terminal can execute the first operation.

[0313] Specifically, the first AIoT terminal can determine its temporary identifier using a third algorithm based on its permanent identifier and a second temporary identifier as input parameters. If this temporary identifier is the same as the second temporary identifier carried in the first operation request, it can be determined that the first operation request is for the first AIoT terminal; conversely, if the temporary identifier is different from the second temporary identifier carried in the first operation request, it can be determined that the first operation request is not for the first AIoT terminal, that is, the second temporary identifier is determined to be the temporary identifier of the first AIoT terminal, and the first permanent identifier is determined to be the permanent identifier of the first AIoT terminal.

[0314] Optionally, S405 may also include the following steps S405-1b to S405-3b:

[0315] S405-3a can be considered as Figure 4 An exemplary implementation of S306.

[0316] S405-1b: AIoTF determines the third temporary identifier based on the second permanent identifier and the third temporary identifier input parameters through a fourth algorithm.

[0317] The method for determining the third temporary identifier can be found in the section on determining the third temporary identifier, and will not be repeated here.

[0318] S405-2b: The AIoTF sends a second operation request to the first AIoTF terminal. The second operation request is used to request the AIoT terminal corresponding to the third temporary identifier to perform an inventory operation. The second operation request includes the third temporary identifier.

[0319] Optionally, the second operation request may also include indication information for the third temporary identifier input parameters and / or the fourth algorithm. For example, if the third temporary identifier input parameters and / or the fourth algorithm are determined by AIoTF, the second operation request may carry indication information for the third temporary identifier input parameters and / or the fourth algorithm. The indication information for the third temporary identifier input parameters and / or the fourth algorithm may also be carried in the second service request, without specific limitation.

[0320] S405-3b: If the third temporary identifier is not the temporary identifier of the first AIoT terminal, that is, if the second permanent identifier is not the permanent identifier of the first AIoT terminal, the first AIoT terminal does not send the response information of the first operation request to the AIoTF, that is, it does not need to perform inventory operation.

[0321] Specifically, the first AIoT terminal can determine its temporary identifier using a fourth algorithm based on its permanent identifier and a third temporary identifier input parameters. If this temporary identifier differs from the third temporary identifier carried in the first operation request, it can be determined that the first operation request is not an operation request for the first AIoT terminal, and the first AIoT terminal will not perform inventory operations subsequently.

[0322] S406: The AIoTF sends an inventory reply message to the AF via the NEF. This message may include the permanent identifier of the first AIoT terminal and / or the identifier of the first AIoT terminal that the AF can recognize.

[0323] According to S405-1a to S405-3a, if it is determined that the first permanent identifier is the permanent identifier of the first AIoT terminal, the inventory reply message may include the first permanent identifier. Alternatively, the AIoTF can determine the identifier of the first AIoT terminal that the AF can recognize, such as GPSI, based on the first permanent identifier. The inventory reply message may carry this GPSI, and optionally, the inventory reply message may also include the first permanent identifier.

[0324] S406 can be considered as Figure 4 An exemplary implementation of S306.

[0325] above Figure 5 This application provides an implementation of the communication method provided in its embodiments when inventory is triggered by an AIoTF. This implementation should not be construed as encompassing all implementations of the communication method shown in this application. For example, inventory can also be initiated by the AIoTF according to certain configurations or strategies. Furthermore, inventory can be triggered by other network elements besides the AIoTF, including but not limited to the AMF or SMF.

[0326] This application embodiment also provides another communication method. When AIoTF determines that the temporary identifier of the first AIoT terminal corresponds to multiple permanent identifiers, the input parameters used to determine the temporary identifier of the first AIoT terminal can be updated, that is, the temporary identifier of the first AIoT terminal is updated, so that the updated temporary identifier of the first AIoT terminal does not correspond to multiple permanent identifiers, thereby avoiding the situation where the temporary identifier of the first AIoT terminal corresponds to multiple permanent identifiers.

[0327] like Figure 6 As shown, this method can be implemented through the following steps:

[0328] S501: AIoTF determines the first temporary identifier input parameter, which is used to determine the first temporary identifier of the first AIoT terminal.

[0329] Referring to the description in S103, AIoTF can determine the permanent identifier corresponding to the first temporary identifier.

[0330] S502: When the first temporary identifier corresponds to a permanent identifier, that is, when the number of permanent identifiers corresponding to the first temporary identifier is 1, the AIoTF sends the first temporary identifier input parameter to the first AIoT terminal. This first temporary identifier input parameter is used by the first AIoT terminal to determine the first temporary identifier. The permanent identifier corresponding to the first temporary identifier is also the permanent identifier of the first AIoT terminal.

[0331] For example, AIoTF can determine the permanent identifier corresponding to the first temporary identifier through ADM. The implementation method can be found in the description in S103.

[0332] For example, the AIoTF can determine whether a first temporary identifier corresponds to a permanent identifier based on duplicate temporary identifiers in the temporary identifier list. The AIoTF can provide the ADM with a first temporary identifier input parameter, and optionally also provide the permanent identifier of the first AIoT terminal, and obtain a temporary identifier list from the ADM. This temporary identifier list includes the first temporary identifier of the first AIoT terminal, which can be determined based on the first AIoT's permanent identifier and the first temporary identifier input parameter. Optionally, the temporary identifier list may also include the identifiers of at least one AIoT terminal other than the first AIoT terminal.

[0333] In the case that there is no duplicate first temporary identifier in the list of temporary identifiers, that is, there are no multiple temporary identifiers in AIoT that are both first temporary identifiers, the first temporary identifier can be identified as a permanent identifier.

[0334] For example, the ADM can determine the first temporary identifier input parameter, and if the ADM determines that there is no duplicate first temporary identifier in the temporary identifier list, the ADM sends the first temporary identifier input parameter to the AIoTF. The action of the ADM determining whether there is a duplicate first temporary identifier in the temporary identifier list can be considered to have been performed before S501.

[0335] Optionally, if the first temporary identifier corresponds to at least two permanent identifiers, AIoTF can determine a fourth temporary identifier input parameter, which is used to determine the fourth temporary identifier of the first AIoT terminal. Furthermore, AIoTF can also determine the number of permanent identifiers corresponding to the fourth temporary identifier.

[0336] In the case where the fourth temporary identifier corresponds to a permanent identifier, AIoTF sends the fourth temporary identifier input parameter to the first AIoT terminal. This fourth temporary identifier input parameter is used by the first AIoT terminal to determine the fourth temporary identifier. The permanent identifier corresponding to the fourth temporary identifier is also the permanent identifier of the first AIoT terminal.

[0337] For example, AIoTF can determine the permanent identifier corresponding to the fourth temporary identifier through ADM. The implementation method can be found in the description of the method of determining the corresponding permanent identifier based on the first temporary identifier in S103.

[0338] If the fourth temporary identifier, determined according to the fourth temporary identifier input parameter, corresponds to at least two permanent identifiers, AIoTF can update the fourth temporary identifier input parameter again, for example, to determine the fifth temporary identifier input parameter, until the temporary identifier determined according to the updated input parameter corresponds to a permanent identifier.

[0339] The fourth temporary identifier input parameter and / or the fifth temporary identifier input parameter can be similar to the first temporary identifier input parameter, and will not be described in detail here.

[0340] The following is based on Figure 7 For example, this illustrates the process by which the AIoTF avoids having multiple permanent identifiers corresponding to the temporary identifier of the first AIoT terminal when it receives a storage request from the AF. In this process, the AIoTF can... Figure 6 The communication method shown determines the input parameters corresponding to the temporary identifier of the first AIoT terminal.

[0341] S601: AF sends a first service request to AIoTF via NEF to request inventory of one or more AIoT terminals.

[0342] Optionally, after receiving the first service request, AIoTF can send a response message to AF.

[0343] The above S601 can be found in [reference]. Figure 3 The description of S201 in the process will not be repeated here.

[0344] S602: AIoTF obtains a first temporary identifier input parameter, which is used to determine the temporary identifier of the first AIoT terminal.

[0345] Optionally, the first temporary identifier input parameter may be assigned to an AIoT terminal group, which includes one or more AIoT terminals, including the first AIoT terminal.

[0346] S602 can be used as Figure 6 An example of one implementation of S501.

[0347] S603: When the first temporary identifier input parameter causes the temporary identifier of the first AIoT terminal to correspond to a permanent identifier, the AIoTF sends a second service request to the reader to request the inventory of one or more AIoT terminals. The second service request includes the first temporary identifier input parameter. Optionally, the second service request includes a group identifier for the AIoT terminal group. This permanent identifier can be referred to as the first permanent identifier, which is also the permanent identifier of the first AIoT terminal.

[0348] Optionally, upon receiving the second service request, the reader may send a response to the second service request to the AIoTF.

[0349] The above S603 can be found in [reference]. Figure 3 The description of S202 in the process is repeated and will not be elaborated upon. The difference lies in the fact that the second service request in S603 carries the first temporary identifier input parameter.

[0350] Optionally, prior to S603, AIoTF or ADM can determine whether the first temporary identifier input parameter causes the temporary identifier of the first AIoT terminal to correspond to a permanent identifier.

[0351] One possible implementation is that in S602, the AIoTF generates a first temporary identifier input parameter and sends it to the ADM to obtain a list of temporary identifiers provided by the ADM. The temporary identifier list may include multiple temporary identifiers determined based on the first temporary identifier input parameter and the permanent identifiers of multiple AIoT terminals. If there are no duplicate temporary identifiers in the temporary identifier list, it can be determined that the first temporary identifier input parameter causes the temporary identifier of the first AIoT terminal to correspond to a permanent identifier.

[0352] ADM can determine the permanent identifiers of multiple AIoT terminals based on temporary identifiers of multiple AIoT terminals, a first temporary identifier input parameter, and a first algorithm, and obtain a temporary identifier list. This temporary identifier list includes the temporary identifiers of one or more AIoT terminals. Specifically, the one or more AIoT terminals include a first AIoT terminal, meaning the temporary identifier list includes the first temporary identifier of the first AIoT terminal.

[0353] ADM can also send a list of temporary identifiers to AIoTF. AIoTF can determine whether there are duplicate temporary identifiers in this list. If duplicate temporary identifiers exist, it means that multiple AIoT terminals have duplicate temporary identifiers; if no duplicate temporary identifiers exist, it means that multiple AIoT terminals have unique temporary identifiers. For example, suppose the temporary identifier list includes {temporary identifier #1, temporary identifier #2, temporary identifier #1, temporary identifier #3}, where two AIoT terminals both have temporary identifier #1. In this case, there is a duplicate temporary identifier.

[0354] If there are no duplicate temporary identifiers in the temporary identifier list, that is, if the permanent identifiers corresponding to the temporary identifiers are not duplicated, the AIoTF can execute S603 and send a second service request containing the first temporary identifier input parameter. If at least one temporary identifier in the temporary identifier list corresponds to multiple permanent identifiers, the AIoTF can reallocate the first temporary identifier input parameter. For example, the method of reallocating the first temporary identifier input parameter may be to change the random number 1 (nonce1) in the first temporary identifier input parameter to a random number 2 (nonce1) until there are no duplicate temporary identifiers in the temporary identifier list.

[0355] Another possible implementation is that, prior to S602, the ADM generates a first temporary identifier input parameter and provides a list of temporary identifiers to the AIoTF. The temporary identifier list may include multiple temporary identifiers determined based on the first temporary identifier input parameter and the permanent identifiers of multiple AIoT terminals. If no duplicate temporary identifiers exist in the temporary identifier list, it can be determined that the first temporary identifier input parameter causes the temporary identifier of the first AIoT terminal to correspond to a permanent identifier. Subsequently, S602 can be executed, whereby the ADM sends the first temporary identifier input parameter to the AIoTF, and the AIoTF receives the first temporary identifier input parameter accordingly.

[0356] For example, before S602, the ADM can generate a first temporary identifier input parameter, and the ADM can determine the permanent identifiers of the multiple AIoT terminals based on the temporary identifiers of multiple AIoT terminals, the first temporary identifier input parameter, and a first algorithm to obtain a temporary identifier list. If there are no duplicate temporary identifiers in this temporary identifier list, that is, if the permanent identifiers corresponding to the temporary identifiers in the temporary identifier list are not duplicated, the ADM can send the first temporary identifier input parameter to the AIoTF. In other words, the first temporary identifier input parameter obtained by the AIoTF through S602 can guarantee that the permanent identifiers corresponding to the temporary identifiers in the temporary identifier list are not duplicated. If at least one temporary identifier in the temporary identifier list corresponds to multiple permanent identifiers, the ADM can reallocate the first temporary identifier input parameter. For example, the method of reallocating the first temporary identifier input parameter is to change the random number 1 (nonce1) in the first temporary identifier input parameter to a random number 2 (nonce1) until there are no duplicate temporary identifiers in the temporary identifier list, and then send the first temporary identifier input parameter to the AIoTF.

[0357] S603 can be used as Figure 6 An example of one implementation of S502.

[0358] S604: The reader sends a broadcast message, which is used to inventory AIoT terminals.

[0359] Correspondingly, after receiving a broadcast message, the AIoT terminal responds to the broadcast message by randomly accessing the reader.

[0360] The above S603 can be found in [reference]. Figure 3 The description of S203 in the process will not be repeated here.

[0361] This can be understood as follows: the second service request in S402 can be seen as an example of an implementation of the first request in S301. Alternatively, S402 can be seen as an example of an implementation of S302. In other words, the description of the second service request in S402 can be applied to the first request in S201. Furthermore, the combination of S402 and S403 can be considered as an implementation of S101.

[0362] S605: After accessing the reader through a random access procedure, the first AIoT terminal sends an inventory reply message to the AIoTF through the reader. The inventory reply message contains a first temporary identifier.

[0363] Accordingly, AIoTF receives the inventory reply message and obtains the first temporary identifier of the first AIoT terminal.

[0364] The method by which the first AIoT terminal determines the first temporary identifier can be referred to in S102, and will not be repeated here.

[0365] S605 can be found in the description of S204, and the repetitions will not be repeated here. The difference between S604 and S204 is that the inventory reply message in S604 may not carry RES.

[0366] S606: The AIoTF sends an inventory reply message to the AF via the NEF. This message may include a first permanent identifier and / or an identifier of the first AIoT terminal that the AF can recognize. The permanent identifier of the first AIoT terminal corresponds to the first permanent identifier.

[0367] based on Figure 7 The process shown can send input parameters to AIoT terminals to determine the accuracy of temporary identifiers, verify whether the input parameters will cause duplicate temporary identifiers of multiple AIoT terminals, and avoid duplicate temporary identifiers of AIoT terminals by changing the input parameters in the case of duplicate temporary identifiers.

[0368] It is understood that, in order to achieve the functions in the above embodiments, each device may include corresponding hardware structures and / or software modules for performing the above functions. Those skilled in the art should readily recognize that, based on the units and method steps described in conjunction with the embodiments disclosed in this application, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0369] Figure 8 and Figure 9 The diagram illustrates the possible communication devices provided in the embodiments of this application. These communication devices can be used to implement the functions of the first device in the above method embodiments, and thus also achieve the beneficial effects of the above method embodiments. The first device can be an AIoTF, or a module or component applied in an AIoTF, such as a chip.

[0370] like Figure 8 As shown, the communication device 800 includes a processing unit 810 and a transceiver unit 820. The communication device 800 is used to implement the above-mentioned... Figures 2 to 7 The function of the first device in any of the illustrated method flows.

[0371] Among them, when the communication device 800 is used to achieve Figure 2 In the method embodiment shown, the first device functions as follows: the transceiver unit 820 is used to send a first request, as detailed in S101. The transceiver unit 820 can also be used to receive a first temporary identifier and first authentication information from the first AIoT terminal, as detailed in S102. The processing unit 810 can be used to obtain the authentication result of the first AIoT terminal for the first authentication information, as detailed in S103. The processing unit 810 can also be used to determine the permanent identifier of the first AIoT terminal corresponding to the first temporary identifier based on the authentication result, as detailed in S104.

[0372] When the communication device 800 is used to implement Figure 4In the method embodiment shown, the first device functions as follows: Transceiver unit 820 is used to send a first request, as detailed in S301. Transceiver unit 820 can also be used to receive a first temporary identifier of the first AIoT terminal, as detailed in S302. Processing unit 810 can be used to determine a second temporary identifier based on the first permanent identifier among multiple permanent identifiers when the first temporary identifier corresponds to multiple permanent identifiers, as detailed in S303. Transceiver unit 820 can also be used to send a first operation request, including the second temporary identifier, as detailed in S304. Transceiver unit 820 can also be used to receive response information for the first operation request, as detailed in S306. Processing unit 810 can be used to determine, based on the response information for the first operation request, that the first permanent identifier is a permanent identifier of the first AIoT terminal, as detailed in S307.

[0373] When the communication device 800 is used to implement Figure 6 In the method embodiment shown, the first device functions as follows: the processing unit 810 can be used to determine the first input parameter, as detailed in S501. The transceiver unit 820 can be used to send the first input parameter when the first temporary identifier corresponds to a permanent identifier, as detailed in S502.

[0374] For a more detailed description of the aforementioned processing unit 810 and transceiver unit 820, please refer to [reference needed]. Figures 2 to 7 The relevant descriptions in any of the illustrated method embodiments are provided. For example, the technical terms involved in the above operations of processing unit 810 and transceiver unit 820 can be found in the descriptions in the above method embodiments, and will not be repeated here.

[0375] like Figure 9 As shown, the communication device 900 includes a processor 910 and an interface circuit 920. The processor 910 and the interface circuit 920 are coupled to each other. It is understood that the interface circuit 920 can be a transceiver or an input / output interface. Optionally, the communication device 900 may also include a memory 930 for storing instructions executed by the processor 910, or storing input data required by the processor 910 to execute instructions, or storing data generated after the processor 910 executes instructions.

[0376] When the communication device 900 is used to implement Figures 2 to 7 In any of the methods shown, the processor 910 is used to implement the functions of the processing unit 810, and the interface circuit 920 is used to implement the functions of the transceiver unit 820.

[0377] When the aforementioned communication device is a chip applied in the first to third devices or a consensus node, the chip implements the processing functions of the corresponding devices in the above method embodiments. The chip can receive information sent to the device by other devices through other modules in the device (such as radio frequency modules, antennas, or communication interfaces), or the chip can send information to other modules in the device (such as radio frequency modules, antennas, or interfaces). This information can be sent by the device to other network elements or devices.

[0378] It is understood that the processor in the embodiments of this application may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor may be a microprocessor or any conventional processor.

[0379] The method steps in the embodiments of this application can be implemented in hardware or in software instructions executable by a processor. The software instructions can consist of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, portable hard disks, compact disc read-only memory (CD-ROM), or any other form of storage medium well known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. The storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Furthermore, the ASIC can reside in one or more of the first to third devices or consensus nodes. The processor and storage medium can also exist as discrete components in one or more of the first to third devices or consensus nodes.

[0380] This application also provides a communication system, including a first device and a second device for implementing the above method embodiments, to achieve... Figure 2 or Figure 3 The method shown. Alternatively, the system may include a first device and a first AIoTF terminal to support... Figures 4 to 7Any of the methods shown. The second device is, for example, an ADM or a module or chip within an ADM, such as a chip. The first AIoTF terminal can also be replaced with a module or component within an AIoTF terminal, such as a chip.

[0381] This application also provides a communication method, which corresponds to the functions implemented by the above communication system.

[0382] This application also provides a computer-readable storage medium for storing computer programs or instructions that, when run, enable the methods described in the above method embodiments to be implemented.

[0383] This application also provides a computer program product that, when run on a computer, enables the method shown in the method embodiment to be implemented.

[0384] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both types of storage media.

[0385] In the description of this application, terms such as "first" and "second" are used only for the purpose of distinguishing descriptions and should not be construed as indicating or implying relative importance, nor should they be construed as indicating or implying order. It should be noted that this application does not limit the order in which "first," "second," etc., appear; for example, "second" may appear first, followed by "first," and this application does not impose such a limitation.

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

[0387] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0388] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers described above does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

Claims

1. A communication method, characterized in that, include: Send a first request, the first request being used to request inventory of one or more environmental IoT devices; Receive a first temporary identifier and first verification information from a first environmental IoT device, wherein the one or more environmental IoT devices include the first environmental IoT device, and the first verification information is used to verify the identity of the first environmental IoT device; Obtain the authentication result of the first environmental IoT device based on the first verification information; The permanent identifier of the first environmental IoT device corresponding to the first temporary identifier is determined based on the authentication result of the first environmental IoT device.

2. The method as described in claim 1, characterized in that, Before determining the permanent identifier of the first environmental IoT device corresponding to the first temporary identifier based on the authentication result of the first environmental IoT device, the method further includes: The permanent identifier corresponding to the first temporary identifier is determined to include a first permanent identifier and a second permanent identifier, and the permanent identifier of the first environmental IoT device corresponding to the first temporary identifier is either the first permanent identifier or the second permanent identifier.

3. The method as described in claim 2, characterized in that, Obtaining the authentication result of the first environmental IoT device based on the first verification information includes: Send a first verification request to the second device. The first verification request includes the first verification information and the first permanent identifier. The first verification request is used to request the verification of the identity of the first environmental IoT device based on the first verification information and the first permanent identifier. Receive a first verification response, which includes the authentication result.

4. The method as described in claim 2, characterized in that, Obtaining the authentication result of the first environmental IoT device based on the first verification information includes: Send a second verification information request to the second device. The second verification information request includes the first permanent identifier and the first verification information input parameters. The first verification information is determined based on the first verification information input parameters. The second verification information request is used to request the second verification information. Receive the second verification information, which is determined based on the key of the first environmental IoT device and the verification information input parameters. The key of the first environmental IoT device is determined based on the first permanent identifier. The authentication result is determined based on the first verification information and the second verification information.

5. The method as described in claim 3 or 4, characterized in that, The step of determining the permanent identifier of the first environmental IoT device corresponding to the first temporary identifier based on the authentication result of the first environmental IoT device includes: If the authentication result of the first environmental IoT device indicates that the authentication of the first environmental IoT device is successful, the first permanent identifier is determined as the permanent identifier of the first environmental IoT device.

6. The method as described in claim 5, characterized in that, The method further includes: Send a second verification request to the second device. The second verification request includes the first verification information and the second permanent identifier. The second verification request is used to request the verification of the identity of the first environmental IoT device based on the first verification information and the second permanent identifier. Receive a second verification response, which indicates the verification result of the first IoT device's authentication failure.

7. The method as described in claim 5, characterized in that, The method further includes: Send a third verification information request to the second device. The third verification information request includes the second permanent identifier and the first verification information input parameters. The first verification information is determined based on the first verification information input parameters. The third verification information request is used to request third verification information. Receive the third verification information, which is determined based on the second permanent identifier and the verification information input parameters; Based on the first verification information and the third verification information, it is determined that the authentication of the first environmental IoT device failed.

8. The method according to any one of claims 2-7, characterized in that, The determination of the permanent identifier corresponding to the first temporary identifier includes a first permanent identifier and a second permanent identifier, including: Based on the first temporary identifier and the identifier correspondence, the permanent identifier corresponding to the first temporary identifier is determined to include a first permanent identifier and a second permanent identifier. The identifier correspondence includes the correspondence between multiple temporary identifiers and multiple permanent identifiers. The multiple temporary identifiers include the first temporary identifier, and the multiple permanent identifiers include the first permanent identifier and the second permanent identifier.

9. The method according to any one of claims 1-8, characterized in that, The first temporary identifier is determined by a first algorithm based on the permanent identifier of the first environmental IoT device and the first temporary identifier input parameters; The first verification information is determined by a second algorithm based on the key of the first environmental IoT device and the first verification information input parameters. The key of the first environmental IoT device is determined based on the permanent identifier of the first environmental IoT device. Wherein, the first temporary identifier input parameter and the first verification information input parameter include at least one different parameter; and / or The first algorithm and the second algorithm are different.

10. A communication method, characterized in that, include: Send a first request, the first request being used to request inventory of one or more environmental IoT devices; Receive a first temporary identifier of a first environmental IoT device, wherein the one or more environmental IoT devices include the first environmental IoT device; If the permanent identifier corresponding to the first temporary identifier includes at least two permanent identifiers, the second temporary identifier is determined based on the first permanent identifier among the at least two permanent identifiers. Send a first operation request to the first environmental IoT device. The first operation request includes the second temporary identifier. The first operation request is used to request the environmental IoT device corresponding to the second temporary identifier to perform a first operation. Based on the response information of the first operation request, the first permanent identifier is determined to be the permanent identifier of the first environmental IoT device.

11. The method as described in claim 10, characterized in that, The step of determining the first permanent identifier as the permanent identifier of the first environmental IoT device based on the response information of the first operation request includes: Upon receiving the response information of the first operation request, the first permanent identifier is determined to be the permanent identifier of the first environmental IoT device.

12. The method as described in claim 10 or 11, characterized in that, The first temporary identifier is determined by a first algorithm based on the permanent identifier of the first environmental IoT device and the first temporary identifier input parameters; the second temporary identifier is determined by a third algorithm based on the first permanent identifier and the second temporary identifier input parameters. Wherein, the first temporary identifier input parameter is different from the second temporary identifier input parameter; and / or, The first algorithm is different from the third algorithm.

13. The method as described in claim 12, characterized in that, The first operation request also includes the second temporary identifier input parameter and / or the indication information of the third algorithm.

14. The method according to any one of claims 10-13, characterized in that, The method further includes: The third temporary identifier is determined based on the second permanent identifier among the at least two permanent identifiers; Send a second operation request to the first environmental IoT device. The second operation request includes the third temporary identifier. The third operation request is used to request the environmental IoT device corresponding to the third temporary identifier to perform the first operation. Based on the response information of the second operation request, it is determined that the second permanent identifier is not the permanent identifier of the first environmental IoT device.

15. The method as described in claim 14, characterized in that, The step of determining, based on the response information of the second operation request, that the second permanent identifier is not the permanent identifier of the first environmental IoT device includes: If no response is received to the second operation request, it is determined that the second permanent identifier is not the permanent identifier of the first environmental IoT device.

16. The method as described in claim 14 or 15, characterized in that, The first temporary identifier is determined by a first algorithm based on the permanent identifier of the first environmental IoT device and the first temporary identifier input parameters; the third temporary identifier is determined by a fourth algorithm based on the second permanent identifier and the third temporary identifier input parameters. Wherein, the first temporary identifier input parameter is different from the third temporary identifier input parameter; and / or, The first algorithm is different from the fourth algorithm.

17. The method as described in claim 16, characterized in that, The second operation request also includes the third temporary identifier input parameter and / or the indication information of the fourth algorithm.

18. The method according to any one of claims 10-17, characterized in that, The first operation is an inventory operation.

19. A communication device, characterized in that, Includes units or modules for performing the method as described in any one of claims 1-18.

20. A communication device, characterized in that, Includes a processor for executing computer programs or instructions to implement the method as described in any one of claims 1-18.

21. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions, and when the computer program or instructions are executed by a communication device, the method as described in any one of claims 1-18 is implemented.

22. A computer program product, characterized in that, When the computer program product is executed by a computer, the computer performs the method as described in any one of claims 1-18.

Images