Communication method and apparatus, and storage medium

Abstract

The present application provides a communication method and apparatus, and a storage medium, which enable an AIoT device to re-access when a reader fails to receive a message 1 sent by the AIoT device, so that the reader successfully receives the message 1. The method comprises: a first device acquires first information, wherein the first information is used for determining that a random access mode is contention-free random access; the first device receives a first message, wherein the first message is used for re-triggering the first device to access a second device, the first message comprises first identification information, the first identification information is used for identifying a first AIoT service on an AIoT interface, and the second device is a device triggering the first message; in response to the first message, the first device determines, on the basis of the first information, to re-access the second device; and the first device sends a second message to the second device, wherein the second message comprises second identification information, and the second identification information is used for identifying the first device.

Description

Communication methods, devices and storage media

[0001] This application claims priority to Chinese Patent Application No. 202510392365.1, filed on March 28, 2025, entitled "Communication Method, Apparatus and Storage Medium", the entire contents of which are incorporated herein by reference. Technical Field

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

[0003] The Ambient Internet of Things (AIoT) is based on cellular network communication infrastructure and consists of readers and passive / semi-passive / active AIoT devices. Its main functions include inventory management, command processing, location tracking, and sensor reporting. Typical application scenarios include logistics, warehousing, industrial manufacturing, identification, and environmental monitoring. Transmission from reader to device (R2D) can be called R2D transmission, and transmission from AIoT device to reader (D2R) can be called D2R transmission.

[0004] For inventory scenarios, the AIoT air interface process can include: the reader sends a paging message, triggering a random access by the AIoT devices that need to respond; the AIoT devices that successfully access the system send identification information, such as a device identifier (ID) or a temporary ID, to the reader. This identification information is used to identify the AIoT device. The random access method can include contention-based random access or contention-free random access.

[0005] In a disk storage scenario where a single AIoT device performs contention-free random access, how to enable the AIoT device to reconnect so that the reader can successfully receive message 1 (Msg1) sent by the AIoT device is an urgent problem to be solved. Summary of the Invention

[0006] This application provides a communication method, apparatus, and storage medium that can enable the AIoT device to reconnect when the reader fails to successfully receive message 1 sent by the AIoT device, so that the reader can successfully receive message 1.

[0007] In a first aspect, a communication method is provided, which can be applied to a first device, which can be an AIoT device or a module configured in an AIoT device, such as a processor, chip, chip system, circuit, etc.

[0008] The method includes: acquiring first information, the first information being used to determine that the random access method is contention-free random access; receiving a first message, the first message being used to re-trigger the first device to access the second device, the first message including first identification information, the first identification information being used to identify the first AIoT service on the AIoT interface, the first message being triggered by the second device; responding to the first message according to the first information, determining to re-access the second device; and sending a second message, the second message including second identification information, the second identification information being used to identify the first device.

[0009] The first message is the subsequent AIoT paging message, meaning that an AIoT paging message has already been transmitted before the first message. The second message is message 1 (Msg1) in the contention-free random access procedure. The first device sending the second message to the second device can be regarded as a D2R data transmission.

[0010] It is understandable that for the same AIoT service, such as the first AIoT service, when the first device fails to connect randomly, the second device can send the first message to re-trigger the first device to connect to the second device.

[0011] In this application, the first device can use a contention-free random access method to align with the second device based on the first information. In this way, when the first message is received, the first device can determine that it is the paged device, and then the first device can determine to reconnect to the second device so that the second device can successfully receive the second message, i.e. message 1 in the contention-free random access process.

[0012] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: receiving a third message, the third message being used to trigger the first device to access the second device, the third message including first identification information, and the third message being triggered by the second device; and in response to the third message, sending a fourth message, the fourth message including the second identification information. The fourth message may be, for example, message 1 in a contention-free random access procedure.

[0013] The third message is an AIoT paging message that precedes the first message. In other words, the first message is an AIoT paging message that follows the third message, and can be referred to as a subsequent AIoT paging message.

[0014] It is understandable that the first message includes the first identification information of the first AIoT service, and the third message also includes the first identification information of the first AIoT service. Since the first and third messages carry the same identification information of the same AIoT service, the first device will assume that it has responded to the third message to access the second device, or that it has executed the first AIoT service. Therefore, the first device does not respond to the first message. However, in reality, the second device did not successfully receive the fourth message. In this application, the first device can determine that the random access method is contention-free random access based on the indication of the first message. In this way, when receiving the first message, the first device can determine that the paging target of the first message is itself. Therefore, the first device can determine to reconnect to the second device.

[0015] Optionally, the third message includes a first portion of the identification information of the first device, and the fourth message includes a second portion of the identification information of the first device. Optionally, the first message includes a first portion of the identification information of the first device, and the second message includes a second portion of the identification information of the first device.

[0016] The first part of the identification information is, for example, a part of the device ID of the first device, and the second part of the information is, for example, the remaining part of the device ID of the first device, or the second part of the information is, for example, the complete device ID of the first device.

[0017] In conjunction with the first aspect, in some implementations of the first aspect, the first information is contained in the third or fifth message. The fifth message is another R2D message besides the third message; for example, the fifth message is an R2D trigger message, such as a QueryRep message.

[0018] In conjunction with the first aspect, in some implementations of the first aspect, the first information is an access opportunity, which is used to transmit the fourth message. Here, an access opportunity refers to a time-frequency domain resource.

[0019] Understandably, for contention-free random access, the second device configures one access opportunity for a single device that needs to respond, while for contention-based random access, the second device configures multiple access opportunities for multiple devices. Thus, contention-free random access and contention-based random access can be distinguished based on the number of access opportunities.

[0020] Secondly, a communication method is provided, which can be applied to a second device, which can be a reader or a module configured in the reader, such as a processor, chip, chip system, circuit, etc.

[0021] The method includes: sending first information, the first information being used to determine that the random access method is contention-free random access; sending a first message, the first message being used to re-trigger the first device to access the second device, the first message including first identification information, the first identification information being used to identify the first AIoT service on the AIoT interface; and receiving a second message, the second message including second identification information, the second identification information being used to identify the first device.

[0022] In this scenario, if the second device fails to receive the fourth message, it sends the first message to the first device. The fourth message is a response to the third message. The third message is used to trigger the first device to access the second device, and the fourth message includes the second identification information.

[0023] In this application, the first device can use a contention-free random access method to align with the second device based on the first information. In this way, when the first message is sent, the first device can determine that it is the paged device, and then the first device can determine to reconnect to the second device so that the second device can successfully receive the second message, i.e. message 1 in the contention-free random access process.

[0024] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes: sending a third message, the third message being used to trigger the first device to access the second device, the third message including first identification information; and receiving a fourth message, the fourth message including second identification information. The fourth message is message 1 in the contention-free random access procedure.

[0025] In conjunction with the second aspect, in some implementations of the second aspect, the first information is contained in the third or fifth message. The fifth message is another R2D message besides the third message; for example, the fifth message is an R2D trigger message, such as a QueryRep message.

[0026] In conjunction with the second aspect, in some implementations of the second aspect, the first information is an access opportunity, which is used to transmit the fourth message. Here, an access opportunity refers to a time-frequency domain resource.

[0027] It should be understood that the second aspect of this application corresponds to the technical solution of the first aspect of this application, and the beneficial effects achieved by each aspect and the corresponding feasible implementation are similar, and will not be repeated here.

[0028] Thirdly, a communication method is provided, which can be applied to a first device, which can be an AIoT device or a module configured in an AIoT device, such as a processor, chip, chip system, circuit, etc.

[0029] The method includes: receiving a third message, the third message being used to trigger a first device to access a second device, the third message including first identification information, the first identification information being used to identify a first AIoT service on an AIoT interface, the third message being triggered by the second device; responding to the third message, sending a fourth message, the fourth message including second identification information, the second identification information being used to identify the first device; receiving a first message, the first message being used again to trigger the first device to access the second device, the first message including the first identification information; obtaining second information, the second information instructing the first device to re-access the second device; and based on the second information, sending a second message, the second message including the second identification information.

[0030] The third message is an AIoT paging message, and the first message is an AIoT paging message transmitted after the third message, which can be called a subsequent AIoT paging message.

[0031] Understandably, for the same AIoT service, such as the first AIoT service, if the first device fails to connect randomly, the second device can send a first message to re-trigger the first device to connect to the second device. However, since the AIoT service is still the first AIoT service, the third message includes the first identification information of the first IoT service, and the first message also includes the first identification information of the first AIoT service. However, the first device believes it has already responded to the third message and connected to the second device, or has executed the first AIoT service; therefore, the first device does not respond to the first message. But in reality, the second device did not successfully receive the fourth message, meaning it did not successfully connect to the second device, or did not complete the first AIoT service.

[0032] If the second device fails to receive the fourth message, meaning the first device fails to connect to the second device, to prevent the first device from ignoring the first message, the first device can obtain second information from the second device. This second information instructs the first device to reconnect to the second device. This means the first device can ignore the first identification information carried in the first message and reconnect to the second device. Based on the instruction of the second information, the first device responds to the first message and reconnects to the second device, ensuring the second device successfully receives the second message, i.e., message 1 in the contention-free random access procedure.

[0033] In conjunction with the third aspect, in some implementations of the third aspect, the second information is included in the first message or the sixth message, wherein the sixth message may be transmitted later than the first message. The sixth message may be, for example, a message from the AIoT physical layer / layer 1, or a message from the AIoT medium access control (MAC) layer.

[0034] In conjunction with the third aspect, in some implementations of the third aspect, the second information is the medium access control element (MAC CE).

[0035] Fourthly, a communication method is provided, which can be applied to a second device, which can be a reader or a module configured in the reader, such as a processor, chip, chip system, circuit, etc.

[0036] The method includes: sending a third message, the third message being used to trigger a first device to access a second device, the third message including first identification information, the first identification information being used to identify a first AIoT service on an AIoT interface; if a fourth message is not successfully received, sending a first message, the first message being used to re-trigger the first device to access the second device, the first message including first identification information, the fourth message including second identification information, the second identification information being used to identify the first device; sending a second message, the second message instructing the first device to re-access the second device; and receiving a second message, the second message including second identification information.

[0037] The third message is an AIoT paging message, and the first message is an AIoT paging message transmitted after the third message, which can be called a subsequent AIoT paging message.

[0038] If the second device fails to receive the fourth message, meaning the first device fails to connect to the second device, the second device sends the first message to the first device to re-trigger the first device's connection. To prevent the first device from ignoring the first message, the second device can send a second message to the first device, instructing the first device to reconnect. This means the first device can ignore the first identifier information carried in the first message and reconnect. Then, based on the instruction of the second message, the first device responds to the first message and reconnects, ensuring the second device successfully receives the second message, i.e., message 1 in the contention-free random access procedure.

[0039] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the second information is included in the first message or the sixth message, wherein the sixth message may be transmitted later than the first message, and the sixth message may be, for example, a message from the AIoT physical layer / layer 1, or a message from the AIoT MAC layer.

[0040] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the second information is MAC CE.

[0041] It should be understood that the fourth aspect of this application corresponds to the technical solution of the third aspect of this application, and the beneficial effects achieved by each aspect and the corresponding feasible implementation are similar, so they will not be repeated here.

[0042] Fifthly, a communication method is provided, which can be applied to a first device, which can be an AIoT device or a module configured in an AIoT device, such as a processor, chip, chip system, circuit, etc.

[0043] The method includes: receiving a third message, the third message being used to trigger a first device to access a second device, the third message including first identification information, the first identification information being used to identify a first AIoT service on an AIoT interface, the third message being triggered by the second device; responding to the third message, sending a fourth message, the fourth message including second identification information, the second identification information being used to identify the first device; receiving a seventh message, the seventh message being used to re-trigger the first device to access the second device, the seventh message including third identification information, the third identification information being used to identify a second AIoT service on an AIoT interface, the third identification information being different from the first identification information; responding to the seventh message, sending an eighth message, the eighth message including the second identification information.

[0044] In this application, if the second device fails to receive the fourth message, the first device receives a seventh message, which is used to re-trigger the first device to access the second device. The seventh message includes a new identification information, namely a third identification information, which differs from the first identification information. The third identification information is used to make the first device understand that the seventh message is a new message used to trigger the first device to access the second device. This ensures that the first device does not ignore the first message, and thus can respond to the first message and re-access the second device, allowing the second device to successfully receive the second message, i.e., message 1 in the contention-free random access procedure.

[0045] The first AIoT service and the second AIoT service can be the same AIoT service initiated by the core network equipment, or they can be two AIoT services initiated by the core network equipment.

[0046] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the method further includes: receiving fourth identification information, the fourth identification information being used to identify the second AIoT service on the next generation (NG) interface, and the third identification information being determined based on the fourth identification information.

[0047] In this application, the first AIoT service and the second AIoT service are two separate AIoT services triggered by the core network equipment. That is, the core network equipment first initiates the first AIoT service, and if the first device fails to connect to the second device, i.e., the first AIoT service fails, the core network equipment initiates the second AIoT service.

[0048] Optionally, the third identification information is part of the fourth identification information.

[0049] Sixthly, a communication method is provided, which can be applied to a second device, which can be a reader or a module configured in the reader, such as a processor, chip, chip system, circuit, etc.

[0050] The method includes: sending a third message, which triggers a first device to access a second device, the third message including first identification information used to identify a first AIoT service on an AIoT interface; if a fourth message is not successfully received, sending a seventh message, which re-triggers the first device to access the second device, the seventh message including third identification information used to identify a second AIoT service on an AIoT interface, the third identification information being different from the first identification information; the fourth message including second identification information used to identify the first device; and receiving an eighth message, the eighth message including the second identification information.

[0051] In this application, if the second device fails to receive the fourth message, the second device sends a seventh message to the first device. The seventh message is used to re-trigger the first device's access to the second device. The seventh message includes a new identification information, namely a third identification information, which is different from the first identification information. The third identification information is used to make the first device understand that the seventh message is a new message used to trigger the first device's access to the second device. This ensures that the first device will not ignore the first message, and thus can respond to the first message and re-access the second device, allowing the second device to successfully receive the second message, i.e., message 1 in the contention-free random access procedure.

[0052] In conjunction with the sixth aspect, in some implementations of the sixth aspect, the method further includes: sending fourth identification information, which is used to identify the second AIoT service on the NG interface, and the third identification information is determined based on the fourth identification information.

[0053] In this application, the first AIoT service and the second AIoT service are two separate AIoT services triggered by the core network equipment. That is, the core network equipment first initiates the first AIoT service, and if the first device fails to connect to the second device, i.e., the first AIoT service fails, the core network equipment initiates the second AIoT service.

[0054] Optionally, the third identification information is part of the fourth identification information.

[0055] In a seventh aspect, a communication apparatus is provided for executing the method in any possible implementation of any of the above aspects. Specifically, the apparatus includes a module for executing the method in any possible implementation of any of the above aspects.

[0056] In one design, the device may include modules that perform the methods / operations / steps / actions described in any of the above aspects. These modules may be hardware circuits, software, or a combination of hardware circuits and software.

[0057] In another design, the device is a communication chip, which may include input circuitry or interface for transmitting information or data, and output circuitry or interface for receiving information or data.

[0058] In another design, the device is an AIoT device or reader, which may include a transmitter for sending information or data and a receiver for receiving information or data.

[0059] In another design, the device is used to perform the method in any of the possible implementations of any of the above aspects, and the device can be configured in an AIoT device or a reader / writer.

[0060] Eighthly, a communication device is provided, comprising at least one processor for calling and running a computer program from a memory, such that the device performs the method in any possible implementation of any of the preceding aspects.

[0061] Optionally, the device further includes a memory for storing instructions and data. The memory is coupled to the processor, which, when executing the instructions stored in the memory, can implement the methods described in the foregoing aspects.

[0062] Optionally, the device may also include a transmitter and a receiver, which may be separate or integrated together and referred to as a transceiver.

[0063] Ninthly, a computer program product is provided, the computer program product comprising: a computer program (also referred to as code or instructions), which, when the computer program is run, causes a computer to perform a method in any possible implementation of any of the above aspects.

[0064] In a tenth aspect, a computer-readable storage medium is provided that stores a computer program (also referred to as code or instructions) that, when run on a computer, causes the computer to perform the method in any possible implementation of any of the above aspects.

[0065] In one aspect, this application provides a chip system including at least one processor for supporting the implementation of the functions involved in any possible implementation of any of the above aspects, such as receiving or processing data involved in the above methods.

[0066] In one possible design, the chip system also includes a memory for storing program instructions and data, which may be located within or outside the processor.

[0067] Optionally, the chip system may consist of chips or may include chips and other discrete components.

[0068] In a twelfth aspect, this application provides a communication system including a first device for implementing the method described in the first aspect and any possible implementation thereof, and a second device for implementing the method described in the second aspect and any possible implementation thereof.

[0069] In a thirteenth aspect, this application provides a communication system including a first device for implementing the method described in the third aspect and any possible implementation thereof, and a second device for implementing the method described in the fourth aspect and any possible implementation thereof.

[0070] In a fourteenth aspect, this application provides a communication system including a first device for implementing the method described in the fifth aspect and any possible implementation thereof, and a second device for implementing the method described in the sixth aspect and any possible implementation thereof.

[0071] It should be understood that aspects seven to fourteen of this application correspond to the technical solutions of aspects one to six of this application, and the beneficial effects achieved by each aspect and the corresponding feasible implementation are similar, and will not be repeated here. Attached Figure Description

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

[0073] Figure 2 is a schematic diagram of the architecture of an O-RAN system;

[0074] Figure 3 is a schematic diagram of the AIoT air interface / AS process;

[0075] Figures 4A to 4E are schematic diagrams of the network architecture applicable to the embodiments of this application;

[0076] Figure 5 is a schematic diagram of the logical system architecture of Topology 1;

[0077] Figure 6 is a schematic diagram of the AIoT-related processes defined under Topology 1;

[0078] Figure 7 is a schematic diagram of the direct connection between AIoT RAN and AIoTF in Topology 1;

[0079] Figure 8 is a schematic diagram of the non-direct connection between AIoT RAN and AIoTF under Topology 1;

[0080] Figure 9 is a schematic diagram of the logical system architecture of Topology 2;

[0081] Figure 10 is a schematic diagram of a protocol stack corresponding to Topology 2;

[0082] Figure 11 is a schematic diagram of the direct connection between AIoT-enabled gNB and AIoTF in Topology 2;

[0083] Figure 12 is a schematic diagram of the non-direct connection between AIoT-enabled gNB and AIoTF under topology 2;

[0084] Figure 13 is a schematic diagram of another protocol stack corresponding to Topology 2;

[0085] Figure 14 is a schematic diagram of another protocol stack corresponding to Topology 2;

[0086] Figures 15, 16, and 17 are schematic flowcharts of the communication method provided in the embodiments of this application;

[0087] Figures 18 and 19 are schematic block diagrams of a communication device provided in an embodiment of this application. Detailed Implementation

[0088] Before introducing the technical solutions provided in the embodiments of this application, the following points should be made first.

[0089] First, in the embodiments shown below, the terms and English abbreviations, such as reader / writer, AIoT, paging message, etc., are exemplary examples given for ease of description and should not constitute any limitation on this application. This application does not preclude the possibility of defining other terms that can achieve the same or similar functions in existing or future agreements.

[0090] Second, in the embodiments shown below, the terms "first," "second," and various numerical designations are merely for descriptive convenience to distinguish identical or similar items with substantially the same function and purpose. For example, "first message" and "second message" are only used to distinguish different messages and do not limit their order, nor are they used to limit the scope of the embodiments of this application. Those skilled in the art will understand that the terms "first," "second," etc., do not limit the quantity or execution order, and that "first," "second," etc., are not necessarily different.

[0091] Third, "at least one" means one or more, while "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, and c can mean: a, or b, or c, or a and b, or a and c, or b and c, or a, b, and c, where a, b, and c can be single or multiple.

[0092] Fourth, in this application, "instruction" can include direct and indirect instructions, explicit and implicit instructions, and instructions used for determination. When describing certain instruction information to indicate A, it can be understood that the instruction information carries A, directly indicates A, or indirectly indicates A. In this application, the information indicated by the instruction information is called the information to be instructed. In specific implementation, there are many ways to indicate the information to be instructed, such as, but not limited to, directly indicating the information to be instructed, such as the information to be instructed itself or its index. It can also indirectly indicate the information to be instructed by indicating other information, where there is a correlation between the other information and the information to be instructed. It can also indicate only a part of the information to be instructed, while the other parts are known or pre-agreed upon. For example, the instruction of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various information, thereby reducing instruction overhead to some extent. Furthermore, the information to be instructed can be sent as a whole or divided into multiple sub-information to be sent separately, and the sending period and / or timing of these sub-information can be the same or different. This application does not limit the specific method of instruction. It is understood that, for the sender of the instruction information, the instruction information can be used to indicate the information to be indicated, and for the receiver of the instruction information, the instruction information can be used to determine the information to be indicated.

[0093] The information in this application is used to indicate one or more contents, or it may be replaced with the information indicating one or more contents, or the information including one or more contents.

[0094] Fifth, in this application, "when," "if," and "if" all refer to the device taking corresponding actions under certain objective circumstances, not to a time limit, nor do they require the device to perform a judgment action, nor do they imply any other limitations. Unless otherwise specified, "if" and "if" are interchangeable, and "when" and "under the circumstances" are interchangeable. "When" is interchangeable with "if" / "if."

[0095] Sixth, in this application, the words "exemplarily" or "for example" are used to indicate that they are examples, illustrations, or descriptions. Any embodiment or design that is described as "exemplarily" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design options. Specifically, the use of the words "exemplarily" or "for example" is intended to present the relevant concepts in a specific manner.

[0096] Seventh, "Sending information / data" only indicates the direction of information / data transmission, including direct transmission via the device's communication interface (such as an air interface). "Sending" can also be understood as the "output" of the module interface. "Sending" can include indirect transmission by the processing unit through the communication interface, that is, after the processing unit outputs information / data through the module interface, it is transmitted to the device's communication interface and then sent out. "Receiving information / data" only indicates the direction of information / data transmission, including direct reception via the communication interface. "Receiving" can also be understood as the "input" of the module interface. "Receiving information / data" can include indirect reception by the processing unit through the communication interface, that is, after the communication interface receives information / data, it is transmitted to the module interface of the processing unit and then input to the processing unit. "Sending information / data to… (such as a terminal device)" can be understood as the destination of the information being the terminal device. It can include sending information / data directly or indirectly to the terminal device. "Receiving information / data from… (such as a terminal device)" can be understood as the source of the information being the terminal device, and can include receiving information / data directly or indirectly from the terminal device. Information / data may undergo necessary processing, such as format changes, between the source and destination, but the destination can understand the valid information / data from the source. Similar statements in this application can be understood in a similar way, and will not be repeated here.

[0097] In other words, sending and receiving can occur between devices, such as between terminal devices and network devices; or they can occur within a device, such as between components, modules, chips, software modules, or hardware modules within a device via a bus, wiring, or interface.

[0098] Eighth, in this application, the solutions in each embodiment can be used in a reasonable combination, and the explanations or descriptions of various terms, similar operations, or steps appearing in the embodiments can be referenced or explained to each other in the various embodiments, without limitation.

[0099] Figure 1 is a schematic diagram of the architecture of a communication system 100 provided in an embodiment of this application. Figure 1 shows a schematic diagram of a possible, non-limiting system architecture. As shown in Figure 1, the communication system 100 includes a radio access network (RAN) 10 and a core network (CN) 20. Optionally, the communication system 100 also includes an Internet 30. The RAN 10 may include at least one access network device (110a and 110b in Figure 1) and at least one terminal (120a-120j in Figure 1). The terminal is wirelessly connected to the access network device, and the access network device is wirelessly or wiredly connected to the core network 20. The core network device and the access network device may be independent and different physical devices, or the functions of the core network device and the logical functions of the access network device may be integrated on the same physical device, or a single physical device may integrate some of the functions of the core network device and some of the functions of the access network device. Terminals and access network devices can be interconnected via wired or wireless means. Figure 1 is just a schematic diagram. The communication system may also include other access network devices, such as wireless relay devices and wireless backhaul devices, which are not shown in Figure 1.

[0100] The radio access network 10 can be a cellular system related to the 3rd generation partnership project (3GPP), such as a 4th generation (4G) mobile communication system (also known as a long term evolution (LTE) system), a 5th generation (5G) mobile communication system (also known as a NR system), or it can be applied to future mobile communication systems or other similar communication systems, without specific limitations. The radio access network 10 can also be an open radio access network (open RAN, O-RAN, or ORAN) or a cloud radio access network (CRAN). The radio access network 10 can also be a non-terrestrial network (NTN), a satellite communication network, a high altitude platform station (HAPS) communication network, an integrated access and backhaul (IAB) communication network, a reconfigurable intelligent surface (RIS) communication network, etc. The radio access network 10 can also be a communication system that integrates two or more of the above systems.

[0101] RAN nodes, also known as radio access network devices, RAN entities, or access nodes, are used to help terminals access a communication system wirelessly. Multiple RAN nodes in communication system 100 can be of the same type or different types.

[0102] In one possible scenario, a RAN node can be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next-generation NodeB (gNB) in 5G, a base station in a future mobile communication system, an access point (AP) in a satellite, an IAB node, or a RAN node in an NTN communication system; that is, it can be deployed on a high-altitude platform or a satellite. A RAN node can be a macro base station (as shown in Figure 1, 110a), a micro base station or indoor station (as shown in Figure 1, 110b), a relay node or donor node, or a radio controller in a CRAN scenario. A RAN node can also be a device that functions as a base station in device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, drone communication, or machine-to-machine (M2M) communication. Optionally, a RAN node can also be a server, wearable device, vehicle, or in-vehicle equipment. For example, in vehicle-to-everything (V2X) technology, the RAN node can be a roadside unit (RSU).

[0103] In another possible scenario, multiple RAN nodes collaborate to assist the terminal in achieving wireless access, with different RAN nodes implementing some of the base station's functions. For example, a RAN node can be a central unit (CU), a distributed unit (DU), or a radio unit (RU). Here, the CU performs the functions of the base station's radio resource control (RRC) protocol and packet data convergence protocol (PDCP), and can also perform the functions of the service data adaptation protocol (SDAP). The DU performs the functions of the base station's radio link control layer and MAC layer, and can also perform some or all of the physical layer functions. For specific descriptions of the above protocol layers, refer to the relevant 3GPP technical specifications. The RU can be used to implement radio frequency signal transmission and reception functions. The CU and DU can be two independent RAN nodes, or they can be integrated into the same RAN node, such as within a baseband unit (BBU). The RU can be included in radio frequency equipment, such as in a remote radio unit (RRU) or an active antenna unit (AAU). The CU can be further divided into two types of RAN nodes: CU-control plane (CP) and CU-user plane (UP).

[0104] In different systems, RAN nodes may have different names. For example, in an O-RAN system, a CU can be called an open CU (O-CU), a DU can be called an open DU (O-DU), and an RU can be called an open RU (O-RU). The RAN nodes in the embodiments of this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules. For example, a RAN node can be a server loaded with the corresponding software modules. The embodiments of this application do not limit the specific technology or device form used in the RAN nodes. For ease of description, a base station is used as an example of a RAN node in the following description.

[0105] A terminal is a device with wireless transceiver capabilities, capable of sending signals to or receiving signals from access network devices. Terminals can also be referred to as terminal devices, user equipment (UE), mobile stations, mobile terminals, etc. Terminal devices can be widely used in various scenarios, such as D2D, V2X communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, etc. Terminals can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, airplanes, ships, robots, robotic arms, smart home devices, etc. The embodiments of this application do not limit the specific technology or device form used in the terminal. The device used to implement the terminal's functions can be the terminal itself; it can also be a device capable of supporting the terminal in implementing these functions, such as a chip system. This device can be installed in the terminal or used in conjunction with the terminal. In the embodiments of this application, the chip system can consist of chips or include chips and other discrete components. All or part of the functions of the terminal in this application can also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (e.g., a cloud platform).

[0106] Access network devices and terminals can be fixed in location or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can be deployed on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of the access network devices and terminals.

[0107] The roles of access network devices and terminals can be relative. For example, the helicopter or drone 120i in Figure 1 can be configured as a mobile access network device. For terminals 120j that access the wireless access network 10 via 120i, terminal 120i is an access network device; however, for access network device 110a, 120i is a terminal, meaning that 110a and 120i communicate via a wireless air interface protocol. Of course, 110a and 120i can also communicate via an interface protocol between access network devices. In this case, relative to 110a, 120i is also an access network device. Therefore, access network devices and terminals can both be collectively referred to as communication devices. 110a and 110b in Figure 1 can be called communication devices with access network device functions, and 120a-120j in Figure 1 can be called communication devices with terminal functions.

[0108] Communication between access network devices and terminals, between access network devices, and between terminals can be conducted using licensed spectrum, unlicensed spectrum, or both simultaneously. Communication can be conducted using spectrum below 6 GHz, spectrum above 6 GHz, or both simultaneously. The embodiments of this application do not limit the spectrum resources used for wireless communication.

[0109] In the embodiments of this application, the functions of the access network device can be executed by modules (such as chips) within the access network device, or by a control subsystem that includes access network device functions. This control subsystem, including access network device functions, can be a control center in the aforementioned application scenarios such as smart grids, industrial control, intelligent transportation, and smart cities. Similarly, the functions of the terminal can be executed by modules (such as chips or modems) within the terminal, or by a device that includes terminal functions.

[0110] Core network equipment refers to the equipment in the core network that provides service support to terminals. Examples of some core network equipment include: access and mobility management function (AMF) network elements, session management function (SMF) network elements, user plane function (UPF) network elements, etc., which will not be listed here.

[0111] In this application, the access network device sends downlink signals or downlink information to the terminal, and the downlink signals or downlink information are carried on the downlink channel; the terminal sends uplink signals or uplink information to the access network device, and the uplink signals or uplink information are carried on the uplink channel. In order to communicate with the access network device, the terminal needs to establish a radio connection on a cell controlled by the access network device. The cell with which the terminal has established a radio connection is called the terminal's serving cell. When the terminal communicates with the serving cell, it may also be subject to interference from signals from neighboring cells.

[0112] In this application, the channel between the AIoT device and the reader can be referred to as the physical D2R channel (PDRCH), and the channel between the reader and the AIoT device can be referred to as the physical R2D channel (PRDCH). It is understood that PDRCH and PRDCH are merely examples of channels between the AIoT device and the reader, and between the reader and the AIoT device, respectively. In different systems and scenarios, other terms capable of achieving the same or similar functions may be defined in existing or future protocols, and the embodiments of this application do not limit this.

[0113] Figure 2 is a schematic diagram of an O-RAN system architecture. As shown in Figure 2, the O-RAN system may include more or fewer components in addition to those shown in Figure 2, and this application does not limit this. As shown in Figure 2, the O-RAN includes a BBU, and optionally, the O-RAN also includes an RU. The BBU communicates with the CN via a backhaul link, the BBU communicates with the RU via a fronthaul link, and the RU communicates with the terminal via an air interface. The BBU and RU may or may not be co-located.

[0114] The BBU includes at least one CU and at least one DU, wherein the at least one CU and the at least one DU communicate via at least one midhaul link.

[0115] In some examples, the CU is a logical node carrying the RCC layer, SDAP layer, PDCP layer, and other control functions of the access network equipment. The CU connects to network nodes such as the core network through interfaces, which may be interfaces such as the E2 interface. Optionally, the CU may have some core network functions. The CU (e.g., the PDCP layer and higher layers) connects to the DU (e.g., the radio link control (RLC) layer and lower layers) through interfaces, which may be interfaces such as the F1 interface. In some examples, these interfaces (e.g., the F1 interface) can provide control plane and user plane functions (e.g., interface management, system information management, UE context management, RRC message transmission, etc.). F1AP is the application protocol of the F1 interface, defining the F1 signaling procedures in some examples. The F1 interface supports control plane F1-C and user plane F1-U.

[0116] In some examples, the CU can be split into CU-CP and CU-UP. CU-CP is a logical node carrying the RRC layer and PDCP-C (control plane part of PDCP) layer, used to implement the CU's control plane functions. CU-CP can interact with network elements in the core network used to implement control plane functions. These network elements in the core network can be Access and Mobility Function (AMF) network elements, such as the AMF network element in a 5G system. The AMF network element is responsible for mobility management in the mobile network, such as terminal device location updates, terminal device registration with the network, and terminal device handover. CU-UP is a logical node carrying the SDAP layer and PDCP-U (user plane part of PDCP) layer, used to implement the CU's user plane functions. CU-UP can interact with network elements in the core network used to implement user plane functions. These network elements in the core network, such as the UPF in a 5G system, are responsible for data forwarding and receiving in terminal devices. The above CU and DU configurations are merely examples; the functions of CU and DU can be configured as needed. For example, a CU or DU can be configured to have more protocol layer functions, or it can be configured to have only some protocol layer processing functions. For instance, some RLC layer functions and protocol layer functions above the RLC layer can be placed in the CU, while the remaining RLC layer functions and protocol layer functions below the RLC layer can be placed in the DU. As another example, the functions of the CU or DU can be divided according to service type or other system requirements. For instance, based on latency, functions that need to meet low latency requirements can be placed in the DU, while functions that do not need to meet this latency requirement can be placed in the CU.

[0117] In some examples, the DU is a logical node that carries the RLC layer, MAC layer, higher physical (higher PHY) layer, and other functions. In some examples, the DU can control at least one RU. The DU connects to the RU through interfaces, which can be fronthaul interfaces. In some examples, the Higher PHY layer includes the PHY layer processing, such as forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation.

[0118] In some examples, the RU is a logical node that carries both the lower physical layer (lower PHY) and radio frequency (RF) processing. In some examples, the RU can be a TRP (Transmission Replication Platform), a remote radio head (RRH), or other similar entity. In some examples, the Low-PHY includes PHY processing functions such as Fast Fourier Transform (FFT), Inverse Fast Fourier Transform (IFFT), digital beamforming, and filtering. The RU communicates with one or more UEs via a radio link.

[0119] The DU and RU can be co-located or not. The DU and RU exchange control plane and user plane information via a lower-layer split C / U / S-Plane (LLS-CUS) interface through a fronthaul link. LLS-CUS may include LLS-C and LLS-U interfaces that provide the control plane (C-Plane) and user plane (U-Plane), respectively. In some examples, the control plane (C-Plane) refers to real-time control between the DU and RU. The DU and RU exchange management information via an LLS-M interface on the fronthaul link; the management plane (M-Plane) refers to non-real-time management operations between the DU and RU.

[0120] DU and RU can cooperate to implement the functions of the PHY layer. A DU can be connected to one or more RUs. The functions of DU and RU can be configured in various ways depending on the design. For example, a DU can be configured to implement baseband functions, and an RU can be configured to implement mid-RF functions. Another example is that a DU can be configured to implement higher-level functions in the PHY layer, and an RU can be configured to implement lower-level functions in the PHY layer, or to implement both lower-level and RF functions. Higher-level functions in the physical layer can include a portion of the physical layer's functions that are closer to the MAC layer, while lower-level functions in the physical layer can include another portion of the physical layer's functions that are closer to the mid-RF side.

[0121] For ease of understanding, the relevant technologies and concepts involved in this application are introduced below.

[0122] 1. Devices in IoT systems

[0123] Currently, IoT is receiving significant attention. For IoT scenarios, reducing device size and complexity is expected to increase the number of devices that can be accommodated in the IoT ecosystem. These IoT devices can include AIoT devices. For example, the peak power consumption of AIoT devices can range from 1μW to several hundred μW; the uplink signal of an AIoT device can be generated internally, or the AIoT device needs to perform backscattering based on an externally provided carrier wave to achieve uplink transmission. In some implementations, an AIoT device with a peak power consumption of approximately 1μW (referred to as device1) does not have uplink or downlink amplification capabilities; an AIoT device with a peak power consumption of several hundred μW (referred to as device2) has uplink and / or downlink amplification capabilities.

[0124] AIoT devices can perform business with corresponding devices. In this case, the AIoT device can be called an AIoT device. The corresponding device can be called a reader, such as a network device or a UE. Here, "device" can also be replaced with IoT devices such as UE, tag, or AIoT tag; and "reader" can also be replaced with network devices or UEs such as an interrogator.

[0125] A tag can also be called an electronic tag or a tag device. For example, a tag implemented through an AIoT device can also be called an AIoT tag. In this embodiment, the tag can communicate with network devices as a terminal device. Here, "tag" is just an optional name, and the name may change; for example, "AIoT tag" may be changed to other names. This embodiment does not limit the name. For ease of description, the term "tag" will continue to be used as an example below.

[0126] AIoT can be applied to a variety of scenarios. For example, in logistics and warehousing, tags (such as AIoT tags) can be used for inventory and tracking of goods, and to monitor the status of goods during transportation. In industrial manufacturing, tags can be used to monitor the status of the environment and equipment. Furthermore, AIoT can be considered for other consumer-facing businesses, such as managing user assets. By locating tags through inventory processes or other similar processes, users can determine whether their items are lost and in what area, thereby enabling AIoT-based item retrieval.

[0127] In AIoT, AIoT devices (such as tags) and readers can communicate, as shown in Figure 3. Through communication between the AIoT device and the reader, the AIoT device and the reader can perform at least one of the following operations: inventory operation, read operation, write operation, kill or disable operation, or lock operation.

[0128] AIoT technology can include network devices and first-type terminal devices, or, an AIoT-based communication system can include network devices and first-type terminal devices. The first-type terminal devices can be devices with AIoT terminal device functionality. In this case, both the reader / writer and the AIoT terminal device can be implemented based on cellular network infrastructure. In other words, both the reader / writer and the AIoT terminal device can be devices within a cellular network. The AIoT terminal device can also be referred to as an AIoT device.

[0129] For example, the functionality of a reader / writer can be implemented by network devices, such as base stations. AIoT terminal devices can be implemented by terminal devices in cellular networks, such as ultra-low power, ultra-low complexity IoT terminal devices, i.e., the first type of terminal devices. Network devices can perform contactless data communication with the first type of terminal devices, thereby reading information from the first type of terminal devices and / or writing information that needs to be stored into the first type of terminal devices. AIoT technology can be used to implement one or more of the following services: inventory, positioning, sensing, or command. It can be understood that command services can be services that implement write or lock processes. In terms of application scope, AIoT technology can be applied to scenarios such as logistics, warehousing, industrial manufacturing, identity recognition, or environmental monitoring.

[0130] The 3rd Generation Partnership Project (3GPP) plenary meeting defined an extremely low-power, low-complexity Internet of Things (IoT) technology, which can be understood as an extension of radio frequency identification (RFID) within 3GPP. While this IoT technology shares some principles with RFID, such as similar inventory management processes, it will introduce more value-added scenarios within 3GPP.

[0131] AIoT is based on cellular network communication infrastructure and consists of readers (such as base stations) and passive / semi-passive / active AIoT terminal devices (AIoT terminal devices are terminal devices in the cellular network, which can be understood as extremely low-power, extremely low-complexity IoT terminal devices). Its main functions include inventory management, positioning, sensing, or command functions, or one or more of these. Typical application scenarios include logistics, warehousing, industrial manufacturing, identity recognition, and environmental monitoring.

[0132] The following examples illustrate various AIoT services.

[0133] Inventory management involves using a reader (which can be a base station or a terminal) to connect A-IoT devices within the coverage area. Successfully connected AIoT devices need to send their unique identifier to the reader. Inventory management, also known as a checklist operation, is used to obtain the identifiers of AIoT devices.

[0134] Location services utilize positioning signals to pinpoint the location of AIoT devices.

[0135] In the sensing business, AIoT devices can report sensing data to the base station, such as temperature data.

[0136] Command operations can be a series of operational instructions. For example, command operations can include at least one of the following: read, write, disable, enable, kill, or lock operations.

[0137] The read function can read the electronic product code (EPC), tag identifier (TID) in the storage area of ​​the AIoT device, the content stored in the reserved area of ​​the AIoT device, or the content stored in the user storage area.

[0138] The write operation allows for writing to the storage area of ​​an AIoT device. For example, a base station can send a write command (or write request) and data, instructing the AIoT device to write the data into its storage area.

[0139] Disable service: Request AIoT devices to permanently or temporarily disable their radio frequency (RF) transmission capabilities.

[0140] Enable service, requesting the activation of temporarily disabled AIoT devices.

[0141] The kill function can make AIoT devices permanently unusable.

[0142] Locking services can lock the information of an AIoT device, preventing read or write operations on that device. Alternatively, locking services can also lock a storage area, preventing or allowing read or write operations on that storage area.

[0143] The above are just examples. AIoT devices and readers can also perform other services or operations, which will not be listed here.

[0144] In AIoT, AIoT devices can be divided into three categories: Device A, Device B, and Device C.

[0145] Device A (similar to a passive tag) has no energy storage, cannot generate signals independently, and can transmit signals using backscattering.

[0146] Device B (similar to a semi-passive tag) has energy storage but cannot generate signals independently. It can transmit signals using backscattering, and the energy stored in Device B can amplify the reflected signal.

[0147] Device C (similar to an active tag) has energy storage, can generate signals independently, and has active radio frequency components for transmission.

[0148] In addition, the RAN1#116 meeting further defined the following three categories of AIoT devices: Device 1, Device 2a, and Device 2b.

[0149] Device 1 has a peak power consumption of approximately 1 μW and features energy storage. Its initial sampling frequency offset (SFO) reaches 10 x ppm, and it cannot amplify downlink (DL) or uplink (UL) signals. It requires an external carrier signal for backscatter communication to enable uplink transmission.

[0150] Device 2a has a peak power consumption of less than or equal to several hundred μW, features energy storage, achieves an SFO of 10X ppm, and can amplify DL and / or UL signals. It requires an external carrier signal for backscatter communication to enable uplink transmission.

[0151] Device 2b has a peak power consumption of less than or equal to several hundred μW, features energy storage, achieves an SFO of 10X ppm, and can amplify DL and / or UL signals. The device can perform uplink transmission without relying on an externally provided carrier.

[0152] 3. AIoT Air Interface / Access Layer (AS) Process

[0153] The AIoT air interface / AS process is shown in Figure 3.

[0154] Step A: AIoT Paging. Based on the service request, the reader sends an AIoT paging message, indicating the AIoT device that needs to respond.

[0155] AIoT paging messages can be triggered by core network devices, such as AMF network elements, ambient IoT management function (AIoTMF) network elements, or ambient IoT function (AIoTF) network elements. For example, the core network device sends a first service request message or paging message to the access network device. The access network device confirms the first service request message or paging message and sends a first instruction message to the terminal device, instructing it to perform the first service.

[0156] Step B: D2R data transmission. The triggered AIoT device performs the transmission of the device ID via the AIoT random access procedure or without using the AIoT random access procedure (e.g., contention-free resolution).

[0157] Step C1: Possible R2D data transmission. For example, used to send commands, such as read, write, lock, deactivate, and sense commands.

[0158] Step C1: Possible D2R data transfer. For example, corresponding responses to commands, such as data read by a read command, or success / failure feedback for a write command.

[0159] It is understandable that the above process supports inventory and / or command application scenarios in the following ways:

[0160] For inventory-only applications, a possible baseline approach includes steps A and B as described above.

[0161] For inventory and command applications, a possible baseline approach includes steps A, B, C1, and C2 as described above.

[0162] For command-only application scenarios, a baseline solution with steps A, B, C1, and C2 can be used to support this scenario. Another candidate solution to support this scenario is as follows:

[0163] Step A': AIoT Paging. Based on the service request, the reader sends an AIoT paging message containing commands, instructing the AIoT device to process / respond to the commands.

[0164] Step C2: Perform possible D2R data transmission (e.g., device ID or corresponding response to a command) with or without the A-IoT random access procedure.

[0165] At the AS layer, AIoT paging messages are used to indicate which AIoT devices need to respond. An AIoT paging message can identify one or more AIoT devices included or associated with it. For example, an AIoT paging message may include the identifier of a single AIoT device; another example is that an AIoT paging message may include a group identifier mapped to multiple AIoT devices; yet another example is that an AIoT paging message does not contain the identifier of any AIoT device or AIoT device group, meaning the AIoT paging message instructs all AIoT devices that can receive it to respond to the AIoT paging message.

[0166] Optionally, AIoT paging messages can also indicate time-domain and / or frequency-domain resources used for D2R transmission.

[0167] Optionally, the paging function of AIoT devices can be understood as not supporting paging messages from NR, paging timing, and discontinuous reception (DRX). It can be assumed that AIoT devices can receive AIoT paging messages as long as they have sufficient power.

[0168] In this application, the paging message / indication can be equivalently replaced by: select message, trigger message / indication, or initial trigger message / indication.

[0169] 4. AIoT Random Access Process

[0170] The AIoT random access procedure is used for AIoT devices to access the reader for data transmission. The AIoT random access procedure is triggered by the reader, including triggering a single AIoT device, a group of AIoT devices, or all AIoT devices within the reader's coverage area to access the reader.

[0171] When an AIoT device responds based on an AIoT paging message, the AIoT device executes the following process:

[0172] Step 1: Determine the type of AIoT random access and access resources. AIoT random access types include contention-based random access and contention-free random access.

[0173] If the type of AIoT random access is contention-free random access, the AIoT paging message indicates the access resource, the AIoT device selects the access resource indicated by the reader / writer, and then proceeds to step 3.

[0174] If the type of random access for AIoT is contention-based random access, the AIoT device determines the type of random access. For example, the AIoT device randomly selects access resources and then executes step 2.

[0175] Step 2, contention-based random access contention resolution.

[0176] This step involves two possible implementations. In one possible implementation, message 1 sent by the AIoT device does not contain upper layer data. In the other possible implementation, message 1 sent by the AIoT device contains upper layer data.

[0177] The following section describes the case where there is no upper-level data in message 1.

[0178] An AIoT device generates a random identifier and sends message 1, which includes the random identifier, to a reader / writer on the selected access resource. For example, the random identifier is a randomly generated random number or generated based on the device ID. This application does not limit the length of the random identifier; for example, it can be 16 bits of data.

[0179] The reader sends message 2 (Msg2) to the AIoT device. Message 2 includes a random identifier and is a response to message 1, used for contention resolution. If the AIoT device successfully receives message 2, and the random identifier included in message 2 is the same as the random identifier included in message 1, the AIoT device considers the contention resolution successful and proceeds to step 3. Message 2 can also be expressed as ACK, access ID response, access response, or contention resolution identifier.

[0180] The following section describes the case where message 1 contains upper-level data.

[0181] The AIoT device sends message 1 to the reader on the selected access resource. Message 1 includes upper-layer data, such as the device ID and / or other upper-layer data. Optionally, message 1 may include a random identifier.

[0182] The reader sends message 2 to the AIoT device. Message 2 may include the device ID (all or part), a random identifier, and / or an ACK message. If message 2 is generated based on message 1, for example, message 2 may contain part or all of the information in message 1, or message 2 is obtained by hashing message 1, then the AIoT device considers the contention to be resolved successfully and proceeds to step 3.

[0183] Step 3: The AIoT device performs D2R data transmission to the reader. This data transmission may include the device ID and / or other upper-layer data.

[0184] It is understandable that, for contention-based random access, the D2R data transmission in this step can be regarded as the transmission of message 3 (Msg3). For contention-free random access, the D2R data transmission in this step can be regarded as the transmission of message 1.

[0185] In step 3 above, D2R data transmission may fail, therefore, the AIoT device needs to re-access the reader.

[0186] For contention-based random access, it supports re-access based on negative acknowledgment (NACK) feedback. The principle is as follows: After an AIoT device sends message 3 or message 5, if the reader fails to receive message 3 or message 5 (Msg5), the reader can send a NACK feedback to the AIoT device, indicating that message 3 or message 5 was not received. The NACK feedback is a broadcast R2D message and can include identification information of one or more failed AIoT devices, such as the Access Layer ID (AS ID). An AIoT device receiving a NACK feedback receives a subsequent AIoT paging message, which triggers a re-access attempt by the failed AIoT device. An AIoT device that does not receive a NACK feedback can ignore a subsequent AIoT paging message if it subsequently receives one, without needing to re-access.

[0187] For inventory management applications under contention-free random access, AIoT paging messages only need to page a single AIoT device, and the AIoT device only performs inventory management tasks. The reader / writer does not need to use AS IDs to distinguish / identify different AIoT devices. When an AIoT device sends message 1, but the reader / writer fails to receive message 1, the reader / writer does not send a NACK feedback to the AIoT device. In this case, how the AIoT device can re-access so that the reader / writer can successfully receive message 1 is a problem that urgently needs to be solved.

[0188] In view of this, this application provides a communication method that enables re-access of AIoT devices in disk storage application scenarios based on contention-free random access.

[0189] Figures 4A to 4E are schematic diagrams of the network architecture applicable to the embodiments of this application.

[0190] In Figure 4A, AIoT devices communicate directly and bidirectionally with network devices. Communication between network devices and AIoT devices includes AIoT data and / or signaling. In this network architecture, uplink and downlink data and / or signaling exist between network devices and AIoT devices.

[0191] In Figure 4B, AIoT devices and network devices communicate bidirectionally through intermediate nodes. For example, the intermediate node can be a repeater, an IAB node, or a terminal device, and the intermediate node can implement AIoT. The intermediate node transmits AIoT data and / or signaling between the network device and the AIoT device.

[0192] In Figure 4C, the AIoT device sends data and / or signaling to the network device and receives data and / or signaling from the auxiliary node.

[0193] In Figure 4D, the AIoT device receives data and / or signaling from the network device and sends data and / or signaling to the auxiliary node.

[0194] In Figure 4C or Figure 4D, for example, the auxiliary node can be a repeater, an IAB node, or a terminal device, and the auxiliary node can implement AIoT.

[0195] In Figure 4E, the AIoT device and the terminal device communicate bidirectionally. The communication between the terminal device and the AIoT device includes AIoT data and / or signaling. The terminal device can act as a reader / writer.

[0196] Figure 4A can be considered AIoT topology 1, Figure 4B can be considered AIoT topology 2, Figures 4C and 4D can be considered AIoT topology 3, and Figure 4E can be considered AIoT topology 4. For topology 1 or topology 3, the writer is an access network device or RAN reader, such as a TRP. For topology 2 or topology 4, the reader is a UE reader, where the UE reader can be equivalently replaced by an intermediate node, an intermediate UE, or an AIoT-enabled UE.

[0197] In this context, any of the network devices shown in Figures 4A, 4B, 4C, and 4D may be, for example, access network devices or base stations.

[0198] Please refer to Figure 5, which is a schematic diagram of the logical system architecture of Topology 1. As shown in Figure 5, the xx interface is the next generation (NG) interface, and XXAP is the control plane protocol of the XX interface (NG interface). One possible implementation of "XXAP" is to include AIoTF information / cells in NGAP, and another possible implementation is to carry a newly defined protocol layer on top of the NGAP protocol.

[0199] The AIoT-related processes are defined on XXAP as shown in Figure 6. Figure 6 includes the protocol stack between the AIoT device, AIoT RAN, and AIoT CN. In Figure 6, the xx interface can be an NG interface. For example, in various embodiments of this application, the interface between the access network device and the core network device can be an NG interface, as exemplified in Figures 5 and 6. The AIoT device communicates with the AIoT RAN's AIoT radio protocol layer through AIoT radio protocol layers. The XXAP layer of the AIoT RAN communicates with the XXAP layer of the AIoT CN, the Stream Control Transmission Protocol (SCTP) layer of the AIoT RAN communicates with the SCTP layer of the AIoT CN, the Internet Protocol (IP) layer of the AIoT RAN communicates with the IP layer of the AIoT CN, the Layer 2 (L2) layer of the AIoT RAN communicates with the L2 layer of the AIoT CN, and the Layer 1 (L1) layer of the AIoT RAN communicates with the L1 layer of the AIoT CN.

[0200] In Topology 1, there are two scenarios between AIoT RAN and AIoTF: direct connection and indirect path via AMF. Figure 7 shows the direct connection scenario, and Figure 8 shows the indirect connection scenario.

[0201] Optionally, for Topology 1, whether in a direct or indirect connection scenario, "AIoT RAN" (e.g., the AIoT RAN shown in Figure 7 or Figure 8) or "AIoT RAN node" can be replaced with "access network device", such as "gNB".

[0202] Please refer to Figure 9, which is a schematic diagram of the logical system architecture of Topology 2. In Topology 2, the xx interface between the AIoT-enabled gNB (the AIoT-enabled base station in Figure 9) and the A-IoT CN is the NG interface. The AIoT-enabled UE (the AIoT-enabled UE in Figure 9) and the AIoT device (the AIoT device in Figure 9) communicate through the AIoT interface (e.g., AIoT radio).

[0203] AIoT-enabled gNB includes an AIoT RAN node function, and AIoT-enabled UE includes a common reader function. This common reader function refers to the ability to communicate with A-IoT devices via an AIoT interface (e.g., A-IoT radio); the AIoT RAN node function includes the ability to control AIoT radio resources.

[0204] Topology 2 supports three approaches: RRC-based solution, NAS-based solution, and UP-based solution.

[0205] solution1:RRC based solution.

[0206] The basic idea is that after the access network device (e.g., a base station) receives an AIoT service-related request from the AIoT CN via XXAP, the base station further sends the relevant information to the A-IoT-enabled UE via RRC messages. When the base station receives AIoT service-related data or signaling from the A-IoT-enabled UE via RRC, the base station transmits the relevant information to the AIoT CN via XXAP / NGAP.

[0207] For an RRC-based solution, a possible protocol stack can be found in Figure 10. Figure 10 shows the protocol stack between the AIoT device, the AIoT RAN, and the AIoT CN. The AIoT device communicates with the AIoT RAN's AIoT radio protocol layer through AIoT radio protocol layers. The RRC layer of the AIoT-enabled UE communicates with the RRC layer of the AIoT-enabled gNB, the PDCP layer of the AIoT-enabled UE communicates with the PDCP layer of the AIoT-enabled gNB, the RLC layer of the AIoT-enabled UE communicates with the RLC layer of the AIoT-enabled gNB, the MAC layer of the AIoT-enabled UE communicates with the MAC layer of the AIoT-enabled gNB, and the physical layer of the AIoT-enabled UE communicates with the physical layer of the AIoT-enabled gNB. The XXAP layer of the AIoT-enabled gNB communicates with the XXAP layer of the AIoT CN, the SCTP layer of the AIoT-enabled gNB communicates with the SCTP layer of the AIoT CN, the IP layer of the AIoT-enabled gNB communicates with the IP layer of the AIoT CN, the L2 layer of the AIoT-enabled gNB communicates with the L2 layer of the AIoT CN, and the L1 layer of the AIoT-enabled gNB communicates with the L1 layer of the AIoT CN.

[0208] Among them, the xx interface is the NG-C interface (i.e., the NG control plane interface). One possible implementation of "XXAP" is to include AIoTF information / cells in the NGAP, and another possible implementation is to carry a newly defined protocol layer on the NGAP protocol.

[0209] For RRC-based solutions, there are two scenarios between AIoT-enabled gNBs and AIoTFs: direct connection and indirect connection (indirect path via AMF).

[0210] (1) A schematic diagram of direct connection between AIoT-enabled gNB and AIoTF is shown in Figure 11 (in Figure 11, AIoTF can be replaced with A-IoT CN, and Nx / XX is the NG interface).

[0211] (2) The indirect path via AMF between AIoT-enabled gNB and AIoTF is shown in Figure 12. That is, the AIoT data / signaling transmitted between AIoTF and AIoT-enabled gNB is carried on NGAP. Optionally, "N2" in Figure 12 can also be replaced with "NG".

[0212] solution 2: NAS based solution.

[0213] The basic idea is that the access network equipment (such as the base station) cannot see the AIoT-related processes. The AIoT CN and the AIoT-enabled UE transmit AIoT-related data / signaling through the DL / UL NAS packets of the AIoT-enabled UE (transparent transmission of AIoT-enabled gNB). The base station can use the DL NAS transport process and the UL NAS transport process on the NGAP to process the DL / UL NAS packets of the AIoT-enabled UE.

[0214] Figure 13 shows a possible protocol stack for a NAS-based solution.

[0215] solution 3: UP based solution.

[0216] The basic idea is that access network devices (such as base stations) can not see the AIoT-related processes. AIoT service-related data / signaling between the AIoT CN and the -IoT-enabled UE are transmitted on the PDU Session of the AIoT-enabled UE (transparent transmission to the AIoT-enabled gNB). The gNB processes the user plane data of the AIoT-enabled UE through the NG-U GTP-U channel.

[0217] Figure 14 illustrates a possible protocol stack for an UP-based solution.

[0218] Alternatively, for topology 3, “AIoT-enabled UE” (e.g., the AIoT-enabled UE shown in Figure 9) can also be replaced with “UEreader”, “intermediate UE”, or “intermediate node”, etc.

[0219] The network architecture and communication process described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0220] The following describes some signaling or information involved in the embodiments of this application.

[0221] The Select message can also be replaced with a Paging message, an (initial) trigger message, an (initial) DL trigger message, or an indication message, etc. There are no restrictions on the name.

[0222] The Query message can also be replaced with an access round trigger or indication message, etc., and there are no restrictions on the name.

[0223] The QueryRep message can also be replaced with the (next)access occasion trigger message or the / Indication message, etc., and there are no restrictions on the name.

[0224] The random number (RN) can also be replaced with a random access ID or random ID, and there are no restrictions on the name.

[0225] Msg2 or ACK can also be replaced with access ID response, access response, or UE / device contention resolution identity, etc. There are no restrictions on the name.

[0226] EPC can also be replaced with uplink data (UL data) or device ID, etc., and there are no restrictions on the name.

[0227] One or more of the above signaling can be carried in the media access control (MAC) layer, for example, in a MAC CE, MAC service data unit (SDU), or MAC protocol data unit (PDU). Optionally, "MAC layer" can also be replaced with "AIoT AS".

[0228] A query can trigger or indicate at least one access opportunity. For example, it can directly or indirectly indicate the total number of access opportunities, and / or trigger the first access opportunity.

[0229] QueyRep can trigger or indicate the next access opportunity. It can also be understood as QueyRep indicating or associating the boundary (start or end) of an access opportunity.

[0230] Optionally, the aforementioned "access opportunity" may also be referred to as access timing or access slot, etc. Each access opportunity may allow the AIoT device to send one or more of the following messages: access (request), contention resolution, or data.

[0231] Paging can instruct AIoT devices to access the reader / writer. For example, when the reader / writer is an access network device, paging can instruct the AIoT device to access the network; or, for example, when the reader / writer is a UE, paging can instruct the AIoT device to access the UE. Optionally, if the reader / writer is an access network device, the AIoT device can access the network through the corresponding UE.

[0232] Paging can also trigger or instruct AIoT devices to send data, or trigger, instruct, or request AIoT devices to perform corresponding services. These services can include at least one of the following: paging services, inventory services, command services (such as read, write, deactivate, lock, etc.), location services, or sensing services. Paging can be triggered by a reader / writer.

[0233] RN can be used for contention resolution or to distinguish different AIoT devices during random access or contention resolution.

[0234] An ACK can indicate whether contention resolution was successful. Optionally, an ACK can carry a contention resolution identifier to be associated with the corresponding AIoT device.

[0235] This application relates to air interface transmission between a first device (as an IoT device) and a second device (as a reader / writer). The reader / writer can be a handheld or fixed device that reads (and sometimes writes) tag information; it can also be understood as a device that communicates with the tag. Its form can be a terminal device, a network device, or a device with read / write capabilities. The reader / writer can also be an IAB node or a relay node. This application does not limit the form of the reader / writer.

[0236] When an IoT device is within the coverage area of ​​a reader / writer, and the reader / writer acts as a base station, the communication between the reader / writer and the IoT device is via the AIoT Uu interface, i.e., air interface communication. When the reader / writer acts as a terminal device, the communication between the reader / writer and the IoT device can also reuse the AIoT Uu interface communication mechanism. As an example, the IoT device can be an AIoT device.

[0237] The methods provided in the embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0238] Figure 15 is a schematic flowchart of a communication method 1500 provided in an embodiment of this application. The steps of method 1500 can be interactively executed by a first device (or modules in the first device, such as a processor, chip, chip system, circuit, etc.) and a second device (or modules in the second device, such as a processor, chip, chip system, circuit, etc.). The following description uses the first device and the second device as examples. Furthermore, the processing performed by a single execution entity can also be divided into multiple execution entities, which can be logically and / or physically separated. For example, when the second device is a network device, the processing performed by the network device can be divided into execution by at least one of CU, DU, RU, etc.

[0239] It should be noted that, unless otherwise specified, the definitions and explanations of the terms or concepts in the embodiments of this application are applicable not only to this embodiment but also to other embodiments in this application.

[0240] Method 1500 includes steps S1501 to S1504, and optionally, method 1500 also includes steps S1505 and S1506. The steps are described in detail below.

[0241] S1501, the first device obtains first information, which is used to determine that the random access method is contention-free random access.

[0242] In a disk storage application scenario based on contention-free random access, the second device only needs to send the R2D message to a single device, which is the device to be paged. In this embodiment, the first device is used as an example for description.

[0243] If the terminal device determines that the random access method is contention-free random access, it can determine that the R2D message broadcast by the second device is addressed to it. The R2D message can be, for example, an AIoT paging message.

[0244] S1502, the second device sends a first message to the first device. The first message is used to re-trigger the first device to access the second device. The first message includes first identification information, which is used to identify the first AIoT service on the AIoT interface. Accordingly, the first device receives the first message.

[0245] The first message refers to the subsequent AIoT paging message described above. The first AIoT service is, for example, an inventory check.

[0246] Sending the first message from the second device to the first device can be regarded as an R2D message transmission by the second device.

[0247] It is understood that the first device and the second device communicate via an AIoT interface, and the first identification information is used to identify the first AIoT service on the AIoT interface. Optionally, the first AIoT service is triggered by a core network device, such as an AMF network element or an AIoTF network element.

[0248] Optionally, method 1500 further includes S1505: the second device sends a third message to the first device, the third message being used to trigger the first device to access the second device, the third message including first identification information. Optionally, method 1500 further includes S1506: in response to the third message, the first device sends a fourth message to the second device, the fourth message including second identification information, the second identification information being used to identify the first device. S1505 can be executed before S1501.

[0249] The third message is the AIoT paging message described above, and the fourth message is message 1 in the contention-free random access procedure, which can also be called D2R data. That is, the first device sending the fourth message to the second device can be regarded as a D2R data transmission by the first device.

[0250] The second identification information is, for example, the device ID of the first device or a temporary ID. For the temporary ID, the first device can report the temporary ID instead of the device ID when performing inventory reporting, thus avoiding exposing the device ID on the AIoT interface. The temporary ID can be assigned by a network device (e.g., AIoTF or other core network device) to the first device, or it can be temporarily assigned by the first device, or it can be pre-configured on the first device side. This application embodiment does not limit the allocation method of the temporary ID.

[0251] Understandably, the second device sends a third message to the first device to trigger the first device to access the second device. In response to the third message, the first device sends a fourth message to the second device. If the second device fails to receive the fourth message, it sends a first message to the first device to re-trigger the first device to access the second device. The first message also includes first identification information to identify the first AIoT service.

[0252] S1503, the first device responds to the first message based on the first information and determines to reconnect to the second device.

[0253] Understandably, from the perspective of the first device, after sending the fourth message, it assumes it has connected to the second device. Therefore, if the first message also includes the first identification information, the first device will ignore the first message and not respond. However, in reality, the second device fails to receive the fourth message, meaning the first device's connection to the second device fails. In this embodiment, the first device determines that the random access method is contention-free random access based on the first information. Therefore, it can determine that it is the device to be paged, and thus, the first device can determine to reconnect to the second device.

[0254] S1504, the first device sends a second message to the second device, the second message including second identification information. Accordingly, the second device receives the second message.

[0255] If the first device determines that it needs to reconnect to the second device, it responds to the first message and sends the second message. The second message is message 1 in the random access procedure.

[0256] It is understandable that the fourth message mentioned above is message 1, which the second device failed to receive in a contention-free random access procedure, and the second message is message 1, which the second device successfully received in the next contention-free random access procedure.

[0257] It is understandable that the second device receives the second message and then transmits the second message to the core network device. That is, the second device is unaware of the content contained in the second message. For the second device, the second message is the result of the first device successfully executing the first AIoT service.

[0258] Based on the technical solution of the embodiments of this application, the first device determines that the random access method is contention-free random access based on the first information. In this way, when the first device receives the first message, the first device can determine that it is the paged device. Then, the first device can respond to the first message so that the second device can successfully receive the second message, that is, message 1 in the contention-free random access process.

[0259] Optionally, the first information is included in the third or fifth message. The fifth message can be another R2D message besides the AIoT paging message.

[0260] Optionally, the first piece of information is an access opportunity, and the second device implicitly indicates that the random access method is contention-free random access through an access opportunity. It is understood that if it were a contention-based random access method, the second device would need to allocate multiple access opportunities to multiple AIoT devices. Therefore, the number of access opportunities can distinguish between contention-based random access and contention-free random access. Here, an access opportunity can also be described as an access resource or access chance. One access opportunity refers to one time-frequency resource.

[0261] Optionally, the second device may display an indication that the random access method is contention-free random access.

[0262] In one possible implementation, the third or fifth message includes a first field, which indicates the random access method. For example, a value of "1" indicates that the random access method is contention-based random access, and a value of "0" indicates that the random access method is contention-free random access; or, a value of "0" indicates that the random access method is contention-based random access, and a value of "1" indicates that the random access method is contention-free random access.

[0263] In another possible implementation, the third or fifth message includes bitmap information. For example, this bitmap information includes two bits: the first bit corresponds to contention-based random access, and the second bit corresponds to contention-free random access. For example, a bit value of "1" indicates that its corresponding state is active, and a bit value of "0" indicates that its corresponding state is inactive, or vice versa. For example, a bitmap information of 01 indicates that contention-free random access is active, and contention-based random access is inactive, that is, it indicates that the random access method is contention-free random access.

[0264] The following describes another communication method provided in this application for enabling a first device to reconnect to a second device.

[0265] Figure 16 is a schematic flowchart of another communication method 1600 provided in an embodiment of this application. The steps of method 1600 can be interactively executed by a first device (or modules in the first device, such as processors, chips, chip systems, circuits, etc.) and a second device (or modules in the second device, such as processors, chips, chip systems, circuits, etc.). The following description uses the first device and the second device as examples. Furthermore, the processing performed by a single execution entity can also be divided into multiple execution entities, which can be logically and / or physically separated. For example, when the second device is a network device, the processing performed by the network device can be divided into execution by at least one of CU, DU, RU, etc.

[0266] It should be noted that, unless otherwise specified, the definitions and explanations of the terms or concepts in the embodiments of this application are applicable not only to this embodiment but also to other embodiments in this application.

[0267] Method 1600 includes steps S1601 to S1605, and each step is described in detail below.

[0268] S1601, the second device sends a third message to the first device. The third message triggers the first device to access the second device. The third message includes first identification information, which is used to identify the first AIoT service on the AIoT interface. Accordingly, the first device receives the third message.

[0269] In a disk storage application scenario based on contention-free random access, the second device only needs to send the R2D message to a single device, which is the device to be paged. In this embodiment, the first device is used as an example for description.

[0270] The third message is the AIoT paging message described above, and the first AIoT service is, for example, an inventory service.

[0271] For more information on the third message and the first identification information, please refer to the description of method 1500 above, which will not be repeated here.

[0272] S1602, the first device responds to the third message by sending a fourth message, which includes second identification information used to identify the first device.

[0273] The fourth message is message 1 in the contention-free random access procedure, also known as D2R data. That is, the first device sends the fourth message to the second device, which can be regarded as a D2R data transmission by the first device.

[0274] For more information on the fourth message and the second identification information, please refer to the description in Method 1500 above, which will not be repeated here.

[0275] S1603, if the fourth message is not successfully received, the second device sends a first message to the first device. The first message is used to re-trigger the first device to access the second device, and the first message includes first identification information. Accordingly, the second device receives the first message.

[0276] The first message is the subsequent AIoT paging message described above, and it is transmitted later than the third message.

[0277] Since the second device failed to receive the fourth message, meaning the first device failed to connect to the second device, the second device can resend the first message to trigger the first device to reconnect to the second device. The first message also includes first identification information to identify the first AIoT service.

[0278] Understandably, after receiving the third message, the first device responds by sending a fourth message. From the first device's perspective, it considers itself connected to the second device. Therefore, if the first message also includes the first identification information (i.e., the first and third messages contain the identification information of the same AIoT service), the first device will ignore the first message and not respond. However, in reality, the second device fails to receive the fourth message, meaning the first device's connection to the second device fails. Therefore, to prevent the first device from ignoring the first message, the first device can execute step S1604.

[0279] S1604, the first device obtains the second information, and the second information instructs the first device to reconnect to the second device.

[0280] The second information indicating that the first device can reconnect to the second device may include: the second information indicating that the first device can ignore the first identification information and reconnect to the second device.

[0281] In one possible implementation, the second information is contained in the first message, and the first device obtains the second information by: the first device obtaining the second information from the first message.

[0282] In another possible implementation, the first device acquires the second information by receiving a sixth message from the second device, the sixth message including the second information. The sixth message can be a message from the AIoT physical layer / layer 1, or it can be a message from the AIoT MAC layer.

[0283] Optionally, the second information is the MAC CE in the message of the AIoT MAC layer.

[0284] S1605, the first device sends a second message based on the second information, the second message being a response message to the first message.

[0285] The second message is message 1 in the contention-free random access procedure, also known as D2R data. That is, the first device sends the second message to the second device, which can be regarded as a D2R data transmission by the first device.

[0286] It is understandable that the fourth message mentioned above is message 1, which the second device failed to receive during a contention-free random access procedure, and the second message is message 1, which the second device successfully received during another contention-free random access procedure.

[0287] In this embodiment of the application, the first device can respond to the first message based on the second information, ignoring the first identification information in the first message, so that the second device can successfully receive the second message, i.e. message 1 in the contention-free random access procedure.

[0288] The following describes another communication method provided in this application for enabling a first device to reconnect to a second device.

[0289] Figure 17 is a schematic flowchart of another communication method 1700 provided in an embodiment of this application. The steps of method 1700 can be interactively executed by a first device (or modules in the first device, such as a processor, chip, chip system, circuit, etc.) and a second device (or modules in the second device, such as a processor, chip, chip system, circuit, etc.). The following description uses the first device and the second device as examples. Furthermore, the processing performed by a single execution entity can also be divided into multiple execution entities, which can be logically and / or physically separated. For example, when the second device is a network device, the processing performed by the network device can be divided into execution by at least one of CU, DU, RU, etc.

[0290] It should be noted that, unless otherwise specified, the definitions and explanations of the terms or concepts in the embodiments of this application are applicable not only to this embodiment but also to other embodiments in this application.

[0291] Method 1700 includes steps S1701 to S1704, and optionally, method 1700 also includes steps S1705 to S1708. Each step is described in detail below.

[0292] S1701, the second device sends a third message to the first device. The third message triggers the first device to access the second device. The third message includes first identification information, which is used to identify the first AIoT service on the AIoT interface. Accordingly, the first device receives the third message.

[0293] In a disk storage application scenario based on contention-free random access, the second device only needs to send the R2D message to a single device, which is the device to be paged. In this embodiment, the first device is used as an example for description.

[0294] The third message is the AIoT paging message described above, and the first AIoT service is, for example, the inventory service described above.

[0295] The second device sending a third message to the first device can be regarded as an R2D message transmission by the second device.

[0296] For more information on the third message and the first identification information, please refer to the description in Method 1500 above, which will not be repeated here.

[0297] S1702, the first device sends a fourth message to the second device. The fourth message includes second identification information, which is used to identify the first device.

[0298] The fourth message is message 1 in the random access procedure, also known as D2R data. That is, the first device sends the fourth message to the second device, which can be regarded as a D2R data transmission by the first device.

[0299] For more information on the fourth message and the second identification information, please refer to the description in Method 1500 above, which will not be repeated here.

[0300] S1703, if the fourth message is not successfully received, the second device sends a seventh message to the first device. The seventh message is used to re-trigger the first device to access the second device. The seventh message includes third identification information, which is used to identify the second AIoT service on the AIoT interface. The third identification information is different from the first identification information. Accordingly, the first device receives the seventh message.

[0301] In this embodiment of the application, when the second device re-triggers the first device to access the second device through the seventh message, the seventh message can carry a third identification information that is different from the first identification information, so that the first device understands that the seventh message is a new message used to trigger the first device to access the second device, such as a new AIoT paging message, so that the first device will not ignore the seventh message.

[0302] Among them, the seventh message is the subsequent AIoT paging message described above. The first AIoT service is, for example, the inventory service described above, and the second AIoT service is, for example, the inventory service described above. That is, the first AIoT service and the second AIoT service are two inventory services initiated.

[0303] Sending the seventh message from the second device to the first device can be regarded as an R2D message transmission by the second device.

[0304] S1704, the first device sends an eighth message to the second device, the eighth message including the second identification information.

[0305] Among them, the eighth message is message 1 in the contention-free access process, which can also be called D2R data. That is, the first device sending the eighth message to the second device can be regarded as a D2R data transmission.

[0306] It is understandable that the fourth message mentioned above is message 1, which the second device failed to receive in a contention-free random access procedure, and the eighth message is message 1, which the second device successfully received in the next contention-free random access procedure.

[0307] In this embodiment of the application, since the third identification information carried in the seventh message is different from the first identification information carried in the third message, the first device can consider the seventh message to be a new message used to trigger the first device to access the second device. Therefore, the first device will not ignore the seventh message and will respond to the seventh message so that the second device can successfully receive the second message, i.e. message 1 in the contention-free random access procedure.

[0308] In one possible implementation, the first AIoT service and the second AIoT service can be the same AIoT service initiated at the same time. That is, for the same AIoT service initiated at the same time, the second device distinguishes the seventh message from the third message on the AIoT interface through the third identification information, so that the first device considers the seventh message carrying the third identification information as a new message used to trigger the first device to access the second device, such as a new AIoT paging message.

[0309] In another possible implementation, the second AIoT service can be a new AIoT service distinct from the first AIoT service. Both the first and second AIoT services are triggered by core network equipment, such as AMF or AIoTF.

[0310] Optionally, method 1700 further includes S1705: the third device sends a first request message to the second device, the first request message being used to request the initiation of a second AIoT service, the first request message including fourth identification information, the fourth identification information being used to identify the second AIoT service on the NG interface. S1705 can be executed before S1701. The third device is a core network device, such as an AMF or AIoTF.

[0311] Optionally, the third identification information is determined based on the fourth identification information. For example, the third identification information is obtained by truncating the fourth identification information. For instance, the fourth identification information consists of 32 bits, and the third identification information consists of 16 bits of that fourth identification information.

[0312] Optionally, method 1700 further includes S1706: the second device sends a first response message to the third device, the first response message being a response message to the first request message, used to indicate that the first device has successfully accessed the network. Optionally, the first response message includes fourth identification information and second identification information.

[0313] Optionally, method 1700 further includes S1707: the third device sends a second request message to the second device, the second request message being used to request the initiation of a first AIoT service, the second request message including fifth identification information, the fifth identification information being used to identify the first AIoT service on the NG interface. S1707 can be executed before S1705.

[0314] Optionally, the first identification information is determined based on the fifth identification information. For example, the first identification information is the identification information obtained after truncating the fifth identification information.

[0315] Optionally, method 1700 further includes S1708: the second device sends a second response message to the third device, the second response message being a response message to the second request message, used to indicate that the first device's access has failed. Optionally, the second response message includes fifth identification information. Wherein, the second response message does not include the identification information of the first device.

[0316] In the above embodiments, when the second device is a CU-DU separated base station, after the CU receives the NGAP message from the core network, it forwards the NGAP message to the DU via an F1AP message, or sends the AIoT information contained in the NGAP message to the DU via an F1AP message. The AIoT information may be, for example, the first information, the information contained in the third message, or the information contained in the first message as described above. After the DU receives the RRC message from the first device, it forwards the RRC message to the CU via an F1AP message, or sends the AIoT information contained in the RRC message to the CU via an F1AP message. The AIoT information may be, for example, the information contained in the fourth message (such as the second identification information) or the information contained in the second message (such as the second identification information). It is understood that the NGAP message transmitted on the F1 interface (F1AP) may be different from the NGAP message transmitted on the NG interface; that is, the CU can perform related processing on the message, such as deleting, filtering, mapping, or adding auxiliary information.

[0317] It is understood that the F1AP interface mentioned above is only an example of an interface name between the access network and the core network, and this application does not exclude the definition of terms with similar or the same function in existing or future protocols.

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

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

[0320] The communication method according to the embodiments of this application has been described in detail above with reference to FIG4. The communication device according to the embodiments of this application will be described in detail below with reference to FIG8 and FIG9. These communication devices can be used to implement the functions of the first device or the second device in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments. In the embodiments of this application, the communication device can be the terminal device 120 shown in FIG1, the network device 110 shown in FIG1, or a module (such as a chip) applied to the first device or the second device.

[0321] As shown in Figure 18, the communication device 1800 includes a transceiver module 1810 and a processing module 1820. The processing module 1820 is used for data processing. The transceiver module 1810 can also be referred to as a communication interface or a communication module. The communication device 1800 is used to perform the actions performed by the first or second device in the embodiments shown in Figures 15, 16, or 17. For details, please refer to the relevant descriptions in the embodiments shown in Figures 15, 16, or 17, which will not be repeated here.

[0322] The communication device 1800 can be used to perform the actions performed by the terminal device or network device in the above method embodiments. The communication device 1800 can be a component (e.g., a chip) configured in the terminal device or network device. The processing module 1820 is used to perform processing-related operations of the terminal device or network device in the above method embodiments. The transceiver module 1810 is used to perform receiving and transmitting-related operations of the terminal device or network device in the above method embodiments.

[0323] Optionally, the transceiver module 1810 may include a sending module and a receiving module. The sending module is used to perform the sending operation in the above method embodiments. The receiving module is used to perform the receiving operation in the above method embodiments.

[0324] It should be noted that the communication device 1800 may include a transmitting module but not a receiving module. Alternatively, the communication device 1800 may include a receiving module but not a transmitting module. Specifically, it depends on whether the above-described scheme executed by the communication device 1800 includes both transmitting and receiving actions.

[0325] Optionally, the communication device 1800 may further include a storage module, which can be used to store data and / or to store computer programs or instructions. The processing module 1820 can read the computer programs / instructions and / or data in the storage module so that the communication device 1800 can implement the above-described method embodiments.

[0326] When the communication device 1800 is used to implement the function of the first device in the method embodiment shown in FIG15, the processing module 1820 is used to: obtain first information, the first information being used to determine that the random access method is contention-free random access; the transceiver module 1810 is used to: receive a first message, the first message being used to re-trigger the first device to access the second device, the first message including first identification information, the first identification information being used to identify the first AIoT service on the AIoT interface; the processing module 1820 is also used to: respond to the first message according to the first information and determine to re-access the second device; the transceiver module 1810 is also used to: send a second message, the second message including second identification information, the second identification information being used to identify the first device.

[0327] Optionally, the transceiver module 1810 is configured to: receive a third message, the third message being used to trigger the first device to access the second device, the third message including first identification information; and, in response to the third message, send a fourth message, the fourth message including second identification information.

[0328] Optionally, the first information is included in the third or fifth message.

[0329] Optionally, the first information is an access timing, which is used to transmit the fourth message.

[0330] When the communication device 1800 is used to implement the function of the second device in the method embodiment shown in FIG15, the transceiver module 1810 is used to: send first information, the first information being used to determine that the random access method is contention-free random access; send a first message, the first message being used to re-trigger the first device to access the second device, the first message including first identification information, the first identification information being used to identify the first AIoT service on the AIoT interface; and receive a second message, the second message including second identification information, the second identification information being used to identify the first device.

[0331] Optionally, the transceiver module 1810 is configured to: send a third message, the third message being used to trigger the first device to access the second device, the third message including first identification information; and, in response to the third message, send a fourth message, the fourth message including second identification information.

[0332] Optionally, the first information may be included in the third or fifth message.

[0333] Optionally, the first information is an access timing, which is used to transmit the fourth message.

[0334] When the communication device 1800 is used to implement the function of the first device in the method embodiment shown in FIG16, the transceiver module 1810 is used to: receive a third message, the third message being used to trigger the first device to access the second device, the third message including first identification information, the first identification information being used to identify the first AIoT service on the AIoT interface; in response to the third message, send a fourth message, the fourth message including second identification information, the second identification information being used to identify the first device; receive a first message, the first message being used to re-trigger the first device to access the second device, the first message including first identification information, the first identification information being used to identify the first AIoT service on the AIoT interface; the processing module 1820 is used to: obtain second information, the second information indicating that the first device re-accesses the second device; the transceiver module 1810 is also used to: receive a second message, the second message including second identification information.

[0335] Optionally, the second information may be included in the first or sixth message.

[0336] Optionally, the second information is MAC CE.

[0337] When the communication device 1800 is used to implement the function of the second device in the method embodiment shown in FIG16, the transceiver module 1810 is used to: send a third message, the third message being used to trigger the first device to access the second device, the third message including first identification information, the first identification information being used to identify the first AIoT service on the AIoT interface; if the fourth message is not successfully received, send a first message, the first message being used to re-trigger the first device to access the second device, the first message including first identification information, the first identification information being used to identify the first AIoT service on the AIoT interface; send a second message, the second message being used to instruct the first device to re-access the second device; and receive a second message, the second message including second identification information.

[0338] Optionally, the second information may be included in the first or sixth message.

[0339] Optionally, the second information is MAC CE.

[0340] When the communication device 1800 is used to implement the function of the first device in the method embodiment shown in FIG17, the transceiver module 1810 is configured to: receive a third message, the third message being used to trigger the first device to access the second device, the third message including first identification information, the first identification information being used to identify a first AIoT service on the AIoT interface; in response to the third message, send a fourth message, the fourth message including second identification information; receive a seventh message, the seventh message being used to re-trigger the first device to access the second device, the seventh message including third identification information, the third identification information being used to identify a second AIoT service, the third identification information being different from the first identification information; and in response to the seventh message, send an eighth message, the eighth message including the second identification information.

[0341] Optionally, the transceiver module 1810 is used to receive fourth identification information, which is used to identify the second AIoT service on the NG interface, and the third identification information is determined based on the fourth identification information.

[0342] When the communication device 1800 is used to implement the function of the second device in the method embodiment shown in FIG17, the transceiver module 1810 is used to: send a third message, the third message being used to trigger the first device to access the second device, the third message including first identification information, the first identification information being used to identify the first AIoT service on the AIoT interface; if the fourth message is not successfully received, send a seventh message, the seventh message being used to re-trigger the first device to access the second device, the seventh message including third identification information, the third identification information being used to identify the second AIoT service, the third identification information being different from the first identification information, the fourth message including second identification information, the second identification information being used to identify the first device; and receive an eighth message, the eighth message including the second identification information.

[0343] Optionally, the transceiver module 1810 is used to: send fourth identification information, which is used to identify the second AIoT service on the NG interface, and the third identification information is determined based on the fourth identification information.

[0344] For a more detailed description of the above-mentioned processing module 1820 and transceiver module 1810, please refer to the relevant descriptions in the method embodiments shown in Figures 15, 16 or 17, which will not be repeated here.

[0345] Figure 19 is a schematic block diagram of another communication device 1900 provided in an embodiment of this application. As shown in Figure 9, the communication device 1900 includes one or more processors 1910 and an interface circuit 1920. The one or more processors 1910 and the interface circuit 1920 are coupled to each other. It is understood that the interface circuit 1920 can be a transceiver or an input / output interface. Optionally, the communication device 1900 may also include a memory 1930 for storing instructions executed by the processor 1910, or for storing input data required by the processor 1910 to execute instructions, or for storing data generated after the processor 1910 executes instructions. Sometimes, the interface circuit 1920 can also be understood as part of the one or more processors 1910, in which case the communication device 1900 includes the one or more processors 1910.

[0346] The one or more processors 1910 and memory 1930 can be configured separately or integrated, and this application does not limit this.

[0347] When the communication device 1900 is used to implement the method shown in FIG6, the one or more processors 1910 are used to implement the functions of the processing module 1820, and the interface circuit 1920 is used to implement the functions of the transceiver module 1810.

[0348] When the aforementioned communication device 1900 is a chip applied to the first device, the chip of the first device implements the functions of the first device in the above method embodiments. The chip of the first device receiving information from the second device can be understood as the information being first received by other modules (such as an RF module or antenna) in the first device, and then sent to the chip of the first device by these modules. The chip of the first device sending information to the second device can be understood as the information being first sent to other modules (such as an RF module or antenna) in the first device, and then sent to the second device by these modules.

[0349] When the aforementioned communication device 1900 is a chip applied to a second device, the chip of the second device implements the functions of the second device in the above method embodiments. The chip of the second device receiving information from the first device can be understood as the information being first received by other modules (such as an RF module or antenna) in the second device, and then sent to the chip of the second device by these modules. The chip of the second device sending information to the first device can be understood as the information being first sent to other modules (such as an RF module or antenna) in the second device, and then sent to the first device by these modules.

[0350] This application also provides a computer-readable storage medium for storing a computer program that, when run on a computer, causes the computer to perform the methods described in the above embodiments. Alternatively, the computer program includes instructions for implementing the methods described in the above embodiments.

[0351] This application also provides a computer program product, including: a computer program or instructions that, when run on a computer, cause the computer to perform the methods described above.

[0352] This application also provides an apparatus, which can be a chip, including at least one processor for supporting the implementation of the methods in the above embodiments, such as receiving or processing data involved in the methods in the above embodiments.

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

[0354] The method steps in the embodiments of this application can be implemented in hardware or in software instructions executable by a processor. The software instructions can consist of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, portable hard disks, optical discs, or any other form of storage medium well known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. The storage medium can also be a component of the processor. The processor and the storage medium can reside in an application-specific integrated circuit (ASIC). Alternatively, the ASIC can reside in a base station or terminal. The processor and the storage medium can also exist as discrete components in the base station or terminal.

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

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

[0357] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, The method, applied to a first device or a module in a first device, includes: Obtain first information, which is used to determine that the random access method is contention-free random access; A first message is received, which is used to re-trigger the first device to access the second device. The first message includes first identification information, which is used to identify the first environment IoT AIoT service on the AIoT interface. The first message is triggered by the second device. Based on the first information, respond to the first message and determine to reconnect to the second device; A second message is sent, the second message including second identification information, the second identification information being used to identify the first device.

2. The method as described in claim 1, characterized in that, The method further includes: A third message is received, the third message being used to trigger the first device to access the second device, the third message including the first identification information, and the third message being triggered by the second device; In response to the third message, a fourth message is sent, the fourth message including the second identification information.

3. The method as described in claim 2, characterized in that, The first information is contained in the third message and / or the fifth message.

4. The method as described in claim 2 or 3, characterized in that, The first information is an access opportunity, which is used to transmit the fourth message.

5. A communication method, characterized in that, The method, applied to a first device or a module in a first device, includes: A third message is received, which is used to trigger the first device to access the second device. The third message includes first identification information, which is used to identify the first environment IoT AIoT service on the AIoT interface. The third message is triggered by the second device. In response to the third message, a fourth message is sent, the fourth message including second identification information, the second identification information being used to identify the first device; Receive a first message, the first message being used to re-trigger the first device to access the second device, the first message including the first identification information, the first message being triggered by the second device; Obtain second information, which instructs the first device to reconnect to the second device; Based on the second information, a second message is sent, the second message including the second identification information.

6. A communication method, characterized in that, The method, applied to a second device or a module within a second device, includes: Send a third message, the third message being used to trigger the first device to access the second device, the third message including first identification information, the first identification information being used to identify the first environment IoT AIoT service on the AIoT interface; If the fourth message is not successfully received, a first message is sent. The first message is used to trigger the first device to reconnect to the second device. The first message includes the first identification information. The fourth message includes the second identification information, which is used to identify the first device. Send a second message, which instructs the first device to reconnect to the second device; Receive a second message, the second message including the second identification information.

7. The method as described in claim 5 or 6, characterized in that, The second information is contained in the first message or the sixth message.

8. The method as described in claim 7, characterized in that, The second piece of information is the Media Access Control (MAC) CE.

9. A communication device, characterized in that, It includes modules for implementing the method as described in any one of claims 1 to 4, or modules for implementing the method as described in any one of claims 5, 7, or 8, or modules for implementing the method as described in any one of claims 6 to 8.

10. A communication device, characterized in that, The device includes a processor and an interface circuit. The interface circuit is used to receive signals from other communication devices and transmit them to the processor, or to send signals from the processor to other communication devices. The processor is used to implement the method as described in any one of claims 1 to 4, or to implement the method as described in any one of claims 5, 7 or 8, or to implement the method as described in any one of claims 6 to 8, through logic circuits or execution code instructions.

11. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions that, when executed by a communication device, implement the method as described in any one of claims 1 to 4, or the method as described in any one of claims 5, 7, or 8, or the method as described in any one of claims 6 to 8.

12. A computer program product, characterized in that, include: A computer program or instruction, when executed by a communication device, to implement the method as described in any one of claims 1 to 4, or to implement the method as described in any one of claims 5, 7, or 8, or to implement the method as described in any one of claims 6 to 8.

Images