Communication method and communication apparatus

Abstract

The present application provides a communication method and a communication apparatus. The communication method comprises: receiving a first message from a first access network device, the first message being used for requesting handover of a first terminal to a second access network device, the first message comprising first indication information, and the first indication information indicating the type of the first terminal; and sending a second message to the first access network device, the second message comprising second indication information, the second indication information indicating that the first terminal will continue to serve as a reader of a first AIoT service and / or the first terminal will continue to execute the first AIoT service, and the second indication information being determined on the basis of the type of the first terminal.

Description

A communication method and a communication device

[0001] This application claims priority to Chinese Patent Application No. 202411451213.6, filed on October 16, 2024, entitled "A Communication Method and Communication Device", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and more specifically, to a communication method and a communication device. Background Technology

[0003] With the development of communication technology, the 3rd Generation Partnership Project (3GPP) defined the Ambient Internet of Things (AIoT or A-IoT) technology. In AIoT and other related technologies, the communication system can include readers and tags. Readers can be implemented by network devices (such as base stations) or user equipment (UE), while tags can be IoT terminals, such as passive / semi-passive / active tags. AIoT technology is mainly used to achieve the following services: inventory management, positioning, sensing, or command. Typical application scenarios for AIoT technology include logistics, warehousing, industrial manufacturing, identity recognition, and environmental monitoring.

[0004] For example, when the reader / writer is implemented by the UE, the AIoT device can send AIoT data and / or signaling to the UE, and the UE can then send the received AIoT data and / or signaling to the core network element that supports or enables AIoT via the base station. However, in practice, the UE may undergo cell handover, resulting in the ineffective transmission of AIoT data and / or signaling, which may compromise the continuity of AIoT services. Summary of the Invention

[0005] This application provides a communication method and a communication device that can ensure the continuity of AIoT services and guarantee the user's service experience.

[0006] In a first aspect, a communication method is provided, which can be executed by a first access network device or a component of the first access network device (e.g., a chip, chip system, circuit, or communication module).

[0007] The method includes: sending a first message to a second access network device, the first message being used to request switching a first terminal to the second access network device, the first message including first indication information, the first indication information indicating that the first terminal can continue to act as a reader / writer for a first AIoT service, and / or, the first terminal continues to execute the first AIoT service; receiving a second message from the second access network device, the second message including a first resource allocated by the second access network device for the first terminal, the first resource being used to execute the first AIoT service.

[0008] For example, the first terminal in this application is referred to as a UE reader, an A-IoT-enable UE, an intermediate node, or an intermediate terminal. That is, the reader can be replaced with an A-IoT-enable UE, etc.

[0009] Based on the above solution, for the scenario where the first terminal switches to the second access network device, by determining whether the first terminal continues to execute the first AIoT service, the first resource allocated by the second access network device to the first terminal is obtained. That is, when the first terminal switches to the second access network device, it can continue to use the first resource to continue executing the first AIoT service, ensuring the continuity of AIoT services and protecting the user's service experience.

[0010] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: sending a third message to the first terminal, the third message instructing the first terminal to switch to the second access network device, wherein the third message includes indication information used to indicate the first resource.

[0011] In conjunction with the first aspect, in some implementations of the first aspect, before sending the first message to the second access network device, the method further includes: determining whether the first terminal continues to perform the first AIoT service, including: obtaining area information and the first terminal type, the area information indicating the area used to perform the first AIoT service; determining whether the first terminal continues to perform the first AIoT service based on the area information and the first terminal type, and / or determining whether the first terminal continues to act as a reader / writer for the first AIoT service.

[0012] In conjunction with the first aspect, in some implementations of the first aspect, before sending the first message to the second access network device, the method further includes: determining that the signal reception quality of the first terminal is less than or equal to a first threshold, which may be predefined or preconfigured.

[0013] In conjunction with the first aspect, in some implementations of the first aspect, determining whether the first terminal should continue to execute the first AIoT service includes: obtaining area information, the area information indicating the area used to execute the first AIoT service; and determining whether the first terminal should continue to execute the first AIoT service based on the area information.

[0014] For example, obtaining regional information includes receiving regional information from a core network element or a first terminal.

[0015] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: upon determining that the first terminal will no longer execute the first AIoT service, sending a fourth message to the second access network device, the fourth message being used to request switching the first terminal to the second access network device; receiving a fifth message from the second access network device, the fifth message including a fourth resource allocated by the second access network device to the first terminal, the fourth resource being used by the first terminal to execute non-AIoT services; and sending a sixth message to the first terminal, the sixth message instructing the first terminal to switch to the second access network device. The sixth message includes indication information indicating the fourth resource, the fourth resource being used by the first terminal to execute non-AIoT services.

[0016] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes: if it is determined that the first terminal will not continue to perform the first AIoT service, refusing to send a fourth message to the second access network device, the fourth message being used to request the first terminal to be switched to the second access network device, or refusing to switch the first terminal to the second access network device.

[0017] In conjunction with the first aspect, in some implementations of the first aspect, the first message includes at least one of the following: a first terminal type, a second identifier, the first terminal having an ongoing AIoT service, the first terminal continuing to execute the first AIoT service, or the first terminal reporting data and / or signaling related to the first AIoT service; wherein, the first terminal type includes the first terminal being a reader / writer, or a terminal that does not support reader / writer functionality, and the second identifier is used to identify the first AIoT service.

[0018] It should be noted that the data and / or signaling related to the first AIoT service reported by the first terminal usually refers to air interface transmission, that is, the first terminal reports the data and / or signaling related to the first AIoT service to the base station through the air interface.

[0019] Secondly, a communication method is provided, which can be executed by a second access network device or a component of the second access network device (e.g., a chip, chip system, circuit, or communication module).

[0020] The method includes: receiving a first message from a first access network device, the first message being used to request switching a first terminal to a second access network device, the first message including first indication information, the first indication information indicating that the first terminal can continue to act as a reader / writer for a first AIoT service, and / or, the first terminal continues to execute the first AIoT service; sending a second message to the first access network device, the second message including a first resource allocated by the second access network device for the first terminal, the first resource being used to execute the first AIoT service.

[0021] In conjunction with the second aspect, in some implementations of the second aspect, the first message includes at least one of the following: a first terminal type, a second identifier, the first terminal having an ongoing AIoT service, the first terminal continuing to execute the first AIoT service, or the first terminal reporting data and / or signaling related to the first AIoT service; wherein, the first terminal type includes the first terminal being a reader / writer, or a terminal that does not support reader / writer functionality, and the second identifier is used to identify the first AIoT service.

[0022] Thirdly, a communication method is provided, which can be executed by a first access network device or a component of the first access network device (e.g., a chip, chip system, circuit, or communication module).

[0023] The method includes: sending a first message to a second access network device, the first message requesting a switch of a first terminal to the second access network device, the first message including first indication information indicating the type of the first terminal; receiving a second message from the second access network device, the second message including second indication information indicating that the first terminal continues to act as a reader / writer for a first AIoT service, and / or that the first terminal continues to execute the first AIoT service; wherein the second indication information is determined based on the type of the first terminal.

[0024] In conjunction with the third aspect, in some implementations of the third aspect, the second instruction information further indicates at least one of the following: a first resource, the first terminal reporting data and / or signaling related to the first AIoT service, or indicating permission to continue indicating the first AIoT service; wherein the first resource is allocated to the first terminal by the second access network device, and the first resource is used to execute the first AIoT service.

[0025] In conjunction with the third aspect, in some implementations of the third aspect, the method further includes: sending a fourth message to the first terminal, the fourth message instructing the first terminal to switch to the second access network device, the fourth message including fourth indication information, the fourth indication information indicating the first resource.

[0026] In conjunction with the third aspect, in some implementations of the third aspect, the first message further includes at least one of the following: resource request information, area information, second identifier, whether to continue executing the first AIoT service, whether there is an ongoing AIoT service, whether to continue acting as a reader / writer for the first AIoT service, and whether to report data and / or signaling related to the first AIoT service; wherein, the resource request information is used to request the first resource, the first resource is used for the first terminal to continue executing the first AIoT service, the second identifier is used to identify the first AIoT service, the area information indicates the area used to execute the first AIoT service, and the area information and the first terminal type are used to determine the second indication information.

[0027] In this embodiment, the first resource used by the first terminal to continue executing the first AIoT service can be configured by either the first access network device or the second access network device, and there is no limitation on this. That is, the first access network device and the second access network device can exchange resource configuration information.

[0028] In conjunction with the third aspect, in some implementations of the third aspect, before receiving the second message from the second access network device, the method further includes: sending a fifth message to the first terminal, the fifth message including fifth indication information, the fifth indication information indicating a third resource, the third resource being used by the first terminal to execute the first AIoT service before switching to the second access network device.

[0029] Understandably, before triggering a handover, the first access network device can provide a third resource to the first terminal, allowing the first terminal to execute the first AIoT service using the third resource before switching to the second access network device. Optionally, the third resource can be either the first resource or the second resource.

[0030] For example, the fifth message is carried in a radio resource control (RRC) message. For the RRC scheme, the fifth indication information may be included in a task request message (e.g., inventoryRequest) sent by the first access network device to the first terminal, or it may be included outside of the inventoryRequest; this is not limited. It is understood that the inventoryRequest may be a single element carried in the RRC message.

[0031] Fourthly, a communication method is provided, which can be executed by a second access network device or a component of the second access network device (e.g., a chip, chip system, circuit, or communication module).

[0032] The method includes: receiving a first message from a first access network device, the first message being used to request switching a first terminal to a second access network device, the first message including first indication information indicating the type of the first terminal; sending a second message (e.g., HANDOVER REQUEST ACKNOWLEDGE) to the first access network device, the second message including second indication information indicating that the first terminal continues to act as a reader / writer for a first AIoT service, and / or that the first terminal continues to perform the first AIoT service; wherein the second indication information is determined based on the type of the first terminal.

[0033] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the second instruction information further indicates at least one of the following: a first resource, or, the first terminal reporting data and / or signaling related to the first AIoT service; wherein, the first resource is allocated to the first terminal by the second access network device, and the first resource is used to execute the first AIoT service.

[0034] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the first message further includes at least one of the following: resource request information (e.g., AIoT resource request information), area information, a second identifier, whether to continue executing the first AIoT service, whether to continue acting as a reader / writer for the first AIoT service, whether there is an ongoing AIoT service, or whether to report data and / or signaling related to the first AIoT service; wherein, the resource request information is used to request the first resource, the first resource is used for the first terminal to continue executing the first AIoT service, the second identifier is used to identify the first AIoT service, the area information indicates the area used to execute the first AIoT service, and the area information and the first terminal type are used to determine the second indication information.

[0035] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the method further includes: receiving a third message (e.g., PATH SWITCH REQUEST ACKNOWLEDGE) from a core network element, the third message including third indication information, the third indication information indicating that the first terminal is authorized as a reader / writer for the first AIoT service.

[0036] As an example, if the second access network device cannot determine whether the first terminal will continue to act as a reader / writer for the first AIoT service, and / or if the first terminal continues to execute the first AIoT service, the second access network device may first allocate resources (e.g., second resources) to the first terminal for executing the first AIoT service. The first terminal can temporarily use these AIoT resources to execute the first AIoT service. That is, when the second access network device sends a second message to the first access network device, it can carry indication information #1, which indicates the AIoT resources used by the first terminal to continue executing the first AIoT service. Then, when the first access network device sends a HandoverCommand message to the first terminal, it can carry the AIoT resources. Then, after the second access network device receives the PATH SWITCH REQUEST ACKNOWLEDGE message sent from the core network element, which carries an indication to deny authorization for the first terminal as a reader, the second access network device sends an RRC message to the first terminal. The RRC message includes indication information #2, which instructs the first terminal to stop or cease performing the first AIoT service, and / or instructs the first terminal to release the AIoT resources.

[0037] Optionally, before triggering the handover, the first access network device may allocate AIoT resource #1 (e.g., the second resource) to the first terminal via an RRC message. For example, when the first access network device sends an AIoT service request (e.g., Inventory Request / Command / Command Request, etc.) to the first terminal, it may also carry indication information. The AIoT service request information is used to request the execution of the first AIoT service, and the indication information indicates the AIoT resource #1. The AIoT resource is used by the first terminal to execute the first AIoT service. When the first terminal receives the AIoT resource #2 (e.g., the first resource) allocated by the second access network device from the handover command, it then uses the AIoT resource #2 allocated by the second access network device to perform the AIoT service.

[0038] Optionally, the method further includes: receiving a message #1 from a core network element, the message #1 including indication information #1, which indicates that authorization for the first terminal as a reader / writer for the first AIoT service is denied. At this time, the first access network device or the second access network device sends indication information #2 to the first terminal, which indicates that the first AIoT service should be stopped or discontinued, and / or indicates that the first resource should be released.

[0039] Fifthly, a communication method is provided, which can be executed by a first access network device or a component of the first access network device (e.g., a chip, chip system, circuit, or communication module).

[0040] The method includes: sending a third message to a second access network device, the third message being used to request switching the first terminal to the second access network device, the third message including second indication information, the second indication information indicating the type of the first terminal, the first terminal type including the first terminal being a reader / writer or the first terminal being a terminal that does not support reader / writer functionality; receiving a fourth message from the second access network device, the fourth message indicating permission to switch the first terminal to the second access network device, the first terminal type being used to determine whether to allow the first terminal to switch to the second access network device.

[0041] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the third message may further include at least one of the following: resource request information, area information, second identifier, whether to continue executing the first environment Internet AIoT service, whether there is an ongoing AIoT service, and whether the first terminal reports data and / or signaling related to the first AIoT service; wherein, the resource request information is used to request the first resource, the first resource is used to execute the first AIoT service, the second identifier is used to identify the first AIoT service, and the area information indicates the area used to execute the first AIoT service.

[0042] In conjunction with the fifth aspect, in some implementations of the fifth aspect, before sending the third message to the second access network device, the method further includes: receiving an eighth message, the eighth message including resource request information, the resource request information being used to request a first resource, the first resource being used to execute a first AIoT service; or, receiving a ninth message, the ninth message being used to request to perform the first AIoT service; or, the ninth message including sixth indication information, the sixth indication information indicating the first AIoT service, or that there is an ongoing AIoT service; and determining the first terminal type based on the eighth message or the ninth message.

[0043] In a sixth aspect, a communication method is provided, which can be executed by a second access network device or a component of the second access network device (e.g., a chip, chip system, circuit, or communication module).

[0044] The method includes: receiving a third message, the third message being used to request switching a first terminal to a second access network device, the third message including second indication information, the second indication information indicating the type of the first terminal, the first terminal type including the first terminal being a reader / writer or the first terminal being a terminal that does not support reader / writer functionality; sending a fourth message to the first access network device, the fourth message indicating permission to switch the first terminal to the second access network device, the first terminal type being used to determine whether to allow the first terminal to switch to the second access network device.

[0045] In conjunction with the sixth aspect, in some implementations of the sixth aspect, the third message further includes at least one of the following: resource request information, area information, second identifier, whether to continue executing the first AIoT service, whether there is an ongoing AIoT service, and whether to report data and / or signaling related to the first AIoT service; wherein, the resource request information is used to request the first resource, the first resource is used to execute the first AIoT service, the second identifier is used to identify the first AIoT service, and the area information indicates the area used to execute the first AIoT service.

[0046] In conjunction with the sixth aspect, in some implementations of the sixth aspect, the method further includes: sending a first message to a core network element, the first message including first information, the first information being used to request whether the first terminal continues to execute the first AIoT service, and / or whether the first terminal continues to act as a reader / writer for the first AIoT service; receiving a second message from the core network element, the second message including first indication information; wherein the first indication information indicates authorization for the first terminal to act as a reader / writer for the first AIoT service, and / or, the first terminal continues to execute the first AIoT service, and / or, the first terminal continues to act as a reader / writer for the first AIoT service; or, the first indication information indicates denial of authorization for the first terminal to act as a reader / writer for the first AIoT service, and / or, the first terminal does not continue to execute the first AIoT service, and / or, the first terminal does not continue to act as a reader / writer for the first AIoT service.

[0047] In conjunction with the sixth aspect, in some implementations of the sixth aspect, before receiving the second message from the core network element, the method further includes: sending a fifth message to the first terminal or the first access network device, the fifth message including third indication information, the third indication information indicating a second resource, the second resource being used by the first terminal to perform a first AIoT service.

[0048] Understandably, if the second access network device cannot determine whether the first terminal will continue to act as a reader for the first AIoT service, and / or whether the first terminal will continue to execute the first AIoT service, or before receiving the determination result, the second access network device may first allocate AIoT resource #1 (e.g., the second resource) to the first terminal for executing the first AIoT service. The first terminal can temporarily use or employ the AIoT resource #1 to execute the first AIoT service. That is, the second access network device first sends a HANDOVER REQUEST ACKNOWLEDGE message to the first access network device carrying the AIoT resource, and then the first access network device sends a HandoverCommand message to the first terminal carrying the AIoT resource #1. Afterwards, after receiving a PATH SWITCH REQUEST ACKNOWLEDGE message from the core network element carrying an indication to refuse authorization for the first terminal as a reader, the second access network device instructs the first terminal to stop or cease performing the first AIoT service via an RRC message, and / or instructs the first terminal to release the AIoT resource #1.

[0049] In the embodiments of this application, the first resource and the second resource may be the same or different, and there is no limitation on this. The only difference between the two is the timing of allocation. That is, the second resource is the resource allocated to the second access network device before it is determined whether it can continue. When the core network element subsequently instructs not to authorize and / or not to continue executing the first AIoT service, the second access network device will instruct the first terminal to stop performing the first AIoT service and / or release the second resource.

[0050] In conjunction with the sixth aspect, in some implementations of the sixth aspect, the method further includes: if the first indication information indicates that the first terminal is refused authorization as a reader / writer of the first AIoT service, and / or, the first terminal does not continue to execute the first AIoT service, and / or, the first terminal does not continue to act as a reader / writer of the first AIoT service, a sixth message is sent to the first terminal, the sixth message including the fourth indication information, the fourth indication information indicating that the first AIoT service is stopped or no longer performed, and / or, indicating that the second resource is released.

[0051] Understandably, the sixth message could be an RRC message sent from the second access network device to the first terminal after receiving the PATH SWITCH REQUEST ACKNOWLEDGE message from the core network element.

[0052] In conjunction with the sixth aspect, in some implementations of the sixth aspect, the method further includes: if the first indication information indicates that the first terminal is authorized as a reader / writer of the first AIoT service, and / or the first terminal continues to execute the first AIoT service, and / or the first terminal continues to act as a reader / writer of the first AIoT service, a seventh message is sent to the first terminal, the seventh message including the fifth indication information, the fifth indication information indicating the first resource.

[0053] Optionally, the second access network device may allocate the first resource to the first terminal after receiving the authorization instruction sent by the core network element.

[0054] The authorization instruction can be carried in the PATH SWITCH REQUEST ACKNOWLEDGE message.

[0055] Optionally, the authorization instruction can be understood as: indicating that the first terminal is allowed (allowance can be replaced by authorization) to act as a reader / writer for the AIoT service, or that the first terminal is authorized to act as an A-IoT-enable UE for the first AIoT service, or indicating that the first terminal is authorized to perform the first AIoT service, or indicating that the first terminal is authorized to act as an A-IoT-enable UE for the first AIoT service, or indicating that the first terminal is authorized to communicate with the AIoT device, or indicating that the first terminal is authorized to transmit one or more of the following messages, data, or signaling related to the first AIoT service to the AIoT device.

[0056] In a seventh aspect, a communication method is provided, which can be executed by a core network element or a component of a core network element (such as a chip, chip system, circuit, or communication module).

[0057] The method includes: receiving a first message, the first message including first information, the first information being used to request whether a first terminal should continue to perform a first AIoT service, and / or whether the first terminal should continue to act as a reader / writer for the first AIoT service; sending a second message to a second access network device, the second message including first indication information; wherein the first indication information indicates that the first terminal is authorized to act as a reader / writer for the first AIoT service, and / or that the first terminal continues to perform the first AIoT service, and / or that the first terminal continues to act as a reader / writer for the first AIoT service; or, the first indication information indicates that authorization for the first terminal to act as a reader / writer for the first AIoT service is denied, and / or that the first terminal does not continue to perform the first AIoT service, and / or that the first terminal does not continue to act as a reader / writer for the first AIoT service.

[0058] For example, the first indication information is determined based on the first terminal type.

[0059] Eighthly, a communication method is provided, which can be executed by a first access network device or a component of the first access network device (e.g., a chip, chip system, circuit, or communication module).

[0060] The method includes: receiving a first message from a first terminal, the first message including resource request information and area information, the resource request information being used by the first terminal to execute a first AIoT service, and the area information indicating the area used to execute the first AIoT service; determining, based on the area information, whether the first terminal should continue executing the first AIoT service; if it is determined that the first terminal should continue executing the first AIoT service, sending a second message to a second access network device, the second message being used to request switching the first terminal to the second access network device, the second message including the resource request information; receiving a third message from the second access network device, the third message including a first resource allocated by the second access network device to the first terminal, the first resource being used to execute the first AIoT service; and sending a fourth message to the first terminal, the fourth message instructing the first terminal to switch to the second access network device. The fourth message includes indication information indicating the first resource.

[0061] In conjunction with aspect eight, in some implementations of aspect eight, the method further includes: upon determining that the first terminal will not continue to execute the first AIoT service, sending a fifth message to the second access network device, the fifth message requesting a switch of the first terminal to the second access network device, the fifth message including a sixth message requesting a fourth resource for the first terminal to execute non-AIoT services; receiving a seventh message from the second access network device, the seventh message including the fourth resource allocated by the second access network device to the first terminal; and sending an eighth message to the first terminal, the eighth message instructing the first terminal to switch to the second access network device. The eighth message includes indication information indicating the fourth resource for the first terminal to execute non-AIoT services.

[0062] In conjunction with the eighth aspect, in some implementations of the eighth aspect, the method further includes: refusing to switch the first terminal to the second access network device if it is determined that the first terminal will not continue to perform the first AIoT service.

[0063] In conjunction with aspect eight, in some implementations of aspect eight, before receiving the first message from the first terminal, the method further includes: receiving a ninth message from a core network element, the ninth message being used to request the execution of a first AIoT service, the ninth message including a first identifier, the first identifier being used to identify an AIoT device, and the first terminal supporting communication with the AIoT device; and sending a tenth message to the first terminal, the tenth message being used to request the execution of the first AIoT service, the tenth message including the first identifier.

[0064] In the embodiments of this application, the AIoT device is related to the first AIoT service, that is, the AIoT device identified by the second identifier in the embodiments.

[0065] In conjunction with aspect eight, in some implementations of aspect eight, the first message includes a second identifier; the second message also includes at least one of the following: a first terminal type, a second identifier, the first terminal continuing to execute the first AIoT service, the first terminal having an ongoing AIoT service, and the first terminal reporting data and / or signaling related to the first AIoT service; wherein, the first terminal type includes the first terminal being a reader / writer or a terminal that does not support reader / writer functionality, and the second identifier is used to identify the first AIoT service.

[0066] In a ninth aspect, a communication method is provided, which can be executed by a second access network device or a component of the second access network device (e.g., a chip, chip system, circuit, or communication module).

[0067] The method includes: receiving a second message from a first access network device, the second message being used to request switching a first terminal to a second access network device, the second message including resource request information, the resource request information being used by the first terminal to execute a first AIoT service; and sending a third message to the first access network device, the third message including a first resource allocated by the second access network device for the first terminal, the first resource being used to execute the first AIoT service.

[0068] In conjunction with aspect nine, in some implementations of aspect nine, the second message further includes at least one of the following: a first terminal type, a second identifier, the first terminal continuing to execute the first AIoT service, the first terminal having an ongoing AIoT service, and the first terminal reporting data and / or signaling related to the first AIoT service; wherein, the first terminal type includes the first terminal being a reader / writer or a terminal that does not support reader / writer functionality, and the second identifier is used to identify the first AIoT service.

[0069] In a tenth aspect, a communication method is provided, which can be executed by a first access network device or a component of the first access network device (e.g., a chip, a chip system, a circuit, or a communication module).

[0070] The method includes: receiving a first message from a first terminal, the first message including resource request information and area information, the resource request information being used to request a first resource, the first resource being used to execute a first AIoT service, and the area information indicating the area used to execute the first AIoT service; sending a second message to a second access network device, the second message being used to request switching the first terminal to the second access network device, the second message including resource request information and area information; receiving a third message from the second access network device, the third message including the first resource allocated by the second access network device to the first terminal; and sending a fourth message to the first terminal, the fourth message instructing the first terminal to switch to the second access network device. The fourth message includes indication information indicating the first resource.

[0071] In conjunction with aspect ten, in some implementations of aspect ten, before receiving the first message from the first terminal, the method further includes: receiving a fifth message from a core network element, the fifth message being used to request the execution of a first AIoT service, the fifth message including a first identifier, the first identifier being used to identify an AIoT device, and the first terminal supporting communication with the AIoT device; and sending a sixth message to the first terminal, the sixth message being used to request the execution of the first AIoT service, the sixth message including the first identifier.

[0072] In conjunction with aspect ten, in some implementations of aspect ten, the first message includes a second identifier; the second message also includes at least one of the following: a first terminal type, a second identifier, whether to continue executing the first AIoT service, whether there is an ongoing AIoT service, and whether to report data and / or signaling related to the first AIoT service; wherein, the first terminal type includes the first terminal being a reader or a terminal that does not support reader functionality, and the second identifier is used to identify the first AIoT service.

[0073] In the eleventh aspect, a communication method is provided, which can be executed by a second access network device or a component of the second access network device (e.g., a chip, chip system, circuit, or communication module).

[0074] The method includes: receiving a second message from a first access network device, the second message being used to request switching a first terminal to a second access network device, the second message including a resource request message and area information, the resource request information being used to request a first resource, the first resource being used to execute a first AIoT service, and the area information indicating the area used to execute the first AIoT service; determining, based on the area information, that the first terminal continues to execute the first AIoT service; and sending a third message to the first access network device, the third message including the first resource allocated by the second access network device for the first terminal.

[0075] In conjunction with the eleventh aspect, in some implementations of the eleventh aspect, the second message further includes at least one of the following: a first terminal type, a second identifier, whether to continue executing the first AIoT service, whether there is an ongoing AIoT service, and whether to report data and / or signaling related to the first AIoT service; wherein, the first terminal type includes the first terminal being a reader or a terminal that does not support reader functionality, and the second identifier is used to identify the first AIoT service.

[0076] In a twelfth aspect, a communication method is provided, which can be executed by a first access network device or a component of the first access network device (e.g., a chip, a chip system, a circuit, or a communication module).

[0077] The method includes: acquiring area information, the area information indicating the area used to execute the first AIoT service; receiving a first message from a second access network device, the first message being used to request confirmation whether the first terminal should continue to execute the first AIoT service, the second access network device being a network device accessed by the first terminal after the wireless link between the first terminal and the first access network device fails; determining whether the first terminal should continue to execute the first AIoT service based on the area information; and sending a second message to the second access network device, the second message indicating whether the first terminal should continue to execute the first AIoT service.

[0078] In conjunction with aspect 12, in some implementations of aspect 12, obtaining regional information includes: receiving a third message from a core network element, the third message being used to request the execution of a first AIoT service, the third message including regional information.

[0079] Optionally, the first access network device sends a fourth message to the first terminal. The fourth message is used to request the execution of the first AIoT service and includes regional information.

[0080] In conjunction with the twelfth aspect, in certain implementations of the twelfth aspect, the first message includes at least one of the following: a second identifier, a first terminal type, whether to continue as a reader / writer, whether to continue executing the first AIoT service, or whether to report data and / or signaling related to the first AIoT service; the second message includes at least one of the following: a second identifier, a first terminal type, the first terminal continuing as a reader / writer, the first terminal continuing to execute the first AIoT service, and the first terminal reporting data and / or signaling related to the first AIoT service; wherein, the first terminal type includes the first terminal being a reader / writer, or a terminal that does not support reader / writer functionality, and the second identifier is used to identify the first AIoT service.

[0081] Alternatively, the method includes: a first access network device sending first information to a first terminal, the first information indicating a third resource, the third resource being used by the first terminal to execute a first environment Internet AIoT service when a first condition is met. The first condition includes any one of the following: the first terminal discovers / declares a radiolink failure (RLF) after accessing the first access network device, or the first terminal discovers / declares an RLF after accessing the first access network but before successfully accessing the second access network device.

[0082] In conjunction with the twelfth aspect, in some implementations of the twelfth aspect, before sending the first information to the first terminal, the method further includes: receiving a first message, the first message including resource request information, the resource request information being used to request a first resource, the first resource being used to execute the first AIoT service; or, receiving a second message, the second message including indication information, the indication information indicating the first AIoT service, or being used to request to perform the first AIoT service; and determining the first terminal type based on the first message or the second message.

[0083] In other words, the first access network device can provide a third resource to the first terminal in advance, so that the UE can use the third resource to execute the first AIoT service after discovering the RLF. This step is provided by the first access network device in advance before the UE discovers the RLF. The first access network device can send an indication information when sending an AIoT task request message (e.g., inventory request). This indication information is used to indicate the third resource. This indication information can be carried in the AIoT task request message (e.g., inventory request), or the AIoT task request message (e.g., inventory request) and the indication information can be sent independently. There is no limitation on this.

[0084] In a thirteenth aspect, a communication method is provided, which can be executed by a second access network device or a component of the second access network device (e.g., a chip, chip system, circuit, or communication module).

[0085] The method includes: sending a first message to a first access network device, the first message being used to request confirmation as to whether a first terminal continues to perform a first AIoT service; the second access network device being a network device accessed by the first terminal after the wireless link between the first terminal and the first access network device fails; receiving a second message from the first access network device, the second message indicating whether the first terminal continues to perform the first AIoT service; and sending a fifth message to the first terminal, the fifth message including at least one of the following: a second identifier, a first terminal type, whether to continue as a reader / writer, whether to continue performing the first AIoT service, and whether to report data and / or signaling related to the first AIoT service; wherein, the first terminal type includes the first terminal being a reader / writer, or a terminal that does not support reader / writer functionality, and the second identifier being used to identify the first AIoT service.

[0086] In conjunction with aspect thirteen, in certain implementations of aspect thirteen, the first message includes at least one of the following: a second identifier, a first terminal type, whether it continues to be a reader / writer, whether it continues to execute the first AIoT service, or whether the first terminal reports data and / or signaling related to the first AIoT service; the second message includes at least one of the following: a second identifier, a first terminal type, the first terminal continuing to be a reader / writer, the first terminal continuing to execute the first AIoT service, or the first terminal reporting data and / or signaling related to the first AIoT service; wherein, the first terminal type includes the first terminal being a reader / writer, or a terminal that does not support reader / writer functionality, and the second identifier is used to identify the first AIoT service.

[0087] In conjunction with aspect thirteen, in some implementations of aspect thirteen, the method further includes, before sending the fifth message to the first terminal, receiving a sixth message from a core network element, the sixth message indicating that the first terminal is authorized as a reader / writer.

[0088] In a fourteenth aspect, a communication method is provided, which can be executed by a first access network device or a component of the first access network device (e.g., a chip, chip system, circuit, or communication module).

[0089] The method includes: acquiring area information, the area information indicating the area for performing a first AIoT service; and sending a second message to a second access network device, the second message including the area information.

[0090] In conjunction with aspect fourteen, in some implementations of aspect fourteen, obtaining regional information includes: receiving regional information from core network elements or a first terminal.

[0091] In conjunction with the fourteenth aspect, in some implementations of the fourteenth aspect, before receiving the first message from the second access network device, the method further includes: receiving a third message from a core network element, the third message being used to request the execution of a first AIoT service, the third message including area information; and sending a fourth message to the first terminal, the fourth message being used to request the execution of the first AIoT service, the fourth message including area information.

[0092] In conjunction with aspect fourteen, in some implementations of aspect fourteen, the second message further includes at least one of the following: a second identifier, a first terminal type, whether it continues to be a reader / writer, whether it continues to execute the first AIoT service, whether there is an ongoing AIoT service, and whether data and / or signaling related to the first AIoT service is reported; wherein, the first terminal type includes the first terminal being a reader / writer, or a terminal that does not support reader / writer functionality, and the second identifier is used to identify the first AIoT service.

[0093] In a fifteenth aspect, a communication method is provided, which can be executed by a second access network device or a component of the second access network device (e.g., a chip, chip system, circuit, or communication module).

[0094] The method includes: receiving a re-establishment request message from a first access network device; obtaining first indication information, the first indication information indicating a first terminal type; sending a second message to the first terminal, the second message including second indication information, the second indication information indicating that the first terminal continues to act as a reader / writer for a first AIoT service, and / or, the first terminal continues to execute the first AIoT service.

[0095] In conjunction with aspect 15, in certain implementations of aspect 15, obtaining the first indication information includes: receiving a third message (from the UE sending an RRC Reestablishment Request / UE Assistance Information (UAI) / other RRC msg), the third message including the first indication information; and receiving a fourth message (from the last serving gNB sending a Retrieve UE Context Response), the third message including the first indication information.

[0096] In conjunction with aspect fifteen, in some implementations of aspect fifteen, the fourth message further includes at least one of the following: first information, area information, second identifier, whether to continue executing the first AIoT service, whether there is an ongoing AIoT service, and whether to report data and / or signaling related to the first AIoT service; wherein, the first information is used to request a first resource, the first resource is used for the first terminal to continue executing the first AIoT service; the second identifier is used to identify the first AIoT service; the area information indicates the area for executing the first AIoT service, and the area information and the first terminal type are used to determine the second indication information.

[0097] In a sixteenth aspect, a communication method is provided, which can be performed by a second access network device or a component of the second access network device (e.g., a chip, a chip system, a circuit, or a communication module).

[0098] The method includes: receiving a first message from a first terminal, the first message including resource request information, the resource request information being used by the first terminal to execute a first AIoT service, and a second access network device being a network device accessed by the first terminal after a wireless link between the first terminal and the first access network device fails; sending a second message to a core network element, the second message including at least one of the following: whether the first terminal is authorized as a reader / writer, whether it continues to be a reader / writer, or whether it continues to execute the first AIoT service; receiving a third message from a core network element, the third message including at least one of the following: the first terminal is authorized as a reader / writer, the first terminal continues to be a reader / writer, or the first terminal continues to execute the first AIoT service; and sending a fourth message to the first terminal, the fourth message including indication information, the indication information indicating a first resource, the first resource being used to execute the first AIoT service.

[0099] In a seventeenth aspect, a communication method is provided, which can be executed by a first terminal or a component of the first terminal (e.g., a chip, a chip system, a circuit, or a communication module).

[0100] The method includes: receiving a message from a first access network device or a second access network device, the message being used to instruct a first terminal to switch to the second access network device; if the message includes resource configuration information, the resource configuration information indicating a first resource, and continuing to execute the first AIoT service according to the first resource; if the message does not include resource configuration information, stopping or ceasing to execute the first AIoT service.

[0101] In this embodiment, continuing to execute the first AIoT service based on the first resource can be replaced with: continuing to execute the first AIoT service using or based on the first resource, without limitation.

[0102] In conjunction with the seventeenth aspect, in some implementations of the seventeenth aspect, before receiving a message from the first access network device or the second access network device, the method further includes: receiving indication information #1 from the second access network device, the indication information #1 indicating a third resource, the third resource being used by the first terminal to perform a first AIoT service before switching to the second access network device.

[0103] Optionally, the first terminal receives indication information #2 from the second access network device, which indicates a timer and / or an effective area. That is, the first terminal can execute or perform a first AIoT service within the time period indicated by the timer and / or within the effective area.

[0104] In an eighteenth aspect, a communication method is provided, which can be executed by a first terminal or a component of the first terminal (e.g., a chip, a chip system, a circuit, or a communication module).

[0105] The method includes: a first terminal accessing a first access network device and executing a first AIoT service; discovering an RLF between the first terminal and the first access network device, and stopping or continuing to execute the first AIoT service.

[0106] In conjunction with the eighteenth aspect, in certain implementations of the eighteenth aspect, before discovering the RLF between the first terminal and the first access network device, the method further includes: receiving first information from the first access network device, the first information indicating a third resource, the third resource being used by the first terminal to execute a first environment Internet AIoT service when a first condition is met. Wherein, the first condition includes any one of the following: the first terminal discovers a radio link failure (RLF) after accessing the first access network device, or the first terminal discovers an RLF after accessing the first access network but before successfully accessing the second access network device; continuing the first AIoT service includes: continuing the first AIoT service according to the third resource.

[0107] In a nineteenth aspect, a communication device is provided. This communication device has the functions described in the first aspect above. For example, the communication device includes modules, units, or means corresponding to the operations involved in the first aspect. These modules, units, or means can be implemented in software, hardware, or a combination of software and hardware.

[0108] In one possible design, the communication device includes: a processing module for determining whether a first terminal should continue executing a first AIoT service; if it is determined that the first terminal should continue executing the first AIoT service, the communication module is configured to send a first message to a second access network device, the first message requesting that the first terminal be switched to the second access network device; the communication module is further configured to receive a second message from the second access network device, the second message including a first resource allocated by the second access network device for the first terminal, the first resource being used to execute the first AIoT service; and the communication module is further configured to send a third message to the first terminal, the third message instructing the first terminal to switch to the second access network device. The third message includes indication information indicating the first resource.

[0109] In a twentieth aspect, a communication device is provided. This communication device has the functions described in the second aspect above. For example, the communication device includes modules, units, or means corresponding to the operations involved in the second aspect. These modules, units, or means can be implemented in software, hardware, or a combination of software and hardware.

[0110] In one possible design, the communication device includes: a communication module for receiving a first message from a first access network device, the first message being for requesting a first terminal to switch to a second access network device; the communication module is also configured to send a second message to the first access network device, the second message including a first resource allocated by the second access network device for the first terminal, the first resource being for executing a first AIoT service.

[0111] In a twenty-first aspect, a communication device is provided. This communication device has the functions described in the third aspect above. For example, the communication device includes modules, units, or means corresponding to the operations involved in the third aspect. These modules, units, or means can be implemented in software, hardware, or a combination of software and hardware.

[0112] In one possible design, the communication device includes: a communication module for sending a first message to a second access network device, the first message requesting a switch of a first terminal to the second access network device, the first message including first indication information indicating the type of the first terminal; and the communication module further for receiving a second message from the second access network device, the second message including second indication information indicating that the first terminal continues to act as a reader / writer for a first AIoT service, and / or that the first terminal continues to execute the first AIoT service. The second indication information is determined based on the type of the first terminal.

[0113] In a twenty-second aspect, a communication device is provided. This communication device has the functions described in the fourth aspect above. For example, the communication device includes modules, units, or means corresponding to the operations involved in the fourth aspect. These modules, units, or means can be implemented in software, hardware, or a combination of software and hardware.

[0114] In one possible design, the communication device includes: a communication module for receiving a first message from a first access network device, the first message requesting a switch of a first terminal to a second access network device, the first message including first indication information indicating the type of the first terminal; the communication module is further configured to send a second message to the first access network device, the second message including second indication information indicating that the first terminal continues to act as a reader / writer for a first AIoT service, and / or that the first terminal continues to perform the first AIoT service; wherein the second indication information is determined based on the type of the first terminal.

[0115] In a twenty-third aspect, a communication device is provided. This communication device has the functions described in the fifth aspect above. For example, the communication device includes modules, units, or means corresponding to the operations involved in the fifth aspect. These modules, units, or means can be implemented through software, hardware, or a combination of software and hardware.

[0116] In one possible design, the communication device includes: a communication module for sending a third message to a second access network device, the third message requesting a switch of the first terminal to the second access network device, the third message including second indication information indicating the type of the first terminal, the first terminal type including the first terminal being a reader / writer or the first terminal being a terminal that does not support reader / writer functionality; the communication module is also configured to receive a fourth message from the second access network device, the fourth message indicating permission to switch the first terminal to the second access network device, the first terminal type being used to determine whether to allow the switch of the first terminal to the second access network device.

[0117] In a twenty-fourth aspect, a communication device is provided. This communication device has the functions described in the sixth aspect above. For example, the communication device includes modules, units, or means corresponding to the operations involved in the sixth aspect. These modules, units, or means can be implemented in software, hardware, or a combination of software and hardware.

[0118] In one possible design, the communication device includes: a communication module for receiving a third message, the third message being for requesting a switch of a first terminal to a second access network device, the third message including second indication information indicating the type of the first terminal, the first terminal type including the first terminal being a reader / writer or the first terminal being a terminal that does not support reader / writer functionality; the communication module is also configured to send a fourth message to the first access network device, the fourth message indicating permission to switch the first terminal to the second access network device, the first terminal type being used to determine whether the switch of the first terminal to the second access network device is permitted.

[0119] In a twenty-fifth aspect, a communication device is provided. This communication device has the functions described in the seventh aspect above. For example, the communication device includes modules, units, or means corresponding to the operations involved in the seventh aspect. These modules, units, or means can be implemented in software, hardware, or a combination of software and hardware.

[0120] In one possible design, the communication device includes: a communication module for receiving a first message, the first message including first information, the first information being used to request whether a first terminal should continue to perform a first AIoT service, and / or whether the first terminal should continue to act as a reader / writer for the first AIoT service; the communication module is further configured to send a second message to a second access network device, the second message including first indication information; wherein the first indication information indicates authorization for the first terminal to act as a reader / writer for the first AIoT service, and / or, the first terminal to continue performing the first AIoT service, and / or, the first terminal to continue acting as a reader / writer for the first AIoT service; or, the first indication information indicates denial of authorization for the first terminal to act as a reader / writer for the first AIoT service, and / or, the first terminal not to continue performing the first AIoT service, and / or, the first terminal not to continue acting as a reader / writer for the first AIoT service.

[0121] In a twenty-sixth aspect, a communication device is provided. This communication device has the functions described in the eighth aspect above. For example, the communication device includes modules, units, or means corresponding to the operations involved in the eighth aspect. These modules, units, or means can be implemented in software, hardware, or a combination of software and hardware.

[0122] In one possible design, the communication device includes: a communication module for receiving a first message from a first terminal, the first message including resource request information and area information, the resource request information being used by the first terminal to execute a first AIoT service, and the area information indicating the area used to execute the first AIoT service; a processing module for determining, based on the area information, whether the first terminal should continue executing the first AIoT service; the communication module further for sending a second message to a second access network device if it is determined that the first terminal should continue executing the first AIoT service, the second message requesting a switch to the second access network device, the second message including resource request information; the communication module further for receiving a third message from the second access network device, the third message including a first resource allocated by the second access network device to the first terminal, the first resource being used to execute the first AIoT service; and the communication module further for sending a fourth message to the first terminal, the fourth message instructing the first terminal to switch to the second access network device. The fourth message includes indication information indicating the first resource.

[0123] In a twenty-seventh aspect, a communication device is provided. This communication device has the functions described in the ninth aspect above. For example, the communication device includes modules, units, or means corresponding to the operations involved in the ninth aspect. These modules, units, or means can be implemented in software, hardware, or a combination of software and hardware.

[0124] In one possible design, the communication device includes: a communication module for receiving a second message from a first access network device, the second message requesting a switch of a first terminal to a second access network device, the second message including resource request information for the first terminal to perform a first AIoT service; the communication module is also configured to send a third message to the first access network device, the third message including a first resource allocated by the second access network device for the first terminal, the first resource being used to perform the first AIoT service.

[0125] In a twenty-eighth aspect, a communication device is provided. This communication device has the functions described in the tenth aspect above. For example, the communication device includes modules, units, or means corresponding to the operations described in the tenth aspect. These modules, units, or means can be implemented in software, hardware, or a combination of software and hardware.

[0126] In one possible design, the communication device includes: a communication module for receiving a first message from a first terminal, the first message including resource request information and area information, the resource request information requesting a first resource, the first resource being used to execute a first AIoT service, and the area information indicating the area used to execute the first AIoT service; the communication module is further configured to send a second message to a second access network device, the second message requesting a switch of the first terminal to the second access network device, the second message including resource request information and area information; the communication module is further configured to receive a third message from the second access network device, the third message including the first resource allocated by the second access network device to the first terminal; and the communication module is further configured to send a fourth message to the first terminal, the fourth message instructing the first terminal to switch to the second access network device. The fourth message includes indication information indicating the first resource.

[0127] In a twenty-ninth aspect, a communication device is provided. This communication device has the functions described in the eleventh aspect above. For example, the communication device includes modules, units, or means corresponding to the operations involved in the eleventh aspect. These modules, units, or means can be implemented in software, hardware, or a combination of software and hardware.

[0128] In one possible design, the communication device includes: a communication module for receiving a second message from a first access network device, the second message requesting a switch of a first terminal to the second access network device, the second message including a resource request message and area information, the resource request message requesting a first resource, the first resource being used to execute a first AIoT service, and the area information indicating the area used to execute the first AIoT service; a processing module for determining, based on the area information, that the first terminal should continue to execute the first AIoT service; and the communication module further for sending a third message to the first access network device, the third message including the first resource allocated by the second access network device to the first terminal.

[0129] In a thirtieth aspect, a communication device is provided. This communication device has the functions described in the twelfth aspect above. For example, the communication device includes modules, units, or means corresponding to the operations described in the twelfth aspect above. These modules, units, or means can be implemented in software, hardware, or a combination of software and hardware.

[0130] In one possible design, the communication device includes: a processing module for acquiring area information, the area information indicating an area for executing a first AIoT service; a communication module for receiving a first message from a second access network device, the first message requesting confirmation as to whether a first terminal should continue executing the first AIoT service, the second access network device being a network device accessed by the first terminal after a wireless link between the first terminal and the first access network device fails; the processing module is further configured to determine, based on the area information, whether the first terminal should continue executing the first AIoT service; and the communication module is further configured to send a second message to the second access network device, the second message indicating whether the first terminal should continue executing the first AIoT service.

[0131] In a thirty-first aspect, a communication device is provided. This communication device has the functions described in the thirteenth aspect above. For example, the communication device includes modules, units, or means corresponding to the operations involved in the thirteenth aspect. These modules, units, or means can be implemented in software, hardware, or a combination of software and hardware.

[0132] In one possible design, the communication device includes: a communication module for sending a first message to a first access network device, the first message being used to obtain a first terminal type, and the second access network device being a network device accessed by the first terminal after the wireless link between the first terminal and the first access network device fails; the communication module is further configured to receive a second message from the first access network device, the second message including the first terminal type; and the communication module is further configured to send a fifth message to the first terminal, the fifth message including at least one of the following: a second identifier, the first terminal type, whether to continue as a reader / writer, whether to continue executing the first AIoT service, and whether the first terminal reports data and / or signaling related to the first AIoT service; wherein, the first terminal type includes the first terminal being a reader / writer, or a terminal that does not support reader / writer functionality, and the second identifier is used to identify the first AIoT service.

[0133] In a thirty-second aspect, a communication device is provided. This communication device has the functions described in the fourteenth aspect above. For example, the communication device includes modules, units, or means corresponding to the operations described in the fourteenth aspect. These modules, units, or means can be implemented in software, hardware, or a combination of software and hardware.

[0134] In one possible design, the communication device includes: a processing module for acquiring area information, the area information indicating an area for performing a first AIoT service; and a communication module for sending a second message, the second message including the area information.

[0135] In a thirty-third aspect, a communication device is provided. This communication device has the functions described in aspect fifteen above. For example, the communication device includes modules, units, or means corresponding to the operations described in aspect fifteen above. These modules, units, or means can be implemented in software, hardware, or a combination of software and hardware.

[0136] In one possible design, the communication device includes: a processing module for acquiring area information, the area information indicating the area for executing the first AIoT service, and a second access network device being a network device accessed by the first terminal after the wireless link between the first terminal and the first access network device fails; the processing module is further configured to determine, based on the area information, whether the first terminal should continue executing the first AIoT service; and a communication module for sending a fifth message to the first terminal, the fifth message including at least one of the following: a second identifier, a first terminal type, whether to continue as a reader / writer, whether to continue executing the first AIoT service, and whether to report data and / or signaling related to the first AIoT service; wherein, the first terminal type includes the first terminal being a reader / writer, or a terminal that does not support reader / writer functionality, and the second identifier is used to identify the first AIoT service.

[0137] In a thirty-fourth aspect, a communication device is provided. This communication device has the functions described in the sixteenth aspect above. For example, the communication device includes modules, units, or means corresponding to the operations described in the sixteenth aspect. These modules, units, or means can be implemented in software, hardware, or a combination of software and hardware.

[0138] In one possible design, the communication device includes: a communication module for receiving a first message from a first terminal, the first message including resource request information, the resource request information being used by the first terminal to execute a first AIoT service, and a second access network device being a network device accessed by the first terminal after the wireless link between the first terminal and the first access network device fails; the communication module is further configured to send a second message to a core network element, the second message including at least one of the following: whether the first terminal is authorized as a reader / writer, whether it continues to be a reader / writer, or whether it continues to execute the first AIoT service; the communication module is further configured to receive a third message from a core network element, the third message including at least one of the following: the first terminal is authorized as a reader / writer, the first terminal continues to be a reader / writer, or the first terminal continues to execute the first AIoT service; and to send a fourth message to the first terminal, the fourth message including indication information, the indication information indicating a first resource, the first resource being used to execute the first AIoT service.

[0139] In a thirty-fifth aspect, a communication device is provided. This communication device has the functions described in the seventeenth aspect above. For example, the communication device includes modules, units, or means corresponding to the operations described in the seventeenth aspect. These modules, units, or means can be implemented in software, hardware, or a combination of software and hardware.

[0140] In one possible design, the communication device includes: a communication module for receiving a message from a first access network device or a second access network device, the message being used to instruct a first terminal to switch to the second access network device; and a processing module for continuing to execute a first AIoT service based on the first resource if the message includes resource configuration information indicating a first resource; and stopping or ceasing to execute the first AIoT service if the message does not include resource configuration information.

[0141] In a thirty-sixth aspect, a communication device is provided. This communication device has the functions described in the eighteenth aspect above. For example, the communication device includes modules, units, or means corresponding to the operations described in the eighteenth aspect above. These modules, units, or means can be implemented in software, hardware, or a combination of software and hardware.

[0142] In one possible design, the communication device includes: a processing module for a first terminal to access a first access network device and execute a first AIoT service; the processing module is further configured to stop executing the first AIoT service in the event of a radio link failure (RLF) between the first terminal and the first access network device.

[0143] In aspects nineteen through thirty-six, the communication module can perform the receiving and transmitting processes described in aspects one through eighteen above, and the processing module can perform other processes described in aspects one through eighteen above besides receiving and transmitting.

[0144] A thirty-seventh aspect provides a communication device including an interface circuit and one or more processors. The one or more processors are coupled to a memory. The memory stores part or all of a computer program or instructions necessary for implementing the functions involved in any of the first or second aspects described above. The one or more processors are executable to carry out the computer program or instructions, which, when executed, cause the communication device to implement the methods in any possible design or implementation of the first to eighteenth aspects described above. The interface circuit is used to implement communication functions within the communication device and / or communication functions between the communication device and other devices or components.

[0145] In one possible design, the processor is used to communicate with other devices or components through the interface circuit.

[0146] In one possible design, the communication device may also include the memory.

[0147] The aforementioned communication device may be a first terminal, or a communication module in the first terminal, or a chip in the first terminal responsible for communication functions, such as a modem chip (also known as a baseband chip) or a SoC or SIP chip containing a modem module.

[0148] The aforementioned communication device may be an access network device, or a module (such as a circuit, chip, or chip system) in the access network device, or a logical node, logical module, or software that can realize all or part of the functions of the access network device.

[0149] The aforementioned communication device may be a core network element, or a module (such as a circuit, chip, or chip system) within a core network element, or a logical node, logical module, or software capable of implementing all or part of the functions of a core network element.

[0150] In the thirty-eighth aspect, a communication system is provided, which includes at least one of the communication devices of any one of the nineteenth to thirty-sixth aspects.

[0151] In a thirty-ninth aspect, a computer-readable storage medium is provided. This computer-readable storage medium stores computer program code or instructions, which, when read and executed by a computer, cause the methods in any of the possible implementations of the first to eighteenth aspects to be implemented.

[0152] In a fortieth aspect, a computer program product is provided. The computer program product includes computer program code or instructions that, when read and executed by a computer, cause the methods in any of the possible implementations of the first to eighteenth aspects to be implemented.

[0153] In the forty-first aspect, a computer program is provided. When the computer program is run, it causes the methods in any of the possible implementations of the first to eighteenth aspects above to be implemented.

[0154] It should be understood that the beneficial effects of aspects 19 to 41 above can be referenced from aspects 1 to 18 above and any possible implementation thereof, and will not be elaborated here. Attached Figure Description

[0155] Figures 1 to 4 are schematic diagrams of a communication system applicable to embodiments of this application;

[0156] Figures 5 and 6 are schematic diagrams of an open radio access network (O-RAN) system applicable to embodiments of this application;

[0157] Figure 7 is a schematic diagram of the protocol stack structure related to the communication system 200;

[0158] Figures 8 to 15 are schematic flowcharts of the communication method in the handover (HO) scenario provided in the embodiments of this application;

[0159] Figures 16 to 21 are schematic flowcharts of the communication method in the RLF scenario provided in the embodiments of this application;

[0160] Figure 22 is a schematic block diagram of a communication device provided in an embodiment of this application;

[0161] Figure 23 is a schematic block diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0162] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0163] Before introducing the scheme of this application, the following points should be noted.

[0164] (1) In this application, unless otherwise specified or logically conflicting, the terms 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.

[0165] (2) In this application, "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 there can be three relationships. 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. In the textual description of this application, the character " / " generally indicates that the related objects before and after are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, and c can mean: a, or, b, or, c, or, a and b, or, a and c, or, b and c, or, a, b, and c. Where a, b, and c can be single or multiple.

[0166] (3) In this application, "first," "second," and "#1," "#2" are merely for descriptive convenience and are used to distinguish objects, and are not intended to limit the scope of the embodiments of this application. For example, they are used to distinguish different messages, rather than to describe a specific order or sequence. It should be understood that such described objects can be interchanged where appropriate so as to describe solutions other than those in the embodiments of this application.

[0167] (4) In this application, "instruction" can include direct instruction, indirect instruction, explicit instruction, implicit instruction, etc. When describing an instruction information as indicating A, it can be understood as the instruction information carrying A, carrying the identifier of A, carrying B which is associated with A, carrying the identifier of B which is associated with A, etc. In other words, if the receiving side of an instruction information can determine A based on the instruction information, it can be described as the instruction information indicating A, and the specific method of determination is not limited. When it is understood that the instruction information carries A, "instruction" can be replaced with "includes". In this case, a statement such as "send / receive instruction information, the instruction information indicates A" can be replaced with "send / receive A".

[0168] In this application, the information indicated by the instruction information is called the information to be instructed. In specific implementations, there are many ways to indicate the information to be instructed, such as, but not limited to, directly indicating the information to be instructed, such as the information to be instructed itself or its index. It can also indirectly indicate the information to be instructed by indicating other information, where there is a relationship between the other information and the information to be instructed. It can also indicate only a part of the information to be instructed, while the other parts are known or pre-agreed upon. For example, the instruction of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing instruction overhead to some extent. Furthermore, the information to be instructed can be sent as a whole or divided into multiple sub-information pieces, and the sending period and / or timing of these sub-information pieces can be the same or different.

[0169] (5) In this application, "predefined" may refer to a standard protocol predefined, or it may refer to a pre-agreed or pre-negotiated agreement between devices. "Pre-configuration" can be achieved by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device, and this application does not limit the implementation method. "Protocol" may refer to a standard protocol in the field of communication, such as fourth-generation (4G) protocols. th Generation 4G network, fifth generation (5G) network th This application does not limit the scope to network protocols such as 5G (generation, 5G), New Radio (NR), 5.5G, and related protocols applied in future communication networks.

[0170] (6) In this application, “message”, “information”, “signal” or “information element (IE)” can be used interchangeably. There are no restrictions on the name of the message or information, as long as it can achieve the corresponding function.

[0171] "Sending information to XX (device)" can be understood as the destination of the information being that device. This can include sending information to that device directly or indirectly. "Receiving information from XX (device), or receiving information from XX (device)" can be understood as the source of the information being that device. This can include receiving information from that device directly or indirectly. Information may undergo necessary processing between the source and destination, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this application can be interpreted similarly, and will not be elaborated further here.

[0172] "Communication" can also be described as data transmission, information transmission, data processing, etc. "Transmission" includes sending and / or receiving. "Transmission" can be described as output. "Sending" can also be understood as the output of a chip interface, and "receiving" can be understood as the input of a chip interface. In other words, "sending" or "receiving" can occur between devices, for example, between network devices and terminal devices via an air interface. "Sending" or "receiving" can also occur within a device, for example, between components, modules, chips, software modules, or hardware modules within a device via a bus, wiring, or interface.

[0173] For example, "sending information" can be understood as one device sending information to another device, or it can also be understood as one logical module within a device sending information to another logical module. For instance, "a network device sending information" can be understood as a network device sending information to another device (such as a terminal device), or it can be understood as logical module 1 within the network device sending information to logical module 2 within the network device. Similarly, "receiving information" can be understood as one device receiving information from another device, or it can also be understood as one logical module within a device receiving information from another logical module. For instance, "a network device receiving information" can be understood as a network device receiving information from another device (such as a terminal device), or it can be understood as logical module 1 within the network device receiving information from logical module 2 within the network device.

[0174] (7) In this application, the words “exemplary,” “for example,” etc., are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as an “example” in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of the word “example” is intended to present the concept in a concrete manner. In the embodiments of this application, “of,” “corresponding, relevant,” “corresponding,” and “associate” may sometimes be used interchangeably, and it should be noted that their intended meanings are consistent unless their distinctions are emphasized.

[0175] (8) In this application, the configuration can be signaling configuration, such as RRC messages, downlink control information (DCI), or system information blocks (SIBs). Optionally, the signaling configuration can be pre-configured signaling configuration given to the terminal device, or configured to the terminal device through pre-configuration. Here, pre-configuration means defining or configuring the values ​​of corresponding parameters in advance in a protocol manner, and storing them in the terminal device during communication. The pre-configured messages can be modified or updated when the terminal device is connected to the network.

[0176] The following describes the communication system to which this application applies.

[0177] The technical solutions provided in this application can be applied to various communication systems, such as: 5th generation (5G) or new radio (NR) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, wireless local area network (WLAN) systems, satellite communication systems, future communication systems, or integrated systems of multiple systems. The technical solutions provided in this application can also be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), and Internet of Things (IoT) communication systems or other communication systems.

[0178] The technical solutions provided in this application can also be applied to non-terrestrial network (NTN) systems such as inter-satellite communication and satellite communication. As an example, a satellite communication system includes a satellite base station and terminal equipment. The satellite base station provides communication services to the terminal equipment. The satellite base station can also communicate with other base stations. A satellite can act as a base station or as a terminal device. Here, "satellite" can refer to unmanned aerial vehicles (UAVs), hot air balloons, low-Earth orbit (LEO) satellites, medium-Earth orbit (MEO) satellites, high-Earth orbit (HEO) satellites, etc. "Satellite" can also refer to non-terrestrial base stations or non-terrestrial equipment, etc.

[0179] In a communication system, a device can send signals to or receive signals from another device. These signals can include information, signaling, or data. The device can also be replaced by an entity, network entity, communication device, mobile device, network element, communication module, node, communication node, communication apparatus, etc. This disclosure uses a device as an example. For instance, a communication system can include at least one terminal device and at least one network device. The network device can send downlink signals to the terminal device, and / or the terminal device can send uplink signals to the network device. It is understood that the terminal device in this disclosure can be replaced by a first communication device, and the network device can be replaced by a second communication device, both performing the corresponding communication methods described in this disclosure. Alternatively, the corresponding communication methods in this disclosure can be applied between network devices or between terminal devices, without limitation herein.

[0180] The terminal device in this application embodiment can be a device or module that accesses the aforementioned communication system and has corresponding communication functions. The terminal device can include various devices with wireless communication capabilities, which can be used to connect people, objects, machines, etc. The terminal device can be widely used in various scenarios, such as: cellular communication, D2D, V2X, peer-to-peer, M2M, MTC, IoT, virtual reality (VR), augmented reality (AR), industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, autonomous delivery, etc. The terminal device can be a terminal in any of the above scenarios, such as an MTC terminal, an IoT terminal, etc. Terminal equipment can be user equipment (UE), terminal, fixed equipment, mobile station equipment or mobile equipment, subscriber unit, handheld device, vehicle-mounted equipment, wearable device, cellular phone, smartphone, session initiation protocol (SIP) phone, wireless data card, personal digital assistant (PDA), computer, tablet computer, laptop computer, wireless modem, handset, laptop computer, computer with wireless transceiver capability, smart book, vehicle, satellite, global positioning system (GPS) device, target tracking device, aircraft (e.g., drone, helicopter, multiple helicopters, four helicopters, or airplanes), ship, remote control device, smart home device, industrial equipment, transportation vehicle with wireless communication capability, communication module, or roadside unit with terminal function, all conforming to the 3rd generation partnership project (3GPP) standard. The terminal device (RSU) can be a unit or a device built into the aforementioned equipment (e.g., a communication module, modem, or chip in the aforementioned equipment), or other processing devices connected to a wireless modem. For ease of description, the terminal device will be described below as a terminal or UE.

[0181] It should be understood that in certain scenarios, a UE can also be used as a base station. For example, a UE can act as a scheduling entity, providing sidelink signaling between UEs in scenarios such as V2X, D2D, or end-to-end.

[0182] In this embodiment, the device for implementing the functions of the terminal device can be the terminal device itself, or it can be any device capable of supporting the terminal device in implementing those functions, such as a chip system. This device can be installed in or used in conjunction with the terminal device. In this embodiment, the chip system can be composed of chips or may include chips and other discrete components. This embodiment only uses the terminal device as an example to illustrate the device for implementing the functions of the terminal device, and does not constitute a limitation on the solution of this embodiment.

[0183] The network device in this application embodiment can be a device or module with corresponding communication functions. The network device can be a device used to communicate with terminal devices; it can also be called an access network device or a wireless access network device, such as a base station. In this application embodiment, the network device can refer to a radio access network (RAN) node (or device) that connects the terminal device to the wireless network. A base station can broadly encompass, or be replaced by, various names including: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitter point, master station, auxiliary station, motor slide retainer (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, micro base station, relay node, donor node, or a combination thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. A base station can also be a mobile switching center, a device that performs base station functions in D2D, V2X, and M2M communications, or a device that performs base station functions in future communication systems. A base station can support networks using the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the network equipment.

[0184] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.

[0185] In some deployments, the network devices mentioned in the embodiments of this application may be devices including CU, or DU, or devices including both CU and DU, or devices with control plane CU nodes (central unit-control plane (CU-CP)) and user plane CU nodes (central unit-user plane (CU-UP)) and DU nodes. For example, the network devices may include gNB-CU-CP, gNB-CU-UP, and gNB-DU.

[0186] In some deployments, multiple RAN nodes collaborate to assist terminals in achieving wireless access, with different RAN nodes each implementing some of the base station's functions. For example, RAN nodes can be CUs, DUs, CU-CPs, CU-UPs, or RUs. CUs and DUs can be configured separately or included in the same network element, such as a BBU. RUs can be included in radio frequency equipment or radio frequency units, such as RRUs, AAUs, or RRHs.

[0187] In some deployments, the CU (Core Unit) is a logical node that carries the RRC (Resource Control Code) 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 may be E2 interfaces, etc. Optionally, the CU possesses some core network functions. The CU (e.g., the PDCP layer and higher layers) connects to the DU (e.g., the Radio Link Control (RLC) layer and lower layers) through interfaces, which may be F1 interfaces, etc. 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.). The F1 application protocol (F1AP) is the application protocol for the F1 interface, and in some examples, it defines the F1 signaling procedures. The F1 interface supports both the control plane (F1-C) and the user plane (F1-U).

[0188] In some deployments, the CU can be split into CU-CP and CU-UP. 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. 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. 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. CU-UP can interact with network elements in the core network used to implement user plane functions. The above CU and DU configurations are merely examples; 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 CU or DU can be configured to have only partial protocol layer processing functions. For example, some functions of the RLC layer and the functions of the protocol layer above the RLC layer can be placed in the CU, while the remaining functions of the RLC layer and the functions of the protocol layer below the RLC layer can be placed in the DU. Another example is that the functions of the CU or DU can be divided according to service type or other system requirements. For instance, based on latency, functions that need to meet low latency requirements can be placed in the DU, while functions that do not need to meet such latency requirements can be placed in the CU.

[0189] In some deployments, the DU (Distributed Unit) is a logical node that carries the RLC (Real-Time Control) layer, the medium access control (MAC) layer, the higher physical layer (Higher PHY) layer, and other functions. In some examples, the DU can control at least one RU (Remote Root). 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.

[0190] In some deployments, the RU is a logical node that carries both lower physical layer (PHY) and radio frequency (RF) processing. In some examples, the RU can be a TRP, RRH, or other similar entity. In some examples, the Low-PHY includes portions of the PHY processing, 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.

[0191] The DU and RU can be co-located or not. The DU and RU exchange control plane and user plane information via a fronthaul link through a lower-layer split-control, user, and synchronization (LLS-CUS) interface. LLS-CUS may include interfaces providing control and user planes respectively. In some examples, the control plane refers to real-time control between the DU and RU. The DU and RU exchange management information via a fronthaul link interface (such as an LLS-M interface), and the management plane (M-Plane) refers to non-real-time management operations between the DU and RU.

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

[0193] In one possible design, the processing unit in the BBU used to implement baseband functions is called the baseband high (BBH) unit, and the processing unit in the RRU / AAU / RRH used to implement baseband functions is called the baseband low (BBL) unit.

[0194] 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, a radio access network can also be an open radio access network (O-RAN) architecture. In an O-RAN system, CU can also be called an open CU (open CU, O-CU), DU can also be called an open DU (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-UP), and RU can also be called an open RU (open RU, O-RU). Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software modules and hardware modules.

[0195] In this embodiment, the device for implementing the functions of a network device can be a network device itself, or a device capable of supporting the network device in implementing those functions, such as a chip system, chip, circuit, or communication module (i.e., a communication module that performs communication functions). This device can be installed within the network device. In this embodiment, the chip system can be composed of chips, or it can include chips and other discrete devices. Furthermore, the device can be configured with program instructions for performing corresponding communication functions. This embodiment only uses a network device as an example to illustrate the device for implementing the functions of a network device, and does not limit the solution of this embodiment.

[0196] Network devices and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and satellites. This application does not limit the scenario in which the network devices and terminal devices are located. Furthermore, terminal devices and network devices can be hardware devices, software functions running on dedicated hardware, or software functions running on general-purpose hardware, such as virtualization functions instantiated on a platform (e.g., a cloud platform), or entities that include dedicated or general-purpose hardware devices and software functions. This application does not limit the specific form of the terminal devices and network devices.

[0197] First, a brief introduction to the communication system applicable to the embodiments of this application is given below.

[0198] Figure 1 is a schematic diagram of a communication system 100 applicable to an embodiment of this application. As shown in Figure 1, the communication system includes a network device 110 and an ambient Internet of Things (AIoT) device 120. The network device 110 and the AIoT device 120 communicate bidirectionally. The communication between the network device 110 and the AIoT device 120 includes ambient Internet of Things data and / or signaling. That is, the network device 110 sends downlink data and / or signaling to the AIoT device 120, and the AIoT device 120 sends uplink data and / or signaling to the network device 110. Alternatively, it can be understood that the network device 110 and the AIoT device 120 transmit uplink and downlink data and / or signaling.

[0199] Figure 2 is a schematic diagram of a communication system 200 applicable to an embodiment of this application. As shown in Figure 2, the communication system includes a network device 210, an intermediate node 220, and an AIoT device 230. The network device 210 and the AIoT device 230 communicate bidirectionally with the intermediate node 220. For example, the network device 210 communicates bidirectionally with the intermediate node 220, and then the intermediate node 220 communicates bidirectionally with the AIoT device 120. That is, the network device 210 transmits uplink and downlink data and / or signaling between itself and the intermediate node 220, and the intermediate node 220 transmits uplink and downlink data and / or signaling between itself and the AIoT device 120. In this embodiment, the intermediate node 220 can be a repeater, an integrated access backhaul (IAB) node, a UE, etc.

[0200] Figure 3 is a schematic diagram of a communication system 300 applicable to an embodiment of this application. As shown in Figures 3(a) and (b), the communication system includes a network device 310, an auxiliary node 320, and an AIoT device 330. In Figure 3(a), the AIoT device 330 sends data and / or signaling to the network device 310, the network device 310 sends data and / or signaling to the auxiliary node 320 via the Uu interface, and then the AIoT device 330 receives data and / or signaling from the auxiliary node 320. In Figure 3(b), the AIoT device 330 receives data and / or signaling sent by the network device 310 and sends data and / or signaling to the auxiliary node 320, and then the network device 310 receives data and / or signaling from the auxiliary node 320 via the Uu interface. In this embodiment of the application, the intermediate node of the auxiliary node 320 may be a repeater, an IAB node, a UE, etc.

[0201] Figure 4 is a schematic diagram of a communication system 400 applicable to an embodiment of this application. As shown in Figure 4, the communication system includes a terminal device 410 and an AIoT device 420. The terminal device 410 and the AIoT device 420 communicate bidirectionally. The communication between the terminal device 410 and the AIoT device 420 includes environmental IoT data and / or signaling. That is, the terminal device 410 sends downlink data and / or signaling to the AIoT device 420, and the AIoT device 420 sends uplink data and / or signaling to the terminal device 410. It can also be understood that the terminal device 410 and the AIoT device 420 transmit uplink and downlink data and / or signaling.

[0202] Figures 1 to 4 are merely schematic diagrams. The communication system to which the embodiments of this application are applicable may also include other devices, such as core network elements, wireless relay devices and / or wireless backhaul devices, which are not shown in Figures 1 to 4.

[0203] The embodiments of this application can also be applied to open RAN (O-RAN) system architecture.

[0204] Figure 5 is a schematic diagram of a communication system 500 applicable to an embodiment of this application. As shown in Figure 5, the O-RAN system may include core network (CN) equipment, access network (RAN) equipment, and terminal equipment (UE). The access network equipment communicates with core network elements through a backhaul link and with the terminal equipment through an air interface. For example, the BBU in the access network equipment communicates with core network elements through a backhaul link, and the RU in the access network equipment communicates with the terminal equipment through an air interface. The BBU communicates with at least one RU through a fronthaul link. The BBU and RU may or may not be co-located. The BBU includes at least one CU and at least one DU, and the CU and DU can communicate through at least one midhaul link.

[0205] Figure 5 is just a schematic diagram. The wireless communication system may also include other devices, which are not shown in Figure 5.

[0206] Figure 6 is a schematic diagram of the application framework involving the RIC module under the O-RAN architecture. As shown in Figure 6, the 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). The non-real-time RIC mainly processes non-real-time information, such as data that is not sensitive to latency, with latency in the order of seconds. The real-time RIC mainly processes near-real-time information, such as data that is relatively sensitive to latency, with latency in the order of tens of milliseconds.

[0207] The near real-time RIC and non-real-time RIC can also be set up as separate network elements. Optionally, the near real-time RIC and non-real-time RIC can also be part of other devices. For example, the near real-time RIC can be set in the RAN node (e.g., in CU, DU), while the non-real-time RIC can be set in the OAM, cloud server, core network element, or other network device.

[0208] To facilitate a better understanding of the technical solution of this application, some related technologies involved in the technical solution of this application are introduced.

[0209] 1. Passive Radio Frequency Identification (RFID):

[0210] An RFID system consists of an interrogator and tags, which communicate with each other without contact. The interrogator can read information from the tag or write information to the tag. The tag itself is simple, requiring excitation from the interrogator to transmit information; it converts the wireless signal emitted by the interrogator into energy to power itself. If RFID is applied to mobile communication systems, such as 5G systems, the base station can act as the interrogator, fulfilling its functions.

[0211] The primary application of RFID is identification, but it can also be used for data reading and writing. The tags have the following characteristics:

[0212] 1) The label design is simple, for example, the application layer and air interface signaling are combined into one design.

[0213] 2) The tag supports power consumption in the microwatt (μW) level or hundreds of microwatts level, but cannot support complex designs or complex measurements.

[0214] 3) When using multi-tag communication, time-division multiplexing is used, and multiple tags are read serially. It does not support the distinction between the frequency domain and the code domain, and its parallel performance is poor.

[0215] 2. AIoT (or AIoT):

[0216] Devices in AIoT technology can include network devices and Type I terminal devices; or, in other words, AIoT-based communication systems can include network devices and Type I terminal devices. Type I terminal devices can be terminal devices with AIoT functionality, also referred to as AIoT devices. In this case, both A-IoT-enabled UEs and AIoT devices can be implemented based on cellular network infrastructure. In other words, both A-IoT-enabled UEs and AIoT devices can be devices within a cellular network. For example, the functionality of an A-IoT-enabled UE can be implemented by network devices, such as base stations; or, the functionality of an A-IoT-enabled UE can also be implemented by terminal devices. AIoT devices can also be referred to as devices and can be implemented by terminal devices within a cellular network, such as ultra-low-power, ultra-low-complexity IoT terminal devices (e.g., Type I terminal devices). Non-contact data communication can be performed between network devices and Type I terminal devices to read information from and / or write information to be stored in the Type I terminal devices. AIoT technology can be used to implement one or more of the following services: inventory, positioning, sensing, or command. For example, command-line operations can include implementing read, write, disable, kill, or lock processes. In terms of application scope, AIoT technology can be applied to scenarios such as logistics, warehousing, industrial manufacturing, identity recognition, and environmental monitoring.

[0217] Inventory management involves using readers (e.g., base stations or terminal devices) to connect to AIoT devices within the coverage area. Successfully connected devices need to send their unique identifier (identifiable by the network, such as the EPC in RFID) to the reader. Inventory management, also known as a checklist operation, retrieves tag identification information. For example, readers can use commands like `query` and `ACK` to obtain tag identification information. To facilitate tag inventory, tags include four session identifiers, each corresponding to two inventory states: A and B. The inventory state is indicated by a sessInventoried flag. When a reader selects a tag, the selection command sent to it includes a session identifier, which the tag then stores. When the reader performs inventory management on the tag, the query command sent to it includes the session identifier, at which point the tag can flip its inventory state from A to B. If the reader sends a query command to perform inventory operations again, the tag will not respond to the reader because the inventory status of the tag is B, thus avoiding the same tag being inventoried multiple times in the same inventory cycle.

[0218] Positioning is the process of using location signals to pinpoint the location of AIoT devices.

[0219] Sensing involves AIoT devices reporting sensor data to the base station, such as temperature data.

[0220] Commands are operational instructions, such as read, write, disable, kill, or lock. Read operations can read the EPC, tag identifier (TID), content stored in the tag's reserved area, or content stored in the user's storage area from the tag's memory. Write operations can perform write operations on the tag's storage area; for example, a network device (e.g., a base station) can send a downlink command and data to instruct the AIoT device to write data to its storage area. Disable operations can temporarily or permanently disable the tag, preventing both reading and writing of data to its memory. Kill operations can permanently disable the tag. Lock operations can lock the tag's information, preventing read or write operations on that tag. Alternatively, lock operations can also lock a storage area, preventing or disallowing read or write operations on that storage area; for example, a network device can send a downlink command to instruct the AIoT device to lock a specified address in the storage area, making the contents of that storage area immutable and / or unreadable.

[0221] 3. AIoT devices (or AIoT equipment):

[0222] With the increasing application of MTC and IoT communication in 5G NR communication, the number of connected IoT devices is growing daily. Therefore, the industry's demand for reduced cost and power consumption of IoT devices is becoming increasingly strong. During the 4G era, 3GPP introduced Narrow-Band IoT (NB-IoT) systems. However, NB-IoT terminals still require external power (battery) and have the ability to generate local high-frequency carrier waves, thus limiting their power consumption to milliwatts. But with the evolution and development of 5G IoT, the need for lower-power terminals in 5G networks is growing. Passive Radio Frequency Identification (RFID) technology provides a good technical reference for low power consumption, supporting microwatt-level power consumption. RFID terminals (tags) use low-precision, low-power mid-to-low frequency ring oscillators or receive downlink signals without a local oscillator. When the tag is working, the energy and carrier wave for communication are supplied by the reader, and communication is based on reflected carrier waves.

[0223] Given the low power consumption advantage of RFID communication technology, 5G AIoT has emerged. To meet ultra-low power consumption requirements, terminal devices in AIoT also use low-precision, low-power mid-to-low frequency ring oscillators or receivers without a local oscillator to receive downlink signals. This receiving method further reduces the power consumption of downlink reception. However, for such low-power receiving methods, only amplitude detection, such as envelope detection, can be performed because a low-precision ring oscillator alone cannot guarantee accurate demodulation of signal phase information.

[0224] AIoT devices can be divided into three categories: device A, device B, and device C.

[0225] (1) Device A (similar to a passive tag): It has no energy storage, cannot generate independent signals, and uses backscattering to transmit signals.

[0226] (2) Device B (similar to a semi-passive tag): It has energy storage but cannot generate signals independently; it uses backscattering to transmit signals. The energy it stores can amplify the reflected signal.

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

[0228] The 3GPP meeting further defined the following three types of AIoT devices: device 1, device 2a, and device 2b.

[0229] (1) Device 1: Peak power consumption is approximately 1μW, with energy storage function, and initial sampling frequency offset (SFO) reaches 10. X At parts per million (ppm), it cannot amplify downlink (DL) or uplink (UL) signals. It requires an external carrier signal for backscatter communication to enable uplink transmission.

[0230] (2) Device 2a: Peak power consumption less than or equal to several hundred μW, with energy storage function, and initial sampling frequency offset of 10. X ppm can amplify DL and / or UL signals. An external carrier signal is required for backscatter communication in order to perform uplink transmission.

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

[0232] 4. AIoT data and / or signaling:

[0233] AIoT data and / or signaling are related to AIoT services. For example, for inventory services, AIoT data and / or signaling may include a device ID or an encrypted device ID; for read command services, AIoT data and / or signaling may include read commands and / or read response data; for write command services, AIoT data and / or signaling may include write commands and / or write feedback; for other AIoT services, AIoT data and / or signaling may include the corresponding uplink (UL) data (UL Data) reported by the AIoT device to the AIoT-enabled UE.

[0234] Figure 7 illustrates the CN architecture applicable to the aforementioned communication system 200. As shown in Figure 7, AIoT devices and UEs can exchange AIoT data and / or signaling via the AIoT radio interface. The UE exchanges AIoT data and / or signaling with AIoT-enabled core network elements (AIoT tag management function (TMF) network elements as shown in Figure 7) through an AIoT-enabled gNB. There can be various communication methods between the AIoT-enabled gNB and the AIoT-enabled core network elements.

[0235] The embodiments of this application can be applied to the network architecture of topology 2, where the UE acts as an A-IoT-enable UE to perform AIoT services.

[0236] Under the topology 2 architecture, there are currently three solutions that can be used to transmit one or more of the following: messages, data, or signaling related to AIoT services.

[0237] Solution 1: RRC-based solution. Here, A-IoT-enabled UE refers to a UE that is A-IoT-enabled.

[0238] The protocol stack corresponding to solution 1 can be referred to in Figure 7(a). The AIoT device includes AIoT radio protocol layers for communication with the A-IoT-enabled UE. The A-IoT-enabled UE includes AIoT radio protocol layers for communication with the AIoT device, as well as the RRC layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and Physical (PHY) layer for communication with access network devices. The access network device includes the RRC layer, PDCP layer, RLC layer, MAC layer, and PHY layer for communication with the A-IoT-enabled UE; it also includes the XXAP layer, Stream Control Transmission Protocol (SCTP) layer, Internet Protocol (IP) layer, Layer 2 (L2), and Layer 1 (L1) for communication with AIoT core network elements. The AIoT core network elements include the XXAP layer, SCTP layer, IP layer, L2 layer, and L1 layer, which communicate with access network devices. These AIoT core network elements may be, for example, AIoTF, or AMF capable of executing AIoT services or implementing AIoT functions.

[0239] Specifically, after the access network device receives an AIoT service-related request from the AIoT core network element via XXAP, it can further send the relevant information to the A-IoT-enabled UE via RRC message; when the access network device receives AIoT service-related data / signaling from the A-IoT-enabled UE via RRC, it can further transmit the relevant information to the AIoT core network element via XXAP.

[0240] As shown in Figure 7(a), information related to AIoT services can be forwarded via NR Uu RRC between an AIoT-enabled UE and an AIoT-enabled gNB.

[0241] AIoT devices include one or more of the following protocol layers: for transmitting AIoT service-related information between the AIoT device and the AIoT CN; and an AIoT wireless protocol layer for transmitting AIoT service-related information between the AIoT device and the AIoT-enabled UE.

[0242] AIoT-enabled UEs include one or more of the following protocol layers: AIoT radio protocol layer, used to transmit AIoT service-related information between AIoT devices and AIoT-enabled UEs; RRC, which can be used to transmit AIoT service-related information between AIoT-enabled UEs and AIoT-enabled gNBs; PDCP, RLC, MAC, or PHY.

[0243] AIoT-enabled gNBs include one or more of the following protocol layers: XXAP, SCTP, IP, L2, L1, RRC, PDCP, RLC, MAC, or PHY.

[0244] AIoT CN includes one or more of the following protocol layers: XXAP, SCTP, IP, L2, or L1.

[0245] The gNB supporting AIoT can include the following functions: allocating time and frequency resources for communication between the UE and AIoT devices, and transmitting AIoT service-related data and / or signaling. The core network element supporting AIoT can be one of the following: access and mobile management function (AMF), TMF element, ambient IoT management function (AIoTMF), ambient IoT function (AIoTF), AIoT-aware core network (AIoT-aware CN), or other core network elements / nodes / devices that support or enable AIoT.

[0246] The UE can be called an AIoT-enabled UE, an A-IoT-enable UE, or an intermediate node.

[0247] Solution 2: NAS-based solution.

[0248] The protocol stack for solution 2 can be found in Figure 7(b). The AIoT device includes AIoT radio protocol layers for communication with the A-IoT-enabled UE. The A-IoT-enabled UE includes AIoT radio protocol layers for communication with the AIoT device, a NAS layer for communication with AIoT core network elements, and 5G-access network protocol layers (AN protocol layers) for communication with access network devices. The access network devices include 5G-AN protocol layers for communication with the A-IoT-enabled UE; they also include next-generation application protocol (NGAP) layers, SCTP layers, IP layers, L2, and L1 layers for communication with AIoT core network elements. The AIoT core network elements include a NAS layer for communication with the A-IoT-enabled UE, and also NGAP layers, SCTP layers, IP layers, L2, and L1 layers for communication with access network devices. These AIoT core network elements can be, for example, a TMF (Technology Management Function), or an AMF (Application Function) capable of executing AIoT services or implementing AIoT functions.

[0249] Solution 2 can be understood as follows: one or more of the messages, data, or signaling related to AIoT services between the AIoT core network elements and the A-IoT-enabled UE are carried on the DL NAS packet or UL NAS packet of the A-IoT-enabled UE for transmission (where the access network device can transparently transmit the NAS packet). The access network device can process the NAS packet of the A-IoT-enabled UE on the NGAP interface through the existing DL NAS transport message (DL NASTransport msg) and / or UL NAS Transport msg.

[0250] As shown in Figure 7(b), the gNB cannot see the AIoT-related processes; these processes are implemented in the NAS layer of the A-IoT-enable UE. A NAS layer exists between the AIoT-enabled UE and the AIoT CN for transmitting AIoT service-related information. When the AIoT CN knows about the AIoT-enabled UE and the AIoT-enabled gNB, AIoT service-related information (e.g., service requests) can be transmitted through the NAS between the AIoT-enabled UE and the AIoT CN.

[0251] AIoT devices include one or more of the following protocol layers: AIoT wireless protocol layer, used to transmit AIoT service-related information between the AIoT device and the AIoT-enabled UE.

[0252] AIoT-enabled UEs include one or more of the following protocol layers: AIoT radio protocol layer, NAS, or 5G access network (AN) protocol layer. The 5G access network protocol layer may include one or more of the following: RRC, PDCP, RLC, MAC, or PHY.

[0253] AIoT-enabled gNBs include one or more of the following protocol layers: 5G access network protocol layer, NGAP, SCTP, IP, L2, or L1.

[0254] AIoT CN includes one or more of the following protocol layers: NAS, NGAP, SCTP, IP, L2, or L1.

[0255] Solution 3: User plane (UP) based solution.

[0256] The protocol stack for solution 3 can be found in Figure 7(c). The AIoT device includes AIoT radio protocol layers for communication with the A-IoT-enabled UE. The A-IoT-enabled UE includes AIoT radio protocol layers for communication with the AIoT device, a Protocol Data Unit (PDU) layer for communication with core network elements, and 5G-AN protocol layers for communication with access network devices. The access network devices include 5G-AN protocol layers for communication with the A-IoT-enabled UE; they also include the General Packet Radio Service (GPRS) Tunneling Protocol User Plane (GTP-U) layer, User Datagram Protocol (UDP) layer, IP layer, L2, and L1 layers for communication with core network elements. The core network elements include the PDU layer for communication with the A-IoT-enabled UE, and also the GTP-U layer, UDP layer, SCTP layer, IP layer, L2, and L1 layers for communication with access network devices. This core network element is, for example, a core network user plane device, such as a UPF. This core network element can communicate with AIoT core network elements, or can communicate with AIoT core network elements through other network elements (such as AMFs). This AIoT core network element is, for example, a TMF, or an AMF capable of executing AIoT services or implementing AIoT functions. For example, this core network element can send one or more of the following messages, data, or signaling related to AIoT services from an A-IoT-enabled UE or access network device to itself; similarly, this core network element can send one or more of the following AIoT service-related messages, data, or signaling from an AIoT core network element to an A-IoT-enabled UE or access network device.

[0257] AIoT service-related data / signaling between AIoT core network elements and A-IoT-enabled UEs can be carried on the PDU Session of the A-IoT-enabled UE (access network devices can transmit transparently). The access network device can process the user plane data of the A-IoT-enabled UE through channels such as next-generation user plane (NG-U) and general packet radio service (GPRS) tunneling protocol user plane (GTP-U).

[0258] As shown in Figure 7(c), the gNB cannot see the AIoT-related processes. AIoT service-related data / signaling between the AIoT CN and the A-IoT-enable UE is transmitted on the A-IoT-enable UE's PDU Session (transparently transmitted to the A-IoT-enable gNB). The gNB processes the A-IoT-enable UE's user plane data through the NG-U GTP-U channel. A PDU layer exists between the AIoT-enabled UE and the AIoT CN for transmitting AIoT service-related information. When the AIoT CN knows about the AIoT-enabled UE and the AIoT-enabled gNB, AIoT service-related information (e.g., service requests) can be transmitted through the PDU between the AIoT-enabled UE and the AIoT CN.

[0259] AIoT devices include one or more of the following protocol layers: AIoT wireless protocol layer, used to transmit AIoT service-related information between the AIoT device and the AIoT-enabled UE.

[0260] AIoT-enabled UEs include one or more of the following protocol layers: AIoT radio protocol layer, NAS, or 5G access network (AN) protocol layer. The 5G access network protocol layer may include one or more of the following: RRC, PDCP, RLC, MAC, or PHY.

[0261] AIoT-enabled gNBs include one or more of the following protocol layers: 5G access network protocol layer, GTP-U, UDP, IP, L2, or L1.

[0262] AIoT CN includes one or more of the following protocol layers: PDU layer, GTP-U, UDP, IP, L2, or L1.

[0263] Figure 7 is merely an exemplary protocol stack corresponding to the three solutions above. Alternatively, any one or more of the three solutions above may correspond to other forms of protocol stacks, without limitation.

[0264] Based on the aforementioned communication system 200, in some scenarios, a UE reader performing AIoT services (such as inventory management) may undergo cell handover. For example, in a HO scenario, a UE reader performing AIoT services may switch from the source gNB to a new target gNB. Alternatively, in an RLF scenario, a UE reader performing AIoT services may undergo cell selection / cell reselection (e.g., it may switch to a cell under a new target gNB) after the source cell declares an RLF. In these cases, ensuring the continuity of AIoT services is a crucial issue. Specifically, how does the new target gNB determine whether the UE can continue as a reader, or whether the UE can continue performing its previous AIoT services? Or, if the new target gNB determines that the UE can continue performing its previous AIoT services, how does the new target gNB configure AIoT resources for the UE?

[0265] In view of this, embodiments of this application provide a communication method and a communication device to support the effective transmission of AIoT data and / or signaling, ensure the continuity of AIoT services, and protect the user's service experience.

[0266] The method provided by the embodiments of this application will be described in detail below with reference to the accompanying drawings. The embodiments provided by this application can be applied to the communication system shown in FIG2 above, and are not limited thereto.

[0267] It should be noted that the following description uses the interaction between a first terminal (e.g., UE), a first access network device (e.g., source gNB or last serving gNB), a second access network device (e.g., target gNB or new station), and a core network element (e.g., AMF or AIoTF) as an example to illustrate the method provided in this application embodiment. The first terminal can be replaced by a terminal device or a component of a terminal device (e.g., a chip, chip system, circuit, or communication module). The access network device can be replaced by an access network device or a component of an access network device (e.g., a chip, chip system, circuit, or communication module). The core network element can be replaced by a core network element or a component of a core network element (e.g., a chip, chip system, circuit, or communication module).

[0268] It should be noted that, in the HO scenario, the first access network device is the source gNB, and the second access network device is the target gNB. In the RLF scenario, the first access network device (origin site) is the last serving gNB, and the second access network device (new site) is the new gNB.

[0269] Furthermore, the steps described below as being performed by a single execution entity can also be divided into being performed by multiple execution entities, which may be logically and / or physically separate.

[0270] In the embodiments of this application, the core network element can be one of the following: access and mobile management function (AMF), tag management function (TMF) network element, ambient IoT management function (AIoTMF), ambient IoT function (AIoTF), ambient IoT aware core network (AIoT aware CN), etc. Alternatively, the core network element can be other core network elements / nodes / devices that support or enable AIoT. This application does not limit the name of the core network element.

[0271] Core network elements are core network elements that serve the first access network equipment and / or the second access network equipment.

[0272] Core network elements are used to transmit AIoT data and / or signaling; in other words, core network elements are those that provide services to AIoT devices. Core network elements can be AIoTF, TMF, AIoTMF, AIoT-aware CN, or other core network elements that support or enable AIoT. Core network elements are not used to transmit non-AIoT data and / or signaling.

[0273] The source gNB or target gNB refers to an AIoT-enabled network device, or a network device that supports AIoT. An AIoT-enabled network device may include the ability to provide resource allocation, meaning it can allocate resources to the UE to support communication between the UE and AIoT devices.

[0274] Figure 8 is a schematic diagram of a communication method 800 provided in an embodiment of this application. As shown in Figure 8, method 800 may include the following steps; for details not covered herein, please refer to the relevant description of method 1000 in Figure 10 below.

[0275] S810, optionally, the first access network device determines whether the first terminal continues to execute the first AIoT service.

[0276] In one implementation, the first access network device determines whether the first terminal should continue to execute the first AIoT service based on the area information and the type of the first terminal.

[0277] For example, if the UE is located within the cell covered by the target gNB, or in other words, the UE is located in the area of ​​the first AIoT service, then the UE can be considered to continue acting as a reader, and / or continue to execute the current first AIoT service, and / or report data and / or signaling related to the first AIoT service; conversely, if the UE is not located within the cell covered by the target gNB, or in other words, the UE is not located in the area of ​​the first AIoT service, or in other words, the UE is located outside the area of ​​the first AIoT service, then the UE can be considered not to continue acting as a reader, or not to continue executing the current first AIoT service, and / or not to report data and / or signaling related to the first AIoT service.

[0278] For example, if the first terminal type indicates that the UE is a reader / writer, then the UE can be considered to continue acting as a reader, and / or continue to execute the current first AIoT service, and / or report data and / or signaling related to the first AIoT service; conversely, if the first terminal type indicates that the UE does not support the reader / writer function, then the UE can be considered not to continue acting as a reader, or not to continue executing the current first AIoT service, and / or not to report data and / or signaling related to the first AIoT service.

[0279] S820, the first access network device sends a first message to the second access network device;

[0280] Correspondingly, the second access network device receives the first message from the first access network device.

[0281] The first message is used to request the first terminal to be switched to the second access network device. The first message includes the first terminal type, which includes the first terminal being a reader or a terminal that does not support the reader function. The second identifier is used to identify the first AIoT service.

[0282] In one implementation, when it is determined that the first terminal continues to execute the first AIoT service, the first access network device sends a first message to the second access network device, and correspondingly, the second access network device receives the first message from the first access network device.

[0283] For example, the first message includes at least one of the following: area information, a second identifier, the first terminal continuing to execute the first AIoT service, the first terminal having an ongoing AIoT service, the first terminal continuing to execute the first AIoT service, or the first terminal reporting data and / or signaling related to the first AIoT service. Wherein, the second identifier is used to identify the first AIoT service, and the area information indicates the area where the first AIoT service is executed.

[0284] S830, the second access network device sends a second message to the second access network device;

[0285] Correspondingly, the first access network device receives a second message from the second access network device.

[0286] The second message includes a first resource allocated by the second access network device to the first terminal, which is used to execute the first AIoT service.

[0287] Optionally, the method further includes: the second access network device sending a third message to the first terminal, and correspondingly, the first terminal receiving the third message from the second access network device. The third message instructs the first terminal to switch to the second access network device. The third message includes indication information indicating a first resource.

[0288] For example, the third message could be a toggle command (HandoverCommand).

[0289] Furthermore, the first terminal continues to execute the first AIoT service based on the first resource. Optionally, if the third message does not indicate the first resource, the first terminal stops executing or does not execute the first AIoT service.

[0290] Optionally, before sending the first message to the second access network device, the method further includes: determining that the signal reception quality of the first terminal is less than or equal to a first threshold.

[0291] Optionally, the method further includes: if it is determined that the first terminal will not continue to execute the first AIoT service, sending a fourth message to the second access network device, the fourth message being used to request switching the first terminal to the second access network device; receiving a fifth message from the second access network device, the fifth message including a fourth resource allocated by the second access network device to the first terminal, the fourth resource being used by the first terminal to execute non-AIoT services; and sending a sixth message to the first terminal, the sixth message instructing the first terminal to switch to the second access network device. The sixth message includes indication information indicating the fourth resource, which is used by the first terminal to execute non-AIoT services.

[0292] Optionally, the method further includes: if it is determined that the first terminal will not continue to perform the first AIoT service, refusing to send a fourth message to the second access network device, the fourth message being used to request the first terminal to be switched to the second access network device, or refusing to switch the first terminal to the second access network device.

[0293] Furthermore, the first terminal continues to execute the first AIoT service based on the first resource. Optionally, if the seventh message does not indicate the first resource, the first terminal stops executing or does not execute the first AIoT service.

[0294] Optionally, the first terminal receives indication information from the second access network device, which indicates a timer and / or a valid area. That is, the first terminal can execute or perform a first AIoT service within a period of time indicated by the timer and / or within the valid area.

[0295] Figure 9 is a schematic diagram of a communication method 900 provided in an embodiment of this application. As shown in Figure 9, method 900 may include the following steps; for details not covered herein, please refer to the relevant description of method 2 in method 1000 of Figure 10 below.

[0296] S910, the first access network device sends a first message to the second access network device;

[0297] Correspondingly, the second access network device receives the first message from the first access network device.

[0298] The first message is used to request the first terminal to be switched to the second access network device. The first message includes first indication information, which indicates the type of the first terminal. The first terminal type includes the first terminal being a reader or a terminal that does not support the function of a reader.

[0299] For example, the first message includes at least one of the following: resource request information, area information, a second identifier, whether to continue executing the first AIoT service, whether to continue acting as a reader / writer for the first AIoT service, whether there is an ongoing AIoT service, or whether to report data and / or signaling related to the first AIoT service. The resource request information is used to request a first resource, the first resource is used to execute the first AIoT service, the second identifier is used to identify the first AIoT service, the area information indicates the area for executing the first AIoT service, and the area information and the first terminal type are used to determine the second indication information.

[0300] For example, the resource request information includes at least one of the following:

[0301] (1) The number of resource blocks (RBs) or the duration of communication between the first terminal and the AIoT device;

[0302] (2) The first terminal requests or indicates whether it supports LTE or NR guard band, inband, or standalone bands;

[0303] (3) The frequency band number supported by the first terminal or the frequency band number requested by the first terminal.

[0304] Based on this, the second access network device can indicate appropriate frequency domain resource configuration (such as appropriate frequency band, number of RBs, or configuration method) and time domain resource configuration (such as duration) when allocating resources to the first terminal according to the resource request information, thereby improving the user service experience.

[0305] The frequency domain configuration / deployment methods include guard band, inband, or standalone bands.

[0306] Optionally, the method further includes: the second access network device receiving a third message (e.g., PATH SWITCH REQUEST ACKNOWLEDGE) from a core network element, the third message including third indication information, the third indication information indicating that the first terminal is authorized as a reader / writer for the first AIoT service.

[0307] As an example, if the second access network device cannot determine the resource allocation method, it can first allocate resources to the first terminal, allowing the first terminal to use these resources (i.e., the second access network device sends a second message to the first access network device carrying AIoT resources; then the first access network device sends a HandoverCommand message to the first terminal carrying AIoT resources). Afterwards, the second access network device receives a PATH SWITCH REQUEST ACKNOWLEDGE message from the core network element, which includes an indication to deny authorization for the first terminal as a reader. Then, it instructs the first terminal to stop or cease performing the first AIoT service via an RRC message, and / or instructs the release of the first resources.

[0308] Optionally, the first access network device can allocate resources first, allowing the first terminal to continue using them. After the first terminal receives the resources allocated by the new station from the handover command, it can then use the resources allocated by the second access network device to perform AIoT services.

[0309] Optionally, the method further includes: receiving a message #1 from a core network element, the message #1 including indication information #1, which indicates that authorization for the first terminal as a reader / writer for the first AIoT service is denied. At this time, the first access network device or the second access network device sends indication information #2 to the first terminal, which indicates that the first AIoT service should be stopped or discontinued, and / or indicates that the first resource should be released.

[0310] Optionally, before the first access network device sends the first message to the second access network device, the method further includes: determining that the signal reception quality of the first terminal is less than or equal to a first threshold.

[0311] S920, optionally, the second access network device determines whether the first terminal continues to execute the first AIoT service.

[0312] In one implementation, the second access network device determines whether the first terminal should continue to perform the first AIoT service based on regional information and / or the type of the first terminal.

[0313] For example, if the UE is located within the cell covered by the target gNB, or in other words, the UE is located in the area of ​​the first AIoT service, then the UE can be considered to continue acting as a reader, and / or continue to execute the current first AIoT service, and / or report data and / or signaling related to the first AIoT service; conversely, if the UE is not located within the cell covered by the target gNB, or in other words, the UE is not located in the area of ​​the first AIoT service, or in other words, the UE is located outside the area of ​​the first AIoT service, then the UE can be considered not to continue acting as a reader, or not to continue executing the current first AIoT service, and / or not to report data and / or signaling related to the first AIoT service.

[0314] For example, if the first terminal type indicates that the UE is a reader / writer, then the UE can be considered to continue acting as a reader, and / or continue to execute the current first AIoT service, and / or report data and / or signaling related to the first AIoT service; conversely, if the first terminal type indicates that the UE does not support the reader / writer function, then the UE can be considered not to continue acting as a reader, or not to continue executing the current first AIoT service, and / or not to report data and / or signaling related to the first AIoT service.

[0315] S930, the second access network device sends a second message to the first access network device;

[0316] Correspondingly, the first access network device receives a second message from the second access network device.

[0317] The second message includes a second instruction message, which instructs the first terminal to continue acting as a reader / writer for the first environment's Internet of Things (AIoT) service, and / or the first terminal to continue executing the first AIoT service.

[0318] Understandably, the second instruction information is determined based on the first terminal type.

[0319] For example, the second indication information also indicates at least one of the following: a first resource, the first terminal reporting data and / or signaling related to the first AIoT service, or indicating permission to continue indicating the first AIoT service. The first resource is allocated to the first terminal by the second access network device, and the first resource is used to execute the first AIoT service.

[0320] Optionally, the method further includes: the first access network device sending a fourth message to the first terminal, the fourth message instructing the first terminal to switch to the second access network device, the fourth message including fourth indication information, the fourth indication information indicating the first resource.

[0321] Optionally, before performing step S930, i.e. before receiving the second message from the second access network device, the method further includes: the first access network device sending a fifth message to the first terminal, the fifth message including fifth indication information, the fifth indication information indicating a third resource, the third resource being used by the first terminal to perform the first AIoT service before switching to the second access network device.

[0322] Understandably, before triggering a handover, the first access network device can provide a third resource to the first terminal, allowing the first terminal to execute the first AIoT service using the third resource before switching to the second access network device. Optionally, the third resource can be either the first resource or the second resource.

[0323] For example, the fifth message is carried in an RRC message.

[0324] The task request message (e.g., inventoryRequest) sent by the first access network device to the first terminal can be included in the inventoryRequest message, or it can be included outside of the inventoryRequest message; there is no limitation on this. It is understood that the inventoryRequest message can be an element carried in an RRC message.

[0325] Furthermore, the first terminal continues to execute the first AIoT service based on the first resource. Optionally, if the seventh message does not indicate the first resource, the first terminal stops executing or does not execute the first AIoT service.

[0326] Optionally, the first terminal receives indication information from the second access network device, which indicates a timer and / or a valid area. That is, the first terminal can execute or perform a first AIoT service within a period of time indicated by the timer and / or within the valid area.

[0327] Figure 10 is a schematic diagram of a communication method 1000 provided in an embodiment of this application. As shown in Figure 10, taking the first terminal as UE, the core network element as AMF / AIoTF, the first access network device as the source gNB, and the second access network device as the target gNB as an example, this method is applicable to the RRC-based solution architecture in the HO scenario, and the method 1000 may include the following multiple steps.

[0328] S1001, AMF / AIoTF sends AIoT (or A-IoT) service request message #1 to the source gNB;

[0329] Correspondingly, the source gNB receives AIoT service request message #1 from AMF / AIoTF.

[0330] The AIoT service request message #1 (e.g., Inventory Request or Command / Command Request) is used to request the execution of a first AIoT service (e.g., inventory service). The AIoT service request message #1 includes service area information, indicating the area used to execute the first AIoT service. For example, for an inventory service, the service area information refers to the inventory area, i.e., the area used for the inventory service. For example, the core network can map the service area to cell / TAI information, such as the service area information indicating cell #1 and cell #2. Cell #1 is associated with the source gNB, which can be understood as the coverage area of ​​the source gNB including cell #1. The coverage area of ​​the source gNB can include one or more cells, which is not limited in this application. Similarly, cell #2 is associated with the target gNB, which can be understood as the coverage area of ​​the target gNB including cell #2. The coverage area of ​​the target gNB can include one or more cells, which is not limited in this application.

[0331] Optionally, the AIoT service request message #1 may also include at least one of the following: a first identifier (e.g., device identification) and / or a second identifier (e.g., service / session / task / transaction ID), wherein the first identifier is used to identify an AIoT device, a group of AIoT devices, or all AIoT devices, for example, identifying an AIoT device through a mask and identifying the entire group of AIoT devices through a group ID. In one possibility, the AIoT service request message may not include the identification information of the AIoT devices, indicating that all AIoT devices are executing the current AIoT service. The second identifier is used to identify the first AIoT service.

[0332] In this application, the UE performs a first AIoT service or reports data and / or signaling corresponding to the first AIoT service, including: the UE sending data and / or signaling related to the first AIoT service to an AIoT device, and / or the UE receiving data and / or signaling related to the first AIoT service from an AIoT device, and / or reporting data and / or signaling corresponding to the first AIoT service.

[0333] It is understood that the data and / or signaling associated with different first AIoT services may differ. For example, if the first AIoT service is an inventory service, the data and / or signaling associated with it may include an inventory request, a device ID, or an encrypted device ID. For example, if the first AIoT service is a read command service, the data and / or signaling associated with it may include a read command or read response data. For example, if the first AIoT service is a write command service, the data and / or signaling associated with it may include a write command or write feedback. Optionally, the first AIoT service may also be other AIoT services, and this application does not limit this.

[0334] In this application, the source gNB refers to an AIoT-enabled network device, or a network device that supports AIoT. An AIoT-enabled network device may include the function of providing resource allocation, that is, an AIoT-enabled network device can allocate resources for the UE to support communication between the UE and AIoT devices.

[0335] It should be noted that the source gNB can parse and obtain the regional information carried in AIoT service request message #1.

[0336] S1002, the source gNB sends AIoT service request message #2 to the UE;

[0337] Correspondingly, the UE receives AIoT service request message #2 from the source gNB.

[0338] Among them, AIoT service request message #2 includes regional information.

[0339] For example, a UE can be referred to as a UEreader, an A-IoT-enable UE, or an intermediate node. A UE refers to a terminal device with reader functionality, or an AIoT-enabled terminal device, or a terminal device that supports AIoT.

[0340] Optionally, the AIoT service request message #2 may also include at least one of the following: a first identifier and / or a second identifier, wherein the first identifier is used to identify the AIoT device and the second identifier is used to identify the first AIoT service.

[0341] The following section, combining Method 1 and Method 2, explains how to ensure the continuity of the first AIoT service in a scenario where the UE switches to the target gNB. Method 1 primarily illustrates how the source gNB determines whether the UE should continue executing the first AIoT service, while Method 2 primarily illustrates how the target gNB determines whether the UE should continue executing the first AIoT service.

[0342] Method 1:

[0343] S1003, the source gNB determines whether the UE should continue to execute the first AIoT service.

[0344] For example, the source gNB determines, based on the area information and / or the first terminal type, whether the UE (after switching to the target gNB) can continue (or replace with executing, operating, etc.) the current first AIoT service, and / or whether it can continue to act as the reader of the first AIoT service. Here, the first terminal type corresponds to the UE, and the first terminal type includes whether the UE is a reader / writer or whether the UE does not support reader / writer functionality.

[0345] For example, if the UE is located within the cell covered by the target gNB, or in other words, the UE is located in the area of ​​the first AIoT service, then the UE can be considered to continue acting as a reader, and / or continue to execute the current first AIoT service, and / or report data and / or signaling related to the first AIoT service; conversely, if the UE is not located within the cell covered by the target gNB, or in other words, the UE is not located in the area of ​​the first AIoT service, or in other words, the UE is located outside the area of ​​the first AIoT service, then the UE can be considered not to continue acting as a reader, or not to continue executing the current first AIoT service, and / or not to report data and / or signaling related to the first AIoT service.

[0346] For example, if the first terminal type indicates that the UE is a reader / writer, then the UE can be considered to continue acting as a reader, and / or continue to execute the current first AIoT service, and / or report data and / or signaling related to the first AIoT service; conversely, if the first terminal type indicates that the UE does not support the reader / writer function, then the UE can be considered not to continue acting as a reader, or not to continue executing the current first AIoT service, and / or not to report data and / or signaling related to the first AIoT service.

[0347] Optionally, the area information can be from the UE or from a core network element (e.g., AMF / AIoTF), and the first terminal type can be from the UE or from a core network element (e.g., AMF / AIoTF), without limitation.

[0348] ●Scenario 1: The source gNB determines that the UE should continue to execute the first AIoT service. At this time, the UE undergoes handover, and the UE is a UE Reader.

[0349] S1004, the source gNB sends a handover request message #1 (e.g., Xn handover request message, such as HANDOVER REQUEST) to the target gNB;

[0350] Correspondingly, the target gNB receives the handover request message #1 from the source gNB.

[0351] For example, the switch request message #1 carries or indicates one or more of the following:

[0352] (1) UE type (i.e., first terminal type, such as UE type indication): UE reader, or in other words, UE type is reader / writer;

[0353] (2) Second identifier (service / session / task / transaction ID): Used to identify the current first AIoT service, which can be assigned by the core network element (e.g., AMF / AIoTF);

[0354] (3) The UE continues to perform the first AIoT service (AIoT service continue or not), or the UE continues to act as the reader / writer of the first AIoT service;

[0355] (4) There is an ongoing AIoT service, such as the first AIoT service;

[0356] (5) Report data and / or signaling related to the first AIoT business.

[0357] S1005, the target gNB sends a handover request confirmation message #1 (e.g., Xn handover request confirmation message, such as HANDOVER REQUEST ACKNOWLEDGE) to the source gNB;

[0358] Correspondingly, the source gNB receives the handover request confirmation message #1 from the target gNB.

[0359] For example, the handover request confirmation message #1 indicates that the UE is allowed to hand over to the target gNB. The handover request confirmation message #1 includes indication information #a, which indicates a first resource (e.g., an AIoT radio resource). The first resource is used for the UE to communicate with AIoT devices, or in other words, the first resource is used for the UE to perform a first AIoT service.

[0360] ●Scenario 2: The source gNB determines that the UE will not continue to execute the first AIoT service. In this case, the UE undergoes handover, and the UE is a regular UE (e.g., a legacy UE), that is, a UE that does not support reader / writer functions.

[0361] For example, the source gNB sends message #A to the target gNB, which requests a handover of the UE to the target gNB; the source gNB receives message #B from the target gNB, which includes indication information #A, indicating a fourth resource allocated by the target gNB for the UE to perform non-AIoT services; the source gNB then sends message #C to the UE, which instructs the UE to handover to the target gNB, and includes indication information #B, which indicates the fourth resource. The fourth resource is used for the UE to communicate with other devices and for the UE to perform non-AIoT services.

[0362] For example, message #C can be a handover command or an RRCReconfiguration, in which case RRCReconfiguration is used to instruct the UE to hand over to the target cell / target base station.

[0363] For example, message #B can be used to indicate at least one of the following:

[0364] (1) UE type: Ordinary UE (e.g., legacy UE), that is, UE that does not support reader / writer function;

[0365] (2) The UE does not continue to execute or perform the first AIoT service, or the UE does not continue to act as the reader / writer of the first AIoT service;

[0366] (3) The UE is not currently running any AIoT services;

[0367] (4) The UE does not report data and / or signaling related to the first AIoT service.

[0368] ●Scenario 3: The source gNB determines that the UE will not continue to execute the first AIoT service. In this case, the UE will not perform a cell handover.

[0369] For example, the source gNB may not perform the above steps S1004-S1005, that is, the source gNB does not request the target gNB to hand over the UE to the target gNB, or refuses to hand over the UE to the target gNB.

[0370] In this application, the target gNB refers to an AIoT-enabled network device, or a network device that supports AIoT. An AIoT-enabled network device may include the function of providing resource allocation, that is, an AIoT-enabled network device can allocate resources for the UE to support communication between the UE and AIoT devices.

[0371] Method 2:

[0372] S1006, The source gNB sends a handover request message #2 to the target gNB;

[0373] Correspondingly, the target gNB receives the handover request message #2 from the source gNB.

[0374] For example, the switch request message #2 carries one or more of the following:

[0375] (1) Service area: Used by the target gNB to determine whether it can continue to perform the current first AIoT service, and / or whether to determine whether the UE can continue to perform the first AIoT service.

[0376] (2) UE type indication: UEreader or legacy UE;

[0377] (3) Second identifier (service / session / task / transaction ID): used to identify the current first AIoT service;

[0378] (4) Whether to continue executing the first AIoT service (AIoT service continue or not), or whether to continue acting as the reader / writer for the first AIoT service;

[0379] (5) Are there any ongoing AIoT services?

[0380] (6) Whether to report data and / or signaling related to the first AIoT business.

[0381] S1007, the target gNB determines whether the UE should continue to execute the first AIoT service.

[0382] For example, the target gNB determines whether the UE can continue to perform the current first AIoT service and / or whether it can continue to act as the first AIoT service reader based on the service area and / or UE type (i.e., the first terminal type). For instance, if the UE is located within the cell covered by the target gNB, or in other words, the UE is located in the area covered by the first AIoT service, then the UE can be considered to continue acting as a reader and / or continue to perform the current first AIoT service and / or report data and / or signaling related to the first AIoT service. Conversely, if the UE is not located within the cell covered by the target gNB, or in other words, the UE is not located in the area covered by the first AIoT service, or in other words, the UE is located outside the area covered by the first AIoT service, then the UE can be considered not to continue acting as a reader, or not to continue performing the current first AIoT service, and / or not to report data and / or signaling related to the first AIoT service.

[0383] For example, if the first terminal type indicates that the UE is a reader / writer, then the UE can be considered to continue acting as a reader, and / or continue to execute the current first AIoT service, and / or report data and / or signaling related to the first AIoT service; conversely, if the first terminal type indicates that the UE does not support the reader / writer function, then the UE can be considered not to continue acting as a reader, or not to continue executing the current first AIoT service, and / or not to report data and / or signaling related to the first AIoT service.

[0384] ●Scenario 1: The target gNB determines that the UE should continue to execute the first AIoT service. At this time, the UE undergoes handover, and the UE becomes a UE Reader.

[0385] S1008, the target gNB sends a handover request confirmation message #2 to the source gNB;

[0386] Correspondingly, the source gNB receives the handover request confirmation message #2 from the target gNB.

[0387] The handover request confirmation message #2 includes indication information #1, which indicates a first resource. The first resource is used for the UE to communicate with the AIoT device, or in other words, the first resource is used for the UE to perform a first AIoT service.

[0388] Optionally, the switch request confirmation message #2 includes at least one of the following:

[0389] (1) UE type (i.e., first terminal type, such as UE type indication): UE reader, or in other words, UE type is reader / writer;

[0390] (2) Second identifier (service / session / task / transaction ID): used to identify the current first AIoT service;

[0391] (3) The UE continues to perform the first AIoT service (AIoT service continue or not), or the UE continues to act as the reader / writer of the first AIoT service;

[0392] (4) There is an ongoing AIoT service, such as the first AIoT service;

[0393] (5) Report data and / or signaling related to the first AIoT service;

[0394] (6) Service area information indicates the area where the first AIoT service is performed, or in other words, the UE Reader can perform or conduct the first AIoT service within the area indicated by the service area information.

[0395] ●Scenario 2: The target gNB determines that the UE will not continue to execute the first AIoT service. In this case, the UE undergoes handover, and the UE is a regular UE.

[0396] (e.g., legacy UE), which is a UE that does not support reader functionality.

[0397] For example, the target gNB sends a handover request confirmation message #3 to the source gNB. The handover request confirmation message #3 instructs the UE to hand over to the target gNB. The handover request confirmation message #3 includes indication information #2, which instructs a fourth resource. The fourth resource is used by the UE to communicate with other devices, or in other words, the fourth resource is used by the UE to perform non-AIoT services.

[0398] For example, the switch request confirmation message #3 can be used to indicate at least one of the following:

[0399] (1) UE type: Ordinary UE (e.g., legacy UE), that is, UE that does not support reader / writer function;

[0400] (2) The UE does not continue to execute or perform the first AIoT service, or the UE does not continue to act as the reader / writer of the first AIoT service;

[0401] (3) The UE is not currently running any AIoT services;

[0402] (4) The UE does not report data and / or signaling related to the first AIoT service.

[0403] ●Scenario 3: The target gNB determines that the UE will not continue to execute the first AIoT service. In this case, the UE will not switch over.

[0404] For example, the target gNB does not send a handover request confirmation message to the source gNB, that is, the target gNB refuses to hand over the UE to the target gNB.

[0405] Based on the above method one or method two, the source gNB or the target gNB can determine whether the UE continues to execute the first AIoT service, and then determine whether to configure the first resource or the fourth resource for the UE. The specific implementation is described in the relevant description of step S1009 below.

[0406] S1009, the source gNB sends configuration information to the UE;

[0407] Correspondingly, the UE receives configuration information from the source gNB.

[0408] For example, the configuration information can be replaced with the HandoverCommand message (or the RRCReconfiguration message).

[0409] In the first scenario described above, the configuration information instructs the UE to switch to the target gNB, or in other words, instructs the UE to switch to the target cell, which is a cell within the coverage area of ​​the target gNB. The configuration information includes instruction information #A, which indicates that the target gNB has configured a first resource (e.g., an AIoT radio resource config) for the UE. This first resource is used for the UE to communicate with AIoT devices, or in other words, for the UE to execute or perform a first AIoT service.

[0410] Alternatively, in scenario two above, the configuration information instructs the UE to switch to the target gNB, or in other words, instructs the UE to switch to the target cell, which is a cell within the coverage area of ​​the target gNB. The configuration information includes instruction information #B, which indicates that the target gNB is a fourth resource configured for the UE, and the UE performs or conducts non-AIoT services based on this fourth resource.

[0411] Alternatively, in case three above, if the source gNB or the target gNB determines that the UE will not continue to execute the first AIoT service and refuses the UE to switch to the target gNB, then the configuration information does not need to be sent to the UE. That is, the above step S1009 does not need to be executed, and the following step S1010 also does not need to be executed.

[0412] Optionally, in either Case 1 or Case 2 above, the configuration information may also include a second identifier, which is used to identify the first AIoT service.

[0413] As an example, in step S1009 above, the source gNB can send configuration information to the UE via a system information block (SIB) or RRC signaling. Further, the UE can execute the first AIoT service using resources (i.e., the first resource) used for transmitting data and / or signaling related to the first AIoT service. In this case, the resources related to the data and / or signaling of the first AIoT service can be referred to as AIoT radio resources.

[0414] In the first implementation, the first resource is configured by the target gNB for the UE. For example, the target gNB can send configuration information #a to the UE, which is used to configure resources for the UE to transmit data and / or signaling related to AIoT services.

[0415] For example, the first resource can be used for the UE to communicate with the AIoT device in cell #2, or for the UE to communicate with the AIoT device in a cell within a cell group (cell list), where cell #2 is included. Optionally, if the first resource is used for the UE to communicate with the AIoT device in a cell within a cell group, the configuration information #a may include the ID of the cell group. Alternatively, the first resource may be referred to as an exceptional resource pool for AIoT. If the target gNB configures an exceptional resource pool for AIoT for the UE, the UE uses the exceptional resource pool for AIoT to communicate with the AIoT device when leaving cell #2 to travel to other cells, or when the UE leaves the target gNB and before switching to / accessing other access network devices.

[0416] Optionally, before the UE switches to the target base station, that is, before receiving the command HO to switch to the target base station, the UE can also use the resources allocated to the UE by the original base station to perform the first AIoT service.

[0417] In another implementation, the first resource is configured by the core network for the UE. For example, the core network can configure a first resource in the UE's subscriber identity module (SIM) (or the UE's mobile equipment (ME) / universal integrated circuit card (UICC)) for transmitting data and / or signaling related to the first AIoT service, allowing the UE to communicate with AIoT devices when within the coverage area of ​​the target gNB. Alternatively, the core network can send configuration information #b to the target gNB via a non-access stratum (NAS) or protocol data unit (PDU) session. Configuration information #b is used to configure the first resource for the UE to transmit data and / or signaling related to the first AIoT service. Another example is that the core network can send configuration information #b to the source gNB, which then forwards it to the UE, thereby configuring the first resource for the UE to transmit data and / or signaling related to the first AIoT service through configuration information #b.

[0418] Optionally, the core network can also update AIoT resource configuration information #c via NAS. For example, the core network sends configuration information #c to the UE via NAS. Configuration information #c is used to configure AIoT resources for the UE, and configuration information #c is different from configuration information #b.

[0419] The first resource configured in the above configuration information #a, configuration information #b, or configuration information #c (collectively referred to as configuration information #A) will be explained below.

[0420] For example, configuration information #A may include one or more of frequency domain resource configuration information, time domain resource configuration information, or the maximum power that the UE can transmit to the AIoT device.

[0421] For example, frequency domain resource configuration methods include at least one of the following: stand-alone deployment, protection band deployment, or in-band deployment.

[0422] Optionally, the information of independently deployed frequency domain resources includes at least one of the following: frequency band or frequency band information, subcarrier spacing information, bandwidth information, frequency point information, and resource block (RB) configuration information. The information of in-band deployed frequency domain resources includes at least one of the following: For co-frequency deployment: co-frequency band or co-frequency band indication, frequency band or frequency band information, subcarrier spacing information, bandwidth information, frequency point information, and RB configuration information; or for inter-frequency deployment: frequency band or frequency band information, subcarrier spacing information, bandwidth information, frequency point information, and RB configuration information. Information on the frequency domain resources deployed in the guard band includes at least one of the following: LTE guard band deployment: LTE frequency band or band information, LTE frequency point information, subcarrier spacing information, bandwidth information, frequency point information, LTE guard band configuration information, RB configuration information; or NR guard band deployment: Co-band deployment: Co-band or co-band indication, NR frequency band or band information, NR frequency point information, subcarrier spacing information, bandwidth information, frequency point information, NR guard band configuration information, RB configuration information; Different frequency band deployment: NR frequency band or band information, NR frequency point information, subcarrier spacing information, bandwidth information, frequency point information, NR guard band configuration information, RB configuration information.

[0423] Optionally, the information of independently deployed frequency domain resources includes at least one of the following: frequency band list, multi-frequency band list (NR), multi-band information list (EUTRA) for evolved-UMTS terrestrial radio access (EUTRA), multi-band information list (multiBandInfoList), absolute frequency point A (absolute FrequencyPointA), absolute channel number value (ARFCN-ValueNR), specific carrier list (scs-specificCarrierList), location and bandwidth, subcarrier spacing, cyclic prefix, starting RB on the bandwidth portion (BWP), RB offset on the BWP, RB length on the BWP, index of the RB on the BWP, RB location on the BWP, maximum power of the first terminal transmitting downlink information, starting subcarrier on the RB, subcarrier offset on the RB, subcarrier length on the RB, index of the subcarrier on the RB, and location of the subcarrier on the RB.

[0424] Optionally, the information of the frequency domain resources deployed in-band includes at least one of the following: co-frequency deployment: co-band or co-band indication, frequencyBandList, MultiFrequencyBandListNR, MultiBandInfoListEUTRA, multiBandInfoList, absoluteFrequencyPointA, ARFCN-ValueNR, locationAndBandwidth, scs-SpecificCarrierList, subcarrierSpacing, cyclicPrefix, starting RB on the bandwidth portion BWP, RB offset on the BWP, RB length on the BWP, RB index on the BWP, RB location on the BWP, maximum power of the first device transmitting downlink information, starting subcarrier on the RB, subcarrier offset on the RB, subcarrier length on the RB, and so on. The subcarrier index, the subcarrier position on the RB; or inter-frequency deployment: frequencyBandList, MultiFrequencyBandListNR, MultiBandInfoListEUTRA, multiBandInfoList, absoluteFrequencyPointA, ARFCN-ValueNR, locationAndBandwidth, scs-SpecificCarrierList, subcarrierSpacing, cyclicPrefix, starting RB on the bandwidth portion BWP, RB offset on the BWP, RB length on the BWP, index of the RB on the BWP, RB position on the BWP, maximum power of the first terminal transmitting downlink information, starting subcarrier on the RB, subcarrier offset on the RB, subcarrier length on the RB, index of the subcarrier on the RB, and position of the subcarrier on the RB.

[0425] Optionally, the information on the frequency domain resources deployed in the guard band includes at least one of the following: LTE guard band deployment: Frequency Band Indicator EUTRA, Multi Band Info List EUTRA, EUTRA Frequency, Absolute Channel Number Value NR, locationAndBandwidth, scs-SpecificCarrierList, subcarrierSpacing, cyclicPrefix, starting RB of the guard band, RB offset of the guard band, RB length of the guard band, RB position of the guard band, RB index of the guard band, starting subcarrier on the RB, subcarrier offset on the RB, subcarrier length on the RB, subcarrier index on the RB, and subcarrier position on the RB.Or NR guard band deployment: Co-frequency deployment: Co-band or co-band indicator, FreqBandIndicatorNR, MultiFrequencyBandListNR, absoluteFrequencyPointA, ARFCN-ValueNR, locationAndBandwidth, scs-SpecificCarrierList, subcarrierSpacing, cyclicPrefix, Guardband configuration information, Guardband starting RB, Guardband RB offset, Guardband RB length, Guardband RB position, Guardband RB index, starting subcarrier on RB, subcarrier offset on RB, subcarrier length on RB, subcarrier index on RB, and subcarrier position on RB. Or, for multi-frequency deployment: Frequency Band Indicator NR (FreqBandIndicatorNR), MultiFrequencyBandList NR (MultiFrequencyBandListNR), absoluteFrequencyPointA, ARFCN-Value NR, scs-SpecificCarrierList, locationAndBandwidth, subcarrierSpacing, cyclicPrefix, Guardband configuration information, Guardband starting RB, Guardband RB offset, Guardband RB length, Guardband RB position, Guardband RB index, starting subcarrier on RB, subcarrier offset on RB, subcarrier length on RB, subcarrier index on RB, and subcarrier position on RB.

[0426] S1010, the UE completes random access with the target gNB.

[0427] This application does not limit the specific implementation of random access; please refer to existing relevant descriptions, which will not be elaborated here.

[0428] It should be noted that step S1010 is performed based on the configuration information in step S1009 indicating the first resource or the fourth resource. For example, the UE can continue to perform AIoT services based on the first resource, such as continuing to perform the first AIoT service; for example, the UE can perform non-AIoT services based on the fourth resource.

[0429] Optionally, if the configuration information in S1009 does not indicate the first resource or the fourth resource, or in other words, the target gNB refuses the UE's handover to the target gNB, then step S1010 is not executed, and the UE can suspend or terminate the first AIoT service.

[0430] Based on the above solution, the T2 RRC-based solution addresses the issue of AIoT service continuity, ensures the performance of AIoT services, and improves the user experience.

[0431] Figure 11 is a schematic diagram of a communication method 1100 provided in an embodiment of this application. As shown in Figure 11, method 1100 may include the following steps, and for details not covered herein, please refer to the relevant description in method 1200 of Figure 12 below.

[0432] S1110, the first access network device sends a third message to the second access network device;

[0433] Correspondingly, the first access network device receives the third message from the first access network device.

[0434] The third message is used to request the first terminal to be switched to the second access network device. The third message includes second indication information, which indicates the type of the first terminal. The type of the first terminal includes whether the first terminal is a reader or a terminal that does not support the function of a reader.

[0435] For example, the third message may also include at least one of the following: resource request information, area information, second identifier, whether to continue executing the first AIoT service, whether there is an ongoing AIoT service, and whether the first terminal reports data and / or signaling related to the first AIoT service; wherein, the resource request information is used to request the first resource, the first resource is used to execute the first AIoT service, the second identifier is used to identify the first AIoT service, and the area information indicates the area used to execute the first AIoT service.

[0436] For example, the resource request information includes at least one of the following:

[0437] (1) The number of resource blocks (RBs) or the duration of communication between the first terminal and the AIoT device;

[0438] (2) The first terminal requests or indicates whether it supports LTE or NR guard band, inband, or standalone bands;

[0439] (3) The frequency band number supported by the first terminal or the frequency band number requested by the first terminal.

[0440] Optionally, before performing step S1110, i.e. before sending the third message to the second access network device, the method further includes: the first access network device determining the first terminal type.

[0441] For example, the first access network device receives an eighth message from a first terminal or a core network element, the eighth message including resource request information, the resource request information being used to request a first resource, the first resource being used to execute a first AIoT service; or, receives a ninth message, the ninth message being used to request to perform the first AIoT service; or, the ninth message includes sixth indication information, the sixth indication information indicating the first AIoT service, or that there is an ongoing AIoT service; the type of the first terminal is determined based on the eighth message or the ninth message.

[0442] S1120, the second access network device sends a fourth message to the first access network device;

[0443] Correspondingly, the first access network device receives the fourth message from the second access network device.

[0444] The fourth message indicates that the first terminal is allowed or authorized to be switched to the second access network device.

[0445] Understandably, the first terminal type is used to determine whether switching the first terminal to the second access network device is permitted.

[0446] Optionally, the second message may also include at least one of the following: a first terminal type, a second identifier, and a first AIoT service being executed by the first terminal. The first terminal type includes a first terminal being a reader / writer, or a terminal that does not support reader / writer functionality, and the second identifier is used to identify the first AIoT service.

[0447] S1130, the second access network device sends the first message to the core network element;

[0448] Correspondingly, the core network element receives the first message from the second access network device.

[0449] The first message includes first information, which is used to request whether the first terminal should continue to perform the first environment Internet of Things (AIoT) service, and / or whether the first terminal should continue to act as a reader / writer for the first AIoT service.

[0450] S1140, the core network element determines whether the first terminal should continue to execute the first AIoT service.

[0451] In one implementation, the core network element determines whether the first terminal should continue to execute the first AIoT service based on regional information and / or the type of the first terminal.

[0452] For example, if the UE is located within the cell covered by the target gNB, or in other words, the UE is located in the area of ​​the first AIoT service, then the UE can be considered to continue acting as a reader, and / or continue to execute the current first AIoT service, and / or report data and / or signaling related to the first AIoT service; conversely, if the UE is not located within the cell covered by the target gNB, or in other words, the UE is not located in the area of ​​the first AIoT service, or in other words, the UE is located outside the area of ​​the first AIoT service, then the UE can be considered not to continue acting as a reader, or not to continue executing the current first AIoT service, and / or not to report data and / or signaling related to the first AIoT service.

[0453] For example, if the first terminal type indicates that the UE is a reader / writer, then the UE can be considered to continue acting as a reader, and / or continue to execute the current first AIoT service, and / or report data and / or signaling related to the first AIoT service; conversely, if the first terminal type indicates that the UE does not support the reader / writer function, then the UE can be considered not to continue acting as a reader, or not to continue executing the current first AIoT service, and / or not to report data and / or signaling related to the first AIoT service.

[0454] S1150, the core network element sends a second message to the second access network device;

[0455] Correspondingly, the second access network device receives the second message from the core network element.

[0456] The second message includes the first instruction information.

[0457] Example 1: The first instruction information indicates that the first terminal is authorized as a reader / writer for the first AIoT service, and / or the first terminal continues to perform the first AIoT service, and / or the first terminal continues to act as a reader / writer for the first AIoT service.

[0458] Example 2: The first instruction message indicates that the authorization for the first terminal to act as a reader / writer for the first AIoT service is denied, and / or the first terminal will not continue to execute the first AIoT service, and / or the first terminal will not continue to act as a reader / writer for the first AIoT service.

[0459] Understandably, the first instruction information is determined based on the first terminal type.

[0460] Optionally, before performing step S1150, i.e. before receiving the second message from the core network element, the method further includes: the second access network device sending a fifth message to the first terminal or the first access network device, the fifth message including third indication information, the third indication information indicating a second resource, the second resource being used by the first terminal to perform a first AIoT service.

[0461] Example 1: The method further includes: if the first indication information indicates that the first terminal is refused authorization as a reader / writer of the first AIoT service, and / or, the first terminal does not continue to perform the first AIoT service, and / or, the first terminal does not continue to act as a reader / writer of the first AIoT service, a sixth message is sent to the first terminal, the sixth message including the fourth indication information, the fourth indication information indicating to stop or no longer perform the first AIoT service, and / or, indicating to release the second resource.

[0462] Example 2: The method further includes: if the first indication information indicates that the first terminal is authorized as a reader / writer of the first AIoT service, and / or the first terminal continues to perform the first AIoT service, and / or the first terminal continues to act as a reader / writer of the first AIoT service, a seventh message is sent to the first terminal, the seventh message including the fifth indication information, the fifth indication information indicating the first resource.

[0463] Furthermore, the first terminal continues to execute the first AIoT service based on the first resource. Optionally, if the seventh message does not indicate the first resource, the first terminal stops executing or does not execute the first AIoT service.

[0464] Optionally, the first terminal receives indication information from the second access network device, which indicates a timer and / or a valid area. That is, the first terminal can execute or perform a first AIoT service within a period of time indicated by the timer and / or within the valid area.

[0465] Figure 12 is a schematic diagram of a communication method 1200 provided in an embodiment of this application. As shown in Figure 12, taking the first terminal as UE, the core network element as AMF / AIoTF, the first access network device as the source gNB, and the second access network device as the target gNB as an example, this method is applicable to the NAS / UP-based solution architecture in the HO scenario, and method 1200 may include the following steps.

[0466] S1201, AMF / AIoTF sends NAS message / PDU session #1 to the source gNB;

[0467] Correspondingly, the source gNB receives NAS messages / PDU sessions #1 from the AMF / AIoTF.

[0468] Among them, NAS message / PDU session #1 includes AIoT service request message, which is used to request the execution of the first AIoT service (such as inventory service).

[0469] Optionally, NAS message / PDU session #1 may also include at least one of the following: a first identifier and / or a second identifier, wherein the first identifier is used to identify the AIoT device and the second identifier is used to identify the first AIoT service.

[0470] S1202, the source gNB sends a NAS message / PDU session #2 to the UE;

[0471] Correspondingly, the UE receives NAS message / PDU session #2 from the source gNB.

[0472] Among them, NAS message / PDU session #2 includes AIoT service request messages.

[0473] It should be noted that in step S1201 above, the AMF / AIoTF sends a NAS message / PDU session to the UE through the source gNB. This NAS message / PDU session #1 is transparent to the N source gNB, that is, the source gNB cannot parse and obtain the information carried in the NAS message / PDU session, but the UE can parse and obtain the information carried in the NAS message / PDU session.

[0474] Optionally, NAS message / PDU session #2 may also include at least one of the following: a first identifier and / or a second identifier, wherein the first identifier is used to identify the AIoT device and the second identifier is used to identify the first AIoT service.

[0475] S1203, the UE sends an AIoT resource request message to the source gNB;

[0476] Correspondingly, the source gNB receives the AIoT resource request message from the UE.

[0477] Among them, the AIoT resource request message is used to request the first resource, which is used by the UE to perform the first AIoT service or by the UE to communicate with the AIoT device.

[0478] Optionally, the UE sends a second identifier (service / session / task / transaction ID) to the source gNB to identify the first AIoT service.

[0479] S1204, the source gNB sends a handover request message (e.g., Xn handover request message, HANDOVER REQUEST message) to the target gNB;

[0480] Correspondingly, the target gNB receives a handover request message from the source gNB.

[0481] For example, a switch request message may carry at least one of the following:

[0482] (1) AIoT radio resource request message;

[0483] (2) Whether to continue to perform the first AIoT service, or to continue to act as the reader / writer of the first AIoT service;

[0484] (3) Second identifier;

[0485] (4) Are there any AIoT services currently in operation?

[0486] (5) Whether data and / or signaling related to the first AIoT business are reported;

[0487] (6) UE type.

[0488] S1205, the target gNB sends a handover request confirmation message (e.g., Xn handover request confirmation message) to the source gNB;

[0489] Correspondingly, the source gNB receives a handover request confirmation message from the target gNB.

[0490] For example, the handover request confirmation message indicates that the UE is allowed or authorized to hand over to the target gNB.

[0491] S1206, the source gNB sends configuration information #1 (e.g., RRCReconfiguration) to the UE;

[0492] Correspondingly, the UE receives configuration information #1 from the source gNB.

[0493] Configuration information #1 indicates that the UE switches to the target gNB.

[0494] S1207, the UE and the target gNB complete random access.

[0495] Optionally, the UE may send an RRCReconfigurationComplete message to the target gNB to indicate that random access has been completed.

[0496] S1208, the target gNB sends a path switching request message (e.g., PATH SWITCH REQUEST message) to the AMF / AIoTF;

[0497] Correspondingly, the AMF / AIoTF receives a path switching request message from the target gNB.

[0498] For example, a path switching request message includes at least one of the following:

[0499] (1) Second identifier;

[0500] (2) Whether to continue performing the first AIoT service, or whether to continue acting as the reader / writer for the first AIoT service;

[0501] (3) Are there any AIoT services currently in operation?

[0502] (4) Whether data and / or signaling related to the first AIoT business are reported;

[0503] (5) UE type.

[0504] S1209, AMF / AIoTF determines whether the UE should continue to execute the first AIoT service.

[0505] For example, the AMF / AIoTF determines whether the UE can continue to perform the current first AIoT service and / or whether it can continue to act as a reader based on the service area information and / or the first terminal type (UE type). For specific implementation methods, please refer to the implementation method of the target gNB determining whether the UE continues to perform the first AIoT service in step S1007 above.

[0506] ●Scenario 1: The AMF / AIoTF determines that the UE should continue executing the first AIoT service. At this time, the UE undergoes a handover, and the UE becomes the UE Reader.

[0507] S1210, AMF / AIoTF sends a path switch request confirmation message (e.g., PATH SWITCH REQUEST ACKNOWLEDGE) to the target gNB;

[0508] Correspondingly, the target gNB receives a path switching request confirmation message from the AMF / AIoTF.

[0509] For example, a path switching request confirmation message may include at least one of the following:

[0510] (1) UE type: UEreader;

[0511] (2) Second identifier: used to identify the current first AIoT service;

[0512] (3) The UE continues to perform the first AIoT service, or the UE continues to act as the reader / writer of the first AIoT service, or the UE is authorized to act as the reader / writer;

[0513] (4) Report data and / or signaling related to the first AIoT business.

[0514] ●Scenario 2: The AMF / AIoTF determines that the UE will not continue to execute the first AIoT service. In this case, the UE undergoes handover, and the UE is a regular UE (e.g., a legacy UE).

[0515] For example, the AMF / AIoTF sends a handover request confirmation message #1 to the target gNB, wherein the handover request confirmation message #1 includes at least one of the following:

[0516] (1) UE type: Legency UE;

[0517] (2) The UE does not continue to execute the first AIoT service, or the UE does not continue to act as the reader / writer of the first AIoT service, or the UE is refused authorization to act as the reader / writer;

[0518] (3) The UE does not report data and / or signaling related to the first AIoT service.

[0519] ●Scenario 3: The AMF / AIoTF determines that the UE will not continue to execute the first AIoT service. In this case, the UE will not switch over.

[0520] For example, the AMF / AIoTF may not send a handover request confirmation message to the target gNB, that is, the above step S1210 may not be performed.

[0521] S1211, The target gNB sends configuration information #2 to the UE;

[0522] Correspondingly, the UE receives configuration information #2 from the target gNB.

[0523] In the case of the above situation, configuration information #2 includes indication information #A, which indicates that the target gNB is a first resource configured for the UE (e.g., AIoT radio resource config). The first resource is used for the UE to communicate with AIoT devices, or in other words, the first resource is used for the UE to perform a first AIoT service.

[0524] Alternatively, for scenario two above, configuration information #2 includes indication information #B, which indicates that the target gNB is the fourth resource configured by the UE, that is, the UE switches to the target gNB. At this time, the UE is a normal UE and performs non-AIoT services according to the fourth resource.

[0525] Alternatively, in case three above, if it is determined that the UE will not continue to execute the first AIoT service and refuses the UE to switch to the target gNB, then configuration information #2 can be omitted from the UE, that is, step S1211 above can be omitted.

[0526] Based on the above solutions, the T2 NAS-based or UP-based solutions address the issue of AIoT service continuity, ensure the performance of AIoT services, and improve the user experience.

[0527] Figure 13 is a schematic diagram of a communication method 1300 provided in an embodiment of this application. As shown in Figure 13, method 1300 may include the following steps, and for parts not covered in detail, please refer to the relevant description of method 1500 in Figure 15 below.

[0528] S1310, the first terminal sends a first message to the first access network device;

[0529] Correspondingly, the first access network device receives the first message from the first terminal.

[0530] The first message includes resource request information and region information. The resource request information is used by the first terminal to execute the first AIoT service, and the region information indicates the region used to execute the first AIoT service.

[0531] For example, the resource request information includes at least one of the following:

[0532] (1) The number of resource blocks (RBs) or the duration of communication between the first terminal and the AIoT device;

[0533] (2) The first terminal requests or indicates whether it supports LTE or NR guard band, inband, or standalone bands;

[0534] (3) The frequency band number supported by the first terminal or the frequency band number requested by the first terminal.

[0535] For example, the first message includes a second identifier.

[0536] Optionally, before receiving the first message from the first terminal, the method further includes: the first access network device receiving a ninth message from a core network element, the ninth message being used to request the execution of a first AIoT service, the ninth message including a first identifier, the first identifier being used to identify an AIoT device, and the first terminal supporting communication with the AIoT device; the first access network device sending a tenth message to the first terminal, the tenth message being used to request the execution of the first AIoT service, the tenth message including the first identifier.

[0537] S1320, the first access network device determines whether the first terminal should continue to execute the first AIoT service based on the area information and / or the type of the first terminal. For specific implementation details, please refer to the relevant description of method 900 above.

[0538] S1330, if it is determined that the first terminal continues to execute the first AIoT service, the first access network device sends a second message to the second access network device, and correspondingly, the second access network device receives the second message from the first access network device. The second message requests that the first terminal be switched to the second access network device, and includes resource request information.

[0539] For example, the second message may also include at least one of the following: a first terminal type, a second identifier, the first terminal continuing to execute the first AIoT service, the first terminal having an ongoing AIoT service, and the first terminal reporting data and / or signaling related to the first AIoT service; wherein, the first terminal type includes the first terminal being a reader / writer or a terminal that does not support reader / writer functionality, and the second identifier is used to identify the first AIoT service.

[0540] S1340, the second access network device sends a third message to the first access network device;

[0541] Correspondingly, the first access network device receives a third message from the second access network device.

[0542] The third message includes a first resource allocated by the second access network device to the first terminal, which is used to execute the first AIoT service.

[0543] S1350, the first access network device sends a fourth message to the first terminal;

[0544] Correspondingly, the first terminal receives the fourth message from the first access network device.

[0545] The fourth message instructs the first terminal to switch to the second access network device. This fourth message includes indication information indicating the first resource.

[0546] Optionally, the method further includes: if it is determined that the first terminal will not continue to execute the first AIoT service, sending a fifth message to the second access network device, the fifth message requesting the first terminal to switch to the second access network device, the fifth message including a sixth message requesting a fourth resource, the fourth resource being used by the first terminal to execute non-AIoT services; receiving a seventh message from the second access network device, the seventh message including the fourth resource allocated by the second access network device to the first terminal; and sending an eighth message to the first terminal, the eighth message instructing the first terminal to switch to the second access network device. The eighth message includes indication information indicating the fourth resource, the fourth resource being used by the first terminal to execute non-AIoT services.

[0547] Optionally, the method further includes: if it is determined that the first terminal will not continue to perform the first AIoT service, refusing to switch the first terminal to the second access network device.

[0548] Furthermore, the first terminal continues to execute the first AIoT service based on the first resource. Optionally, if the fourth message does not indicate the first resource, the first terminal stops executing or does not execute the first AIoT service.

[0549] Optionally, the first terminal receives indication information from the second access network device, which indicates a timer and / or a valid area. That is, the first terminal can execute or perform a first AIoT service within a period of time indicated by the timer and / or within the valid area.

[0550] Figure 14 is a schematic diagram of a communication method 1400 provided in an embodiment of this application. As shown in Figure 14, method 1400 may include the following steps; for details not covered herein, please refer to the relevant description of method 1500 in Figure 15 below.

[0551] S1410, the first terminal sends a first message to the first access network device;

[0552] Correspondingly, the first access network device receives the first message from the first terminal.

[0553] The first message includes resource request information and region information. The resource request information is used by the first terminal to execute the first AIoT service, and the region information indicates the region used to execute the first AIoT service.

[0554] For example, the resource request information includes at least one of the following:

[0555] (1) The number of resource blocks (RBs) or the duration of communication between the first terminal and the AIoT device;

[0556] (2) The first terminal requests or indicates whether it supports LTE or NR guard band, inband, or standalone bands;

[0557] (3) The frequency band number supported by the first terminal or the frequency band number requested by the first terminal.

[0558] For example, the first message includes a second identifier.

[0559] Optionally, before receiving the first message from the first terminal, the method further includes: the first access network device receiving a fifth message from a core network element, the fifth message being used to request the execution of a first AIoT service, the fifth message including a first identifier, the first identifier being used to identify an AIoT device, and the first terminal supporting communication with the AIoT device; the first access network device sending a sixth message to the first terminal, the sixth message being used to request the execution of the first AIoT service, the sixth message including the first identifier.

[0560] S1420, the first access network device sends a second message to the second access network device;

[0561] Correspondingly, the second access network device receives a second message from the first access network device.

[0562] The second message is used to request the first terminal to be switched to the second access network device, and the second message includes resource request information.

[0563] For example, the second message may also include at least one of the following: a first terminal type, a second identifier, whether to continue executing the first AIoT service, whether there is an ongoing AIoT service, and whether to report data and / or signaling related to the first AIoT service; wherein, the first terminal type includes the first terminal being a reader or a terminal that does not support reader functionality, and the second identifier is used to identify the first AIoT service.

[0564] S1430, the second access network device determines whether the first terminal should continue to execute the first AIoT service based on the area information and the type of the first terminal. For specific implementation details, please refer to the relevant description of method 800 above.

[0565] S1440, the second access network device sends a third message to the first access network device;

[0566] Correspondingly, the first access network device receives a third message from the second access network device.

[0567] The third message includes a first resource allocated by the second access network device to the first terminal, which is used to execute the first AIoT service.

[0568] S1450, the first access network device sends a fourth message to the first terminal;

[0569] Correspondingly, the first terminal receives the fourth message from the first access network device.

[0570] The fourth message instructs the first terminal to switch to the second access network device. This fourth message includes indication information indicating the first resource.

[0571] Furthermore, the first terminal continues to execute the first AIoT service based on the first resource. Optionally, if the fourth message does not indicate the first resource, the first terminal stops executing or does not execute the first AIoT service.

[0572] Optionally, the first terminal receives indication information from the second access network device, which indicates a timer and / or a valid area. That is, the first terminal can execute or perform a first AIoT service within a period of time indicated by the timer and / or within the valid area.

[0573] Figure 15 is a schematic diagram of a communication method 1500 provided in an embodiment of this application. As shown in Figure 15, taking the first terminal as UE, the core network element as AMF / AIoTF, the first access network device as the source gNB, and the second access network device as the target gNB as an example, this method is applicable to the NAS / UP-based solution architecture in the HO scenario, and method 1500 may include the following steps.

[0574] S1501, AMF / AIoTF sends NAS message / PDU session #1 to the source gNB;

[0575] Correspondingly, the source gNB receives NAS messages / PDU sessions #1 from the AMF / AIoTF.

[0576] The NAS message / PDU session #1 includes an AIoT service request message and area information. The AIoT service request message is used to request the execution of a first AIoT service (such as inventory management), and the area information indicates the area where the first AIoT service is to be executed.

[0577] Optionally, NAS message / PDU session #1 may also include at least one of the following: a first identifier and / or a second identifier, wherein the first identifier is used to identify the AIoT device and the second identifier is used to identify the first AIoT service.

[0578] S1502, the source gNB sends a NAS message / PDU session #2 to the UE;

[0579] Correspondingly, the UE receives NAS message / PDU session #2 from the source gNB.

[0580] Among them, NAS message / PDU session #2 includes AIoT service request messages and regional information.

[0581] Optionally, NAS message / PDU session #2 may also include at least one of the following: a first identifier and / or a second identifier, wherein the first identifier is used to identify the AIoT device and the second identifier is used to identify the first AIoT service.

[0582] It should be noted that in step S1501 above, the AMF / AIoTF sends a NAS message / PDU session to the UE through the source gNB. This NAS message / PDU session #1 is transparent to the N source gNB, that is, the source gNB cannot parse and obtain the information carried in the NAS message / PDU session, but the UE can parse and obtain the information carried in the NAS message / PDU session.

[0583] S1503, the UE sends an AIoT resource request message and area information to the source gNB;

[0584] Correspondingly, the source gNB receives AIoT resource request messages and service area information from the UE.

[0585] The AIoT resource request message is used to request a first resource, which is used by the UE to perform a first AIoT service or for the UE to communicate with an AIoT device. The area information indicates the area where the first AIoT service is performed.

[0586] Optionally, the UE may also send a second identifier and / or UE type (i.e., a first terminal type) to the source gNB, the second identifier being used to identify the first AIoT service.

[0587] The following section, combining Method 1 and Method 2, explains how to ensure the continuity of the first AIoT service in a scenario where the UE switches to the target gNB. Method 1 primarily illustrates how the source gNB determines whether the UE should continue executing the first AIoT service, while Method 2 primarily illustrates how the target gNB determines whether the UE should continue executing the first AIoT service.

[0588] Method 1:

[0589] S1504, the source gNB determines whether the UE should continue to execute the first AIoT service.

[0590] For example, the source gNB determines, based on the service area and UE type, whether the UE (after switching to the target gNB) can continue to perform the current first AIoT service, and / or whether it can continue to act as the reader of the first AIoT service.

[0591] ●Scenario 1: The source gNB determines that the UE should continue to execute the first AIoT service. At this time, the UE undergoes handover, and the UE is a UE Reader.

[0592] S1505, the source gNB sends a handover request message #1 (e.g., Xn handover request message, such as HANDOVER REQUEST) to the target gNB;

[0593] Correspondingly, the target gNB receives the handover request message #1 from the source gNB.

[0594] For example, the switch request message #1 carries one or more of the following:

[0595] (1) AIoT resource request message;

[0596] (2) UE type (UE type indication): UEreader, or in other words, UE type is reader / writer;

[0597] (3) Second identifier (service / session / task / transaction ID): Used to identify the current first AIoT service, which can be assigned by the core network element (e.g., AMF / AIoTF);

[0598] (4) The UE continues to perform the first AIoT service (AIoT service continue or not), or the UE continues to be a reader / writer;

[0599] (5) There is an ongoing AIoT service, such as the first AIoT service;

[0600] (6) Report data and / or signaling related to the first AIoT service;

[0601] (7) Service area information indicates the area where the first AIoT service is performed, or in other words, the UE Reader can perform or conduct the first AIoT service within the area indicated by the service area information.

[0602] S1506, the target gNB sends a handover request confirmation message (e.g., Xn handover request confirmation message, such as HANDOVER REQUEST ACKNOWLEDGE) to the source gNB;

[0603] Correspondingly, the source gNB receives a handover request confirmation message from the target gNB.

[0604] For example, the handover request confirmation message #1 indicates that the UE is allowed to hand over to the target gNB. The handover request confirmation message #1 includes indication information #a, which indicates a first resource (e.g., an AIoT radio resource). The first resource is used for the UE to communicate with AIoT devices, or in other words, the first resource is used for the UE to perform a first AIoT service.

[0605] ●Scenario 2: The source gNB determines that the UE will not continue to execute the first AIoT service. In this case, the UE undergoes handover, and the UE is a regular UE (e.g., a legacy UE), that is, a UE that does not support reader / writer functions.

[0606] For example, the source gNB sends message #1 to the target gNB, which requests the UE to switch to the target gNB; the source gNB receives message #2 from the target gNB, which includes indication information #A, indicating the fourth resource allocated by the target gNB to the UE, the fourth resource being used by the UE to perform non-AIoT services; the source gNB sends message #3 to the UE, which instructs the UE to switch to the target gNB, and message #3 includes indication information #B, which indicates the fourth resource. The parameters carried in message #3 and their interpretations can be found in the description of message #B in step S1005 of method 1000 above.

[0607] ●Scenario 3: The source gNB determines that the UE will not continue to execute the first AIoT service. In this case, the UE will not switch over.

[0608] For example, the source gNB does not perform the above steps S1505-S1506, that is, the source gNB does not request the target gNB to hand over the UE to the target gNB, or refuses to hand over the UE to the target gNB.

[0609] Method 2:

[0610] S1507, the source gNB sends a handover request message #2 to the target gNB;

[0611] Correspondingly, the target gNB receives the handover request message #2 from the source gNB.

[0612] For example, the switch request message #2 carries one or more of the following:

[0613] (1) AIoT resource request message;

[0614] (2) Area information: used to determine whether the current first AIoT service can continue, and / or whether the reader can continue to function;

[0615] (3) UE type: UEreader or legacy UE;

[0616] (4) Second identifier: used to identify the current first AIoT service;

[0617] (5) Whether to continue performing the first AIoT service, or whether to continue acting as the reader / writer for the first AIoT service;

[0618] (6) Are there any AIoT services currently in operation?

[0619] (7) Whether to report data and / or signaling related to the first AIoT business.

[0620] S1508, the target gNB determines whether the UE should continue to execute the first AIoT service.

[0621] For example, the target gNB determines whether the UE can continue to perform the current first AIoT service and / or whether it can continue to act as a reader based on the service area and / or UE type (i.e., the first terminal type). For instance, if the UE is located within the cell covered by the target gNB, or in other words, the UE is located in the area covered by the first AIoT service, then the UE can be considered to continue acting as a reader and / or continue to perform the current first AIoT service and / or report data and / or signaling related to the first AIoT service. Conversely, if the UE is not located within the cell covered by the target gNB, or in other words, the UE is not located in the area covered by the first AIoT service, or in other words, the UE is located outside the area covered by the first AIoT service, then the UE can be considered not to continue acting as a reader, or not to continue performing the current first AIoT service, and / or not to report data and / or signaling related to the first AIoT service.

[0622] For example, if the first terminal type indicates that the UE is a reader / writer, then the UE can be considered to continue acting as a reader, and / or continue to execute the current first AIoT service, and / or report data and / or signaling related to the first AIoT service; conversely, if the first terminal type indicates that the UE does not support the reader / writer function, then the UE can be considered not to continue acting as a reader, or not to continue executing the current first AIoT service, and / or not to report data and / or signaling related to the first AIoT service.

[0623] ●Scenario 1: The target gNB determines that the UE should continue to execute the first AIoT service. At this time, the UE undergoes a handover, and the UE is a UE Reader.

[0624] S1509, The target gNB sends a handover request confirmation message #2 to the source gNB;

[0625] Correspondingly, the source gNB receives the handover request confirmation message #2 from the target gNB.

[0626] The handover request confirmation message #2 includes indication information #1, which indicates the first resource. The parameters carried in the handover request confirmation message #2 and their interpretations can be found in the relevant description of the handover request confirmation message #2 in step S1008 of method 1000 described above.

[0627] ●Scenario 2: The target gNB determines that the UE will not continue to execute the first AIoT service. In this case, the UE undergoes handover, and the UE is a regular UE.

[0628] (e.g., legacy UE), which is a UE that does not support reader functionality.

[0629] For example, the target gNB sends a handover request confirmation message #3 to the source gNB. The handover request confirmation message #3 instructs the UE to handover to the target gNB. The handover request confirmation message #3 includes indication information #2, which indicates a fourth resource. The parameters carried in the handover request confirmation message #3 and their interpretations can be found in the relevant description of the handover request confirmation message #3 in step S1008 of the method 1000 described above.

[0630] ●Scenario 3: The target gNB determines that the UE will not continue to execute the first AIoT service. In this case, the UE will not switch over.

[0631] For example, the target gNB does not send a handover request confirmation message to the source gNB, that is, the target gNB refuses to hand over the UE to the target gNB.

[0632] Based on the above method one or method two, the source gNB or the target gNB can determine whether the UE continues to execute the first AIoT service, and then determine whether to configure the first resource or the fourth resource for the UE. The specific implementation is described in the relevant description of step S1510 below.

[0633] S1510, the source gNB sends configuration information #1 to the UE; correspondingly, the UE receives configuration information #1 from the source gNB.

[0634] For example, configuration information #1 can be replaced with the HandoverCommand message (or the RRC Reconfiguration message).

[0635] In the case of scenario one above, configuration information #1 instructs the UE to switch to the target gNB. Configuration information #1 includes indication information #1, which indicates that the target gNB is a first resource configured for the UE. The first resource is used for the UE to communicate with AIoT devices.

[0636] Alternatively, for scenario two above, configuration information #1 instructs the UE to switch to the target gNB. In this case, the UE is a normal UE. Configuration information #1 includes instruction information #2, which indicates that the target gNB is the fourth resource configured by the UE. The UE can perform non-AIoT services according to the fourth resource.

[0637] Alternatively, in case three above, if the source gNB or the target gNB determines that the UE will not continue to execute the first AIoT service and refuses the UE to switch to the target gNB, then configuration information #1 can be omitted from the UE. That is, step S1509 above can be omitted, and step S1510 below also does not need to be executed.

[0638] S1511, the UE completes random access with the target gNB.

[0639] S1512, the target gNB sends a path switching request message (e.g., PATH SWITCH REQUEST ACKNOWLEDGE) to the AMF / AIoTF;

[0640] Correspondingly, the AMF / AIoTF receives a path switching request message from the target gNB.

[0641] S1513, AMF / AIoTF sends a path switch request confirmation message (e.g., PATH SWITCH REQUEST ACKNOWLEDGE message) to the target gNB;

[0642] Correspondingly, the target gNB receives a path switching request confirmation message from the AMF / AIoTF.

[0643] The specific implementation methods of the above steps S1511-S1513 can be found in existing relevant descriptions, and will not be explained here.

[0644] Based on the above solutions, the T2 NAS-based or UP-based solutions address the issue of AIoT service continuity, ensure the performance of AIoT services, and improve the user experience.

[0645] It should be noted that Figures 8 to 15 above illustrate the implementation methods for ensuring AIoT service continuity in the HO scenario. The following section, in conjunction with Figures 16 to 21, illustrates the implementation methods for ensuring AIoT service continuity in the RLF scenario, i.e., when the UE undergoes cell handover.

[0646] Figure 16 is a schematic diagram of a communication method 1600 provided in an embodiment of this application. As shown in Figure 16, method 1600 may include the following steps; for details not covered herein, please refer to the relevant description of method 1800 in Figure 18 below.

[0647] S1610, the first access network device obtains area information and / or the first terminal type.

[0648] The area information indicates the area where the first AIoT service is performed.

[0649] Optionally, the first access network device may receive area information and / or the type of the first terminal from the first terminal or a core network element.

[0650] In one implementation, the first access network device receives a third message from a core network element. The third message is used to request the execution of a first AIoT service and includes regional information.

[0651] S1620, the second access network device sends a first message to the first access network device;

[0652] Correspondingly, the first access network device receives the first message from the second access network device.

[0653] The first message is used to request confirmation as to whether the first terminal should continue to execute the first AIoT service, and the second access network device is the network device that the first terminal accesses after the wireless link between the first terminal and the first access network device fails.

[0654] For example, the first message includes at least one of the following: a second identifier, a first terminal type, whether the first terminal continues to be a reader / writer, whether the first terminal continues to perform the first AIoT service, or whether the first terminal reports data and / or signaling related to the first AIoT service; the second message includes at least one of the following: a second identifier, a first terminal type, whether the first terminal continues to be a reader / writer, whether the first terminal continues to perform the first AIoT service, or whether the first terminal reports data and / or signaling related to the first AIoT service; wherein, the first terminal type includes the first terminal being a reader / writer, or a terminal that does not support reader / writer functionality, and the second identifier is used to identify the first AIoT service.

[0655] S1630, the first access network device determines whether the first terminal should continue to execute the first AIoT service based on the area information and / or the type of the first terminal. For specific implementation details, please refer to the relevant description of method 800 above.

[0656] S1640, the first access network device sends a second message to the second access network device;

[0657] Correspondingly, the second access network device receives a second message from the first access network device.

[0658] The second message indicates whether the first terminal should continue to execute the first AIoT service.

[0659] S1650, the second access network device sends the fifth message to the first terminal;

[0660] Correspondingly, the first terminal receives the fifth message from the second access network device.

[0661] The fifth message includes at least one of the following: a second identifier, a first terminal type, whether to continue as a reader / writer, whether to continue executing the first AIoT service, and whether to report data and / or signaling related to the first AIoT service; wherein, the first terminal type includes the first terminal being a reader / writer or a terminal that does not support reader / writer functionality, and the second identifier is used to identify the first AIoT service.

[0662] Optionally, before the second access network device sends the fifth message to the first terminal, the method further includes: the second access network device receiving a sixth message from a core network element, the sixth message indicating that the first terminal is authorized as a reader / writer.

[0663] Furthermore, the first terminal continues to execute the first AIoT service based on the first resource. Optionally, if the fifth message does not indicate the first resource, the first terminal stops executing or does not execute the first AIoT service.

[0664] Optionally, the first terminal receives indication information from the second access network device, which indicates a timer and / or a valid area. That is, the first terminal can execute or perform a first AIoT service within a period of time indicated by the timer and / or within the valid area.

[0665] Figure 17 is a schematic diagram of a communication method 1700 provided in an embodiment of this application. As shown in Figure 17, method 1700 may include the following steps; for details not covered herein, please refer to the relevant description of method 1800 in Figure 18 below.

[0666] S1710, the first access network device obtains area information and / or the first terminal type.

[0667] The area information indicates the area where the first AIoT service is performed.

[0668] Optionally, the first access network device may receive area information and / or the type of the first terminal from the first terminal or a core network element.

[0669] In one implementation, the first access network device receives area information from a core network element or a first terminal.

[0670] S1720, the first access network device sends a second message to the second access network device;

[0671] Correspondingly, the second access network device receives a second message from the first access network device.

[0672] The second message includes regional information and is used to request confirmation of whether the first terminal should continue to perform the first AIoT service. The second access network device is the network device that the first terminal accesses after the wireless link between the first terminal and the first access network device fails.

[0673] For example, the second message includes at least one of the following: the second message further includes at least one of the following: a second identifier, a first terminal type, whether the first terminal continues to be a reader / writer, whether the first AIoT service continues to be executed, whether there is an ongoing AIoT service, and whether data and / or signaling related to the first AIoT service are reported; wherein, the first terminal type includes the first terminal being a reader / writer, or a terminal that does not support reader / writer functionality, and the second identifier is used to identify the first AIoT service.

[0674] Optionally, before the second access network device receives the second message from the first access network device, the method further includes: the first access network device receiving the first message from the second access network device.

[0675] Optionally, before receiving the first message from the second access network device, the method further includes: the first access network device receiving a third message from a core network element, the third message being used to request the execution of a first AIoT service, the third message including area information; the first access network device sending a fourth message to the first terminal, the fourth message being used to request the execution of the first AIoT service, the fourth message including area information.

[0676] S1730, the second access network device determines whether the first terminal should continue to execute the first AIoT service based on the area information and / or the type of the first terminal. For specific implementation details, please refer to the relevant description of method 900 above.

[0677] S1740, the second access network device sends the fifth message to the first terminal;

[0678] Correspondingly, the first terminal receives the fifth message from the second access network device.

[0679] The fifth message includes at least one of the following: a second identifier, a first terminal type, whether the first terminal continues to be a reader / writer, whether the first terminal continues to execute the first AIoT service, and whether the first terminal reports data and / or signaling related to the first AIoT service; wherein the first terminal type includes the first terminal being a reader / writer or a terminal that does not support reader / writer functionality, and the second identifier is used to identify the first AIoT service.

[0680] Furthermore, the first terminal continues to execute the first AIoT service based on the first resource. Optionally, if the fifth message does not indicate the first resource, the first terminal stops executing or does not execute the first AIoT service.

[0681] Optionally, the first terminal receives indication information from the second access network device, which indicates a timer and / or a valid area. That is, the first terminal can execute or perform a first AIoT service within a period of time indicated by the timer and / or within the valid area.

[0682] Figure 18 is a schematic diagram of a communication method 1800 provided in an embodiment of this application. As shown in Figure 18, taking the first terminal as UE, the core network element as AMF / AIoTF, the first access network device as source gNB (or lastserving gNB), and the second access network device as target gNB (or new gNB) as an example, this method is applicable to the RRC-based solution architecture in the RLF scenario, and the method 1800 may include the following steps.

[0683] S1801, AMF / AIoTF sends a service request message #1 (e.g., Service Request) to the source gNB;

[0684] Correspondingly, the source gNB receives service request message #1 from AMF / AIoTF.

[0685] Among them, the AMF / AIoTF service request message #1 includes regional information, which indicates the region used to perform the first AIoT service.

[0686] Optionally, the AMF / AIoTF service request message #1 also includes a first identifier (device identification) used to identify the AIoT device.

[0687] S1802, the source gNB sends a service request message #2 to the UE;

[0688] Correspondingly, the UE receives service request message #2 from the source gNB.

[0689] Among them, the AMF / AIoTF service request message #2 includes regional information, which indicates the region used to perform the first AIoT service.

[0690] Optionally, the AMF / AIoTF service request message #2 also includes a first identifier (device identification) used to identify the AIoT device.

[0691] S1803, the UE confirms whether the gNB (e.g., the target gNB) supports AIoT capabilities.

[0692] For example, if an RLF occurs between the UE and the source gNB, the source gNB determines whether the target gNB supports AIoT capabilities. For example, if it is determined that the target gNB supports AIoT capabilities, the UE and the target gNB complete a RA.

[0693] S1804, the UE sends an RRC establishment request message (e.g., RRCReestablishmentRequest / UAI / other RRC msg) to the target gNB;

[0694] Correspondingly, the target gNB receives an RRC establishment request message from the UE.

[0695] For example, an RRC establishment request message includes at least one of the following:

[0696] (1) UE type: UEreader or legacy UE;

[0697] (2) Second identifier: used to identify the current first AIoT service;

[0698] (3) Whether to continue to perform the first AIoT service, or whether to continue to act as the reader / writer of the first AIoT service;

[0699] (4) Does it have any ongoing AIoT business?

[0700] (5) Whether data and / or signaling related to the first AIoT business are reported.

[0701] The following section, combining Method 1 and Method 2, explains how to ensure the continuity of the first AIoT service in scenarios where a Recurrent Function Failure (RLF) occurs between the UE and the source gNB, i.e., a cell handover occurs for the UE. Method 1 primarily provides an example of the source gNB determining whether the UE should continue executing the first AIoT service, while Method 2 primarily provides an example of the target gNB determining whether the UE should continue executing the first AIoT service.

[0702] Method 1:

[0703] S1805, the target gNB sends a Retrieve UE Context Request message #1 (e.g., a Retrieve UE Context Request message) to the source gNB;

[0704] Correspondingly, the source gNB receives the Get UE Context Request message #1 from the target gNB.

[0705] For example, the UE context request message #1 includes at least one of the following:

[0706] (1) UE type: UEreader or legacy UE;

[0707] (2) Second identifier: used to identify the current first AIoT service;

[0708] (3) Whether to continue to perform the first AIoT service, or whether to continue to act as the reader / writer of the first AIoT service;

[0709] (4) Does it have any ongoing AIoT business?

[0710] (5) Whether data and / or signaling related to the first AIoT business are reported;

[0711] (6) Service area information indicates the area where the first AIoT service is performed, or in other words, the UE Reader can perform or conduct the first AIoT service within the area indicated by the service area information.

[0712] S1806, the source gNB determines whether the UE should continue to execute the first AIoT service.

[0713] For example, the source gNB determines whether the UE can continue to perform the current first AIoT service, and / or whether it can continue to act as a reader, based on the service area and / or UE type. For specific determination methods, please refer to the relevant description of step S1003 of method 1000 above.

[0714] ●Scenario 1: The source gNB determines that the UE should continue to execute the first AIoT service. At this time, the UE is a UE Reader.

[0715] S1807, the source gNB sends a Retrieve UE Context Response message #1 (e.g., a Retrieve UE Context Response message) to the target gNB;

[0716] Correspondingly, the target gNB receives the Get UE Context Response Message #1 from the source gNB.

[0717] For example, obtaining UE context response message #1 includes at least one of the following:

[0718] (1) UE type (UE type indication): UEreader, or in other words, UE type is reader / writer;

[0719] (2) The UE continues to perform the first AIoT service (AIoT service continue or not), or the UE continues to be a reader / writer;

[0720] (3) Report data and / or signaling related to the first AIoT business.

[0721] ●Scenario 2: The source gNB determines that the UE will not continue to execute the first AIoT service. In this case, the UE is a normal UE (e.g., a legacy UE).

[0722] For example, obtaining UE context response message #1 includes at least one of the following:

[0723] (1) UE type (UE type indication): Legency UE, or in other words, UE type is ordinary UE;

[0724] (2) The UE will not continue to execute the first AIoT service.

[0725] (3) The UE does not report data and / or signaling related to the first AIoT service.

[0726] Method 2:

[0727] S1808, the target gNB sends a Retrieve UE Context Request message #2 (e.g., a Retrieve UE Context Request message) to the source gNB;

[0728] Correspondingly, the source gNB receives the Get UE Context Request message #2 from the target gNB.

[0729] For example, the UE context request message #2 includes at least one of the following:

[0730] (1) UE type: UEreader or legacy UE;

[0731] (2) Second identifier: used to identify the current first AIoT service;

[0732] (3) Whether to continue to perform the first AIoT service, or whether to continue to act as the reader / writer of the first AIoT service;

[0733] (4) Are there any AIoT services currently in operation?

[0734] (5) Whether data and / or signaling related to the first AIoT business are reported.

[0735] Optionally, the UE type can also come from the UE or the core network element, without limitation.

[0736] S1809, the source gNB sends a Retrieve UE Context Response message #2 (e.g., a Retrieve UE Context Response message) to the target gNB;

[0737] Correspondingly, the target gNB receives the Get UE Context Response Message #2 from the source gNB.

[0738] For example, obtaining UE context response message #2 includes at least one of the following:

[0739] (1) Regional information;

[0740] (2) UE type: UEreader or legacy UE;

[0741] (3) Second identifier: used to identify the current first AIoT service;

[0742] (4) Whether to continue performing the first AIoT service, or whether to continue acting as the reader / writer for the first AIoT service;

[0743] (5) Whether there are any ongoing AIoT services;

[0744] (6) Whether data and / or signaling related to the first AIoT business are reported;

[0745] (7) Service area information indicates the area where the first AIoT service is performed, or in other words, the UE Reader can perform or conduct the first AIoT service within the area indicated by the service area information.

[0746] S1810, the target gNB determines whether the UE should continue to execute the first AIoT service.

[0747] For example, the target gNB determines whether the UE can continue to perform the current first AIoT service, and / or whether it can continue to act as the reader of the first AIoT service, based on the service area and / or UE type.

[0748] ●Scenario 1: The target gNB determines that the UE should continue to execute the first AIoT service. At this time, the UE is a UE Reader.

[0749] S1811, the target gNB sends an RRC establishment response message (e.g., RRCReestablishmentResponse / UAI / other RRC msg) to the UE;

[0750] Correspondingly, the UE receives an RRC establishment response message from the target gNB.

[0751] For example, an RRC establishment response message includes at least one of the following:

[0752] (1) UE type: UEreader;

[0753] (2) Second identifier: used to identify the current first AIoT service;

[0754] (3) The UE continues to perform the first AIoT service, or the UE continues to act as the reader / writer of the first AIoT service;

[0755] (4) It has ongoing AIoT business;

[0756] (5) Report data and / or signaling related to the first AIoT service;

[0757] (6) First resource (e.g., AIoT radio resource): used for the UE to communicate with AIoT devices or to perform the first AIoT service.

[0758] ●Scenario 2: The target gNB determines that the UE will not continue to execute the first AIoT service. In this case, the UE is a normal UE (e.g., a legacy UE).

[0759] For example, an RRC establishment response message includes at least one of the following:

[0760] (1) UE type: Legency UE;

[0761] (3) The UE does not continue to execute the first AIoT service, or the UE does not continue to act as the reader / writer of the first AIoT service;

[0762] (4) The UE is not currently running any AIoT services;

[0763] (5) The UE does not report data and / or signaling related to the first AIoT service;

[0764] (6) Fourth resource: Used for the UE to communicate with other devices or to perform non-AIoT services.

[0765] Based on the above method one or method two, the UE completes the RRC connection with the target gNB and sends an RRC establishment completion message back to the target gNB. The specific implementation is described in the following steps S1812.

[0766] S1812, the UE sends an RRC establishment completion message (e.g., RRCReestablishment) to the target gNB;

[0767] Correspondingly, the target gNB receives the RRC establishment complete message from the UE.

[0768] S1813, the target gNB sends a path switching request message to the AMF / AIoTF;

[0769] Correspondingly, the AMF / AIoTF receives a path switching request message from the target gNB.

[0770] S1814, AMF / AIoTF sends a path switching request confirmation message to target gNB A;

[0771] Correspondingly, the target gNB receives a path switching request confirmation message from the AMF / AIoTF.

[0772] Optionally, the path switching request confirmation message may carry an authorization indication and / or a first resource, wherein the authorization indication is used to authorize the UE as a reader / writer for the first AIoT service. If the first resource is carried in step S1811, the path switching request confirmation message may not carry the first resource.

[0773] Optionally, the authorization instruction is used to indicate that the first terminal is allowed (allowance can be replaced by authorization) to act as a reader / writer for the AIoT service, or that the first terminal is authorized to act as an A-IoT-enable UE for the first AIoT service, or to indicate that the first terminal is authorized to perform the first AIoT service, or to indicate that the first terminal is authorized to act as an A-IoT-enable UE for the first AIoT service, or to indicate that the first terminal is authorized to communicate with the AIoT device, or to indicate that the first terminal is authorized to transmit one or more of the following messages, data, or signaling related to the first AIoT service to the AIoT device.

[0774] The specific implementation of steps S1813-S1814 above can be found in existing descriptions and will not be explained here.

[0775] S1815, the target gNB sends an indication message to the UE, which indicates the first resource or the fourth resource;

[0776] Correspondingly, the UE receives indication information from the target gNB.

[0777] The indication information indicates the first resource or the fourth resource, depending on whether the UE continues to perform the first AIoT service, and / or whether the UE continues to act as a reader / writer for the first AIoT service, and / or whether the UE is authorized to act as a reader / writer, etc.

[0778] For example, the target gNB may send the first resource to the UE based on the authorization instruction.

[0779] Understandably, step S1815 is optional. If step S1811 carries the first resource, then step S1815 may not be executed.

[0780] Based on the above solution, the T2 RRC-based solution addresses the issue of AIoT service continuity, ensures the performance of AIoT services, and improves the user experience.

[0781] Figure 19 is a schematic diagram of a communication method 1900 provided in an embodiment of this application. As shown in Figure 19, method 1900 may include the following steps, and for details not covered herein, please refer to the relevant description in method 2000 of Figure 20 below.

[0782] S1910, the first terminal sends a first message to the first access network device;

[0783] Correspondingly, the first access network device receives the first message from the first terminal.

[0784] The first message includes resource request information, which is used by the first terminal to execute the first AIoT service. The second access network device is the network device that the first terminal accesses after the wireless link between the first terminal and the first access network device fails.

[0785] For example, the resource request information includes at least one of the following:

[0786] (1) The number of resource blocks (RBs) or the duration of communication between the first terminal and the AIoT device;

[0787] (2) The first terminal requests or indicates whether it supports LTE or NR guard band, inband, or standalone bands;

[0788] (3) The frequency band number supported by the first terminal or the frequency band number requested by the first terminal.

[0789] For example, the first message includes a second identifier.

[0790] S1920, the first access network device sends the second message to the core network element;

[0791] Correspondingly, the core network element receives the second message from the first access network device.

[0792] The second message includes at least one of the following: whether the first terminal is authorized as a reader / writer, whether the first terminal continues to be a reader / writer, or whether the first terminal continues to perform the first AIoT service.

[0793] S1930, the core network element determines whether the first terminal should continue to execute the first AIoT service based on the regional information and / or the type of the first terminal. For specific implementation details, please refer to the relevant description of method 1100 above.

[0794] S1940, the core network element sends the fourth message to the first terminal;

[0795] Correspondingly, the first terminal receives the fourth message from the core network element.

[0796] The fourth message includes an instruction message that instructs the first resource.

[0797] Furthermore, the first terminal continues to execute the first AIoT service based on the first resource. Optionally, if the fourth message does not indicate the first resource, the first terminal stops executing or does not execute the first AIoT service.

[0798] Optionally, the first terminal receives indication information from the second access network device, which indicates a timer and / or a valid area. That is, the first terminal can execute or perform a first AIoT service within a period of time indicated by the timer and / or within the valid area.

[0799] Figure 20 is a schematic diagram of a communication method 2000 provided in an embodiment of this application. As shown in Figure 20, taking the first terminal as UE, the core network element as AMF / AIoTF, the first access network device as source gNB (or lastserving gNB), and the second access network device as target gNB (or new gNB) as an example, this method is applicable to the NAS / UP-based solution architecture in the RLF scenario, and method 2000 may include the following steps.

[0800] S2001, AMF / AIoTF sends NAS message / PDU session #1 to the source gNB;

[0801] Correspondingly, the source gNB receives NAS messages / PDU sessions #1 from the AMF / AIoTF.

[0802] Among them, NAS message / PDU session #1 includes AIoT service request message, which is used to request the execution of the first AIoT service (such as inventory service).

[0803] S2002, the source gNB sends a NAS message / PDU session #2 to the UE;

[0804] Correspondingly, the UE receives NAS message / PDU session #2 from the source gNB.

[0805] Among them, NAS message / PDU session #2 includes AIoT service request messages.

[0806] It should be noted that in step S2001 above, the AMF / AIoTF sends a NAS message / PDU session to the UE through the source gNB. This NAS message / PDU session #1 is transparent to the N source gNB, that is, the source gNB cannot parse and obtain the information carried in the NAS message / PDU session, but the UE can parse and obtain the information carried in the NAS message / PDU session.

[0807] S2003, the UE confirms whether the gNB (e.g., the target gNB, or the new gNB) supports AIoT capabilities.

[0808] For example, if an RLF occurs between the UE and the source gNB, the source gNB determines whether the target gNB supports AIoT capabilities. For example, if it is determined that the target gNB supports AIoT capabilities, the UE and the target gNB complete a RA.

[0809] S2004, the UE sends an RRC establishment request message (e.g., RRCReestablishmentRequest / UAI / other RRC msg) to the target gNB;

[0810] Correspondingly, the target gNB receives an RRC establishment request message from the UE.

[0811] The RRC establishment request message includes a resource request message, which is used to request a first resource, and the first resource is used by the UE to execute a first AIoT service.

[0812] Optionally, the RRC establishment request message may also include a second identifier, which is used to identify the first AIoT service.

[0813] Optionally, the target gNB sends a Get UE Context Request message to the source gNB to request the UE context; correspondingly, the source gNB receives the Get UE Context Request message from the target gNB and sends the UE context to the target gNB.

[0814] S2005, the target gNB sends a path switching request message #1 to the AMF / AIoTF;

[0815] Correspondingly, the AMF / AIoTF receives path switching request message #1 from the target gNB.

[0816] For example, the path switching request message #1 may carry at least one of the following:

[0817] (1) UE type: UEreader or legacy UE;

[0818] (2) Second identifier: used to identify the current first AIoT service;

[0819] (3) Whether to continue to perform the first AIoT service, or whether to continue to act as the reader / writer of the first AIoT service;

[0820] (4) Are there any AIoT services currently in operation?

[0821] (5) Whether data and / or signaling related to the first AIoT business are reported.

[0822] S2006, AMF / AIoTF determines whether the UE can continue to perform the current first AIoT service.

[0823] For example, the AMF / AIoTF determines whether the UE can continue performing the current first AIoT service and / or whether it can continue to act as a reader based on the service area information and / or UE type. For specific implementation details, please refer to the description of step S1209 in method 1200 above, which will not be repeated here.

[0824] S2007, AMF / AIoTF sends a handover request confirmation message #1 (e.g., Xn handover request confirmation message) to the target gNB;

[0825] Correspondingly, the target gNB receives path switching request confirmation message #1 from AMF / AIoTF.

[0826] S2008, the target gNB sends the first resource to the UE;

[0827] Correspondingly, the UE receives the first resource from the target gNB.

[0828] Based on the above solutions, the T2 NAS-based or UP-based solutions address the issue of AIoT service continuity, ensure the performance of AIoT services, and improve the user experience.

[0829] Figure 21 is a schematic diagram of a communication method 2100 provided in an embodiment of this application. As shown in Figure 21, taking the first terminal as UE, the core network element as AMF / AIoTF, the first access network device as source gNB (or lastserving gNB), and the second access network device as target gNB (or new gNB) as an example, method 2100 may include the following steps.

[0830] S2101, AMF / AIoTF sends NAS message / PDU session #1 to the source gNB;

[0831] Correspondingly, the source gNB receives NAS messages / PDU sessions #1 from the AMF / AIoTF.

[0832] Among them, NAS message / PDU session #1 includes AIoT service request message, which is used to request the execution of the first AIoT service (such as inventory service).

[0833] S2102, the source gNB sends a NAS message / PDU session #2 to the UE;

[0834] Correspondingly, the UE receives NAS message / PDU session #2 from the source gNB.

[0835] Among them, NAS message / PDU session #2 includes AIoT service request messages.

[0836] It should be noted that in step S2101 above, the AMF / AIoTF sends a NAS message / PDU session to the UE through the source gNB. This NAS message / PDU session #1 is transparent to the N source gNB, that is, the source gNB cannot parse and obtain the information carried in the NAS message / PDU session, but the UE can parse and obtain the information carried in the NAS message / PDU session.

[0837] S2103, the UE confirms whether the gNB (e.g., the target gNB) supports AIoT capabilities.

[0838] For example, if an RLF occurs between the UE and the source gNB, the source gNB determines whether the target gNB supports AIoT capabilities. For example, if it is determined that the target gNB supports AIoT capabilities, the UE and the target gNB complete a RA.

[0839] S2104, the UE sends an RRC establishment request message (e.g., RRCReestablishmentRequest / UAI / other RRC msg) to the target gNB;

[0840] Correspondingly, the target gNB receives an RRC establishment request message from the UE.

[0841] The RRC establishment request message includes a resource request message and area information. The resource request message is used to request a first resource, which is used by the UE to execute a first AIoT service. The area information indicates the area used to execute the first AIoT service.

[0842] The following section, combining Method 1 and Method 2, explains how to ensure the continuity of the first AIoT service in scenarios where the UE and source gNB experience a Recurrent Function Failure (RLF), i.e., a cell handover occurs. Method 1 primarily provides an example of the target gNB determining whether the UE should continue executing the first AIoT service, while Method 2 primarily provides an example of the source gNB determining whether the UE should continue executing the first AIoT service.

[0843] Method 1:

[0844] S2105, the source gNB sends a Retrieve UE Context Request message #1 (e.g., a Retrieve UE Context Request message) to the target gNB;

[0845] Correspondingly, the target gNB receives the Get UE Context Request message #1 from the source gNB.

[0846] S2106, the source gNB determines whether the UE can continue to perform the current first AIoT service based on the service area information and / or the first terminal type (e.g., UE type).

[0847] S2107, the target gNB sends a UE context acquisition response message #1 to the source gNB;

[0848] Correspondingly, the source gNB receives the Get UE Context Response Message #1 from the target gNB.

[0849] Method 2:

[0850] S2108, the source gNB sends a Retrieve UE Context Request message #2 (e.g., a Retrieve UE Context Request message) to the target gNB;

[0851] Correspondingly, the target gNB receives the Get UE Context Request message #2 from the source gNB.

[0852] S2109, the target gNB sends a UE context acquisition response message #1 to the source gNB;

[0853] Correspondingly, the source gNB receives the Get UE Context Response Message #1 from the target gNB.

[0854] S2110, the source gNB determines whether the UE can continue to perform the current first AIoT service based on the service area information and / or the first terminal type (e.g., UE type).

[0855] For any parts not fully explained in Method 1 or Method 2 above, please refer to the relevant descriptions of Method 1 or Method 2 of Method 1800 above.

[0856] S2111, the target gNB sends a path switching request message #1 to the AMF / AIoTF;

[0857] Correspondingly, the AMF / AIoTF receives path switching request message #1 from the target gNB.

[0858] S2112, AMF / AIoTF sends a path switching request confirmation message #1 to the target gNB;

[0859] Correspondingly, the target gNB receives path switching request confirmation message #1 from AMF / AIoTF.

[0860] S2113, the target gNB sends the first resource to the UE;

[0861] Correspondingly, the UE receives the first resource from the target gNB.

[0862] Based on the above solutions, the T2 NAS-based or UP-based solutions address the issue of AIoT service continuity, ensure the performance of AIoT services, and improve the user experience.

[0863] As mentioned above, the access network equipment involved in this implementation example can be based on the ORAN architecture. The following is a brief introduction to the application of the communication methods shown in Figures 8 to 21 above under the ORAN architecture.

[0864] Under the O-RAN architecture, the RIC can directly control both gNB-CU and gNB-DU. Therefore, the "access network device" in the communication method steps shown in Figures 8 to 21 above needs to be expanded to "CU" and "DU".

[0865] Optionally, in various embodiments of this application, if the access network device (e.g., the first access network device and / or the second access network device) is a CU-DU separated architecture, after the CU receives the xxAP / NGAP message from the core network element (e.g., the first core network element or the second core network element), it can forward the xxAP / NGAP message to the DU via an F1AP message, or send the AIoT-related information contained in the xxAP / NGAP message to the DU via an F1AP message. After the DU receives the RRC message from the UE, it can forward the RRC message to the CU via an F1AP message, or send the AIoT information contained in the RRC message to the CU via an F1AP message.

[0866] In this scheme, the XXAP / NGAP messages transmitted on the F1 interface F1AP and the xxAP / NGAP messages transmitted on the XX / NG interface XXAP / NGAP can be different. That is, the CU can perform relevant processing on the messages, which may include one or more of the following: deletion, filtering, mapping, modification, or addition of auxiliary information. Based on this scheme, access network devices under the CU-DU separation architecture can also implement the methods provided in the various embodiments of this application.

[0867] In one possible implementation, the first access network device receives a message from the first terminal, including: the DU of the first access network device receiving message #z1 from the first terminal (e.g., message #z1 is an RRC message); the DU of the first access network device sending message #z2 to the CU of the first access network device according to message #z1 (e.g., message #z2 is an F1 application protocol (F1AP) message). Furthermore, the CU of the first access network device can send message #z3 to the core network element (message #z3 can be an XXAP message or an NGAP message).

[0868] Message #z2 contains information #z2 that is related to information #z1 in message #z1. For example, information #z1 and information #z2 are the same, or information #z2 is obtained by the DU of the first access network device processing information #z1 (e.g., deleting, filtering, mapping, modifying, or adding auxiliary information). Message #z3 contains information #z3 that is related to information #z2 in message #z2. For example, information #z3 and information #z2 are the same, or information #z3 is obtained by the CU of the first access network device processing information #z2 (e.g., deleting, filtering, mapping, modifying, or adding auxiliary information).

[0869] In one possible implementation, the first access network device receives a message from a core network element, including: the CU of the first access network device receiving message #z4 from the core network element (message #z4 can be an XXAP message or an NGAP message); the CU of the first access network device sending message #z5 to the DU of the first access network device based on message #z4 (for example, message #z2 is an F1AP message). Furthermore, the DU of the first access network device can send message #z6 to the UE based on the received message #z5.

[0870] Message #z5 contains information #z5 that is related to information #z4 in message #z4. For example, information #z4 and information #z5 are the same, or information #z5 is obtained by the CU of the first access network device processing information #z4 (e.g., deleting, filtering, mapping, modifying, or adding auxiliary information). Message #z6 contains information #z6 that is related to information #z5 in message #z5. For example, information #z5 and information #z6 are the same, or information #z6 is obtained by the DU of the first access network device processing information #z5 (e.g., deleting, filtering, mapping, modifying, or adding auxiliary information).

[0871] It should be understood that the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0872] It should also be understood that, in the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other, and the technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0873] It should also be understood that in some of the above embodiments, exemplary descriptions are mainly based on devices in existing network architectures (such as AIoT devices or core network elements). It should be understood that the specific form of the device is not limited in the embodiments of this application. For example, any device that can achieve the same function in the future is applicable to the embodiments of this application.

[0874] It is understood that the methods and operations implemented by devices (such as AIoT devices or core network elements) in the above-described method embodiments can also be implemented by components (such as chips or circuits).

[0875] Those skilled in the art will recognize that, based on the units and algorithm steps described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is implemented in hardware or by computer software driving hardware 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.

[0876] The communication method embodiments of this application have been described in detail above with reference to Figures 1 to 21. The communication device embodiments of this application will now be described in detail with reference to Figures 22 and 23. It should be understood that the descriptions of the device embodiments correspond to the descriptions of the method embodiments; therefore, any parts not described in detail can be referred to the preceding method embodiments.

[0877] Figure 22 is a schematic block diagram of a communication device 2200 provided in an embodiment of this application. As shown in Figure 22, the communication device 2200 includes a processing module 2210 and a communication module 2220. The communication device 2200 can be a terminal-side device, or a communication device applied to or used in conjunction with a terminal-side device to implement a method executed on the terminal-side device, such as a chip, chip system, or circuit; or, the communication device 2200 can be a network-side device, or a communication device applied to or used in conjunction with a network-side device to implement a method executed on the network-side device, such as a chip, chip system, or circuit.

[0878] The communication module can also be called a transceiver module, transceiver, transceiver unit, or transceiver device. The processing module can also be called a processor, processing board, processing unit, or processing device. Optionally, the communication module is used to perform the sending and receiving operations on the terminal side and network side in the above method. The device in the communication module that implements the receiving function can be considered a receiving unit, and the device in the communication module that implements the sending function can be considered a sending unit; that is, the communication module includes a receiving unit and a sending unit.

[0879] Optionally, the communication device 2200 may also include a storage module for storing device program code and / or data.

[0880] In one example, when the communication device 2200 is applied to the terminal side, it is for example, a terminal or a communication module in the terminal, or a circuit or chip in the terminal responsible for communication functions. The processing module 2210 can be used to implement the processing functions on the terminal side in the above embodiments, and the communication module 2220 can be used to implement the transmit and receive functions on the terminal side in the above embodiments.

[0881] For example, the communication module 2220 is configured to receive a message from a first access network device or a second access network device, the message being configured to instruct the first terminal to switch to the second access network device; the processing module 2210 is configured to continue executing the first environment Internet of Things (AIoT) service according to the first resource if the message includes resource configuration information, the resource configuration information indicating a first resource; the processing module 2210 is configured to stop or cease executing the first AIoT service if the message does not include the resource configuration information.

[0882] For example, the processing module 2210 is configured to: execute a first environment Internet of Things (AIoT) service, wherein the first terminal accesses a first access network device; discover an RLF between the first terminal and the first access network device; and stop or continue the first AIoT service.

[0883] The terminal side includes terminal devices, or chips or circuits in the terminal devices (such as modem chips, also known as baseband chips, or system-on-chip (SoC) chips or system-in-package (SIP) chips containing modem cores), or functional modules in the terminal devices that can call and execute programs.

[0884] In one possible design, when the communication device 2200 is a terminal or a communication module within a terminal, the functionality of the processing module 2210 can be implemented by one or more processors. Specifically, the processor may include a modem chip, or a system-on-a-chip (SoC) or SIP chip containing a modem core. The functionality of the communication module 2220 can be implemented by transceiver circuitry.

[0885] In one possible design, when the communication device 2200 is a circuit or chip in a terminal responsible for communication functions, such as a modem chip or a system-on-a-chip (SoC) or SIP chip containing a modem core, the function of the processing module 2210 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 module 2220 can be implemented by interface circuits or data transceiver circuits on the aforementioned chip.

[0886] In one example, when the communication device 2200 is applied to the network side, it is for example, a network device or a communication module in a network device, or a circuit or chip on the network side responsible for communication functions. The processing module 2210 can be used to implement the processing functions on the network side in the above embodiments, and the communication module 2220 can be used to implement the transmit and receive functions on the network side in the above embodiments.

[0887] For example, the communication module 2220 is configured to receive a first message from a first access network device, the first message being a request to switch the first terminal to a second access network device, the first message including first indication information indicating the type of the first terminal; the communication module 2220 is configured to send a second message to the first access network device, the second message including second indication information, the second indication information indicating that the first terminal continues to act as a reader / writer for the first AIoT service, and / or that the first terminal continues to perform the first AIoT service; wherein, the second indication information is determined according to the type of the first terminal.

[0888] For example, the communication module 2220 is configured to send a first message to the second access network device, the first message being a request to switch the first terminal to the second access network device, the first message including first indication information indicating the type of the first terminal; the communication module 2220 is configured to receive a second message from the second access network device, the second message including second indication information, the second indication information indicating that the first terminal continues to act as a reader / writer for the first environment's Internet of Things (AIoT) service, and / or that the first terminal continues to perform the first AIoT service; wherein, the second indication information is determined based on the type of the first terminal.

[0889] The network side includes network devices (e.g., a first access network device or a second access network device), or chips or circuits in the network devices, or central units (CUs) or distributed units (DUs) in the network devices, or functional modules in the network devices that can call and execute programs.

[0890] In one example, when the communication device 2200 is applied to the core network side, it is for example, a core network element or a communication module within a core network element, or a circuit or chip within a core network element responsible for communication functions. The processing module 2210 can be used to implement the processing functions on the core network side in the above embodiments, and the communication module 2220 can be used to implement the transmit and receive functions on the core network side in the above embodiments.

[0891] For example, the communication module 2220 is configured to receive a first message, the first message including first information, the first information being used to request whether the first terminal should continue to perform the first environment Internet of Things (AIoT) service, and / or whether the first terminal should continue to act as a reader / writer for the first AIoT service; the communication module 2220 is configured to send a second message to the second access network device, the second message including first indication information; wherein, the first indication information indicates that the first terminal is authorized to act as a reader / writer for the first AIoT service, and / or that the first terminal continues to perform the first AIoT service, and / or that the first terminal continues to act as a reader / writer for the first AIoT service; or, the first indication information indicates that the first terminal is denied authorization to act as a reader / writer for the first AIoT service, and / or that the first terminal does not continue to perform the first AIoT service, and / or that the first terminal does not continue to act as a reader / writer for the first AIoT service.

[0892] Furthermore, it should be noted that the aforementioned communication module and / or processing module can be implemented through virtual modules. For example, the processing module can be implemented through software functional units or virtual devices, and the communication module can be implemented through software functions or virtual devices. Alternatively, the processing module or communication module can also be implemented through physical devices, such as chips / circuits (e.g., integrated circuits or logic circuits). The communication module can be an input / output circuit and / or a communication interface, performing input operations (corresponding to the aforementioned receiving operation) and output operations (corresponding to the aforementioned sending operation); the processing module is an integrated processor, microprocessor, or circuit (e.g., integrated circuits or logic circuits).

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

[0894] The module division in this application is illustrative and represents only one logical functional division. In actual implementation, other division methods are possible. Furthermore, the functional modules in the various examples of this application can be integrated into a single processor, exist as separate physical entities, or be integrated into a single module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0895] Figure 23 is a schematic block diagram of a communication device 2300 provided in an embodiment of this application. Optionally, the communication device 2300 may be a chip or a chip system. Optionally, in this application, the chip system may be composed of chips or may include chips and other discrete devices.

[0896] As shown in Figure 23, the communication device 2300 can be used to implement the functions of any device (e.g., terminal device, network device) in the communication system described in the foregoing examples. The communication device 2300 may include at least one processor 2310. Optionally, the processor 2310 is coupled to a memory, which may be located within the device, integrated with the processor, or located outside the device. For example, the communication device 2300 may also include at least one memory 2320. The memory 2320 stores the computer programs, instructions, and / or data necessary for implementing any of the above examples; the processor 2310 may execute the computer programs stored in the memory 2320 to complete the methods in any of the above examples.

[0897] The communication device 2300 may also include a communication interface 2330, through which the communication device 2300 can interact with other devices. For example, the communication interface 2330 may be a transceiver, circuit, bus, module, pin, or other type of communication interface. When the communication device 2300 is a chip-based device or circuit, the communication interface 2330 in the device 2300 may also be an input / output circuit, capable of inputting information (or receiving information) and outputting information (or sending information). The processor 2310 may be an integrated processor, microprocessor, integrated circuit, or logic circuit, etc., and the processor can determine the output information based on the input information.

[0898] In one example, when the communication device 2300 is applied to the terminal side, the processor 2310 can be used to implement the processing functions of the terminal side in the above embodiments, and the communication interface 2330 can be used to implement the sending and receiving functions of the terminal side in the above embodiments.

[0899] The terminal side includes terminal devices, or chips or circuits in the terminal devices (such as modem chips, also known as baseband chips, or system-on-chip (SoC) chips or system-in-package (SIP) chips containing modem cores), or functional modules in the terminal devices that can call and execute programs.

[0900] In another example, when the communication device 2300 is applied to the network side, the processor 2310 can be used to implement the network side processing function in the above embodiments, and the communication interface 2330 can be used to implement the network side sending and receiving function in the above embodiments.

[0901] The network side includes network devices, or chips or circuits within network devices, or central units (CUs) or distributed units (DUs) within network devices, or functional modules within network devices that can call and execute programs.

[0902] The coupling in this application refers to indirect coupling or communication connection between devices, units, or modules, which can be electrical, mechanical, or other forms, used for information exchange between devices, units, or modules. The processor 2310 may operate in conjunction with the memory 2320 and the communication interface 2330. This application does not limit the specific connection medium between the processor 2310, the memory 2320, and the communication interface 2330.

[0903] Optionally, as shown in FIG23, the processor 2310, the memory 2320, and the communication interface 2330 are interconnected via a bus 2340. Optionally, the bus may include buses of the types such as address bus, data bus, and control bus. Furthermore, for ease of illustration, FIG23 shows one bus 2340, but does not indicate that there is only one bus or only one type of bus.

[0904] It should be understood that the processor mentioned in the embodiments of this application can be one of the following devices or a portion of the circuitry used for processing functions: 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, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor.

[0905] It should also be understood that the memory mentioned in the embodiments of this application can be volatile memory and / or non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM includes the following forms: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0906] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, the memory (storage module) can be integrated into the processor.

[0907] It should also be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0908] This application also provides a computer-readable storage medium storing computer instructions for implementing the methods executed by a communication device (such as a network side or a terminal side) in the above-described method embodiments.

[0909] This application also provides a computer program product comprising instructions which, when executed by a computer, implement the methods performed by a communication device (such as a network side or a terminal side) in the above-described method embodiments.

[0910] This application also provides a communication system, which includes the network side and / or terminal side described in the above embodiments.

[0911] The explanations and beneficial effects of the relevant contents in any of the devices provided above can be found in the corresponding method embodiments provided above, and will not be repeated here.

[0912] In the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0913] In this application, examples may reference each other without logical contradiction. For example, methods and / or terms between method embodiments may reference each other, functions and / or terms between device embodiments may reference each other, and functions and / or terms between device examples and method examples may reference each other.

[0914] It should be understood that the above embodiments are mainly illustrated using devices in existing network architectures as examples, and the specific form of the devices is not limited in the embodiments of this application. For example, any device that can achieve the same function in the future is applicable to the embodiments of this application.

[0915] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented 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.

[0916] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0917] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0918] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0919] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0920] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

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

Claims

1. A communication method, said method being applied to a second access network device or a chip in the second access network device, characterized in that, The method includes: Receive a first message from a first access network device, the first message being used to request switching the first terminal to the second access network device, the first message including first indication information, the first indication information indicating the type of the first terminal; Send a second message to the first access network device. The second message includes second indication information, which instructs the first terminal to continue acting as a reader / writer for the first AIoT service, and / or the first terminal to continue executing the first AIoT service. The second indication information is determined based on the first terminal type.

2. The method according to claim 1, characterized in that, The second indication information also indicates at least one of the following: a first resource, the first terminal reporting data and / or signaling related to the first AIoT service, or indicating permission to continue indicating the first AIoT service; The first resource is allocated to the first terminal by the second access network device, and the first resource is used to execute the first AIoT service.

3. The method according to claim 1 or 2, characterized in that, The first message also includes at least one of the following: Resource request information, area information, second identifier, whether to continue executing the first AIoT service, whether to continue acting as a reader / writer for the first AIoT service, whether there is an ongoing AIoT service, or whether to report data and / or signaling related to the first AIoT service; The resource request information is used to request a first resource, the first resource is used to execute the first AIoT service, the second identifier is used to identify the first AIoT service, and the area information indicates the area used to execute the first AIoT service.

4. The method according to any one of claims 1 to 3, characterized in that, The method further includes: A third message is received from a core network element, the third message including third indication information, the third indication information indicating that the first terminal is authorized as a reader / writer for the first AIoT service.

5. A communication method, said method being applied to a first access network device or a chip in the first access network device, characterized in that, The method includes: Send a first message to the second access network device. The first message is used to request the first terminal to be switched to the second access network device. The first message includes first indication information, which indicates the type of the first terminal. Receive a second message from the second access network device, the second message including second indication information, the second indication information instructing the first terminal to continue as a reader / writer for the first environment Internet of Things (AIoT) service, and / or, the first terminal to continue executing the first AIoT service; The second indication information is determined based on the first terminal type.

6. The method according to claim 5, characterized in that, The second indication information also indicates at least one of the following: a first resource, the first terminal reporting data and / or signaling related to the first AIoT service, or indicating permission to continue indicating the first AIoT service; The first resource is allocated to the first terminal by the second access network device, and the first resource is used to execute the first AIoT service.

7. The method according to claim 6, characterized in that, The method further includes: A fourth message is sent to the first terminal, the fourth message instructing the first terminal to switch to the second access network device, the fourth message including fourth indication information, the fourth indication information indicating the first resource.

8. The method according to any one of claims 5 to 7, characterized in that, The first message also includes at least one of the following: Resource request information, area information, second identifier, whether to continue executing the first AIoT service, whether there is an ongoing AIoT service, whether to continue acting as a reader / writer for the first AIoT service, and whether to report data and / or signaling related to the first AIoT service; The resource request information is used to request a first resource, which is used by the first terminal to continue executing the first AIoT service. The second identifier is used to identify the first AIoT service, and the area information indicates the area used to execute the first AIoT service.

9. The method according to any one of claims 5 to 8, characterized in that, Before receiving the second message from the second access network device, the method further includes: A fifth message is sent to the first terminal. The fifth message includes a fifth indication information, which indicates a third resource. The third resource is used by the first terminal to execute the first AIoT service before switching to the second access network device.

10. A communication method, said method being applied to a core network element or a chip within a core network element, characterized in that, The method includes: Receive a first message, the first message including first information, the first information being used to request whether the first terminal continues to execute the first environment Internet of Things (AIoT) service, and / or whether the first terminal continues to act as a reader / writer for the first AIoT service; Send a second message to the second access network device, the second message including first indication information; Wherein, the first indication information indicates that the first terminal is authorized as a reader / writer for the first AIoT service, and / or, the first terminal continues to execute the first AIoT service, and / or, the first terminal continues to act as a reader / writer for the first AIoT service; or, The first indication information indicates that authorization for the first terminal to act as a reader / writer for the first AIoT service is denied, and / or, the first terminal will not continue to execute the first AIoT service, and / or, the first terminal will not continue to act as a reader / writer for the first AIoT service.

11. The method according to claim 10, characterized in that, The first indication information is determined based on the first terminal type.

12. A communication method, said method being applied to a second access network device or a chip in the second access network device, characterized in that, The method includes: Receive a third message, the third message being used to request switching the first terminal to the second access network device, the third message including second indication information, the second indication information indicating the type of the first terminal, the first terminal type including the first terminal being a reader or the first terminal being a terminal that does not support reader functionality; A fourth message is sent to the first access network device, the fourth message indicating permission to switch the first terminal to the second access network device, wherein the first terminal type is used to determine whether to allow the first terminal to switch to the second access network device.

13. The method according to claim 12, characterized in that, The third message also includes at least one of the following: Resource request information, area information, second identifier, whether to continue executing the first AIoT service, whether there is an ongoing AIoT service, and whether to report data and / or signaling related to the first AIoT service; The resource request information is used to request a first resource, the first resource is used to execute the first AIoT service, the second identifier is used to identify the first AIoT service, and the area information indicates the area used to execute the first AIoT service.

14. The method according to claim 12 or 13, characterized in that, The method further includes: Send a first message to the core network element. The first message includes first information. The first information is used to request whether the first terminal should continue to execute the first environment Internet of Things (AIoT) service, and / or whether the first terminal should continue to act as a reader / writer for the first AIoT service. Receive a second message from the core network element, the second message including first indication information; Wherein, the first indication information indicates that the first terminal is authorized as a reader / writer for the first AIoT service, and / or, the first terminal continues to execute the first AIoT service, and / or, the first terminal continues to act as a reader / writer for the first AIoT service; or, The first indication information indicates that authorization for the first terminal to act as a reader / writer for the first AIoT service is denied, and / or, the first terminal will not continue to execute the first AIoT service, and / or, the first terminal will not continue to act as a reader / writer for the first AIoT service.

15. The method according to claim 14, characterized in that, Before receiving the second message from the core network element, the method further includes: A fifth message is sent to the first terminal or the first access network device. The fifth message includes third indication information, which indicates a second resource. The second resource is used by the first terminal to execute the first AIoT service.

16. The method according to claim 15, characterized in that, The method further includes: If the first indication information indicates that the first terminal is denied authorization as a reader / writer for the first AIoT service, and / or, the first terminal does not continue to execute the first AIoT service, and / or, the first terminal does not continue to act as a reader / writer for the first AIoT service, a sixth message is sent to the first terminal, the sixth message including a fourth indication information, the fourth indication information indicating to stop or cease the first AIoT service, and / or, indicating to release the second resource.

17. The method according to any one of claims 14 to 16, characterized in that, The method further includes: If the first indication information indicates that the first terminal is authorized as a reader / writer of the first AIoT service, and / or the first terminal continues to execute the first AIoT service, and / or the first terminal continues to act as a reader / writer of the first AIoT service, a seventh message is sent to the first terminal, the seventh message including a fifth indication information, the fifth indication information indicating the first resource.

18. A communication method, said method being applied to a first access network device or a chip in the first access network device, characterized in that, The method includes: Send a third message to the second access network device. The third message is used to request the first terminal to be switched to the second access network device. The third message includes second indication information, which indicates the type of the first terminal. The first terminal type includes the first terminal being a reader or the first terminal being a terminal that does not support the reader function. A fourth message is received from the second access network device, the fourth message indicating permission to switch the first terminal to the second access network device, wherein the first terminal type is used to determine whether to allow the first terminal to switch to the second access network device.

19. The method according to claim 18, characterized in that, The third message also includes at least one of the following: Resource request information, area information, second identifier, whether to continue executing the first environment Internet AIoT service, whether there is an ongoing AIoT service, and whether to report data and / or signaling related to the first AIoT service; The resource request information is used to request a first resource, the first resource is used to execute the first AIoT service, the second identifier is used to identify the first AIoT service, and the area information indicates the area used to execute the first AIoT service.

20. The method according to claim 18 or 19, characterized in that, Before sending the third message to the second access network device, the method further includes: Receive an eighth message, the eighth message including resource request information, the resource request information being used to request a first resource, the first resource being used to execute the first AIoT service; or... Receive a ninth message, which is used to request the first AIoT service; or, the ninth message includes a sixth indication information, which indicates the first AIoT service, or that there is an ongoing AIoT service. The first terminal type is determined based on the eighth message or the ninth message.

21. A communication method, said method being applied to a first terminal or a chip in the first terminal, characterized in that, include: Receive a message from a first access network device or a second access network device, the message being used to instruct the first terminal to switch to the second access network device; If the message includes resource configuration information, the resource configuration information indicates a first resource, and the first environment IoT AIoT service continues to be executed according to the first resource; If the message does not include the resource configuration information, the first AIoT service will be stopped or no longer executed.

22. The method according to claim 21, characterized in that, Before receiving a message from a first access network device or a second access network device, the method further includes: The device receives an indication message from the second access network device, the indication message indicating a third resource, the third resource being used by the first terminal to execute the first AIoT service before switching to the second access network device.

23. A communication method, said method being applied to a first access network device or a chip in the first access network device, characterized in that, The method includes: Send first information to a first terminal, the first information indicating a third resource, the third resource being used by the first terminal to execute a first environment Internet AIoT service when a first condition is met; The first condition includes any one of the following: the first terminal discovers a radio link failure (RLF) after accessing the first access network device, or the first terminal discovers an RLF after accessing the first access network but before successfully accessing the second access network device.

24. The method according to claim 23, characterized in that, Before sending the first information to the first terminal, the method further includes: Receive a first message, the first message including resource request information, the resource request information being used to request a first resource, the first resource being used to execute the first AIoT service; or... Receive a second message, the second message including indication information, the indication information indicating the first AIoT service, or for requesting to perform the first AIoT service; The first terminal type is determined based on the first message or the second message.

25. A communication method, said method being applied to a first terminal or a chip in the first terminal, characterized in that, The method includes: Execute the first environment Internet of Things (AIoT) service, wherein the first terminal is connected to the first access network device; A radio link failure (RLF) was detected between the first terminal and the first access network device. Stop or continue the first AIoT service.

26. The method according to claim 25, characterized in that, Before detecting the RLF between the first terminal and the first access network device, the method further includes: The system receives first information from the first access network device, the first information indicating a third resource, the third resource being used by the first terminal to execute a first environment Internet AIoT service when a first condition is met. The first condition includes any one of the following: the first terminal discovers a radio link failure (RLF) after accessing the first access network device, or the first terminal discovers an RLF after accessing the first access network but before successfully accessing the second access network device. Continuing the first AIoT service includes: The first AIoT service will continue based on the third resource.

27. A communication device, characterized in that, Includes modules or units for implementing the method as described in any one of claims 1 to 4, 12 to 17; or, Includes modules or units for implementing the method as described in any one of claims 5 to 9, 18 to 20, 23, or 24; or, Includes modules or units for implementing the method as described in claim 10 or 11; or, Includes modules or units for implementing the method as described in any one of claims 21 or 22, 25 or 26.

28. The communication device according to claim 27, characterized in that, The communication device includes a second access network device or a chip within the second access network device; or... The first access network device or the chip in the first access network device; or... Core network elements or chips within core network elements; or, The first terminal or the chip in the first terminal.

29. A computer-readable storage medium, characterized in that, The computer-readable storage medium is included in the communication device, and the computer-readable storage medium stores a computer program or instructions that, when executed, cause the method as described in any one of claims 1 to 26 to be implemented.

30. A computer program product comprising a computer program or instructions, characterized in that, When the computer program or instructions are run, the method as described in any one of claims 1 to 26 is implemented.

Images