Communication method, communication device, communication system, storage medium and program product

By utilizing ambient energy sources and optimizing communication processes in IoT devices, the problem of low communication efficiency under the limitations of traditional power supply methods is solved, enabling efficient information exchange and resource management.

WO2026232609A1PCT designated stage Publication Date: 2026-11-12BEIJING XIAOMI MOBILE SOFTWARE CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2025/094106
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2025-05-09
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

IoT devices are limited by environmental, cost, and energy-saving factors due to the traditional battery-powered method, which cannot meet the needs of large-scale deployment and has low communication efficiency.

Method used

By using environmental energy sources to power IoT devices and leveraging information interaction mechanisms in communication methods, including sending instruction messages to trigger random access or delete invalid information, the communication process of the devices can be optimized to improve efficiency.

Benefits of technology

It significantly reduced communication latency, improved the communication efficiency of IoT devices, freed up system resources, restored data transmission, and optimized communication processes.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2025094106_12112026_PF_FP_ABST
    Figure CN2025094106_12112026_PF_FP_ABST
Patent Text Reader

Abstract

The present disclosure relates to a communication method, a communication device, a communication system, a storage medium and a program product. The method comprises: a first device sending first information to a second device, wherein the first information indicates that the sending of second information to be sent to the second device has failed, and the first information is further used for triggering the second device to execute at least one of the following: executing random access, and deleting third information, the third information being a response to the second information; and / or the first device sending fourth information to a third device, wherein the fourth information is used for indicating that the sending of the second information has failed, and the fourth information comprises first identification information associated with the second device. By means of the solution of the present disclosure, the communication efficiency of an Internet-of-Things device is improved.
Need to check novelty before this filing date? Find Prior Art

Description

Communication methods, communication equipment, communication systems, storage media and software products Technical Field

[0001] This disclosure relates to the field of wireless communication, and more particularly to a communication method, communication device, communication system, storage medium, and program product. Background Technology

[0002] With the application of Internet of Things (IoT) technology in various industries, the large-scale deployment of IoT devices powered by traditional batteries is limited by factors such as environment, cost, energy conservation and environmental protection, and cannot meet the needs in some scenarios.

[0003] In light of this, an IoT technology supporting ambient energy is proposed. Ambient energy-enabled IoT devices can utilize energy sources present in the environment to power themselves, enabling communication and data transmission. Summary of the Invention

[0004] Improving the communication efficiency of IoT devices is a problem that needs to be solved.

[0005] According to a first aspect of the present disclosure, a communication method is provided, executed by a first device, the method comprising: sending first information to a second device, the first information being used to indicate that the transmission of second information failed, or, the first information being used to indicate that the reception of third information failed, or, the first information being used to indicate that the first device did not receive the third information, the first information further being used to trigger the second device to perform at least one of the following: performing random access; deleting the third information, the third information being a response to the second information.

[0006] According to a second aspect of the present disclosure, a communication method is provided, executed by a second device, the method comprising: receiving first information sent by a first device, the first information indicating that the transmission of second information failed, or, the first information indicating that the reception of third information failed, or, the first information indicating that the first device did not receive the third information; and, based on the first information, performing at least one of the following: performing random access; and deleting the third information, the third information being a response to the second information.

[0007] According to a third aspect of the present disclosure, a communication method is provided, performed by a third device, the method comprising: receiving fourth information sent by a first device, the fourth information being used to indicate that the second device failed to send second information, or, the fourth information being used to indicate that the third information failed to be received, or, the fourth information being used to indicate that the first device did not receive the third information, the fourth information including first identification information associated with the second device, the first identification information being used to identify the second device, and the third information being a response to the second information.

[0008] According to a fourth aspect of the present disclosure, a communication method is provided, the method comprising: a first device sending first information to a second device, the first information indicating that the second device failed to send second information, or, the first information indicating that the third information failed to be received, or, the first information indicating that the first device did not receive the third information, the first information further being used to trigger the second device to perform at least one of the following: performing random access; deleting the third information, the third information being a response to the second information; and / or, the first device sending fourth information to the third device, the fourth information indicating that the second information failed to be sent, or, the fourth information indicating that the third information failed to be received, or, the fourth information indicating that the first device did not receive the third information, the fourth information including first identification information associated with the second device, the first identification information being used to identify the second device.

[0009] According to a fifth aspect of the present disclosure, a communication device, such as a first device, is provided. The communication device includes a transceiver module configured to: send first information to a second device, wherein the first information indicates that the second device failed to send second information, or, the first information is used to indicate that the reception of third information failed, or, the first information is used to indicate that the first device did not receive the third information; the first information is further configured to trigger the second device to perform at least one of the following: perform random access; delete the third information, wherein the third information is a response to the second information.

[0010] According to a sixth aspect of the present disclosure, a communication device, such as a second device, is provided. The communication device includes: a transceiver module configured to receive first information sent by a first device, wherein the first information indicates that the second device failed to send second information, or, the first information is used to indicate that the reception of third information failed, or, the first information is used to indicate that the first device did not receive the third information; and a processing module configured to, based on the first information, perform at least one of the following: perform random access; delete the third information, wherein the third information is a response to the second information.

[0011] According to a seventh aspect of the present disclosure, a communication device, such as a third device, is provided. The communication device includes: a transceiver module configured to receive fourth information sent by a first device, the fourth information being used to indicate second information from a second device, or, the fourth information being used to indicate that the reception of third information failed, or, the fourth information being used to indicate that the first device did not receive the third information, the fourth information including first identification information associated with the second device, the first identification information being used to identify the second device, and the third information being a response to the second information.

[0012] According to an eighth aspect of the present disclosure, a communication system is provided. The communication system includes at least one of a first device, a second device, and a third device. The first device is configured to perform the communication method as described in the first aspect. The second device is configured to perform the communication method as described in the second aspect. The third device is configured to perform the communication method as described in the third aspect.

[0013] According to a ninth aspect of the present disclosure, a storage medium is provided. The storage medium stores instructions. When executed on a communication device, the instructions cause the communication device to perform the communication method as described in the first, second, or third aspect.

[0014] According to a tenth aspect of the present disclosure, a program product is provided. The program product includes at least one of a program and instructions. When the program or instructions are executed by a communication device, they implement the communication method as described in the first, second, or third aspect.

[0015] According to an eleventh aspect of the present disclosure, a computer program is provided. When the computer program is run on a computer, it causes the computer to perform the communication method as described in the first, second, or third aspect.

[0016] According to a twelfth aspect of this disclosure, a chip or chip system is provided. The chip or chip system includes processing circuitry. The processing circuitry is configured to perform the communication methods described in the first, second, or third aspects.

[0017] According to embodiments of this disclosure, the communication efficiency of Internet of Things (IoT) devices is improved.

[0018] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not constitute a limitation on the embodiments of this disclosure. Attached Figure Description

[0019] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments of the invention and, together with the description, serve to explain the principles of the embodiments of the invention.

[0020] Figure 1A is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.

[0021] Figure 1B is a schematic diagram illustrating wireless communication based on backscattering according to an embodiment of the present disclosure.

[0022] Figure 1C is a schematic diagram of an architecture of an A-IoT system according to an embodiment of the present disclosure.

[0023] Figure 1D is a schematic diagram of another architecture of an A-IoT system according to an embodiment of the present disclosure.

[0024] Figure 1E is a schematic diagram of another architecture of an A-IoT system according to an embodiment of the present disclosure.

[0025] Figure 1F is a schematic diagram of another architecture of an A-IoT system according to an embodiment of the present disclosure.

[0026] Figure 1G is a schematic diagram of a passive device according to an embodiment of the present disclosure.

[0027] Figure 1H is a schematic diagram illustrating the interaction between a reader and a device in a passive Internet of Things system according to an embodiment of the present disclosure.

[0028] Figure 1I is a schematic diagram illustrating a random access process for an Internet of Things (IoT) device according to an embodiment of the present disclosure.

[0029] Figure 2A is an exemplary interactive schematic diagram of a communication method according to an embodiment of the present disclosure.

[0030] Figure 2B is an exemplary interactive schematic diagram of a communication method according to an embodiment of the present disclosure.

[0031] Figure 2C is an exemplary interactive schematic diagram of a communication method according to an embodiment of the present disclosure.

[0032] Figures 2D to 2F are exemplary interactive schematic diagrams of a communication method according to embodiments of the present disclosure.

[0033] Figures 2G to 2H are exemplary interactive schematic diagrams of a communication method according to embodiments of the present disclosure.

[0034] Figure 3A is an interactive schematic diagram of a communication method provided according to an embodiment of the present disclosure.

[0035] Figure 3B is an interactive schematic diagram of a communication method provided according to an embodiment of the present disclosure.

[0036] Figure 4 is a schematic diagram of the structure of a communication device shown in an embodiment of this disclosure.

[0037] Figure 5A is a schematic diagram of the structure of a communication device shown in an embodiment of this disclosure.

[0038] Figure 5B is a schematic diagram of the chip structure shown in an embodiment of this disclosure. Detailed Implementation

[0039] This disclosure provides a communication method, communication device, communication system, storage medium, and program product.

[0040] In a first aspect, embodiments of this disclosure provide a communication method executed by a first device, the method comprising: sending first information to a second device, the first information indicating that the second device failed to send second information, or, the first information indicating that the third information failed to be received, or, the first information indicating that the first device did not receive the third information, the first information further being used to trigger the second device to perform at least one of the following: performing random access; deleting the third information, the third information being a response to the second information.

[0041] In the above embodiments, the first device sends first information to the second device to trigger the second device to perform random access and / or delete the third information if the second device fails to send the second information, or fails to receive the third information, or if the first device does not receive the third information. This avoids waiting time for the second device due to uncertainty about subsequent operations, significantly reducing communication latency and improving communication efficiency. Furthermore, the first information can trigger the second device to resynchronize with the first device, thereby resuming data transmission, and / or the first information can trigger the second device to delete invalid information, thereby releasing system resources, thus improving the communication efficiency of IoT devices.

[0042] In some embodiments of the first aspect, the method further includes: sending fourth information to a third device, the fourth information indicating that the second information failed to be sent or the third information failed to be received, the fourth information including first identification information associated with the second device, the first identification information being used to identify the second device, and the third information being a response to the second information.

[0043] In the above embodiments, the first device sends a fourth message to the third device to indicate that the second message failed to be sent, or that the third message failed to be received, or that the first device did not receive the third message. This allows the third device to determine the operation to be performed in this situation, thereby avoiding the waiting time caused by the third device's uncertainty about subsequent operations. This can significantly reduce communication latency and improve communication efficiency.

[0044] In some embodiments of the first aspect, the fourth information is also used to trigger the third device to delete the context information of the second device.

[0045] In the above embodiments, the first device sends a fourth message to the third device to trigger the third device to delete the context information of the second device if the second message fails to be sent, or if the third message fails to be received, or if the first device does not receive the third message, thereby releasing system resources and improving the communication efficiency of IoT devices.

[0046] In some embodiments in conjunction with the first aspect, the method further includes: receiving fifth information sent by a third device based on fourth information, the fifth information being used to indicate whether to continue communication with the second device, the first information being sent by the first device based on the fifth information.

[0047] In the above embodiments, the first device sends a fourth message to the third device to trigger the third device to decide whether to continue communicating with the second device if the second device fails to send the second message, thereby improving the communication efficiency of IoT devices.

[0048] In some embodiments in conjunction with the first aspect, the fifth information includes at least one of the following: second identification information for indicating at least one device, the at least one device including the second device; and identification type information for indicating the type of the second identification information.

[0049] In some embodiments in conjunction with the first aspect, the type of the second identification information includes one of the following: a first identification for indicating a device; a second identification for indicating multiple devices.

[0050] In some embodiments of the first aspect, the fifth information indicates continued communication with the second device, and the fifth information is used by the first device to determine whether to trigger the second device to perform contention-based random access, or the fifth information is used by the first device to determine whether to trigger the second device to perform non-contention-based random access.

[0051] In some embodiments of the first aspect, the identifier type information indicates that the second identifier information is a second identifier, and the first information is used to trigger the second device to perform contention-based random access; or, the identifier type information indicates that the second identifier information is a first identifier, and the first information is used to trigger the second device to perform non-contention-based random access.

[0052] In some embodiments of the first aspect, the fifth information indicates that communication with the second device will cease, and the fifth information is used by the first device to determine whether to trigger the second device to delete the third information.

[0053] In some embodiments in conjunction with the first aspect, the method further includes one of the following: deleting the context information of the second device; or saving the context information of the second device.

[0054] In some embodiments in conjunction with the first aspect, the context information of the second device includes at least one of the following: first identification information associated with the second device; second information; and third information.

[0055] In some embodiments of the first aspect, the first information includes one of the following: a first service identifier, which is different from the second service identifier associated with the second information; a negative response message; or an end identifier.

[0056] In some embodiments in conjunction with the first aspect, the first information includes at least one of the following: a device identifier of the second device; a first service identifier; and a second service identifier.

[0057] In some embodiments of the first aspect, the method further includes: sending a paging message to a second device, the paging message being sent by the first device after sending the first information; and receiving, based on the paging message, a device identifier of the second device sent by the second device via random access.

[0058] In some embodiments of the first aspect, the method further includes: sending identification information of the second device to a third device, the identification information of the second device being used by the third device to establish context information of the second device.

[0059] In some embodiments in conjunction with the first aspect, the method further includes: sending second information to the second device based on the device identifier of the second device.

[0060] In a second aspect, embodiments of this disclosure provide a communication method. This method is executed by a second device. The method includes: receiving first information sent by a first device, the first information indicating that the second device failed to send second information, or, the first information indicating that the second device failed to receive third information, or, the first information indicating that the first device did not receive third information; and, based on the first information, performing at least one of the following: performing random access; and deleting the third information, the third information being a response to the second information.

[0061] In the above embodiments, the second device performs random access and / or deletes the third information based on the first information sent by the first device, in the event that the second device fails to send the second information, or fails to receive the third information, or the first device does not receive the third information. This avoids waiting time for the second device due to uncertainty about subsequent operations, significantly reducing communication latency and improving communication efficiency. Furthermore, the first information can trigger the second device to resynchronize with the first device, thereby resuming data transmission, and / or the first information can trigger the second device to delete invalid information, thereby releasing system resources, thus improving the communication efficiency of IoT devices.

[0062] In some embodiments in conjunction with the second aspect, the first information includes one of the following: a first service identifier, which is different from the second service identifier associated with the second information; a negative response message; or an end identifier.

[0063] In some embodiments in conjunction with the second aspect, the first information includes at least one of the following: a device identifier of the second device; a first service identifier; and a second service identifier.

[0064] In some embodiments of the second aspect, the method further includes: receiving a paging message sent by a first device, wherein the second paging message is sent by the first device after sending the first information; and sending a device identifier of the second device to the first device via random access based on the paging message.

[0065] In some embodiments of the second aspect, the device identifier of the second device is used by the first device to trigger the third device to establish context information of the second device.

[0066] In some embodiments of the second aspect, the device identifier of the second device is used by the first device to send second information to the second device.

[0067] In a third aspect, embodiments of this disclosure provide a communication method. This method is executed by a third device. The method includes: receiving fourth information sent by a first device, the fourth information indicating that the second device failed to send second information, or, the fourth information indicating that the third information failed to be received, or, the fourth information indicating that the first device did not receive the third information, the fourth information including first identification information associated with the second device, the first identification information being used to identify the second device, and the third information being a response to the second information.

[0068] In the above embodiments, the fourth information sent by the first device to the third device can indicate that the second information failed to be sent, the third information failed to be received, or that the first device did not receive the third information, so that the third device can determine the operation to be performed in this case, thereby avoiding the waiting time caused by the third device being uncertain about subsequent operations, which can significantly reduce communication latency and improve communication efficiency.

[0069] In some embodiments in conjunction with the third aspect, the method further includes: deleting the context information of the second device based on the fourth information.

[0070] In some embodiments in conjunction with the third aspect, the context information of the second device includes at least one of the following: first identification information; second information; and third information.

[0071] In some embodiments of the third aspect, the method further includes: sending fifth information to the first device based on fourth information, the fifth information indicating whether to continue communication with the second device, the fifth information being used by the first device to send first information, the first information being used to trigger the second device to perform at least one of the following: performing random access; deleting the third information.

[0072] In some embodiments in conjunction with the third aspect, the fifth information includes at least one of the following: second identification information for indicating at least one device, the at least one device including the second device; and identification type information for indicating the type of the second identification information.

[0073] In some embodiments in conjunction with the third aspect, the type of the second identification information includes one of the following: a first identification for indicating a device; and a second identification for indicating multiple devices.

[0074] In some embodiments of the third aspect, the fifth information indicates continued communication with the second device, and the fifth information is used by the first device to determine whether to trigger the second device to perform contention-based random access or non-contention-based random access.

[0075] In some embodiments of the third aspect, the identifier type information indicates that the second identifier information is a second identifier, and the first information is used to trigger the second device to perform contention-based random access; or, the identifier type information indicates that the second identifier information is a first identifier, and the first information is used to trigger the second device to perform non-contention-based random access.

[0076] In some embodiments of the third aspect, the fifth information indicates that communication with the second device will cease, and the fifth information is used by the first device to determine whether to trigger the second device to delete the third information.

[0077] In some embodiments of the third aspect, the first information includes one of the following: a first service identifier, which is different from the second service identifier associated with the second information; a negative response message; or an end identifier.

[0078] In some embodiments in conjunction with the third aspect, the first information includes at least one of the following: a device identifier of the second device; a first service identifier; and a second service identifier.

[0079] In some embodiments of the third aspect, the method further includes: receiving identification information of a second device sent by a first device, the identification information of the second device being sent to the first device by the second device via random access; and establishing context information of the second device based on the identification information of the second device.

[0080] In a fourth aspect, embodiments of this disclosure provide a communication method executed by a communication system, the communication system including at least one of a first device, a second device, and a third device. The method includes: the first device sending first information to the second device, the first information indicating that the transmission of second information sent to the second device failed, or, the first information indicating that the reception of third information failed, or, the first information indicating that the first device did not receive the third information; the second device performing at least one of the following based on the first information: performing random access; deleting the third information, the third information being a response to the second information; and / or, the first device sending fourth information to the third device, the fourth information indicating that the transmission of the second information by the second device failed, or, the fourth information indicating that the reception of the third information failed, or, the fourth information indicating that the first device did not receive the third information, the fourth information including first identification information associated with the second device, the first identification information being used to identify the second device.

[0081] In some embodiments in conjunction with the fourth aspect, the method further includes: the third device deleting the context information of the second device based on the fourth information.

[0082] In some embodiments in conjunction with the fourth aspect, the method further includes: a third device sending fifth information to a first device based on the fourth information, the fifth information being used to indicate whether to continue communication with the second device, and the first information being sent by the first device based on the fifth information.

[0083] In some embodiments in conjunction with the fourth aspect, the fifth information includes at least one of the following: second identification information for indicating at least one device, the at least one device including the second device; and identification type information for indicating the type of the second identification information.

[0084] In some embodiments of the fourth aspect, the type of the second identification information includes one of the following: a first identification for indicating a device; and a second identification for indicating multiple devices.

[0085] In some embodiments of the fourth aspect, the fifth information indicates continued communication with the second device, and the fifth information is used by the first device to determine whether to trigger the second device to perform contention-based random access or non-contention-based random access.

[0086] In some embodiments of the fourth aspect, the identifier type information indicates that the second identifier information is a second identifier, and the first information is used to trigger the second device to perform contention-based random access; or, the identifier type information indicates that the second identifier information is a first identifier, and the first information is used to trigger the second device to perform non-contention-based random access.

[0087] In some embodiments of the fourth aspect, the fifth information indicates that communication with the second device will cease, and the fifth information is used by the first device to determine whether to trigger the second device to delete the third information.

[0088] In some embodiments of the fourth aspect, the method further includes one of the following: the first device deletes the context information of the second device; the first device saves the context information of the second device.

[0089] In some embodiments in conjunction with the fourth aspect, the second device context information includes at least one of the following: first identification information associated with the second device; second information; and third information.

[0090] In some embodiments of the fourth aspect, the first information includes one of the following: a first service identifier, which is different from the second service identifier associated with the second information; a negative response message; or an end identifier.

[0091] In some embodiments of the fourth aspect, the first information includes at least one of the following: a device identifier of the second device; a first service identifier; and a second service identifier.

[0092] In some embodiments of the fourth aspect, the method further includes: a first device sending a paging message to a second device, the second paging message being sent by the first device after sending the first information; and the second device sending its device identifier to the first device via random access based on the paging message.

[0093] In some embodiments of the fourth aspect, the method further includes: the first device sending identification information of the second device to the third device, the identification information of the second device being used by the third device to establish context information of the second device.

[0094] In some embodiments of the fourth aspect, the method further includes: the first device sending second information to the second device based on the device identifier of the second device.

[0095] In a fifth aspect, embodiments of this disclosure provide a communication device, such as a first device. The communication device includes: a transceiver module configured to send first information to a second device, the first information indicating that the transmission of second information failed, or, the first information indicating that the reception of third information failed, or, the first information indicating that the first device did not receive the third information; the first information further being configured to trigger the second device to perform at least one of the following: perform random access; delete the third information, the third information being a response to the second information.

[0096] In some embodiments of the fifth aspect, the transceiver module is further configured to send fourth information to a third device, the fourth information being used to indicate that the second device failed to send the second information, or that the third information failed to be received, or that the fourth information is used to indicate that the first device did not receive the third information, the fourth information including first identification information associated with the second device, the first identification information being used to identify the second device.

[0097] In some embodiments of the fifth aspect, the fourth information is also used to trigger the third device to delete the context information of the second device.

[0098] In some embodiments of the fifth aspect, the transceiver module is configured to receive fifth information sent by the third device based on the fourth information, the fifth information being used to indicate whether to continue communication with the second device, the first information being sent by the first device based on the fifth information.

[0099] In some embodiments of the fifth aspect, the fifth information includes at least one of the following: second identification information for indicating at least one device, the at least one device including the second device; and identification type information for indicating the type of the second identification information.

[0100] In some embodiments of the fifth aspect, the type of the second identification information includes one of the following: a first identification for indicating a device; a first identification for indicating multiple devices.

[0101] In some embodiments of the fifth aspect, the fifth information indicates continued communication with the second device, and the fifth information is used by the first device to determine whether to trigger the second device to perform contention-based random access or non-contention-based random access.

[0102] In some embodiments of the fifth aspect, the identifier type information indicates that the second identifier information is the first identifier, and the first information is used to trigger the second device to perform contention-based random access; or, the identifier type information indicates that the second identifier information is the second identifier, and the first information is used to trigger the second device to perform non-contention-based random access.

[0103] In some embodiments of the fifth aspect, the fifth information indicates that communication with the second device will cease, and the fifth information is used by the first device to determine whether to trigger the second device to delete the third information.

[0104] In some embodiments in conjunction with the fifth aspect, the communication device includes a processing module configured to perform one of the following: deleting context information of the second device; or saving the context information of the second device.

[0105] In some embodiments of the fifth aspect, the context information of the second device includes at least one of the following: first identification information associated with the second device; second information; and third information.

[0106] In some embodiments of the fifth aspect, the first information includes one of the following: a first service identifier, which is different from the second service identifier associated with the second information; a negative response message; or an end identifier.

[0107] In some embodiments of the fifth aspect, the first information includes at least one of the following: a device identifier of the second device; a first service identifier; and a second service identifier.

[0108] In some embodiments of the fifth aspect, the transceiver module is further configured to: send a paging message to a second device, the second paging message being sent by the first device after sending the first information; and receive the device identifier of the second device sent by the second device through random access.

[0109] In some embodiments of the fifth aspect, the transceiver module is further configured to send identification information of the second device to the third device, the identification information of the second device being used by the third device to establish context information of the second device.

[0110] In some embodiments of the fifth aspect, the transceiver module is further configured to send second information to the second device based on the device identifier of the second device.

[0111] In a sixth aspect, embodiments of this disclosure provide a communication device, such as a second device. The communication device includes: a transceiver module configured to receive first information sent by a first device, the first information indicating that the transmission of second information failed, or that the reception of third information failed, or that the first information indicates that the first device did not receive the third information; and a processing module configured to, based on the first information, perform at least one of the following: perform random access; delete the third information, the third information being a response to the second information.

[0112] In some embodiments of the sixth aspect, the first information includes one of the following: a first service identifier, which is different from the second service identifier associated with the second information; a negative response message; or an end identifier.

[0113] In some embodiments of the sixth aspect, the first information includes at least one of the following: a device identifier of the second device; a first service identifier; and a second service identifier.

[0114] In some embodiments of the sixth aspect, the transceiver module is configured to: receive a paging message sent by a first device, the paging message being sent by the first device after sending first information; and, based on the paging message, send the device identifier of a second device to the first device via random access.

[0115] In some embodiments of the sixth aspect, the device identifier of the second device is used by the first device to trigger the third device to establish context information for the second device.

[0116] In some embodiments of the sixth aspect, the device identifier of the second device is used by the first device to send second information to the second device.

[0117] In a seventh aspect, embodiments of this disclosure provide a communication device, such as a third device. The communication device includes: a transceiver module configured to receive fourth information sent by a first device, the fourth information being used to indicate that the second device failed to send second information, or, the fourth information being used to indicate that the third information failed to be received, or, the fourth information being used to indicate that the first device did not receive the third information, the fourth information including first identification information associated with the second device, the first identification information being used to identify the second device, and the third information being a response to the second information.

[0118] In some embodiments of the seventh aspect, the communication device further includes a processing module configured to delete the context information of the second device based on the fourth information.

[0119] In some embodiments of the seventh aspect, the context information of the second device includes at least one of the following: first identification information; second information; and third information.

[0120] In some embodiments of the seventh aspect, the transceiver module is further configured to: send fifth information to the first device based on the fourth information, the fifth information being used to indicate whether to continue communication with the second device, the fifth information being used by the first device to send first information, and the first information being used to trigger the second device to perform at least one of the following: perform random access; delete the third information.

[0121] In some embodiments of the seventh aspect, the fifth information includes at least one of the following: second identification information for indicating at least one device, the at least one device including the second device; and identification type information for indicating the type of the second identification information.

[0122] In some embodiments of the seventh aspect, the type of the second identification information includes one of the following: a first identification for indicating a device; and a second identification for indicating multiple devices.

[0123] In some embodiments of the seventh aspect, the fifth information indicates continued communication with the second device, and the fifth information is used by the first device to determine whether to trigger the second device to perform contention-based random access or non-contention-based random access.

[0124] In some embodiments of the seventh aspect, the identifier type information indicates that the second identifier information is the first identifier, and the first information is used to trigger the second device to perform contention-based random access; or, the identifier type information indicates that the second identifier information is the second identifier, and the first information is used to trigger the second device to perform non-contention-based random access.

[0125] In some embodiments of the seventh aspect, the fifth information indicates that communication with the second device will cease, and the fifth information is used by the first device to determine that the second device is triggering the deletion of the third information.

[0126] In some embodiments of the seventh aspect, the first information includes one of the following: a first service identifier, which is different from the second service identifier associated with the second information; a negative response message; or an end identifier.

[0127] In some embodiments of the seventh aspect, the first information includes at least one of the following: a device identifier of the second device; a first service identifier; and a second service identifier.

[0128] In some embodiments of the seventh aspect, the communication device further includes: a processing module; a transceiver module, further configured to: receive identification information of a second device sent by a first device, the identification information of the second device being sent to the first device by the second device through random access; and the processing module is further configured to establish context information of the second device based on the identification information of the second device.

[0129] In an eighth aspect, embodiments of this disclosure provide a communication device. This communication device is used to perform the communication method as described in any one of the first, second, third, and possible implementations thereof.

[0130] In a ninth aspect, embodiments of this disclosure provide a communication system. The communication system includes at least one of a first device, a second device, and a third device. The first device is configured to perform a communication method as described in any one of the first aspects and their possible embodiments. The second device is configured to perform a communication method as described in any one of the second aspects and their possible embodiments. The third device is configured to perform a communication method as described in any one of the third aspects and their possible embodiments.

[0131] In a tenth aspect, embodiments of this disclosure provide a storage medium. The storage medium stores instructions. When executed on a communication device, the instructions cause the communication device to perform a communication method as described in any one of the first, second, third, and possible embodiments thereof.

[0132] In an eleventh aspect, embodiments of this disclosure provide a program product. The program product includes at least one of a program and instructions. When executed by a communication device, the program or instructions implement the steps of the communication method as described in any one of the first, second, third, and possible embodiments thereof.

[0133] In a twelfth aspect, embodiments of this disclosure provide a computer program. When this computer program is run on a computer, it causes the computer to perform the communication method as described in any one of the first, second, third, and possible implementations thereof.

[0134] In a thirteenth aspect, embodiments of this disclosure provide a chip or chip system. The chip or chip system includes processing circuitry. The processing circuitry is configured to perform a communication method as described in any one of the first, second, third, and possible embodiments thereof.

[0135] It is understood that the aforementioned communication devices, communication systems, storage media, program products, computer programs, chips, and chip systems are all used to execute the methods provided in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0136] This disclosure provides a communication method, communication device, communication system, storage medium, and program product. In some embodiments, terms such as communication method, information processing method, and paging method can be used interchangeably; terms such as terminal, communication device, information processing device, information transmission device, Internet of Things device, reader, network device, communication equipment, network function, and network entity can be used interchangeably; and terms such as communication system, information processing system, and information transmission system can be used interchangeably.

[0137] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0138] In the embodiments disclosed herein, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the various embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0139] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0140] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.

[0141] In the embodiments of this disclosure, "a plurality of" means two or more.

[0142] In some embodiments, the terms “at least one of A or B, at least one of A and B”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.

[0143] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of whether there is a branch B); in some embodiments, B (execute B regardless of whether there is a branch A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, both A and B are executed. The same applies when there are more branches such as A, B, C, etc.

[0144] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execute A regardless of whether a branch B exists); in some embodiments, B (execute B regardless of whether a branch A exists); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, and C.

[0145] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0146] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0147] In some embodiments, terms such as “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “when…”, “if…”, etc. can be used interchangeably. These descriptions all refer to the device making a corresponding action under certain objective circumstances. They do not necessarily limit the time, nor do they require the device to make a judgment action when implementing it, nor do they mean that there must be other limitations.

[0148] In some embodiments, terms such as “greater than,” “more than,” “higher than,” and “exceeding” can be used interchangeably; terms such as “greater than or equal to,” “not less than,” “more than or equal to,” “not less than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably; terms such as “less than,” “less than,” and “lower than” can be used interchangeably; and terms such as “less than or equal to,” “not greater than,” “less than or equal to,” “not more than,” “lower than or equal to,” “not higher than,” and “below” can be used interchangeably.

[0149] In some embodiments, devices, etc., can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. Terms such as “device”, “equipment”, “circuit”, “network element”, “node”, “function”, “unit”, “section”, “system”, “network”, “chip”, “chip system”, “entity”, and “subject” can be used interchangeably.

[0150] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).

[0151] In some embodiments, the terms "access network device (AN device)," "radio access network device (RAN device)," "base station (BS)," "radio base station," "fixed station," "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cell group," "serving cell," "carrier," "component carrier," and "bandwidth part (BWP)" can be used interchangeably.

[0152] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", "subscriber station", "mobile unit", "subscriber unit", "wireless unit", "remote unit", "mobile device", "wireless device", "wireless communication device", "remote device", "mobile subscriber station", "access terminal", "mobile terminal", "wireless terminal", "remote terminal", "handset", "user agent", "mobile client", and "client" can be used interchangeably.

[0153] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, embodiments of this disclosure can also be applied to structures where communication between access network devices, core network devices, or network devices and terminals is replaced by communication between multiple terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, and uplink link, downlink, etc., can be replaced with sidelink link.

[0154] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, core network device, or network device may also be configured to have all or some of the functions of the terminal.

[0155] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

[0156] In some embodiments, data, information, etc., may be obtained with the user's consent.

[0157] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0158] Figure 1 is a schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure. As shown in Figure 1, the communication system 100 includes a terminal 101 and a network device 102. The network device 102 can be at least one of an access network device and a core network device.

[0159] In some embodiments, terminal 101 includes, but is not limited to, at least one of the following: mobile phone, wearable device, Internet of Things device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, and wireless terminal device in smart home.

[0160] In some embodiments, the access network device is, for example, a node or device that connects a terminal to a wireless network. The access network device may include, but is not limited to, at least one of the following in a 5G communication system: evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), node B (NB), home node B (HNB), home evolved node B (HeNB), radio backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in a 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in a Wi-Fi system.

[0161] In some embodiments, the technical solutions of this disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within access network devices involved in the embodiments of this disclosure can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.

[0162] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

[0163] In some embodiments, the communication system 100 may include a 5G communication system (5GS) or a 6G communication system (6GS). It should be noted that the communication system 100 may also be other communication systems, such as a 4G communication system (LTE), and this disclosure does not specifically limit it.

[0164] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions provided in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in this disclosure are also applicable to similar technical problems.

[0165] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.

[0166] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1, or some of the main bodies in the communication system 100, but are not limited thereto. The main bodies shown in FIG1 are illustrative. The communication system 100 may include all or some of the main bodies in 1, or may include other main bodies besides 1. The number and form of each main body are arbitrary. Each main body may be physical or virtual. The connection relationship between the main bodies is illustrative. The main bodies may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0167] The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0168] In some cases, with the application of Internet of Things (IoT) technology across various industries, the large-scale deployment of IoT devices powered by traditional batteries is limited by factors such as environment, cost, and energy conservation. This makes it unsuitable for certain scenarios and negatively impacts user experience. In some embodiments, the astronomical growth of IoT networks, coupled with the proliferation of IoT devices, has pushed network maintenance costs, including labor and battery costs, to unprecedented levels. Furthermore, billions of traditional batteries are discarded annually, with only a small fraction being effectively recycled, causing harmful impacts on the Earth's ecosystem. Maintaining IoT networks and replacing batteries can be extremely challenging under extreme environmental conditions. Therefore, battery-free IoT (also known as passive IoT) communication has been proposed, which improves network performance and sustainability and expands application scenarios. Moreover, battery-free communication is more environmentally friendly and safer for children and the elderly. By eliminating traditional batteries, device size and cost can be significantly reduced, paving the way for a variety of new applications.

[0169] In some embodiments, various low-power wide-area (LPWA) technologies, such as machine-type communication (MTC), narrowband Internet of Things (NB-IoT), and reduced-capability (RedCap) terminals, have been developed to meet the growing demands of vertical industries. These LPWA technologies achieve low cost, low power consumption, and massive connectivity, satisfying the requirements of many applications. However, the following issues still need to be addressed: 1. In some scenarios (such as extreme environmental conditions, such as high pressure, extremely high / low temperatures, and humid environments), traditional battery-powered devices are not suitable. 2. Maintenance-free devices (such as devices that do not require replacement of traditional batteries) are needed. 3. Devices with ultra-low complexity, very small device size (e.g., millimeter (mm) thickness), and longer lifespan are required. To meet these unmet needs, ambient energy-enabled IoT is a promising technology.

[0170] In some embodiments, an ambient energy-enabled IoT device is an IoT device powered by harvested energy. Such IoT devices are battery-free or have limited energy storage capacity (e.g., the device uses capacitors). An ambient energy-enabled IoT device can power itself by harvesting radio waves, light, motion, heat, or any other suitable source of energy to drive wireless communication or data transmission.

[0171] In some embodiments, the above-mentioned IoT devices that support ambient energy can be used interchangeably with terms such as passive devices, passive IoT devices, ambient energy-based devices, and ambient IoT (A-IoT) devices.

[0172] In some embodiments, energy harvested from the environment can power IoT devices that support ambient energy for data transmission and wireless communication. Current mainstream low-power IoT communication chips (such as Bluetooth Low Energy (BLE) chips, Long Range Radio (LoRa) chips, and NB-IoT chips) consume tens or even hundreds of milliwatts of power for transmission and reception, while energy harvested from the environment is only in the microwatt range, insufficient to power devices with these types of chips. Therefore, a new wireless communication technology is needed to reduce communication power consumption to tens or even less than ten microwatts. Backscatter (BS) communication technology can be used for this purpose. Backscatter communication is one of the key technologies for building a green, energy-efficient, low-cost, and flexibly deployable future IoT, and is an important means of realizing "intelligent interconnection of everything."

[0173] In some embodiments, backscatter communication utilizes the principle of backscattering radio frequency signals to design an extremely low-power modulation and transmission technology. As shown in Figure 1B, which is a schematic diagram illustrating wireless communication based on backscattering according to an embodiment of this disclosure, an excitation source 11 transmits a radio frequency signal to a passive device 12. When the radio frequency signal reaches the passive device 12, a portion is reflected. The passive device 12 can adjust the matching between its receiving antenna and impedance according to the information to be transmitted to enhance the reflection of the radio frequency signal and modulate the information to be transmitted onto the backscattered signal for transmission. This process is similar to a reflector. Compared to other communication technologies, backscatter transmission does not require complex radio frequency structures, reducing the use of devices such as power amplifiers, high-precision crystal oscillators, duplexers, and high-precision filters. It also does not require complex baseband processing, thus simplifying terminal design and significantly reducing terminal node costs.

[0174] In some embodiments, the radio frequency signal is used to provide energy for the passive device 12 to transmit signals. Therefore, the radio frequency signal can be referred to as an excitation signal or a trigger signal.

[0175] In some embodiments, the excitation source 11 may be the reader of the passive device 12 or the anchor point of the reader.

[0176] In some embodiments, backscatter communication has been widely used in radio frequency identification (RFID) systems, resulting in many large-scale commercial applications. Its working principle is that the receiver (typically an RFID reader) sends a radio frequency excitation signal to activate a passive node (typically an RFID tag). The tag uses backscatter communication to modulate its own information onto the radio frequency signal. The reader receives the reflected signal from the tag and demodulates it to achieve information transmission.

[0177] However, current RFID technology also has many drawbacks, such as short coverage distance (the wireless signal experiences double-path fading during communication, resulting in significant path loss and a short effective communication distance), single-channel transmission, the need for precise tag alignment, and the lack of power control. There is significant room for improvement in the communication aspects of RFID technology. For example, integrating 3GPP communication technologies is needed to improve the wireless communication performance of RFID in A-IoT.

[0178] In some embodiments, when A-IoT technology is integrated into the communication system 100 described above, the present disclosure embodiments may provide, but are not limited to, the following A-IoT system architectures:

[0179] Architecture 1: As shown in Figure 1C, Figure 1C is a schematic diagram of an A-IoT system architecture according to an embodiment of this disclosure. Uplink and / or downlink transmissions are directly performed between the passive device 12 and the network device 20 (such as an access network device).

[0180] Architecture 2: As shown in Figure 1D, Figure 1D is a schematic diagram of another architecture of an A-IoT system according to an embodiment of this disclosure. The passive device 12 and the network device 20 (such as an access network device) indirectly perform uplink and / or downlink transmissions through an intermediate node 30.

[0181] In some embodiments, intermediate node 30 forwards uplink and / or downlink transmissions. For example, intermediate node 30 may be a relay node, an access integration backhaul (IAB) node, a terminal, a repeater, etc.

[0182] Architecture 3: As shown in Figure 1E, Figure 1E is a schematic diagram of another architecture of an A-IoT system according to an embodiment of this disclosure. The passive device 12 and the network device 20 (such as an access network device) directly perform one of the uplink and downlink transmissions, and indirectly perform the other of the uplink and downlink transmissions through an auxiliary node 40.

[0183] In some embodiments, the auxiliary node 40 forwards uplink and / or downlink transmissions. For example, the auxiliary node 40 may be a relay node, an access integration backhaul (IAB) node, a terminal, a repeater, etc.

[0184] Architecture 4: As shown in Figure 1F, Figure 1F is a schematic diagram of another architecture of the A-IoT system according to an embodiment of this disclosure. The passive device 12 and the terminal 50 directly perform uplink and downlink transmissions. The terminal 50 is responsible for collecting data from the passive device 12 and forwarding the collected data to the network side.

[0185] In some embodiments, the excitation source of the passive device 12 may include at least one of the network device 20, intermediate node 30, auxiliary node 40, and terminal 50.

[0186] In some embodiments, the A-IoT system can support both Architecture 1 and Architecture 2 topologies described above. In one embodiment, when the A-IoT system can communicate using either Architecture 1 or Architecture 2, the available spectrum resources can include three deployment modes: in-band mode, guard-band mode, or stand-alone mode. In-band mode refers to transmission using general uplink and / or downlink spectrum resources. Guard-band mode refers to transmission using the guard band spectrum resources between the general uplink and downlink spectrum. Stand-alone mode refers to transmission using spectrum resources unrelated to the general transmission spectrum.

[0187] In some embodiments, FIG1G is a schematic diagram of a passive device according to an embodiment of the present disclosure. As shown in FIG1G, the passive device 12 may be, but is not limited to, the following three types:

[0188] Type A: No energy storage and no independent signal generation / amplification, and transmission is based on backscattering.

[0189] Type B: Has energy storage but no independent signal generation, and transmits based on backscattering. The energy stored in passive device 12 can be used to amplify the backscattered signal.

[0190] Type C: It has energy storage to enable independent signal generation and uses active radio frequency components for transmission.

[0191] In some embodiments, the following constraints may be imposed on A-IoT devices:

[0192] The overall goal should be to research a coordinated air interface design that minimizes the differences in IoT environments (where necessary) to enable the following devices:

[0193] Peak power consumption is approximately 1 μW, with energy storage capability. Initial sampling frequency offset (SFO) is as high as 10Xppm (per million units). The device contains neither DL nor UL amplification. The UL transmission of this device is backscattered on an externally provided carrier.

[0194] Peak power consumption ≤ several hundred μW, with energy storage capability, initial SFO up to 10X ppm, and DL and / or UL amplification capabilities. The UL transmission of the device can be generated internally or backscattered on an externally provided carrier.

[0195] The above X will be decided within the work group (WG).

[0196] In some cases, in order to support data transmission of passive device 12, a device in the network needs to support at least one of the following functions:

[0197] The function of the energy source (ES) is only used for passive devices 12 of type B and passive devices 12 of type C.

[0198] The downlink transmission (DT) function sends an indication message to the passive device 12, thereby triggering the uplink transmission of the passive device 12. This function is only used for type A passive devices 12.

[0199] As a continuous wave (CW) function, it is only used for Type A passive devices 12 and Type B passive devices 12. Type A passive devices 12 achieve uplink transmission through backscattered CW. CW is actually also a type of energy storage (ES), and Type A passive devices 12 can receive CW and store energy.

[0200] The uplink receive (UR) function receives D2R messages backscattered by passive device 12, or receives D2R messages actively transmitted by passive device 12, and is only used for passive device 12 of type A.

[0201] It should be noted that the devices that perform the above-mentioned ES, DT, CW, UR and other functions can be terminals, repeaters, relay nodes or network devices, etc.

[0202] In some embodiments, a passive device 12 may support only one of the above functions. Alternatively, a passive device 12 may support only a number of the above functions. Or, a passive device 12 may support only all of the above functions.

[0203] In some embodiments, FIG1H is a schematic diagram of the interaction between a reader and a device in a passive Internet of Things system according to an embodiment of the present disclosure.

[0204] Step S1: The reader sends an inventory command to the device (such as a tag).

[0205] In some embodiments, inventory commands include Query, QueryAdjust, QueryRep, ACK, and NACK.

[0206] In some embodiments, the Query command carries a parameter Q. In one example, the value of parameter Q is between 0 and 15.

[0207] In step S2, after receiving a valid Query command, the device generates a random value (such as RN16) based on the Q value and sends the RN16 back to the reader.

[0208] Step S3: The reader sends an ACK command carrying RN16.

[0209] In some embodiments, the reader generates the same RN16 as RN16 in step S2 and sends the RN16 in the ACK command.

[0210] In step S4, after receiving a valid ACK command, the device backscatters application data to the reader and enters the acknowledgment state.

[0211] In some embodiments, after receiving a valid ACK command carrying the correct RN16, the device sends application data to the reader so that the reader can identify the device. In one example, the application data may include protocol control (PC), EPC, and checksum (CRC).

[0212] In some embodiments, if the device does not receive a valid ACK command or receives an ACK command but the ACK command carries an incorrect RN16, it will not respond.

[0213] In step S5, the reader sends a random number request (such as Req_RN) to the device, wherein Req_RN carries the same RN16 as RN16 in step S2.

[0214] In step S6, after receiving a valid Req_RN, the device sends a handle back to the reader to identify the communication between the reader and the device.

[0215] In some embodiments, if the device does not receive a valid Req_RN or receives a Req_RN but the Req_RN carries an incorrect RN16, it will not respond.

[0216] In step S7, the reader sends a command to access the device.

[0217] In some embodiments, the command carries a handle configured by the reader for the device.

[0218] Step S8: The device verifies the above command.

[0219] In some embodiments, IoT devices can access the network via a random access procedure. In one embodiment, an IoT device can access the network via a contention-based random access (CBRA) procedure. In another embodiment, an IoT device can access the network via a contention-free random access (CFRA) procedure.

[0220] In some embodiments, FIG1I is a schematic diagram of a random access process for an Internet of Things (IoT) device according to an embodiment of the present disclosure. As shown in FIG1I, the random access process for an IoT device includes steps S101 to S105.

[0221] In step S101, the network device sends a paging message to the IoT device.

[0222] In some embodiments, the paging message may be triggered by a service request message. In one embodiment, the A-IoT core network (CN) may send a service request message to a network device, and the network device may respond to the service request message by sending a paging message to the IoT device.

[0223] In some embodiments, the network device can be a reader. The IoT device can be a passive device.

[0224] In some embodiments, the network device broadcasts a paging message.

[0225] In some embodiments, the paging message may also be referred to as message 0 (msg0).

[0226] In some embodiments, network devices trigger random access of IoT devices via msg0.

[0227] It should be noted that the term "message" in this disclosure can be replaced with terms such as "information," "signaling," "signaling," or "command." Of course, it can also refer to other transmission forms sent by network devices to IoT devices to perform a certain operation on the IoT devices. This disclosure does not specifically limit this.

[0228] In step S102, the IoT device returns message 1 (msg1) to the network device based on the paging message.

[0229] In some embodiments, after receiving a paging message, the IoT device determines whether random access is required based on the device that needs to respond as indicated in the paging message. If random access is required, the IoT device may send msg1 as a response message to the paging message.

[0230] In some embodiments, msg1 carries an RN16 generated by an IoT device.

[0231] In step S103, the network device sends message 2 (msg2) to the IoT device.

[0232] In some embodiments, after receiving msg1, the network device, based on the successfully received RN16 response msg1, sends msg2, which is a response message to msg1. In one example, msg2 could be referred to as a random access response (RAR) message.

[0233] In some embodiments, msg2 carries RN16.

[0234] In some embodiments, after receiving msg2, the IoT device can respond to msg2 by sending msg3 to the network device.

[0235] In step S104, the IoT device sends message 3 (msg3) to the network device.

[0236] In some embodiments, after receiving msg2, the IoT device can respond to msg2 by sending msg3 to the network device.

[0237] In some embodiments, msg3 may carry RN16 and the device ID of the IoT device.

[0238] In step S105, the network device sends message 4 (msg4) to the IoT device.

[0239] In some embodiments, after receiving msg3, the IoT device can respond to msg3 by sending msg4 to the network device.

[0240] In some embodiments, FIG1J is a schematic diagram of a random access process for an Internet of Things (IoT) device according to an embodiment of the present disclosure. As shown in FIG1J, the random access process for an IoT device includes steps S111 to S115.

[0241] In step S111, the IoT device successfully completes the access process and has sent its device ID to the reader, which then forwards the device ID to the AIoT core network (AIoT CN).

[0242] In step S112, the reader obtains the information of the IoT device from the AIoT core network. At the same time, the reader and the AIoT core network maintain the context information of the IoT device, such as the next generation access point identifier (NG AP ID) and access stratum identifier (AS ID) associated with the IoT device.

[0243] In step S113, the reader fails to send information from the AIoT core network to the IoT device.

[0244] In some cases, the reader sends information from the AIoT core network to the IoT device through step S113. However, due to uneven uplink and downlink quality or temporary obstruction, the IoT device does not receive the information. In this case, the IoT device will be unable to send the corresponding response to the reader.

[0245] In step S114, the reader fails to receive a response from the IoT device.

[0246] In some cases, the reader sends information from the AIoT core network to the IoT device via step S113, and the IoT device receives this information and sends a corresponding response to the reader. However, due to uneven uplink and downlink quality, or temporary obstruction, the reader may not receive this response.

[0247] In step S115, the reader confirms that no response has been received from the IoT device.

[0248] In the above scenario, if the reader does not receive a response from the IoT device after waiting for a period of time or repeatedly sending the information, the reader can determine that the information transmission failed, the response reception failed, the second device did not receive the information, and the first device did not receive the response.

[0249] In this situation, it is necessary to clarify how IoT devices, readers, and the AIoT core network should further handle the situation. In one embodiment, if the transmission of information to an IoT device fails, the uncertainty of subsequent operations will increase communication latency and reduce communication efficiency.

[0250] In some embodiments, the AIoT core network may be deployed with AIoT core network devices, also known as AIoT functions (AIoTF). In one embodiment, the AIoTF is used to dynamically adjust policies and billing rules based on IoT device type, service requirements, etc., to optimize resource allocation and improve device access efficiency.

[0251] In some embodiments, AIoTF can collaborate with core network devices such as access and mobility management function (AMF), session management function (SMF), and user plane function (UPF).

[0252] To address the aforementioned issues, this disclosure provides a communication method, communication device, communication system, storage medium, and program product that can avoid waiting time caused by uncertain subsequent operations, significantly reduce communication latency, and improve communication efficiency.

[0253] In some embodiments, the first device can be a reader of the second device. In one example, the first device can be a base station, an intermediate node or an auxiliary node, or a terminal.

[0254] In some embodiments, the second device may be a passive device. In one example, the passive device may be an AIoT device.

[0255] In some embodiments, the third device may be an AIoT core network device. In one example, the AIoT core network device may be an AIoTF.

[0256] Figure 2A is an exemplary interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 2A, the embodiment of the present disclosure relates to a communication method executed by the aforementioned A-IoT system. In one example, the communication method includes steps S2101 to S2108.

[0257] In some embodiments, if the second information transmission fails, steps S2101 to S2108 may be performed.

[0258] In some embodiments, if the reception of the third information fails, steps S2101 to S2108 may be performed.

[0259] In some embodiments, if the second device does not receive the second information, steps S2101 to S2108 may be performed.

[0260] In some embodiments, if the third device does not receive the third information, steps S2101 to S2108 may be executed.

[0261] It should be noted that the terms "failed to send second information", "failed to receive third information", "second device did not receive second information", and "third device did not receive third information" are interchangeable.

[0262] In some embodiments, the second information described above can be understood as information sent from the first device or the third device to the second device, such as a command or a message. In one example, when the second information is sent from the first device to the second device, the second information can be referred to as reader-to-device (R2D) information. In some embodiments, the third information described above can be understood as information sent from the second device to the first device or the third device, and the response is a response to the aforementioned information, such as a command response or a message response. In one example, when the third information is sent from the second device to the first device, the third information can be referred to as device-to-reader (D2R) information.

[0263] In some embodiments, the second information may be the entirety of the information sent by the first device or the third device to the second device, or it may be a segment of the information sent by the first device or the third device to the second device.

[0264] In some embodiments, the third information may be the entirety of the response sent by the second device to the first or third device, or it may be a segment of the response sent by the second device to the first or third device.

[0265] In some embodiments, the information sent by the first device or the third device may be associated with a second service identifier. In one embodiment, the second information includes the second service identifier. In one example, the second service identifier may be a session ID of the first IoT service or a transaction ID of the first IoT service.

[0266] In step S2101, the first device sends fourth information to the third device.

[0267] In some embodiments, the first device sends fourth information. In some embodiments, the fourth information may be sent by the first device, but is not limited thereto, and may also be sent by other entities.

[0268] In some embodiments, the third device receives the fourth information. In some embodiments, the fourth information may be received by the third device, but is not limited thereto, and may also be received by other entities.

[0269] In some embodiments, if the first device determines that the transmission of the second information has failed or the reception of the third information has failed, it sends a fourth message to the third device. In one embodiment, the fourth message is used to indicate that the transmission of the second information has failed. In some embodiments, the fourth message is used to indicate the end of a process related to the second information. In one embodiment, the second information may include third identification information associated with the second device, which is used to identify the second device. In one embodiment, the third identification information may also be referred to as the identifier of the second device. In one example, the third identification information may include at least one of NG AP ID, RN16, AS ID, and device ID.

[0270] In some embodiments, the fourth information includes first identification information associated with the second device. The first identification information is used to identify the second device. In one embodiment, the first identification information may also be referred to as the identifier of the second device. In one embodiment, the first identification information is the same as the third identification information. In one example, the first identification information may include at least one of NG AP ID, RN16, AS ID, and device ID.

[0271] In step S2102, the third device deletes the context information of the second device.

[0272] In some embodiments, after receiving the fourth information, the third device determines that the second device failed to send the second information, and the process corresponding to the second information ends. At this time, the context information of the second device becomes invalid, and the third device deletes the context information of the second device.

[0273] In some embodiments, the context information of the second device may include at least one of: first identification information associated with the second device, second information to be sent, and third information already received. In one embodiment, the second information in the context information of the second device may be second information stored locally by the third device and to be sent to the first device. In one embodiment, the third information in the context information of the second device may be third information received from the second device and stored locally by the third device, i.e., a response to the second information.

[0274] In step S2103, the first device deletes the context information of the second device.

[0275] In some embodiments, if the first device determines that the second device has failed to send second information or failed to receive third information, the first device deletes the context information of the second device.

[0276] In some embodiments, the context information of the second device may include at least one of: first identification information associated with the second device, second information to be sent, and third information already received. In one embodiment, the second information in the context information of the second device may be second information stored locally by the first device and to be sent to the second device. In one embodiment, the third information in the context information of the second device may be third information received from the second device and stored locally by the first device, i.e., a response to the second information.

[0277] In some embodiments, steps S2102 and S2103 can be executed simultaneously or sequentially. In one embodiment, the execution order of steps S2102 and S2103 can be interchanged.

[0278] In step S2104, the first device sends a first service identifier or an end identifier to the second device.

[0279] In some embodiments, the first device sends a first service identifier or an end identifier. In some embodiments, the first service identifier or end identifier may be sent by the first device, but is not limited thereto, and may also be sent by other entities.

[0280] In some embodiments, the second device receives a first service identifier or an end identifier. In some embodiments, the first service identifier or end identifier may be received by the second device, but is not limited thereto, and may also be received by other entities.

[0281] In some embodiments, a first service identifier is used to indicate that the transmission of second information failed or the reception of third information failed. In some embodiments, an end identifier is used to indicate that the transmission of second information failed or the reception of third information failed. In some embodiments, the first service identifier or the end identifier is used to indicate a transmission interruption between the first device and the second device, or it may indicate a transmission failure between the first device and the second device.

[0282] In some embodiments, the first device can implicitly indicate to the second device that the transmission of the second information has failed or the reception of the third information has failed. In this case, the first information may include a first service identifier, i.e., a new service identifier. Based on this, the first device indicates the failure of the transmission of the second information or the failure of the reception of the third information through the new service identifier; in other words, the first device indicates the end of the process associated with the second service identifier through the new service identifier. In one embodiment, the first service identifier may be included in a paging message or a trigger message.

[0283] In some embodiments, the first device may also explicitly indicate to the second device that the second information transmission failed or the third information reception failed. In this case, the first information may be an end identifier to indicate the end of the process associated with the second service identifier. In one embodiment, the end identifier may be included in a paging message or a trigger message, which may also carry the second service identifier.

[0284] In step S2105, the second device deletes the third information to be sent.

[0285] In some embodiments, after receiving the first service identifier or the end identifier, the second device determines that the second information transmission failed or the third information reception failed. In this case, the response to the second information, i.e., the third information, is invalid. The second device deletes the third information.

[0286] In some embodiments, the third information deleted by the second device may be third information stored locally on the second device, i.e., a response to the second information. This third information may be the complete response from the third device to the second device, or it may be a segmented response from the third device to the second device. In some embodiments, the third information stored locally on the second device may be third information that the second device did not send to the first device.

[0287] In some embodiments, if the second device does not have any third information to be sent stored locally after receiving the first service identifier or the end identifier, then step S2106 is omitted.

[0288] In step S2106, the third device sends the fifth information to the first device.

[0289] In some embodiments, the third device sends the fifth information. In some embodiments, the fifth information may be sent by the first device, but is not limited thereto, and may also be sent by other entities.

[0290] In some embodiments, the first device receives the fifth information. In some embodiments, the fifth information may be received by the first device, but is not limited thereto, and may also be received by other entities.

[0291] In some embodiments, the fifth information is used to trigger the first device to send a paging message to the second device, and the paging message is used to trigger the second device to perform random access. In this case, the first information is the paging message. In one embodiment, after deleting the context information of the second device, if the third device needs to continue sending information to the second device, the third device can send the fifth information to the first device to trigger the first device to send a paging message to the second device, causing the second device to perform random access. In one embodiment, the paging message triggers the second device to perform non-contention-based random access. In one embodiment, the fifth information can be a service request message.

[0292] In some embodiments, the fifth information is used to initiate a new IoT service, thereby instructing the third device to continue sending information to the second device. In some embodiments, the fifth information may include a first service identifier, i.e., a new service identifier. In one example, the first service identifier may be a session ID of the second IoT service, a transaction ID of the second IoT service, etc.

[0293] In some embodiments, the fifth information may include a first identifier, which may indicate a device, such as a second device, to instruct the third device to continue sending information to the second device. In one example, the first identifier may be a temporary identifier (temp-ID), tag ID (TID), electronic product code (EPC), etc.

[0294] In some embodiments, if the paging message is not triggered by a third device, and the first information is not sent by the first device based on the fifth information, then step S2206 can be omitted.

[0295] In step S2107, the first device sends a paging message to the second device.

[0296] In some embodiments, the first device sends a paging message. In some embodiments, the paging message may be sent by the first device, but is not limited to this, and may also be sent by other entities.

[0297] In some embodiments, the second device receives the paging message. In some embodiments, the paging message may be received by the second device, but is not limited thereto, and may also be received by other entities.

[0298] In some embodiments, a paging message is used to trigger a second device to initiate a non-contention-based random access.

[0299] In some embodiments, the paging message includes a first identifier, which may indicate a second device. In this case, the second device is the device that needs to respond to the paging message, and may also be referred to as the paged device. In one example, the first identifier may be the device identifier of the device that needs to respond, such as the device identifier of the second device. In one implementation, the first identifier may be assigned by the access network (such as A-IoT RAN) or by the core network (such as AIoTF). In one embodiment, the first identifier may uniquely identify a device; in other words, the first identifier may be a global identifier.

[0300] In some embodiments, the device requiring a response may be an A-IoT device in a connected state. In some embodiments, the device requiring a response may be an A-IoT device in an idle state. In some embodiments, the device requiring a response may be an A-IoT device in an inactive state.

[0301] In step S2108, the second device performs non-contention-based random access.

[0302] In some embodiments, after receiving a paging message, the second device determines whether random access is required based on the device that needs to respond as indicated in the paging message. In one embodiment, the second device can determine whether it is a device that needs to respond based on its own identification information and the identification information carried in the paging message. In one embodiment, if the second device is a device that needs to respond, then the second device determines to perform random access.

[0303] In some embodiments, when the paging message includes a first identifier (such as a device identifier), the second device can determine that it is the device requiring a response by matching the device identifier information included in the paging message with the device identifier of the second device stored locally. In one embodiment, if the device identifier included in the paging message is the same as the device identifier of the second device stored locally, it indicates that the second device is the device requiring a response.

[0304] In some embodiments, the paging message includes a device identifier to indicate a specific device, namely the second device. In this case, after the second device is identified as the device requiring a response, it initiates a non-contention-based random access. The second device then sends message 1 (msg1) to the first device. Message 1 includes the identification information of the second device to identify the first device.

[0305] In some embodiments, if the third device does not continue to communicate with the second device, steps S2106 to S2108 are omitted.

[0306] Thus, the communication method involved in the embodiments of this disclosure is achieved through the above steps S2101 to S2108.

[0307] Figure 2B is an exemplary interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 2B, the embodiment of the present disclosure relates to a communication method executed by the aforementioned A-IoT system. In one example, the communication method includes steps S2201 to S2208.

[0308] In some embodiments, if the second information transmission fails, steps S2101 to S2108 may be performed.

[0309] In some embodiments, if the reception of the third information fails, steps S2101 to S2108 may be performed.

[0310] In some embodiments, if the second device does not receive the second information, steps S2101 to S2108 may be performed.

[0311] In some embodiments, if the third device does not receive the third information, steps S2101 to S2108 may be executed.

[0312] It should be noted that the terms "failed to send second information", "failed to receive third information", "second device did not receive second information", and "third device did not receive third information" are interchangeable.

[0313] In some embodiments, the second information described above can be understood as information sent from the first device or the third device to the second device, such as a command or a message. In one example, when the second information is sent from the first device to the second device, the second information can be referred to as reader-to-device (R2D) information. In some embodiments, the third information described above can be understood as information sent from the second device to the first device or the third device, and the response is a response to the aforementioned information, such as a command response or a message response. In one example, when the third information is sent from the second device to the first device, the third information can be referred to as device-to-reader (D2R) information.

[0314] In some embodiments, the second information may be the entirety of the information sent by the first device or the third device to the second device, or it may be a segment of the information sent by the first device or the third device to the second device.

[0315] In some embodiments, the third information may be the entirety of the response sent by the second device to the first or third device, or it may be a segment of the response sent by the second device to the first or third device.

[0316] In some embodiments, the information sent by the first device or the third device may be associated with a second service identifier. In one embodiment, the second information includes the second service identifier. In one example, the second service identifier may be a session ID of the first IoT service or a transaction ID of the first IoT service.

[0317] In step S2201, the first device sends fourth information to the third device.

[0318] The optional implementation of step S2201 can be found in the optional implementation of step S2101 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0319] In step S2202, the third device deletes the context information of the second device.

[0320] The optional implementation of step S2202 can be found in the optional implementation of step S2102 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0321] In step S2203, the first device deletes the context information of the second device.

[0322] The optional implementation of step S2203 can be found in the optional implementation of step S2103 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0323] In some embodiments, steps S2202 and S2203 can be executed simultaneously or sequentially. In one embodiment, the execution order of steps S2202 and S2203 can be interchanged.

[0324] In step S2204, the first device sends a negative acknowledgment (NACK) message to the second device.

[0325] In some embodiments, the first device sends a NACK message. In some embodiments, the NACK message may be sent by the first device, but is not limited to this, and may also be sent by other entities.

[0326] In some embodiments, the second device receives a NACK message. In some embodiments, the NACK message may be received by the second device, but is not limited thereto, and may also be received by other entities.

[0327] In some embodiments, a NACK message is used to notify the second device that the transmission of the second information failed. In some embodiments, a NACK message is used to notify the second device that either the transmission of the second information failed or the reception of the third information failed. In this case, the first information is a NACK message.

[0328] In some embodiments, the NACK message may carry a second service identifier to indicate that the second information associated with the second service identifier failed to be sent, or to indicate that the third information associated with the second service identifier failed to be received.

[0329] In step S2205, the second device deletes the third information to be sent.

[0330] In some embodiments, after receiving a NACK message, the second device determines that either the second message transmission failed or the third message reception failed. In this case, the response to the second message, i.e., the third message, is invalid. The second device deletes the third message to be sent.

[0331] In some embodiments, the first information is a NACK message, and the second device responds to the NACK message by deleting the third information to be sent. In one embodiment, the third information deleted by the second device may be third information stored locally by the second device and to be sent to the first or third device, that is, a response generated by the second device to the received second information.

[0332] In some embodiments, if the second device does not have the third information to be sent stored locally after receiving the NACK message, step S2205 is omitted.

[0333] In step S2206, the third device sends the fifth information to the first device.

[0334] In some embodiments, the third device sends the fifth information. In some embodiments, the fifth information may be sent by the first device, but is not limited thereto, and may also be sent by other entities.

[0335] In some embodiments, the first device receives the fifth information. In some embodiments, the fifth information may be received by the first device, but is not limited thereto, and may also be received by other entities.

[0336] In some embodiments, the fifth information is used to trigger the first device to send a paging message to the second device, and the first information is used to trigger the second device to perform random access. In one embodiment, after deleting the context information of the second device, if the third device needs to continue sending information to the second device, the third device can send the fifth information to the first device to trigger the first device to send a paging message to the second device, causing the second device to perform random access. In one embodiment, the fifth information can be a service request message.

[0337] In some embodiments, the fifth information may include a second service identifier to instruct the first device to trigger the second device to perform random access. In some embodiments, the fifth information may include a first service identifier and a device identifier to instruct the first device to trigger the second device to perform random access.

[0338] In step S2207, the first device sends a paging message to the second device.

[0339] In some embodiments, the first device sends a paging message. In some embodiments, the paging message may be sent by the first device, but is not limited to this, and may also be sent by other entities.

[0340] In some embodiments, the second device receives the paging message. In some embodiments, the paging message may be received by the second device, but is not limited thereto, and may also be received by other entities.

[0341] In some embodiments, a paging message is used to trigger a second device to initiate random access.

[0342] In some embodiments, the paging message includes a second service identifier, which can instruct the second device to re-access the network for the first IoT service associated with the second service identifier. In one embodiment, the paging message includes a second service identifier, which can instruct the second device to re-access the network for the first IoT service. In some embodiments, the paging message includes a second service identifier, which can instruct the second device to establish a connection with the first device for the first IoT service.

[0343] In some embodiments, the paging message includes a first service identifier and a first identifier. The first identifier can indicate a second device, which is the device that needs to respond to the paging message, and can also be referred to as the paged device. In one example, the first identifier can be the device identifier of the device that needs to respond, such as the device identifier of the second device. In one implementation, the first identifier can be assigned by the access network (such as A-IoT RAN) or by the core network (such as AIoTF). In one embodiment, a first identifier can uniquely identify a device; in other words, the device identifier can be a global identifier.

[0344] In some embodiments, the paging message includes a first service identifier and a first identifier, which may instruct the second device to access the network for the second IoT service associated with the first service identifier. In some embodiments, the paging message including the first service identifier and the first identifier may instruct the second device to establish a connection with the first device for the second IoT service.

[0345] In some embodiments, the paging message may further include a first service identifier and a second identifier, the second identifier indicating multiple devices associated with the second device, where the multiple devices may be multiple devices requiring a response. In other words, the second identifier may indicate multiple devices requiring a response, including the second device. In some implementations, the second identifier may be assigned by the access network (such as A-IoT RAN) or by the core network (such as AIoTF). In one embodiment, a second identifier may uniquely identify a group of devices. The second identifier may be a global identifier.

[0346] In some embodiments, the paging message includes a first service identifier and a second identifier, which can instruct the second device to access the network for the second IoT service associated with the first service identifier. In some embodiments, the paging message including the first service identifier and the second identifier can instruct the second device to establish a connection with the first device for the second IoT service.

[0347] In some embodiments, the device requiring a response may be an A-IoT device in a connected state. In some embodiments, the device requiring a response may be an A-IoT device in an idle state. In some embodiments, the device requiring a response may be an A-IoT device in an inactive state.

[0348] In some embodiments, if the paging message is not triggered by a third device, and the first information is not sent by the first device based on the fifth information, then step S2206 can be omitted.

[0349] In step S2208, the second device performs random access.

[0350] In some embodiments, after receiving a paging message, the second device determines whether to respond to the paging message. If it determines to respond to the paging message, the second device initiates random access. In one embodiment, the second device initiates contention-based random access.

[0351] In some embodiments, after receiving a paging message, the second device determines whether random access is required based on the device that needs to respond as indicated in the paging message. In one embodiment, the second device can determine whether it is a device that needs to respond based on its own identification information and the identification information carried in the paging message. In one embodiment, if the second device is a device that needs to respond, then the second device determines to perform random access.

[0352] In some embodiments, the identification information of the second device may be a device identifier of the second device, which is locally stored on the second device and is used to identify the second device. In one embodiment, the identification information of the second device may be a second identifier associated with the second device, which is locally stored on the second device and is used to identify multiple devices associated with the second device.

[0353] In some embodiments, when the paging message includes device identification information, the second device matches the device identification information included in the paging message with the device identification of the second device stored locally to determine whether the second device is a device that needs to respond. In one embodiment, if the first identifier included in the paging message is the same as the device identification of the second device stored locally, it indicates that the second device is a device that needs to respond.

[0354] In some embodiments, when the paging message includes a second identifier, the second device matches the second identifier included in the paging message with a second identifier associated with the second device stored locally to determine whether the second device is a device that needs to respond. In one embodiment, if the second identifier included in the paging message is the same as the identifiers of multiple devices associated with the second device stored locally, it indicates that the second device is a device that needs to respond.

[0355] In some embodiments, the second identifier may indicate multiple devices, such as a group of devices, that need to respond to a paging message. In one embodiment, the second identifier may be a group ID of the device group. In one embodiment, the second identifier may also be a mask indicating multiple devices that need to respond. In one example, the mask may be a portion of the device identifier of the device that needs to respond. In one implementation, the mask may be assigned by the core network (such as AIoF). In one embodiment, the mask may uniquely indicate several devices. The mask may be a global mask. In one embodiment, the second identifier may also be filtering information indicating multiple devices that need to respond. In one example, the filtering information may be a portion of the device identifier of the device that needs to respond. In one implementation, the filtering information may be assigned by the core network (such as AIoF). In one embodiment, the filtering information may uniquely indicate several devices. The filtering information may be global filtering information.

[0356] In one embodiment, the terms "second identifier (group ID)," "mask," and "filtering information" can be used interchangeably.

[0357] In some embodiments, since the paging message includes a first identifier, the second device initiates a non-contention-based random access procedure after it is determined to be the device requiring a response. During the non-contention-based random access procedure, the second device sends its device identifier to the first device.

[0358] In some embodiments, since the paging message includes a second identifier, the second device initiates a contention-based random access process after it is determined to be the device requiring a response. During the contention-based random access process, the second device sends its device identifier to the first device.

[0359] In some embodiments, after the second device sends its device identifier to the first device via random access, the first device sends the device identifier to the third device. Since the third device deleted the context information of the second device in step S2202, it establishes new context information for the second device after receiving the device identifier. Then, the third device continues to send the information intended for the second device to the first device, which forwards it to the second device. The second device sends its response to the received information to the first device, which forwards it to the third device, thus restoring data transmission between the second device and the network.

[0360] Thus, the communication method involved in the embodiments of this disclosure is achieved through the above steps S2201 to S2208.

[0361] Figure 2C is an exemplary interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 2C, the embodiment of the present disclosure relates to a communication method executed by the aforementioned A-IoT system. In one example, the communication method includes steps S2301 to S2303.

[0362] In some embodiments, if the second information transmission fails, steps S2101 to S2108 may be performed.

[0363] In some embodiments, if the reception of the third information fails, steps S2101 to S2108 may be performed.

[0364] In some embodiments, if the second device does not receive the second information, steps S2101 to S2108 may be performed.

[0365] In some embodiments, if the third device does not receive the third information, steps S2101 to S2108 may be executed.

[0366] It should be noted that the terms "failed to send second information", "failed to receive third information", "second device did not receive second information", and "third device did not receive third information" are interchangeable.

[0367] In some embodiments, the second information described above can be understood as information sent from the first device or the third device to the second device, such as a command or a message. In one example, when the second information is sent from the first device to the second device, the second information can be referred to as reader-to-device (R2D) information. In some embodiments, the third information described above can be understood as information sent from the second device to the first device or the third device, and the response is a response to the aforementioned information, such as a command response or a message response. In one example, when the third information is sent from the second device to the first device, the third information can be referred to as device-to-reader (D2R) information.

[0368] In some embodiments, the second information may be the entirety of the information sent by the first device or the third device to the second device, or it may be a segment of the information sent by the first device or the third device to the second device.

[0369] In some embodiments, the third information may be the entirety of the response sent by the second device to the first or third device, or it may be a segment of the response sent by the second device to the first or third device.

[0370] In some embodiments, the information sent by the first device or the third device may be associated with a second service identifier. In one embodiment, the second information includes the second service identifier. In one example, the second service identifier may be a session ID of the first IoT service or a transaction ID of the first IoT service.

[0371] In step S2301, the first device saves the context information of the second device.

[0372] In some embodiments, if the first device determines that the second information has failed to be sent or the third information has failed to be received, it saves the context information and the second information of the second device in preparation for resuming transmission with the second device.

[0373] In some embodiments, the context information of the second device may include at least one of: first identification information associated with the second device, second information, and third information. In one embodiment, the second information in the context information of the second device may be second information stored locally by the first device. This second information may be the entirety of the information provided by the third device to the second device, or a segment of the information provided by the third device to the second device. In one embodiment, the third information in the context information of the second device may be third information stored locally by the first device, i.e., a response to the second information. This third information may be the entirety of the response to the information provided by the third device to the second device, or a segment of the response to the information provided by the third device to the second device.

[0374] In some embodiments, the second information stored locally by the first device is second information that the first device has not sent to the second device. In some embodiments, the third information stored locally by the first device is third information that the first device has received.

[0375] In step S2302, the first device sends a paging message to the second device.

[0376] In some embodiments, the first device sends a paging message. In some embodiments, the paging message may be sent by the first device, but is not limited to this, and may also be sent by other entities.

[0377] In some embodiments, the second device receives the paging message. In some embodiments, the paging message may be received by the second device, but is not limited thereto, and may also be received by other entities.

[0378] In some embodiments, a paging message is used to trigger a second device to initiate a non-contention-based random access.

[0379] In some embodiments, a paging message is used to indicate that the transmission of second information failed or the reception of third information failed. In some embodiments, a paging message is used to indicate a transmission interruption between the first device and the second device, or it may indicate a transmission failure between the first device and the second device. In this case, the first information is a paging message.

[0380] In some embodiments, the paging message includes a second service identifier, which can instruct the second device to re-access the network for the first IoT service associated with the second service identifier. In one embodiment, the paging message includes a second service identifier, which can instruct the second device to re-access the network for the first IoT service. In some embodiments, the paging message includes a second service identifier, which can instruct the second device to establish a connection with the first device for the first IoT service.

[0381] In some embodiments, the paging message includes a first identifier, which may indicate a second device. In this case, the second device is the device that needs to respond to the paging message, and may also be referred to as the paged device. In one example, the device identifier may be the device identifier of the device that needs to respond. In one implementation, the device identifier may be assigned by the access network (such as A-IoT RAN) or by the core network (such as AIoTF). In one embodiment, a device identifier may uniquely identify a device; in other words, the device identifier may be a global identifier.

[0382] In some embodiments, the paging message includes a second service identifier and a first identifier, which can instruct the second device to access the network for the first IoT service. In some embodiments, the paging message includes a second service identifier and a first identifier, which can instruct the second device to establish a connection with the first device for the first IoT service.

[0383] In some embodiments, the device requiring a response may be an A-IoT device in a connected state. In some embodiments, the device requiring a response may be an A-IoT device in an idle state. In some embodiments, the device requiring a response may be an A-IoT device in an inactive state.

[0384] In step S2303, the second device performs non-contention-based random access.

[0385] The optional implementation of step S2303 can be found in the optional implementation of step S2108 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0386] Thus, the communication method involved in the embodiments of this disclosure is achieved through the above steps S2301 to S2303.

[0387] Figures 2D to 2F are exemplary interactive schematic diagrams illustrating a communication method according to embodiments of the present disclosure. As shown in Figures 2D to 2F, embodiments of the present disclosure relate to a communication method executed by the aforementioned A-IoT system. In one example, the communication method includes steps S2401 to S2409.

[0388] In some embodiments, if the second information transmission fails, steps S2101 to S2108 may be performed.

[0389] In some embodiments, if the reception of the third information fails, steps S2101 to S2108 may be performed.

[0390] In some embodiments, if the second device does not receive the second information, steps S2101 to S2108 may be performed.

[0391] In some embodiments, if the third device does not receive the third information, steps S2101 to S2108 may be executed.

[0392] It should be noted that the terms "failed to send second information", "failed to receive third information", "second device did not receive second information", and "third device did not receive third information" are interchangeable.

[0393] In some embodiments, the second information described above can be understood as information sent from the first device or the third device to the second device, such as a command or a message. In one example, when the second information is sent from the first device to the second device, the second information can be referred to as reader-to-device (R2D) information. In some embodiments, the third information described above can be understood as information sent from the second device to the first device or the third device, and the response is a response to the aforementioned information, such as a command response or a message response. In one example, when the third information is sent from the second device to the first device, the third information can be referred to as device-to-reader (D2R) information.

[0394] In some embodiments, the second information may be the entirety of the information sent by the first device or the third device to the second device, or it may be a segment of the information sent by the first device or the third device to the second device.

[0395] In some embodiments, the third information may be the entirety of the response sent by the second device to the first or third device, or it may be a segment of the response sent by the second device to the first or third device.

[0396] In some embodiments, the information sent by the first device or the third device may be associated with a second service identifier. In one embodiment, the second information includes the second service identifier. In one example, the second service identifier may be a session ID of the first IoT service or a transaction ID of the first IoT service.

[0397] In step S2401, the first device sends fourth information to the third device.

[0398] The optional implementation of step S2401 can be found in the optional implementation of step S2101 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0399] In step S2402, the third device sends the fifth information to the first device.

[0400] In some embodiments, the third device sends the fifth information. In some embodiments, the fifth information may be sent by the first device, but is not limited thereto, and may also be sent by other entities.

[0401] In some embodiments, the first device receives the fifth information. In some embodiments, the fifth information may be received by the first device, but is not limited thereto, and may also be received by other entities.

[0402] In some embodiments, after receiving the fourth information, the third device can determine, based on service requirements, whether there is information that needs to be sent to the second device. If so, the third device determines to continue sending information to the second device; otherwise, it determines not to continue sending information to the second device. Then, the third device sends a fifth message to the first device to indicate whether to continue sending information to the second device.

[0403] In some embodiments, the fifth information is used to instruct the third device to continue sending information to the second device. In this case, the first device may send a paging message to the second device. Here, the first information is a paging message. In some embodiments, the fifth information is used to trigger the first device to send a paging message to the second device, and the first information is used to trigger the second device to perform random access. In one embodiment, if the third device needs to continue sending information to the second device, the third device may send the fifth information to the first device to trigger the first device to send a paging message to the second device, causing the second device to perform random access. In one embodiment, the fifth information may be a service request message.

[0404] In some embodiments, the fifth information further uses the first device to determine whether subsequent information sent by the third device is addressed to one device or multiple devices. In some embodiments, the fifth information includes at least one of the following: second identification information and identification type information. The second identification information is used to indicate at least one device that needs to respond to the paging message, the at least one device including the second device. The identification type information is used to indicate the type of the second identification information.

[0405] In some embodiments, the fifth information includes second identification information, through which the third device indicates to the first device whether the information subsequently sent by the third device is for one device or multiple devices.

[0406] In some embodiments, the second identification information can be the first identification. In this case, the second identification information indicates a device that needs to respond to the paging message. In one example, the first identification can be a temporary identifier (temp-ID), tag identifier (TID), electronic product code (EPC), etc.

[0407] In some embodiments, the second identification information may be a second identifier. In this case, the second identification information indicates a group of devices, i.e., multiple devices, that need to respond to the paging message. In one embodiment, the second identifier may be a group ID. In one embodiment, the second identifier may also be a mask indicating multiple devices that need to respond. In one example, the mask may be a portion of the device identifier of the device that needs to respond. In one implementation, the mask may be assigned by the core network (such as AIoF). In one embodiment, the mask may uniquely identify several devices. The mask may be a global mask. In one embodiment, the second identifier may also be filtering information indicating multiple devices that need to respond. In one example, the filtering information may be a portion of the device identifier of the device that needs to respond. In one implementation, the filtering information may be assigned by the core network (such as AIoF). In one embodiment, the filtering information may uniquely identify several devices. The filtering information may be global filtering information.

[0408] In one embodiment, the terms "group ID", "mask", and "filtering information" can be used interchangeably.

[0409] In one example, the fifth piece of information can be carried in the inventory request transfer message, and the fifth piece of information can also be described as the first identifier (device ID information).

[0410] In some embodiments, the second identification information may include two mandatory fields: one field indicating a first identification and the other field indicating a second identification. In one embodiment, if the field indicating the first identification takes a first value (e.g., 1), it means the second identification information indicates the first identification. Conversely, if the field indicating the first identification takes a second value (e.g., 0), it means the second identification information does not indicate the first identification. Similarly, in one embodiment, if the field indicating the second identification takes a first value (e.g., 1), it means the second identification information indicates the second identification. Conversely, if the field indicating the second identification takes a second value (e.g., 0), it means the second identification information does not indicate the second identification. Therefore, if the field indicating the first identification takes a first value (e.g., 1) and the field indicating the second identification takes a second value (e.g., 0), it means the second identification information indicates the first identification. Alternatively, if the field indicating the first identification takes a second value (e.g., 0) and the field indicating the second identification takes a first value (e.g., 1), it means the second identification information indicates the second identification. It should be noted that the values ​​of the field indicating the first identification and the field indicating the second identification cannot be the same.

[0411] In some embodiments, the second identification information may include two optional fields, one field indicating a first identification and the other field indicating a second identification. In one embodiment, if the second identification information includes a field indicating the first identification, then the second identification information indicates the first identification. In another embodiment, if the second identification information includes a field indicating the second identification, then the second identification information indicates the second identification. It should be noted that the values ​​of the field indicating the first identification and the field indicating the second identification cannot be simultaneously carried in the second identification information.

[0412] In some embodiments, if the first identifier appears, it indicates that the information subsequently sent by the third device is for a single device, namely the second device. In some embodiments, if the second identifier appears, it indicates that the information subsequently sent by the third device is for multiple devices, including the second device.

[0413] In some embodiments, the fifth information includes second identification information and identification type information. The third device uses the second identification information and identification type information to indicate to the first device whether subsequent information sent by the third device is for one device or multiple devices.

[0414] In some embodiments, the identifier type information is a first value, such as {full}, indicating that the second identifier information indicates the first identifier. In some embodiments, the identifier type information is a second value, such as {partial}, indicating that the second identifier information indicates the second identifier.

[0415] In some embodiments, the identifier type information is a first value, such as {group} or {multiple}, indicating that the second identifier information indicates a second identifier. In some embodiments, the identifier type information is a second value, such as {single}, indicating that the second identifier information indicates a first identifier.

[0416] It should be noted that the above is only an exemplary description of the fifth information, and the embodiments disclosed herein do not specifically limit the fifth information.

[0417] In some embodiments, the second identification information is the first identification.

[0418] In some embodiments, the fifth information may further include a service identifier for the second IoT service to initiate a new IoT service, thereby instructing the third device to continue sending information to the second device. In one example, the service identifier for the second IoT service may be a session ID, a transaction ID, or the like.

[0419] In some embodiments, if the fifth information instructs the third device to continue sending information to the second device, steps S2403 to S2408 are executed, as shown in Figures 2D and 2E. In this case, step S2409 is omitted.

[0420] In some embodiments, if the fifth information indicates that the third device should not continue sending information to the second device, steps S2405 to S2407 and S2409 are executed, as shown in FIG2F. In this case, steps S2403, S2404, and S2408 are omitted.

[0421] In step S2403, the first device determines to trigger the second device to perform non-contention-based random access.

[0422] In some embodiments, the first device sends a paging message. In some embodiments, the paging message may be sent by the first device, but is not limited to this, and may also be sent by other entities.

[0423] In some embodiments, the second device receives the paging message. In some embodiments, the paging message may be received by the second device, but is not limited thereto, and may also be received by other entities.

[0424] In some embodiments, the first device can determine whether to trigger the second device to perform non-contention-based random access or contention-based random access by paging messages, based on whether the second identification information in the fifth information is a device identifier or a second identifier. In one embodiment, the second identification information is a device identifier, and the first device determines to trigger the second device to perform non-contention-based random access.

[0425] In step S2404, the first device saves the context information of the second device.

[0426] The optional implementation of step S2404 can be found in the optional implementation of step S2301 in Figure 2C, as well as other related parts in the embodiments involved in Figure 2C, which will not be repeated here.

[0427] In some embodiments, step S2404 is omitted when the context information of the second device is deleted, as shown in FIG2E.

[0428] In step S2405, the third device deletes the context information of the second device.

[0429] The optional implementation of step S2405 can be found in the optional implementation of step S2101 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0430] In step S2406, the first device deletes the context information of the second device.

[0431] The optional implementation of step S2406 can be found in the optional implementation of step S2103 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0432] In some embodiments, steps S2405 and S2406 are omitted while retaining the context information of the second device. In this case, see Figure 2D.

[0433] In some embodiments, whether to retain the context information of the second device can be determined by the third device and notified to the first device, or it can be stipulated by the protocol, or the first device can determine and notify the third device based on its own capabilities. This disclosure does not specifically limit this.

[0434] In step S2407, the first device sends a paging message to the second device.

[0435] The optional implementation of step S2407 can be found in the optional implementation of step S2302 in Figure 2C, as well as other related parts in the embodiments involved in Figure 2C, which will not be repeated here.

[0436] In step S2408, the second device performs non-contention-based random access.

[0437] The optional implementation of step S2408 can be found in the optional implementation of step S2303 in Figure 2C, as well as other related parts in the embodiments involved in Figure 2C, which will not be repeated here.

[0438] In step S2409, the second device deletes the third information.

[0439] In some embodiments, after receiving a paging message, the second device determines that the second information transmission failed, and the process corresponding to the second information ends. At this time, the response to the second information, i.e., the third information, is invalid. The second device deletes the third information.

[0440] In some embodiments, the third information deleted by the second device may be third information stored locally on the second device, i.e., a response to the second information. This third information may be the complete response from the third device to the second device, or it may be a segmented response from the third device to the second device. In some embodiments, the third information stored locally on the second device may be third information that the second device did not send to the first device.

[0441] In some embodiments, the first device may also explicitly indicate to the second device that the second information transmission failed. In this case, the first information serves as an end marker. Therefore, after step S2103, the first device sends an end marker to the second device to indicate that the second information transmission failed and the process corresponding to the second information has ended. The second device deletes the third information after receiving the end marker.

[0442] Thus, the communication method involved in the embodiments of this disclosure is achieved through the above steps S2401 to S2409.

[0443] Figures 2G and 2H are exemplary interactive schematic diagrams illustrating a communication method according to embodiments of the present disclosure. As shown in Figures 2G and 2H, embodiments of the present disclosure relate to a communication method executed by the aforementioned A-IoT system. In one example, the communication method includes steps S2501 to S2508.

[0444] In some embodiments, if the second information transmission fails, steps S2101 to S2108 may be performed.

[0445] In some embodiments, if the reception of the third information fails, steps S2101 to S2108 may be performed.

[0446] In some embodiments, if the second device does not receive the second information, steps S2101 to S2108 may be performed.

[0447] In some embodiments, if the third device does not receive the third information, steps S2101 to S2108 may be executed.

[0448] It should be noted that the terms "failed to send second information", "failed to receive third information", "second device did not receive second information", and "third device did not receive third information" are interchangeable.

[0449] In some embodiments, the second information described above can be understood as information sent from the first device or the third device to the second device, such as a command or a message. In one example, when the second information is sent from the first device to the second device, the second information can be referred to as reader-to-device (R2D) information. In some embodiments, the third information described above can be understood as information sent from the second device to the first device or the third device, and the response is a response to the aforementioned information, such as a command response or a message response. In one example, when the third information is sent from the second device to the first device, the third information can be referred to as device-to-reader (D2R) information.

[0450] In some embodiments, the second information may be the entirety of the information sent by the first device or the third device to the second device, or it may be a segment of the information sent by the first device or the third device to the second device.

[0451] In some embodiments, the third information may be the entirety of the response sent by the second device to the first or third device, or it may be a segment of the response sent by the second device to the first or third device.

[0452] In some embodiments, the information sent by the first device or the third device may be associated with a second service identifier. In one embodiment, the second information includes the second service identifier. In one example, the second service identifier may be a session ID of the first IoT service or a transaction ID of the first IoT service.

[0453] In step S2501, the first device sends fourth information to the third device.

[0454] The optional implementation of step S2501 can be found in the optional implementation of step S2101 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0455] In step S2502, the third device sends the fifth information to the first device.

[0456] In some embodiments, the third device sends the fifth information. In some embodiments, the fifth information may be sent by the first device, but is not limited thereto, and may also be sent by other entities.

[0457] In some embodiments, the first device receives the fifth information. In some embodiments, the fifth information may be received by the first device, but is not limited thereto, and may also be received by other entities.

[0458] In some embodiments, after receiving the fourth information, the third device can determine, based on service requirements, whether there is information that needs to be sent to the second device. If so, the third device determines to continue sending information to the second device; otherwise, it determines not to continue sending information to the second device. Then, the third device sends a fifth message to the first device to indicate whether to continue sending information to the second device.

[0459] In some embodiments, the fifth information is used to instruct the third device to continue sending information to the second device. In this case, the first device may send a paging message to the second device. Here, the first information is a paging message. In some embodiments, the fifth information is used to trigger the first device to send a paging message to the second device, and the first information is used to trigger the second device to perform random access. In one embodiment, if the third device needs to continue sending information to the second device, the third device may send the fifth information to the first device to trigger the first device to send a paging message to the second device, causing the second device to perform random access. In one embodiment, the fifth information may be a service request message.

[0460] In some embodiments, the fifth information further uses the first device to determine whether subsequent information sent by the third device is addressed to one device or multiple devices. In some embodiments, the fifth information includes at least one of the following: second identification information and identification type information. The second identification information is used to indicate at least one device that needs to respond to the paging message, the at least one device including the second device. The identification type information is used to indicate the type of the second identification information.

[0461] In some embodiments, the fifth information includes second identification information, through which the third device indicates to the first device whether the information subsequently sent by the third device is for one device or multiple devices.

[0462] In some embodiments, the second identification information can be the first identification. In this case, the second identification information indicates a device that needs to respond to the paging message, i.e., the second device. In one example, the first identification can be a temporary identifier (temp-ID), tag identifier (TID), electronic product code (EPC), etc.

[0463] In some embodiments, the second identification information may be a second identifier. In this case, the second identification information indicates a group of devices, i.e., multiple devices, that need to respond to the paging message. In one embodiment, the second identifier may be a group ID of the device group. In one embodiment, the second identifier may also be a mask indicating multiple devices that need to respond. In one example, the mask may be a portion of the device identifier of the device that needs to respond. In one implementation, the mask may be assigned by the core network (such as AIoF). In one embodiment, the mask may uniquely identify several devices. The mask may be a global mask. In one embodiment, the second identifier may also be filtering information indicating multiple devices that need to respond. In one example, the filtering information may be a portion of the device identifier of the device that needs to respond. In one implementation, the filtering information may be assigned by the core network (such as AIoF). In one embodiment, the filtering information may uniquely identify several devices. The filtering information may be global filtering information.

[0464] In one embodiment, the terms "group ID", "mask", and "filtering information" can be used interchangeably.

[0465] In one example, the fifth piece of information can be carried in the inventory request transfer message, and the fifth piece of information can also be described as the first identifier (device ID information).

[0466] In some embodiments, the second identification information may include two mandatory fields: one field indicating a first identification and the other field indicating a second identification. In one embodiment, if the field indicating the first identification takes a first value (e.g., 1), it means the second identification information indicates the first identification. Conversely, if the field indicating the first identification takes a second value (e.g., 0), it means the second identification information does not indicate the first identification. Similarly, in one embodiment, if the field indicating the second identification takes a first value (e.g., 1), it means the second identification information indicates the second identification. Conversely, if the field indicating the second identification takes a second value (e.g., 0), it means the second identification information does not indicate the second identification. Therefore, if the field indicating the first identification takes a first value (e.g., 1) and the field indicating the second identification takes a second value (e.g., 0), it means the second identification information indicates the first identification. Alternatively, if the field indicating the first identification takes a second value (e.g., 0) and the field indicating the second identification takes a first value (e.g., 1), it means the second identification information indicates the second identification. It should be noted that the values ​​of the field indicating the first identification and the field indicating the second identification cannot be the same.

[0467] In some embodiments, the second identification information may include two optional fields, one field indicating a first identification and the other field indicating a second identification. In one embodiment, if the second identification information includes a field indicating the first identification, then the second identification information indicates the first identification. In another embodiment, if the second identification information includes a field indicating the second identification, then the second identification information indicates the second identification. It should be noted that the values ​​of the field indicating the first identification and the field indicating the second identification cannot be simultaneously carried in the second identification information.

[0468] In some embodiments, if the first identifier appears, it indicates that the information subsequently sent by the third device is for a single device, namely the second device. In some embodiments, if the second identifier appears, it indicates that the information subsequently sent by the third device is for multiple devices, including the second device.

[0469] In some embodiments, the fifth information includes second identification information and identification type information. The third device uses the second identification information and identification type information to indicate to the first device whether subsequent information sent by the third device is for one device or multiple devices.

[0470] In some embodiments, the identifier type information is a first value, such as {full}, indicating that the second identifier information indicates the first identifier. In some embodiments, the identifier type information is a second value, such as {partial}, indicating that the second identifier information indicates the second identifier.

[0471] In some embodiments, the identifier type information is a first value, such as {group} or {multiple}, indicating that the second identifier information indicates a second identifier. In some embodiments, the identifier type information is a second value, such as {single}, indicating that the second identifier information indicates a first identifier.

[0472] It should be noted that the above is only an exemplary description of the fifth information, and the embodiments disclosed herein do not specifically limit the fifth information.

[0473] In some embodiments, the second identification information is a second identifier.

[0474] In some embodiments, the fifth information may further include a service identifier for the second IoT service to initiate a new IoT service, thereby instructing the third device to continue sending information to the second device. In one example, the service identifier for the second IoT service may be a session ID, a transaction ID, or the like.

[0475] In some embodiments, if the fifth information instructs the third device to continue sending information to the second device, steps S2503 to S2509 are executed, see FIG2G.

[0476] In some embodiments, if the fifth information indicates that the third device should not continue sending information to the second device, steps S2504 to S2507 are executed, as shown in FIG2H. In this case, steps S2503, S2508, and S2509 are omitted.

[0477] In step S2503, the first device determines that it will trigger the second device to perform contention-based random access.

[0478] In some embodiments, the first device sends a paging message. In some embodiments, the paging message may be sent by the first device, but is not limited to this, and may also be sent by other entities.

[0479] In some embodiments, the second device receives the paging message. In some embodiments, the paging message may be received by the second device, but is not limited thereto, and may also be received by other entities.

[0480] In some embodiments, the first device can determine whether to trigger the second device to perform non-contention-based random access or contention-based random access by means of a paging message, based on whether the second identification information in the fifth information is a device identifier or a second identifier. In one embodiment, the second identification information is a second identifier, and the first device determines to trigger the second device to perform contention-based random access.

[0481] In step S2504, the third device deletes the context information of the second device.

[0482] The optional implementation of step S2504 can be found in the optional implementation of step S2102 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0483] In step S2505, the first device deletes the context information of the second device.

[0484] The optional implementation of step S2505 can be found in the optional implementation of step S2103 in Figure 2A, as well as other related parts in the embodiments involved in Figure 2A, which will not be repeated here.

[0485] In step S2506, the first device sends a NACK message to the second device.

[0486] The optional implementation of step S2506 can be found in the optional implementation of step S2204 in Figure 2B, as well as other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0487] In step S2507, the second device deletes the third information.

[0488] The optional implementation of step S2507 can be found in the optional implementation of step S2205 in Figure 2B, as well as other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0489] In step S2508, the first device sends a paging message to the second device.

[0490] The optional implementation of step S2508 can be found in the optional implementation of step S2207 in Figure 2B, as well as other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0491] In step S2509, the second device performs contention-based random access.

[0492] The optional implementation of step S2509 can be found in the optional implementation of step S2208 in Figure 2B, as well as other related parts in the embodiments involved in Figure 2B, which will not be repeated here.

[0493] In this embodiment, the first device sends first information to the second device to trigger the second device to perform random access and / or delete third information if the second device fails to send second information. This avoids waiting time for the second device due to uncertainty about subsequent operations, significantly reducing communication latency and improving communication efficiency. Furthermore, the first information can trigger the second device to resynchronize with the first device, thereby resuming data transmission, and / or trigger the second device to delete invalid information, thereby releasing system resources, thus improving the communication efficiency of IoT devices.

[0494] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0495] In some embodiments, the terms “radio”, “wireless”, “radio access network (RAN)”, “access network (AN)”, and “RAN-based” can be used interchangeably.

[0496] In some embodiments, “get,” “obtain,” “receive,” “transmit,” “bidirectional transmission,” and “send and / or receive” can be used interchangeably and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining through self-processing, or autonomous implementation, among other meanings.

[0497] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.

[0498] In some embodiments, terms such as "certain", "preset", "default", "set", "indicated", "a certain", "any", and "first" can be used interchangeably. "Certain A", "preset A", "default A", "set A", "indicated A", "a certain A", "any A", and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.

[0499] In some embodiments, the terms “wireless resource”, “wireless bearer”, “bearer”, “DRB”, “RLC bearer”, and “logical channel” can be used interchangeably.

[0500] In some embodiments, terms such as “current,” “latest,” “applied,” and “used” may be used interchangeably, but are not limited thereto.

[0501] In some embodiments, terms such as “bearer configuration information”, “bearer configuration”, “bearer configuration information”, and “bearer configuration” can be used interchangeably, but are not limited thereto.

[0502] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value), but is not limited thereto.

[0503] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0504] Figure 3A is an interactive schematic diagram of a communication method provided according to an embodiment of the present disclosure. The communication method involved in this embodiment can be applied to a communication system 100. As shown in Figure 3A, the communication method of this embodiment includes steps S3101 to S3102.

[0505] In step S3101, the first device sends first information to the second device.

[0506] The optional implementations of step S3101 can be found in the optional implementations of step S2105 in Figure 2A, step S2204 in Figure 2B, step S2302 in Figure 2C, step S2407 in Figure 2D, step S2506 in Figure 2E, and other related parts in the embodiments involved in Figures 2A, 2B, 2C, 2D and 2E, which will not be repeated here.

[0507] In step S3102, the second device deletes the third information and / or performs random access based on the first information.

[0508] Optional implementations of step S3102 can be found in the optional implementations of step S2106 in Figure 2A, step S2205 in Figure 2B, step S2303 in Figure 2C, step S2408 in Figure 2D, step S2409 in Figure 2D, step S2507 in Figure 2E, and other related parts in the embodiments involved in Figures 2A, 2B, 2C, 2D, and 2E, which will not be repeated here.

[0509] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0510] Figure 3B is an interactive schematic diagram of a communication method provided according to an embodiment of the present disclosure. The communication method involved in this embodiment can be applied to a communication system 100. As shown in Figure 3B, the communication method of this embodiment includes step S3201.

[0511] In step S3201, the first device sends fourth information to the third device.

[0512] The optional implementations of step S3201 can be found in the optional implementations of step S2101 in Figure 2A, step S2201 in Figure 2B, step S2401 in Figure 2D, step S2501 in Figure 2E, and other related parts in the embodiments involved in Figures 2A, 2B, 2D and 2E, which will not be repeated here.

[0513] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0514] In the following, the technical solutions of the embodiments of this disclosure will be described by way of specific implementation.

[0515] In some embodiments, Scheme 1 is provided: the reader (such as the first device) decides to end the process, informs the AIoTF (such as the third device) to delete the context of the device (such as the second device), and triggers the device to delete the saved message command response, or the message command response segment.

[0516] In one embodiment, if the Reader fails to send a command to the device (i.e., does not receive a response or a segmented response from the device), and if the Reader wants to stop operating on the device:

[0517] Step 1: The reader sends a message to AIoTF through the connection corresponding to the device, for example, carrying the same NG AP ID, AS ID, or device ID, indicating that the command sent to the device failed.

[0518] Step 2: Both the reader and AIoTF delete the device context, including the NG AP ID, AS ID, and stored device ID, commands, received response segments, etc.

[0519] Step 3: The reader informs the device that the process is over either implicitly (e.g., by carrying a new business identifier in paging) or explicitly (e.g., by an end identifier).

[0520] Step 4: After the process is completed, the device deletes any unsent command message responses or segments of the command message responses.

[0521] Step 5: If the AIoTF wants to continue sending command messages to this device, the AIoTF needs to resend the trigger message, carrying a new service identifier, or send only the device's ID to prompt the reader to trigger the device to access via CFRA.

[0522] In some embodiments, a second approach is provided: the reader informs the AIOTF process of failure, deletes the device's context, and triggers the device to reconnect to the network.

[0523] In one embodiment, if the Reader fails to send a command to the device (i.e., does not receive a response or a segmented response from the device), and if the Reader wants to stop operating on the device:

[0524] Step 1: The reader sends a message to AIOTF through the connection corresponding to the device, for example, carrying the same NG AP ID, AS ID, or device ID, indicating that the command sent to that device failed.

[0525] Step 2: Both the reader and AIoTF delete the device context, including the NG AP ID, AS ID, and stored device ID, commands, received response segments, etc.

[0526] Step 3: The reader sends a NACK to the device, triggering the device to reconnect to the network. The device deletes any incomplete command message responses or segments the command message responses.

[0527] In one embodiment, the order of steps 1 / 2 and 3 may be interchanged.

[0528] Step 4: When the device receives a subsequent trigger message, such as paging, carrying the same service identifier, the device re-initiates the access; or when the device receives a new trigger message, such as paging, carrying a different service identifier and the paging ID is specific to the device, the device re-initiates the access.

[0529] Step 5: After the reader receives the device ID, it forwards it to AIoTF and establishes a context for that device with AIoTF, such as NG AP ID and AS ID.

[0530] Step 6: AIoTF sends a command message to the reader.

[0531] Step 7: The reader sends a command message to the device.

[0532] Step 8: The device sends a command message response to the reader.

[0533] Step 9: After the reader receives the command message response from the device, it sends the command message response for that device to AIoTF.

[0534] In some embodiments, a third option is provided: the reader retains the device's context and commands, and triggers the device to reconnect via CFRA.

[0535] In one embodiment, if the reader fails to send a command to the device (i.e., does not receive a response or a segmented response from the device), and if the reader wants to stop operating on the device:

[0536] Step 1: The reader retains the device's context and the command messages received from the reader.

[0537] Step 2: The reader sends a trigger message, such as paging, carrying the device ID and / or the same service identifier.

[0538] Step 3: When the device receives the trigger message, it accesses the reader through non-contention, that is, it directly sends the device ID to the reader.

[0539] Step 4: After the reader receives the device ID, it will continue to send the command message for that device to the device.

[0540] Step 5: The device sends a command message response to the reader.

[0541] Step 6: After the reader receives the command message response from the device, it sends the command message response for that device to the AIoTF.

[0542] In some embodiments, Option 4 is provided: the reader informs AIoTF of the process failure, and AIoTF decides how to handle the device, such as re-triggering the device's individual access, accessing it through a group, or ignoring the device.

[0543] In one embodiment, if the reader fails to send a command to the device (i.e., does not receive a response or a segmented response from the device), and if the reader wants to stop operating on the device:

[0544] Step 1: The reader sends a message to AIOTF through the connection corresponding to the device, for example, carrying the same NG AP ID, AS ID, or device ID, indicating that the command sent to that device failed.

[0545] Step 2: AIoTF determines whether to continue sending messages to the device.

[0546] In one embodiment, if the AIoTF decides to continue sending messages to the device, the AIoTF informs the reader that it wishes to continue sending messages to the device.

[0547] In one example, if AIoTF sends a group paging ID to the reader, the reader will select the CBRA procedure, and steps 2 through 9 of Scheme 2 will be executed.

[0548] In one example, if AIoTF sends the device's paging ID to the reader, the reader will select CFRA. If the context is to be preserved, AIoTF sends the device's paging ID to the reader, and the reader triggers the device to perform CFRA. See steps 1 to 6 of Scheme 3.

[0549] In one example, if CFRA is selected, the following actions are performed if the context is not preserved:

[0550] Step 1: AIoTF sends the device's paging ID to the reader; both the reader and AIoTF delete the device's context, including the NG AP ID, AS ID, and stored device ID, commands, received response segments, etc.

[0551] Step 2: The reader sends a trigger message, such as paging, carrying the device ID and / or the same service identifier.

[0552] Step 3: When the device receives the trigger message, it accesses the reader through non-contention, that is, it directly sends the device ID to the reader;

[0553] Step 4: After the reader receives the device ID, it forwards it to AIoTF and establishes a context for that device with AIoTF, such as NG AP ID and AS ID.

[0554] Step 5: AIoTF sends a command message to the reader.

[0555] Step 6: The reader sends a command message to the device.

[0556] Step 7: The device sends a command message response to the reader.

[0557] Step 8: After the reader receives the command message response from the device, it sends the command message response for that device to the AIoTF.

[0558] In one embodiment, if AIoTF decides to ignore messages sent by the device, AIoTF instructs the reader to delete the device's context:

[0559] Step 1: Both the reader and AIoTF delete the device context, including the NG AP ID, AS ID, and stored device ID, commands, received response segments, etc.

[0560] Step 2: The reader informs the device that the process is over either implicitly (e.g., by carrying a new service identifier in paging) or explicitly (e.g., by an end identifier). Once the device is aware that the process is over, it deletes any unsent command message responses or segments the command message responses.

[0561] In one embodiment, in scheme four, the reader determines, either explicitly or implicitly, whether the Device ID sent by AIOTF is for a single device or a group of devices.

[0562] The current progress of RAN3 is as follows:

[0563] 9.3.x.1 Inventory Request Transfer

[0564] This IE provides information related to inventory requests from the AIOTF to the NG-RAN node.

[0565] In indirect communication, this IE is transparent to the AMF.

[0566] See Table 1 below:

[0567] Table 1

[0568] The reader needs to determine whether the Device ID is for a single user or a group of users based on the AIoTF information. If it's for a group of users, then CBRA needs to be used. If it's for a single user, then CFRA is used.

[0569] In some embodiments, the Device ID is determined implicitly whether it is for a single user or a group of users.

[0570] In one embodiment, when constructing the Device Paging ID, AIoTF divides it into the ID itself and mask or filter information. If the ID carries mask or filter information, it indicates that it is for a group of users; if it does not carry mask or filter information, it indicates that it is for a single user.

[0571] In some embodiments, AIoTF includes A-IoT Device Identification information in the Inventory Request Transfer IE sent to the base station, and the base station performs A-IoT inventory based on the Device Identification information (e.g., determining whether to perform CBRA or CFRA).

[0572] In some embodiments, the A-IoT device identification information includes a choice structure (i.e., either a Device ID or a group ID), where the IE represents the Requested Identity of the A-IoT device(s), as shown in the following example:

[0573] Table 2: A-IoT Device Identification

[0574] In one embodiment, Group ID can be understood as MASK ID or filter information.

[0575] In one embodiment, the presence of a Device ID indicates that the device is for a single user, while the presence of a GroupID or filter information indicates that the device is for a group of users.

[0576] In some embodiments, the AIoT device identification information includes two optional pieces of information. This IE represents the Requested Identity of the A-IoT device(s), as shown in the table below:

[0577] Table 3: A-IoT Device Identification

[0578] In one embodiment, the presence of a Device ID indicates that the device is for a single user, while the presence of a GroupID or filter information indicates that the device is for a group of users.

[0579] In some embodiments, the display indicates whether the Device ID is for a single user or a group of users.

[0580] In one embodiment, when sending the device paging ID, the AIoTF simultaneously sends whether it is a full ID or a partial ID, for example, {full ID, partial ID}. If it is a full ID, it is for a single user; if it is a partial ID, it is for a group of users. Alternatively, when sending the device paging ID, the AIoTF simultaneously sends whether it is a single ID, multiple IDs, or a group of users, for example, {single, multiple, group}.

[0581] In one example, the table below shows an example of an AIoT device idengification requested IE, which represents the Requested Identity of the A-IoT device(s).

[0582] Table 4: A-IoT Device Identification

[0583] In one embodiment, if the Device ID type is included in the A-IoT Device Identification information, the base station or reader can determine whether to use CBRA or CFRA based on the device ID type.

[0584] In some embodiments, by specifying the handling of command transmission failures, content synchronization is enabled between the reader, AIoTF, and the device, thereby preventing the network from retaining invalid device contexts, preventing the device from retaining invalid command message responses, and enabling AIoTF to resend commands to the device.

[0585] In some embodiments, the reader sends a failure message to the AIoTF, triggering the deletion of the device's context and re-triggering the device to access the network via CBRA.

[0586] In some embodiments, the reader retains the device's context, re-triggers the device to access via CFRA, and sends the retained command messages to the device.

[0587] In some embodiments, the reader sends a failure message to the AIoTF, which then decides whether to continue sending messages to the device or ignore the device. If ignored, the reader explicitly or implicitly informs the device that the process has ended and triggers the device to delete any unsent response messages.

[0588] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0589] This disclosure also proposes an apparatus (also referred to as a communication device, etc.) for implementing any of the above methods. For example, this disclosure proposes an apparatus that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Furthermore, another apparatus is proposed that includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods.

[0590] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through a configuration file, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0591] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a central processing unit (CPU), microprocessor, graphics processing unit (GPU) (which can be understood as a type of microprocessor), or digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented as an application-specific integrated circuit (ASIC) or a programmable logic device (FPGA). In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), tensor processing unit (TPU), deep learning processing unit (DPU), etc.

[0592] Figure 4 is a schematic diagram of the structure of a communication device provided according to an embodiment of the present disclosure. As shown in Figure 4, the communication device 400 may include at least one of the following: a transceiver module 401 and a processing module 402.

[0593] In some embodiments, the communication device 400 may be a first device. In some embodiments, the transceiver module 401 is configured to: send first information to a second device, the first information indicating that the transmission of second information sent to the second device failed, and the first information is also used to trigger the second device to perform at least one of the following: perform random access; delete third information, the third information being a response to the second information. Optionally, the transceiver module 401 may be used to perform at least one of the communication steps such as sending and / or receiving performed by the first device in any of the above methods, which will not be elaborated here. Optionally, the processing module 402 may be used to perform at least one of the other steps performed by the first device in any of the above methods besides the communication steps such as sending and / or receiving, which will not be elaborated here.

[0594] In some embodiments, the communication device 400 may be a second device. In some embodiments, the transceiver module 401 is configured to receive first information sent by the first device, the first information indicating that the transmission of second information sent to the second device failed. Optionally, the transceiver module 401 is used to perform at least one of the communication steps such as sending and / or receiving performed by the second device in any of the above methods, which will not be elaborated here. In some embodiments, the processing module 402 is configured to perform at least one of the following based on the first information: perform random access; delete third information, the third information being a response to the second information. Optionally, the processing module 402 may be used to perform at least one of the other steps performed by the second device in any of the above methods besides the communication steps such as sending and / or receiving, which will not be elaborated here.

[0595] In some embodiments, the communication device 400 may be a third device. In some embodiments, the transceiver module 401 is configured to: receive fourth information sent by the first device, the fourth information indicating that the second information sent by the first device to the second device failed to be transmitted, the fourth information including first identification information associated with the second device. Optionally, the transceiver module 401 may be used to perform at least one of the communication steps such as sending and / or receiving performed by the third device in any of the above methods, which will not be elaborated here. Optionally, the processing module 402 may be used to perform at least one of the other steps performed by the third device in any of the above methods besides the communication steps such as sending and / or receiving, which will not be elaborated here.

[0596] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module. The transmitting and receiving modules may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver.

[0597] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module. Optionally, the processing module may be interchangeable with a processor.

[0598] In some embodiments, the storage module may optionally be interchanged with the memory.

[0599] Figure 5A is a schematic diagram of the structure of a communication device provided according to an embodiment of the present disclosure. The communication device 5100 may be at least one of a first node, a first access network node, and a first terminal, or it may be a chip, chip system, or processor that supports at least one of the first node, the first access network node, and the first terminal in implementing any of the above methods. The communication device 5100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0600] As shown in Figure 5A, the communication device 5100 includes one or more processors 5101. The processor 5101 can be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 5100 can be used to execute any of the above methods. Optionally, one or more processors 5101 can be used to invoke instructions to cause the communication device 5100 to execute any of the above methods.

[0601] In some embodiments, the communication device 5100 further includes one or more transceivers 5102. When the communication device 5100 includes one or more transceivers 5102, the transceiver 5102 performs at least one of the communication steps such as sending and / or receiving in the above-described method, and the processor 5101 performs at least one of the other steps. In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., can be used interchangeably; and the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.

[0602] In some embodiments, the communication device 5100 further includes one or more memories 5103 for storing data. Optionally, all or part of the memories 5103 may be located outside the communication device 5100. In optional embodiments, the communication device 5100 may include one or more interface circuits 5104. Optionally, the interface circuits 5104 are connected to the memories 5103 and can be used to receive data from the memories 5103 or other devices, and to send data to the memories 5103 or other devices. For example, the interface circuits 5104 can read data stored in the memories 5103 and send the data to the processor 5101.

[0603] The communication device 5100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 5100 described in this disclosure is not limited thereto, and the structure of the communication device 5100 may not be limited by FIG. 5A. The communication device may be a standalone device or a part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the IC collection may also include storage components for storing data and programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0604] Figure 5B is a schematic diagram of the structure of a chip provided according to an embodiment of the present disclosure. For cases where the communication device 5100 can be a chip or a chip system, please refer to the schematic diagram of the chip 5200 shown in Figure 5B, but it is not limited thereto.

[0605] Chip 5200 includes one or more processors 5201. Chip 5200 is used to perform any of the methods described above.

[0606] In some embodiments, chip 5200 further includes one or more interface circuits 5202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 5200 further includes one or more memories 5203 for storing data. Optionally, all or part of the memories 5203 may be located outside of chip 5200. Optionally, interface circuit 5202 is connected to memory 5203, and interface circuit 5202 can be used to receive data from memory 5203 or other devices, and interface circuit 5202 can be used to send data to memory 5203 or other devices. For example, interface circuit 5202 can read data stored in memory 5203 and send the data to processor 5201.

[0607] In some embodiments, the interface circuit 5202 performs at least one of the communication steps, such as sending and / or receiving, in the above-described method. For example, the interface circuit 5202 performing the communication steps, such as sending and / or receiving, in the above-described method means that the interface circuit 5202 performs data interaction between the processor 5201, the chip 5200, the memory 5203, or the transceiver device. In some embodiments, the processor 5201 performs at least one of the other steps.

[0608] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0609] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device 6100, cause the communication device 6100 to perform any of the methods described above. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0610] This disclosure also provides a program product that, when executed by a communication device 6100, causes the communication device 6100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0611] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.

Claims

1. A communication method, performed by a first device, the method comprising: Send the first message to the second device. Wherein, the first information is used to indicate that the second information failed to be sent, or the first information is used to indicate that the third information failed to be received, or the first information is used to indicate that the first device did not receive the third information; The first information is further used to trigger the second device to perform at least one of the following: perform random access; delete the third information, which is used in response to the second information.

2. The method according to claim 1, wherein, The method further includes: Send a fourth message to a third device, the fourth message being used to indicate that the second message failed to be sent, the fourth message being used to indicate that the third message failed to be received, or the fourth message being used to indicate that the first device did not receive the third message, the fourth message including a first identification information associated with the second device, the first identification information being used to identify the second device.

3. The method according to claim 2, wherein, The fourth piece of information is used to instruct the deletion of the context information of the second device.

4. The method according to claim 2, wherein, The method further includes: After sending the fourth information, the system receives a fifth information sent by the third device. The fifth information is used to indicate whether to continue communication with the second device. The first information is sent by the first device based on the fifth information.

5. The method according to claim 4, wherein, The fifth information includes second identification information; or, the fifth information includes second identification information and identification type information; wherein, the second identification information is used to indicate at least one device, the at least one device including the second device; and the identification type information is used to indicate the type of the second identification information.

6. The method according to claim 5, wherein, The type of the second identification information includes: a first identification or a second identification, wherein the first identification is used to indicate a device; and the second identification is used to indicate multiple devices.

7. The method according to claim 5 or 6, wherein, The fifth information is used to indicate continued communication with the second device; or, the fifth information is used by the first device to determine that it triggers the second device to perform contention-based random access; or, the fifth information is used by the first device to determine that it triggers the second device to perform non-contention-based random access.

8. The method according to claim 7, wherein, The identifier type information is used to indicate that the second identifier information is the second identifier, and the first information is used to trigger the second device to perform contention-based random access; or, the identifier type information is used to indicate that the second identifier information is the first identifier, and the first information is used to trigger the second device to perform non-contention-based random access.

9. The method according to claim 5 or 6, wherein, The fifth information is used to indicate that communication with the second device will not continue, and / or the fifth information is used by the first device to determine that it triggers the second device to delete the third information.

10. The method according to any one of claims 1 to 9, wherein, The method further includes: Delete the context information of the second device.

11. The method according to claim 10, wherein, The context information includes at least one of the following: The first identification information is used to identify the second device; The second information; The third piece of information.

12. The method according to any one of claims 1 to 11, wherein, The first information includes one of the following: The first service identifier is different from the second service identifier associated with the second information; Negative response message; End marker.

13. The method according to claim 12, wherein, The first information includes at least one of the following: The device identifier of the second device; The first service identifier; The second business identifier.

14. The method according to claim 12 or 13, wherein, The method further includes: Send a paging message to the second device, the paging message being sent by the first device after sending the first information; According to the paging message, the device identifier of the second device sent by the second device through random access is received.

15. The method according to claim 14, wherein, The method further includes: The identification information of the second device is sent to the third device, and the identification information of the second device is used to establish the context information of the second device.

16. The method of claim 14, wherein, The method further includes: The second information is sent to the second device based on the device identifier of the second device.

17. A communication method performed by a second device, the method comprising: Receive the first information sent by the first device. Wherein, the first information is used to indicate that the second information failed to be sent, or the first information is used to indicate that the third information failed to be received, or the first information is used to indicate that the first device did not receive the third information; Based on the first information, perform at least one of the following: Perform random access; Delete the third information, which is a response to the second information.

18. The method according to claim 17, wherein, The first information includes one of the following: The first service identifier is different from the second service identifier associated with the second information; Negative response message; End marker.

19. The method according to claim 18, wherein, The first information includes at least one of the following: The device identifier of the second device; The first service identifier; The second service identifier; The first service identifier is different from the second service identifier.

20. The method according to claim 18 or 19, wherein, The method further includes: Receive a paging message sent by the first device, wherein the paging message is sent by the first device after sending the first information; Based on the paging message, the device identifier of the second device is sent to the first device via random access.

21. The method according to claim 20, wherein, The device identifier of the second device is used by the first device to trigger the third device to establish the context information of the second device.

22. The method according to claim 20, wherein, The device identifier of the second device is used by the first device to send the second information.

23. A communication method performed by a third device, the method comprising: The device receives a fourth message sent by a first device. The fourth message indicates that the first device failed to send the second message, or that the first device failed to receive the third message. Alternatively, the fourth message indicates that the first device did not receive the third message. The fourth message includes a first identification information associated with the second device, which is used to identify the second device. The third message is a response to the second message.

24. The method according to claim 23, wherein, The method further includes: Based on the fourth information, delete the context information of the second device.

25. The method according to claim 24, wherein, The context information includes at least one of the following: The first identification information; The second information; The third piece of information.

26. The method according to claim 23, wherein, The method further includes: Based on the fourth information, a fifth information is sent to the first device. The fifth information is used to indicate whether to continue communication with the second device. The fifth information is used by the first device to send a first information. The first information is used to trigger the second device to perform at least one of the following: perform random access; delete the third information.

27. The method according to claim 26, wherein, The fifth information includes second identification information; or, the fifth information includes second identification information and identification type information; wherein, the second identification information is used to indicate at least one device, the at least one device including the second device; and the identification type information is used to indicate the type of the second identification information.

28. The method according to claim 27, wherein, The type of the second identification information includes: a first identification or a second identification, wherein the first identification is used to indicate a device; and the second identification is used to indicate multiple devices.

29. The method according to claim 27 or 28, wherein, The fifth information is used to indicate continued communication with the second device; or, the fifth information is used by the first device to determine that it triggers the second device to perform contention-based random access; or, the fifth information is used by the first device to determine that it triggers the second device to perform non-contention-based random access.

30. The method according to claim 29, wherein, The identifier type information is used to indicate that the second identifier information is the second identifier, and the first information is used to trigger the second device to perform contention-based random access; or, the identifier type information is used to indicate that the second identifier information is the first identifier, and the first information is used to trigger the second device to perform non-contention-based random access.

31. The method according to claim 27 or 28, wherein, The fifth information is used to indicate that communication with the second device will not continue; or, the fifth information is used by the first device to determine that it triggers the second device to delete the third information.

32. The method according to any one of claims 26 to 31, wherein, The first information includes one of the following: The first service identifier is different from the second service identifier associated with the second information; Negative response message; End marker.

33. The method according to claim 32, wherein, The first information includes at least one of the following: The device identifier of the second device; The first service identifier; The second business identifier.

34. The method according to claim 32 or 33, wherein, The method further includes: The device receives the identification information of the second device sent by the first device, wherein the identification information of the second device is sent to the first device by the second device through random access. Based on the identification information of the second device, establish the context information of the second device.

35. A communication method, wherein, The method includes: A first device sends a first message to a second device, the first message indicating that the second message transmission failed, or, the first message indicating that the third message reception failed, or, the first message indicating that the first device did not receive the third message. The first message also triggers the second device to perform at least one of the following: perform random access; delete the third message, the third message being a response to the second message; and / or, The first device sends a fourth message to the third device. The fourth message is used to indicate that the second message failed to be sent, or that the third message failed to be received, or that the first device did not receive the third message. The fourth message includes a first identification information associated with the second device, which is used to identify the second device.

36. A communication device, wherein, The communication device is used to perform the communication method as described in any one of claims 1 to 16, 17 to 22, and 23 to 34.

37. A communication system comprising a terminal and network equipment, wherein, The first device is configured to implement the communication method as described in any one of claims 1 to 16, the second device is configured to implement the communication method as described in any one of claims 17 to 22, and the third device is configured to implement the communication method as described in any one of claims 23 to 34.

38. A storage medium storing instructions, characterized in that, When the instructions are executed on the communication device, the communication device performs the communication method as described in any one of claims 1 to 16, 17 to 22, and 23 to 34.

39. A program product comprising at least one of a program and instructions, characterized in that, When at least one of the programs or instructions is executed by a communication device, it implements the communication method as described in any one of claims 1 to 16, 17 to 22, and 23 to 34.