Communication method and device

Abstract

The present application relates to a communication method and a device. The method comprises: sending a paging message, wherein the paging message carries a freshness value and group identification information; receiving a paging response carrying the freshness value; calculating a temporary identifier of an AIoT device on the basis of the freshness value; and when the temporary identifier is the same as a first identifier of the AIoT device, determining that the AIoT device in a group is successfully paged.

Description

Communication methods and devices Technical Field

[0001] This application relates to the field of communications, and more specifically, to a communication method and apparatus. Background Technology

[0002] In related technologies, Ambient Powered IoT (AIoT) devices interact with AIoT functional entities through their corresponding readers or readers / writers. In this scenario, AIoT functional entities typically page AIoT devices using the AIoT device's identifier. To avoid the AIoT device's identifier being exposed over the air interface for extended periods, a temporary identifier for the AIoT device is used for paging. The paging message carries parameters for generating or updating the temporary identifier, along with the temporary identifier itself. The AIoT device calculates the temporary identifier and compares it with the received temporary identifier to determine whether to page itself. However, this approach presents two problems: firstly, the increased content carried in the paging message leads to higher overhead; secondly, the computational demands on the AIoT device are too high due to the need to calculate the temporary identifier. Summary of the Invention

[0003] This application provides a communication method and device.

[0004] This application provides a communication method executed by a read / write device, including:

[0005] Send a paging message, wherein the paging message carries a freshness value and group identification information;

[0006] Receive a paging response carrying the freshness value;

[0007] Calculate a temporary identifier for the AIoT device based on the freshness value;

[0008] When the temporary identifier is the same as the first identifier of the AIoT device, it is determined that paging the AIoT device in the group was successful.

[0009] This application provides a communication method performed by an AIoT functional entity, including:

[0010] Send a first request message, wherein the first request message carries a freshness value, group identification information, and a first identifier of the AIoT device;

[0011] Receive a first response corresponding to the first request message, wherein the first response is used to indicate that the AIoT device in the group has been successfully paged.

[0012] This application provides a communication method performed by an AIoT functional entity, including:

[0013] Send a first request message, wherein the first request message carries a freshness value and group identification information;

[0014] Receive a first response corresponding to the first request message, wherein the first response carries the freshness value;

[0015] Calculate a temporary identifier for the AIoT device based on the freshness value;

[0016] When the temporary identifier of the AIoT device is the same as the first identifier of the AIoT device, it is determined that paging the AIoT device in the group was successful.

[0017] This application provides a communication method executed by a read / write device, including:

[0018] Receive a first request message, wherein the first request message carries a freshness value and group identification information;

[0019] Send a paging message, wherein the paging message carries the freshness value and the group identification information;

[0020] Receive a paging response carrying the freshness value;

[0021] Send a first response corresponding to the first request message, wherein the first response carries the freshness value.

[0022] This application provides a communication method executed by an AIoT device, including:

[0023] Receive a paging message, wherein the paging message carries a freshness value and group identification information;

[0024] Send a paging response carrying the freshness value, wherein the freshness value is used to determine whether the AIoT device in the group was successfully paged.

[0025] This application provides a read / write device, including:

[0026] The first communication unit is configured to send a paging message, wherein the paging message carries a freshness value and group identification information; and to receive a paging response carrying the freshness value.

[0027] The first processing unit is used to calculate a temporary identifier for the AIoT device based on the freshness value; when the temporary identifier is the same as the first identifier of the AIoT device, it is determined that paging the AIoT device in the group was successful.

[0028] This application provides an AIoT functional entity, including:

[0029] The second communication unit is configured to send a first request message, wherein the first request message carries a freshness value, group identification information, and a first identifier of the AIoT device; and to receive a first response corresponding to the first request message, wherein the first response is configured to indicate that the AIoT device in the group has been successfully paged.

[0030] This application provides an AIoT functional entity, including:

[0031] The second communication unit is configured to send a first request message, wherein the first request message carries a freshness value and group identification information; and to receive a first response corresponding to the first request message, wherein the first response carries the freshness value.

[0032] The second processing unit is used to calculate a temporary identifier for the AIoT device based on the freshness value; when the temporary identifier of the AIoT device is the same as the first identifier of the AIoT device, it is determined that paging the AIoT device in the group was successful.

[0033] This application provides a read / write device, including:

[0034] A first communication unit is configured to receive a first request message, wherein the first request message carries a freshness value and group identification information; send a paging message, wherein the paging message carries the freshness value and the group identification information; receive a paging response carrying the freshness value; and send a first response corresponding to the first request message, wherein the first response carries the freshness value.

[0035] This application provides an AIoT device, including:

[0036] The third communication unit is used to receive a paging message, wherein the paging message carries a freshness value and group identification information; and to send a paging response carrying the freshness value, wherein the freshness value is used to determine whether the AIoT device in the group has been successfully paged.

[0037] This application provides a read / write device, including a transceiver, a processor, and a memory. The memory stores a computer program, the transceiver communicates with other devices, and the processor calls and runs the computer program stored in the memory to enable the read / write device to perform the methods described above.

[0038] This application provides an AIoT functional entity, including a transceiver, a processor, and a memory. The memory stores a computer program, the transceiver communicates with other devices, and the processor calls and runs the computer program stored in the memory to enable the AIoT functional entity to perform the methods described above.

[0039] This application provides an AIoT device, including a transceiver, a processor, and a memory. The memory stores a computer program, the transceiver communicates with other devices, and the processor calls and runs the computer program stored in the memory to enable the AIoT device to perform the methods described above.

[0040] This application provides a chip for implementing the above method.

[0041] Specifically, the chip includes a processor for retrieving and running a computer program from memory, causing a device equipped with the chip to perform the methods described above.

[0042] This application provides a computer-readable storage medium for storing a computer program, which, when run by a device, causes the device to perform the above-described method.

[0043] This application provides a computer program product, including computer program instructions that cause a computer to perform the above-described method.

[0044] By adopting the above scheme, the paging message sent by the reader / writer can carry a fresh value and group identification information to achieve paging of AIoT devices. The reader / writer calculates the temporary identifier of the AIoT device based on the fresh value carried in the paging response. By comparing the calculated temporary identifier with the AIoT device's primary identifier, it can determine whether the AIoT device has been successfully paged. Thus, in group scenarios, paging of AIoT devices can be achieved without carrying the temporary identifier of the AIoT device, reducing the length of the paging message and making the protocol simpler. Furthermore, the AIoT device does not need to perform calculations based on the fresh value to obtain its own temporary identifier to determine whether it is being paged. Instead, the reader / writer calculates the temporary identifier of the AIoT device based on the fresh value to determine whether a particular AIoT device has been successfully paged, thereby reducing the computational resource requirements of the AIoT device.

[0045] Furthermore, after the AIoT functional entity identifies a successfully paged AIoT device, it sends a command request to the AIoT device to write a temporary identifier. This enables the allocation or updating of temporary identifiers for individual devices after group paging. This reduces the length of paging messages and the computational resource requirements of AIoT devices, while also allowing temporary identifiers to be written on the AIoT device side.

[0046] By adopting the above scheme, the request message sent by the AIoT functional entity carries a fresh value and group identification information to achieve paging of AIoT devices. The AIoT functional entity calculates a temporary identifier for the AIoT device based on the fresh value carried in the response. By comparing the calculated temporary identifier with the AIoT device's primary identifier, it can determine whether the AIoT device has been successfully paged. Thus, in group scenarios, paging of AIoT devices can be achieved without carrying the temporary identifier of the AIoT device, reducing the length of the paging message and making the protocol simpler. Furthermore, the AIoT device does not need to perform calculations based on the fresh value to obtain its own temporary identifier to determine whether it is being paged. Instead, the AIoT functional entity calculates the temporary identifier of the AIoT device based on the fresh value to determine whether a page has been successfully paged, thereby reducing the computational resource requirements of the AIoT device. Attached Figure Description

[0047] Figure 1 is a schematic diagram of an application scenario according to an embodiment of this application.

[0048] Figure 2 is a schematic flowchart of a communication method according to an embodiment of this application.

[0049] Figure 3 is a flowchart illustrating a communication method according to an embodiment of this application.

[0050] Figure 4 is another flowchart illustrating a communication method according to an embodiment of this application.

[0051] Figure 5 is a schematic flowchart of a communication method according to another embodiment of this application.

[0052] Figure 6 is another flowchart illustrating a communication method according to yet another embodiment of this application.

[0053] Figure 7 is a schematic block diagram of a read / write device according to an embodiment of the present application.

[0054] Figure 8 is a schematic block diagram of an AIoT functional entity according to an embodiment of this application.

[0055] Figure 9 is a schematic block diagram of an AIoT device according to an embodiment of this application.

[0056] Figure 10 is a schematic block diagram of a communication device according to an embodiment of this application.

[0057] Figure 11 is a schematic block diagram of a chip according to an embodiment of this application. Detailed Implementation

[0058] The technical solutions of this application embodiment can be applied to various communication systems, such as NR, NR evolution, WLAN, WiFi, 6G, or other communication systems.

[0059] This application describes various embodiments in conjunction with network devices and terminals. A terminal is a device with data collection capabilities, which can be mobile or fixed, and may also be referred to as a mobile station, user unit, etc. A terminal can be a station in a WLAN, or a smart terminal, wireless modem, laptop, tablet, etc. In this application's embodiments, the terminal can be a VR / AR terminal, industrial control terminal, autonomous driving terminal, telemedicine terminal, smart grid terminal, transportation safety terminal, smart city terminal, or smart home wireless terminal, etc. By way of example and not limitation, in this application's embodiments, the terminal can also be a wearable device.

[0060] In this embodiment, the network device can be a device for communicating with a terminal. The network device can be an access point in a WLAN, an evolved base station in LTE, a relay station, a network device (gNB) in a vehicle-mounted device, wearable device, or NR network, or a network device in a future PLMN network, or a network device in a non-terrestrial network, etc. As an example and not a limitation, in this embodiment, the network device can have mobility characteristics; for example, the network device can be a mobile device.

[0061] In this embodiment, the network device may include at least one of the following: a 6G system architecture 6G Radio Access Network (RAN) and a 6G Core Network Function (CN NF). Under the 6G system architecture, independent distributed NAS termination can be supported between user equipment (UE) and its corresponding 6G network function. That is, each function within a 6G user equipment can directly transmit signals with the appropriate network function (NF) without going through a single termination point. Therefore, the 6G Radio Access Network (RAN) and the 6G Core Network Function (CN NF) can communicate directly with each other.

[0062] To facilitate understanding of the technical solutions of the embodiments of this application, the relevant technologies of the embodiments of this application are described below. The following relevant technologies are optional solutions and can be combined with the technical solutions of the embodiments of this application in any way, and they all fall within the protection scope of the embodiments of this application.

[0063] Figure 1 exemplarily illustrates a communication system 100. The communication system includes network devices 110 and terminals 90. In one possible implementation, the communication system 100 may include multiple network devices 110, and each network device 110 may include at least one terminal 90 within its coverage area; this embodiment does not limit this. In another possible implementation, the communication system 100 may also include other network entities such as mobility management entities and access and mobility management functions; this embodiment does not limit this. The communication system may also include multiple core networks for communicating with access network devices. Access network devices may be base stations of LTE, LTE-A, or NR systems, or 6G radio access networks (RANs). Taking the communication system shown in Figure 1 as an example, the communication devices may include network devices and terminals with communication functions. The communication devices may also include other devices in the communication system, such as network controllers, mobility management entities, and other network entities; this embodiment does not limit this.

[0064] Figure 2 is a schematic flowchart of a communication method according to an embodiment of this application. In Figure 2, the communication method is described from the perspective of the interaction between the AIoT device, the read / write device, and the AIoT function entity. As shown in Figure 2, the communication method may include the following steps:

[0065] S210 is executed on the AIoT functional entity side to send a first request message, wherein the first request message carries a freshness value, group identification information, and a first identifier of the AIoT device.

[0066] The read / write device executes S220: sending a paging message, wherein the paging message carries a freshness value and group identification information;

[0067] On the AIoT device side, S230 is executed to receive a paging message, wherein the paging message carries a freshness value and group identification information;

[0068] S240 is executed on the AIoT device side, sending a paging response carrying the freshness value, wherein the freshness value is used to determine whether the AIoT device in the group has been successfully paged.

[0069] The read / write device executes S250: receiving a paging response carrying the freshness value;

[0070] The read / write device executes S260, calculating a temporary identifier for the AIoT device based on the freshness value;

[0071] The read / write device executes S270, and when the temporary identifier of the AIoT device is the same as the first identifier of the AIoT device, it determines that paging the AIoT device in the group was successful.

[0072] S280 is executed on the AIoT functional entity side, receiving a first response corresponding to the first request message, wherein the first response is used to indicate that the AIoT device in the group has been successfully paged.

[0073] AIoT functional entities can also be referred to as AIoT NF (Network Function) or AIoT MF (Management Function), etc.

[0074] Reading and writing devices may include terminals and / or access network devices.

[0075] In some possible implementations, referring to Figure 3, the communication method by which the read / write device determines whether paging of the AIoT device is successful in the group paging process is described:

[0076] Step 301: AF sends a service request to the AIoT functional entity. This service request may be forwarded through NEF, which is not limited here.

[0077] The business request can be an inventory request message from an Application Function (AF). The business request can carry at least one of the following: group identification information, information of each AIoT device in the group (such as a permanent identifier), number of devices, business type indication, and mass sending (or mass sending indication).

[0078] The group identification information includes at least one of the following corresponding to the group: bitmask, filtering information, etc.

[0079] The purpose of the bit mask is to page or identify a group of AIoT devices. The specific composition of the bit mask is not limited in this embodiment. For example, the bit mask may include multiple bits, some of which are composed of the same bits in the identifier of the AIoT devices in the group, and the remaining bits in the bit mask may be set to zero.

[0080] The filtering information can be relevant conditions used to page a group of AIoT devices. For example, the filtering information can include conditions for paged a group of AIoT devices consisting of at least one of the following: a specified operator, a specified geographical area, or a specified service type (such as inventory service, wake-up service, etc.).

[0081] The business type indicator can be used to indicate any one of the following: inventory only, command only, inventory and command.

[0082] This is merely an illustrative example and does not limit or exhaustively list the content that the business request issued by AF may carry.

[0083] Step 302: The AIoT functional entity generates a fresh value, and the AIoT functional entity calculates a temporary identifier for each AIoT device in the group based on the fresh value.

[0084] The freshness value can be a random number, such as NONCE. This random number is generated by the AIoT functional entity. This embodiment does not limit the specific way the AIoT functional entity generates the random number.

[0085] Alternatively, the fresh value can be a count value. An AIoT functional entity can generate a fresh value by using the value of its own maintained counter as the fresh value.

[0086] In this embodiment, the freshness value is taken as an example for subsequent explanation.

[0087] Taking any AIoT device in the group as an example, the processing of the AIoT functional entity may include: calculating the first identifier of the AIoT device based on the freshness value and at least one of the following: the permanent identifier of the AIoT device, the previous temporary identifier of the AIoT device, the group identification information, and business-related information.

[0088] The first identifier of the AIoT device refers to the temporary identifier of the AIoT device calculated by the AIoT functional entity. In this embodiment, in order to distinguish between the temporary identifier of the AIoT device calculated by the AIoT functional entity and the temporary identifier of the AIoT device calculated by the subsequent reading and writing device, the temporary identifier of the AIoT device calculated by the AIoT functional entity is referred to as the first identifier of the AIoT device, which will not be explained again below.

[0089] Optionally, the AIoT functional entity calculates the first identifier of the AIoT device based on the freshness value and at least one identifier of the AIoT device. The at least one identifier of the AIoT device includes at least one of the following: the permanent identifier of the AIoT device, and the previous temporary identifier of the AIoT device.

[0090] The previous temporary ID of an AIoT device can refer to the temporary ID used during the last pager of the AIoT device. Specifically, the previous temporary ID can be the initial temporary ID or the last updated temporary ID. If the previous temporary ID is the initial temporary ID, it can be pre-configured on the AIoT functional entity side or can be obtained by the AIoT functional entity from other network entities, which can include at least one of ADM, AF, and AAA servers. If the previous temporary ID is the last updated temporary ID, it can be saved on the AIoT functional entity side when the temporary ID was last updated. This is only an illustrative example and does not limit or exhaustively list the specific ways in which the AIoT functional entity obtains the previous temporary ID of the AIoT device.

[0091] For example, the first identifier of an AIoT device is calculated based on the freshness value and the permanent identifier of the AIoT device using a preset algorithm.

[0092] The preset algorithm may include at least one of the following: hash function, encryption algorithm, integrity algorithm, KDF (Key Derivation Function), XOR calculation, direct connection calculation, HMAC (Hash-based Message Authentication Code), etc. These are all illustrative examples, and this embodiment does not limit or exhaustively list all possible preset algorithms.

[0093] For example, the first identifier of an AIoT device can be represented as F (freshness value, the permanent identifier of the AIoT device), where F() represents the preset algorithm.

[0094] For another example, the first identifier of the AIoT device is calculated based on the freshness value and the previous temporary identifier of the AIoT device using a preset algorithm. For instance, the first identifier of the AIoT device is represented as F(freshness value, previous temporary identifier of the AIoT device).

[0095] For another example, the first identifier of the AIoT device is calculated based on a preset algorithm using the freshness value, the permanent identifier of the AIoT device, and the previous temporary identifier. For instance, the first identifier of the AIoT device is represented as F(freshness value, previous temporary identifier of the AIoT device, permanent identifier of the AIoT device).

[0096] For example, the AIoT functional entity can first determine whether the reading and writing device has served a group. If the reading and writing device has served a group, the previous temporary identifier and / or permanent identifier can be used when calculating the first identifier of the AIoT device. If the reading and writing device has not served the group, the permanent identifier is preferably used when calculating the first identifier of the AIoT device.

[0097] Optionally, the AIoT functional entity calculates the first identifier of the AIoT device based on freshness value, at least one identifier of the AIoT device, and at least one of the following: group identification information, business-related information.

[0098] The business-related information includes a business correlation ID and / or a transaction ID.

[0099] The service association indicator corresponds to the service of the AF. The service association indicator can be generated by the AIoT functional entity. This application embodiment does not limit the specific way the AIoT F generates the service association indicator corresponding to the service of the AF. As long as the AIoT functional entity can generate different service association indicators for different services of the AF, it is within the protection scope of this embodiment. This service association indicator can also be referred to as a service association indicator; this is not limited or exhaustive.

[0100] A transaction indicator can correspond to a business association indicator. Optionally, the transaction indicator may be generated by the read / write device based on the business association indicator; if the transaction indicator is generated by the read / write device, the AIoT functional entity may not need to use the transaction indicator when calculating the first identifier of the AIoT device.

[0101] For example, the first identifier of an AIoT device can be represented as F(nonce, Permanent ID / Previous Temp ID, BITMASK / transaction ID / Correlation ID).

[0102] For example, the first identifier of the AIoT device is calculated based on the freshness value, at least one identifier of the AIoT device, and group identification information using a preset algorithm.

[0103] For example, the first identifier of an AIoT device can be represented as F(fresh value, permanent identifier of the AIoT device (and / or previous temporary identifier), bit mask).

[0104] For example, the first identifier of an AIoT device can be represented as F(fresh value, permanent identifier of the AIoT device (and / or the previous temporary identifier), filtering information).

[0105] For example, the first identifier of an AIoT device is represented as F(fresh value, permanent identifier of the AIoT device (and / or previous temporary identifier), bitmask, filtering information).

[0106] For another example, the first identifier of the AIoT device is calculated based on the freshness value, at least one temporary identifier of the AIoT device, and business-related information using a preset algorithm.

[0107] For example, the first identifier of an AIoT device can be represented as F(fresh value, permanent identifier of the AIoT device (and / or the previous temporary identifier), business association indicator).

[0108] For another example, the first identifier of the AIoT device is calculated based on the freshness value, at least one temporary identifier of the AIoT device, business-related information, and group identification information using a preset algorithm.

[0109] For example, the first identifier of an AIoT device can be represented as F(fresh value, permanent identifier of the AIoT device (and / or the previous temporary identifier), bitmask, business association indicator).

[0110] For example, the first identifier of an AIoT device can be represented as F(fresh value, permanent identifier of the AIoT device (and / or the previous temporary identifier), filtering information, business association indicator).

[0111] The above is merely an illustrative example. In actual processing, as long as the first identifier of the AIoT device can be obtained based on the freshness value, at least one identifier of the AIoT device, and combined with group identification information and / or business-related information, it is within the protection scope of this example. Not all possible combinations are exhaustively listed here.

[0112] It should be noted that in actual processing, the key shared between the AIoT device and the network side may or may not be used in the process of calculating the first identifier of the AIoT device, depending on the actual situation. The network side may include at least one of the following: AIoT functional entity, AF, ADM (Ambient IoT Data Management), and AAA (Authentication, Authorization and Accounting) server. If the key shared between the AIoT device and the network side is not stored on the AIoT functional entity side, it can be obtained by the AIoT functional entity from other network entities (such as at least one of AF, ADM, and AAA servers). This embodiment does not limit the specific way in which the AIoT functional entity obtains the key shared between the AIoT device and the network side.

[0113] If the first identifier of the AIoT device is calculated using a key shared between the AIoT device and the network side, this key can be added to the above example. This key can be used as an input key for calculating the first identifier of the AIoT device, or as an input parameter for calculating the first identifier of the AIoT device; there are no restrictions here.

[0114] The above example illustrates how the AIoT functional entity calculates the first identifier of any AIoT device. In actual processing, a group includes multiple AIoT devices, such as other AIoT devices in the group. The AIoT functional entity will calculate the first identifier corresponding to other AIoT devices in the same way. Since the calculation method for the first identifier of each AIoT device is the same as the calculation method for the first identifier of the AIoT devices mentioned above, it will not be described in detail.

[0115] Step 303: The AIoT functional entity sends a first request message. Specifically, the AIoT functional entity sends a first request message to the read / write device, wherein the first request message carries the freshness value, the group identification information, and the first identifier of the AIoT device; the first request message also carries service-related information. Correspondingly, the read / write device receives the first request message, wherein the first request message carries the freshness value, the group identification information, the first identifier of the AIoT device, and service-related information.

[0116] Optionally, the first request message carries a permanent identifier of the AIoT device. Whether the first request message carries a permanent identifier may be specified by the relevant protocol; or determined by the AIoT functional entity based on local policies; or the permanent identifier may be carried in the first request message when calculating the first identifier of the AIoT device using the permanent identifier.

[0117] In this embodiment, the first request message can be an inventory request issued by an AIoT functional entity.

[0118] The content carried in the first request message above is mainly an illustrative example using any one AIoT device included in the group. In actual processing, the group includes multiple AIoT devices. Therefore, the content that the first request message can carry may be: the freshness value, the first identifiers of the multiple AIoT devices, the group identification information, and business-related information. Optionally, the first request message may carry permanent identifiers of the multiple AIoT devices.

[0119] In some preferred examples, the service-related information sent by the AIoT functional entity to the read / write device may only include the service association indicator. This is because the AIoT functional entity can obtain the service association indicator based on the AF service, therefore the service-related information must at least include the service association indicator. The transaction indicator, on the other hand, can be generated by the read / write device based on the service association indicator; therefore, the service-related information sent by the AIoT functional entity may not include the transaction indicator. It should be noted that this is only a preferred example; in actual processing, if the AIoT functional entity can generate a transaction indicator, the service-related information may also include the transaction indicator. This is not intended to limit all possible scenarios.

[0120] Step 304: Read and write the content of the first request message and the ID of the AIoT functional entity stored in the device.

[0121] For example, the reading and writing device may store the content of the first request message and the ID of the AIoT functional entity by: extracting the fresh value, the group identification information, the first identifier of multiple AIoT devices, and business-related information from the first request message, and associating or binding the content of the first request message and the ID of the AIoT functional entity and saving them.

[0122] In one scenario, if the business-related information only includes a business association indicator, the reading / writing device extracts the fresh value, the group identification information, the first identifier of multiple AIoT devices, and the business association indicator from the first request message, and associates or binds the content of the first request message with the ID of the AIoT functional entity and saves it.

[0123] In one scenario, if the business-related information only includes a business association indicator, the read / write device extracts the fresh value, the group identification information, the first identifiers of multiple AIoT devices, and the business association indicator from the first request message. The read / write device can further generate a transaction indicator. Then, the fresh value, the group identification information, the first identifiers of multiple AIoT devices, the business association indicator, the transaction indicator, and the ID of the AIoT functional entity are associated or bound and saved.

[0124] In one scenario, the business-related information includes a business association indicator and a transaction indicator. The read / write device extracts the fresh value, the group identification information, the first identifier of multiple AIoT devices, the business association indicator, and the transaction indicator from the first request message. Then, it associates or binds the content of the first request message with the ID of the AIoT functional entity and saves it.

[0125] Optionally, if the first request message also carries the permanent identifiers of multiple AIoT devices, the read / write device will also associate or bind the permanent identifier of each of the multiple AIoT devices with the IDs of the various possible contents and AIoT functional entities mentioned above, and save them.

[0126] Optionally, the reader / writer can also associate and save the underlying identifier of each AIoT device in the group with the first identifier and / or permanent identifier corresponding to each AIoT device. The underlying identifier of each AIoT device can be obtained in advance by the reader / writer, and there is no limitation here.

[0127] Step 305: The read / write device sends a paging message. Specifically, the read / write device sends a paging message to each AIoT device in the group, carrying a freshness value and group identification information (such as a bitmask). This paging message can be used for inventory checks.

[0128] In step 306, after receiving the paging message, the AIoT device sends a paging response, carrying a fresh value. This fresh value can be used by the reading and writing device to calculate the temporary identifier of the AIoT device to determine whether paging of AIoT devices in the group has been successful.

[0129] After receiving a paging message, the AIoT device confirms that the paging range includes AIoT devices based on the group identification information carried in the paging message, such as a bit mask, and reads the fresh value in the paging message; the AIoT device returns a paging response carrying the fresh value.

[0130] Optionally, the paging response also carries the underlying identifier of the AIoT device. This underlying identifier may be written into the AIoT device at the factory; for example, the underlying identifier may include the EPC (Electronic Product Code).

[0131] Optionally, the paging response also carries group identification information.

[0132] Step 307: The reading / writing device receives a paging response carrying the freshness value and calculates a temporary identifier for the AIoT device based on the freshness value.

[0133] Specifically, the read / write device receives a paging response; extracts the fresh value carried in the paging response; and, if it confirms that the fresh value carried in the paging response is the same as the fresh value contained in the first request message stored by the read / write device, calculates a temporary identifier for the AIoT device based on the fresh value carried in the AIoT device's paging response. The AIoT device returns a fresh value (NONCE in this embodiment), and the read / write device determines that this fresh value is the same as the fresh value in the first request message. This prevents the fresh value or the underlying identifier from being tampered with, ensuring information security and resistance to attacks.

[0134] The calculation of the temporary identifier of the AIoT device based on the freshness value includes: calculating the temporary identifier of the AIoT device based on the freshness value and at least one of the following: the permanent identifier of the AIoT device, the previous temporary identifier of the AIoT device, the group identification information, and business-related information.

[0135] Here, freshness refers to the freshness value carried in the paging response of an AIoT device.

[0136] The permanent identifier of an AIoT device can be read and stored from the first request message.

[0137] The previous temporary identifier of an AIoT device can be stored locally on the reader / writer. The specific method by which the reader / writer obtains the previous temporary identifier of the AIoT device is not specified here.

[0138] Group identification information and business-related information can both be read and stored from the first request message.

[0139] The specific processing method for calculating the temporary identifier of the AIoT device and the combination method of various possible parameters used in calculating the AIoT device should be the same as the relevant description of the AIoT functional entity calculating the first identifier of the AIoT device in the previous embodiment. In this embodiment, in order to distinguish the results obtained by the calculation processing performed by different entities, the result calculated by the reading and writing device side is called the temporary identifier of the AIoT device, and the temporary identifier corresponding to the AIoT device calculated by the AIoT functional entity is called the first identifier of the AIoT device. Therefore, it will not be described again.

[0140] Step 308: When the temporary identifier of the AIoT device is the same as the first identifier of the AIoT device, the reading and writing device determines that paging the AIoT device in the group is successful.

[0141] Optionally, the paging response also carries the underlying identifier of the AIoT device; the method further includes: finding the first identifier of the AIoT device based on the underlying identifier of the AIoT device.

[0142] In other words, the reader extracts the underlying identifier of the AIoT device from the paging response, and then searches for the first identifier of the AIoT device stored locally based on the underlying identifier. Next, the reader compares the temporary identifier of the AIoT device, calculated by the reader based on the fresh value returned by the AIoT device, with the first identifier of the AIoT device. If they match, it determines that the AIoT devices within the range of the group identification information have been successfully paged. Additionally, if the temporary identifier of the AIoT device differs from the first identifier of the AIoT device, it determines that paging the AIoT device in the group has failed.

[0143] Steps 306 to 308 are exemplary descriptions using any one AIoT device in the group as an example. The processing of each AIoT device in the group should be the same as the processing of any one AIoT device, so they will not be described in detail.

[0144] Optionally, after completing step 308, the reading and writing device further includes: determining whether all AIoT devices included in the range of group identification information (such as bit mask) have been paged (or have been successfully paged). If not, steps 305 to 308 can be executed again. If it is determined that all AIoT devices included in the range of group identification information (such as bit mask) have been paged (or have been successfully paged), then step 309 is executed.

[0145] For example, the reader / writer can determine whether all AIoT devices within the range of the group identification information have been paged by: checking if the number of currently paged AIoT devices is less than the number of devices corresponding to the group identification information; if less, then it is determined that none of the AIoT devices within the range of the group identification information have been paged; if the number is the same, then it is determined that all AIoT devices within the range of the group identification information have been paged. The number of devices corresponding to the group identification information can be pre-configured in the reader / writer or obtained by the reader / writer through other methods; this is not limited here.

[0146] For example, the reader / writer can determine whether all AIoT devices within the scope of the group identification information have been paged by: The reader / writer uses the group device list corresponding to the group identification information to determine whether all AIoT devices within the scope of the group identification information have been paged. The group device list corresponding to the group identification information may include the underlying identifiers of all devices in the group, etc., which is not limited here; the group device list may be pre-configured in the reader / writer or obtained by the reader / writer through other methods, which is not limited here.

[0147] Step 309: The reading and writing device locates the AIoT functional entity.

[0148] Specifically, the read / write device finds the ID of the AIoT functional entity based on the content stored in step 304. For example, the read / write device finds the AIoT functional entity based on at least one of the bitmask, freshness value (such as NONCE), business-related information (such as business association indicator and / or transaction indicator) stored in step 304, and the identifier of the AIoT functional entity.

[0149] Step 310: The read / write device sends a first response corresponding to the first request message, wherein the first response is used to indicate that the AIoT device in the group has been successfully paged.

[0150] Specifically, the read / write device returns a first response to the AIoT functional entity. Correspondingly, the AIoT functional entity receives a first response corresponding to the first request message. The first response carries at least one of the following: a temporary identifier of the AIoT device, the group identification information, and the service-related information.

[0151] In this embodiment, the first response can be an inventory count response.

[0152] Optionally, the first response may carry at least a temporary identifier of the AIoT device. Optionally, the first response may carry the temporary identifier of the AIoT device and the group identification information. Optionally, the first response may carry the temporary identifier of the AIoT device and the service-related information. Optionally, the first response may carry the temporary identifier of the AIoT device, the group identification information, and the service-related information.

[0153] After receiving the first response, the AIoT functional entity can record that the AIoT device corresponding to the temporary identifier was successfully paged.

[0154] The above explanation uses any single AIoT device as an example. In actual processing, the read / write device can execute steps 309 and 310 after successfully paging all AIoT devices in the group. These can be further explained in the following scenarios:

[0155] In one scenario, the first response can be directed to all AIoT devices in the group. The first response may carry temporary identifiers for all AIoT devices in the group, and optionally, group identification information and / or service-related information. Upon receiving the first response, the AIoT functional entity can record the temporary identifiers of all AIoT devices in the group to indicate that each AIoT device in the group has been successfully paged.

[0156] It should be understood that the read / write device can pre-configure the number of repeated paging attempts. After reaching the paging attempt limit, the read / write device can execute steps 309 to 310 regardless of whether there are still unpaging AIoT devices in the group. If there are still unpaging AIoT devices, the temporary identifier carried in the first response sent by the read / write device can be the temporary identifier of the successfully paging AIoT device. The number of paging attempts can be configured according to actual conditions and is not limited here.

[0157] In one scenario, there can be multiple first responses, meaning there is a corresponding first response for each AIoT device in the group.

[0158] The first response corresponding to any AIoT device carries a temporary identifier for the AIoT device; optionally, it carries group identification information and / or the service-related information. Accordingly, after receiving this first response, the AIoT functional entity can record that the AIoT device corresponding to the temporary identifier has been successfully paged.

[0159] It should be understood that the read / write device can pre-configure the number of repeated paging attempts. After reaching the paging attempt limit, the read / write device can execute steps 309 to 310 regardless of whether there are still unpaging AIoT devices in the group. If there are still unpaging AIoT devices, the read / write device can send the first response corresponding to the successfully paging AIoT device.

[0160] Step 311: The AIoT functional entity returns an inventory response to the AF. The inventory response may carry other IDs of each AIoT Device in the group (or each AIoT Device that has been successfully paged). For example, the inventory response may carry at least one of the following: the permanent identifier of each AIoT Device in the group (or each AIoT Device that has been successfully paged), business-related information, etc. This is not limited or exhaustive.

[0161] The embodiment corresponding to Figure 3 above is an illustration of the inventory process.

[0162] In some alternative embodiments, the embodiment illustrated in FIG3 above can also be used for a command-only process. When the process illustrated in FIG3 is applied to a command-only process, the following differences may occur:

[0163] The business request in step 301 can be a command request message, which can carry a command. The specific type of the command is not limited in this embodiment. For example, it can include at least one of the following: read command, write command, activation command, deactivation command (temporary deactivation or permanent deactivation).

[0164] The first request message in steps 303 to 304 is a command request. In addition to the content of the above embodiments, the first request message may optionally carry a command.

[0165] The paging message in step 305 can be used to send a command. In addition to the content included in the above embodiments, the paging message may optionally carry a command.

[0166] The processing in step 306 remains unchanged. Optionally, the operation corresponding to the AIoT device executing the command can be added. Accordingly, the paging response may or may not carry the response information fed back by the AIoT device after executing the command.

[0167] In step 310, the first response can be a command response.

[0168] In step 311, the AIoT functional entity returns a command response to the AF.

[0169] When the process shown in Figure 3 is applied to a command-only process, the other processes are similar to the steps shown in Figure 3, except for the possible differences mentioned above, so they will not be repeated.

[0170] In another alternative embodiment, step 302, as shown in Figure 3, is replaced by: the AIoT functional entity sending an identification request message to other network entities. This identification request message carries at least one of the following: group identification information, a permanent identifier for each AIoT device, and the previous temporary identifier for each AIoT device. Other network entities receive the identification request message, generate a fresh value, calculate a temporary identifier for each AIoT device in the group based on the fresh value, and send the fresh value and the temporary identifier for each AIoT device to the AIoT functional entity. Other network entities may include at least one of ADM, AF, and AAA servers. The method by which other network entities calculate the temporary identifier is the same as the specific processing in step 302 and will not be repeated.

[0171] By adopting the above scheme, the paging message sent by the reader / writer can carry a fresh value and group identification information to achieve paging of AIoT devices. The reader / writer calculates the temporary identifier of the AIoT device based on the fresh value carried in the paging response. By comparing the calculated temporary identifier with the AIoT device's primary identifier, it can determine whether the AIoT device has been successfully paged. Thus, in group scenarios, paging of AIoT devices can be achieved without carrying the temporary identifier of the AIoT device, reducing the length of the paging message and making the protocol simpler. Furthermore, the AIoT device does not need to perform calculations based on the fresh value to obtain its own temporary identifier to determine whether it is being paged. Instead, the reader / writer calculates the temporary identifier of the AIoT device based on the fresh value to determine whether a particular AIoT device has been successfully paged, thereby reducing the computational resource requirements of the AIoT device.

[0172] In some possible implementations, referring to Figure 4, the process of the group paging procedure, in which the read / write device determines whether paging of the AIoT device is successful, and sends a command to the AIoT device individually based on the temporary identifier of the AIoT device during the command process, is described as follows:

[0173] Step 401: AF sends a service request to the AIoT functional entity. This service request may be forwarded through NEF, which is not limited here.

[0174] A service request can be an AF command request message. A service request can carry at least one of the following: group identification information, information of each AIoT device in the group (such as a permanent identifier), number of devices, service type indication, mass sending (or mass sending indication), etc.

[0175] The description of the group identification information is the same as that in the previous embodiments, and will not be repeated here.

[0176] The business type indicator can be used to indicate any one of the following: inventory only, command only, inventory and command. In this embodiment, the business type indicator can indicate both inventory and command.

[0177] This is merely an illustrative example and does not limit or exhaustively list the content that the business request issued by AF may carry.

[0178] Step 402: The AIoT functional entity generates a fresh value, and the AIoT functional entity calculates a temporary identifier for each AIoT device in the group based on the fresh value.

[0179] In this embodiment, the fresh value can be a counter value. The AIoT functional entity generates the fresh value by using the value of a counter it maintains as the fresh value. The update rule for this counter value can be preset in the AIoT functional entity. For example, it could be that the counter value is incremented by one every time the temporary identifier is updated, the counter value is incremented by one every time a request message is sent, or the counter value is reset to the initial value (e.g., 0) when it reaches the maximum value, etc. At least one of these rules is not limited or exhaustive here.

[0180] Alternatively, the freshness value can also be a random number. The relevant description of the random number is the same as that in the aforementioned embodiments, and will not be repeated here.

[0181] Since the group includes multiple AIoT devices, the AIoT functional entity can calculate the temporary identifier of each AIoT device in the group separately.

[0182] Here, taking any AIoT device in the group as an example, the processing of the AIoT functional entity may include: calculating the first identifier of the AIoT device based on the freshness value and at least one of the following: the permanent identifier of the AIoT device, the previous temporary identifier of the AIoT device, the group identification information, and business-related information.

[0183] The specific processing method and parameters used for calculating the first identifier of the AIoT device by the AIoT functional entity are the same as those in step 302 of the aforementioned embodiment, and will not be repeated here.

[0184] Step 403: The AIoT functional entity sends a first request message to the read / write device, wherein the first request message carries the freshness value (e.g., a count value), the group identification information, the first identifier of the AIoT device, and service-related information. Correspondingly, the read / write device receives the first request message, wherein the first request message carries the freshness value, the group identification information, the first identifier of the AIoT device, and service-related information. Optionally, the first request message carries a permanent identifier of the AIoT device.

[0185] The first request message can be an inventory request.

[0186] The descriptions regarding all possible contents carried by the first request message and the relevant information of each AIoT device in the group carried by the first request message are the same as those for step 303 in the aforementioned embodiments, and therefore will not be repeated.

[0187] Steps 404 to 408 are similar to steps 304 to 308, except that in this embodiment, the fresh value can be a count value, so it will not be described in detail. It should be noted that in this embodiment, the fresh value can also be replaced with a random number, which is not limited here.

[0188] Optionally, after completing step 408, the reading and writing device further includes: determining whether all AIoT devices included within the range of the group identification information have been paged (or successfully paged). If not, steps 405 to 408 can be executed again; if it is determined that all AIoT devices included within the range of the group identification information have been paged (or successfully paged), then step 409 is executed. The specific process by which the reading and writing device determines whether all AIoT devices included within the range of the group identification information have been paged is the same as in the aforementioned embodiments and will not be described in detail.

[0189] Optionally, after completing step 408 for any AIoT device in the group, the read / write device can directly execute step 409 for that successfully paged AIoT device. In other words, in this case, the read / write device does not need to wait for every AIoT device to be successfully paged; instead, it executes subsequent step 409 for any AIoT device that is successfully paged. The processing for each successfully paged AIoT device is the same and will not be described in detail.

[0190] Step 409 is the same as step 309, and will not be described in detail.

[0191] Step 410: The read / write device returns a first response to the AIoT functional entity, wherein the first response indicates that the AIoT device in the group has been successfully paged. Accordingly, the AIoT functional entity receives the first response. In this embodiment, the first response may be an inventory response.

[0192] The first response carries at least one of the following: the temporary identifier of the AIoT device, the group identification information, and the service-related information.

[0193] Optionally, if the reading / writing device determines that all AIoT devices within the range of the group identification information have been paged, the execution of steps 409 to 410 can take one of the following two forms:

[0194] In one scenario, the first response can be directed to all AIoT devices in the group. The first response may carry temporary identifiers for all AIoT devices in the group, and optionally, group identification information and / or service-related information. Upon receiving the first response, the AIoT functional entity can record the temporary identifiers of all AIoT devices in the group to indicate that each AIoT device in the group has been successfully paged.

[0195] That is, the read / write device determines that it has completed paging of all AIoT devices in the group and returns the first response to the AIoT functional entity. After the AIoT functional entity records that each AIoT device in the group has been successfully paging, it performs subsequent steps 411 for each AIoT device in the group.

[0196] It should be understood that the read / write device can pre-configure the number of repeated paging attempts. After reaching the paging attempt limit, the read / write device will execute steps 409 to 410 regardless of whether there are still unpaging AIoT devices in the group. If there are still unpaging AIoT devices, the temporary identifier carried in the first response issued by the read / write device can be the temporary identifier of the successfully paging AIoT device. After recording each successfully paging AIoT device, the AIoT functional entity will execute subsequent step 411 for each successfully paging AIoT device in the group.

[0197] In another scenario, there can be multiple first responses, meaning there is a corresponding first response for each AIoT device in the group.

[0198] The first response for each AIoT device carries a temporary identifier for that AIoT device; optionally, it may also carry group identification information and / or the service-related information. Accordingly, after receiving the first response from the AIoT device, the AIoT functional entity can record that the AIoT device corresponding to the temporary identifier has been successfully paged.

[0199] That is, the read / write device determines that it has completed paging of all AIoT devices in the group, and returns the first response corresponding to each AIoT device to the AIoT functional entity. After the AIoT functional entity records that each AIoT device in the group has been successfully paging, it performs subsequent steps 411 for each AIoT device in the group.

[0200] It should be understood that the read / write device can pre-configure the number of repeated paging attempts. After reaching the paging count, the read / write device will execute steps 409 to 410 regardless of whether there are still unpaged AIoT devices in the group. If there are still unpaged AIoT devices, the read / write device will issue the first response corresponding to the successfully paged AIoT device. After recording each successfully paged AIoT device, the AIoT functional entity will execute subsequent step 411 for each successfully paged AIoT device in the group.

[0201] Optionally, if the reading / writing device determines that an AIoT device within the scope of the group identification information has been paged, and executes steps 409 to 410, the first response can be the first response corresponding to the successfully paged AIoT device, carrying the temporary identifier of the AIoT device; optionally, it can carry group identification information and / or the service-related information. Accordingly, after receiving the first response corresponding to the AIoT device, the AIoT functional entity can record that the AIoT device corresponding to the temporary identifier has been successfully paged.

[0202] In other words, each time the read / write device confirms that a paging of an AIoT device has been completed, it returns a first response corresponding to the AIoT device to the AIoT functional entity. After the AIoT functional entity records that the AIoT device has been successfully paging, it can then perform the next step 411 for that AIoT device.

[0203] Since the AIoT functional entity executes the command process separately or individually for each AIoT device in the group, the following explanation of step 411 and its subsequent steps will be based on the example of the AIoT functional entity executing the next command process for any AIoT device that has been successfully paged. The subsequent command processes for each AIoT device will not be described in detail.

[0204] Step 411: The AIoT functional entity sends a second request message, wherein the second request message carries a temporary identifier of the AIoT device. The second request message is a command request message.

[0205] Specifically, the AIoT functional entity sends a second request message to the read / write device, carrying the temporary identifier of the AIoT device. Correspondingly, the read / write device receives the second request message, wherein the second request message carries the temporary identifier of the AIoT device.

[0206] The second request message may also carry a write command, which is used by the AIoT device to write a temporary identifier (or current temporary identifier).

[0207] Step 412, the read / write device sends a command request, wherein the command request carries at least a portion of the temporary identifier of the AIoT device.

[0208] Specifically, the read / write device sends a command request to the AIoT device corresponding to the temporary identifier. This command request carries all or part of the temporary identifier of the AIoT device. Correspondingly, the AIoT device receives the command request, wherein the command request carries at least a part of the temporary identifier of the AIoT device.

[0209] Here, if the read / write device sends out a portion of the temporary identifier of the AIoT device, it may use multiple bits specified in the temporary identifier of the AIoT device as part of the temporary identifier of the AIoT device. These multiple specified bits may be configured according to the actual situation or determined by the read / write device based on local policies, and there is no limitation here.

[0210] Optionally, the command request may also carry a write command, which is used by the AIoT device to write a temporary identifier (or current temporary identifier).

[0211] Step 413: The AIoT device receives the command request and saves the temporary identifier.

[0212] Optionally, after receiving a command request, if the command request carries the entirety of the temporary identifier, the AIoT device can directly save or write the temporary identifier.

[0213] Optionally, after receiving a command request, if the command request carries a temporary identifier, the AIoT device saves or writes the temporary identifier.

[0214] Optionally, after receiving a command request, if the command request carries a temporary identifier, the AIoT device can also combine this temporary identifier with the existing remaining bits to form the complete temporary identifier, and save or write this temporary identifier. The existing remaining bits of the AIoT device may be the same bits that are shared by default with the AIoT functional entity, or they may be bits determined using other methods; this is not limited here.

[0215] Step 414: The AIoT device sends a command response, wherein the command response carries at least a portion of the AIoT device's temporary identifier. Specifically, the AIoT device sends a command response to the read / write device. Correspondingly, the read / write device receives the command response, wherein the command response carries at least a portion of the AIoT device's temporary identifier.

[0216] Here, if the AIoT device has written or saved the entire temporary identifier locally, the command response carries the entire temporary identifier of the AIoT device; if the AIoT device has written or saved only part of the temporary identifier locally, the command response carries only part of the temporary identifier of the AIoT device.

[0217] Step 415, the read / write device sends a second response corresponding to the second request message, wherein the second response is used to determine that the AIoT device has completed writing the temporary identifier, and the second response carries at least a portion of the temporary identifier of the AIoT device.

[0218] Specifically, the read / write device sends a second response to the AIoT functional entity. Correspondingly, the AIoT functional entity receives a second response corresponding to the second request message, wherein the second response is used to determine that the AIoT device has completed writing the temporary identifier, and the second response carries at least a portion of the temporary identifier of the AIoT device.

[0219] The second response can be the same as the response received by the reader / writer from the AIoT device.

[0220] Step 416: The AIoT functional entity confirms that the AIoT device corresponding to the temporary identifier has completed the command's business and sends a command response to the AF. The command response sent by the AIoT functional entity to the AF may carry other IDs of the AIoT device, such as the permanent identifier of the AIoT device, etc., which are not limited or exhaustively listed here.

[0221] In some embodiments, after completing the aforementioned step 410, the AIoT functional entity can also send a group command message to the read / write device. For example, the group command message may carry the command that the group needs to execute, such as at least one of the following: read command, write command, activation command, temporary deactivation command, and permanent deactivation command; the group command message may also carry at least one of the following: group identification information, business-related information, etc., which are not limited here.

[0222] Accordingly, the read / write device sends the group command message to each AIoT device in the group. After receiving the response from each AIoT device in the group to the group command message, the read / write device sends the group command response to the AIoT functional entity. After confirming that each AIoT device has completed the group command service, the AIoT functional entity can send a group command response to the AF, which may include other IDs of each AIoT device, group identification information, etc., which are not limited here.

[0223] In some alternative embodiments, in step 411 above, the second request message can be replaced with a new temporary identifier for the AIoT device. That is, the AIoT functional entity can update the temporary identifier of the AIoT device again before executing step 411, and include the new temporary identifier of the AIoT device in the second request message. The method by which the AIoT functional entity generates the new temporary identifier of the AIoT device is similar to the method by which the first identifier of the AIoT device is generated, and will not be described in detail here.

[0224] In this embodiment, the subsequent steps 412 to 416 are similar to those in the above embodiment, except that the temporary identifier is replaced with a new temporary identifier, so they will not be described again.

[0225] By adopting the above scheme, the paging message sent by the reader / writer can carry a fresh value and group identification information to achieve paging of AIoT devices. The reader / writer calculates a temporary identifier for the AIoT device based on the fresh value in response. By comparing the calculated temporary identifier with the AIoT device's primary identifier, it can determine whether the AIoT device has been successfully paged. Thus, in group scenarios, paging of AIoT devices can be achieved without carrying the temporary identifier of the AIoT device, reducing the length of the paging message and making the protocol simpler. Furthermore, the AIoT device does not need to perform calculations based on the fresh value to obtain its own temporary identifier to determine whether it is being paged. Instead, the reader / writer calculates the temporary identifier of the AIoT device based on the fresh value to determine whether a page has been successfully paged, thereby reducing the computational resource requirements of the AIoT device.

[0226] Furthermore, after the AIoT functional entity identifies a successfully paged AIoT device, it sends a command request to the AIoT device to write a temporary identifier. This enables the allocation or updating of temporary identifiers for individual devices after group paging. This reduces the length of paging messages and the computational resource requirements of AIoT devices, while also allowing temporary identifiers to be written on the AIoT device side.

[0227] Figure 5 is a schematic flowchart of a communication method according to an embodiment of this application. In Figure 5, the communication method is described from the perspective of the interaction between the AIoT device, the read / write device, and the AIoT functional entity. As shown in Figure 5, the communication method may include the following steps:

[0228] S501 is executed on the AIoT functional entity side to send a first request message, wherein the first request message carries a freshness value and group identification information.

[0229] The read / write device executes S502 to receive a first request message, wherein the first request message carries a freshness value and group identification information;

[0230] The read / write device executes S503 and sends a paging message, wherein the paging message carries the freshness value and the group identification information;

[0231] S504 is executed on the AIoT device side to receive a paging message, wherein the paging message carries a freshness value and group identification information;

[0232] S505 is executed on the AIoT device side, sending a paging response carrying the freshness value, wherein the freshness value is used to determine whether the AIoT device in the group has been successfully paged;

[0233] The read / write device executes S506: receiving a paging response carrying the freshness value;

[0234] The read / write device executes S507: sending a first response corresponding to the first request message, wherein the first response carries the freshness value;

[0235] S508 is executed on the AIoT functional entity side to receive a first response corresponding to the first request message, wherein the first response carries the freshness value;

[0236] S509 is executed on the AIoT functional entity side to calculate the temporary identifier of the AIoT device based on the freshness value.

[0237] S510 is executed on the AIoT functional entity side. When the temporary identifier of the AIoT device is the same as the first identifier of the AIoT device, it is determined that paging the AIoT device in the group was successful.

[0238] Referring to Figure 6, the communication method provided in this embodiment will be described by way of example:

[0239] Steps 601 to 602 are the same as steps 301 to 302 in the previous embodiments, and will not be described again.

[0240] Step 603: The AIoT functional entity sends a first request message. Specifically, the AIoT functional entity sends a first request message to the read / write device, wherein the first request message carries the freshness value and the group identification information. Correspondingly, the read / write device receives the first request message, wherein the first request message carries the freshness value and the group identification information. The first request message carries service-related information.

[0241] In this embodiment, the first request message can be an inventory request issued by an AIoT functional entity.

[0242] The business-related information includes business association indicators and / or transaction indicators.

[0243] In some preferred examples, the service-related information sent by the AIoT functional entity to the read / write device may only include the service association indicator. This is because the AIoT functional entity can obtain the service association indicator based on the AF service, therefore the service-related information must at least include the service association indicator. The transaction indicator, on the other hand, can be generated by the read / write device based on the service association indicator; therefore, the service-related information sent by the AIoT functional entity may not include the transaction indicator. It should be noted that this is only a preferred example; in actual processing, if the AIoT functional entity can generate a transaction indicator, the service-related information may also include the transaction indicator. This is not intended to limit all possible scenarios.

[0244] Step 604: Read and write devices store the content of the first request message and the ID of the AIoT functional entity.

[0245] For example, the reading and writing device can store the content of the first request message and the ID of the AIoT functional entity by: extracting the fresh value, the group identification information, and the business-related information from the first request message, and associating or binding the content of the first request message and the ID of the AIoT functional entity and saving them.

[0246] In one scenario, if the business-related information only includes a business association indicator, the reading / writing device extracts the fresh value, the group identification information, and the business association indicator from the first request message, and associates or binds the content of the first request message with the ID of the AIoT functional entity and saves it.

[0247] In one scenario, if the business-related information only includes a business association indicator, the read / write device extracts the fresh value, the group identification information, and the business association indicator from the first request message. The read / write device can further generate a transaction indicator. Then, the fresh value, the group identification information, the business association indicator, the transaction indicator, and the ID of the AIoT functional entity are associated or bound and saved.

[0248] In one scenario, if the business-related information includes a business association indicator and a transaction indicator, the read / write device extracts the fresh value, the group identification information, the business association indicator, and the transaction indicator from the first request message; then it associates or binds the content of the first request message with the ID of the AIoT functional entity and saves it.

[0249] Step 605: The read / write device sends a paging message. Specifically, the read / write device sends a paging message to each AIoT Device in the group, carrying a freshness value and group identification information (such as filtering information and / or a bitmask). This paging message can be used for inventory checks.

[0250] In step 606, after receiving the paging message, the AIoT device sends a paging response carrying a fresh value. This fresh value can be used by the AIoT functional entity to calculate a temporary identifier for the AIoT device to determine whether paging of AIoT devices in the group has been successful.

[0251] Specifically, after receiving a paging message, the AIoT device confirms that the paging scope includes AIoT devices based on the group identification information carried in the paging message, such as filtering information, and reads the fresh value in the paging message; the AIoT device returns a paging response carrying the fresh value.

[0252] Optionally, the paging response also carries the underlying identifier of the AIoT device. The description of this underlying identifier is the same as in the previous embodiments and will not be repeated here.

[0253] Optionally, the paging response also carries group identification information.

[0254] Upon receiving a paging response carrying the fresh value, the read / write device sends a first response carrying the fresh value. Specifically, the read / write device performs the following steps 607-608:

[0255] Step 607: The reading and writing device receives a paging response; extracts the fresh value carried by the paging response; and finds the AIoT functional entity if it is confirmed that the fresh value carried by the paging response is the same as the fresh value contained in the first request message stored by the reading and writing device.

[0256] The read / write device can locate the AIoT functional entity by finding its ID based on the content stored in step 604. For example, the read / write device can locate the AIoT functional entity based on at least one of the bitmask, freshness value (such as NONCE), business-related information (such as business association indicators and / or transaction indicators), and the identifier of the AIoT functional entity stored in step 604. In this way, the read / write device can determine that the freshness value is the same as the freshness value in the first request message, which can prevent the freshness value or the underlying identifier from being tampered with, ensuring information security and resistance to attacks.

[0257] Step 608: The read / write device sends a first response corresponding to the first request message. Specifically, the read / write device returns the first response to the AIoT functional entity. Correspondingly, the AIoT functional entity receives the first response. In this embodiment, the first response can be an inventory response.

[0258] The first response carries freshness.

[0259] Optionally, the paging response also carries the underlying identifier of the AIoT device; correspondingly, the first response also carries the underlying identifier of the AIoT device.

[0260] Optionally, the first response may also carry the group identification information and business-related information.

[0261] Step 609: The AIoT functional entity receives a first response corresponding to the first request message carrying the fresh value, and calculates a temporary identifier for the AIoT device based on the fresh value.

[0262] Specifically, the AIoT functional entity receives the first response; extracts the fresh value carried by the first response; and calculates the temporary identifier of the AIoT device based on the fresh value carried by the first response.

[0263] The step of calculating the temporary identifier of the AIoT device based on the freshness value includes: calculating the temporary identifier of the AIoT device based on the freshness value and at least one of the following: the permanent identifier of the AIoT device, the previous temporary identifier of the AIoT device, the group identification information, and business-related information.

[0264] Here, the fresh value used by the AIoT functional entity to calculate the temporary identifier of the AIoT device in this step is the fresh value carried in the first response.

[0265] The specific processing method for calculating the temporary identifier of the AIoT device and the combination of various possible parameters used in calculating the AIoT device should be the same as the relevant description of the AIoT functional entity calculating the first identifier of the AIoT device in the aforementioned embodiment. In this embodiment, in order to distinguish the results obtained by the calculation processing performed by the AIoT functional entity at different stages, the result calculated in step 609 is called the temporary identifier of the AIoT device, and the temporary identifier corresponding to the AIoT device calculated by the AIoT functional entity in step 602 is called the first identifier of the AIoT device. Therefore, the description will not be repeated.

[0266] Step 610: If the temporary identifier of the AIoT device is the same as the first identifier of the AIoT device, the AIoT functional entity determines that paging the AIoT device in the group was successful.

[0267] Optionally, the first response may also carry the underlying identifier of the AIoT device; the method further includes: searching for a first identifier of the AIoT device based on the underlying identifier of the AIoT device. The AIoT functional entity can, after generating the first identifier of the AIoT device, associate the first identifier of the AIoT device with the underlying identifier of the AIoT device and store it locally. Thus, upon receiving the first response, the first identifier of the AIoT device can be found based on the underlying identifier of the AIoT device carried in it.

[0268] In other words, the AIoT functional entity extracts the underlying identifier of the AIoT device from the first response, and searches for the first identifier of the AIoT device corresponding to the AIoT device in its local storage based on the underlying identifier; it then compares the temporary identifier of the AIoT device calculated by itself based on the fresh value in the first response with the first identifier of the AIoT device; if they are the same, it determines that the AIoT devices included in the range of the group identification information have been successfully paged. Additionally, if the temporary identifier of the AIoT device is different from the first identifier of the AIoT device, it determines that pageing the AIoT device in the group has failed.

[0269] In this way, the AIoT functional entity calculates the temporary identifier of the AIoT device based on the fresh value carried in the first response, and then compares it with the first identifier of the AIoT device corresponding to the underlying identifier of the AIoT device to determine whether they are the same. This can prevent the fresh value or the underlying identifier from being tampered with, and ensure the security and resistance to attacks of information.

[0270] Steps 606 to 610 are exemplary descriptions using any one AIoT device in the group as an example. The processing of each AIoT device in the group should be the same as the processing of the AIoT device described above, so they will not be described in detail.

[0271] Optionally, after completing step 610, the processing of the AIoT functional entity may further include: determining whether all AIoT devices included in the range of the group identification information (such as filter information and / or bit mask) have been paged (or have been successfully paged). If not, steps 603 to 610 may be executed again. If it is determined that all AIoT devices included in the range corresponding to the group identification information have been paged (or have been successfully paged), then step 611 is executed.

[0272] For example, the AIoT functional entity determines whether all AIoT devices within the range of the group identification information have been paged. This can be done by: the AIoT functional entity checking if the number of currently paged AIoT devices is less than the number of devices corresponding to the group identification information; if less, then it determines that none of the AIoT devices within the range of the group identification information have been paged; if the number is the same, then it determines that all AIoT devices within the range of the group identification information have been paged. The number of devices corresponding to the group identification information can be pre-configured in the AIoT functional entity or obtained by the AIoT functional entity through other methods; this is not limited here.

[0273] For example, the AIoT functional entity can determine whether all AIoT devices within the scope of the group identification information have been paged by: the AIoT functional entity determining whether all AIoT devices within the scope of the group identification information have been paged based on the group device list corresponding to the group identification information. The group device list corresponding to the group identification information may include the underlying identifiers of all devices in the group, etc., which is not limited here; the group device list may be pre-configured in the AIoT functional entity, or it may be obtained by the AIoT functional entity through other methods, which is not limited here.

[0274] It should be understood that the AIoT functional entity can pre-configure the number of repeated paging attempts. After reaching the paging count, the AIoT functional entity can execute step 611 regardless of whether there are any unpaging AIoT devices in the group. The number of paging attempts on the AIoT functional entity side can be configured according to actual conditions and is not limited here.

[0275] Step 611: The AIoT functional entity returns an inventory response to the AF. The inventory response may carry other IDs of each AIoT device in the group (or each AIoT device that has been successfully paged). For example, the inventory response may carry at least one of the following: the permanent identifier of each AIoT device in the group (or each AIoT device that has been successfully paged), business-related information, etc. This is not limited or exhaustive.

[0276] In some embodiments, after completing step 611, steps 411 to 416 of the foregoing embodiments can also be performed, which will not be repeated here. Regarding the alternative embodiments of steps 411 to 416, the same applies as the foregoing descriptions, and will not be elaborated upon further.

[0277] In some embodiments, after completing the aforementioned step 611, the AIoT functional entity can also send a group command message to the read / write device. For example, the group command message may carry the command that the group needs to execute, such as at least one of the following: read command, write command, activation command, temporary deactivation command, and permanent deactivation command. The group command message may also carry at least one of the following: group identification information, business-related information, etc., which are not limited here.

[0278] Accordingly, the read / write device sends the group command message to each AIoT device in the group. After receiving the response from each AIoT device in the group to the group command message, the read / write device sends the group command response to the AIoT functional entity. After confirming that each AIoT device has completed the group command service, the AIoT functional entity can send a group command response to the AF, which may include other IDs of each AIoT device, group identification information, etc., which are not limited here.

[0279] In some alternative embodiments, the embodiment illustrated in FIG6 above can also be used for a command-only process. When the process illustrated in FIG6 is applied to a command-only process, the following differences may occur:

[0280] The service request in step 601 can be a command request message, which can carry a command. The specific type of the command is not limited in this embodiment.

[0281] The first request message in steps 603 to 604 is a command request. In addition to the content of the above embodiments, the first request message may optionally carry a command.

[0282] The paging message in step 605 can be used to send a command. In addition to the content included in the above embodiments, the paging message may optionally carry a command.

[0283] The processing in step 606 remains unchanged. Optionally, the operation corresponding to the AIoT device executing the command can be added. Accordingly, the paging response may or may not carry the response information fed back by the AIoT device after executing the command.

[0284] In step 608, the first response can be a command response.

[0285] In step 611, the AIoT functional entity returns a command response to the AF.

[0286] When the process shown in Figure 6 is applied to a command-only process, the remaining processes are similar to the steps shown in Figure 6, except for the possible differences mentioned above, so they will not be repeated.

[0287] By adopting the above scheme, a fresh value and group identification information can be included in the request message sent by the AIoT functional entity to achieve paging of AIoT devices. The AIoT functional entity calculates a temporary identifier for the AIoT device based on the fresh value carried in the response. By comparing the calculated temporary identifier with the AIoT device's primary identifier, it can determine whether the AIoT device has been successfully paged. Thus, in group scenarios, paging of AIoT devices can be achieved without carrying the temporary identifier of the AIoT device, reducing the length of the paging message and making the protocol simpler. Furthermore, the AIoT device does not need to perform calculations based on the fresh value to obtain its own temporary identifier in order to determine whether it is being paged. Instead, the AIoT functional entity calculates the temporary identifier of the AIoT device based on the fresh value to determine whether a page has been successfully paged, thereby reducing the computational resource requirements of the AIoT device.

[0288] Figure 7 is a schematic diagram of the composition structure of a read / write device according to an embodiment of this application, including:

[0289] The first communication unit 701 is used to send a paging message, wherein the paging message carries a freshness value and group identification information; and to receive a paging response carrying the freshness value.

[0290] The first processing unit 702 is used to calculate a temporary identifier for the AIoT device based on the freshness value; when the temporary identifier is the same as the first identifier of the AIoT device, it is determined that paging the AIoT device in the group was successful.

[0291] The first processing unit is configured to calculate a temporary identifier for the AIoT device based on the freshness value and at least one of the following: the permanent identifier of the AIoT device, the previous temporary identifier of the AIoT device, the group identification information, and business-related information.

[0292] The first communication unit is configured to receive a paging response carrying the freshness value and the underlying identifier of the AIoT device;

[0293] The first processing unit is used to look up the first identifier based on the underlying identifier.

[0294] The first communication unit is configured to receive a first request message, wherein the first request message carries the freshness value, the group identification information, the first identifier of the AIoT device, and business-related information.

[0295] The first request message also carries a permanent identifier of the AIoT device.

[0296] The first communication unit is configured to send a first response corresponding to the first request message, wherein the first response is configured to indicate that the AIoT device in the group has been successfully paged.

[0297] The first response carries at least one of the following: the temporary identifier of the AIoT device, the group identification information, and the service-related information.

[0298] The business-related information includes business association indicators and / or transaction indicators.

[0299] The first communication unit is configured to send a command request, wherein the command request carries at least a portion of the temporary identifier.

[0300] The first communication unit is configured to receive a command response, wherein the command response carries at least a portion of the temporary identifier.

[0301] The first communication unit is configured to receive a second request message, wherein the second request message carries the temporary identifier.

[0302] The first communication unit is configured to send a second response corresponding to the second request message, wherein the second response is configured to determine that the AIoT device has completed writing the temporary identifier, and the second response carries at least a portion of the temporary identifier.

[0303] Figure 8 is a schematic diagram of the composition structure of an AIoT functional entity according to an embodiment of this application, including:

[0304] The second communication unit 801 is configured to send a first request message, wherein the first request message carries a freshness value, group identification information, and a first identifier of the AIoT device; and to receive a first response corresponding to the first request message, wherein the first response is configured to indicate that the AIoT device in the group has been successfully paged.

[0305] As shown in Figure 8, it also includes:

[0306] The second processing unit 802 is used to calculate the first identifier of the AIoT device based on the freshness value and at least one of the following: the permanent identifier of the AIoT device, the previous temporary identifier of the AIoT device, the group identification information, and the business-related information.

[0307] The first request message also carries business-related information.

[0308] The first request message also carries a permanent identifier of the AIoT device.

[0309] The first response carries at least one of the following: a temporary identifier of the AIoT device, the group identification information, and business-related information.

[0310] The business-related information includes business association indicators and / or transaction indicators.

[0311] The second communication unit is used to send a second request message, wherein the second request message carries a temporary identifier of the AIoT device.

[0312] The second communication unit is configured to receive a second response corresponding to the second request message, wherein the second response is configured to determine that the AIoT device has completed writing the temporary identifier, and the second response carries at least a portion of the temporary identifier.

[0313] In one implementation, the AIoT functional entity includes:

[0314] The second communication unit is configured to send a first request message, wherein the first request message carries a freshness value and group identification information; and to receive a first response corresponding to the first request message, wherein the first response carries the freshness value.

[0315] The second processing unit is used to calculate a temporary identifier for the AIoT device based on the freshness value; when the temporary identifier of the AIoT device is the same as the first identifier of the AIoT device, it is determined that paging the AIoT device in the group was successful.

[0316] The second processing unit is configured to calculate a temporary identifier for the AIoT device based on the freshness value and at least one of the following: the permanent identifier of the AIoT device, the previous temporary identifier of the AIoT device, the group identification information, and business-related information.

[0317] The second processing unit is configured to calculate a first identifier of the AIoT device based on the freshness value and at least one of the following: the permanent identifier of the AIoT device, the previous temporary identifier of the AIoT device, the group identification information, and the service-related information.

[0318] The first response also carries the underlying identifier of the AIoT device; the second processing unit is used to find the first identifier of the AIoT device based on the underlying identifier of the AIoT device.

[0319] The first request message carries business-related information.

[0320] The first response also carries the group identification information and business-related information.

[0321] The business-related information includes business association indicators and / or transaction indicators.

[0322] The second communication unit is used to send a second request message, wherein the second request message carries a temporary identifier of the AIoT device.

[0323] The second communication unit is configured to receive a second response corresponding to the second request message, wherein the second response is configured to determine that the AIoT device has completed writing the temporary identifier, and the second response carries at least a portion of the temporary identifier.

[0324] In one embodiment, the read / write device includes:

[0325] A first communication unit is configured to receive a first request message, wherein the first request message carries a freshness value and group identification information; send a paging message, wherein the paging message carries the freshness value and the group identification information; receive a paging response carrying the freshness value; and send a first response corresponding to the first request message, wherein the first response carries the freshness value.

[0326] The first request message carries business-related information.

[0327] The paging response also carries the underlying identifier of the AIoT device; the first response also carries the underlying identifier of the AIoT device.

[0328] The first response also carries the group identification information and business-related information.

[0329] The business-related information includes business association indicators and / or transaction indicators.

[0330] The first communication unit is configured to send a command request, wherein the command request carries at least a portion of the temporary identifier of the AIoT device.

[0331] The first communication unit is configured to receive a command response, wherein the command response carries at least a portion of the temporary identifier.

[0332] The first communication unit is configured to receive a second request message, wherein the second request message carries the temporary identifier.

[0333] The first communication unit is configured to send a second response corresponding to the second request message, wherein the second response is configured to determine that the AIoT device has completed writing the temporary identifier, and the second response carries at least a portion of the temporary identifier.

[0334] Figure 9 is a schematic diagram of the composition structure of an AIoT device according to an embodiment of this application, including:

[0335] The third communication unit 901 is used to receive a paging message, wherein the paging message carries a freshness value and group identification information; and to send a paging response carrying the freshness value, wherein the freshness value is used to determine whether the AIoT device in the group has been successfully paged.

[0336] The paging response also carries the underlying identifier of the AIoT device.

[0337] The third communication unit is configured to receive a command request, wherein the command request carries at least a portion of the temporary identifier of the AIoT device.

[0338] The third communication unit is configured to send a command response, wherein the command response carries at least a portion of the temporary identifier of the AIoT device.

[0339] The device in this application embodiment can realize the corresponding functions of the various devices in the foregoing communication method embodiments. The processes, functions, implementation methods, and beneficial effects of each module (sub-module, unit, or component, etc.) in this device can be found in the corresponding descriptions in the above method embodiments, and will not be repeated here. It should be noted that the functions described for each module (sub-module, unit, or component, etc.) in the device of this application embodiment can be implemented by different modules (sub-modules, units, or components, etc.) or by the same module (sub-module, unit, or component, etc.).

[0340] It should be understood that the sequence number of each process in the various embodiments of this application does not imply the order of execution; the execution order of each process should be determined by its function and internal logic. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. The above descriptions are merely specific embodiments of this application, and the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0341] Figure 10 is a schematic structural diagram of a communication device 1000 according to an embodiment of this application. The communication device 1000 includes a processor 1010, which can call and run computer programs from a memory to enable the communication device 1000 to implement the methods in the embodiments of this application. In one possible implementation, the communication device 1000 may further include a memory 1020. The processor 1010 can call and run computer programs from the memory 1020 to enable the communication device 1000 to implement the methods in the embodiments of this application. The memory 1020 may be a separate device independent of the processor 1010, or it may be integrated into the processor 1010. In one possible implementation, the communication device 1000 may further include a transceiver 1030, which the processor 1010 can control to communicate with other devices. Specifically, it can send information or data to other devices, or receive information or data sent by other devices. The transceiver 1030 may include a transmitter and a receiver. The transceiver 1030 may further include antennas, and the number of antennas may be one or more.

[0342] In one possible implementation, the communication device 1000 may be an AIoT device, an AIoT functional entity, or a read / write device according to the embodiments of this application. The communication device 1000 may implement the corresponding processes implemented by the AIoT device, the AIoT functional entity, or the read / write device in the various methods of the embodiments of this application. For the sake of brevity, these will not be elaborated here.

[0343] Figure 11 is a schematic structural diagram of a chip 1100 according to an embodiment of this application. The chip 1100 includes a processor 1110, which can call and run computer programs from memory to implement the methods in the embodiments of this application. In one possible implementation, the chip 1100 may further include a memory 1120. The processor 1110 can call and run computer programs from the memory 1120 to implement the methods executed by an AIoT device, an AIoT functional entity, or a read / write device in the embodiments of this application. The memory 1120 may be a separate device independent of the processor 1110, or it may be integrated into the processor 1110. In one possible implementation, the chip 1100 may further include an input interface 1130. The processor 1110 can control the input interface 1130 to communicate with other devices or chips; specifically, it can acquire information or data sent by other devices or chips. In one possible implementation, the chip 1100 may further include an output interface 1140. The processor 1110 can control the output interface 1140 to communicate with other devices or chips, specifically, it can output information or data to other devices or chips.

[0344] In one possible implementation, the chip can be applied to the AIoT device, AIoT functional entity, or read / write device in the embodiments of this application, and the chip can implement the corresponding processes implemented by the AIoT device, AIoT functional entity, or read / write device in the various methods of the embodiments of this application. For simplicity, these will not be elaborated further here. It should be understood that the chip mentioned in the embodiments of this application can also be called a system-on-a-chip, system-on-a-chip, chip system, or system-on-chip, etc. The processor mentioned above can be a general-purpose processor, digital signal processor (DSP), field-programmable gate array (FPGA), application-specific integrated circuit (ASIC), or other programmable logic device, transistor logic device, discrete hardware component, etc. Among them, the general-purpose processor mentioned above can be a microprocessor or any conventional processor, etc. The memory mentioned above can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM). It should be understood that the above-described memory is exemplary but not limiting. For example, the memory in the embodiments of this application can also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DR RAM), etc. In other words, the memory in the embodiments of this application is intended to include, but is not limited to, these and any other suitable types of memory.

[0345] This application also provides a communication system. The communication system includes an AIoT device, an AIoT functional entity, and a read / write device. The AIoT device is used to implement the corresponding functions implemented by the AIoT device in the above-described method; the AIoT functional entity is used to implement the corresponding functions implemented by the AIoT functional entity in the above-described method; and the read / write device is used to implement the corresponding functions implemented by the read / write device in the above-described method.

[0346] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. This computer program product includes one or more computer instructions. When these computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives (SSDs)).

[0347] It should be understood that the sequence number of each process in the various embodiments of this application does not imply the order of execution; the execution order of each process should be determined by its function and internal logic. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. The above descriptions are merely specific embodiments of this application, and the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method executed by a read / write device, comprising: Send a paging message, wherein the paging message carries a freshness value and group identification information; Receive a paging response carrying the freshness value; Calculate a temporary identifier for the AIoT device based on the freshness value; When the temporary identifier is the same as the first identifier of the AIoT device, it is determined that paging the AIoT device in the group was successful.

2. The method according to claim 1, wherein, The calculation of the temporary identifier of the AIoT device based on the freshness value includes: The temporary identifier of the AIoT device is calculated based on the freshness value and at least one of the following: the permanent identifier of the AIoT device, the previous temporary identifier of the AIoT device, the group identification information, and the business-related information.

3. The method according to claim 1 or 2, wherein, Receiving a paging response carrying the freshness value includes: Receive a paging response carrying the freshness value and the underlying identifier of the AIoT device; Based on the underlying identifier, the first identifier is located.

4. The method according to any one of claims 1-3, further comprising: Receive a first request message, wherein the first request message carries the freshness value, the group identification information, the first identifier, and business-related information.

5. The method according to claim 4, wherein, The first request message also carries a permanent identifier of the AIoT device.

6. The method according to claim 4 or 5, further comprising: Send a first response corresponding to the first request message, wherein the first response is used to indicate that the AIoT device in the group has been successfully paged.

7. The method according to claim 6, wherein, The first response carries at least one of the following: the temporary identifier of the AIoT device, the group identification information, and the service-related information.

8. The method according to any one of claims 2, 4-7, wherein, The business-related information includes business association indicators and / or transaction indicators.

9. The method according to any one of claims 1-8, further comprising: Send a command request, wherein the command request carries at least a portion of the temporary identifier.

10. The method of claim 9, further comprising: Receive a command response, wherein the command response carries at least a portion of the temporary identifier.

11. The method of claim 10, further comprising: Receive a second request message, wherein the second request message carries the temporary identifier.

12. The method of claim 11, further comprising: Send a second response corresponding to the second request message, wherein the second response is used to determine that the AIoT device has completed writing the temporary identifier, and the second response carries at least a portion of the temporary identifier.

13. A communication method performed by an AIoT functional entity, comprising: Send a first request message, wherein the first request message carries a freshness value, group identification information, and a first identifier of the AIoT device; Receive a first response corresponding to the first request message, wherein the first response is used to indicate that the AIoT device in the group has been successfully paged.

14. The method of claim 13, further comprising: The first identifier is calculated based on the freshness value and at least one of the following: the permanent identifier of the AIoT device, the previous temporary identifier of the AIoT device, the group identification information, and the business-related information.

15. The method according to claim 13 or 14, wherein, The first request message also carries business-related information.

16. The method according to any one of claims 13-15, wherein, The first request message also carries a permanent identifier of the AIoT device.

17. The method according to any one of claims 13-16, wherein, The first response carries at least one of the following: a temporary identifier of the AIoT device, the group identification information, and business-related information.

18. The method according to any one of claims 14, 15, and 17, wherein, The business-related information includes business association indicators and / or transaction indicators.

19. The method according to any one of claims 13-18, further comprising: Send a second request message, wherein the second request message carries a temporary identifier of the AIoT device.

20. The method of claim 19, further comprising: Receive a second response corresponding to the second request message, wherein the second response is used to determine that the AIoT device has completed writing the temporary identifier, and the second response carries at least a portion of the temporary identifier.

21. A communication method performed by an AIoT functional entity, comprising: Send a first request message, wherein the first request message carries a freshness value and group identification information; Receive a first response corresponding to the first request message, wherein the first response carries the freshness value; Calculate a temporary identifier for the AIoT device based on the freshness value; When the temporary identifier of the AIoT device is the same as the first identifier of the AIoT device, it is determined that paging the AIoT device in the group was successful.

22. The method according to claim 21, wherein, The calculation of the temporary identifier of the AIoT device based on the freshness value includes: The temporary identifier of the AIoT device is calculated based on the freshness value and at least one of the following: the permanent identifier of the AIoT device, the previous temporary identifier of the AIoT device, the group identification information, and the business-related information.

23. The method according to claim 21 or 22, further comprising: The first identifier is calculated based on the freshness value and at least one of the following: the permanent identifier of the AIoT device, the previous temporary identifier of the AIoT device, the group identification information, and the business-related information.

24. The method according to any one of claims 21-23, wherein, The first response also carries the underlying identifier of the AIoT device; the method further includes: Based on the underlying identifier of the AIoT device, the first identifier is located.

25. The method according to any one of claims 21-24, wherein, The first request message carries business-related information.

26. The method according to any one of claims 21-25, wherein, The first response also carries the group identification information and business-related information.

27. The method according to any one of claims 22, 23, 25, and 26, wherein, The business-related information includes business association indicators and / or transaction indicators.

28. The method according to any one of claims 21-27, further comprising: Send a second request message, wherein the second request message carries a temporary identifier of the AIoT device.

29. The method of claim 28, further comprising: Receive a second response corresponding to the second request message, wherein the second response is used to determine that the AIoT device has completed writing the temporary identifier, and the second response carries at least a portion of the temporary identifier.

30. A communication method performed by a read / write device, comprising: Receive a first request message, wherein the first request message carries a freshness value and group identification information; Send a paging message, wherein the paging message carries the freshness value and the group identification information; Receive a paging response carrying the freshness value; Send a first response corresponding to the first request message, wherein the first response carries the freshness value.

31. The method according to claim 30, wherein, The first request message carries business-related information.

32. The method according to claim 30 or 31, wherein, The paging response also carries the underlying identifier of the AIoT device; the first response also carries the underlying identifier of the AIoT device.

33. The method according to any one of claims 30-32, wherein, The first response also carries the group identification information and business-related information.

34. The method according to claim 31 or 33, wherein, The business-related information includes business association indicators and / or transaction indicators.

35. The method according to any one of claims 30-34, further comprising: Send a command request, wherein the command request carries at least a portion of the temporary identifier of the AIoT device.

36. The method of claim 35, further comprising: Receive a command response, wherein the command response carries at least a portion of the temporary identifier.

37. The method of claim 36, further comprising: Receive a second request message, wherein the second request message carries the temporary identifier.

38. The method of claim 37, further comprising: Send a second response corresponding to the second request message, wherein the second response is used to determine that the AIoT device has completed writing the temporary identifier, and the second response carries at least a portion of the temporary identifier.

39. A communication method performed by an AIoT device, comprising: Receive a paging message, wherein the paging message carries a freshness value and group identification information; Send a paging response carrying the freshness value, wherein the freshness value is used to determine whether the AIoT device in the group was successfully paged.

40. The method according to claim 39, wherein, The paging response also carries the underlying identifier of the AIoT device.

41. The method according to claim 39 or 40, further comprising: A command request is received, wherein the command request carries at least a portion of the temporary identifier of the AIoT device.

42. The method of claim 41, further comprising: Send a command response, wherein the command response carries at least a portion of the temporary identifier of the AIoT device.

43. A read / write device, comprising: The first communication unit is configured to send a paging message, wherein the paging message carries a freshness value and group identification information; and to receive a paging response carrying the freshness value. The first processing unit is used to calculate a temporary identifier for the AIoT device based on the freshness value; when the temporary identifier is the same as the first identifier of the AIoT device, it is determined that paging the AIoT device in the group was successful.

44. An AIoT functional entity, comprising: The second communication unit is configured to send a first request message, wherein the first request message carries a freshness value, group identification information, and a first identifier of the AIoT device; and to receive a first response corresponding to the first request message, wherein the first response is configured to indicate that the AIoT device in the group has been successfully paged.

45. An AIoT functional entity, comprising: The second communication unit is configured to send a first request message, wherein the first request message carries a freshness value and group identification information; and to receive a first response corresponding to the first request message, wherein the first response carries the freshness value. The second processing unit is used to calculate a temporary identifier for the AIoT device based on the freshness value; when the temporary identifier of the AIoT device is the same as the first identifier of the AIoT device, it is determined that paging the AIoT device in the group was successful.

46. ​​A read / write device, comprising: A first communication unit is configured to receive a first request message, wherein the first request message carries a freshness value and group identification information; send a paging message, wherein the paging message carries the freshness value and the group identification information; receive a paging response carrying the freshness value; and send a first response corresponding to the first request message, wherein the first response carries the freshness value.

47. An AIoT device, comprising: The third communication unit is used to receive a paging message, wherein the paging message carries a freshness value and group identification information; and to send a paging response carrying the freshness value, wherein the freshness value is used to determine whether the AIoT device in the group has been successfully paged.

48. A read / write device, comprising: A transceiver, a processor, and a memory for storing a computer program, the transceiver for communicating with other devices, and the processor for calling and running the computer program stored in the memory to cause the read / write device to perform the method as claimed in any one of claims 1 to 12 or 30 to 38.

49. An AIoT functional entity, comprising: A transceiver, a processor, and a memory for storing a computer program, the transceiver for communicating with other devices, and the processor for calling and running the computer program stored in the memory to cause the AIoT functional entity to perform the method as claimed in any one of claims 13 to 20 or 21 to 29.

50. An AIoT device, comprising: A transceiver, a processor, and a memory for storing a computer program, the transceiver for communicating with other devices, and the processor for calling and running the computer program stored in the memory to cause the AIoT device to perform the method as described in any one of claims 39 to 42.

51. A chip, comprising: A processor for retrieving and running a computer program from memory, causing a device having the chip mounted to perform the method as described in any one of claims 1 to 12, or claims 13 to 20, 21 to 29, 30 to 38, or 39 to 42.

52. A computer-readable storage medium for storing a computer program that, when run by a device, causes the device to perform the method as described in any one of claims 1 to 12, or claims 13 to 20, 21 to 29, 30 to 38, or 39 to 42.

53. A computer program product comprising computer program instructions that cause a computer to perform the method as described in any one of claims 1 to 12, or claims 13 to 20, 21 to 29, 30 to 38, or 39 to 42.

54. A computer program that causes a computer to perform the method as described in any one of claims 1 to 12, or claims 13 to 20, 21 to 29, 30 to 38, or 39 to 42.

Images