Communication method and apparatus

Abstract

A communication method and apparatus. In the method, a reader may instruct an AIoT device that supports a timing capability to send Msg1 by using a non-first time-domain resource, and a resource allocation mechanism is provided. Since time-domain resources used by the AIoT device that supports a timing capability are restricted, collisions between time-domain resources used by such AIoT devices that support the timing capability to transmit Msg1 and time-domain resources used by other types of AIoT devices (e.g., AIoT devices that do not support the timing capability) to transmit Msg1 can be reduced, thereby reducing the probability of different AIoT devices sending Msg1 on the same time-domain resource, and helping improve the success rate of an AIoT device accessing a reader.

Description

A communication method and apparatus

[0001] Cross-reference to related applications

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

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

[0004] The 3rd Generation Partnership Project (3GPP) defines the Ambient Internet of Things (A-IoT / AIoT) technology. AIoT technology involves devices including readers and AIoT devices. AIoT devices need to connect to readers to perform AIoT services. However, there is currently no solution for how readers allocate appropriate time-domain resources for AIoT device access. Summary of the Invention

[0005] This application provides a communication method and apparatus for providing a mechanism for allocating time-domain resources for AIoT device access.

[0006] Firstly, embodiments of this application provide a communication method. This method can be applied to the reader / writer side. The reader / writer side can be the reader / writer itself, a module within the reader / writer, or a logic module or software capable of implementing all or part of the reader / writer's functions. Modules within the reader / writer can be, for example, software modules, hardware modules, or a combination of software and hardware modules. Specific modules within the reader / writer include processors, communication modules, or circuits or chips responsible for communication functions. Chips can be, for example, modem chips (also known as baseband chips), or system-on-chip (SoC) chips containing modem cores, or system-in-package (SIP) chips, etc. The following description uses the application of this method to a reader / writer as an example. The method includes: sending a first message, wherein the first message indicates that an AIoT device supporting timing capabilities uses a non-first time domain resource among X time domain resources, where X is an integer greater than 1; receiving a sixteenth message from a first AIoT device, the first AIoT device supporting timing capabilities. Optionally, the sixteenth message is message (Msg)1. Optionally, the first message may be received by the reader on the first time domain resource, which is not the first time domain resource among X time domain resources.

[0007] Optionally, the sixteenth message can be a message in the access procedure (such as in the random access procedure). For example, the sixteenth message is the first message in the random access procedure, which is message (Msg)1.

[0008] Optionally, the first message can be a paging message, a reader-to-device (R2D) trigger message, or a proprietary message, etc., and is not limited thereto. Support for timing capability can be understood as, or alternatively described as, any of the following: supporting timing function, supporting timekeeping function, supporting timing capability, having timing capability or time sensing capability, being able to measure time, being able to sense time, supporting the transmission of the sixteenth message on any of X time-domain resources, or being able to respond to messages indicating X time-domain resources (such as paging messages), where X is an integer greater than 1. X time-domain resources are used to transmit the sixteenth message. For example, X time-domain resources are used for the AIoT device accessing this time to transmit the sixteenth message; in other words, X time-domain resources include time-domain resources used for the AIoT device accessing this time to transmit the sixteenth message. A non-first time-domain resource among X time-domain resources can be understood or replaced by one of the following: a time-domain resource whose index is not the minimum index among the X time-domain resources, or a time-domain resource whose start time is not the earliest among the X time-domain resources, a time-domain resource whose index is greater than the minimum index among the X time-domain resources, or a time-domain resource whose start time is later than the earliest start time among the X time-domain resources. Here, the minimum index refers to the minimum index of the X time-domain resources. The earliest start time refers to the earliest start time of the X time-domain resources.

[0009] In this embodiment, the reader can instruct AIoT devices supporting timing capabilities to send the sixteenth message using a non-first time domain resource, providing a mechanism for allocating time domain resources. Such AIoT devices supporting timing capabilities can perform timing based on non-first time domain resources until a non-first time domain resource is reached, at which point the sixteenth message is sent. In other words, these AIoT devices can send the sixteenth message on the time domain resource indicated by the reader, making the allocated time domain resources more reasonable. Furthermore, restricting the time domain resources used by AIoT devices supporting timing capabilities helps reduce the probability of conflicts between the time domain resources used by these devices for transmitting the sixteenth message and those used by other types of AIoT devices (such as AIoT devices that do not support timing capabilities) for transmitting the sixteenth message. This reduces the probability of different AIoT devices sending the sixteenth message on the same time domain resource, improving the success rate of AIoT devices sending the sixteenth message and thus increasing the success rate of AIoT devices connecting to the reader.

[0010] In one possible implementation, the sixteenth message from a second AIoT device is received on a second time-domain resource. The second AIoT device does not support timing capabilities, and the second time-domain resource is the first of X time-domain resources. Optionally, "not supporting timing capabilities" can be understood or replaced by one of the following: not supporting timing functions, not supporting timekeeping functions, not supporting timekeeping capabilities, lacking timing capabilities, unable to measure time, unable to sense time, or supporting sending the sixteenth message on the first of X time-domain resources.

[0011] In this way, AIoT devices that do not support timing capabilities and AIoT devices that do support timing capabilities can choose different time domain resources, which reduces the probability of time domain resource conflicts when AIoT devices that support timing capabilities transmit the sixteenth message and AIoT devices that do not support timing capabilities transmit the sixteenth message. This reduces the probability of time domain resource collisions when AIoT devices transmit the sixteenth message, improves the rationality of resource allocation, and also helps to improve the success rate of AIoT devices accessing the reader.

[0012] In one possible implementation, the method includes: sending a second message instructing an AIoT device that does not support timing capabilities to preferentially use (or use) the first time domain resource among X time domain resources; or, the first message further instructs an AIoT device that does not support timing capabilities to preferentially use (or use) the first time domain resource among X time domain resources. Optionally, the second message can be a paging message, an R2D trigger message, or a proprietary message, etc., and is not limited thereto. For example, the first message is a paging message, and the second message is an R2D trigger message. Or, the first message is an R2D trigger message, and the second message is a paging message.

[0013] Thus, since the start time of the first time-domain resource is closer to the time of receiving the second or first message compared to other time-domain resources, even AIoT devices without timing capabilities can successfully send the sixteenth message after receiving the second or first message, achieving resource allocation for AIoT devices that do not support timing capabilities. Furthermore, when using the second message to indicate that AIoT devices without timing capabilities should prioritize the use of the first time-domain resource, the first message instruction is unnecessary, reducing the data volume of the first message. Alternatively, when using the first message to indicate that AIoT devices without timing capabilities should prioritize the use of the first time-domain resource, no additional message instruction is needed, which helps reduce the number of messages in the system and the number of interactions between the reader and the AIoT device.

[0014] In one possible implementation, the method further includes: receiving a third message from a core network device or an access network device, the third message indicating that the first AIoT device supports timing capabilities. Optionally, the third message may also indicate that a second AIoT device does not support timing capabilities.

[0015] In this way, the reader can determine in advance whether the connected AIoT device supports timing capabilities, which makes it easier for the reader to allocate time domain resources more reasonably and accurately.

[0016] In one possible implementation, the method further includes: receiving a tenth message, the tenth message including first information, the first information indicating the inventory and reporting of a Public Land Mobile Network (PLN) identifier and / or network identifier that does not carry the first AIoT device; and sending an eleventh message, the eleventh message including second information, the second information indicating the inventory and reporting of a PPN identifier and / or network identifier that does not carry the first AIoT device. Optionally, the method further includes: receiving first data from the first AIoT device, the first data not carrying the PPN identifier and / or network identifier of the first AIoT device. Optionally, the first information and the second information may be the same information or different information, and this is not limited.

[0017] Thus, when the first AIoT device successfully accesses the network and reports its inventory, it does not need to carry the public land mobile network identifier and / or network identifier, which reduces the amount of data reported by the first AIoT device and reduces the power consumption of the first AIoT device.

[0018] Secondly, embodiments of this application provide a communication method. This method can be applied to a first AIoT device. The first AIoT device can be the first AIoT device itself, a module within the first AIoT device, or a logic module or software capable of implementing all or part of the functions of the first AIoT device. Modules within the first AIoT device can be, for example, software modules, hardware modules, or a combination of software and hardware modules. The first AIoT device can be, for example, a processor, a communication module, or a circuit or chip responsible for communication functions within the first AIoT device; a chip can be, for example, a modem chip, or a SoC chip or SIP chip containing a modem core. The following description uses the application of this method to a first AIoT device as an example. The method includes: receiving a first message, the first message indicating that an AIoT device supporting timing capabilities uses a non-first time domain resource among X time domain resources, where X is an integer greater than 1; and sending a sixteenth message on the first time domain resource, indicating that the first AIoT device supports timing capabilities, and the first time domain resource is a non-first time domain resource among X time domain resources. Optionally, the sixteenth message is a message during a random access process.

[0019] One possible implementation supports timing capabilities, including: supporting the transmission of the sixteenth message on any of the X time-domain resources.

[0020] In one possible implementation, the method further includes: receiving an eleventh message, the eleventh message including second information, the second information indicating the inventory and reporting of a public terrestrial mobile network identifier and / or network identifier that does not carry the first AIoT device.

[0021] In one possible implementation, the method further includes: sending first data, the first data not carrying the public terrestrial mobile network identifier and / or network identifier of the first AIoT device.

[0022] Thirdly, embodiments of this application provide a communication method. This method can be applied to the core network (CN) device side. The core network device side can refer to the core network device itself, or a module within the core network device, or a logical module or software capable of implementing all or part of the functions of the core network device. Modules within the core network device can be, for example, software modules, hardware modules, or a combination of software and hardware modules. Modules within the core network device can be, for example, processors, communication modules, or circuits or chips responsible for communication functions, such as modem chips, or SC chips or SIP chips containing modem cores. The core network device can be, for example, an AIoT core network element (AIoT CN function, AIoTF) or an access and mobility management function (AMF). The method includes: sending a third message, the third message indicating that a first AIoT device supports timing capabilities. Optionally, the third message may also indicate that a second AIoT device does not support timing capabilities.

[0023] In one possible implementation, the method further includes: sending a tenth message, the tenth message including first information, the first information indicating the inventory and reporting of a public terrestrial mobile network identifier and / or network identifier that does not carry the first AIoT device.

[0024] In one possible implementation, the method further includes: receiving first data, the first data not carrying the public terrestrial mobile network identifier and / or network identifier of the first AIoT device.

[0025] Fourthly, embodiments of this application provide a communication method. This method can be applied to the reader / writer side. The content regarding the reader / writer side can be referred to in the first aspect above, and will not be repeated here. The following description uses the application of this method to a reader / writer as an example. The method includes: sending a fourth message, the fourth message indicating that an AIoT device supporting timing capabilities has accessed the network; receiving a seventeenth message from one or more AIoT devices, the one or more AIoT devices supporting timing capabilities. Optionally, the seventeenth message is a message during the random access process, such as Msg1.

[0026] In this embodiment, the reader can instruct AIoT devices that support timing capabilities to connect, providing a mechanism for selecting AIoT devices to connect. Furthermore, based on the feature of supporting timing capabilities, the reader allocates resources to connected AIoT devices that support timing capabilities, which helps improve the rationality of resource allocation by the reader.

[0027] One possible implementation supports timing capabilities, including: supporting the transmission of a seventeenth message on any of X time-domain resources; wherein the X time-domain resources are configured by the reader / writer via a fourth or fifth message, and the fifth message is sent before or after the fourth message, where X is an integer greater than 1. Optionally, the fifth message can be a paging message, an R2D trigger message, or a proprietary message, etc., and is not limited thereto. For example, the fourth message is a paging message, and the fifth message is an R2D trigger message. Or, the fourth message is an R2D trigger message, and the fifth message is a paging message.

[0028] In one possible implementation, before sending the fourth message, the method further includes receiving a sixth message from a core network device or an access network device, the sixth message indicating that one or more AIoT devices support timing capabilities.

[0029] In one possible implementation, the method further includes: receiving a tenth message, the tenth message including first information, the first information indicating the inventory and reporting of a public land mobile network identifier and / or network identifier that does not carry the first AIoT device; and sending an eleventh message, the eleventh message including second information, the second information indicating the inventory and reporting of a public land mobile network identifier and / or network identifier that does not carry the first AIoT device, wherein the first AIoT device belongs to one or more AIoT devices.

[0030] In one possible implementation, the method further includes: receiving first data from a first AIoT device, the first data not carrying the public terrestrial mobile network identifier and / or network identifier of the first AIoT device.

[0031] Fifthly, embodiments of this application provide a communication method. This method can be applied to a first AIoT device. The content of the first AIoT device can be referred to the content of the first AIoT device discussed in the second aspect above, and will not be listed here again. The following description uses the application of this method to a first AIoT device as an example. The method includes: receiving a fourth message, the fourth message indicating that an AIoT device supporting timing capability has accessed; sending a seventeenth message on a third time domain resource, the third time domain resource being one of X time domain resources, the first AIoT device supporting timing capability, the X time domain resources being indicated by the fourth message or the fifth message, the fifth message being sent before or after the fourth message, and X being greater than or equal to 1. Optionally, the seventeenth message is a message in the random access process.

[0032] One possible implementation supports timing capabilities, including: supporting the transmission of the seventeenth message on any of the X time-domain resources.

[0033] In one possible implementation, the method further includes: receiving an eleventh message, the eleventh message including second information, the second information indicating that a public land mobile network identifier and / or network identifier not carrying a first AIoT device is stored and reported, the first AIoT device belonging to one or more AIoT devices.

[0034] In one possible implementation, the method further includes: sending first data, the first data not carrying the public terrestrial mobile network identifier and / or network identifier of the first AIoT device.

[0035] Sixthly, embodiments of this application provide a communication method. This method can be applied to the core network device side. The content regarding the core network device side can be referred to the content discussed in the third aspect above, and will not be listed here again. The method includes: sending a sixth message, the sixth message indicating that one or more AIoT devices support timing capabilities.

[0036] In one possible implementation, the method further includes: sending a tenth message, the tenth message including first information, the first information indicating the inventory and reporting of a public terrestrial mobile network identifier and / or network identifier that does not carry the first AIoT device.

[0037] In one possible implementation, the method further includes: receiving first data, the first data not carrying the public terrestrial mobile network identifier and / or network identifier of the first AIoT device.

[0038] In a seventh aspect, embodiments of this application provide a communication method. This method can be applied to the reader / writer side. The content regarding the reader / writer side can be referred to in the first aspect above, and will not be repeated here. The following description uses the application of this method to a reader / writer as an example. The method includes: sending a seventh message indicating that an AIoT device that does not support timing capabilities has accessed the device; and receiving an eighteenth message from one or more AIoT devices, wherein the one or more AIoT devices do not support timing capabilities. Optionally, the eighteenth message is a message during a random access process, for example, the eighteenth message is Msg1.

[0039] In this embodiment, the reader can instruct AIoT devices that do not support timing capabilities to connect, providing a mechanism for selecting AIoT devices to connect. Furthermore, based on the characteristic of not supporting timing capabilities, the reader allocates resources to connected AIoT devices that do not support timing capabilities, which helps improve the rationality of resource allocation by the reader.

[0040] In one possible implementation, the method further includes: not supporting timing capabilities, including: not supporting the transmission of the eighteenth message on a non-first time domain resource among X time domain resources; wherein the X time domain resources are configured by the reader via the seventh message or the eighth message, the eighth message is sent before or after the seventh message, and X is an integer greater than 1.

[0041] In one possible implementation, the method further includes receiving a ninth message from a core network device or an access network device, the ninth message indicating that one or more AIoT devices do not support timing capabilities.

[0042] In one possible implementation, the method further includes: receiving a twelfth message, the twelfth message including third information, the third information indicating the inventory and reporting of a Public Land Mobile Network (PLN) identifier and / or network identifier that does not carry the first AIoT device; and / or sending a thirteenth message, the thirteenth message including fourth information, the fourth information indicating the inventory and reporting of a PRN identifier and / or network identifier that does not carry the first AIoT device. Optionally, the third information and the fourth information may be the same information or different information, and this is not limited.

[0043] In one possible implementation, the method further includes: receiving first data, the first data not carrying the public terrestrial mobile network identifier and / or network identifier of the first AIoT device.

[0044] Eighthly, this application provides a communication method. This method can be applied to a second AIoT device. The second AIoT device can be the second AIoT device itself, a module within the second AIoT device, or a logic module or software capable of implementing all or part of the functions of the second AIoT device. Modules within the second AIoT device can be, for example, software modules, hardware modules, or a combination of both, such as a processor, communication module, or circuit or chip responsible for communication functions within the second AIoT device. Chips can be, for example, modem chips (also known as baseband chips), or SoC chips or SIP chips containing modem cores. The following description uses the application of this method to a second AIoT device as an example. The method includes: receiving a seventh message, which indicates that an AIoT device without timing capabilities is accessing the device; sending an eighteenth message on a fourth time-domain resource, where the fourth time-domain resource is the first of X time-domain resources, the second AIoT device does not support timing capabilities, the X time-domain resources are indicated by the seventh or eighth message, the eighth message is sent before or after the seventh message, the eighteenth message is a message during a random access process, and X is an integer greater than 1.

[0045] One possible implementation does not support timing capabilities, including: not supporting the sending of the eighteenth message on a non-first time domain resource among X time domain resources.

[0046] In one possible implementation, the method further includes: receiving a thirteenth message, the thirteenth message instructing the inventory and / or reporting of a public terrestrial mobile network identifier and / or network identifier that does not carry the first AIoT device.

[0047] In one possible implementation, the method further includes: receiving first data, the first data not carrying the public terrestrial mobile network identifier and / or network identifier of the first AIoT device.

[0048] Ninthly, embodiments of this application provide a communication method. This method can be applied to the core network device side. The content regarding the core network device side can be referred to the core network device side discussed in the third aspect above, and will not be listed here again. The following description uses the application of this method to a core network device as an example. The method includes: sending a ninth message, the ninth message indicating that one or more AIoT devices do not support timing capabilities.

[0049] Tenthly, embodiments of this application provide a communication method. This method can be applied to a reader / writer side. The reader / writer side can refer to the content discussed in the first aspect above. The following description uses the application of this method to a reader / writer as an example. The method includes: receiving a tenth message, the tenth message including first information, the first information indicating the storage and reporting of a Public Land Mobile Network Identifier and / or a Network Identifier that does not carry a first AIoT device; and sending an eleventh message, the eleventh message including second information, the second information indicating the storage and reporting of a Public Land Mobile Network Identifier and / or a Network Identifier that does not carry a first AIoT device.

[0050] In this embodiment of the application, when the first AIoT device inventory and reports, it is not necessary to carry the public land mobile network identifier and / or network identifier, which can reduce the amount of data reported by the first AIoT device and help reduce the amount of data transmission in the system.

[0051] In one possible implementation, the method includes: receiving first data from a first AIoT device, the first data not carrying the public terrestrial mobile network identifier and / or network identifier of the first AIoT device.

[0052] Eleventhly, embodiments of this application provide a communication method. This method can be applied to a first AIoT device. The first AIoT device can refer to the content discussed in the second aspect above. The following description uses the application of this method to a first AIoT device as an example. The method includes: receiving an eleventh message, the eleventh message including second information, the second information indicating the storage and reporting of a Public Land Mobile Network Identifier and / or network identifier without carrying the first AIoT device; and sending first data, the first data not carrying the Public Land Mobile Network Identifier and / or network identifier of the first AIoT device.

[0053] In a twelfth aspect, embodiments of this application provide a communication method. This method can be applied to the core network equipment side. The core network equipment side can refer to the content discussed in the third aspect above. The following description uses the application of this method to a core network equipment as an example. The method includes: sending a tenth message, the tenth message including first information, the first information indicating the storage and reporting of a Public Land Mobile Network Identifier and / or network identifier that does not carry the first AIoT device; and receiving first data, the first data not carrying the Public Land Mobile Network Identifier and / or network identifier of the first AIoT device.

[0054] In a thirteenth aspect, embodiments of this application provide a communication method. This method can be applied to the reader / writer side. The content regarding the reader / writer side can be referred to in the first aspect above, and will not be repeated here. The following description uses the application of this method to a reader / writer as an example. The method includes: sending a second message, the second message indicating that an AIoT device that does not support timing capabilities preferentially uses (or uses) the first time domain resource among X time domain resources, where X is an integer greater than 1; and receiving a nineteenth message from a second AIoT device on the second time domain resource, the second device not supporting timing capabilities. Optionally, the nineteenth message is a message in the random access process, such as the first message in the random access process, such as Msg1. The second message indicating that an AIoT device that does not support timing capabilities preferentially uses the first time domain resource among X time domain resources can be understood or alternatively described as: the second message indicating that an AIoT device that supports timing capabilities does not preferentially use the first time domain resource among X time domain resources, or that the priority of an AIoT device that does not support timing capabilities using the first time domain resource is higher than the priority of an AIoT device that supports timing capabilities using the first time domain resource. For example, the nineteenth message is Msg1.

[0055] In this embodiment, an AIoT device that does not support timing capabilities is instructed to preferentially use the first time-domain resource to send the nineteenth message, providing a mechanism for allocating time-domain resources. Furthermore, by restricting the time-domain resources used by AIoT devices that do not support timing capabilities, conflicts between these devices and other AIoT devices regarding the time-domain resources for transmitting the nineteenth message are reduced. This decreases the probability of different AIoT devices sending the nineteenth message on the same time-domain resource, increases the success rate of AIoT devices sending the nineteenth message, and ultimately improves the success rate of AIoT devices connecting to the reader / writer.

[0056] In one possible implementation, the method further includes receiving a fourteenth message from a core network device or an access network device, the fourteenth message indicating that the second AIoT device does not support timing capabilities.

[0057] In one possible implementation, the method further includes: receiving a twelfth message, the twelfth message including third information, the third information indicating the inventory and reporting of a Public Land Mobile Network (PLN) identifier and / or network identifier not carrying the first AIoT device, and / or sending a thirteenth message, the thirteenth message including fourth information, the fourth information indicating the inventory and reporting of a PPN identifier and / or network identifier not carrying the first AIoT device. Optionally, the method further includes: receiving second data from a second AIoT device, the second data not carrying the PPN identifier and / or network identifier of the second AIoT device.

[0058] In a fourteenth aspect, embodiments of this application provide a communication method. This method can be applied to a second AIoT device. The details regarding the second AIoT device are as described in aspect eight and will not be repeated here. The following description uses the application of this method to a second AIoT device as an example. The method includes: a second message indicating that an AIoT device that does not support timing capabilities will preferentially use (or use) the first time-domain resource among X time-domain resources, where X is an integer greater than 1; and sending a nineteenth message on the second time-domain resource, indicating that the second AIoT device does not support timing capabilities and that the second time-domain resource is the first time-domain resource among X time-domain resources. Optionally, the nineteenth message is a message during a random access process.

[0059] One possible implementation does not support timing capabilities, including: not supporting the sending of the nineteenth message on a non-first time domain resource among X time domain resources.

[0060] In one possible implementation, the method further includes: receiving a thirteenth message, the thirteenth message including fourth information, the fourth information indicating the inventory and reporting of a public terrestrial mobile network identifier and / or network identifier that does not carry a second AIoT device.

[0061] In one possible implementation, the method further includes: sending second data, the second data not carrying the public terrestrial mobile network identifier and / or network identifier of the second AIoT device.

[0062] In a fifteenth aspect, embodiments of this application provide a communication method. This method can be applied to the core network device side. The content regarding the core network device side can be referred to in the third section and will not be repeated here. The method includes: sending a fourteenth message, the fourteenth message indicating that a second AIoT device does not support timing capabilities.

[0063] In a sixteenth aspect, embodiments of this application provide a communication method. This method can be applied to a third AIoT device. The third AIoT device can be the third AIoT device itself, a module within the third AIoT device, or a logic module or software capable of implementing all or part of the functions of the third AIoT device. Modules within the third AIoT device can be, for example, software modules, hardware modules, or a combination of software and hardware modules, such as processors, communication modules, or circuits or chips responsible for communication functions. Chips can be, for example, modem chips, or SoC chips or SIP chips containing modem cores. The following description uses the application of this method to a third AIoT device as an example. The method includes: if the third A-IoT device supports timing capabilities, sending a twentieth message on a non-first time domain resource among X time domain resources, where X time domain resources are used to send the twentieth message, and X is an integer greater than 1; if the third A-IoT device does not support timing capabilities, sending a twentieth message on the first time domain resource among the X time domain resources. The twentieth message is, for example, Msg1.

[0064] In this embodiment, the third AIoT device can select resources that match its timing capabilities based on whether it supports timing capabilities. This ensures that the timing resources selected by the third AIoT device better meet its needs, which is beneficial to improving the success rate of the third AIoT device sending the twentieth message and thus improving the success rate of the third AIoT device accessing the network.

[0065] In one possible implementation, the method includes: determining whether timing capability is supported.

[0066] In a seventeenth aspect, embodiments of this application provide a communication device. The communication device includes corresponding means or modules for performing any of the possible implementations of the first to sixteenth aspects described above. For example, the communication device includes a communication unit (sometimes also called a communication module). Optionally, the communication device further includes a processing unit (sometimes also called a processing module). The communication unit is used to perform transmit and receive operations, such as functions related to sending and receiving; the communication unit may be called a transceiver unit; optionally, the communication unit includes a receiving unit and a transmitting unit. The processing unit is used to perform processing operations. Alternatively, the communication unit may be a transmitter and a receiver, or a transmitter and a receiver. Optionally, the communication device further includes a storage unit (sometimes also called a storage module).

[0067] In a first possible implementation, the communication device can perform the functions of the reader / writer described in the first aspect above.

[0068] For example, the communication unit is used to send the first message and receive the sixteenth message.

[0069] In one possible design, the communication device may also implement any of the possible implementations of the first aspect described above, which will not be listed here.

[0070] In a second possible implementation, the communication device can perform the functions of the first AIoT device described in the second aspect above.

[0071] For example, the communication unit is used to receive the first message and to send the sixteenth message.

[0072] In one possible design, the communication device may also implement any of the possible implementations of the second aspect described above, which will not be listed here.

[0073] In a third possible implementation, the communication device can perform the functions of the core network equipment described in the third aspect above.

[0074] For example, a communication unit is used to send a third message.

[0075] In one possible design, the communication device may also implement any of the possible implementations in the third aspect described above, which will not be listed here.

[0076] In a fourth possible implementation, the communication device can perform the functions of the reader / writer described in the fourth aspect above.

[0077] For example, the communication unit is used to send the fourth message and receive the seventeenth message.

[0078] In one possible design, the communication device may also implement any of the possible implementations in the fourth aspect described above, which will not be listed here.

[0079] In a fifth possible implementation, the communication device can perform the functions of the first AIoT device described in the fifth aspect above.

[0080] For example, the communication unit is used to receive the fourth message and to send the seventeenth message.

[0081] In one possible design, the communication device may also implement any of the possible implementations in the fifth aspect described above, which will not be listed here.

[0082] In a sixth possible implementation, the communication device can perform the functions of the core network equipment described in the sixth aspect above.

[0083] For example, the communication unit is used to send the sixth message.

[0084] In one possible design, the communication device may also implement any of the possible implementations in the sixth aspect described above, which will not be listed here.

[0085] In a seventh possible implementation, the communication device can perform the functions of the reader / writer described in the seventh aspect above.

[0086] For example, the communication unit is used to send the seventh message and receive the eighteenth message.

[0087] In one possible design, the communication device may also implement any of the possible implementations in the seventh aspect described above, which will not be listed here.

[0088] In an eighth possible implementation, the communication device can realize the functions of the second AIoT device mentioned in the eighth aspect above.

[0089] For example, the communication unit is used to receive the seventh message and send the eighteenth message.

[0090] In one possible design, the communication device may also implement any of the possible implementations in the eighth aspect described above, which will not be listed here.

[0091] In a ninth possible implementation, the communication device can perform the functions of the core network equipment described in the ninth aspect above.

[0092] For example, the communication unit is used to send the twelfth message.

[0093] In one possible design, the communication device may also implement any of the possible embodiments described in the ninth aspect above, which will not be listed here.

[0094] In a tenth possible implementation, the communication device can perform the functions of the reader / writer described in the tenth aspect above.

[0095] For example, the communication unit is used to receive the tenth message and send the eleventh message.

[0096] In one possible design, the communication device may also implement any of the possible embodiments described in the tenth aspect above, which will not be listed here.

[0097] In the eleventh possible implementation, the communication device can realize the functions of the first AIoT device in the eleventh aspect above.

[0098] For example, the communication unit is used to receive the eleventh message and to send the first data.

[0099] In one possible design, the communication device may also implement any of the possible embodiments described in the eleventh aspect above, which will not be listed here.

[0100] In a twelfth possible implementation, the communication device can perform the functions of the core network equipment described in the twelfth aspect above.

[0101] For example, the communication unit is used to send the tenth message.

[0102] In one possible design, the communication device may also implement any of the possible embodiments described in the twelfth aspect above, which will not be listed here.

[0103] In a thirteenth possible implementation, the communication device can perform the functions of the reader / writer described in the thirteenth aspect above.

[0104] For example, the communication unit is used to send a second message and receive a nineteenth message.

[0105] In one possible design, the communication device may also implement any of the possible embodiments described in aspect thirteen above, which will not be listed here.

[0106] In the fourteenth possible implementation, the communication device can realize the functions of the second AIoT device in the fourteenth aspect above.

[0107] For example, the communication unit is used to receive the second message and to send the nineteenth message.

[0108] In one possible design, the communication device may also implement any of the possible embodiments described in aspect fourteen above, which will not be listed here.

[0109] In the fifteenth possible implementation, the communication device can perform the functions of the core network equipment described in the fifteenth aspect above.

[0110] For example, the communication unit is used to send the fourteenth message.

[0111] In one possible design, the communication device may also implement any of the possible embodiments described in aspect fifteen above, which will not be listed here.

[0112] In a sixteenth possible implementation, the communication device can perform the functions of the third AIoT device described in the sixteenth aspect above.

[0113] For example, the communication unit is used to send the twentieth message on a non-first time domain resource among X time domain resources if the third A-IoT device supports timing capability, where X time domain resources are used to send the twentieth message, and X is an integer greater than 1; and to send the twentieth message on the first time domain resource among X time domain resources if the third A-IoT device does not support timing capability.

[0114] In one possible design, the communication device may also implement any of the possible embodiments described in the sixteenth aspect above, which will not be listed here.

[0115] In an eighteenth aspect, embodiments of this application provide a communication device. The communication device includes one or more processors. The one or more processors are capable of executing computer programs or instructions stored in memory, which, when executed, cause the communication device to implement the methods described in any of the first to sixteenth aspects above.

[0116] Optionally, the communication device may include a memory, in which case the memory may be coupled to one or more processors, or the memory may be configured relatively independently of one or more processors. Alternatively, the memory may exist independently of the communication device.

[0117] In one possible design, the communication device may further include an interface circuit, through which the processor communicates with other devices or components.

[0118] In the specific implementation process, the communication device can be a chip, and the processor can be a transistor, gate circuit, flip-flop, and various logic circuits, etc. The specific implementation method of the processor is not limited in the embodiments of this application.

[0119] In one implementation, the communication device can be a wireless communication device, i.e., a computer device that supports wireless communication functionality. Specifically, the wireless communication device can be a network device such as a wireless access network device (e.g., a base station).

[0120] In another implementation, the communication device can be a component of a wireless communication device, such as an integrated circuit product like a system-on-a-chip (SoC) or communication chip. A SoC can also be called a System-on-a-Chip (SoC). A communication chip may include a baseband processing chip and a radio frequency (RF) processing chip. A baseband processing chip is sometimes referred to as a modem or baseband chip. An RF processing chip is sometimes referred to as an RF transceiver or RF chip. In physical implementation, some or all of the communication chip may be integrated within the SoC. For example, the baseband processing chip may be integrated into the SoC, while the RF processing chip may not be integrated. The interface circuit can be the RF processing chip in the wireless communication device, and the processor can be the baseband processing chip in the wireless communication device. The interface circuit can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip or chip system. The processor can also be a processing circuit or logic circuit.

[0121] In another implementation, the communication device can be a chip system, which may consist of chips or include chips and other discrete devices. Chip systems may include, for example, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), system-on-chips (SoCs), central processing units (CPUs), network processors (NPs), digital signal processors (DSPs), microcontroller units (MCUs), programmable logic devices (PLDs), or other integrated chips.

[0122] In a nineteenth aspect, embodiments of this application provide a communication system.

[0123] Optionally, the communication system includes the communication device in the first possible embodiment of the seventeenth aspect described above to the communication device in the third possible embodiment.

[0124] Optionally, the communication system includes the communication device in the fourth to sixth possible embodiments of the seventeenth aspect described above.

[0125] Optionally, the communication system includes the communication device in the seventh to ninth possible embodiments of the seventeenth aspect described above.

[0126] Optionally, the communication system includes the communication device in the tenth to twelfth possible embodiments of the seventeenth aspect described above.

[0127] Optionally, the communication system includes the communication device in the thirteenth to fifteenth possible embodiments of the seventeenth aspect described above.

[0128] In a twentieth aspect, embodiments of this application provide a chip system. The chip system includes a processor. Optionally, the chip system may further include an interface (such as a communication interface). The processor can be used to implement the methods discussed in any of the first to sixteenth aspects above.

[0129] Optionally, the chip system also includes a memory. The memory is used to store computer programs (also called code or instructions). The processor is used to retrieve and run the computer programs from the memory, causing the device equipped with the chip system to perform any of the methods described in the first to fourth aspects above. The implementation of the chip system can be referred to the content of the chip systems discussed above, and will not be listed here again.

[0130] In a twentieth aspect, embodiments of this application provide a computer-readable storage medium. This computer-readable storage medium is used to store a computer program or instructions that, when executed, implement the methods described in the first aspect and possibly in any of the first to sixteenth aspects above.

[0131] In a twenty-second aspect, embodiments of this application provide a computer program product. When the computer program product is executed, it causes a processor to perform the methods described in any of the first to sixteenth aspects above. The computer program product includes computer programs and / or instructions, etc.

[0132] Regarding the beneficial effects of any of the technical solutions in the second to twenty-second aspects mentioned above, please refer to the discussion of the beneficial effects of the corresponding technical solutions in the first, fourth, seventh, thirteenth, and sixteenth aspects, which will not be listed here one by one. Attached Figure Description

[0133] Figures 1 and 2 are schematic diagrams of two structures of access network equipment;

[0134] Figure 3 is a schematic diagram of an access process;

[0135] Figures 4 to 8 are schematic diagrams of the architecture of several communication systems applicable to the embodiments of this application;

[0136] Figures 9 to 18 are schematic diagrams of several AIoT network architecture topologies applicable to the embodiments of this application;

[0137] Figure 19 is a schematic diagram of a communication method provided in an embodiment of this application;

[0138] Figure 20 is a schematic diagram of the identifier of the AIoT device provided in an embodiment of this application;

[0139] Figure 21 is a schematic diagram of X time-domain resources provided in an embodiment of this application;

[0140] Figures 22 to 27 are schematic diagrams of several communication methods provided in the embodiments of this application;

[0141] Figures 28 and 29 are schematic diagrams of the structures of several communication devices provided in the embodiments of this application. Detailed Implementation

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

[0143] In this application embodiment, the number of nouns, unless otherwise specified, refers to "singular nouns or plural nouns," that is, "one or more." "At least one" means one or more, and "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 exists alone, A and B exist simultaneously, or B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. For example, A / B means: A or B. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c means: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, and c can be single or multiple.

[0144] The ordinal numbers such as "first" and "second" mentioned in the embodiments of this application are used to distinguish multiple objects, and are not used to limit the size, content, order, timing, priority, or importance of the multiple objects. Furthermore, the numbering of steps in the various embodiments described in this application is only to distinguish different steps and is not used to limit the order in which the steps are performed.

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

[0146] 1. A terminal device is a user-side device with wireless transceiver capabilities. A terminal device can be a fixed device, a mobile device, a handheld device (such as a mobile phone), a wearable device, an in-vehicle device, or a wireless device (such as a communication module, modem, or chip system) built into the above devices. The terminal devices are used to connect people, objects, and machines, and can be widely used in various scenarios, including but not limited to the following: sensing scenarios, cellular communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine / machine-type (M2M / MTC) communication, Internet of Things (IoT), virtual reality (VR), augmented reality (AR), industrial control, self-driving, remote medical care, smart grid, smart furniture, smart office, smart wearables, smart transportation, smart city, drones, robots, and terminal devices in indoor commercial scenarios (such as mobile phone screen mirroring, file sharing, and mobile phone to VR glasses). When the terminal equipment is applied to V2X, it can also be called a V2X device, such as a smart car, digital car, unmanned car, driverless car, pilotless car, or automobile, self-driving car, battery EV, hybrid electric vehicle (HEV), range-extended electric vehicle (REEV), plug-in hybrid electric vehicle (PHEV), new energy vehicle, or roadside unit (RSU). The terminal equipment can also be a device used in D2D communication, such as an electricity meter or water meter. Terminal equipment typically contains communication modules, circuits, or chips that perform the corresponding communication functions. The terminal equipment can also be configured with program instructions for performing these communication functions.

[0147] Furthermore, in this embodiment of the application, the terminal device can also be a terminal device in an Internet of Things (IoT) system. IoT is an important component of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-machine interconnection and object-to-object interconnection.

[0148] The various terminal devices described above, if located in a vehicle (e.g., placed inside or installed inside a vehicle), can all be considered in-vehicle terminal devices, also known as on-board units (OBUs). The terminal device of this application can also be an in-vehicle module, in-vehicle component, in-vehicle chip, or in-vehicle unit built into a vehicle as one or more components or units. The vehicle can implement the methods of this application through the built-in in-vehicle module, in-vehicle component, in-vehicle chip, or in-vehicle unit.

[0149] The terminal equipment may sometimes be referred to as UE, terminal, access station, UE station, remote station, wireless communication equipment, or user equipment, etc.

[0150] In this application embodiment, the device used to implement the functions of the terminal device can be the terminal device itself, or it can be a device that supports the terminal device in implementing the functions, such as a chip system, which can be installed in the terminal device. In the technical solutions provided in this application embodiment, the terminal device is used as an example to describe the technical solutions provided in this application embodiment.

[0151] 2. A network device is a network-side device with wireless transceiver capabilities. A network device can be a device, equipment, or module located on the network side of a communication system and possessing corresponding communication functions. A network device typically contains a communication module, circuit, or chip that performs the corresponding communication function. The network device may also be configured with program instructions for performing the corresponding communication function and corresponding program instructions. For example, it may include access network equipment (or access network element, or access network device) and / or core network equipment (or core network element, or core network device). The access network equipment is a device with wireless transceiver capabilities used to communicate with the terminal device. The access network equipment includes, but is not limited to, base stations (base transceiver stations, BTS, Node B, evolved Node B (eNodeB) / eNB, or next-generation Node B (gNodeB) / gNB), transmission reception points (TRPs), base stations evolved under the 3rd generation partnership project (3GPP), access nodes in Wi-Fi systems, wireless relay nodes, and wireless backhaul nodes. The base stations can be macro base stations, micro base stations, pico base stations, small cells, relay stations, etc. Multiple base stations can support networks using the same access technology or networks using different access technologies. A base station can contain one or more co-located or non-co-located transmission and reception points. The access network equipment can also be a radio controller, centralized unit (CU), and / or distributed unit (DU) in a cloud radio access network (CRAN) scenario. The access network equipment can also be a server, etc. For example, network devices in V2X technology can be roadside units (RSUs). The following description of access network devices uses base stations as an example. Base stations can communicate with terminal devices, or they can communicate with terminal devices through relay stations. Terminal devices can communicate with multiple base stations in different access technologies. The core network devices are used to implement functions such as mobility management, data processing, session management, policy and charging. The names of the devices implementing core network functions may differ in systems using different access technologies; this application does not limit this.Taking the 5th generation (5G) mobile communication technology system as an example, the core network equipment includes, for example, AMF, session management function (SMF), policy control function (PCF), or user plane function (UPF), etc.

[0152] In a CU-DU architecture, or in an open RAN (ORAN) system, access network equipment may include one or more logical network elements such as a central unit (CU), control unit (CU), distributed unit (DU), CU-control plane (CP), CU-user plane (UP), or radio unit (RU). CUs and DUs can be separate entities or included in the same network element, such as a baseband unit (BBU). RUs may be included in radio equipment or radio units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs).

[0153] Optionally, the interface between access network devices (such as CU, CU-CP, or CU-UP) in a New Radio (NR) communication system can be an Xn interface. The interface between access network devices and core network devices in NR can be an NG interface. Specifically, the user plane interface between access network devices and core network devices in an NR communication system is NG-u, and the control plane interface is NG-c.

[0154] In long-term evolution (LTE) communication systems, the interface between access network devices can be the X2 interface. Specifically, the user plane interface between access network devices in an LTE communication system can be X2-u, and the control plane interface can be X2-c. In NR communication systems, the X2 interface is mainly used in evolved universal mobile telecommunications system terrestrial radio access-NR dual connectivity (E-UTRA-NR-DC / EN-DC) scenarios, where the master station is an access network device in the LTE communication system, and this master station connects to the core network of the LTE communication system through the X2 interface.

[0155] Figure 1 shows one possible structure for access network equipment. In this structure, core network equipment and access network equipment can communicate via a backhaul link; within the access network equipment, CU and DU can communicate via a midhaul link, and DU and RU can communicate via a fronthaul link.

[0156] In some examples, the CU is a logical node carrying the radio resource control (RRC) layer, service data adaptation protocol (SDAP) layer, packet data convergence protocol (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 can be interfaces such as E2 interfaces. 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 RLC layer and lower layers) through interfaces, which can be interfaces such as F1 interfaces. In some examples, these interfaces (e.g., the F1 interface) can provide control plane (C-Plane) and user plane (U-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. For example, the interface between CU-CP and CU-UP can be an E1 interface. The interface between CU-CP and DU can be an F1-C interface. The interface between CU-UP and DU can be an F1-U interface.

[0157] In some examples, the CU can be split into a central unit-control plane (CU-CP) and a central unit-user plane (CU-UP). The CU-CP is a logical node carrying the RRC layer and the control plane part of PDCP (PDCP-C) layer, used to implement the CU's control plane functions. The 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 network elements, such as the AMF 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. The CU-UP is a logical node carrying the SDAP layer and the user plane part of PDCP (PDCP-U) layer, used to implement the CU's user plane functions. The CU-UP can interact with network elements in the core network used to implement user plane functions. In the core network, network elements used to implement user plane functions, such as the UPF in a 5G system, are responsible for forwarding and receiving data in terminal devices. The above configuration of CU and DU is merely an example; the functions of CU and DU can be configured as needed. For example, CU or DU can be configured to have more protocol layer functions, or 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. Furthermore, the functions of CU or DU can be divided according to service type or other system requirements, such as by latency, placing functions that need to meet low latency requirements in the DU and functions that do not need to meet such latency requirements in the CU.

[0158] In some examples, a DU is a logical node that carries the radio link control (RLC) layer, medium access control (MAC) layer, higher physical layer (Higher PHY) layer, and other functions. In some examples, a 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.

[0159] In some examples, the RU is a logical node carrying both lower physical layer (PHY) and radio frequency (RF) processing. In some examples, the RU can be a 3GPP transmission reception point (TRP), a remote radio head (RRH), or other similar entities. 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.

[0160] 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-control, user, and synchronization (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.

[0161] The above CU and DU configurations are merely examples; the functions of the CU and DU can be configured as needed. For instance, the CU or DU can be configured to have more protocol layer functions, or only some protocol layer processing functions. For example, 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. Furthermore, the functions of the CU or DU can be divided according to service type or other system requirements, such as by latency. Functions that require low latency can be placed in the DU, while functions that do not require low latency can be placed in the CU.

[0162] 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.

[0163] Alternatively, another structure for the access network device can be seen in Figure 2, which illustrates an access network device implemented using an open RAN architecture. Figure 2 is a schematic diagram of the application framework involving the RIC module under the O-RAN architecture. This communication system includes a RAN intelligent controller (RIC). The RIC includes near-real-time RIC (near-RT RIC) and non-real-time RIC (non-RT RIC).

[0164] Near real-time (NRT) RICs are used for model training and inference. For example, they are used to train AI models and then use those models for inference. NRT RICs can obtain network-side and / or terminal-side information from RAN nodes (e.g., CUs, CU-CPs, CU-UPs, DUs, and / or RUs) and / or terminals. This information can be used as training data or inference data. Optionally, the NRT RIC can deliver inference results to RAN nodes and / or terminals. Optionally, inference results can be exchanged between CUs and DUs, and / or between DUs and RUs. For example, the NRT RIC delivers inference results to a DU, which then forwards them to an RU.

[0165] Non-real-time RICs are used for model training and inference. For example, they are used to train AI models and then use those models for inference. Non-real-time RICs can obtain network-side and / or terminal-side information from RAN nodes (e.g., CUs, CU-CPs, CU-UPs, DUs, and / or RUs) and / or terminals. This information can be used as training data or inference data, and the inference results can be delivered to RAN nodes and / or terminals. Optionally, inference results can be exchanged between CUs and DUs, and / or between DUs and RUs; for example, a non-real-time RIC delivers inference results to a DU, which then forwards them to an RU.

[0166] Near real-time RICs and non-real-time RICs can also be configured as separate network elements. Optionally, the near real-time RICs and non-real-time RICs can also be part of other devices. For example, the near real-time RIC can be set in the RAN node (e.g., in the CU or DU), while the non-real-time RIC can be set in the operation administration and maintenance (OAM) (commonly known as network management) or service management and orchestration framework (SMO), cloud server, core network equipment, or other network equipment.

[0167] In a communication system, network elements are connected via interfaces (e.g., NG, Xn) or over-the-air interfaces. These network element nodes, such as core network equipment, access network nodes (RAN nodes), terminals, or one or more devices in the OAM, are equipped with one or more AI modules (only one is shown in the figure for clarity). The access network node can be a single RAN node or can include multiple RAN nodes, for example, including CU and DU. The CU and / or DU can also be equipped with one or more AI modules. Optionally, the CU can be further divided into CU-CP and CU-UP. One or more AI models are configured in the CU-CP and / or CU-UP.

[0168] AI modules are used to implement corresponding AI functions. AI modules deployed in different network elements can be the same or different. Depending on the parameter configuration, the AI ​​module can implement different functions. The AI ​​module model can be configured based on one or more of the following parameters: structural parameters (e.g., at least one of the following: number of neural network layers, neural network width, inter-layer connections, neuron weights, neuron activation function, or biases in the activation function), input parameters (e.g., the type and / or dimension of the input parameters), or output parameters (e.g., the type and / or dimension of the output parameters). The biases in the activation function can also be referred to as the neural network biases.

[0169] An AI module can have one or more models. A model can infer an output, which includes one or more parameters. The learning, training, or inference processes of different models can be deployed on different nodes or devices, or they can be deployed on the same node or device.

[0170] Optionally, the interface between the Non-RT RIC and the Near-RT RIC can be an A1 interface, which is used for intelligent and dynamic control of radio resources within the O-RAN. The Non-RT RIC provides policies, rich information, and ML model updates to the Near-RT RIC through the A1 interface, while the Near-RT RIC provides policy feedback to the Non-RT RIC through the A1 interface.

[0171] Optionally, the interface used to connect the Near-RT RIC and the RAN node can be an E2 interface, which is an open interface between two endpoints. RAN nodes include, for example, CU and DU in 5G, O-RAN compatible eNB in ​​4G, O-CU (O-CU-CP and / or O-CU-UP) and / or O-DU in O-RAN, etc. The RIC can obtain RAN node data collection and feedback through the E2 node, and the RAN node can obtain control feedback from the Near-RT RIC through the E2 node.

[0172] Optionally, the interface between the management entity in the SMO and the O-RAN module can be the O1 interface. The O1 interface is used for operation management, enabling FCAPS management, software management, and file management. The interface between the SMO and the infrastructure management framework that supports O-RAN virtual network functions can be the O2 interface.

[0173] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called an open CU (O-CU), DU can also be called an open DU (O-DU), CU-CP can also be called an open CU-CP (O-CU-CP), CU-UP can also be called an open CU-UP (O-CU-CP), and RU can also be called an open RU (O-RU). For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples in its embodiments. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in the embodiments of this application can be implemented through software modules, hardware modules, or a combination of software modules and hardware modules.

[0174] In this application embodiment, the device used to implement the function of the network device can be the network device itself, or it can be a device that supports the network device or network element to implement the function, such as a chip system, which can be installed in the network device. In the technical solutions provided in the embodiments of this application, the device used to implement the function of the network device is a network device (for example, the device used to implement the function of the access network device is an access network device, and the device used to implement the function of the core network device is a core network device) to describe the technical solutions provided in the embodiments of this application.

[0175] 3. Resources, including time-domain resources and / or frequency-domain resources.

[0176] Temporal resources include symbols, slots, mini-slots, partial slots, sub-frames, radio frames (or frames), or sensing slots.

[0177] A time slot can include at least one symbol, such as 14 symbols or 12 symbols. There can be different time slot types, and different time slot types include different numbers of symbols. For example, a mini slot contains less than 7 symbols, 2 symbols, 3 symbols, 4 symbols, etc., while a regular time slot contains 7 symbols or 14 symbols, etc.

[0178] For time-domain resources, in addition to the examples above, other time units are also included, and there are no restrictions on them.

[0179] Depending on the subcarrier spacing, the length of each symbol can vary, and therefore the time slot length can also vary. For example, a time slot with a subcarrier spacing of 15 kHz has a length of 0.5 ms, a time slot with a subcarrier spacing of 60 kHz has a length of 0.125 ms, and so on.

[0180] Frequency domain resources include sub-channels, bands, carriers, bandwidth parts (BWP), resource blocks (RBs), or resource pools.

[0181] A subchannel may include one or more resource blocks (RBs). The bandwidth of a wireless communication system in the frequency domain may include multiple RBs. For example, in the various possible bandwidths of an LTE system, the number of physical resource blocks (PRBs) may be 6, 15, 25, 50, etc. In the frequency domain, an RB may include several subcarriers. For example, in LTE and NR systems, an RB includes 12 subcarriers, where each subcarrier is spaced at 15 kHz. Other subcarrier spacings, such as 3.75 kHz, 30 kHz, 60 kHz, or 120 kHz, can also be used; no limitation is made here. A subcarrier or resource element (RE) refers to the smallest frequency resource unit on a specific symbol in a multi-carrier system. In the embodiments of this application, an RE may refer to a resource unit of time-frequency resources, such as the smallest time-frequency resource unit. For example, one RE occupies one symbol in the time domain and one subcarrier in the frequency domain. That is, one subcarrier within one symbol in the time domain is one RE.

[0182] In addition to the examples above, frequency domain resources also include other frequency domain units, and there are no restrictions on this.

[0183] 4. Passive Radio Frequency Identification (RFID) systems consist of an interrogator / reader and a tag (or simply tag, such as an electronic tag). The reader reads information from the tag or writes information to the tag. Non-contact data communication occurs between the reader and the tag. The tag has simple functionality, requiring excitation from the reader to send information; that is, the tag converts the wireless signal emitted by the reader into energy to power itself. Tags support microwatt-level or even hundreds of microwatt-level power consumption, limiting their ability to support complex designs.

[0184] If RFID is applied to mobile communication systems, such as 5G systems, then base stations can act as readers, fulfilling their functions—an example of AIoT. The reader can interact with electronic tags to manage them. The primary application of RFID is identification, but it can also be used for data reading and writing.

[0185] 5. AIoT technology.

[0186] AIoT technology, defined by 3GPP, is an extremely low-power, low-complexity IoT technology that can be understood as an extension of Radio Frequency Identification (RFID) within 3GPP. While AIoT shares some principles with RFID, such as similar inventory management processes, 3GPP aims to introduce more valuable application scenarios. AIoT technology is based on cellular network communication infrastructure, and its main services include inventory management, location tracking, and sensor reporting. Typical application scenarios include logistics, warehousing, industrial manufacturing, identity verification, and environmental monitoring.

[0187] AIoT devices are devices within the Internet of Things (IoT) system.

[0188] 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 microwatt (μ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.

[0189] 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.

[0190] 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.

[0191] 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.

[0192] In AIoT, AIoT devices (such as tags) can communicate with readers. Through this communication, 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.

[0193] 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.

[0194] 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.

[0195] 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.

[0196] The 3GPP plenary meeting defined an extremely low-power, extremely low-complexity Internet of Things (IoT) technology. It can be understood as an extension of RFID in 3GPP. Although it shares some principles with RFID, such as similar inventory management processes, it introduces more value scenarios in 3GPP.

[0197] A-IoT is based on cellular network communication infrastructure and consists of readers (such as base stations) and passive / semi-passive / active A-IoT terminals (A-IoT terminals are terminals in the cellular network, which can be understood as IoT terminals with extremely low power consumption and extremely low complexity). Its main services include: inventory, positioning, sensing, command, etc.; typical application scenarios include logistics, warehousing, industrial manufacturing, identity recognition, environmental monitoring, etc.

[0198] The following examples illustrate various AIoT services.

[0199] 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.

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

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

[0202] 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.

[0203] 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.

[0204] 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.

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

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

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

[0208] 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.

[0209] The above are just examples. Other business processes or operations can be performed between the tag and the reader, which will not be illustrated here.

[0210] 6. Classification of AIoT devices.

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

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

[0213] 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.

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

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

[0216] 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.

[0217] 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.

[0218] 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.

[0219] Device 2a: Peak power consumption less than or equal to several hundred μW, with energy storage function, initial sampling frequency offset (SFO) reaching 10X ppm, capable of DL and / or UL signal amplification. Requires an external carrier signal for backscatter communication for uplink transmission.

[0220] Device 2b: Peak power consumption less than or equal to several hundred μW, with energy storage function, initial sampling frequency offset (SFO) reaching 10X ppm, and capable of DL and / or UL signal amplification. The device can perform uplink transmission without relying on an externally provided carrier.

[0221] 7. AIoT device access process.

[0222] The following describes the access stratum (AS) process between AIoT devices and readers. Please refer to Figure 3. Figure 3 illustrates the process using an AIoT device as an example.

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

[0224] The term "AIoT paging message" can be replaced with "(initial) trigger message" or "paging message," or any other name. For simplicity, no restrictions are imposed.

[0225] Step B: D2R Data Transmission. The triggered AIoT device performs AIoT device ID transmission via or without the AIoT random access procedure (e.g., contention-free resolution). For example, the AIoT device sends its ID to the reader.

[0226] Step C: Data transmission. Step C may include steps C1 and C2 as follows.

[0227] Step C1: Possible R2D data transmission (e.g., for sending commands, such as read, write, lock, deactivate, sensor, etc.).

[0228] Step C2: Possible D2R data transfer (e.g., responses to commands, such as data read by a read command, success / failure feedback for a write command, etc.).

[0229] The process shown in Figure 3 above can support inventory and command application scenarios in the following ways:

[0230] For the "inventory-only" scenario, the baseline solution may include steps A and B as described above.

[0231] For the "inventory and command" scenario, the baseline scheme may include steps A, B, C1 and C2 as described above.

[0232] For the "command-only" scenario, a solution that includes steps A, B, C1, and C2 as a baseline can also be supported. Furthermore, another candidate solution supporting this scenario is as follows:

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

[0234] Step C2: Perform possible D2R data transmission (e.g., transmit the ID of the AIoT device or a corresponding response to a command) with or without the AIoT random access procedure.

[0235] The following are examples illustrating the content of each of the above sections.

[0236] Part 1: A-IoT Paging

[0237] At the AS layer (access layer), the A-IoT paging function indicates which device needs to respond.

[0238] For A-IoT paging messages, an identifier may be required to identify the device / group of devices included or associated with this triggering message (e.g., a single device, a group of devices, or all devices).

[0239] Optionally, an A-IoT paging message may include a single A-IoT device ID.

[0240] Optionally, the A-IoT paging message includes a group ID mapped to multiple A-IoT devices.

[0241] Optionally, an A-IoT paging message without any identifier is an A-IoT paging message that instructs all A-IoT devices capable of receiving the message to respond.

[0242] Optionally, an A-IoT paging message containing multiple A-IoT device identifiers.

[0243] Optionally, for A-IoT paging messages, it can also indicate that the device can determine, based on this information, the resources (such as time-domain and / or frequency-domain resources) to be used for D2R response messages.

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

[0245] Part Two: Random Access to A-IoT

[0246] The A-IoT random access procedure is used for A-IoT devices to access the network for data transmission.

[0247] A-IoT random access is triggered by a reader, including access triggered by a single A-IoT device, a group of A-IoT devices, or all A-IoT devices under the reader's coverage. Optionally, the slotted-ALOHA protocol serves as the baseline for the A-IoT random access process. The slotted-ALOHA protocol divides time into fixed time slots, each with a length equal to the transmission time of one data frame. AIoT devices can only transmit data at the beginning of a fixed time slot, thereby reducing the probability of AIoT device collisions.

[0248] When an A-IoT device responds to a paging message, it performs the following process:

[0249] Step 1: Determine the random access type and access timing / resources.

[0250] If random access is contention-free access:

[0251] Select the appropriate D2R timing / resources;

[0252] Skip the race resolution in step 2 and proceed to step 3 to perform data transmission.

[0253] If it is contention-based random access:

[0254] Determining / selecting the timing / resources for access, such as random selection;

[0255] Step 2 of the competition resolution procedure.

[0256] Step 2: Contention-based random access contention resolution.

[0257] The contention solution can include the following two options.

[0258] Option 1: A-IoT Msg1 has no data.

[0259] A-IoT Msg1: When an A-IoT device recognizes the start of its access occasion, it sends a random ID generated by the A-IoT device to the reader.

[0260] Optionally, there is currently no conclusion on how A-IoT devices should generate random IDs, such as through random generation or generation based on the device ID. The size of the random ID can also be unrestricted, for example, a 16-bit random number.

[0261] A-IoT Msg2: The reader's response indicating a successfully received random ID.

[0262] If the A-IoT device receives A-IoT Msg2 containing a random ID, and that random ID is the same as the one previously sent in A-IoT Msg1, then the race condition is considered resolved successfully.

[0263] Optionally, A-IoT Msg2 is used for contention resolution because it is assumed that the size of the random ID in A-IoT Msg1 should be sufficient for contention resolution purposes. It is a sufficiently low probability that A-IoT devices choosing the same access timing / resources will send the same random ID value in A-IoT Msg1, and the range of random ID values ​​can be considered sufficiently large.

[0264] Option 2: A-IoT Msg1 has data.

[0265] A-IoT Msg1: When an A-IoT device recognizes the start of its own access event, it sends A-IoT Msg1 containing upper-layer data, which can be the device ID and / or any other upper-layer data. Optionally, in Scheme 2, the A-IoT Msg1 may or may not include a random ID.

[0266] A-IoT Msg2: The reader can respond with the successfully received random ID and / or device ID (partial or complete) and / or ACK, or it can choose not to respond. If Msg1 does not receive a signal indicating failure, reconnection, or retransmission, it is considered that the access is successful, the data transmission is successful, or the service is successful.

[0267] If an A-IoT device receives an A-IoT Msg2 containing a random ID and / or a device ID (partial or complete) and / or an ACK, and this information is a part of the previously sent information in A-IoT Msg1 or information generated based on A-IoT Msg1 (e.g., a hash function on msg1), then the A-IoT device considers the race condition to be resolved successfully.

[0268] Step 3: Data transmission.

[0269] If contention-based random access is used, or if contention-free access is used, the A-IoT device can perform upper-layer data transmission with the reader after it considers the contention to be resolved successfully. The upper-layer data transmission may be the device ID and / or any other upper-layer data (if any).

[0270] In step 3, it can be understood that subsequent R2D transmissions after a D2R transmission do not always need to be sent. The use / existence of subsequent R2D transmissions requires further research; for example, handling retransmissions or reconnection after a D2R transmission failure could be considered.

[0271] Therefore, the above does not provide a specific mechanism for allocating time-domain resources to AIoT devices.

[0272] In view of this, embodiments of this application provide a communication method that can instruct an AIoT device with timing capabilities to use a non-first time domain resource among X time domain resources, enabling the AIoT device with timing capabilities to select a non-first time domain resource among the X time domain resources to transmit messages during the access process. Thus, a mechanism for allocating time domain resources for AIoT devices with timing capabilities is provided.

[0273] The communication methods provided in the various embodiments of this application can be applied to fourth-generation (4G) communication systems, such as LTE communication systems, as well as fifth-generation (5G) communication systems, such as 5G NR communication systems, or various communication systems evolved after 5G, such as future communication systems. The methods provided in the embodiments of this application can also be applied to Bluetooth systems, wireless fidelity (Wi-Fi) systems, long-range radio (LoRa) systems, or vehicle-to-everything (V2X) systems. The methods provided in the embodiments of this application can also be applied to terrestrial networks (TN) and non-terrestrial networks (NTN), such as satellite communication systems. For example, they can be applied to transparent satellite architectures, backhaul satellite architectures, or regenerative satellite architectures, etc., without limitation.

[0274] The communication system to which the communication method of the embodiments of this application is applicable will be described below with reference to the accompanying drawings.

[0275] Figures 4 to 8 are schematic diagrams of five communication systems applicable to embodiments of this application, which are also several network topologies of AIoT technology.

[0276] Figure 4 shows topology 1. In topology 1, AIoT devices communicate directly and bidirectionally with network devices (such as access network devices). Communication between network devices and AIoT devices includes the transmission of AIoT data and / or signaling. The network device can act as a reader / writer.

[0277] Figure 5 shows Topology 2. In Topology 2, an intermediate node exists between the AIoT device and network devices (such as access network devices). The AIoT device and network device can communicate bidirectionally through this intermediate node, which can transmit AIoT data and / or signaling between the network device and the AIoT device. In Topology 2, the intermediate node can be a repeater, an integrated access and backhaul (IAB) node, a UE, or other devices, enabling AIoT technology implementation. This intermediate node can also function as a reader / writer.

[0278] Figures 6 and 7 both illustrate Topology 3. In Topology 3, AIoT devices send AIoT data and / or signaling to network devices (such as access network devices) and can receive AIoT data and / or signaling from auxiliary nodes, as shown in Figure 6; alternatively, AIoT devices can receive AIoT data and / or signaling from network devices and send AIoT data and / or signaling to auxiliary nodes, as shown in Figure 7. In Topology 3, auxiliary nodes can be repeaters, IAB nodes, UEs, or other devices capable of implementing AIoT technology. The network device can function as a reader / writer.

[0279] Figure 8 shows topology 4. In topology 4, the AIoT device and the UE communicate bidirectionally. The communication between the UE and the AIoT device includes AIoT data and / or signaling. The UE can act as a reader / writer.

[0280] In this context, the network device shown in any of the attached figures 4 to 7 is, for example, an access network device, such as a base station.

[0281] Please refer to Figure 9, which is a schematic diagram of the logical system architecture of Topology 1. As shown in Figure 9, AIoT RAN and AIoT CN can communicate through the next generation (NG) interface. NGAP is the control plane protocol of the NG interface. One possible implementation of "NGAP" is to include AIoTF information / cells in NGAP. Another possible implementation is to carry a newly defined protocol layer on top of the NGAP protocol.

[0282] The AIoT-related processes are defined on NGAP as shown in Figure 10. Figure 10 includes the protocol stack between the AIoT device, the AIoT radio access network (RAN), and the AIoT core network (CN). 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 illustrated in Figures 9 and 10. The AIoT device communicates with the AIoT RAN's AIoT radio protocol layer through AIoT radio protocol layers. The NGAP layer of the AIoT RAN communicates with the NGAP 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) of the AIoT RAN communicates with the L2 of the AIoT CN, and the L1 of the AIoT RAN communicates with the L1 of the AIoT CN.

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

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

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

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

[0287] Topology 2 supports three approaches: a radio resource control (RRC) based solution, a non-access stratum (NAS) based solution, and a user plane (UP) based solution.

[0288] solution1: RRC based solution.

[0289] 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 the NG AP, the base station further sends the relevant information to the A-IoT-enabled UE via an RRC message. 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 the NG AP / NGAP.

[0290] For an RRC-based solution, a possible protocol stack can be found in Figure 14. Figure 14 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 radio link control (RLC) layer of the AIoT-enabled UE communicates with the RLC layer of the AIoT-enabled gNB, the media access control (MAC) layer of the AIoT-enabled UE communicates with the MAC layer of the AIoT-enabled gNB, and the physical (PHY) layer of the AIoT-enabled UE communicates with the physical layer of the AIoT-enabled gNB. The NGAP layer of the AIoT-enabled gNB communicates with the NGAP 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 layer 2 (L2) of the AIoT-enabled gNB communicates with the L2 of the AIoT CN, and the L1 of the AIoT-enabled gNB communicates with the L1 of the AIoT CN.

[0291] Among them, the NG interface is the NG-C interface (i.e., the NG control plane interface). One possible implementation of "NG AP" 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.

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

[0293] (1) A direct connection diagram of AIoT-enabled gNB and AIoTF is shown in Figure 15 (AIoTF in Figure 15 can be replaced with A-IoT CN).

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

[0295] solution 2: NAS based solution.

[0296] 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.

[0297] Figure 17 shows a possible protocol stack for a NAS-based solution.

[0298] solution 3: UP based solution.

[0299] 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.

[0300] Figure 18 shows a possible protocol stack diagram for an UP-based solution.

[0301] Optionally, for topology 2 or topology 4, “AIoT-enabled UE” (e.g., the AIoT-enabled UE shown in Figure 13) can also be replaced with “UEreader”, “intermediate UE”, or “intermediate node”, etc.

[0302] 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.

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

[0304] 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.

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

[0306] 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.

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

[0308] 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.

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

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

[0311] 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.

[0312] 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.

[0313] Optionally, the aforementioned "access opportunity" can 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.

[0314] 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.

[0315] 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.

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

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

[0318] 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.

[0319] The method provided in the embodiments of this application is described below with reference to the accompanying drawings. In the accompanying drawings corresponding to the various embodiments of this application, all steps indicated by dashed lines are optional steps.

[0320] The various embodiments of this application can be applied to the network architecture shown in any of the figures 4 to 18. For example, the reader / writer described in various embodiments of this application can be an AIoT-enabled UE (such as the AIoT-enabled UE in the above-described Topology 2 or Topology 4 architecture), an IoT-enabled UE, an intermediate node, a UE reader, an access network device, or an AIoT RAN (such as the AIoT RAN in the above-described Topology 1 or Topology 3), etc. The reader / writer can be any of the network devices shown in Figures 4 to 7 (such as access network devices), or the intermediate node shown in Figure 5, or the UE shown in Figure 8, or any of the AIoT RANs shown in Figures 9 to 12, or any of the AIoT-enabled UEs shown in Figures 13 to 18; the AIoT device described in various embodiments of this application (such as one or more AIoT devices, a first AIoT device, a second AIoT device, or a third AIoT device) can be any of the AIoT devices shown in Figures 4 to 18; the core network device described in various embodiments of this application can be an AIoT core network device, which serves the AIoT device, for example, the core network device is the AIoT shown in Figures 9, 10, 13, and 14. CN, the AIoTF shown in Figures 11, 12, 15, 16, 17, or 18, or the AMF shown in Figure 12 or 16; the access network device described in various embodiments of this application can be a base station, CU, and / or DU, etc., for example, the access network device is any of the network devices shown in Figures 4, 6 to 8, or any of the AIoT RANs shown in Figures 9 to 12, or any of the AIoT-enabled base stations shown in Figures 14 to 18. The AIoT RAN described in various embodiments of this application can be any of the AIoT RANs shown in Figures 9 to 13.

[0321] This application provides a first communication method. The method flowchart shown in Figure 19 will be described below.

[0322] S1901, The reader sends a first message. In this embodiment, the example is that the first AIoT device receives a first message from the reader.

[0323] For example, the reader can send a first message after receiving a service request from a core network device or an access network device. The service request is used to request the execution of this (or this round) AIoT service, such as an inventory request. The reader can receive the service request from the core network device through the access network device.

[0324] Optionally, the service request may carry a mask for the AIoT device performing this AIoT service. The mask may be a portion of the identifier of the AIoT device performing this AIoT service. For example, the mask may be a portion of the electronic product code (EPC).

[0325] For example, please refer to Figure 20 for an example of an AIoT device identifier. The AIoT device identifier includes a first part and a second part. As shown in Figure 20 (1), the AIoT device identifier includes a first part, such as the device type ID, network ID, and third-party organization ID, and a second part, such as EPC. Among them, the third-party organization ID is optional and is shown in Figure 20 (1) with a dashed box. The device type ID indicates the type of the AIoT device. The network identifier includes the public land mobile network identity (PLMN ID) and / or the network identity (NID). The PLMN ID uniquely identifies the public land mobile network to which the AIoT device is located. The NID indicates a sub-network or a specific area network within a network and can be defined by the operator. The third-party organization ID indicates the third-party organization corresponding to the AIoT device, such as the manufacturer. EPC is a globally unique identifier based on RFID technology used to identify physical objects (such as products, items, or assets). For example, a service request can carry a part of the EPC. After the reader obtains the service request, it can notify the AIoT device whose part of the EPC is masked to access the network. Alternatively, as shown in Figure 20(2), the identifier of an AIoT device includes a first part, such as the device type ID and the third-party organization ID, and a second part, such as EPC. The third-party organization ID is optional and is shown in a dashed box in Figure 20(2).

[0326] In one possible implementation, the reader can also receive a third message from a core network device or an access network device. Optionally, the third message can be carried in the service request, or it can be a message different from the service request; this is not limited. The third message indicates that some or all of the AIoT devices required to perform the AIoT service support timing capabilities, which is equivalent to the third message indicating the capabilities required to perform the AIoT service. In this embodiment, the AIoT devices required to perform the AIoT service include a first AIoT device. Under this assumption, the third message is equivalent to indicating that the first AIoT device supports timing capabilities. Optionally, if the AIoT devices required to perform the AIoT service also include a second AIoT device, then the third message is equivalent to also indicating that the second AIoT device does not support timing capabilities.

[0327] In one possible implementation, the reader / writer can also receive a tenth message from a core network device or an access network device. This tenth message instructs the inventory report not to carry the PLMN ID and / or NID of the AIoT device performing this service. For example, the tenth message includes first information instructing the inventory report not to carry the PLMN ID and / or NID of the AIoT device performing this service. For instance, if the AIoT device performing this service includes a first AIoT device, then the tenth message is equivalent to instructing the inventory report not to carry the PLMN ID and / or NID of the first AIoT device. And, if the AIoT device performing this service also includes a second AIoT device, then the tenth message is equivalent to also instructing the inventory report not to carry the PLMN ID and / or NID of the second AIoT device. Optionally, the tenth message can be a paging message. Optionally, the tenth message can be carried in the service request. Alternatively, the tenth message can be a message different from the service request. Optionally, the tenth message and the third message can be the same message or different messages; this is not limited.

[0328] The reader / writer can send the first message via broadcast, multicast, or unicast. The first message can be a paging message, an R2D trigger message, or a proprietary message, without limitation. The paging message can be an initial trigger message, an initial trigger indication, or an initial downlink (DL) trigger message.

[0329] Paging messages can be triggered by core network elements (such as AMF, AIoTMF, or AIoTF, etc.). For example, a core network element sends a service request or paging message to the reader, and the reader sends a paging message based on the service request or paging message.

[0330] For example, when the reader / writer is an access network device, the paging message can be used to instruct the AIoT device to access the network. Alternatively, when the reader / writer is a terminal device, the paging message can be used to instruct the AIoT device to access the terminal device; optionally, the AIoT device can access the network through the terminal device. Optionally, the paging message can also be used to trigger / instruct the AIoT device to send uplink data, or to trigger / instruct / request the AIoT device to perform AIoT services, wherein the AIoT services can include at least one of the following: paging services, inventory services, command services (such as read, write, deactivate, lock, etc.), positioning services, or sensing services. The paging message can be carried (or transmitted) in MAC layer signaling, such as in a MAC control element (CE), MAC service data unit (SDU), or MAC protocol data unit (PDU). Optionally, the MAC layer can also be replaced by "AIOT access stratum (AS) layer signaling."

[0331] R2D trigger messages include queries or queryreps. A query is also known as an access round indication / trigger. A query can also be known as an access occasion indication / trigger.

[0332] The first message can indicate the content shown in A1 below. Optionally, the first message can also indicate the content shown in A2 and / or A3 below, which are described in detail below.

[0333] A1. The first message indicates that AIoT devices supporting timing capabilities should use a non-first time domain resource from among X time domain resources. Thus, AIoT devices supporting timing capabilities can select the appropriate time domain resource for access based on the first message.

[0334] Instructing an AIoT device that supports timing capabilities to use a non-first time domain resource among X time domain resources can also be described as: instructing an AIoT device that supports timing capabilities to send the sixteenth message using a non-first time domain resource.

[0335] The first message can be an implicit or explicit indication that an AIoT device supporting timing capabilities is using a non-first time domain resource among X time domain resources, and there is no limitation on this.

[0336] For example, if the first field in the first message takes the first value, it means that the first message instructs the AIoT device supporting timing capabilities to use a non-first time domain resource among X time domain resources. Alternatively, if the first field in the first message takes the second value, it means that the first message does not instruct the AIoT device supporting timing capabilities to use a non-first time domain resource among X time domain resources. As another example, if the first message includes the first field, it means that the first message instructs the AIoT device supporting timing capabilities to use a non-first time domain resource among X time domain resources. Alternatively, if the first message does not include the first field, it means that the first message does not instruct the AIoT device supporting timing capabilities to use a non-first time domain resource among X time domain resources.

[0337] The number of AIoT devices supporting timing capabilities can be one or more, and there is no limit to the number. Supporting timing capabilities can be understood as, or alternatively described as, having a timing function, possessing or having timing capabilities, having (or possessing) the ability to measure or calculate time, being able to sense time, being able to send the sixteenth message in any of X time-domain resources, or being able to respond to messages carrying (or indicating) multiple time-domain resources (such as paging messages). The capabilities involved in the various embodiments of this application can be replaced with functions or features, and "supporting" can also be replaced with "possessing" or "being able to."

[0338] The sixteenth message is a message during the AIoT device's access to the reader / writer process, such as a message in the random access process, specifically like the first message in the random access process, for example, the sixteenth message might be Msg1, or as shown in Figure 3, without limitation. As the standard evolves, the sixteenth message may have other names, which are also not limited. The sixteenth message is used to request AIoT device access and can also be called the AIoT sixteenth message. Optionally, the sixteenth message may carry all or part of the identifier of the AIoT device requesting access, or it may carry a random identifier (or random access ID). The random identifier can be generated based on the AIoT device's identifier, or it can be randomly generated, for example, it can be a 16-bit number. Optionally, the sixteenth message may also carry data sent by the AIoT device, such as uplink data.

[0339] Here, X time-domain resources can be one or more time-domain resources, meaning the value of X can be equal to or greater than 1, without limitation. When X is an integer greater than 1, the X time-domain resources can be continuous or discontinuous in time, without limitation. This application embodiment mainly uses the example of X being an integer greater than 1 for description, for example, the value of X can be 2, 3, 4, or 5, etc.

[0340] The X time-domain resources are the time-domain resources determined during the R2D transmission-triggered random access process for transmitting the sixteenth message. In short, X time-domain resources are used to transmit the sixteenth message. These X time-domain resources can also be referred to as X access opportunities, X chances, or access slots, etc. Each access opportunity allows an AIoT device to send at least one of the following: access (request), contention resolution, or data transmission. Optionally, the X time-domain resources include some or all of the time-domain resources used by W AIoT devices to transmit the sixteenth message. The W AIoT devices are the AIoT devices executing this AIoT service, where W is a positive integer, and its value can be 1 or an integer greater than 1. For example, if executing this AIoT service is expected to require 3 AIoT devices, then the X time-domain resources include the time-domain resources used by these 3 AIoT devices to transmit the sixteenth message. Alternatively, the X time-domain resources include the time-domain resources used by 2 of these 3 AIoT devices to transmit the sixteenth message. This section introduces W AIoT devices to illustrate the scope of X time-domain resources. However, for the reader / writer, before paging an AIoT device, it may not know the exact number of AIoT devices required to execute the current AIoT service; that is, the reader / writer may not be certain of the value of W. Of course, the reader / writer may also be certain of the value of W, and this is not a limitation.

[0341] For example, X time-domain resources can be the time-domain resources used by W AIoT devices to transmit the sixteenth message, or the time-domain resources used by some of the W AIoT devices to transmit the sixteenth message, or the time-domain resources used by R AIoT devices to transmit the sixteenth message. The R AIoT devices include W AIoT devices, where R is an integer greater than or equal to W. The R AIoT devices include AIoT devices executing multiple AIoT services. The number of multiple AIoT services can be, for example, the number of AIoT services executed within a time window, or a preset number, or a number predefined by the protocol.

[0342] For example, the number of multiple AIoT services can be two. The current AIoT service is expected to be executed by 10 AIoT devices, and the next AIoT service is expected to be executed by 5 AIoT devices. Then, R AIoT devices would be 15 AIoT devices. Correspondingly, X time domain resources can include the time domain resources of 15 AIoT devices for transmitting the sixteenth message.

[0343] A non-first time-domain resource among X time-domain resources can be understood as a time-domain resource that is not the first (or the first time-domain resource) among X time-domain resources, or a time-domain resource that belongs to X time-domain resources other than the first time-domain resource, such as a time-domain resource other than the first time-domain resource among X time-domain resources. The index of the X time-domain resources can be predefined by the protocol, determined through negotiation between the reader / writer and the AIoT device, or configured by the core network device; there are no restrictions on this.

[0344] In the first possible implementation, the first time-domain resource is the time-domain resource with the smallest index among the X time-domain resources, and the non-first time-domain resources are the time-domain resources whose index is not the smallest among the X time-domain resources.

[0345] For example, Figure 21 illustrates X time-domain resources. As shown in Figure 21 (1), the X time-domain resources include 3 time-domain resources. The indices of these 3 time-domain resources are 0, 1 and 2 respectively. Then the first time-domain resource is the time-domain resource with index 0, and the non-first time-domain resources can be the time-domain resource with index 1 or the time-domain resource with index 2.

[0346] The second possible implementation is that the first time-domain resource is the time-domain resource with the earliest start time (or start time) among the X time-domain resources, and the non-first time-domain resources are time-domain resources with a start time that is not the earliest among the X time-domain resources.

[0347] For example, as shown in Figure 21(2), there are X time-domain resources, including two time-domain resources, such as the time-domain resource with index 1 and the time-domain resource with index 2. The start time of the time-domain resource with index 1 is earlier than the start time of the time-domain resource with index 2. Then the first time-domain resource can be the time-domain resource with index 1, and the non-first time-domain resource can be the time-domain resource with index 2.

[0348] Optionally, the time-domain resource at the start time among the X time-domain resources can be the time-domain resource with the smallest index among the X time-domain resources. In this case, the first time-domain resource is the time-domain resource with the smallest index among the X time-domain resources, and it is also the time-domain resource at the start time among the X time-domain resources.

[0349] A2, X time-domain resources. In this case, the first message both instructs the AIoT device with timing capabilities to use a non-first time-domain resource among the X time-domain resources, and also instructs the X time-domain resources.

[0350] For example, the first message includes information about X time-domain resources, such as indexes of the X time-domain resources, or indexes of multiple time-frequency resources corresponding to the X time-domain resources. Time-frequency resources include both time-domain and frequency-domain resources. The indexes of the X time-domain resources or multiple time-frequency resources can be predefined by the protocol, determined through negotiation between the reader / writer and the AIoT device, or configured by the core network device; there are no restrictions on this. For example, the first field in the first message may have a first value, which indicates that the AIoT device supporting timing capabilities uses a non-first time-domain resource among the X time-domain resources, and the first message may include a second field, which indicates the index of the X time-domain resources.

[0351] In another possible implementation, the X time-domain resources may be indicated by the fifteenth message (or message #1). The fifteenth message may be different from the first message. The fifteenth message may be, for example, a paging message, an R2D trigger message, or a proprietary message, etc., and is not limited thereto. The fifteenth message may be sent before or after the first message. For example, if the first message is a paging message and the fifteenth message is an R2D trigger message, in which case the fifteenth message may be sent after the first message. Alternatively, if the first message is an R2D trigger message and the fifteenth message is a paging message, in which case the fifteenth message is sent before the first message. Or, both the first message and the fifteenth message may indicate X time-domain resources to improve the reliability of indicating the X time-domain resources.

[0352] Optionally, the time when an AIoT device (such as a second AIoT device or a first AIoT device) receives a message (such as a first message or a fifteenth message) indicating X time-domain resources is related to the start time of the first time-domain resource. For example, the time when the first AIoT device receives the first message or the fifteenth message is the start time of the first time-domain resource, or the time difference between the time when the first AIoT device receives the first message or the fifteenth message and the start time of the first time-domain resource is less than or equal to a first threshold. The first threshold may be predetermined by the protocol. Alternatively, the start time of the first time-domain resource is related to the time when the reader sends the first message or the fifteenth message, for example, the time interval between the start time of the first time-domain resource and the time when the reader sends the first message or the fifteenth message is a first duration. The first duration may be predetermined by the protocol. Alternatively, the start time of the first time-domain resource and the time when the reader sends the first message or the fifteenth message are located in two adjacent time slots. For example, the time when the reader sends the first message or the fifteenth message is located in time slot 1, and the start time of the first time-domain resource is located in time slot 2.

[0353] A3. AIoT devices that do not support timing capabilities will preferentially use the first time domain resource among X time domain resources. In this case, the first message instructs both AIoT devices that support timing capabilities to use a non-first time domain resource among the X time domain resources, and AIoT devices that do not support timing capabilities to preferentially use the first time domain resource among the X time domain resources. The situation shown in A3 applies when the AIoT devices required for this AIoT service include both AIoT devices that support timing capabilities and AIoT devices that do not support timing capabilities.

[0354] AIoT devices that do not support timing capabilities will prioritize using the first time domain resource among X time domain resources. This can be understood as AIoT devices that do not support timing capabilities having a higher priority in using the first time domain resource than AIoT devices that do support timing capabilities.

[0355] The lack of timing capability can be described or replaced by one of the following: lacking or being unable to possess timing capability; lacking (or possessing) the ability to measure or calculate time; being unable to perceive time; being unable to send the sixteenth message on any of the X time-domain resources; being unable to respond to messages carrying (or indicating) multiple time-domain resources (such as paging messages); being able to send the sixteenth message on the first of the X time-domain resources; or being able to respond to messages carrying (or indicating) one time-domain resource (such as paging messages). The meaning of the first time-domain resource can be referred to the previous discussion and will not be listed here.

[0356] In another possible implementation, the reader also sends a second message instructing AIoT devices that do not support timing capabilities to prioritize the first of X time-domain resources. In this case, it is unnecessary for the first message to instruct AIoT devices that do not support timing capabilities to prioritize the first of X time-domain resources. The implementation of the second message can refer to the content of the fifteenth message discussed above, and will not be listed here. The second message and the fifteenth message can be the same message or different messages, which is not limited thereto. Alternatively, both the first message and the second message can instruct AIoT devices that do not support timing capabilities to prioritize the first of X time-domain resources.

[0357] In one possible design, the reader also sends an eleventh message, which can be sent via multicast, broadcast, or unicast. This eleventh message instructs the inventory to report without carrying the PLMN ID and / or NID of the AIoT device. Optionally, the reader may send the eleventh message after receiving the tenth message from the access network device or core network device. Optionally, the eleventh message includes second information indicating that the inventory should report without carrying the PLMN ID and / or NID of the AIoT device.

[0358] For example, if the AIoT device performing this AIoT service includes a first AIoT device, the first AIoT device receives the eleventh message, which is equivalent to instructing the storage and non-reporting of the first AIoT device's PLMN ID and / or NID. Similarly, if the AIoT device performing this AIoT service also includes a second AIoT device, the second AIoT device also receives the eleventh message. The eleventh message is equivalent to also instructing the storage and non-reporting of the second AIoT device's PLMN ID and / or NID.

[0359] S1902, the first AIoT device sends the sixteenth message to the reader on the first time domain resource. Correspondingly, the reader receives the sixteenth message from the first AIoT device on the first time domain resource.

[0360] Since the first information indicates that the AIoT device supporting timing capabilities uses a non-first time domain resource among X time domain resources, the first AIoT device can determine the time domain resource or time-frequency resource used to send the sixteenth message based on the first information. Optionally, the first AIoT device can select one time domain resource other than the first time domain resource from the X time domain resources to send the sixteenth message; the selected time domain resource is the first time domain resource. That is, the first time domain resource is one of the X time domain resources other than the non-first time domain resource. Here, we take the first time domain resource as an example; in reality, the first AIoT device can send one or more time domain resources for the sixteenth message, and this is not limited.

[0361] The sixteenth message sent by the first AIoT device (which can be referred to as the sixteenth message of the first AIoT device) may carry a random identifier. The random identifier may be randomly generated by the first AIoT device, such as a 16-bit random number, or it may be generated based on the identifier of the first AIoT device. Optionally, the sixteenth message may also carry data, such as first data. Alternatively, the first data may be sent after the first AIoT device sends the sixteenth message. For example, the first data may be carried in Msg3, where Msg3 is the third message in the access process, specifically the third message in the random access process.

[0362] Optionally, if the first AIoT device receives the eleventh message, then when the first AIoT device reports the first data, it does not need to carry the PLMN ID or NID of the first AIoT device. For example, if the identifier of the first AIoT device includes the device type ID, the network identifier, the third-party organization ID, and the EPC, then the first data can carry the first AIoT device's type ID, third-party organization ID, and EPC content except for the mask; that is, the first data does not carry the PLMN and NID. This reduces the transmission overhead of the first data.

[0363] In one possible implementation, if the AIoT device performing this service also includes a second AIoT device, after the second AIoT device receives the second message or the first message indicating the content shown in A3 above, the second AIoT device can select a second time-domain resource for transmitting the sixteenth message based on the first or second message. For example, the second AIoT device can determine the first time-domain resource among X time-domain resources as the second time-domain resource. Accordingly, the reader receives the sixteenth message from the second AIoT device on the second time-domain resource. The content of the sixteenth message of the second AIoT device can refer to the content of the sixteenth message of the first AIoT device, which will not be listed here. Optionally, the sixteenth message of the second AIoT device can carry data, such as second data. Alternatively, the second data can also be sent by the second AIoT device after sending the sixteenth message. For example, the second data is carried in Msg3.

[0364] Because the second time-domain resource is close to the time of receiving or sending the second or first message used to indicate X time-domain resources, even if the second AIoT device cannot send the sixteenth message in time, it can still send the sixteenth message after receiving the second or first message. The time of sending the sixteenth message may be the same as or close to the time of the second time-domain resource, thus greatly increasing the likelihood of the reader receiving the sixteenth message. This improves the success rate of AIoT devices that do not support timing capabilities connecting to the network. Furthermore, indicating different time-domain resources to AIoT devices that do not support timing and those that do can reduce resource conflicts among these AIoT devices, further increasing the probability of successful AIoT device connection.

[0365] Optionally, when the second AIoT device receives the eleventh message, it is not necessary to carry the PLMN ID and / or NID of the second AIoT device when reporting the second data. Since the AIoT device does not need to carry the PLMN ID and / or NID, the overhead of the data reported by the AIoT device is reduced. For example, if the identifier of the second AIoT device includes the device type ID, PLMN ID, third-party organization ID, and EPC, then the second data can carry the second AIoT device's type ID, third-party organization ID, and EPC information, excluding the mask. That is, the second data does not carry the PLMN and NID, thus reducing the transmission overhead of the second data.

[0366] The method embodiment shown in Figure 19 is applicable to scenarios where the AIoT devices performing this AIoT service include AIoT devices that support timing capabilities. The method embodiment shown in Figure 19 can also be applied to AIoT devices performing this AIoT service that include both AIoT devices that support timing capabilities and AIoT devices that do not support timing capabilities.

[0367] In this embodiment, an AIoT device supporting timing capabilities selects a non-first time-domain resource from X time-domain resources, providing a resource allocation mechanism. Furthermore, it limits the range of time-domain resources used by AIoT devices supporting timing capabilities, which helps reduce the probability of resource conflicts between these devices and other AIoT devices, thus improving the success rate of AIoT device access. Moreover, an AIoT device not supporting timing capabilities selects the first time-domain resource from the X resources, ensuring that even such devices can send the sixteenth message normally, improving the rationality of resource allocation.

[0368] The following example uses an AIoT device including a first AIoT device and a second AIoT device, a reader / writer as an access network device, and the sixteenth message as Msg1, to illustrate the communication method shown in Figure 19. Figure 22 uses the first message indicating the content shown in A1 to A3 as an example. Furthermore, Msg1 in Figure 22 can be replaced with the sixteenth message. Of course, the sixteenth message may be other messages, and this is not limited to these.

[0369] S2201. The core network device can send an inventory request to the access network device. Correspondingly, the access network device can receive an inventory request from the core network device. This inventory request can be used as an example of a service request in the method embodiment shown in Figure 19. The content of the service request can refer to the content of the service request in the method embodiment shown in Figure 19 above, and will not be listed here.

[0370] S2202, The access network device sends a first message. In this embodiment, it is assumed that both the first AIoT device and the second AIoT device receive the first message from the access network device.

[0371] The first message in this embodiment indicates the content shown in A1 to A3 above, that is, the first message indicates that an AIoT device supporting timing capabilities uses a non-first time domain resource among X time domain resources, indicates X time domain resources, and indicates that an AIoT device not supporting timing capabilities uses the first time domain resource among X time domain resources. The content of the first message and the content shown in A1 to A3 can be referred to respectively in the method embodiment shown in Figure 19 above, and will not be listed here again.

[0372] S2203, the second AIoT device sends Msg1 to the access network device in the second time domain resources. Correspondingly, the access network device receives Msg1 from the second AIoT device in the second time domain resources.

[0373] The content of the second time-domain resource and the content of Msg1 of the second AIoT device can be referred to the content of the second time-domain resource and the content of Msg1 of the second AIoT device in the method embodiment shown in Figure 19 above, respectively, and will not be listed here.

[0374] If the second AIoT device does not receive the first message, there is no need to execute step S2203, that is, S2203 is an optional step, which is shown as a dashed line in Figure 22.

[0375] S2204. The first AIoT device sends Msg1 to the access network device in the first time domain resource. Correspondingly, the access network device receives Msg1 from the first AIoT device in the first time domain resource.

[0376] The content of the first time-domain resource and the content of Msg1 of the first AIoT device can be referred to the content of the first time-domain resource and the content of Msg1 of the first AIoT device in the method embodiment shown in Figure 19 above, respectively, and will not be listed here.

[0377] S2205, The access network device sends Msg2 to the second AIoT device. Correspondingly, the second AIoT device receives Msg2 from the access network device.

[0378] Msg2 can carry a random identifier from Msg1 of the second AIoT device, or a portion of that random identifier. If the random identifier or a portion of the random identifier in Msg2 matches the random ID in Msg1, then the contention resolution is considered successful. Msg2 can also be interpreted as indicating successful contention resolution. Msg2 can be called an access response. Msg2 can also carry a device contention resolution identity.

[0379] The execution order of S2205 and S2204 can be arbitrary and is not limited thereto.

[0380] S2206, The access network device sends Msg2 to the first AIoT device. Correspondingly, the first AIoT device receives Msg2 from the access network device. Msg2 may carry the random ID from Msg1 of the first AIoT device. If the random ID in Msg2 is the same as the random ID in Msg1, then the contention for randomization is considered successfully resolved. Msg2 can also be interpreted as indicating successful contention resolution.

[0381] The execution order of S2206 and S2205 can be arbitrary and is not limited thereto.

[0382] S2207. The second AIoT device can send Msg3 to the access network device. Correspondingly, the access network device receives Msg3 from the second AIoT device. In this embodiment, Msg3 includes second data as an example. The content of Msg3 and the content of the second data can be referred to the content of Msg3 and the content of the second data in the method embodiment shown in Figure 19 above, respectively, and will not be listed here.

[0383] S2208, the first AIoT device can send Msg3 to the access network device. Correspondingly, the access network device receives Msg3 from the first AIoT device. In this embodiment, Msg3 includes first data as an example. The content of Msg3 and the content of the first data can be referred to respectively in the method embodiment shown in Figure 19 above, and will not be listed here again.

[0384] S2209. The access network device sends an inventory report to the core network device or other access network devices. The inventory report can also be replaced by a service response or service report. The inventory request can carry a data set. The data set may include, for example, first data and second data. Optionally, the data set is carried in the inventory report.

[0385] The steps S2201, S2203, S2205 to S2209 mentioned above are all optional and are shown as dashed lines in Figure 22.

[0386] Figure 22 uses a reader / writer as an example of an access network device, but the implementation of the reader / writer is not actually limited. For example, the reader / writer can also be an AIoT-enabled UE, such as the AIoT-enabled UE or UE reader in the three solutions involved in Topology 2 above. Optionally, when the reader / writer is an AIoT-enabled UE, the AIoT-enabled UE can interact with the core network device through the access network device.

[0387] In this embodiment, the first message instructs AIoT devices supporting timing capabilities to select a non-first time domain resource from X time domain resources, and instructs AIoT devices not supporting timing to select the first time domain resource from X time domain resources, providing a resource allocation mechanism. Furthermore, by defining the time domain resources used by AIoT devices supporting and not supporting timing, conflicts in the time domain resources used by different AIoT devices transmitting Msg1 are reduced, lowering the probability of collisions between different AIoT devices and thus improving the success rate of AIoT device access. Additionally, by instructing the contents of A1 to A3 in the first message, the number of signaling interactions in the system is reduced.

[0388] To provide a resource allocation mechanism, this application also provides a communication method. In this method, AIoT devices that do not support timing capabilities can be instructed to preferentially use the first time-domain resource among X time-domain resources. This allows AIoT devices that do not support timing capabilities to select the first time-domain resource among the X time-domain resources to transmit messages during the access process. This avoids situations where AIoT devices that do not support timing capabilities cannot access the network using non-first time-domain resources, improving the rationality of resource allocation and increasing the probability of successful access for AIoT devices that do not support timing capabilities.

[0389] The communication method will now be described with reference to the method shown in Figure 23. Figure 23 uses the reader / writer as an access network device as an example, but the actual implementation of the access network device is not limited. Furthermore, Figure 23 uses Msg1 as the nineteenth message as an example, but the content of the nineteenth message is not limited. That is to say, Msg1 in Figure 23 can be replaced with the nineteenth message. Of course, the nineteenth message may also be other messages, which are not limited here.

[0390] S2301. The core network device can send an inventory request to the access network device. Correspondingly, the access network device can receive an inventory request from the core network device. An inventory request can be, for example, a service request. The content of the service request can be referred to the content of the inventory request in the method embodiment shown in Figure 19 above, and will not be listed here.

[0391] Optionally, the core network device can also send a fourteenth message to the access network device, indicating that the second AIoT device does not support timing capabilities. This fourteenth message can be included in the inventory request; there is no limitation on this.

[0392] Optionally, the core network device or access network device may also send a twelfth message to the access network device. This twelfth message instructs the inventory report to not carry the PLMN ID and / or NID of the AIoT device, for example, instructing the inventory report to not carry the PLMN ID and / or NID of the first AIoT device. For instance, the twelfth message may include third information instructing the inventory report to not carry the PLMN ID and / or NID of the AIoT device. Optionally, the twelfth message may be a paging message. Optionally, the twelfth message may be carried in the inventory request, or the twelfth message may be different from the inventory request. Optionally, the twelfth message and the fourteenth message may be the same message or different messages; this is not limited.

[0393] S2302, The access network device sends a second message. In this embodiment, the second AIoT device receiving a second message from the access network device is taken as an example. The second message indicates that the AIoT device, which does not support timing capabilities, preferably uses the first time domain resource among X time domain resources. Optionally, the first message and the second message can be the same message or different messages; this is not limited. The implementation of the second message can refer to the content of the second message in the method embodiment shown in Figure 19 above, and will not be listed here again.

[0394] In this embodiment of the application, the second message indicates that the AIoT device that does not support timing capabilities preferably uses the first time domain resource among the X time domain resources. Alternatively, it can be described that the second message indicates that the AIoT device that supports timing capabilities does not preferably use the first time domain resource among the X time domain resources, or that the priority of the AIoT device that does not support timing capabilities using the first time domain resource is higher than the priority of the AIoT device that supports timing capabilities using the first time domain resource.

[0395] Optionally, the first AIoT device can also receive the second message, in which case the second AIoT device can preferentially select a non-first time domain resource from the X time domain resources. Alternatively, the second message may also instruct AIoT devices with timing capabilities to preferentially select a non-first time domain resource from the X time domain resources.

[0396] Optionally, the access network device may also send a thirteenth message, which instructs the inventory to report a message that does not carry the PLMN ID and / or NID of the AIoT device, for example, instructing the inventory to report a message that does not carry the PLMN ID and / or NID of the first AIoT device. For example, the thirteenth message may include fourth information, which instructs the inventory to report a message that does not carry the PLMN ID and / or NID of the AIoT device. Optionally, the thirteenth message may be a paging message. Optionally, the thirteenth message and the second message may be the same message or different messages; this is not limited. Optionally, the third and fourth messages may also be the same message or different messages; this is not limited.

[0397] S2303, the second AIoT device sends Msg1 to the access network device in the second time domain resources. Correspondingly, the access network device receives Msg1 from the second AIoT device in the second time domain resources.

[0398] The content of the second time-domain resource and the content of Msg1 of the second AIoT device can be referred to the content of the second time-domain resource and the content of Msg1 of the second AIoT device in the method embodiment shown in Figure 19 above, respectively, and will not be listed here.

[0399] S2304. The first AIoT device sends Msg1 to the access network device in the fifth time domain resource. Correspondingly, the access network device receives Msg1 from the first AIoT device in the fifth time domain resource.

[0400] The fifth time-domain resource can be the first time-domain resource among X time-domain resources, or it may be a non-first time-domain resource among X time-domain resources; there is no limitation on this, meaning the fifth time-domain resource can be any of the X time-domain resources. For example, the second AIoT device may preferentially select the time-domain resource corresponding to the first time-domain resource, but if there is still a time-frequency resource corresponding to the first time-domain resource among the X time-domain resources, then the first AIoT device can still select the time-frequency resource corresponding to the first time-domain resource to send Msg1. The content of Msg1 of the first AIoT device can be referred to the content of Msg1 of the first AIoT device discussed in the method embodiment shown in Figure 19 above, and will not be listed here.

[0401] The first AIoT device may not receive the first message. In this case, there is no need to execute step S2304. That is, S2304 is an optional step, which is shown as a dashed line in Figure 23.

[0402] S2305, the access network device sends Msg2 to the second AIoT device. Correspondingly, the second AIoT device receives Msg2 from the access network device. Msg2 may carry the random ID from Msg1 of the second AIoT device. If the random ID in Msg2 is the same as the random ID in Msg1, then the contention for random IDs is considered successfully resolved. Msg2 can also be interpreted as an indication that the contention has been successfully resolved.

[0403] The execution order of S2305 and S2304 can be arbitrary and is not limited thereto.

[0404] S2306. The access network device sends Msg2 to the first AIoT device. Correspondingly, the first AIoT device receives Msg2 from the access network device. Msg2 may carry the random ID from Msg1 of the first AIoT device. If the random ID in Msg2 is the same as the random ID in Msg1, then the contention for randomization is considered successfully resolved. Msg2 can also be understood as an indication that the contention has been successfully resolved.

[0405] The execution order of S2306 and S2305 can be arbitrary and is not limited thereto.

[0406] S2307. The second AIoT device can send Msg3 to the access network device. Correspondingly, the access network device receives Msg3 from the second AIoT device. In this embodiment, Msg3 includes second data as an example. Optionally, the second data may not carry the PLMN ID or NID of the second AIoT device. The content of the second data can refer to the content of the second data in the method embodiment shown in Figure 19 above, and will not be listed here.

[0407] S2308, the first AIoT device can send Msg3 to the access network device. Correspondingly, the access network device receives Msg3 from the first AIoT device. In this embodiment, Msg3 includes first data as an example. Optionally, the first data may not carry the PLMN ID and / or NID of the first AIoT device. The content of the first data can refer to the content of the first data in the method embodiment shown in Figure 19 above, and will not be listed here.

[0408] S2309. The access network device sends an inventory report to the core network device or other access network devices. This inventory report may include a data set. The data set may include, for example, first data and second data. Optionally, the data set is carried in the inventory report.

[0409] The steps S2301, S2304 to S2309 mentioned above are all optional and are shown as dashed lines in Figure 23.

[0410] Figure 23 uses a reader / writer as an example of an access network device, but the implementation of the reader / writer is not actually limited. For example, the reader / writer can also be an AIoT-enabled UE, such as the AIoT-enabled UE or UE reader in the three solutions involved in Topology 2 above. Optionally, when the reader / writer is an AIoT-enabled UE, the AIoT-enabled UE can interact with the core network device through the access network device.

[0411] In this embodiment, an AIoT device that does not support timing capabilities selects the first time-domain resource from X time-domain resources, providing a resource allocation mechanism. Furthermore, it limits the range of time-domain resources used by AIoT devices that do not support timing capabilities, which helps reduce the probability of resource conflicts between AIoT devices that do not support timing capabilities and other AIoT devices, and improves the success rate of AIoT device access.

[0412] As can be seen from the access process described in Figure 3 above, readers currently typically select the corresponding device or device group for paging based on a mask, and the mechanism for selecting the AIoT device to access is relatively simple.

[0413] In view of this, embodiments of this application provide a communication method that can instruct an AIoT device with timing capabilities to access the network. This provides another mechanism for selecting AIoT devices to access the network, as well as paging AIoT devices with timing capabilities to access the network. This facilitates the reader / writer to determine time-domain resources for the paging AIoT device based on the feature of supporting timing capabilities.

[0414] The following section describes the communication method using the method shown in Figure 24. Figure 24 uses a reader / writer as an example of an access network device, but the actual implementation of the access network device is not limited. Furthermore, Figure 24 uses the seventeenth message, Msg1, as an example, but the content of the seventeenth message is not limited. That is, Msg1 in Figure 24 can be replaced with the seventeenth message. Of course, the seventeenth message could be other messages, which are not restricted.

[0415] S2401, The core network device sends a sixth message to the access network device. Correspondingly, the access network device receives the sixth message from the core network device.

[0416] The sixth message indicates that one or more AIoT devices support timing capabilities, or in other words, that the AIoT device executing this AIoT service supports timing capabilities. The number of AIoT devices can be one, two, or three, etc., and is not limited thereto. These one or more AIoT devices are the devices executing the AIoT service. The meaning of supporting timing capabilities can be referred to the discussion of supporting timing capabilities in the method embodiment shown in Figure 19 above, and will not be repeated here. Optionally, the sixth message can be carried in the service request, which is used to request the execution of the AIoT service.

[0417] In one possible implementation, the sixth message further instructs that the PLMN ID and / or NID of one or more AIoT devices not be reported. Alternatively, the instruction to not report the PLMN ID and / or NID of one or more AIoT devices may be indicated by message #3 (such as the tenth message), which is different from the sixth message. The contents of the PLMN ID and NID can be referred to the contents of the PLMN ID and NID discussed in the method embodiment shown in FIG19, and will not be listed here. The contents of the tenth message can be referred to the contents of the tenth message discussed in the method embodiment shown in FIG19, and will not be listed one by one here.

[0418] S2402, The access network device sends a fourth message to one or more AIoT devices. Correspondingly, one or more AIoT devices receive the fourth message from the access network device.

[0419] The fourth message can be a paging message, an R2D trigger message, or a proprietary message, etc., and is not limited thereto. For example, the fourth message indicates that an AIoT device supporting timing capabilities has been connected.

[0420] Optionally, the fourth message may also indicate X time-domain resources, where X is an integer greater than 1. The contents of the X time-domain resources can be referred to the X time-domain resources discussed in the method embodiment shown in Figure 19 above, and will not be listed here again.

[0421] Optionally, if an AIoT device does not support timing capabilities, it may choose not to respond to the fourth message after receiving it.

[0422] Optionally, the access network device may also send an eleventh message. The content of the eleventh message can refer to the content of the eleventh message discussed in the method embodiment shown in Figure 19 above, and will not be listed here.

[0423] S2403, The access network device sends a fifth message to one or more AIoT devices. Correspondingly, the fifth message receives fifth messages from one or more AIoT devices.

[0424] For example, the fifth message may indicate X time-domain resources. The fifth message differs from the fourth message; it may be a paging message, an R2D trigger message, or a proprietary message, and this is not limited. The access network device may send the fourth message after sending the fifth message, or vice versa.

[0425] If the fourth message indicates X time-domain resources, then step S2403 need not be performed; that is, step S2403 is an optional step.

[0426] S2404, One or more AIoT devices send Msg1 to the access network device.

[0427] Taking one or more AIoT devices, including a first AIoT device, as an example, the first AIoT device can send Msg1 to the access network device on a third time domain resource. The third time domain resource can be, for example, one of X time domain resources other than the first time domain resource.

[0428] The contents of the X time-domain resources, the contents of the first time-domain resource, and the contents of Msg1 can be referred to the contents of the X time-domain resources, the contents of the first time-domain resource, and the contents of Msg1 discussed in the method embodiment shown in Figure 19 above, and will not be listed here again.

[0429] S2405, the access network device sends Msg2 to one or more AIoT devices. Correspondingly, one or more AIoT devices receive Msg2 from the access network device. The content of Msg2 can be referred to the Msg2 content discussed in the method embodiment shown in Figure 19 above, and will not be listed here again.

[0430] S2406. One or more AIoT devices send Msg3 to the access network device. Correspondingly, the access network device receives Msg3 from one or more AIoT devices.

[0431] Taking one or more AIoT devices, including a first AIoT device, as an example, the first AIoT device may carry first data in Msg3 and send Msg3 to the access network device. Optionally, the first data may not carry the PLMN ID and / or NID of the first AIoT device.

[0432] S2407. The access network device sends first data to the core network device or the access network device. Correspondingly, the core network device or the access network device receives the first data from the access network device.

[0433] The steps S2401, S2403, S2405 to S2407 mentioned above are all optional steps, and are shown as dashed lines in Figure 24.

[0434] Figure 24 uses a reader / writer as an example of an access network device, but the implementation of the reader / writer is not actually limited. For example, the reader / writer can also be an AIoT-enabled UE, such as the AIoT-enabled UE or UE reader in the three solutions involved in Topology 2 above. Optionally, when the reader / writer is an AIoT-enabled UE, the AIoT-enabled UE can interact with the core network device through the access network device.

[0435] In this embodiment, the reader instructs AIoT devices supporting timing capabilities to connect, providing a mechanism for selecting AIoT devices to connect. Furthermore, the reader allocates resources to connected AIoT devices that support timing capabilities based on their timing capabilities, which helps improve the rationality of resource allocation.

[0436] To provide an alternative mechanism for selecting AIoT devices for access, embodiments of this application also provide a communication method that can instruct AIoT devices that do not support timing capabilities to access the device. This provides another mechanism for selecting AIoT devices for access, as well as paging AIoT devices that do not support timing capabilities, so that the reader can determine time-domain resources for the paging AIoT device based on the feature that it does not support timing capabilities.

[0437] The following section describes the communication method using Figure 25 as an example. Figure 25 uses a reader / writer as an access network device, but the actual implementation of the access network device is not limited. Furthermore, Figure 25 uses Msg1 as the eighteenth message, but the content of the eighteenth message is not limited; that is, Msg1 in Figure 25 can be replaced with the eighteenth message. Of course, the eighteenth message could be other messages, which are not restricted.

[0438] S2501. The core network device sends the ninth message to the access network device. Correspondingly, the access network device receives the ninth message from the core network device.

[0439] The ninth message indicates that one or more AIoT devices do not support timing capabilities, or in other words, that the AIoT device executing this AIoT service does not support timing capabilities. The number of the one or more AIoT devices can be one, two, or three, etc., and is not limited thereto. These one or more AIoT devices are the devices executing the AIoT service. The meaning of "not supporting timing capabilities" can be referred to the discussion of not supporting timing capabilities in the method embodiment shown in Figure 19 above, and will not be repeated here. Optionally, the ninth message can be carried in the service request, which is used to request the execution of the AIoT service.

[0440] In one possible implementation, the ninth message further instructs that the PLMN ID and / or NID of one or more AIoT devices not be reported. Alternatively, the instruction to not report the PLMN ID and / or NID of one or more AIoT devices may be indicated by a twelfth message, which is different from the ninth message. The contents of the PLMN ID and NID can be referred to the contents of the PLMN ID and NID discussed in the method embodiment shown in FIG19, and will not be listed here.

[0441] S2502, The access network device sends a seventh message to one or more AIoT devices. Correspondingly, one or more AIoT devices receive the seventh message from the access network device.

[0442] The seventh message can be a paging message, an R2D trigger message, or a proprietary message, etc., and is not limited thereto. For example, the seventh message indicates that an AIoT device that does not support timing capabilities is connected.

[0443] Optionally, the seventh message may also indicate X time-domain resources, where X is an integer greater than 1. The contents of the X time-domain resources can be referred to the X time-domain resources discussed in the method embodiment shown in Figure 19 above, and will not be listed here again.

[0444] Optionally, if an AIoT device supports timing capabilities, it may choose not to respond to the seventh message after receiving it.

[0445] S2503, The access network device sends an eighth message to one or more AIoT devices. Correspondingly, the eighth message receives an eighth message from one or more AIoT devices.

[0446] For example, the eighth message can indicate X time-domain resources. The eighth message differs from the seventh message; it can be, for example, a paging message, an R2D trigger message, or a proprietary message, and is not limited thereto. The access network device can send the seventh message after sending the eighth message, or vice versa.

[0447] If the seventh message indicates X time-domain resources, then step S2503 need not be performed; that is, step S2503 is an optional step.

[0448] In one possible design, the access network device may also send a thirteenth message to one or more AIoT devices. This thirteenth message instructs the inventory to report messages that do not carry the PLMN ID and / or NID of the first AIoT device. The thirteenth message may be the same as or different from the seventh message. It may also be the same as or different from the eighth message; there is no limitation on this.

[0449] S2504, One or more AIoT devices send Msg1 to the access network device.

[0450] Taking one or more AIoT devices, including a second AIoT device, as an example, the second AIoT device can send Msg1 to the access network device on a third time domain resource. The third time domain resource can be, for example, one of X time domain resources other than the first time domain resource.

[0451] The contents of the X time-domain resources, the contents of the first time-domain resource, and the contents of Msg1 can be referred to the contents of the X time-domain resources, the contents of the first time-domain resource, and the contents of Msg1 discussed in the method embodiment shown in Figure 19 above, and will not be listed here again.

[0452] S2505, the access network device sends Msg2 to one or more AIoT devices. Correspondingly, one or more AIoT devices receive Msg2 from the access network device. The content of Msg2 can be referred to the Msg2 content discussed in the method embodiment shown in Figure 19 above, and will not be listed here again.

[0453] S2506. One or more AIoT devices send Msg3 to the access network device. Correspondingly, the access network device receives Msg3 from one or more AIoT devices.

[0454] Taking one or more AIoT devices, including a second AIoT device, as an example, the second AIoT device may carry second data in Msg3 and send Msg3 to the access network device. Optionally, the second data may not carry the PLMN ID and / or NID of the second AIoT device.

[0455] S2507. The access network device sends second data to the core network device. Correspondingly, the core network device receives the second data from the access network device.

[0456] The steps S2501, S2503, S2505 to S2507 mentioned above are all optional steps, and are shown as dashed lines in Figure 25.

[0457] Figure 25 uses a reader / writer as an example of an access network device, but the implementation of the reader / writer is not actually limited. For example, the reader / writer can also be an AIoT-enabled UE, such as the AIoT-enabled UE or UE reader in the three solutions involved in Topology 2 above. Optionally, when the reader / writer is an AIoT-enabled UE, the AIoT-enabled UE can interact with the core network device through the access network device.

[0458] In this embodiment, the reader can instruct AIoT devices that do not support timing capabilities to connect, providing a mechanism for selecting AIoT devices to connect. Furthermore, the reader can allocate resources more rationally to AIoT devices that do not support timing capabilities, thus improving the rationality of resource allocation.

[0459] To reduce transmission overhead, this application also provides a communication method, which will be described below with reference to the communication method shown in Figure 26.

[0460] Figure 26 uses a reader / writer as an example of an access network device, but the actual implementation of the access network device is not limited. Furthermore, Figure 26 uses message 18 as an example, but the content of message 18 is not limited; that is, Msg1 in Figure 26 can be replaced with message 18. Of course, message 18 could also be other messages, which are not restricted.

[0461] S2601. The core network device sends the tenth message to the access network device. Correspondingly, the access network device receives the tenth message from the core network device.

[0462] The tenth message indicates that the PLMN ID or NID of the AIoT device (such as the first AIoT device) not being reported should be stored. The content of the tenth message can be referred to the content of the tenth message discussed in the method embodiment shown in Figure 19 above, and will not be listed here again.

[0463] In one possible implementation, if the AIoT device performing the AIoT service is one or a group of AIoT devices, the tenth message may also carry the identifier of this one or group of AIoT devices. The identifier of the AIoT device can refer to the content of the AIoT device identifier discussed in Figure 19 above, and will not be listed here.

[0464] In another possible implementation, if the AIoT device performing the AIoT service is for all AIoT devices, such as those within the coverage area of ​​the access network device, then the tenth message may not need to carry the identifiers of these AIoT devices.

[0465] S2602, The access network device sends the eleventh message. In this embodiment, the example is that the first AIoT device receives the eleventh message from the access network device.

[0466] The eleventh message can be a paging message, an R2D trigger message, or a proprietary message, etc., and is not limited thereto. For example, the eleventh message indicates that the PLMN ID or NID of the first AIoT device will not be reported.

[0467] Optionally, the eleventh message may also indicate X time-domain resources, where X is an integer greater than 1. The contents of the X time-domain resources can be referred to the X time-domain resources discussed in the method embodiment shown in Figure 19 above, and will not be listed here again.

[0468] S2603, The first AIoT device and the access network device jointly execute the random access process.

[0469] The random access process can be referred to the content discussed in Figure 3 or Figure 19 above, and will not be listed one by one here.

[0470] S2604, the first AIoT device sends first data to the access network device. Correspondingly, the access network device receives the first data from the first AIoT device. This first data does not carry a PLMN ID or NID. The content of this first data can be referred to the content of the first data discussed in the method embodiment shown in Figure 19 above, and will not be listed here again.

[0471] S2605. The access network device sends first data to the core network device or the access network device. Correspondingly, the core network device or the access network device receives the first data from the access network device. This first data does not carry a PLMN ID or NID.

[0472] Optionally, without conflicting with the method embodiment shown in FIG26, the content shown in any of the method embodiments in FIG19, FIG22 to FIG24 can be used as optional steps in the method embodiment shown in FIG26, and will not be listed one by one here.

[0473] Figure 26 uses a reader / writer as an example of an access network device, but the implementation of the reader / writer is not actually limited. For example, the reader / writer can also be an AIoT-enabled UE, such as the AIoT-enabled UE or UE reader in the three solutions involved in Topology 2 above. Optionally, when the reader / writer is an AIoT-enabled UE, the AIoT-enabled UE can interact with the core network device through the access network device.

[0474] In this embodiment, when the first AIoT device reports its inventory, it does not need to carry the PLMN ID or NID, which can reduce the amount of data reported by the first AIoT device and help reduce the amount of data transmitted by the system.

[0475] This application provides a communication method in which AIoT devices can select appropriate resources for access based on their own capabilities. This improves the rationality of resource use and avoids different AIoT devices selecting the same resource, reducing the probability of AIoT device collisions. The communication method in Figure 27 will be described below. Figure 27 uses a reader / writer as an example of an access network device, but the implementation of the access network device is not limited. Furthermore, Figure 27 uses the twentieth message, Msg1, as an example, but the content of the twentieth message is not limited; that is, Msg1 in Figure 27 can be replaced with the twentieth message. Of course, the twentieth message may be other messages, which are not limited here.

[0476] S2701. The access network device or core network device sends an inventory request to the access network device. Correspondingly, the access network device receives the inventory request from the access network device or core network device. The content of the inventory request can be found in the embodiment shown in Figure 22, and will not be repeated here.

[0477] S2702, The access network device sends a paging message. This embodiment uses the example of a third AIoT device receiving a paging message from the access network device for illustration.

[0478] S2701 and S2702 are both optional steps, and are shown as dashed lines in Figure 27.

[0479] S2703. If the third AIoT device supports timing capability, then Msg1 is sent in a non-first time domain resource; or if the third AIoT device does not support timing capability, then Msg1 is sent in the first time domain resource.

[0480] Here, the first time-domain resource refers to the first time-domain resource among X time-domain resources, and the non-first time-domain resource refers to the non-first time-domain resource among X time-domain resources. The content supporting timing capabilities, content not supporting timing capabilities, the content of the first time-domain resource, the content of the non-first time-domain resource, and the content of the X time-domain resources can be referred to the methods described in Figure 12 above, which respectively discuss the content supporting timing capabilities, content not supporting timing capabilities, the content of the first time-domain resource, the content of the non-first time-domain resource, and the content of the X time-domain resources; they will not be listed individually here.

[0481] Optionally, the third AIoT device can further perform inventory reporting.

[0482] Figure 27 uses a reader / writer as an example of an access network device, but the implementation of the reader / writer is not actually limited. For example, the reader / writer can also be an AIoT-enabled UE, etc., without limitation. Optionally, when the reader / writer is an AIoT-enabled UE, the AIoT-enabled UE can interact with the core network device through the access network device.

[0483] In this embodiment, AIoT devices can independently select suitable time-domain resources based on their own capabilities, providing a mechanism for utilizing time-domain resources. Furthermore, different AIoT devices can choose time-domain resources more suited to their own capabilities. This not only improves the rationality of time-domain resource utilization but also reduces the probability of different AIoT devices selecting the same time-domain resource, thus helping to reduce collisions when AIoT devices send Msg1.

[0484] Based on the same inventive concept, this application provides a communication device. The communication device shown in FIG28 or FIG29 will be described below. This communication device may be, for example, a network device shown in any of FIG4 to FIG7, an intermediate node shown in FIG5, a UE shown in FIG8, an AIoT RAN shown in any of FIG9 to FIG12, an AIoT-enabled UE shown in any of FIG13 to FIG18, an AIoT device shown in any of FIG4 to FIG18, an AIoT CN shown in FIG9, FIG10, FIG13, FIG14, an AIoTF shown in FIG11, FIG12, FIG15, FIG16, FIG17, or FIG18, or an AMF shown in FIG12 or FIG16, etc., or may be a module in these devices (or equipment), etc., without specific limitation.

[0485] As shown in Figure 28, the communication device 2800 may include modules or units for implementing the methods described in the embodiments above. In one possible design, the communication device 2800 includes a processing unit 2810 and a communication unit 2820. The communication unit 2820 is used to perform transmit and receive operations, such as functions related to sending and receiving; the communication unit 2820 may be referred to as a transceiver unit; optionally, the communication unit 2820 includes a receiving unit and a transmitting unit. The processing unit 2810 is used to perform processing operations. Alternatively, the communication unit 2820 may be a transmitter and a receiver, or a transmitter and a receiver. Optionally, the communication device 2800 may also include a storage unit 2830. The storage unit 2830 is used to store the device's program code or data. The storage unit 2830 is an optional unit.

[0486] In a first possible implementation, the communication device 2800 may be a reader / writer as shown in the method embodiments of FIG19 or FIG22 above, a communication module in the reader / writer, or a circuit or chip in the reader / writer responsible for communication functions, etc.

[0487] In the above embodiment, the communication unit 2820 is used to send a first message and receive a sixteenth message.

[0488] The communication device 2800 can also perform other steps executed by the reader in the method implementation shown in Figure 19 or Figure 22 above, which will not be listed here one by one.

[0489] In a second possible implementation, the communication device 2800 may be the first AIoT device in the method embodiment shown in FIG19 or FIG22 above, the communication module in the first AIoT device, or the circuit or chip in the first AIoT device responsible for communication functions, etc.

[0490] In the above-described embodiment, the communication unit 2820 is used to receive the first message and send the sixteenth message.

[0491] The communication device 2800 can also perform other steps executed by the first AIoT device in the method implementation shown in Figure 19 or Figure 22 above, which will not be listed here.

[0492] In a third possible implementation, the communication device 2800 may be a core network device, a communication module in the core network device, or a circuit or chip in the core network device responsible for communication functions, as shown in the method embodiments of FIG19 or FIG22 above.

[0493] In the above-described embodiment, the communication unit 2820 is used to send a third message.

[0494] The communication device 2800 can also perform other steps executed by the core network equipment or access network equipment in the implementation of the method shown in Figure 19 or Figure 22 above, which will not be listed here one by one.

[0495] In a fourth possible implementation, the communication device 2800 may be a reader (or access network device) in the method embodiment shown in FIG23 above, a communication module in the reader, or a circuit or chip in the reader responsible for communication functions, etc.

[0496] In the above embodiment, the communication unit 2820 is used to send a second message and receive a nineteenth message.

[0497] The communication device 2800 can also perform other steps executed by the reader in the method implementation shown in Figure 23 above, which will not be listed here one by one.

[0498] In a fifth possible implementation, the communication device 2800 may be a second AIoT device in the method embodiment shown in FIG23 above, a communication module in the second AIoT device, or a circuit or chip in the second AIoT device that is responsible for communication functions.

[0499] In the above embodiment, the communication unit 2820 is used to receive the second message and send the nineteenth message.

[0500] The communication device 2800 can also perform other steps executed by the second AIoT device in the method implementation shown in Figure 23 above, which will not be listed here one by one.

[0501] In a sixth possible implementation, the communication device 2800 may be a core network device, a communication module in the core network device, or a circuit or chip in the core network device responsible for communication functions, as shown in the method embodiment of FIG23 above.

[0502] In the above implementation, the communication unit 2820 is used to send a fourteenth message to the reader / writer. The fourteenth message indicates that the second AIoT device does not support timing capability. Optionally, the fourteenth message also indicates that the first AIoT device supports timing capability.

[0503] The communication device 2800 can also perform other steps executed by the core network equipment in the method implementation shown in Figure 23 above, which will not be listed here one by one.

[0504] In a seventh possible implementation, the communication device 2800 may be a reader (or access network device) in the method embodiment shown in FIG24 above, a communication module in the reader, or a circuit or chip in the reader responsible for communication functions, etc.

[0505] In the above embodiment, the communication unit 2820 is used to send the fourth message and receive the seventeenth message.

[0506] The communication device 2800 can also perform other steps executed by the reader in the method implementation shown in Figure 24 above, which will not be listed here one by one.

[0507] In the eighth possible implementation, the communication device 2800 may be one or more AIoT devices (such as the first AIoT device) in the method embodiment shown in FIG24 above, a communication module in the first AIoT device, or a circuit or chip in the first AIoT device that is responsible for communication functions.

[0508] In the above embodiment, the communication unit 2820 is used to receive the fourth message and send the seventeenth message.

[0509] The communication device 2800 can also perform other steps executed by the first AIoT device in the method implementation shown in Figure 24 above, which will not be listed here.

[0510] In a ninth possible implementation, the communication device 2800 may be a core network device, a communication module in the core network device, or a circuit or chip in the core network device responsible for communication functions, as shown in the method embodiment of FIG24 above.

[0511] In the above embodiment, the communication unit 2820 is used to send a sixth message.

[0512] The communication device 2800 can also perform other steps executed by the core network equipment in the method implementation shown in Figure 24 above, which will not be listed here one by one.

[0513] In a tenth possible implementation, the communication device 2800 may be a reader (or access network device) in the method embodiment shown in FIG25 above, a communication module in the reader, or a circuit or chip in the reader responsible for communication functions, etc.

[0514] In the above-described embodiment, the communication unit 2820 is used to send the seventh message and receive the eighteenth message.

[0515] The communication device 2800 can also perform other steps executed by the reader in the method implementation shown in Figure 25 above, which will not be listed here one by one.

[0516] In an eleventh possible implementation, the communication device 2800 may be one or more AIoT devices (such as a second AIoT device) in the method embodiment shown in FIG25 above, a communication module in the second AIoT device, or a circuit or chip in the second AIoT device that is responsible for communication functions.

[0517] In the above implementation, the communication unit 2820 is used to receive the eighteenth message and send Msg1.

[0518] The communication device 2800 can also perform other steps executed by the second AIoT device in the method implementation shown in Figure 25 above, which will not be listed here one by one.

[0519] In a twelfth possible implementation, the communication device 2800 may be the core network device in the method embodiment shown in FIG25 above, the communication module in the core network device, or the circuit or chip in the core network device responsible for communication functions, etc.

[0520] In the above embodiment, the communication unit 2820 is used to send the ninth message.

[0521] The communication device 2800 can also perform other steps executed by the core network equipment in the method implementation shown in Figure 25 above, which will not be listed here one by one.

[0522] In the thirteenth possible implementation, the communication device 2800 can be the reader (or access network device) in the method embodiment shown in FIG26 above, the communication module in the reader, or the circuit or chip in the reader responsible for the communication function, etc.

[0523] In the above-described embodiment, the communication unit 2820 is used to send an eleventh message and receive first data.

[0524] The communication device 2800 can also perform other steps executed by the reader in the method implementation shown in Figure 26 above, which will not be listed here one by one.

[0525] In the fourteenth possible implementation, the communication device 2800 may be one or more AIoT devices (such as the first AIoT device) in the method embodiment shown in FIG26 above, a communication module in the first AIoT device, or a circuit or chip in the first AIoT device that is responsible for communication functions.

[0526] In the above-described embodiment, the communication unit 2820 is used to receive the eleventh message and send the first data.

[0527] The communication device 2800 can also perform other steps executed by the first AIoT device in the method implementation shown in Figure 26 above, which will not be listed here one by one.

[0528] The fifteenth possible implementation is that the communication device 2800 can be the core network device in the method embodiment shown in FIG26 above, the communication module in the core network device, or the circuit or chip responsible for communication function in the core network device or access network device.

[0529] In the above embodiment, the communication unit 2820 is used to send the tenth message.

[0530] The communication device 2800 can also perform other steps executed by the core network equipment in the method implementation shown in Figure 26 above, which will not be listed here one by one.

[0531] In the sixteenth possible implementation, the communication device 2800 may be the third AIoT device in the method embodiment shown in FIG27 above, the communication module in the third AIoT device, or the circuit or chip in the third AIoT device responsible for communication functions, etc.

[0532] In the above implementation, the communication unit 2820 is used to perform step S2703, that is, if timing capability is supported, Msg1 is sent in a non-first time domain resource, or if timing capability is not supported, Msg1 is sent in the first time domain resource.

[0533] The communication device 2800 can also perform other steps executed by the third AIoT device in the method implementation shown in Figure 27 above, which will not be listed here one by one.

[0534] In one possible design, when the communication device 2800 is a terminal device, a communication module within a terminal device, an access network device, or a communication module within an access network device, the function of the processing unit 2810 can be implemented by one or more processors. Specifically, the processor may include a modem chip, or a system-on-a-chip (SoC) chip or a SIP chip containing a modem core. The function of the communication unit 2820 can be implemented by transceiver circuitry.

[0535] In one possible design, when the communication device 2800 is a circuit or chip responsible for communication functions in a terminal device, or a circuit or chip responsible for communication functions in an access network device, such as a modem chip or a system-on-a-chip (SoC) chip or SIP chip containing a modem core, the function of the processing unit 2810 can be implemented by a circuit system in the aforementioned chip that includes one or more processors or processor cores. The function of the communication unit 2820 can be implemented by the interface circuit or data transceiver circuit on the aforementioned chip.

[0536] It is understood that the division of units in the above-described device is merely a logical functional division. Each function can correspond to a functional unit, or two or more functions can be integrated into one functional unit. In actual implementation, all or some units can be integrated into a single physical entity, or they can be distributed across different physical entities. Furthermore, the aforementioned functional units can be implemented in hardware, software, or a combination of both. Whether a function is executed in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0537] In one example, the functional unit in any of the above devices (such as a reader, a first AIoT device, a second AIoT device, an access network device, or a core network device) can be one or more integrated circuits configured to implement the above methods, such as: one or more application-specific integrated circuits (ASICs), or one or more central processing units (CPUs), one or more microcontroller units (MCUs), one or more DSPs, or one or more field-programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms.

[0538] In one example, storage unit 2830 may include random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory and / or registers, etc.

[0539] The communication device shown in Figure 29 will be described below. As shown in Figure 29, the communication device 2900 includes a processor 2910. Optionally, the communication device 2900 also includes an interface circuit 2920 and a memory 2930. The processor 2910 and the interface circuit 2920 are coupled to each other. It is understood that the interface circuit 2920 can be a transceiver or an input / output interface. The memory 2930 is used to store instructions executed by the processor 2910, or to store input data required by the processor 2910 to execute instructions, or to store data generated after the processor 2910 executes instructions. The interface circuit 2920 and the memory 2930 are optional modules. In addition, Figure 29 shows an example with one processor 2910 and one memory 2930, but the number of processors 2910 and memory 2930 is not actually limited.

[0540] The communication device 2900 is used to implement any of the method embodiments shown in Figures 19, 22 to 27. Optionally, the processor 2910 is used to implement the functions of the processing unit 2810, and the interface circuit 2920 is used to implement the functions of the communication unit 2820.

[0541] When the aforementioned communication device 2900 is a chip applied to a device (such as the terminal device or network device mentioned above), the device chip implements the functions of the device in the above method embodiments. The device chip receives information from other modules (such as radio frequency modules or antennas) within the device, the information being sent to the device by other devices; or, the device chip sends information to other modules (such as radio frequency modules or antennas) within the device, the information being sent to other devices by the device. Here, the communication device 2900 can be a baseband chip of a device, or a DU or other modules. The DU here can be a DU under an open radio access network (O-RAN) architecture.

[0542] The processor 2910 can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor can be a microprocessor or any conventional processor. Furthermore, the memory involved in the various embodiments of this application can include volatile memory, such as random access memory (RAM). The memory can also include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drives (HDDs), or solid-state drives (SSDs).

[0543] Based on the same inventive concept, embodiments of this application provide a communication system. The communication system includes a reader / writer and a first AIoT device. Optionally, the communication system further includes at least one of a second AIoT device and a core network device.

[0544] The reader / writer can refer to the reader / writer involved in the embodiments shown in Figures 19, 22, 23, 24, 25, or 26 above. The first AIoT device can refer to the first AIoT device involved in any of the embodiments shown in Figures 19, 22, 23, 24, 25, or 26 above. The core network device can refer to the core network device involved in the embodiments shown in Figures 19, 22, 23, 24, 25, or 26 above. The second AIoT device can refer to the second AIoT device involved in Figures 19, 22, and 23 above.

[0545] Based on the same inventive concept, embodiments of this application provide a communication system. The communication system includes a reader / writer and a second AIoT device. Optionally, the communication system may further include at least one of a first AIoT device, a core network device, or an access network device.

[0546] The reader / writer can refer to the reader / writer involved in the embodiments shown in Figure 23 or Figure 25 above. The second AIoT device can refer to the second AIoT device involved in Figure 23 or Figure 25 above. The core network device can refer to the core network device involved in the embodiments shown in Figure 23 or Figure 25 above. The first AIoT device can refer to the first AIoT device involved in the embodiments shown in Figure 23 or Figure 25 above.

[0547] Based on the same inventive concept, this application provides a chip system comprising a processor and an interface. The processor is used to call and execute instructions from the interface, and when the processor executes the instructions, it implements any of the method embodiments shown in Figures 19, 22 to 27.

[0548] Based on the same inventive concept, embodiments of this application provide a computer-readable storage medium for storing computer programs or instructions that, when run, implement any of the method embodiments shown in Figures 19, 22 to 27.

[0549] Based on the same inventive concept, embodiments of this application provide a program product that, when executed, enables a processor to implement any of the method embodiments shown in Figures 19, 22 to 27. This program product is, for example, a computer program product, specifically, a computer program and / or instructions. The processor is, for example, a processor running in a computer.

[0550] 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.

[0551] 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.

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

Claims

1. A communication method, characterized in that, The method, applied to a reader or a chip for a reader, includes: Send a first message, the first message indicating that the environmental IoT AIoT device that supports timing capabilities uses a non-first time domain resource from X time domain resources, where X is an integer greater than 1; On the first time domain resource, a sixteenth message is received from the first AIoT device, which supports timing capabilities. The first time domain resource is a non-first time domain resource among the X time domain resources, and the sixteenth message is a message during the random access process.

2. The method according to claim 1, characterized in that, The method further includes: On the second time domain resource, the sixteenth message is received from the second AIoT device, which does not support timing capabilities, and the second time domain resource is the first time domain resource among the X time domain resources.

3. The method according to claim 2, characterized in that, The method further includes: sending a second message, the second message indicating that AIoT devices that do not support timing capabilities should preferentially use the first time domain resource among the X time domain resources; or, The first message also instructs AIoT devices that do not support timing capabilities to prioritize the use of the first of the X time-domain resources.

4. The method according to any one of claims 1-3, characterized in that, The supported timing capability includes: It supports sending the sixteenth message on any of the X time-domain resources.

5. The method according to any one of claims 1-4, characterized in that, The method further includes: The first AIoT device receives a third message from a core network device or an access network device, the third message indicating that the first AIoT device supports timing capabilities.

6. A communication method, characterized in that, The method, applied to a reader or a chip in a reader, includes: Send a fourth message, which indicates that an AIoT device supporting timing capabilities is connected to the environment. Receive a seventeenth message from one or more AIoT devices that support the timing capability, the seventeenth message being a message during the random access process.

7. The method according to claim 6, characterized in that, The supported timing capability includes: Supports sending the seventeenth message on any of the X time-domain resources; Wherein, the X time-domain resources are configured by the reader / writer through the fourth message or the fifth message, the fifth message is sent before or after the fourth message, and X is an integer greater than 1.

8. The method according to claim 6 or 7, characterized in that, Before sending the fourth message, the method further includes: A sixth message is received from a core network device or an access network device, the sixth message indicating that the one or more AIoT devices support timing capabilities.

9. A communication method, characterized in that, The method, applied to a reader or a chip in a reader, includes: Send a seventh message, which indicates that an AIoT device in an environment that does not support timing capabilities is connected. Receive an eighteenth message from one or more AIoT devices that do not support timing capabilities, the eighteenth message being a message during the random access process.

10. The method according to claim 9, characterized in that, The lack of support for timing capabilities includes: Sending the eighteenth message on a non-first time domain resource among X time domain resources is not supported; Wherein, the X time-domain resources are configured by the reader / writer through the seventh message or the eighth message, the eighth message is sent before or after the seventh message, and X is an integer greater than 1.

11. The method according to claim 9 or 10, characterized in that, The method further includes: A ninth message is received from a core network device or an access network device, the ninth message indicating that the one or more AIoT devices do not support timing capabilities.

12. A communication method, characterized in that, The method, applied to a reader or a chip in a reader, includes: Receive a tenth message, the tenth message including first information, the first information indicating that the public land mobile network identifier and / or network identifier that does not carry the first environment Internet of Things (AIoT) device be stored and reported. Send an eleventh message, the eleventh message including second information, the second information indicating that the public terrestrial mobile network identifier and / or network identifier not carrying the first AIoT device should be stored and reported.

13. The method according to claim 12, characterized in that, The method further includes: Receive first data from the first AIoT device, wherein the first data does not carry the public land mobile network identifier and / or network identifier of the first AIoT device.

14. A communication method, characterized in that, The method, which applies to a first-environment Internet of Things (AIoT) device or a chip of a first AIoT device, includes: Receive a first message, the first message indicating that the AIoT device supporting timing capability uses a non-first time domain resource among X time domain resources, where X is an integer greater than 1; On the first time domain resource, the sixteenth message is sent. The first AIoT device supports timing capability. The first time domain resource is not the first time domain resource among the X time domain resources. The sixteenth message is a message in the random access process.

15. The method according to claim 14, characterized in that, The supported timing capability includes: It supports sending the sixteenth message on any of the X time-domain resources.

16. A communication method, characterized in that, The method, applied to a first-environment Internet of Things (AIoT) device or a chip of a first AIoT device, includes: Receive a fourth message, which indicates that an AIoT device supporting timing capabilities is connected to the environment; The seventeenth message is sent on the third time domain resource, which is one of X time domain resources. The first AIoT device supports timing capability. The X time domain resources are indicated by the fourth or fifth message. The fifth message is sent before or after the fourth message. The seventeenth message is a message in the random access process. X is greater than or equal to 1.

17. The method according to claim 16, characterized in that, The supported timing capability includes: It supports sending the seventeenth message on any of the X time-domain resources.

18. A communication method, characterized in that, The method, applied to a second-environment AIoT device or a chip of a second AIoT device, includes: Receive a seventh message, which indicates that an AIoT device in an environment that does not support timing capabilities is connected. The eighteenth message is sent on the fourth time domain resource, which is the first time domain resource among X time domain resources. The second AIoT device does not support timing capability. The X time domain resources are indicated by the seventh or eighth message. The eighth message is sent before or after the seventh message. The sixteenth message is a message in the random access process. X is an integer greater than 1.

19. The method according to claim 18, characterized in that, The lack of support for timing capabilities includes: Sending the sixteenth message on a time-domain resource other than the first of the X time-domain resources is not supported.

20. A communication method, characterized in that, The method includes: Receive the eleventh message, the eleventh message including second information, the second information indicating that the public land mobile network identifier and / or network identifier that does not carry the first AIoT device are stored and reported. Send first data, which does not carry the public terrestrial mobile network identifier and / or network identifier of the first AIoT device.

21. A communication device, characterized in that, The device includes one or more processors, which are configured to execute computer programs or instructions in memory such that the communication device implements the method as claimed in any one of claims 1-5, the method as claimed in any one of claims 6-8, the method as claimed in any one of claims 9-11, the method as claimed in claim 12 or 13, the method as claimed in claim 14 or 15, the method as claimed in claim 16 or 17, the method as claimed in claim 18 or 19, or the method as claimed in claim 20.

22. A computer program product, comprising a computer program or instructions, characterized in that, When the computer program or instructions are executed, the method as described in any one of claims 1-5, the method as described in any one of claims 6-8, the method as described in any one of claims 9-11, the method as described in claim 12 or 13, the method as described in claim 14 or 15, the method as described in claim 16 or 17, the method as described in claim 18 or 19, or the method as described in claim 20 is performed or implemented.

23. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions that, when executed, cause the method as described in any one of claims 1-5, the method as described in any one of claims 6-8, the method as described in any one of claims 9-11, the method as described in claim 12 or 13, the method as described in claim 14 or 15, the method as described in claim 16 or 17, the method as described in claim 18 or 19, or the method as described in claim 20 to be executed or implemented.

Images