Communication method and communication apparatus

Abstract

A communication method and a communication apparatus. When a reader is implemented by a terminal, if the terminal temporarily loses connection with a network side, for example, due to cell handover, RLF, or the terminal being in a non-connected state, a source access network device or the terminal may send, to a target access network device, information used for determining an A-IoT resource and / or information used for determining a carrier configuration, and the target access network device may configure the A-IoT resource and / or a carrier for the terminal on the basis of the received information, so that the terminal can continue to execute a first A-IoT service, thereby facilitating the continuity of the first A-IoT service, and ensuring users' service experience.

Description

A communication method and a communication device

[0001] This application claims priority to Chinese Patent Application No. 202411999446.X, filed with the China National Intellectual Property Administration on December 31, 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 communications, 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 A-IoT and other related technologies, the communication system can include readers and tags. Readers can be implemented by network devices (such as base stations) or terminals, and tags can be A-IoT devices, such as passive / semi-passive / active tags. A-IoT technology is mainly used to achieve the following services: inventory management, positioning, sensing, or command. Typical application scenarios for A-IoT technology include logistics, warehousing, industrial manufacturing, identity recognition, and environmental monitoring.

[0004] When the reader / writer is implemented by the terminal, the A-IoT device can send A-IoT data and / or signaling to the terminal. The terminal can then transmit the received A-IoT data and / or signaling to the core network elements that support or enable A-IoT via the base station. However, in practice, the terminal may experience temporary out-of-connection situations, such as handover (HO) or radio link failure (RLF). In such cases, the continuity of A-IoT services cannot be guaranteed. Summary of the Invention

[0005] This application provides a communication method and a communication device to ensure the continuity of A-IoT services.

[0006] Firstly, a communication method is provided, which can be applied to the first access network device side, such as the first access network device, modules (e.g., circuits, chips or chip systems (e.g., modem chips, also known as baseband chips, or system-on-chip (SoC) chips or system-in-package (SIP) chips containing modem cores) in the first access network device, or logical nodes, logical modules or software that can implement all or part of the first access network device.

[0007] The method includes: receiving a first message from a second access network device, the first message being used to initiate a handover request, the first message including first information, the first information being used to determine a first resource, the first resource being used by a terminal to execute a first A-IoT service; determining second information based on the first information, the second information indicating the first resource; and sending a second message to the second access network device, the second message including the second information.

[0008] Based on the above method, in the scenario where the terminal switches to the first access network device, the first access network device can receive first information from the second access network device for configuring the first resource, and configure the first resource for the terminal according to the received first information, so that the terminal can continue to execute the first AIoT service using the first resource, which helps to ensure the continuity of the first AIoT service and thus ensure the user service experience.

[0009] In conjunction with the first aspect, in one implementation, the first message further includes third information, which is used to determine the first carrier configuration information; the second message further includes fourth information, which is the first carrier configuration information.

[0010] Based on the above method, in the scenario where the terminal switches to the first access network device, the first access network device can receive third information from the second access network device for configuring the carrier, and configure the carrier for the terminal according to the received third information, which helps to ensure the continuity of the first AIoT service and thus ensure the user service experience.

[0011] Secondly, embodiments of this application provide a communication method that can be applied to a second access network device, such as a second access network device, a module (e.g., a circuit, a chip or chip system (e.g., a modem chip, or a SoC chip or SIP chip containing a modem core) in the second access network device, or a logical node, logical module or software that can implement all or part of the second access network device.

[0012] The method includes: sending a first message to a first access network device, the first message being used to initiate a handover request, the first message including first information, the first information being used to determine a first resource, the first resource being used by a terminal to execute a first A-IoT service; receiving a second message from the first access network device, the second message including second information, the second information indicating the first resource; and sending a third message to the terminal, the third message including the second information.

[0013] Based on the above method, in the scenario where the terminal switches to the first access network device, the second access network device can send first information for configuring the first resource to the first access network device, so that the first access network device can configure the first resource for the terminal according to the received first information, so that the terminal can use the first resource to continue to execute the first AIoT service, which helps to ensure the continuity of the first AIoT service and thus ensure the user service experience.

[0014] In conjunction with the second aspect, in one implementation, before sending the first message to the first access network device, the method further includes: receiving a fourth message from the terminal, the fourth message including the first information.

[0015] The fourth message can be a radio resource control (RRC) message. For example, the fourth message may be used to report data related to A-IoT services, such as an inventory report. For example, the fourth message may be used to provide user equipment assistance information (UAI), such as a UAI message. For example, the fourth message may be used to request A-IoT resources, such as an A-IoT resource request message. For example, the fourth message can also be other RRC messages, including reused existing RRC messages and new RRC messages; there are no restrictions.

[0016] Based on the above method, in scenarios where a terminal switches to the first access network device, the second access network device can receive the first information from the terminal. For example, in Scheme 2 (NAS-based scheme) and Scheme 3 (UP-based scheme) of Topology 2, the second access network device can receive the first information from the terminal.

[0017] In another implementation, in conjunction with the second aspect or any of its implementations, the first message further includes third information, which is used to configure the carrier; the second message further includes fourth information, which is the first carrier configuration information.

[0018] Based on the above method, in the scenario where the terminal switches to the first access network device, the second access network device can send third information for configuring the carrier to the first access network device, so that the first access network device can configure the carrier for the terminal according to the received third information, which helps to ensure the continuity of the first AIoT service and thus ensure the user service experience.

[0019] In conjunction with the second aspect or any of its implementations, in another implementation, the fourth message further includes third information, which is used to determine the first carrier configuration information; the third message further includes fourth information, which is the first carrier configuration information.

[0020] Based on the above method, in scenarios where a terminal switches to the first access network device, the second access network device can receive third information from the terminal. For example, in Scheme 2 (NAS-based scheme) and Scheme 3 (UP-based scheme) of Topology 2, the second access network device can receive third information from the terminal.

[0021] Thirdly, embodiments of this application provide a communication method that can be applied to the terminal side, such as a terminal, a module (e.g., a circuit, a chip or chip system (e.g., a modem chip, or a SoC chip or SIP chip containing a modem core), or a logical node, logical module, or software that can realize all or part of the terminal.

[0022] The method includes: sending a fourth message to a second access network device, the fourth message including first information, the first information being used to determine a first resource, the first resource being used by the terminal to execute a first A-IoT service; and receiving a third message from the second access network device, the third message instructing the terminal to switch to the first access network device, the third message including second information, the second information indicating the first resource.

[0023] The fourth message can be an RRC message. For example, the fourth message may be used to report data related to A-IoT services, such as an inventory report. For example, the fourth message may be used to provide user equipment auxiliary information, such as a UAI message. For example, the fourth message may be used to request A-IoT resources, such as an A-IoT resource request message. For example, the fourth message can also be other RRC messages, including reused existing RRC messages and new RRC messages; there are no restrictions.

[0024] Based on the above method, the terminal can send first information to the second access network device, so that when the terminal switches from the second access network device to the first access network device, the second access network device can send first information for configuring the first resource to the first access network device, so that the first access network device can configure the first resource for the terminal according to the received first information, and the terminal can use the first resource to continue to execute the first AIoT service, which helps to ensure the continuity of the first AIoT service and thus ensure the user service experience.

[0025] In conjunction with the third aspect, in one implementation, the fourth message further includes third information, which is used to determine the first carrier configuration information; the third message also includes fourth information, which is the first carrier configuration information.

[0026] Based on the above method, the terminal can send third information to the second access network device, so that when the terminal switches from the second access network device to the first access network device, the second access network device can send third information for configuring the carrier to the first access network device, so that the first access network device can configure the carrier for the terminal according to the received third information, which helps to ensure the continuity of the first AIoT service and thus ensure the user service experience.

[0027] Fourthly, embodiments of this application provide a communication method that can be applied to a terminal side, such as a terminal, a module (e.g., a circuit, a chip or chip system (e.g., a modem chip, or a SoC chip or SIP chip containing a modem core), or a logical node, logical module, or software that can implement all or part of the terminal.

[0028] The method includes: discovering an RLF while executing a first A-IoT service; sending a fifth message to a first access network device, the fifth message including first information, the first information being used to determine a first resource, the first resource being used by the terminal to execute the first A-IoT service; and receiving a sixth message from the first access network device, the sixth message including second information, the second information indicating the first resource.

[0029] Based on the above method, in the scenario where the terminal switches to the first access network device, the terminal can send first information to the first access network device, so that the first access network device can configure first resources for the terminal according to the received first information, so that the terminal can use the first resources to continue to execute the first AIoT service, which helps to ensure the continuity of the first AIoT service and thus ensure the user service experience.

[0030] In conjunction with the fourth aspect, in one implementation, the fifth message further includes third information, which is used to determine the first carrier configuration information; the sixth message further includes fourth information, which is the first carrier configuration information.

[0031] The fifth message can be an RRC message. For example, the fifth message may be used to request the reconstruction of the terminal's RRC connection, such as an RRC reconstruction request message (RRCRestablishmentRequest). For example, the fifth message may be used to provide user equipment assistance information, such as a UAI message. For example, the fifth message may be used to request A-IoT resources, such as an A-IoT resource request message. For example, the fifth message can also be other RRC messages, including reused existing RRC messages and new RRC messages; there are no restrictions.

[0032] Based on the above method, in the scenario where the terminal switches to the first access network device, the terminal can send third information to the first access network device, so that the first access network device can configure the carrier for the terminal according to the received third information, which helps to ensure the continuity of the first AIoT service and thus ensure the user service experience.

[0033] Fifthly, a communication method is provided, which can be applied to the first access network device side, such as the first access network device, modules (e.g., circuits, chips or chip systems (e.g., modem chips, or SoC chips or SIP chips containing modem cores) in the first access network device, or logical nodes, logical modules or software that can implement all or part of the first access network device.

[0034] The method includes: receiving a fifth message from a terminal, the fifth message including first information, the first information being used to determine a first resource, the first resource being used by the terminal to execute the first A-IoT service; determining second information based on the first information, the second information indicating the first resource; and sending a sixth message to the terminal, the sixth message including the second information.

[0035] The fifth message can be an RRC message. For example, the fifth message may be used to request the reconstruction of the terminal's RRC connection, such as an RRC establishment request. For example, the fifth message may be used to provide user equipment assistance information, such as a UAI message. For example, the fifth message may be used to request A-IoT resources, such as an A-IoT resource request message. For example, the fifth message can also be other RRC messages, including reused existing RRC messages and new RRC messages; there are no limitations.

[0036] Based on the above method, in the scenario where the terminal switches to the first access network device, the first access network device can receive the first information from the terminal and configure the first resource for the terminal according to the received first information, so that the terminal can use the first resource to continue to execute the first AIoT service, which helps to ensure the continuity of the first AIoT service and thus ensure the user service experience.

[0037] In conjunction with the fifth aspect, in one implementation, the fifth message further includes third information, which is used to determine the first carrier configuration information; the sixth message further includes fourth information, which is the first carrier configuration information.

[0038] Based on the above method, in the scenario where the terminal switches to the first access network device, the first access network device can receive third information from the terminal and configure the carrier for the terminal according to the received third information, which helps to ensure the continuity of the first AIoT service and thus ensure the user's service experience.

[0039] Sixthly, embodiments of this application provide a communication method that can be applied to a terminal side, such as a terminal, a module (e.g., a circuit, a chip or chip system (e.g., a modem chip, or a SoC chip or SIP chip containing a modem core), or a logical node, logical module, or software that can implement all or part of the terminal.

[0040] The method includes: executing a first A-IoT service, wherein the terminal is in a disconnected state; in executing the first A-IoT service, sending a seventh message to a first access network device, the seventh message being used to request the restoration of the terminal's suspended RRC connection, the seventh message including first information, the first information being used to determine a first resource, the first resource being used by the terminal to execute the first A-IoT service; and receiving an eighth message from the first access network device, the eighth message including second information, the second information indicating the first resource.

[0041] Based on the above method, in scenarios where the terminal is in a disconnected state, the terminal can send first information to the first access network device, so that the first access network device can configure first resources for the terminal according to the received first information, and the terminal can use the first resources to continue to execute the first AIoT service, which helps to ensure the continuity of the first AIoT service and thus ensure the user service experience.

[0042] In conjunction with the sixth aspect, in one implementation, the seventh message further includes third information, which is used to determine the first carrier configuration information; the eighth message further includes fourth information, which is the first carrier configuration information.

[0043] Based on the above method, in scenarios where the terminal is in a disconnected state, the terminal can send third information to the first access network device, so that the first access network device can configure a carrier for the terminal according to the received third information, which helps to ensure the continuity of the first AIoT service and thus ensure the user's service experience.

[0044] In a seventh aspect, a communication method is provided, which can be applied to the first access network device side, such as the first access network device, modules (e.g., circuits, chips or chip systems (e.g., modem chips, or SoC chips or SIP chips containing modem cores) in the first access network device, or logical nodes, logical modules or software that can implement all or part of the first access network device.

[0045] The method includes: receiving a seventh message from a terminal, the seventh message being used to request the resumption of a suspended RRC connection of the terminal, the seventh message including first information, the first information being used to determine a first resource, the first resource being used by the terminal to execute the first A-IoT service; determining second information based on the first information, the second information indicating the first resource; and sending an eighth message to the terminal, the eighth message including the second information.

[0046] Based on the above method, in scenarios where the terminal is in a disconnected state, the first access network device can receive the first information from the terminal and configure the first resource for the terminal according to the received first information, so that the terminal can use the first resource to continue to execute the first AIoT service, which helps to ensure the continuity of the first AIoT service and thus ensure the user's service experience.

[0047] In conjunction with the seventh aspect, in one implementation, the seventh message further includes third information, which is used to determine the first carrier configuration information; the eighth message further includes fourth information, which is the first carrier configuration information.

[0048] Based on the above method, in scenarios where the terminal is in a disconnected state, the first access network device can receive third information from the terminal and configure a carrier for the terminal according to the received third information, which helps to ensure the continuity of the first AIoT service and thus ensure the user's service experience.

[0049] Eighthly, embodiments of this application provide a communication method that can be applied to a terminal side, such as a terminal, a module (e.g., a circuit, a chip or chip system (e.g., a modem chip, or a SoC chip or SIP chip containing a modem core), or a logical node, logical module, or software that can implement all or part of the terminal.

[0050] The method includes: in executing a first A-IoT service, receiving a ninth message from a second access network device, the ninth message being used to switch the terminal to a first access network device; sending a tenth message to the first access network device, the tenth message including first information, the first information being used to determine a first resource, the first resource being used by the terminal to execute the first A-IoT service; and receiving an eleventh message from the first access network device, the eleventh message including second information, the second information indicating the first resource.

[0051] Based on the above method, in the scenario where the terminal switches to the first access network device, the terminal can send first information for configuring the first resource to the first access network device, so that the first access network device can configure the first resource for the terminal according to the received first information, so that the terminal can use the first resource to continue to execute the first AIoT service, which helps to ensure the continuity of the first AIoT service and thus ensure the user service experience.

[0052] In conjunction with the eighth aspect, in one implementation, the tenth message further includes third information, which is used to determine the first carrier configuration information; the eleventh message further includes fourth information, which is the first carrier configuration information.

[0053] Based on the above method, in the scenario where the terminal switches to the first access network device, the terminal can send third information for configuring the first resource to the first access network device, so that the first access network device can configure the carrier for the terminal according to the received third information, which helps to ensure the continuity of the first AIoT service and thus ensure the user service experience.

[0054] Ninthly, embodiments of this application provide a communication method that can be applied to a first access network device side, such as the first access network device, modules (e.g., circuits, chips or chip systems (e.g., modem chips, or SoC chips or SIP chips containing modem cores) in the first access network device, or logical nodes, logical modules or software that can implement all or part of the first access network device.

[0055] The method includes: after sending a twelfth message, receiving a tenth message from a terminal, the twelfth message being used to switch the terminal to the first access network device, the tenth message including first information, the first information being used to determine a first resource, the first resource being used by the terminal to execute a first A-IoT service; determining second information based on the first information, the second information indicating the first resource; and sending an eleventh message to the terminal, the eleventh message including the second information.

[0056] Based on the above method, in the scenario where the terminal switches to the first access network device, the first access network device can receive first information from the terminal for configuring the first resource, and configure the first resource for the terminal according to the received first information, so that the terminal can use the first resource to continue to execute the first AIoT service, which helps to ensure the continuity of the first AIoT service and thus ensure the user service experience.

[0057] In conjunction with the ninth aspect, in one implementation, the tenth message further includes third information, which is used to determine the first carrier configuration information; the eleventh message further includes fourth information, which is the first carrier configuration information.

[0058] Based on the above method, in the scenario where the terminal switches to the first access network device, the first access network device can receive third information from the terminal for configuring the carrier, and configure the carrier for the terminal according to the received third information, which helps to ensure the continuity of the first AIoT service and thus ensure the user service experience.

[0059] In a tenth aspect, embodiments of this application provide a communication method that can be applied to a first access network device, such as the first access network device, modules (e.g., circuits, chips, or chip systems (e.g., modem chips, or SoC chips or SIP chips containing modem cores) in the first access network device, or logical nodes, logical modules, or software that can implement all or part of the first access network device.

[0060] The method includes: receiving a thirteenth message from a second access network device, the thirteenth message including first information, the first information determining the configuration of a first resource, the first resource being used by a terminal to execute a first environment Internet of Things (A-IoT) service; determining second information based on the first information, the second information indicating the first resource; and sending a fourteenth message to the terminal, the fourteenth message being used to rebuild or restore the terminal's RRC connection, the fourteenth message including the second information.

[0061] Based on the above method, for RLF scenarios or scenarios where the terminal is in an inactive state, the first access network device can receive first information from the second access network device for configuring the first resource, and configure the first resource for the terminal according to the received first information, so that the terminal can use the first resource to continue to execute the first AIoT service, which helps to ensure the continuity of the first AIoT service and thus ensure the user service experience.

[0062] In conjunction with aspect ten, in one implementation, the thirteenth message further includes third information, which is used to determine the first carrier configuration information; the fourteenth message further includes fourth information, which is the first carrier configuration information.

[0063] Based on the above method, for RLF scenarios or scenarios where the terminal is in an inactive state, the first access network device can receive third information from the second access network device for configuring the carrier, and configure the carrier for the terminal according to the received third information, which helps to ensure the continuity of the first AIoT service and thus ensure the user's service experience.

[0064] Eleventhly, embodiments of this application provide a communication method that can be applied to a second access network device, such as a second access network device, a module (e.g., a circuit, chip, or chip system (e.g., a modem chip, or a SoC chip or SIP chip containing a modem core) in the second access network device, or a logical node, logical module, or software that can implement all or part of the first access network device.

[0065] The method includes: sending a thirteenth message to a first access network device, the thirteenth message including first information, the first information being used to determine a first resource, the first resource being used by the terminal to execute a first A-IoT service.

[0066] Based on the above method, for RLF scenarios or scenarios where the terminal is in an inactive state, the second access network device can send first information for configuring the first resource to the first access network device, so that the first access network device can configure the first resource for the terminal according to the received first information, so that the terminal can use the first resource to continue to execute the first AIoT service, which helps to ensure the continuity of the first AIoT service and thus ensure the user service experience.

[0067] In conjunction with the eleventh aspect, in one implementation, the method further includes: receiving a fifteenth message from the terminal, the fifteenth message including the first information.

[0068] Based on the above method, in scenarios involving RLF or when the terminal is in an inactive state, the second access network device can receive third information from the terminal. For example, in Scheme 2 (NAS-based scheme) and Scheme 3 (UP-based scheme) of Topology 2, the second access network device can receive third information from the terminal.

[0069] In conjunction with the eleventh aspect or any of its implementations, in another implementation, the thirteenth message further includes third information, which is used to determine the first carrier configuration information; the fourteenth message further includes fourth information, which is the first carrier configuration information.

[0070] Based on the above method, for RLF scenarios or scenarios where the terminal is in an inactive state, the second access network device can send third information for configuring the carrier to the first access network device, so that the first access network device can configure the carrier for the terminal according to the received third information, which helps to ensure the continuity of the first AIoT service and thus ensure the user service experience.

[0071] In combination with any of the above aspects or implementation methods, in another implementation method, the first information includes at least one of the following: fifth information, the fifth information indicating the number of first devices associated with the first A-IoT service; sixth information, the sixth information indicating the latency associated with the first A-IoT service; seventh information, the seventh information indicating that the first A-IoT service is associated with one first device or indicating that the first A-IoT service is associated with multiple first devices; the frequency band supported by the first device associated with the first A-IoT service; the period for executing the first A-IoT service; the type of the first A-IoT service; the size of the data reported by the first device associated with the first A-IoT service; or the number of identification information of the first device associated with the first A-IoT service.

[0072] In combination with any of the above aspects or implementation methods, in another implementation method, the number of first devices related to the first A-IoT service includes at least one of the following: the number of first devices that did not perform the first A-IoT service when the connection between the terminal and the second access network device was disconnected; the number of first devices that performed the first A-IoT service while the terminal was connected to the second access network device; or the number of first devices related to the first A-IoT service.

[0073] In combination with any of the above aspects or implementation methods, in another implementation method, the latency related to the first A-IoT service includes at least one of the following: the remaining latency of the first A-IoT service when the connection between the terminal and the second access network device is disconnected; the duration of executing the first A-IoT service while the terminal is accessing the second access network device; or the latency of the first A-IoT service.

[0074] In combination with any of the above aspects or any of the implementation methods, in another implementation method, the third information includes at least one of the following: the capabilities of the first device related to the first A-IoT service; or the type of the first device related to the first A-IoT service.

[0075] In combination with any of the above aspects or any of the implementation methods, in another implementation method, the capability includes at least one of the following: reflection capability, energy storage capability, signal amplification capability, or signal generation capability; and / or, the type includes at least one of the following: device 1, device 2a, device 2b, device A, device B, or device C.

[0076] In another implementation, combining any of the above aspects or implementation methods, the third information further includes second carrier configuration information.

[0077] In combination with any of the above aspects or any of the implementation methods, in another implementation method, the fourth information includes at least one of the following: transmission power, transmission start time, transmission end time, transmission period, duration, first region, or frequency domain resources, wherein the first region includes the region of the transmission carrier and / or the region related to the first A-IoT service.

[0078] In a twelfth aspect, embodiments of this application provide a communication method that can be applied to a terminal side, such as a terminal, a module (e.g., a circuit, a chip or chip system (e.g., a modem chip, or a SoC chip or SIP chip containing a modem core), or a logical node, logical module, or software that can implement all or part of the terminal.

[0079] The method includes: determining that a first resource has failed, the first resource being used by the terminal to execute a first A-IoT service; and sending a ninth message to a first device related to the first A-IoT service, the ninth message indicating the time for stopping monitoring of A-IoT interface signaling.

[0080] Based on the above method, in the event of the failure of the first resource, the terminal can send a ninth message to the first device to indicate the time for stopping the monitoring of A-IoT interface signaling, so that the first device stops monitoring A-IoT interface signaling in the event of the failure of the first resource, which helps to reduce the power loss of the first device.

[0081] In conjunction with the twelfth aspect, in one implementation, determining that the first resource has failed includes: determining that the first resource has failed when at least one of the following conditions is met: the first timer corresponding to the first resource times out, or the duration of the first resource expires.

[0082] In conjunction with the twelfth aspect or any of its implementations, in another implementation, the ninth information includes at least one of the following: a second timer, a first duration, or a periodic mode, wherein a period of the periodic mode includes a second duration and a third duration, and the time for stopping monitoring the signaling of the terminal is: during the operation of the second timer, within the first duration, or within one or more second durations.

[0083] In a thirteenth aspect, embodiments of this application provide a communication method that can be applied to a first device, such as the first device, modules (e.g., circuits, chips, or chip systems (e.g., modem chips, or SoC chips or SIP chips containing modem cores) within the first device, or logical nodes, logical modules, or software that can implement all or part of the first device. For example, the first device may be an A-IoT device.

[0084] The method includes: receiving a ninth message from a terminal, the ninth message indicating the time for monitoring A-IoT interface signaling; and stopping monitoring A-IoT interface signaling within the time period according to the ninth message.

[0085] Based on the above method, in the event of failure of the first resource, the first device can stop monitoring A-IoT interface signaling according to the terminal's instructions, which helps to reduce the power loss of the first device.

[0086] In conjunction with aspect thirteen, the ninth information includes at least one of the following: a second timer, a first duration, or a periodic mode, wherein a period of the periodic mode includes a second duration and a third duration, and the time for stopping monitoring the signaling of the terminal is: during the operation of the second timer, within the first duration, or within one or more second durations.

[0087] In conjunction with aspect thirteen or any implementation thereof, in another implementation, after the said time, the first device resumes monitoring A-IoT interface signaling.

[0088] In conjunction with aspect thirteen or any of its implementations, in another implementation, the start time of the time is the time when the first device receives the ninth information.

[0089] In a fourteenth aspect, a communication apparatus is provided for performing the method provided by any of the above aspects or their implementations. Specifically, the apparatus may include modules, units, or means for performing the method provided by any of the above aspects or their implementations, such as a processing unit and / or a communication unit. These modules, units, or means may be implemented in software, in hardware, or in a combination of software and hardware.

[0090] In one implementation, when the device is a first access network device, a second access network device, a terminal, or a first device, the communication unit can be a transceiver, or an input / output interface, or a communication interface; the processing unit can be at least one processor. Optionally, the transceiver is a transceiver circuit. Optionally, the input / output interface is an input / output circuit.

[0091] In another implementation, the device is a chip, chip system, or circuit used in a first access network device, a second access network device, a terminal, or a first device. When the device is a chip, chip system, or circuit used in a first access network device, a second access network device, a terminal, or a first device, the communication unit may be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip, chip system, or circuit; the processing unit may be at least one processor, processing circuit, or logic circuit.

[0092] When the method provided in this application is executed by a chip, this application does not limit the specific number of chips implementing the method. For example, it can be executed by one chip, or by two or more chips. Furthermore, when the number of chips implementing the method is two or more, the chip manufacturers are not limited; they can be from the same manufacturer or different manufacturers.

[0093] In a fifteenth aspect, a communication apparatus is provided, comprising: at least one processor configured to acquire, via a communication interface, a computer program or instructions stored in a memory to execute the method provided in any of the foregoing aspects or their implementations.

[0094] Optionally, the device also includes a communication interface. This communication interface can be implemented in hardware or software.

[0095] Optionally, the device also includes the memory.

[0096] In one implementation, the device is a first access network device, a second access network device, a terminal, or a first device.

[0097] In another implementation, the device is a chip, chip system, or circuit used in a first access network device, a second access network device, a terminal, or a first device.

[0098] When the method provided in this application is executed by a chip, this application does not limit the specific number of chips implementing the method. For example, it can be executed by one chip, or by two or more chips. Furthermore, when the number of chips implementing the method is two or more, the chip manufacturers are not limited; they can be from the same manufacturer or different manufacturers.

[0099] In a sixteenth aspect, a processor is provided for executing the methods provided by any of the foregoing aspects or their implementations.

[0100] Unless otherwise specified, or if it does not contradict its actual function or internal logic in the relevant description, the transmission and acquisition / reception operations involved in the processor can be understood as processor output and reception, input and other operations, or as transmission and reception operations performed by radio frequency circuits and antennas. This application does not limit them in this regard.

[0101] In a seventeenth aspect, a computer-readable storage medium is provided that stores program code for execution by a device, the program code including methods for performing any of the foregoing aspects or implementations thereof.

[0102] In an eighteenth aspect, a computer program product containing instructions is provided, which, when run on a computer, causes the computer to perform the method provided in any of the foregoing aspects or their implementations.

[0103] In a nineteenth aspect, a communication system is provided, comprising at least one of the aforementioned first access network device, second access network device, terminal, or first device.

[0104] In a twentieth aspect, a computer program is provided that, when run on a computer, causes the methods provided by any of the foregoing aspects or their implementations to be executed. Attached Figure Description

[0105] Figure 1 is a schematic diagram of a radio-frequency identification (RFID) system.

[0106] Figure 2 is a schematic diagram of topology 1.

[0107] Figure 3 is a schematic diagram of topology 2.

[0108] Figure 4 is a schematic diagram of topology 3 (I).

[0109] Figure 5 is a schematic diagram of topology 3 (II).

[0110] Figure 6 is a schematic diagram of topology 4.

[0111] Figure 7 is a schematic diagram of the logical system architecture of Topology 2.

[0112] Figure 8 is a schematic diagram of the protocol stack involved in an embodiment of this application.

[0113] Figure 9 is a schematic diagram of the direct connection between a next-generation NodeB (gNB) supporting A-IoT and the A-IoT core network (CN).

[0114] Figure 10 is a schematic diagram of a non-direct connection between a gNB that supports A-IoT and an A-IoT CN.

[0115] Figure 11 is another schematic diagram of the protocol stack involved in the embodiments of this application.

[0116] Figure 12 is another schematic diagram of the protocol stack involved in the embodiments of this application.

[0117] Figure 13 is a schematic diagram of a network architecture applicable to embodiments of this application.

[0118] Figure 14 is an example diagram of an open access network system.

[0119] Figure 15 is a diagram showing the functional division of network elements and the protocol layer structure of an open access network device.

[0120] Figure 16 is a schematic diagram of a protocol stack applicable to an embodiment of this application.

[0121] Figure 17 is another schematic diagram of the protocol stack applicable to an embodiment of this application.

[0122] Figure 18 is a schematic flowchart of a communication method 1800 provided in an embodiment of this application.

[0123] Figure 19 is a schematic flowchart of a communication method 1900 provided in an embodiment of this application.

[0124] Figure 20 is a schematic flowchart of a communication method 2000 provided in an embodiment of this application.

[0125] Figure 21 is a schematic flowchart of a communication method 2100 provided in an embodiment of this application.

[0126] Figure 22 is a schematic flowchart of a communication method 2200 provided in an embodiment of this application.

[0127] Figure 23 is a schematic flowchart of a communication method 2300 provided in an embodiment of this application.

[0128] Figure 24 is a schematic flowchart of a communication method 2400 provided in an embodiment of this application.

[0129] Figure 25 is a schematic flowchart of a communication method 2500 provided in an embodiment of this application.

[0130] Figure 26 is a schematic flowchart of a communication method 2600 provided in an embodiment of this application.

[0131] Figure 27 is a schematic flowchart of a communication method 2700 provided in an embodiment of this application.

[0132] Figure 28 is a schematic flowchart of a communication method 2800 provided in an embodiment of this application.

[0133] Figure 29 is a schematic flowchart of a communication method 2900 provided in an embodiment of this application.

[0134] Figure 30 is a schematic flowchart of a communication method 3000 provided in an embodiment of this application.

[0135] Figure 31 is a schematic flowchart of a communication method 3100 provided in an embodiment of this application.

[0136] Figure 32 is a schematic flowchart of a communication method 3200 provided in an embodiment of this application.

[0137] Figure 33 is a schematic diagram of a device provided in an embodiment of this application.

[0138] Figure 34 is another structural schematic diagram of the device provided in an embodiment of this application.

[0139] Figure 35 is a schematic diagram of a chip system provided in an embodiment of this application. Detailed Implementation

[0140] To facilitate understanding of the embodiments of this application, the following points will be explained before introducing the embodiments of this application.

[0141] "System" and "network" can be used interchangeably. "At least one" refers to one or more, and "multiple" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, "at least one of A, B, or C" includes A, B, C, AB, AC, BC, or ABC. "At least one of A, B, and C" can also be understood as including A, B, C, AB, AC, BC, or ABC, where A, B, and C can be single or multiple. And, unless otherwise specified, the ordinal numbers such as "first" and "second" mentioned in the embodiments of this application are used to distinguish multiple objects and are not used to limit the order, sequence, priority, or importance of multiple objects. The term "protocol" may refer to standard protocols in the field of communications, such as the Long Term Evolution (LTE) protocol, the New Radio (NR) protocol, and related protocols applied to future communication systems; this application does not limit this. Words such as "exemplary," "for example," "exemplarily," and "as (another) example" are used to indicate that something is being described as an example, illustration, or description. Any embodiment or design described as "exemplary" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. The terms "comprising," "including," "having," and variations thereof all mean "including but not limited to," unless otherwise specifically emphasized.

[0142] In this application, "sending information" can be understood as one device sending information to another device, or as one logic module within a device sending information to another logic module. For example, "device Q sending information" can be understood as device Q sending information to another device, or as logic module 1 in device Q sending information to logic module 2 in device Q. Similarly, "receiving information" can be understood as one device receiving information from another device, or as one logic module within a device receiving information from another logic module. For example, "device Q receiving information" can be understood as device Q receiving information from another device, or as logic module 1 in device Q receiving information from logic module 2 in device Q. The phrase "sending information to…device Q" in this application, or the related illustrations in the accompanying drawings, can be understood as the destination of the information being device Q. This can include sending information directly or indirectly to device Q. The phrases "receiving information from... (e.g., device Q)," "receiving information from... (e.g., device Q)," or "receiving information sent by (e.g., device Q)," or the related illustrations in the accompanying drawings, can be understood as indicating that the source of the information is device Q, which may include receiving information directly or indirectly from device Q. The 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 understood in a similar way and will not be repeated here. In the embodiments of this application, the term "wireless communication" can also be simply referred to as "communication," and the term "communication" can also be described as "data transmission," "information transmission," or "transmission."

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

[0144] To facilitate understanding of the embodiments of this application, some concepts or terms involved in the embodiments of this application will be briefly explained.

[0145] The concepts and terms described below are based on those specified in the agreement, but do not imply that the embodiments of this application can only be applied to existing systems. The concepts and terms involved in the embodiments of this application can be applied to future systems. Furthermore, the specific names of the concepts or terms (e.g., concepts or terms related to functional descriptions) may be adjusted as future systems develop.

[0146] 1. Environmental Internet of Things (A-IoT)

[0147] With the increasing prevalence of machine-type communication (MTC) and Internet of Things (IoT) communication, the number of connected IoT devices is growing daily. Therefore, the industry's demand for reduced cost and power consumption in IoT devices is becoming increasingly strong. The 3rd Generation Partnership Project (3GPP) introduced narrowband IoT (NB-IoT) systems. However, NB-IoT terminal devices require external power (such as batteries) and the ability to generate local high-frequency local oscillator carriers; these terminal devices can achieve power consumption down to the milliwatt level. But with the evolution and development of IoT, in the 5G... th The demand for lower-power terminal devices in 5G networks is increasing. Radio frequency identification (RFID) technology provides a good technical reference for low power consumption, supporting microwatt-level power consumption. An RFID system typically includes an RFID reader (or interrogator) and RFID devices (such as tags). The RFID reader can interact with the RFID device for management. The RFID device can use a low-precision, low-power mid-to-low frequency ring oscillator or receive downlink signals without a local oscillator. When the RFID device is operating, the energy and carrier wave for communication are supplied by the reader, and communication is based on a reflected carrier wave. Figure 1 is a schematic diagram of an RFID system. As shown in Figure 1, the line pointing to the right represents the carrier wave transmitted by the RFID reader, and the line pointing to the left represents the RFID device modulating and reflecting the carrier wave transmitted by the RFID reader for transmission.

[0148] Given the low power consumption advantage of RFID technology, ambient IoT (A-IoT) has emerged in 5G environments. To meet ultra-low power consumption requirements, devices in A-IoT 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 can further reduce the power consumption of the terminal's downlink reception. However, for such low-power receiving methods, only amplitude detection, such as envelope detection, is possible because low-precision ring oscillators cannot guarantee accurate demodulation of signal phase information.

[0149] A-IoT is an extremely low-power, low-complexity Internet of Things (IoT) technology defined by 3GPP. It can be understood as an extension of RFID technology within 3GPP. A-IoT and RFID share some principles, such as similar inventory management processes, but 3GPP introduces more value-added scenarios.

[0150] A-IoT, based on cellular network communication infrastructure, consists of readers and passive / semi-passive / active A-IoT devices. The reader can be a network device or a terminal, and the A-IoT device can be a terminal within the cellular network, specifically an extremely low-power, extremely low-complexity IoT terminal. For example, A-IoT can include network devices and a first-type terminal; or, a communication system based on A-IoT technology includes network devices and a first-type terminal. The first-type terminal can be a device with A-IoT device functionality. In this case, both the reader and the A-IoT device can be implemented based on the cellular network infrastructure. In other words, both the reader and the A-IoT device can be devices within the cellular network. For example, the reader's functionality can be implemented by a network device, such as a base station. Alternatively, the reader's functionality can be implemented by a terminal. The A-IoT device can be implemented by a terminal within the cellular network, such as an extremely low-power, extremely low-complexity IoT terminal, i.e., a first-type terminal. The network device and the first-type terminal can perform contactless data communication, thereby reading information from the first-type terminal and / or writing information that needs to be stored into the first-type terminal.

[0151] 2. Application Scenarios of A-IoT

[0152] Typical applications of A-IoT include logistics, warehousing, industrial manufacturing, identity recognition, and environmental monitoring.

[0153] 3. A-IoT business

[0154] The main business of A-IoT includes one or more of the following: inventory, positioning, sensing, or command.

[0155] For example, the inventory management service utilizes readers (such as base stations or terminals) to access A-IoT devices within the coverage area. Successfully connected A-IoT devices need to send their unique identifiers to the reader. This inventory management service, also known as a check-in operation, obtains the identification information of A-IoT devices.

[0156] For example, location services use some location signals to locate the position of A-IoT devices.

[0157] For example, sensing services involve A-IoT devices reporting sensing data (such as temperature data) to readers (such as base stations or terminals).

[0158] For example, a command service can be one that operates an A-IoT device through a series of operational instructions. For example, a command service can include at least one of the following services:

[0159] 1) Read service: It can read the electronic product code (EPC), tag identifier (TID) in the storage area of ​​the A-IoT device, the content stored in the reserved area of ​​the A-IoT device, or the content stored in the user storage area of ​​the A-IoT device.

[0160] 2) Write service: It can perform write operations on the storage area of ​​A-IoT devices. That is, the reader (such as a base station or terminal) sends a downlink command and data to instruct the A-IoT device to write the data into the storage area.

[0161] 3) Disable service: You can request that A-IoT devices permanently or temporarily disable their radio frequency (RF) transmission capabilities.

[0162] 4) Enable service: You can request to enable A-IoT devices that have been temporarily disabled.

[0163] 5) Kill Service: This service can make A-IoT devices permanently unusable.

[0164] 6) Locking service: It can lock the information of A-IoT devices to prevent read or write operations on the A-IoT devices, or it can lock the storage area to prevent read or write operations on the storage area.

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

[0166] 4. Types of A-IoT devices

[0167] A-IoT devices can be divided into three categories: device A, device B, and device C.

[0168] Device A: Similar to a passive tag, it has no energy storage, cannot generate signals independently, and uses backscattering to transmit signals.

[0169] Device B: Similar to a semi-passive tag, it has energy storage but cannot generate signals independently. It uses backscatter to transmit signals, and its stored energy can amplify the reflected signals.

[0170] Device C: Similar to an active tag, it has energy storage, can generate signals independently, and has active radio frequency components for transmission.

[0171] In addition, 3GPP has further defined the following three types of A-IoT devices: device 1, device 2a, and device 2b.

[0172] Device 1: ~1μW peak power consumption, with energy storage function, and initial sampling frequency offset (SFO) of 10. X The ppm signal cannot amplify downlink (DL) or uplink (UL) signals. It needs to obtain a carrier signal from an external source for backscatter communication in order to perform uplink transmission.

[0173] Device 2a: Peak power consumption less than or equal to several hundred μW, with energy storage function, and initial SFO reaching 10. X ppm, X can be, for example, 4 or 5, and can perform DL and / or UL signal amplification. It needs to obtain a carrier signal from the outside for backscatter communication in order to perform uplink transmission.

[0174] Device 2b: Peak power consumption less than or equal to several hundred μW, with energy storage function, and initial SFO reaching 10. X ppm, X can be, for example, 4 or 5, and DL and / or UL signal amplification can be performed. The device can perform uplink transmission without relying on an externally provided carrier.

[0175] 5. A-IoT Topology

[0176] In the discussion of A-IoT, the following topologies exist.

[0177] 1) Topology 1: Figure 2 is a schematic diagram of Topology 1. Topology 1 adopts a direct connection architecture, where A-IoT devices and network devices communicate directly and bidirectionally. Communication between network devices and A-IoT devices includes environmental IoT data and / or signaling. The network device sending environmental IoT data and / or signaling to the A-IoT device and the network device receiving environmental IoT data and / or signaling from the A-IoT device can be the same network device or different network devices.

[0178] 2) Topology 2: Figure 3 shows a schematic diagram of Topology 2. Topology 2 adopts a relay architecture. A-IoT devices communicate with network devices through intermediate nodes. In other words, there is bidirectional communication between A-IoT devices and intermediate nodes, and bidirectional communication between intermediate nodes and network devices. Intermediate nodes transmit environmental IoT data and / or signaling between network devices and A-IoT devices. Intermediate nodes can be A-IoT-enabled relays, integrated access and backhaul (IAB) nodes, user equipment (UE), repeaters, etc. Intermediate nodes act as readers / writers to perform A-IoT services.

[0179] 3) Topology 3: Figures 4 and 5 illustrate Topology 3. In Topology 3, A-IoT devices send environmental IoT data and / or signaling to network devices and receive environmental IoT data and / or signaling from assisting nodes; A-IoT devices receive environmental IoT data and / or signaling from network devices and send environmental IoT data and / or signaling to assisting nodes. In this topology, assisting nodes can be A-IoT-enabled repeaters, IAB nodes, UEs, repeaters, etc.

[0180] 4) Topology 4: Figure 6 is a schematic diagram of Topology 4. In Topology 4, the A-IoT device and the UE communicate bidirectionally. The communication between the UE and the A-IoT device includes environmental IoT data and / or signaling.

[0181] The embodiments of this application mainly relate to topology 2, which will be described in detail below.

[0182] Figure 7 is a schematic diagram of the logical system architecture of Topology 2.

[0183] As shown in Figure 7, in Topology 2, the interface between the A-IoT-enabled gNB and the A-IoT core network (CN) is an NG interface. The A-IoT-enabled UE and A-IoT devices communicate via the A-IoT interface (such as the A-IoT radio interface). The A-IoT-enabled gNB includes the A-IoT RAN node function, and the A-IoT-enabled UE includes the common reader function. The A-IoT RAN node function includes the ability to control / allocate / schedule A-IoT radio resources, while the common reader function refers to the ability to communicate with A-IoT devices through the A-IoT interface.

[0184] In topology 2, access network devices can send access control information to intermediate nodes (such as UEreaders) to instruct / control the intermediate nodes (such as UEreaders) to access the cell / base station. The access control information can be sent in system messages (such as system information blocks (SIBs) and master information blocks (MIBs).

[0185] 6. Three schemes for Topology 2

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

[0187] 1) Solution 1: RRC-based solution

[0188] The basic idea is as follows: After the base station receives a request related to A-IoT services from the A-IoT CN via XXAP, the base station further sends the relevant information to the A-IoT-enabled UE via RRC messages. When the base station receives A-IoT service-related data / signaling from the A-IoT-enabled UE via RRC, the base station transmits the relevant information to the A-IoT CN via XXAP / Next Generation Application Protocol (NGAP).

[0189] One possible protocol stack is shown in Figure 8. Here, the XX interface is the next-generation (NG) control plane (NG-C) interface. One possible implementation of XXAP is to include ambient IoT function (A-IoTF) information / cells in NGAP; another possible implementation is to carry a newly defined protocol layer on top of the NGAP protocol.

[0190] For RRC-based solutions, there are two scenarios supporting A-IoT: direct connection and indirect connection (e.g., an indirect path via AMF). A direct connection between the A-IoT-enabled gNB and A-IoT CN is illustrated in Figure 9, where A-IoTF can be replaced by A-IoT CN, and Nx / XX represents the NG interface. An indirect connection between the A-IoT-enabled gNB and A-IoT CN is illustrated in Figure 10, where A-IoTF can be replaced by A-IoT CN, and the A-IoT data and / or signaling transmitted between the A-IoTF and A-IoT-enabled gNB is carried on the NGAP.

[0191] 2) Solution 2: NAS-based solution

[0192] The basic idea is that the base station cannot see the A-IoT related processes. The A-IoT CN and the A-IoT-enabled UE transmit A-IoT related data / signaling through the DL / UL NAS packets of the A-IoT-enabled UE (that is, the A-IoT-enabled gNB transparently transmits the A-IoT related data / signaling sent to and from the A-IoT-enabled UE). The base station can use the DL NAS transport process and the UL NAS transport process on the NGAP to process the DL / UL NAS packets of the A-IoT-enabled UE.

[0193] One possible protocol stack is shown in Figure 11.

[0194] 3) Solution 3: UP-based solution

[0195] The basic idea is that the base station can not see the A-IoT related processes. The A-IoT service-related data / signaling between the A-IoT CN and the A-IoT-enabled UE is transmitted on the PDU session of the A-IoT-enabled UE (that is, the A-IoT-enabled gNB transparently transmits the A-IoT related data / signaling sent to and from the A-IoT-enabled UE). The gNB processes the user plane data of the A-IoT-enabled UE through the NG control plane (NG-U) interface general packet radio service (GPRS) tunneling protocol user plane (GTP-U) channel.

[0196] One possible protocol stack is shown in Figure 12.

[0197] 7. The three states of RRC

[0198] RRC Connected State: The UE and the access network device have established or have an RRC connection.

[0199] RRC inactive state: In this state, the UE suspends data processing, but the access network equipment still maintains the UE's context information. Simply put, the air interface state of a UE in RRC inactive state is similar to that in RRC idle state, but from the core network side, the UE in RRC inactive state is still in the connection management (CM) connected state.

[0200] RRC Idle: In this state, the UE and the access network equipment have not established an RRC connection.

[0201] As described above, the terminal can act as a reader / writer to perform A-IoT services. When the terminal acts as a reader / writer to perform A-IoT services, the access network device can send access control information to the terminal to instruct / control the terminal to access the cell / base station. Optionally, the access control information can be sent in system messages (such as SIB, MIB). Due to the mobility of the terminal, it may experience temporary out-of-connection situations, such as cell handover, cell selection, cell reselection, or radio link failure (RLF). In such cases, the continuity of A-IoT services cannot be guaranteed.

[0202] To address the aforementioned problems, this application provides a communication method and apparatus. When a UE temporarily loses network connectivity, a second access network device can provide a first access network device with information for configuring A-IoT resources and / or information for configuring carrier wave (CW), or a terminal acting as a reader / writer can report information for configuring A-IoT resources and / or information for configuring carrier wave (CW) to the first access network device. This allows the first access network device to configure the device based on the received information, thereby ensuring the continuity of A-IoT services. Embodiments of this application are described below with reference to the accompanying drawings.

[0203] First, this application describes a communication system to which embodiments of this application can be applied.

[0204] The embodiments of this application can be applied to various communication systems, including but not limited to: 5th generation (5G) systems or NR systems, LTE systems, long term evolution-advanced (LTE-A) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, etc. They can also be applied to future communication systems. Furthermore, they can be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, long term evolution-vehicle (LTE-V) communication, long term evolution-machine (LTE-M) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), Internet of Things (IoT) communication systems, narrow band Internet of Things (NB-IoT), ambient Internet of Things (A-IoT), or other communication systems. The embodiments of this application can also be applied to satellite communication systems, high altitude platform station (HAPS) communication, unmanned aerial vehicles (UAVs) and other non-terrestrial network (NTN) systems, such as integrated communication and navigation (ICAN) systems, global navigation satellite systems (GNSS) and ultra-dense low-Earth orbit satellite communication systems.Furthermore, it can be extended to similar wireless communication systems, such as wireless local area networks (WLAN), wireless-fidelity (WiFi), worldwide interoperability for microwave access (WIMAX), and other communication systems related to the 3rd generation partnership project (3GPP).

[0205] The communication system applicable to embodiments of this application may include one or more transmitting devices and one or more receiving devices. Optionally, one of the transmitting device and the receiving device may be a terminal, and the other may be a network device. Optionally, both the transmitting device and the receiving device may be terminals. Optionally, both the transmitting device and the receiving device may be network devices.

[0206] For example, Figure 13 shows a schematic diagram of a network architecture to which embodiments of this application may be applied.

[0207] Figure 13 illustrates a possible, non-limiting system diagram. As shown in Figure 13, the communication system 1000 includes a radio access network (RAN) 100 and a core network (CN) 200. RAN 100 includes at least one RAN node (110a and 110b in Figure 13, collectively referred to as 110) and at least one terminal (120a-120j in Figure 13, collectively referred to as 120). RAN 100 may also include other RAN nodes, such as wireless relay equipment and / or wireless backhaul equipment (not shown in Figure 13). Terminal 120 is wirelessly connected to RAN node 110. RAN node 110 is wirelessly or wired connected to core network 200. The core network equipment in core network 200 and RAN node 110 in RAN 100 can be different physical devices, or they can be the same physical device integrating core network logical functions and radio access network logical functions.

[0208] A terminal can be a device or module that accesses the aforementioned communication system and has corresponding communication functions. A terminal can also be called a terminal device, user equipment (UE), mobile station, mobile terminal, etc. Terminals can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, etc. Terminals can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, transportation vehicles with wireless communication capabilities, communication modules, etc. The embodiments of this application do not limit the device form of the terminal. A terminal typically contains a communication module, circuit, or chip that performs the corresponding communication function. The terminal can also be configured with program instructions for performing the corresponding communication function.

[0209] RAN 100 can be a 3GPP-related cellular system, such as a 4G, 5G mobile communication system, or a future-oriented evolution system. RAN 100 can also be an open access network (O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi) system. RAN 100 can also be a communication system that integrates two or more of the above systems.

[0210] RAN node 110, sometimes also referred to as access network equipment, network equipment, RAN entity, or access node, constitutes part of the communication system and is used to help terminals achieve wireless access. Multiple RAN nodes 110 in communication system 10 can be of the same type or different types. In some scenarios, the roles of RAN node 110 and terminal 120 are relative. For example, network element 120i in Figure 13 can be a helicopter or drone, which can be configured as a mobile base station. For terminals 120j accessing RAN 100 through network element 120i, network element 120i is a base station; but for base station 110a, network element 120i is a terminal. RAN node 110 and terminal 120 are sometimes both referred to as communication devices. For example, network elements 110a and 110b in Figure 13 can be understood as communication devices with base station functions, and network elements 120a-120j can be understood as communication devices with terminal functions.

[0211] In one possible scenario, the RAN node can be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a gNB, a base station in a future mobile communication system, or an access node in a WiFi system. The RAN node can be a macro base station (as shown in Figure 13, 110a), a micro base station or indoor station (as shown in Figure 13, 110b), a relay node or donor node, or a radio controller in a CRAN scenario. Optionally, the RAN node can also be a server, wearable device, vehicle, or in-vehicle equipment. For example, the access network equipment in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). All or part of the functions of the RAN node in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (e.g., a cloud platform). The RAN node can also be equipped with communication modules, circuits, or chips that perform corresponding communication functions. The RAN node can also be configured with program instructions for performing corresponding communication functions and corresponding program instructions. The RAN node in this application can also be a logical node, logical module, or software that can implement all or part of the functions of the RAN node.

[0212] In another possible scenario, multiple RAN nodes collaborate to assist the terminal in achieving wireless access, with each RAN node performing a portion of the base station's functions. For example, RAN nodes can be central units (CUs), distributed units (DUs), CU-control plane (CPs), CU-user plane (UPs), or radio units (RUs), etc. CUs and DUs can be separate entities or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs).

[0213] It should be understood that multiple RAN nodes collaborate to assist the terminal in achieving wireless access. After receiving an XXAP / NGAP message from the CN, the CU forwards the XXAP / NGAP message to the DU via an F1AP message, or sends the AIoT information contained in the XXAP / NGAP message to the DU via an F1AP message. After receiving an RRC message from the UE, the DU forwards the RRC message to the CU via an F1AP message, or sends the AIoT information contained in the RRC message to the CU via an F1AP message. The XXAP / NGAP messages transmitted on the F1 interface and the XXAP / NGAP messages transmitted on the XX / NG interfaces can be different, meaning the CU can perform related processing on the messages, including deletion, filtering, mapping, modification, and adding auxiliary information.

[0214] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. 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 and hardware modules.

[0215] Figure 14 is an example diagram of an O-RAN system.

[0216] As shown in Figure 14, network devices are also called access network devices. Access network devices communicate with the core network via a backhaul link and with terminals via an air interface. Specifically, a BBU in the access network device communicates with the core network via a backhaul link, and an RU in the access network device communicates with at least one terminal device via an air interface. The BBU communicates with at least one RU via a fronthaul link. The BBU and RU may or may not be co-located. A BBU may include at least one CU and at least one DU, which can communicate via at least one midhaul link.

[0217] It should be understood that the O-RAN system may include components other than those shown in Figure 14.

[0218] Figure 15 shows the network element function division and protocol layer structure of an O-RAN device.

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

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

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

[0222] In some examples, the CU may not have a PDCP layer, i.e., it only includes the RRC layer. CU-CP does not have PDCP-C. CU-UP may not have PDCP-U, or may not have CU-UP at all. In some examples, the DU may not have an RLC layer, only a MAC and a higher PHY layer. Furthermore, in some examples, it may not have a CU and may only include the DU.

[0223] In some examples, the RU is a logical node that carries both lower physical layer (Lower PHY) and radio frequency (RF) processing. In some examples, the RU can be a 3GPP transmission reception point (TRP), a remote radio head (RRH), or other similar entities. In some examples, the Lower PHY includes PHY processing functions such as Fast Fourier Transform (FFT), Inverse Fast Fourier Transform (IFFT), digital beamforming, and filtering. The RU communicates with one or more terminal devices via a wireless link.

[0224] The DU and RU can be co-located or separate. The DU and RU exchange control plane and user plane information via a fronthaul link through a Lower-Layer Split CUS-Plane (LLS-CUS) interface. LLS-CUS may include LLS-C and LLS-U interfaces providing the control plane (C-Plane) and user plane (U-Plane), respectively. In some examples, the control plane (C-Plane) refers to real-time control between the DU and RU. The DU and RU exchange management information via an LLS-M interface on the fronthaul link; the management plane (M-Plane) refers to non-real-time management operations between the DU and RU. The DU and RU can cooperate to implement PHY layer functions. A DU can be connected to one or more RUs. The functions of the DU and RU can be configured in various ways depending on the design. For example, the DU may be configured to implement baseband functions, and the RU may be configured to implement mid-RF functions. For example, DU is configured to implement higher-level functions in the PHY layer, and RU is configured to implement lower-level functions in the PHY layer, or to implement both lower-level functions and RF functions. Higher-level functions in the physical layer may include a portion of the physical layer's functions that are closer to the MAC layer, while lower-level functions in the physical layer may include another portion of the physical layer's functions that are closer to the mid-RF side.

[0225] This application primarily relates to interface transmission between a reader / writer and a network (such as a RAN node). The reader / writer can be a RAN node, a terminal, a relay node, an IAB node, etc., but this application mainly concerns a solution where the terminal acts as the reader / writer. When the reader / writer is a terminal, communication between the terminal and the device can reuse the A-IoT Uu interface communication mechanism, with the terminal and RAN node communicating via the Uu air interface. As shown in Figures 16 and 17, the RAN node connects to the core network via NGAP, and the terminal communicates with the core network via NAS. The core network connected to the RAN node can be an AMF (Advanced Feature Function) or an A-IoT function (A-IoTF or A-IoTMF) related to A-IoT management. The RAN node can also communicate with the A-IoTF via the AMF, without limitation.

[0226] The device in this application mainly refers to an A-IoT device located within the coverage area provided by the reader. The A-IoT device can be an electronic tag, etc. An electronic tag can also be called a tag, RFID tag, etc. The A-IoT device in this application can also be considered a terminal. RFID can be divided into three types: active, passive, and semi-active. Correspondingly, tags can also be divided into passive tags (also called passive tags), semi-passive tags (also called semi-active tags), and active tags (also called active tags). Semi-passive tags and active tags use a backscatter-based communication method, while passive tags use an active carrier wave generation technology. Tag types can be classified based on whether they use a backscatter-based communication method, whether they have energy storage capabilities, or a combination of both. For specific classification methods, please refer to the terminology explanation section.

[0227] The reader / writer in this application can be a handheld or fixed device that reads (and sometimes writes) tag information, or it can be understood as a device that communicates with the tag. It can be a terminal, a base station, a device with read / write capabilities, an IAB node, or a relay node. This application mainly relates to solutions where a terminal is used as a reader / writer.

[0228] The core network equipment in this application includes core network elements for serving A-IoT devices. These network elements can be ambient IoT function (A-IoTF) or ambient IoT management function (A-IoTMF), access and mobility management function (AMF), session management function (SMF), or user plane function (UPF), etc.

[0229] Unless otherwise specified, the means for implementing the functions of the aforementioned devices or network elements in this application may refer to the devices or network elements themselves, or to means capable of supporting the implementation of the functions of the devices or network elements, such as a chip system or chip, specifically a SoC or modem, which may be installed in the devices or network elements. In the embodiments of this application, the chip system may be composed of chips, or may include chips and other discrete devices.

[0230] It should also be noted that some embodiments in this article use a 5G system as an example to introduce specific solution details. It is understood that when this solution is used in other communication systems, such as LTE systems, or future communication systems, the messages, channels, or information in the solution can be replaced with messages, channels, or information in other communication systems that can achieve the corresponding functions, and this application does not limit this.

[0231] The method embodiments of this application are described below with reference to the accompanying drawings.

[0232] It should be noted that the embodiments of this application are applicable to scenarios where the terminal temporarily loses its connection with the network due to its movement.

[0233] It should also be noted that the following description uses the interaction between a terminal (e.g., UE), a first access network device, a second access network device, and a core network element (e.g., AMF or A-IoTF) as an example to illustrate the method provided in the embodiments of this application. The terminal can be replaced by a component of the terminal (e.g., a chip, chip system, circuit, or communication module). The access network device can be replaced by a component of the access network device (e.g., a chip, chip system, circuit, or communication module). The core network element can be replaced by a component of the core network element (e.g., a chip, chip system, circuit, or communication module).

[0234] It should also be noted that the first access network device or the second access network device can refer to an A-IoT-enabled access network device, or an access network device that supports A-IoT, such as an A-IoT-enabled gNB. An A-IoT-enabled access network device may include the function of providing resource allocation, that is, an A-IoT-enabled access network device can allocate resources to the terminal to support communication between the terminal and the A-IoT device. The terminal can refer to an A-IoT-enabled terminal, or a terminal that supports A-IoT. In this application, the terminal can be called a UE reader, an A-IoT-enabled UE (such as an A-IoT-enabled UE), an intermediate node, or an intermediate terminal. That is, "Reader" can be replaced with "A-IoT-enabled UE," etc. An A-IoT-enabled terminal can act as a reader / writer to communicate with A-IoT devices.

[0235] It should also be noted that the devices referred to as the first access network device and the second access network device may differ depending on the scenario. For example, in a HO scenario, the first access network device can be the target access network device, such as the target gNB, and the second access network device can be the source access network device, such as the source gNB. As another example, in an RLF scenario, the first access network device can be a new access network device, such as a gNB, and the second access network device can be the last serving access network device, such as the last serving gNB. Yet another example is when the terminal is in a non-connected state (such as inactive or idle), the first access network device can be a receiving access network device (or access network device), such as the receiving gNB (or gNB), and the second access network device can be the last serving access network device, such as the last serving gNB.

[0236] It should be understood that the first access network device and the second access network device can be different or the same. For example, when a terminal switches from its original cell to a target cell, and the source cell and the target cell are cells under different access network devices, the first access network device and the second access network device are different. Another example is when a terminal discovers / declares an RLF and then performs cell selection or cell reselection, and the selected new cell and the original cell are cells under different access network devices; in this case, the first access network device and the second access network device are the same access network device. Yet another example is when a terminal switches from its source cell to a target cell under the same access network device; in this case, the first access network device and the second access network device are the same access network device. Yet another example is when a terminal discovers / declares an RLF and then performs cell selection or cell reselection, and it may select the original cell or another cell under the same access network device; in this case, the first access network device and the second access network device are the same access network device.

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

[0238] Figure 18 is a schematic flowchart of a communication method 1800 provided in an embodiment of this application.

[0239] Method 1800 describes a scheme for inter-site interaction, namely, a scheme in which a second access network device provides information for configuring A-IoT resources and / or information for configuring CW to a first access network device.

[0240] Method 1800 includes at least a portion of the following.

[0241] Step 1801: The second access network device sends first information to the first access network device, and correspondingly, the first access network device receives the first information from the second access network device.

[0242] The first information is used to configure, schedule, or determine the first resource for the terminal.

[0243] The first resource is used by the terminal to execute the first A-IoT service or for the terminal to communicate with the first device, such as an A-IoT resource. The first information is information that the first access network device can refer to when allocating the first resource. For example, the first resource may be an A-IoT radio resource, which may include time-domain resources and / or frequency-domain resources. The effective area of ​​the first resource may be a single cell or multiple cells. The resource configuration information of the first resource includes time-domain resource configuration information and / or frequency-domain resource configuration information. Optionally, the resource configuration information may also include the maximum power transmitted by the terminal to the A-IoT device. The time-domain resource configuration information may be a duration. If the terminal determines that the duration configured by the access network device is insufficient to complete the first A-IoT service, the terminal can request A-IoT resources (such as duration) from the access network device, and then the access network device will allocate or schedule A-IoT resources (such as duration) to the terminal.

[0244] The first piece of information can be information related to the first A-IoT business, including information derived from inference, such as the number of A-IoT devices not yet inventoried, remaining QoS requirements (e.g., remaining latency), etc.

[0245] In some implementations, the first information includes at least one of the following:

[0246] 1) Fifth Information

[0247] The fifth piece of information indicates the number of first devices associated with the first A-IoT service. The first devices are A-IoT devices, such as electronic tags. There can be one or more first devices associated with the first A-IoT service.

[0248] For example, the number of first devices associated with the first A-IoT service may include at least one of the following: the number of first devices that are not performing the first A-IoT service (which may also be replaced by the remaining number of first devices performing the first A-IoT service), the number of first devices that have performed the first A-IoT service, or the number of first devices associated with the first A-IoT service. A first device that is not performing the first A-IoT service may refer to a first device that does not perform the first A-IoT service when the connection between the terminal and the second access network device is disconnected, when the terminal leaves the second access network device, before the connection between the terminal and the second access network device is disconnected, before the terminal leaves the second access network device, or during the period when the terminal accesses the second access network device. A first device that has performed the first A-IoT service may refer to a first device that performs the first A-IoT service during the period when the terminal accesses the second access network device, or a first device that has performed the first A-IoT service when the connection between the terminal and the second access network device is disconnected, when the terminal leaves the second access network device, before the connection between the terminal and the second access network device is disconnected, or before the terminal leaves the second access network device. The number of first devices associated with the first A-IoT service can be the target / expected number of A-IoT devices or the total number of A-IoT devices for the first A-IoT service. For example, if the first A-IoT service is an inventory service, and the target / expected number of A-IoT devices for the inventory service is 100, and the number of A-IoT devices inventoryed during the terminal access to the second access network device (such as devices that have sent Device IDs) is 53, then the number of A-IoT devices not inventoryed is 47.

[0249] The disconnection between the terminal and the second access network device can be understood as: the terminal is not connected to the second access network device, or the second access network device is not serving the terminal.

[0250] For example, the number of first devices associated with the first A-IoT service includes the number of first devices that are not performing the first A-IoT service, and the first access network device configures the first resources based on the number of first devices that are not performing the first A-IoT service.

[0251] For example, the number of first devices associated with the first A-IoT service includes the number of first devices that have performed the first A-IoT service and the number of first devices associated with the first A-IoT service. The first access network device can determine the number of first devices that have not performed the first A-IoT service based on the number of first devices that have performed the first A-IoT service and the number of first devices associated with the first A-IoT service, and then configure the first resources based on the number of first devices that have not performed the first A-IoT service.

[0252] For example, the number of first devices associated with the first A-IoT service includes the number of first devices associated with the first A-IoT service, and the first access network device can configure the first resources according to the number of first devices associated with the first A-IoT service.

[0253] The phrase "executed / not executed / executed the first A-IoT service" can also be replaced with "performed / not performed / performed the first A-IoT service".

[0254] 2) Sixth Information

[0255] The sixth piece of information indicates the Quality of Service (QoS) information related to the first A-IoT service. For example, the QoS information related to the first A-IoT service may include at least one of the following: latency (such as packet delay budget (PDB)), communication range, priority, maximum data burst volume, packet error rate (PER), or averaging window. Latency can also be replaced by maximum response time, and the reader can perform relevant access stratum (AS) procedures based on latency requirements. Latency can refer to the end-to-end latency between the device and the reader, or the latency associated with different A-IoT services. For example, for inventory management services, the maximum end-to-end latency can be in the range of seconds / milliseconds or other time units, the indoor communication range is typically 30 to 50 meters, and the outdoor communication range is typically 200 to 400 meters.

[0256] The latency associated with the first A-IoT service may include at least one of the following: the remaining latency of the first A-IoT service, the latency already used by the first A-IoT service, or the latency of the first A-IoT service.

[0257] The remaining latency of the first A-IoT service can refer to the remaining latency of the first A-IoT service when the terminal leaves the second access network device or when the connection between the terminal and the second access network device is broken. The used latency of the first A-IoT service can refer to the duration of execution of the first A-IoT service when the connection between the terminal and the second access network device is broken, when the terminal leaves the second access network device, before the connection between the terminal and the second access network device is broken, before the terminal leaves the second access network device, and during the period when the terminal accesses the second access network device. The latency of the first A-IoT service can refer to the total latency of the first A-IoT service. For example, if the first A-IoT service has been executed for 6 seconds when the terminal leaves the second access network device or when the connection between the terminal and the second access network device is broken, and the latency of the first A-IoT service is 10 seconds, then the remaining latency of the first A-IoT service is 4 seconds.

[0258] The disconnection between the terminal and the second access network device can be understood as: the terminal is not connected to the second access network device, or the second access network device is not serving the terminal.

[0259] For example, the latency requirement associated with the first A-IoT service includes the remaining latency requirement of the first A-IoT service, and the first access network device configures the first resource according to the remaining latency requirement of the first A-IoT service.

[0260] For example, the latency requirements related to the first A-IoT service include the latency requirements already used by the first A-IoT service and the latency requirements of the first A-IoT service. The first access network device can determine the remaining latency requirements of the first A-IoT service based on the latency requirements already used by the first A-IoT service and the latency requirements of the first A-IoT service, and then configure the first resource based on the remaining latency requirements of the first A-IoT service that has not been performed.

[0261] For example, the latency requirements associated with the first A-IoT service include the latency requirements of the first A-IoT service, and the first access network device can configure the first resource according to the latency requirements of the first A-IoT service.

[0262] The phrase "executed / not executed / executed the first A-IoT service" can also be replaced with "performed / not performed / performed the first A-IoT service".

[0263] 3) Seventh Information

[0264] The seventh information indicates that the first A-IoT service is associated with one first device, or the seventh information indicates that the first A-IoT service is associated with multiple first devices. For example, the seventh information indicates that the first A-IoT service is targeted for one A-IoT device, or indicates that the first A-IoT service is targeted for more than one A-IoT device.

[0265] 4) Frequency band

[0266] This frequency band can be the frequency band supported by the first device related to the first A-IoT service.

[0267] The first device associated with the first A-IoT business can be one or more.

[0268] When there are multiple first devices associated with the first A-IoT service, if these multiple first devices belong to one or more groups, such as one or more groups of tags, the frequency band can be the frequency band of each of the one or more groups. The frequency band of each group can be indicated by a group ID and frequency band information, or by a list of device IDs for the first devices in that group and frequency band information. For cases where multiple first devices belong to one group, the frequency band information can also be used for indication. When there are multiple first devices associated with the first A-IoT service, the frequency band of each first device can also be indicated by its first device ID and frequency band information.

[0269] When the first device associated with the first A-IoT service is a single device, such as a tag, the frequency band is the frequency band of the first device. The frequency band can be indicated by the first device identifier (device ID) and frequency band information, or it can be indicated by the frequency band information.

[0270] The first device related to the first A-IoT service can refer to a first device that has not carried out the first A-IoT service, or it can refer to the number of target AIoT devices / Approximate number of AIoT devices for the first A-IoT service, without limitation.

[0271] 5) Execution cycle of the first A-IoT service

[0272] The cycle for executing the first A-IoT service can also be replaced with the number of times or frequency of executing the first A-IoT service. For example, the cycle for executing the first A-IoT service can be 8 hours, that is, the first A-IoT service is performed once every 8 hours.

[0273] 6) Types of the first A-IoT business

[0274] The first type of A-IoT service can be any of the following: inventory service, positioning service, sensing service, or command service. Command services can include one or more of the following: read service, write service, disable service, enable service, deactivate service, or lock service. Detailed descriptions of each service can be found in the terminology explanation section.

[0275] 7) Size of the data reported by the first device related to the first A-IoT service.

[0276] The size of the data reported by the first device related to the first A-IoT service can refer to the size of the data reported by the first device related to the first A-IoT service to the reader, or the total size of the data. This size can be an approximation or an estimate. For example, the size of the data reported by the first device related to the first A-IoT service can be the size of the device-to-reader (D2R) message.

[0277] The size of the data reported by the first device related to the first A-IoT service can also refer to the size of the data reported by the first device that performed / conducted the first A-IoT service to the reader.

[0278] The size of the data reported by the first device related to the first A-IoT service can also refer to the size of the data reported by the first device that has not performed / conducted the first A-IoT service to the reader.

[0279] 8) The number of identification information of the first device related to the first A-IoT service

[0280] The number of identification information for the first device associated with the first A-IoT service can refer to the number or total number of device IDs of the first device associated with the first A-IoT service. This number can be an estimate.

[0281] The number of identification information of the first device associated with the first A-IoT service can also refer to the number of device IDs of the first device that performed / conducted the first A-IoT service.

[0282] The number of identification information of the first device associated with the first A-IoT service can also refer to the number of device IDs of the first device that has not performed / conducted the first A-IoT service.

[0283] Step 1802: The first access network device determines the second information based on the first information.

[0284] The second information is used to indicate the first resource.

[0285] For example, the first access network device can allocate first resources to the terminal based on the first information, and then determine the second information.

[0286] After step 1802, the first access network device can send the second information to the terminal.

[0287] The embodiments of this application do not limit the method by which the first access network device sends the second information to the terminal.

[0288] Method 1: The first access network device directly sends the second information to the terminal, corresponding to step 1803 in Figure 18. Step 1803 is as follows.

[0289] Step 1803: The first access network device sends the second information to the terminal, and correspondingly, the terminal receives the second information from the first access network device.

[0290] For example, the first access network device may send the second information to the terminal during the process of the terminal accessing the first access network device or after the terminal accesses the first access network device.

[0291] Method 2: The first access network device sends the second information to the terminal through the second access network device, corresponding to steps 1804-1805 in Figure 18. Steps 1804-1805 are as follows.

[0292] Step 1804: The first access network device sends second information to the second access network device, and correspondingly, the second access network device receives the second information from the first access network device.

[0293] Step 1805: The second access network device sends second information to the terminal, and correspondingly, the terminal receives the second information from the second access network device.

[0294] It should be noted that steps 1802 and 1803 can also be replaced by: the first access network device sending second information to the terminal based on the first information. Steps 1802 and 1804 can also be replaced by: the first access network device sending second information to the second access network device based on the first information.

[0295] Based on method 1800, the second access network device can interact with the first access network device via an inter-site interface to exchange information for configuring A-IoT resources, such as information related to the first A-IoT service. Thus, when a terminal temporarily loses connection to the network, the second access network device can provide the first access network device with information for configuring A-IoT resources through the inter-site interface. The first access network device can then configure the A-IoT resources based on the received information, thereby ensuring the continuity of A-IoT services.

[0296] The embodiments of this application do not limit the method by which the second access network device obtains the first information.

[0297] In some implementations, the second network device determines the first information. For example, in Scheme 1 of Topology 2, the second network device can obtain some information about the first A-IoT service, and the second network device can determine the first information based on this information.

[0298] In some implementations, the second network device can receive the first information from the terminal. In this implementation, method 1800 may further include step 1806, whereby the terminal sends the first information to the second access network device, and the second access network device receives the first information from the terminal accordingly. This implementation can be applied to schemes 1, 2, and 3 of topology 2.

[0299] In some other embodiments of this application, the first information may further include tenth information, which is used to indicate a second resource. The second resource may be a resource allocated by the second access network device for the terminal to perform the first A-IoT service. That is, the second access network device may indicate to the first access network device the resources it has allocated for the terminal to perform the first A-IoT service, for the second access network device to refer to. The second resource may be the same as or different from the first resource.

[0300] In other embodiments of this application, the second access network device can also interact with the first access network device via an inter-site interface to exchange information for configuring the carrier. The information for configuring the carrier and the information for configuring A-IoT resources can be carried in the same message or in different messages, without limitation. In this embodiment, method 1800 may further include: the second access network device sending third information to the first access network device; correspondingly, the first access network device receiving the third information from the second access network device, wherein the third information is used to configure the carrier, or to determine first carrier configuration information, or to determine whether to send a carrier and / or charge to the first device related to the first A-IoT service; the first access network device determines fourth information based on the third information, the fourth information being the first carrier configuration information; and the first access network device sending the fourth information. The implementation method of the first access network device sending the fourth information can refer to the implementation method of the first access network device sending the second information, and will not be detailed further.

[0301] In some implementations, the first carrier configuration information includes at least one of the following: first transmission power, first transmission start time, first transmission end time, first transmission period, first duration, first region, and first frequency domain resources, wherein the first region includes the region of the transmission carrier and / or the region related to the first A-IoT service.

[0302] In some implementations, the third information includes at least one of the following: the capabilities of the first device related to the first A-IoT service, or the type of the first device related to the first A-IoT service. The first device related to the first A-IoT service may refer to a first device that is not performing the first A-IoT service, or it may refer to the number of target A-IoT devices for the first A-IoT service; there is no limitation on this.

[0303] For example, the capabilities of the first device associated with the first A-IoT service include at least one of the following: reflection capability (or backscattering capability), energy storage capability, signal amplification capability (such as uplink and / or downlink signal amplification capability), or signal generation capability.

[0304] For example, the first A-IoT service may be associated with one or more types of first devices. Specifically, the types of first devices associated with the first A-IoT service include at least one of the following: device 1, device 2a, device 2b, device A, device B, or device C. Descriptions of each type can be found above.

[0305] In some implementations, the third information may further include second carrier configuration information. For example, the second carrier configuration information includes at least one of the following: a second transmission power, a second transmission start time, a second transmission end time, a second transmission period, a second duration, a second region, and second frequency domain resources, wherein the second region includes the region for transmitting the carrier and / or the region related to the first A-IoT service. The second carrier configuration information may be determined by the second access network device. That is, the second access network device may indicate to the first access network device that it has determined the carrier configuration information for reference. The second carrier configuration information may be the same as or different from the first carrier configuration information.

[0306] In other embodiments of this application, the first information is further used to configure a third resource, which is used for communication between the terminal and the first access network device, such as an NR Uu air interface resource. In this case, method 1800 may further include: the first access network device determining eleventh information based on the first information, the eleventh information being used to indicate the third resource; and the first access network device sending the eleventh information. The implementation method of the first access network device sending the eleventh information can refer to the implementation method of the first access network device sending the second information, and will not be described in detail here.

[0307] In some other embodiments of this application, the third information may also include at least one of the following: an indication of whether the first A-IoT service continues (service continue or not or A-IoT service on-going indication), the type of the terminal (UEreader type / indication), the service area info related to the first A-IoT service (service area info), the A-IoT resource request (A-IoT resource request), or the identifier of the first A-IoT service.

[0308] For example, the area related to the first A-IoT service can be an area based on GPS coordinates or an area based on grid division (such as an area divided according to signal quality), without limitation.

[0309] For example, the identifier of the first A-IoT service can be a service ID, session ID, task ID, or transaction ID.

[0310] Figure 19 is a schematic flowchart of a communication method 1900 provided in an embodiment of this application.

[0311] Method 1900 describes a scheme in which a terminal and a first access network device interact with information for configuring A-IoT resources and / or information for configuring CW.

[0312] Method 1900 includes at least a portion of the following.

[0313] Step 1901: The terminal sends first information to the first access network device, and correspondingly, the first access network device receives the first information from the terminal.

[0314] The first information is used to configure, schedule, or determine the first resource for the terminal. The first resource is used by the terminal to execute the first A-IoT service or for the terminal to communicate with the first device; for example, the first resource is an A-IoT resource. The first information is information that the first access network device can refer to when allocating the first resource. The first information may be information related to the first A-IoT service, and may include information derived from inference, such as the number of uncounted A-IoT devices. A detailed description of the first resource and the first information can be found in Method 1800, and will not be elaborated further here.

[0315] For example, the terminal may send the first information to the first access network device during or after accessing the first access network device.

[0316] It should be understood that the first message can be sent through a single message or multiple messages without restriction. For example, when a terminal sends the first message upon accessing a first access network device, it can send the first message through message 3 (MSG 3) (e.g., RRCReestablishmentRequest). However, message 3 has a relatively small message size, which may not be enough to send the entire first message. In this case, the remaining information can be sent through RRC messages such as UAI.

[0317] Step 1902: The first access network device determines the second information based on the first information.

[0318] The second information is used to indicate the first resource.

[0319] For example, the first access network device can allocate first resources to the terminal based on the first information, and then determine the second information.

[0320] Step 1903: The first access network device sends the second information to the terminal, and correspondingly, the terminal receives the second information from the first access network device.

[0321] For example, the first access network device may send the second information to the terminal during the process of the terminal accessing the first access network device or after the terminal accesses the first access network device.

[0322] It should be noted that steps 1902 and 1903 can also be replaced by: the first access network device sending the second information to the terminal based on the first information.

[0323] Method 1900 can be applied to Scheme 1, Scheme 2 and Scheme 3 of Topology 2.

[0324] Based on method 1900, the terminal can interact with the first access network device through the interface between the terminal and the access network device to exchange information for configuring A-IoT resources, such as information related to the first A-IoT service. Thus, when the terminal temporarily loses connection to the network, it can provide the first access network device with information for configuring A-IoT resources through the interface between the terminal and the access network device. The first access network device can then configure the A-IoT resources based on the received information, thereby ensuring the continuity of A-IoT services.

[0325] In other embodiments of this application, the terminal can also interact with the first access network device through the interface between the terminal and the access network device to exchange information for configuring the carrier. The information for configuring the carrier and the information for configuring A-IoT resources can be carried in the same message or in different messages, without limitation. In this embodiment, method 1900 may further include: the terminal sending third information to the first access network device, and correspondingly, the first access network device receiving the third information from the terminal, wherein the third information is used to configure the carrier or to determine whether to send a carrier and / or charge the first device related to the first A-IoT service; the first access network device determines fourth information based on the third information, the fourth information being the first carrier configuration information; and the first access network device sending the fourth information to the terminal. The descriptions of the third information and the first carrier configuration information can be found in method 1800.

[0326] In other embodiments of this application, the first information is further used to configure a third resource, which is used for communication between the terminal and the first access network device, such as an NR Uu air interface resource. In this case, method 1900 may further include: the first access network device determining eleventh information based on the first information, the eleventh information being used to indicate the third resource; and the first access network device sending the eleventh information to the terminal.

[0327] Methods 1800 and 1900 described above can be applied to various scenarios where terminals temporarily lose network connection. The following describes methods 1800 and 1900 in detail using HO scenarios, RLF scenarios, and inactive terminal scenarios as examples.

[0328] HO Scene

[0329] The following describes the scheme for information related to A-IoT services between stations, with reference to Figures 20 to 22.

[0330] Figure 20 is a schematic flowchart of a communication method 2000 provided in an embodiment of this application.

[0331] Method 2000 includes at least a portion of the following.

[0332] Optionally, in step 2001, the terminal sends a fourth message to the second access network device, and correspondingly, the second access network device receives the fourth message from the terminal.

[0333] The fourth message includes the first information, which is used to configure, schedule or determine the first resource for the terminal. A detailed description of the first resource and the first information can be found in Method 1800, and will not be elaborated further.

[0334] In one implementation, the terminal executes a first A-IoT service and accesses a second access network device. During the execution of the first A-IoT service, the terminal sends a fourth message to the second access network device.

[0335] For example, the terminal explicitly indicates the first information to the second access network device through a fourth message. Explicitly indicating the first information to the second access network device can be understood as the second access network device being able to parse and obtain the first information.

[0336] The fourth message can be an RRC message. For example, the fourth message is used to report A-IoT service-related data (such as Device ID(s)), such as an inventory report. For example, the fourth message is used to provide user equipment assistance information, such as a user equipment assistance information (UAI) message. For example, the fourth message is used to request A-IoT resources, such as an A-IoT resource request message. For example, the fourth message can also be other RRC messages, which can be reused existing RRC messages or new RRC messages; there are no restrictions.

[0337] It should be understood that the first message can be sent through one message or multiple messages without restriction.

[0338] Step 2001 is optional. For example, in Scheme 1 of Topology 2 (RRC-based scheme), the second network device can obtain some information about the first A-IoT service. Based on this information, the second network device can determine the first information. In this case, step 2001 can be omitted. Of course, the scheme of executing step 2001 is applicable to both Scheme 2 of Topology 2 (NAS-based scheme) and Scheme 3 of Topology 2 (UP-based scheme), as well as Scheme 1 of Topology 2 (RRC-based scheme). For Scheme 1 of Topology 2 (RRC-based scheme), the first information is preferentially exchanged through the XnAP interface.

[0339] In step 2002, the second access network device sends a first message to the first access network device, and correspondingly, the first access network device receives the first message from the second access network device.

[0340] The first message is used to initiate a handover request, such as a handover request message. The first message includes first information, which is used to configure, schedule, or determine first resources for the terminal. Detailed descriptions of the first resources and first information can be found in Method 1800 and will not be repeated here. It should be understood that in HO scenarios, the second access network device can also send the first information to the first access network device through messages from other XnAP interfaces without restriction.

[0341] Step 2003: The first access network device determines the second information based on the first information.

[0342] The second information is used to indicate the first resource.

[0343] For example, the first access network device can allocate first resources to the terminal based on the first information, and then determine the second information.

[0344] In step 2004, 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.

[0345] The second message can be any message from the XnAP interface. For example, the second message is used to switch the terminal to the first access network device; for instance, the second message can be a handover request acknowledgement message.

[0346] In step 2005, the second access network device sends a third message to the terminal, and correspondingly, the terminal receives the third message from the second access network device.

[0347] The third message can be an RRC message. For example, the third message is used to switch the terminal to the first access network device; for instance, the third message can be a handover command or an RRC reconfiguration message. For example, the third message can also be other RRC messages, including reused existing RRC messages and new RRC messages, without limitation.

[0348] It should be noted that steps 2003 and 2004 can also be replaced by: the first access network device sending a third message to the second access network device based on the first information.

[0349] In other embodiments of this application, the first information may further include tenth information, which is used to indicate a second resource. The second resource may be a resource allocated by the second access network device for the terminal to perform the first A-IoT service. The second resource may be the same as or different from the first resource.

[0350] In other embodiments of this application, the second access network device can also interact with the first access network device via an inter-site interface to exchange information for configuring the carrier. The information for configuring the carrier and the information for configuring A-IoT resources can be carried in the same message or in different messages, without limitation. In some implementations, the first message further includes third information, wherein the third information is used to configure the carrier, determine the first carrier configuration information, or determine whether to send a carrier and / or charge to the first device related to the first A-IoT service. The second and third messages also include fourth information, which is the first carrier configuration information. In this case, method 2000 may further include: the first access network device determining the fourth information based on the third information. Furthermore, when step 2001 is executed, the fourth message may also include the third information. A detailed description of the third information and the first carrier configuration information can be found in method 1800, and will not be elaborated further here.

[0351] In some implementations, the third information may also include second carrier configuration information. It should be understood that the third information provided by the second access network device to the first access network device may include the second carrier configuration information, while the third information provided by the terminal to the second access network device does not include the second carrier configuration information. A detailed description of the second carrier configuration information can be found in Method 1800, and will not be elaborated further here.

[0352] In some other embodiments of this application, the first information is also used to configure a third resource, which is used for communication between the terminal and the first access network device, such as an NR Uu air interface resource.

[0353] Figure 21 is a schematic flowchart of a communication method 2100 provided in an embodiment of this application.

[0354] As shown in Figure 21, taking the terminal as UE, the core network element as A-IoT CN, the first access network device as target gNB, and the second access network device as source gNB as an example, A-IoT CN can be A-IoTF, tag management function (TMF), A-IoT management function (A-IoTMF) network element, or other core network elements / nodes / devices that support / enable A-IoT, and the specific name is not limited.

[0355] Method 2100 is applicable to the RRC-based solution architecture in HO handover scenarios. In Method 2100, A-IoT service-related information (including inferred information) is exchanged between stations in the HO scenario for the target gNB to configure A-IoT resources and / or CW for the UE. Method 2100 includes at least some of the following:

[0356] Step 2101: The A-IoT CN sends A-IoT service request #1 to the source gNB via XXAP / NGAP message. Correspondingly, the source gNB receives A-IoT service request #1 from the A-IoT CN.

[0357] Among them, A-IoT service request #1 (e.g., inventory request, or command / command request) is used to request the execution of the first A-IoT service (e.g., inventory service).

[0358] A-IoT service request #1 may include at least one of the following: a first identifier (e.g., device identification) or a second identifier (e.g., service / session / task / transaction ID). The first identifier identifies a single A-IoT device, a group of A-IoT devices, or all A-IoT devices. For example, it identifies a single A-IoT device using a mask and the entire group of A-IoT devices using a group ID. One possibility is that the A-IoT service request message does not include A-IoT device identification information, indicating that all A-IoT devices are executing the current A-IoT service. The second identifier identifies the first A-IoT service.

[0359] For example, for inventory management services, A-IoT service request #1 is an inventory management request; for command services, A-IoT service request #1 is a command request, such as a read request, write request, disable request, enable request, deactivate request, or lock request.

[0360] It should be noted that the source gNB can parse and obtain the information carried in A-IoT service request #1.

[0361] Step 2102: The source gNB sends A-IoT service request #2 to the UE. Correspondingly, the UE receives A-IoT service request #2 from the source gNB.

[0362] The A-IoT service request #2 may include at least one of the following: a first identifier or a second identifier. The first identifier is used to identify the A-IoT device, and the second identifier is used to identify the first A-IoT service.

[0363] Optionally, the A-IoT service request #2 may further include resource configuration information for configuring a first resource for the UE to perform the first A-IoT service. For example, the resource configuration information of the first resource may include time-domain resource configuration information and / or frequency-domain resource configuration information. Optionally, the resource configuration information may further include the maximum power transmitted by the terminal to the A-IoT device.

[0364] For example, for inventory management services, A-IoT service request #2 is an inventory management request; for command services, A-IoT service request #2 is a command request, such as a read request, write request, disable request, enable request, deactivate request, or lock request, etc.

[0365] Step 2103: The source gNB triggers HO and sends a handover request message #1 to the target gNB through the XnAP interface. Correspondingly, the target gNB receives the handover request message #1 from the source gNB.

[0366] The handover request message #1 includes information #1 (corresponding to the first information and the third information), and information #1 includes at least one of the following:

[0367] 1) Indication on whether the first A-IoT service should continue (service continue or not or A-IoT service on-going indication);

[0368] 2) The type of the first A-IoT service;

[0369] 3) The number of A-IoT devices that did not perform the first A-IoT service;

[0370] 4) The number of A-IoT devices that performed the first A-IoT service;

[0371] 5) The number of A-IoT devices related to the first A-IoT business;

[0372] 6) Remaining QoS requirements for the first A-IoT service;

[0373] 7) QoS requirements already used by the first A-IoT service;

[0374] 8) QoS requirements for the first A-IoT service;

[0375] 9) Frequency bands supported by A-IoT devices related to the first A-IoT service;

[0376] 10) Indicates information related to one or more A-IoT devices for the first A-IoT service;

[0377] 11) The cycle of executing the first A-IoT service;

[0378] 12) The size of the data reported by the first device related to the first A-IoT service;

[0379] 13) The number of identification information of the first device related to the first A-IoT service;

[0380] 14) The capabilities of the first device related to the first A-IoT service (such as reflection capability (or backscattering capability), energy storage capability, signal amplification capability (such as uplink and / or downlink signal amplification capability), or signal generation capability);

[0381] 15) The type of the first device associated with the first A-IoT service (e.g., device 1, device 2a, device 2b, device A, device B, or device C or other classifications);

[0382] 16) Terminal type (UE reader type / indication);

[0383] 17) Service area information related to the first A-IoT service;

[0384] 18) A-IoT resource request;

[0385] 19) Identification of the first A-IoT business, etc.

[0386] Specifically, information 2) to 13) above can be used to configure A-IoT resources, and information 14) and 15) above can be used to configure carriers, or to determine carrier configuration information, or to determine whether to send a carrier and / or charge a device related to the first A-IoT service. Detailed descriptions of each of the above information can be found in Method 1800, and will not be elaborated further here.

[0387] Optionally, the source gNB can configure A-IoT resources and / or CW configuration information, which are then forwarded to the UE by the target gNB. In this case, the handover request message #1 may also include tenth information indicating the A-IoT resources configured by the source gNB and / or second CW configuration information configured by the source gNB. Of course, the A-IoT resources and / or CW configuration information can also be configured by the target gNB.

[0388] Step 2104: The target gNB determines whether the UE should continue to execute the first A-IoT service based on the region related to the first A-IoT service.

[0389] If the target gNB determines that the UE should continue executing the first A-IoT service, then proceed to step 2004. If the target gNB determines that the UE should not continue executing the first A-IoT service, then the HO related procedures can proceed normally.

[0390] Step 2105: If the target gNB determines that the UE continues to perform the first A-IoT service, the target gNB sends a handover request acknowledgement message #1 to the source gNB through the XnAP interface. Correspondingly, the source gNB receives the handover request acknowledgement message #1 from the target gNB.

[0391] The handover request confirmation message #1 includes second information and / or fourth information. The second information indicates a first resource, which is used for the UE to communicate with the A-IoT device, or in other words, for the UE to perform a first A-IoT service. The fourth information is first CW configuration information.

[0392] For example, the first resource can be an A-IoT radio resource, which may include time-domain resources and / or frequency-domain resources. The effective area of ​​the first resource can be a single cell or multiple cells. The resource configuration information of the first resource includes time-domain resource configuration information and / or frequency-domain resource configuration information. Optionally, the resource configuration information may also include the maximum power transmitted by the terminal to the A-IoT device. The time-domain resource configuration information can be a duration. If the terminal determines that the duration configured by the access network device is insufficient to complete the first A-IoT service, the terminal can request A-IoT resources (such as duration) from the access network device, and then the access network device will allocate or schedule A-IoT resources (such as duration) to the terminal.

[0393] The first CW configuration information may include at least one of the following: first transmission power, first transmission start time, first transmission end time, first transmission period, first duration, first region, and first frequency domain resources, wherein the first region includes the region of the transmission carrier and / or the region related to the first A-IoT service.

[0394] Step 2106: The source gNB sends a handover command message or an RRC reconfiguration message to the UE. Correspondingly, the UE receives the handover command message or RRC reconfiguration message from the source gNB.

[0395] The handover command message or RRC reconfiguration message includes the second and / or fourth information. The handover command message or RRC reconfiguration message is used to trigger a handover, or in other words, to request the UE to perform a handover and hand over to the target cell, or to hand over the UE to the target cell. The target cell is the cell under the target gNB.

[0396] Step 2107: The UE and the target gNB complete random access.

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

[0398] Subsequently, the UE can continue to execute the first A-IoT service based on the first resource indicated by the second information and / or the first CW configuration information in the fourth information.

[0399] The target gNB sends the second and / or fourth information to the source gNB, which then sends it to the UE. In other implementations, the target gNB may also send the second and / or fourth information directly to the UE when the terminal accesses the target gNB or after the terminal has accessed the target gNB.

[0400] It should be noted that step 2104 can also be executed by other network elements, such as the source gNB, A-IoT CN, etc.

[0401] Based on method 2100, stations can exchange A-IoT service-related information (including derivation-based information) for the target gNB to configure A-IoT resources and / or CW configuration information for the UE, which helps to improve the continuity of A-IoT services, thereby ensuring the performance of A-IoT services and improving the user service experience.

[0402] Figure 22 is a schematic flowchart of a communication method 2200 provided in an embodiment of this application.

[0403] As shown in Figure 22, taking the terminal as UE, the core network element as A-IoT CN, the first access network device as the target gNB, and the second access network device as the source gNB as an example, the A-IoT CN can be an A-IoTF, TMF, A-IoTMF network element or other core network element / node / device that supports / enables A-IoT, and the specific name is not limited.

[0404] Method 2200 is applicable to NAS / UP-based solution architectures in HO handover scenarios. In Method 2200, A-IoT service-related information (including inferred information) is exchanged between sites in the HO scenario, which is used by the target gNB to configure A-IoT resources and / or CW for the UE. Unlike Method 2100, the UE provides A-IoT service-related information to the source gNB, which then provides it to the target gNB based on inter-site interaction.

[0405] Method 2200 includes at least a portion of the following.

[0406] Step 2201: A-IoT CN sends A-IoT service request #3 to UE via NAS message or PDU session. Correspondingly, UE receives A-IoT service request #3 from A-IoT CN.

[0407] Specifically, A-IoT service request #3 is used to request the execution of a first A-IoT service. A-IoT service request #3 may include at least one of the following: a first identifier or a second identifier. The first identifier is used to identify the A-IoT device, and the second identifier is used to identify the first A-IoT service. A detailed description of A-IoT service request #3 can be found in the description of A-IoT service request #1 in step 2101.

[0408] It should be noted that the source gNB does not parse and retrieve the information carried in A-IoT service request #3.

[0409] For a NAS / UP-based solution architecture, the first resource for executing the first A-IoT service can be configured for the terminal in the following way.

[0410] Method 1: The A-IoT CN sends an AIoT resource request to the previous serving gNB to trigger the previous serving gNB to allocate the first resource to the UE.

[0411] Method 2: After receiving AIoT service request #3 included in the NAS / PDU Session, the UE requests AIoT resources from the upstream service gNB, and then the upstream service gNB allocates the first resource to the UE.

[0412] In step 2202, the UE sends information #2 (corresponding to the first information and the third information) to the source gNB, and the source gNB receives information #2 from the UE accordingly.

[0413] Information #2 is related to the first A-IoT service. Information #2 is included in RRC messages, and for example, information #2 may include any of the following: inventory report, UAI, A-IoT resource request message, or other RRC messages.

[0414] For example, information #2 includes at least one of the following:

[0415] 1) The type of the first A-IoT service;

[0416] 2) The number of A-IoT devices that did not perform the first A-IoT service;

[0417] 3) The number of A-IoT devices that performed the first A-IoT service;

[0418] 4) The number of A-IoT devices related to the first A-IoT business;

[0419] 5) Remaining QoS requirements for the first A-IoT service;

[0420] 6) QoS requirements already used by the first A-IoT service;

[0421] 7) QoS requirements for the first A-IoT service;

[0422] 8) Frequency bands supported by A-IoT devices related to the first A-IoT service;

[0423] 9) Indicates information related to one or more A-IoT devices for the first A-IoT service;

[0424] 10) The cycle of executing the first A-IoT service;

[0425] 11) The size of the data reported by the first device related to the first A-IoT service;

[0426] 12) The number of identification information of the first device related to the first A-IoT service;

[0427] 13) The capabilities of the first device related to the first A-IoT service (such as reflection capability (or backscattering capability), energy storage capability, signal amplification capability (such as uplink and / or downlink signal amplification capability), or signal generation capability);

[0428] 14) The type of the first device associated with the first A-IoT service (e.g., device 1, device 2a, device 2b, device A, device B, or device C or other classifications);

[0429] 15) Terminal type (UE reader type / indication);

[0430] 16) Service area information related to the first A-IoT service;

[0431] 17) A-IoT resource request;

[0432] 18) Identification of the first A-IoT business, etc.

[0433] Among these, information 1) to 13) can be used to configure A-IoT resources, and information 13) and 14) can be used to configure carriers, or to determine carrier configuration information, or to determine whether to send a carrier and / or charge a device related to the first A-IoT service. Detailed descriptions of each of the above information can be found in Method 1800, and will not be elaborated further here.

[0434] Step 2203: The source gNB triggers the HO and sends a handover request message #1 to the target gNB through the XnAP interface. Correspondingly, the target gNB receives the handover request message #1 from the source gNB.

[0435] The handover request message #1 includes information #1 (i.e., first information and third information). A description of the handover request message #1 and information #1 can be found in step 2103.

[0436] Optionally, the source gNB can configure A-IoT resources and / or CW configuration information, which are then forwarded to the UE by the target gNB. In this case, the handover request message #1 may also include tenth information indicating the A-IoT resources configured by the source gNB and / or second CW configuration information configured by the source gNB. Of course, the A-IoT resources and / or CW configuration information can also be configured by the target gNB.

[0437] Step 2204: The target gNB sends a handover request confirmation message #2 to the source gNB through the XnAP interface. Correspondingly, the source gNB receives the handover request confirmation message #2 from the target gNB.

[0438] Step 2205: The source gNB sends a handover command message or an RRC reconfiguration message to the UE. Correspondingly, the UE receives the handover command message or RRC reconfiguration message from the source gNB.

[0439] The handover command message or RRC reconfiguration message is used to trigger the handover, or in other words, to request the UE to perform a handover and hand over to the target cell, or to hand over the UE to the target cell. The target cell is the cell under the target gNB.

[0440] Step 2206: The UE and the target gNB complete random access.

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

[0442] Optionally, in step 2207, the UE sends an RRC reconfiguration complete message (RRCReconfigurationComplete) to the target gNB to indicate that random access has been completed.

[0443] Step 2208: The target gNB sends a path switch request message to the A-IoT CN. Correspondingly, the A-IoT CN receives the path switch request message from the target gNB.

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

[0445] 1) Second identifier;

[0446] 2) Whether to continue executing the first A-IoT service, or whether to continue acting as the reader / writer for the first A-IoT service;

[0447] 3) Whether data and / or signaling related to the first A-IoT business are reported.

[0448] Step 2209: The A-IoT CN determines whether the UE should continue to execute the first A-IoT service.

[0449] For example, the A-IoT CN determines whether the UE can continue to perform the current first A-IoT service and / or whether the UE can continue to act as a reader / writer based on the regional information and / or the type of terminal related to the first A-IoT service.

[0450] If the target gNB determines that the UE should continue performing the first A-IoT service, then step 2110 can proceed. If the target gNB determines that the UE should not continue performing the first A-IoT service, and / or the UE cannot continue to act as a reader / writer, then the path switching process can proceed normally.

[0451] Step 2210: The A-IoT CN sends a path switch request acknowledgment message (e.g., path switch request acknowledge) to the target gNB. Correspondingly, the target gNB receives the path switch request acknowledgment message from the A-IoT CN.

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

[0453] 1) UE type: UEreader;

[0454] 2) Second identifier: Used to identify the current first A-IoT service;

[0455] 3) The UE continues to perform the first A-IoT service, or the UE continues to act as the reader / writer of the first A-IoT service, or the UE is authorized to act as the reader / writer;

[0456] 4) Report data and / or signaling related to the first A-IoT business.

[0457] Step 2211: The target gNB sends RRC message #1 to the UE, and correspondingly, the UE receives RRC message #1 from the target gNB.

[0458] RRC message #1 may include second information and / or fourth information. The second information indicates a first resource used by the UE to communicate with A-IoT devices, or in other words, the first resource is used by the UE to perform a first A-IoT service. The fourth information is first CW configuration information. Optionally, RRC message #1 may also include a second identifier. A detailed description of the first resource and the first CW configuration information can be found in method 1800.

[0459] For example, RRC message #1 can be any RRC message, including a reused existing RRC message and a new RRC message, without any restrictions.

[0460] Subsequently, the UE can continue to execute the first A-IoT service based on the first resource indicated by the second information and / or the first CW configuration information in the fourth information.

[0461] It should be noted that step 2209 can also be executed by other network elements, such as the source gNB, the destination gNB, etc.

[0462] Based on method 2200, inter-stations can exchange A-IoT service-related information (including inferred information) for the target gNB to configure A-IoT resources and / or CW configuration information for the UE. This helps improve A-IoT service continuity, thereby ensuring A-IoT service performance and improving user experience. Furthermore, in the NAS / UP-based solution under HO handover scenarios, the UE can provide A-IoT service-related information to the source gNB.

[0463] The following describes the scheme for the UE to report A-IoT service-related information to the first access network device with reference to Figure 23.

[0464] Figure 23 is a schematic flowchart of a communication method 2300 provided in an embodiment of this application.

[0465] Method 2300 includes at least a portion of the following.

[0466] Step 2301: The second access network device sends the sixteenth message to the first access network device, and correspondingly, the first access network device receives the sixteenth message from the second access network device.

[0467] The sixteenth message is used to initiate a handover request, such as the sixteenth message being a handover request message.

[0468] Step 2302: The first access network device sends the twelfth message to the second access network device, and correspondingly, the second access network device receives the twelfth message from the first access network device.

[0469] The twelfth message is used to switch the terminal to the first access network device. For example, the twelfth message can be a handover request confirmation message.

[0470] Step 2303: The second access network device sends a ninth message to the terminal, and the terminal receives the ninth message from the second access network device.

[0471] The ninth message is used to switch the terminal to the first access network device. For example, the third message can be a handover command or an RRC reconfiguration message.

[0472] Step 2304: The terminal sends a tenth message to the first access network device, and the first access network device receives the tenth message from the terminal.

[0473] The tenth message includes first information, which is used to configure, schedule or determine a first resource for the terminal. A detailed description of the first resource and the first information can be found in Method 1800, and will not be elaborated further.

[0474] In one implementation, the terminal executes a first A-IoT service and accesses a second access network device. During the execution of the first A-IoT service, the second access network device instructs the terminal to switch to the first access network device. When or after accessing the first access network device, the terminal sends a tenth message to the first access network device.

[0475] The tenth message can be an RRC message. For example, the tenth message may be used to provide a report on A-IoT services, such as an inventory report. For example, the tenth message may be used to provide user equipment auxiliary information, such as a UAI message. For example, the tenth message may be used to request A-IoT resources, such as an A-IoT resource request message. For example, the tenth message can also be other RRC messages, including reused existing RRC messages and new RRC messages; there are no limitations.

[0476] It should be understood that the first message can be sent through a single message or multiple messages without restriction. For example, when a terminal sends the first message upon accessing a first access network device, it can send the first message through message 3 (MSG 3) (such as RRCReestablishmentRequest). However, message 3 can only send a relatively small amount of information, which may not be enough to send the first message completely. In this case, the remaining information can be sent through RRC messages such as UAI.

[0477] Step 2305: The first access network device determines the second information based on the first information.

[0478] The second information is used to indicate the first resource.

[0479] For example, the first access network device can allocate first resources to the terminal based on the first information, and then determine the second information.

[0480] Step 2306: The first access network device sends an eleventh message to the terminal, and the terminal receives the eleventh message from the first access network device.

[0481] The eleventh message includes the second information. The eleventh message can be an RRC message, a reused existing RRC message, or a new RRC message; there are no restrictions.

[0482] It should be noted that steps 2305 and 2306 can also be replaced by: the first access network device sending an eleventh message to the terminal based on the first information.

[0483] In other embodiments of this application, the terminal may also provide the first access network device with information for configuring the carrier. The information for configuring the carrier and the information for configuring A-IoT resources may be carried in the same message or in different messages, without limitation. In some implementations, the tenth message further includes third information, wherein the third information is used to configure the carrier, determine the first carrier configuration information, or determine whether to send a carrier and / or charge to the first device related to the first A-IoT service; the eleventh message further includes fourth information, which is the first carrier configuration information. In this case, method 2300 may further include: the first access network device determining the fourth information based on the third information.

[0484] In some other embodiments of this application, the first information is also used to configure a third resource, which is used for communication between the terminal and the first access network device, such as an NR Uu air interface resource.

[0485] RLF scene

[0486] The following describes the scheme for the UE to report A-IoT service-related information to the first access network device, with reference to Figures 24 and 25.

[0487] Figure 24 is a schematic flowchart of a communication method 2400 provided in an embodiment of this application.

[0488] Method 2400 includes at least a portion of the following.

[0489] Step 2401: The terminal executes the first A-IoT service and discovers RLF during the execution of the first A-IoT service.

[0490] Step 2402: The terminal sends a fifth message to the first access network device, and correspondingly, the first access network device receives the fifth message from the terminal.

[0491] The fifth message includes first information, which is used to configure, schedule or determine a first resource for the terminal. For a detailed description of the first resource and the first information, please refer to Method 1800, which will not be elaborated here.

[0492] The fifth message can be an RRC message. For example, the fifth message may be used to request the reconstruction of the terminal's RRC connection, such as an RRC reconstruction request message (RRCRestablishmentRequest). For example, the fifth message may be used to provide user equipment assistance information, such as a UAI message. For example, the fifth message may be used to request A-IoT resources, such as an A-IoT resource request message. For example, the fifth message can also be other RRC messages, including reused existing RRC messages and new RRC messages; there are no limitations.

[0493] It should be understood that the first message can be sent through a single message or multiple messages without restriction. For example, when a terminal sends the first message upon accessing a first access network device, it can do so via RRCReestablishmentRequest. However, RRCReestablishmentRequest can only send a relatively small amount of information, which may not be enough to send the entire first message. In this case, the remaining information can be sent via RRC messages such as UAI.

[0494] In one implementation, the terminal executes a first A-IoT service and accesses a second access network device. During the execution of the first A-IoT service, it discovers an RLF (Remote Message Function), and then sends a fifth message to the first access network device when or after accessing the first access network device.

[0495] Step 2403: The first access network device determines the second information based on the first information.

[0496] The second information is used to indicate the first resource.

[0497] For example, the first access network device can allocate first resources to the terminal based on the first information, and then determine the second information.

[0498] Step 2404: The first access network device sends a sixth message to the terminal, and the terminal receives the sixth message from the first access network device.

[0499] The sixth message includes the second information. The sixth message can be an RRC message. For example, the sixth message is used to rebuild the terminal's RRC connection, such as an RRC establishment message. For example, the sixth message is used to allocate A-IoT resources, such as an A-IoT resource request confirmation / response message. For example, the sixth message can also be other RRC messages, including reused existing RRC messages and new RRC messages; there are no limitations.

[0500] It should be noted that steps 2403 and 2404 can also be replaced by: the first access network device sending a sixth message to the terminal based on the first information.

[0501] In other embodiments of this application, the terminal may also provide the first access network device with information for configuring the carrier. The information for configuring the carrier and the information for configuring A-IoT resources may be carried in the same message or in different messages, without limitation. In some implementations, the fifth message further includes third information, wherein the third information is used to configure the carrier, determine the first carrier configuration information, or determine whether to send a carrier and / or charge to the first device related to the first A-IoT service, and the sixth message further includes fourth information, which is the first carrier configuration information. In this case, method 2400 may further include: the first access network device determining the fourth information based on the third information.

[0502] In some other embodiments of this application, the first information is also used to configure a third resource, which is used for communication between the terminal and the first access network device, such as an NR Uu air interface resource.

[0503] Subsequently, the UE can continue to perform the first A-IoT service based on the first resource indicated by the second information and / or the first carrier configuration information in the fourth information.

[0504] Figure 25 is a schematic flowchart of a communication method 2500 provided in an embodiment of this application.

[0505] As shown in Figure 25, taking the terminal as UE, the core network element as A-IoT CN, the first access network device as the new gNB, and the second access network device as the last serving gNB as an example, the A-IoT CN can be an A-IoTF, TMF, A-IoTMF network element or other core network element / node / device that supports / enables A-IoT, and the specific name is not limited.

[0506] In method 2500, the UE reports information related to A-IoT services to the new gNB, which is used by the new gNB to configure A-IoT resources and / or CW for the UE. Method 2500 includes at least some of the following.

[0507] Optionally, in step 2501, the A-IoT CN sends an A-IoT service request #1 to the previous serving gNB via an XXAP / NGAP message. Correspondingly, the previous serving gNB receives the A-IoT service request #1 from the A-IoT CN.

[0508] Specifically, A-IoT service request #1 is used to request the execution of a first A-IoT service. A-IoT service request #1 may include at least one of the following: a first identifier or a second identifier. The first identifier is used to identify the A-IoT device, and the second identifier is used to identify the first A-IoT service. For example, for an inventory service, A-IoT service request #1 is an inventory request; for a command service, A-IoT service request #1 is a command request, such as a read request, write request, disable request, enable request, deactivate request, or lock request, etc.

[0509] Optionally, in step 2502, the source gNB sends an A-IoT service request #2 to the UE, and correspondingly, the UE receives the A-IoT service request #2 from the source gNB.

[0510] Specifically, A-IoT service request #2 is used to request the execution of a first A-IoT service. A-IoT service request #2 may include at least one of the following: a first identifier or a second identifier. The first identifier is used to identify the A-IoT device, and the second identifier is used to identify the first A-IoT service.

[0511] Optionally, the A-IoT service request #2 may further include resource configuration information for configuring a first resource for the UE to perform the first A-IoT service. For example, the resource configuration information of the first resource may include time-domain resource configuration information and / or frequency-domain resource configuration information. Optionally, the resource configuration information may further include the maximum power transmitted by the terminal to the A-IoT device.

[0512] For example, for inventory management services, A-IoT service request #2 is an inventory management request; for command services, A-IoT service request #2 is a command request, such as a read request, write request, disable request, enable request, deactivate request, or lock request, etc.

[0513] Steps 2501 and 2502 above apply to the RRC-based solution architecture. Descriptions of A-IoT service request #1 and A-IoT service request #2 can be found in method 2100.

[0514] Optionally, in step 2503, the A-IoT CN sends an A-IoT service request #3 to the UE via a NAS message or a PDU session, and correspondingly, the UE receives the A-IoT service request #3 from the A-IoT CN.

[0515] Specifically, A-IoT service request #3 is used to request the execution of a first A-IoT service. A-IoT service request #3 may include at least one of the following: a first identifier or a second identifier. The first identifier is used to identify the A-IoT device, and the second identifier is used to identify the first A-IoT service.

[0516] For a NAS / UP-based solution architecture, the first resource for executing the first A-IoT service can be configured for the terminal in the following way.

[0517] Method 1: The A-IoT CN sends an AIoT resource request to the previous serving gNB to trigger the previous serving gNB to allocate the first resource to the UE.

[0518] Method 2: After receiving AIoT service request #3 included in the NAS / PDU Session, the UE requests AIoT resources from the upstream service gNB, and then the upstream service gNB allocates the first resource to the UE.

[0519] Step 2503 above applies to NAS / UP-based solution architectures. A detailed description of A-IoT service request #3 can be found in step 2101, which describes A-IoT service request #1.

[0520] Furthermore, the previous serving gNB can pre-configure the first resource to the UE via RRC messages (as in step 2502) for the UE to use in RRC connected state. Optionally, the UE can continue to use the first resource to perform the first A-IoT service when an RLF is discovered. For example, the configuration information for configuring the first resource includes time-domain resource configuration information and / or frequency-domain resource configuration information. Optionally, the configuration information may also include the maximum power sent by the terminal to the A-IoT device. Optionally, the configuration information may also include a first timer, during which the UE can use the first resource; if the first timer expires, the UE stops using the first resource. The first timer can be a timer already defined in the existing protocol or a newly defined timer, without restriction. Step 2504: During the execution of the first A-IoT service, the UE discovers an RLF.

[0521] Step 2505: The UE performs cell reselection or cell selection and reconnects to the new gNB.

[0522] Step 2506: The UE sends RRC message #2 to the new gNB, and the new gNB receives RRC message #2 from the UE.

[0523] RRC message #2 (corresponding to message #5) includes information #2. A description of information #2 can be found in step 2202.

[0524] RRC message #2 can be an RRC message, such as an RRC reconstruction request message, a UAI message, an A-IoT resource request message, or other RRC messages.

[0525] Step 2507: The new gNB sends a UE context request message (e.g., retrieve UE context request) #1 to the previous serving gNB. Correspondingly, the previous serving gNB receives the UE context request message #1 from the new gNB.

[0526] Step 2508: The previous serving gNB sends a retrieve UE context response message (e.g., retrieve UE context response) #1 to the new gNB. Correspondingly, the new gNB receives the retrieve UE context response message #1 from the previous serving gNB.

[0527] Step 2509: The new gNB determines whether the UE should continue to execute the first A-IoT service.

[0528] For example, the new gNB determines whether the UE can continue to perform the current first A-IoT service and / or whether the UE can continue to act as a reader / writer based on the area information related to the first A-IoT service and / or the type of the UE.

[0529] If the new gNB determines that the UE should continue performing the first A-IoT service, then proceed to step 2510. If the new gNB determines that the UE should not continue performing the first A-IoT service, and / or the UE cannot continue to act as a reader / writer, then the relevant procedures for RRC reconstruction can proceed normally.

[0530] It should be noted that the previous serving gNB or A-IoT CN can also determine whether the UE should continue to execute the first A-IoT service and instruct the new gNB on the result, without restriction.

[0531] Step 2510: The new gNB sends RRC message #3 to the UE, and the UE receives RRC message #3 from the new gNB.

[0532] RRC message #3 may include second information and / or fourth information. The second information indicates a first resource, which is used by the UE to communicate with A-IoT devices, or in other words, the first resource is used by the UE to perform a first A-IoT service. The fourth information is first CW configuration information. A detailed description of the first resource and the first CW configuration information can be found in method 1800.

[0533] Optionally, RRC message #3 may also include a second identifier.

[0534] Optionally, RRC message #3 may also include information instructing the UE to continue performing the first A-IoT service and / or the UE to continue acting as a reader / writer.

[0535] For example, RRC message #3 can be any RRC message, including reused existing RRC messages and new RRC messages, without restriction. For instance, RRC message #3 can be an RRC reconstruction message, an A-IoT resource request confirmation / response message, or other RRC messages.

[0536] Optionally, in step 2511, the UE sends an RRC establishment completion message to the new gNB to notify that the RRC reconstruction is complete.

[0537] Subsequently, the UE can continue to execute the first A-IoT service based on the first resource indicated by the second information and / or the first CW configuration information in the fourth information. Based on method 2500, in the RLF scenario, the UE can send A-IoT service-related information (including inferred information) to the new gNB, which is used by the target gNB to configure A-IoT resources and / or CW configuration information for the UE. This helps improve the continuity of A-IoT services, thereby ensuring the performance of A-IoT services and improving the user service experience.

[0538] The following describes the scheme for information related to inter-station A-IoT services in conjunction with Figure 26.

[0539] Figure 26 is a schematic flowchart of a communication method 2600 provided in an embodiment of this application.

[0540] Method 2600 includes at least a portion of the following:

[0541] Step 2601: The terminal executes the first A-IoT service and discovers RLF during the execution of the first A-IoT service.

[0542] Step 2602: The terminal sends the seventeenth message to the first access network device, and correspondingly, the first access network device receives the seventeenth message from the terminal.

[0543] Among them, the seventeenth message is used to request the terminal to rebuild the RRC connection, such as the seventeenth message being an RRC rebuild request message.

[0544] Step 2603: The first access network device sends the eighteenth message to the second access network device, and correspondingly, the second access network device receives the eighteenth message from the first access network device.

[0545] The eighteenth message is used to retrieve the UE context; for example, the eighteenth message can be "retrieve UE context request".

[0546] In addition, the eighteenth message can be any other XnAP message, which can be a reused existing XnAP message or a new XnAP message, without restriction.

[0547] Step 2604: The second access network device sends a thirteenth message to the first access network device, and correspondingly, the first access network device receives the thirteenth message from the second access network device.

[0548] The thirteenth message includes first information, which is used to configure, schedule or determine a first resource for the terminal. For a detailed description of the first resource and the first information, please refer to Method 1800, which will not be elaborated here.

[0549] For example, the thirteenth message can be a UE context response message (such as retrieve UE context response).

[0550] In addition, the thirteenth message can be any other XnAP message, which can be a reused existing XnAP message or a new XnAP message, without restriction.

[0551] In some implementations, the second access network device can obtain the first information through the fifteenth message sent by the terminal.

[0552] In some other implementations, the second network device can obtain some information about the first A-IoT service, and the second network device can determine the first information based on this information.

[0553] Step 2605: The first access network device determines the second information based on the first information.

[0554] The second information is used to indicate the first resource.

[0555] For example, the first access network device can allocate first resources to the terminal based on the first information, and then determine the second information.

[0556] Step 2606: The first access network device sends the fourteenth message to the terminal, and correspondingly, the terminal receives the fourteenth message from the first access network device.

[0557] The fourteenth message is used to rebuild the terminal's RRC connection, such as the RRC rebuild message. The fourteenth message includes second information.

[0558] In addition, the fourteenth message can be any other RRC message, which can be a reused existing RRC message or a new RRC message, without restriction.

[0559] It should be noted that steps 2605 and 2606 can also be replaced by: the first access network device sending the fourteenth message to the terminal based on the first information.

[0560] In other embodiments of this application, the second access network device may also provide the first access network device with information for configuring a carrier. The information for configuring the carrier and the information for configuring A-IoT resources may be carried in the same message or in different messages, without limitation. In some implementations, the thirteenth message further includes third information, wherein the third information is used to configure the carrier, determine the first carrier configuration information, or determine whether to send a carrier and / or charge to the first device related to the first A-IoT service; the fourteenth message further includes fourth information, which is the first carrier configuration information. In this case, method 2300 may further include: the first access network device determining the fourth information based on the third information. If the second access network device obtains information related to the first A-IoT service from the terminal, then the fifteenth message may also include the third information.

[0561] In some other embodiments of this application, the first information is also used to configure a third resource, which is used for communication between the terminal and the first access network device, such as an NR Uu air interface resource.

[0562] Inactive terminal scenarios

[0563] The following describes the scheme for the UE to report A-IoT service-related information to the first access network device, with reference to Figures 27 and 28.

[0564] Figure 27 is a schematic flowchart of a communication method 2700 provided in an embodiment of this application.

[0565] Method 2700 includes at least a portion of the following.

[0566] Step 2701: The terminal in the non-connected state executes the first A-IoT service.

[0567] The non-connected state can refer to the RRC idle state or the RRC inactive state.

[0568] Step 2702: During the execution of the first A-IoT service, a seventh message is sent to the first access network device, and correspondingly, the first access network device receives the seventh message from the terminal.

[0569] The seventh message is used to request the resumption of a suspended RRC connection of the terminal, such as an RRC Resume Request message. The seventh message includes first information, which is used to configure, schedule, or determine a first resource for the terminal. A detailed description of the first resource and the first information can be found in Method 1800, and will not be elaborated further.

[0570] Step 2703: The first access network device determines the second information based on the first information.

[0571] The second information is used to indicate the first resource.

[0572] For example, the first access network device can allocate first resources to the terminal based on the first information, and then determine the second information.

[0573] Step 2704: The first access network device sends the eighth message to the terminal, and correspondingly, the terminal receives the eighth message from the first access network device.

[0574] The eighth message includes the second information. The eighth message can be an RRC message. For example, the eighth message is used to restore the terminal's RRC connection; such as an RRC Resume message. For example, the eighth message can also be other RRC messages, including reused existing RRC messages and new RRC messages, without limitation.

[0575] It should be noted that steps 2703 and 2704 can also be replaced by: the first access network device sending the eighth message to the terminal based on the first information.

[0576] In other embodiments of this application, the terminal may also provide the first access network device with information for configuring the carrier. The information for configuring the carrier and the information for configuring A-IoT resources may be carried in the same message or in different messages, without limitation. In some implementations, the seventh message further includes third information, wherein the third information is used to configure the carrier, determine the first carrier configuration information, or determine whether to send a carrier and / or charge to the first device related to the first A-IoT service, and the eighth message further includes fourth information, which is the first carrier configuration information. In this case, method 2700 may further include: the first access network device determining the fourth information based on the third information.

[0577] In some other embodiments of this application, the first information is also used to configure a third resource, which is used for communication between the terminal and the first access network device, such as an NR Uu air interface resource.

[0578] Subsequently, the UE can continue to perform the first A-IoT service based on the first resource indicated by the second information and / or the first carrier configuration information in the fourth information.

[0579] Figure 28 is a schematic flowchart of a communication method 2800 provided in an embodiment of this application.

[0580] As shown in Figure 28, taking the terminal as UE, the core network element as A-IoT CN, the first access network device as the new gNB, and the second access network device as the previous serving gNB as an example, A-IoT CN can be A-IoTF, TMF, A-IoTMF network elements or other core network elements / nodes / devices that support / enable A-IoT, and the specific name is not limited.

[0581] In method 2800, the UE reports information related to A-IoT services to the new gNB, which is used by the new gNB to configure A-IoT resources and / or CW for the UE. Method 2800 includes at least some of the following.

[0582] Optionally, in step 2801, the A-IoT CN sends an A-IoT service request #1 to the source gNB via an XXAP / NGAP message, and correspondingly, the source gNB receives the A-IoT service request #1 from the A-IoT CN.

[0583] Specifically, A-IoT service request #1 is used to request the execution of a first A-IoT service. A-IoT service request #1 may include at least one of the following: a first identifier or a second identifier. The first identifier is used to identify the A-IoT device, and the second identifier is used to identify the first A-IoT service.

[0584] Optionally, in step 2802, the source gNB sends A-IoT service request #2 to the UE, and correspondingly, the UE receives A-IoT service request #2 from the source gNB.

[0585] Specifically, A-IoT service request #2 is used to request the execution of a first A-IoT service. A-IoT service request #2 may include at least one of the following: a first identifier or a second identifier. The first identifier is used to identify the A-IoT device, and the second identifier is used to identify the first A-IoT service.

[0586] Steps 2801 and 2802 above apply to the RRC-based solution architecture. Descriptions of A-IoT service request #1 and A-IoT service request #2 can be found in method 2100.

[0587] Optionally, in step 2803, the A-IoT CN sends an A-IoT service request #3 to the UE via a NAS message or a PDU session, and correspondingly, the UE receives the A-IoT service request #3 from the A-IoT CN.

[0588] Specifically, A-IoT service request #3 is used to request the execution of a first A-IoT service. A-IoT service request #3 may include at least one of the following: a first identifier or a second identifier. The first identifier is used to identify the A-IoT device, and the second identifier is used to identify the first A-IoT service.

[0589] Step 2803 above applies to NAS / UP-based solution architectures. A detailed description of A-IoT service request #3 can be found in step 2101, which describes A-IoT service request #1.

[0590] The description of steps 2801-2803 can be found in steps 2501-2503.

[0591] Step 2804: The UE in the non-connected state executes the first A-IoT service.

[0592] In the embodiments of this application, the gNB can paging a non-connected state (RRC inactive or RRC idle) UE. The paging cause may be that the base station determines that there is interference between UE Readers and needs to allocate / schedule new A-IoT resources and / or NR resources to the UE Readers. For this purpose, it is necessary to paging the non-connected state UE Readers into the RRC connected state so that the UE Readers can receive new A-IoT resources and / or NR resources in the connected state. Optionally, the new A-IoT resources (hereinafter referred to as the first resources) can be used to perform A-IoT services when the UE (again) enters the non-connected state. Further optionally, the new A-IoT resource configuration may include a valid timer, that is, the UE uses the resources to perform A-IoT services during the valid timer operation period, and stops using the resources when the timer expires. The timer may be predefined by the protocol or newly defined.

[0593] Step 2805: During the execution of the first A-IoT service, the UE sends an RRC recovery request message #1 (corresponding to the seventh message) to the new gNB. Correspondingly, the new gNB receives the RRC recovery request message #1 from the UE.

[0594] The RRC recovery request message #1 includes information #2. A description of information #2 can be found in step 2202.

[0595] In step 2806, the new gNB sends a UE context request message (e.g., retrieve UE context request) #1 to the previous serving gNB. Correspondingly, the previous serving gNB receives the UE context request message #1 from the new gNB.

[0596] Step 2807: The previous serving gNB sends a retrieve UE context response message (e.g., retrieve UE context response) #1 to the new gNB. Correspondingly, the new gNB receives the retrieve UE context response message #1 from the previous serving gNB.

[0597] Step 2808: The new gNB determines whether the UE should continue to execute the first A-IoT service.

[0598] For example, the new gNB determines whether the UE can continue to perform the current first A-IoT service and / or whether the UE can continue to act as a reader / writer based on the area information related to the first A-IoT service and / or the type of the UE.

[0599] If the new gNB determines that the UE should continue performing the first A-IoT service, then proceed to step 2809. If the new gNB determines that the UE should not continue performing the first A-IoT service, and / or the UE cannot continue to act as a reader / writer, then the RRC recovery process can proceed normally.

[0600] It should be noted that the previous serving gNB or A-IoT CN can also determine whether the UE should continue to execute the first A-IoT service and instruct the new gNB on the result, without restriction.

[0601] Step 2809: The new gNB sends RRC recovery message #1 to the UE, and the UE receives RRC recovery message #1 from the new gNB.

[0602] The RRC recovery message #1 may include second information and / or fourth information. The second information indicates a first resource, which is used by the UE to communicate with A-IoT devices, or in other words, the first resource is used by the UE to perform a first A-IoT service. The fourth information is first CW configuration information. A detailed description of the first resource and the first CW configuration information can be found in method 1800.

[0603] Optionally, RRC recovery message #1 may also include a second identifier.

[0604] Optionally, RRC recovery message #1 may also include information instructing the UE to continue performing the first A-IoT service and / or the UE to continue acting as a reader / writer.

[0605] Subsequently, the UE can continue to execute the first A-IoT service based on the first resource indicated by the second information and / or the first CW configuration information in the fourth information.

[0606] Based on method 2800, a UE in a disconnected state can send A-IoT service-related information (including inferred information) to a new gNB. This information is used by the target gNB to configure A-IoT resources and / or CW configuration information for the UE, which helps improve the continuity of A-IoT services, thereby ensuring the performance of A-IoT services and improving the user experience.

[0607] The following describes the scheme for information related to inter-station A-IoT services in conjunction with Figure 29.

[0608] Figure 29 is a schematic flowchart of a communication method 2900 provided in an embodiment of this application.

[0609] Method 2900 includes at least a portion of the following.

[0610] Step 2901: The terminal in the non-connected state executes the first A-IoT service.

[0611] Step 2902: The terminal sends the seventeenth message to the first access network device, and correspondingly, the first access network device receives the seventeenth message from the terminal.

[0612] Among them, the seventeenth message is used to request the terminal to restore the RRC connection, such as the seventeenth message being an RRC restoration request message.

[0613] Step 2903: The first access network device sends the eighteenth message to the second access network device, and correspondingly, the second access network device receives the eighteenth message from the first access network device.

[0614] The eighteenth message is used to retrieve the UE context; for example, the eighteenth message can be "retrieve UE context request".

[0615] In addition, the eighteenth message can be any other XnAP message, which can be a reused existing XnAP message or a new XnAP message, without restriction.

[0616] In step 2904, the second access network device sends a thirteenth message to the first access network device, and correspondingly, the first access network device receives the thirteenth message from the second access network device.

[0617] The thirteenth message includes first information, which is used to configure, schedule or determine a first resource for the terminal. For a detailed description of the first resource and the first information, please refer to Method 1800, which will not be elaborated here.

[0618] For example, the thirteenth message can be a UE context response message (such as retrieve UE context response).

[0619] In addition, the thirteenth message can be any other XnAP message, which can be a reused existing XnAP message or a new XnAP message, without restriction.

[0620] In some implementations, the second access network device can obtain the first information through the fifteenth message sent by the terminal.

[0621] In some other implementations, the second network device can obtain some information about the first A-IoT service, and the second network device can determine the first information based on this information.

[0622] Step 2905: The first access network device determines the second information based on the first information.

[0623] The second information is used to indicate the first resource.

[0624] For example, the first access network device can allocate first resources to the terminal based on the first information, and then determine the second information.

[0625] Step 2906: The first access network device sends the fourteenth message to the terminal, and correspondingly, the terminal receives the fourteenth message from the first access network device.

[0626] The fourteenth message is used to restore the terminal's RRC connection, such as the RRC recovery message. The fourteenth message includes second information.

[0627] In addition, the fourteenth message can be any other RRC message, which can be a reused existing RRC message or a new RRC message, without restriction.

[0628] It should be noted that steps 2905 and 2906 can also be replaced by: the first access network device sending the fourteenth message to the terminal based on the first information.

[0629] In other embodiments of this application, the second access network device may also provide the first access network device with information for configuring a carrier. The information for configuring the carrier and the information for configuring A-IoT resources may be carried in the same message or in different messages, without limitation. In some implementations, the thirteenth message further includes third information, wherein the third information is used to configure the carrier, determine the first carrier configuration information, or determine whether to send a carrier and / or charge to the first device related to the first A-IoT service; the fourteenth message further includes fourth information, which is the first carrier configuration information. In this case, method 2300 may further include: the first access network device determining the fourth information based on the third information. If the second access network device obtains information related to the first A-IoT service from the terminal, then the fifteenth message may also include the third information.

[0630] In some other embodiments of this application, the first information is also used to configure a third resource, which is used for communication between the terminal and the first access network device, such as an NR Uu air interface resource.

[0631] Currently, base stations can configure A-IoT resources for terminals while simultaneously configuring a first timer for the terminal. During the operation of the first timer, the terminal can use the A-IoT resource to communicate with A-IoT devices. When the first timer expires and / or the duration of the A-IoT resource expires, the terminal stops using the A-IoT resource. Although the terminal stops using the A-IoT resource, the A-IoT device will still continue to monitor A-IoT air interface signaling, resulting in unnecessary power consumption.

[0632] To address the aforementioned problems, this application provides a communication method and a communication device to reduce power loss in the device.

[0633] Figure 30 is a schematic flowchart of a communication method 3000 provided in an embodiment of this application.

[0634] Method 3000 includes at least a portion of the following:

[0635] Step 3001: The terminal or access network device determines that the first resource has failed.

[0636] The first resource is used by the terminal to execute the first A-IoT service or for the terminal to communicate with A-IoT devices. For example, the first resource may be an A-IoT radio resource, which can include time-domain resources and / or frequency-domain resources. The effective area of ​​the first resource can be a single cell or multiple cells. The resource configuration information of the first resource includes time-domain resource configuration information and / or frequency-domain resource configuration information. Optionally, the resource configuration information may also include the maximum power transmitted by the terminal to the A-IoT device. The time-domain resource configuration information can be duration. If the terminal determines that the duration configured by the access network device is insufficient to complete the first A-IoT service, the terminal can request A-IoT resources (such as duration) from the access network device, and then the access network device will allocate or schedule A-IoT resources (such as duration) to the terminal.

[0637] In some implementations, the terminal determines that the first resource has expired when at least one of the following conditions is met: the first timer corresponding to the first resource times out, or the duration of the first resource expires. The expiration of the first resource's duration can refer to the expiration of a time-domain resource within the first resource; for example, if the time-domain resource in the first resource is 10 seconds, the first resource will expire after 10 seconds. Step 3002: The terminal or access network device sends a ninth message to the A-IoT device related to the first A-IoT service. Correspondingly, the A-IoT device related to the first A-IoT service receives the ninth message from the terminal or access network device.

[0638] The ninth piece of information indicates the time for ceasing monitoring of A-IoT interface signaling, or the time for ceasing use of the first resource. For example, the ninth piece of information can be configured by the terminal itself, or by the base station, or it can be predefined by the protocol; there are no restrictions.

[0639] It is understandable that the A-IoT interface signaling is associated with the first A-IoT service, or in other words, the A-IoT interface signaling is used to execute the first A-IoT service. Therefore, stopping the monitoring of the A-IoT interface signaling or stopping the use of the first resource indicates that the A-IoT device stops executing or does not execute the first A-IoT service.

[0640] Optionally, the A-IoT interface signaling or A-IoT air interface signaling in the embodiments of this application can be replaced with the first signaling, which is related to the first A-IoT service. In other words, this application does not limit the specific name of the first signaling.

[0641] In the embodiments of this application, the A-IoT interface (A-IoT radio) can be understood as: the interface between the A-IoT device and the A-IoT enabled UE, or the interface between the A-IoT device and the A-IoT RAN node, etc.

[0642] In some implementations, the ninth information includes at least one of the following: a second timer, a first duration, or a periodic mode, wherein a periodic mode includes a second time period and a third time period, and the time for stopping monitoring A-IoT interface signaling is: during the operation of the second timer, within the first duration, or within one or more second time periods.

[0643] Step 3003: The A-IoT device related to the first A-IoT service stops monitoring A-IoT interface signaling, stops using the first resource, or goes into hibernation within the time indicated by the ninth information.

[0644] For example, the start time for stopping monitoring A-IoT interface signaling or stopping the use of the first resource is the moment when the A-IoT device receives the ninth information.

[0645] In one implementation, if the ninth information in step 3302 indicates a second timer, the A-IoT device can stop monitoring A-IoT interface signaling, stop using the first resource, or go into sleep mode during the second timer's operation. After the second timer expires, it can resume monitoring A-IoT interface signaling, resume use (or continue using), or release the first resource. For example, if the second timer's duration is 1 hour, the A-IoT device can start the second timer while sending inventory results (e.g., the A-IoT device's identifier). Within 1 hour after the second timer starts, the second resource is deactivated, and the A-IoT device cannot use the first resource, or in other words, the A-IoT device stops monitoring A-IoT interface signaling. After the second timer expires, that is, after 1 hour, the A-IoT device can resume monitoring A-IoT interface signaling, or resume use or continue using the first resource, for example, using the first resource to perform other A-IoT services (e.g., a second A-IoT service).

[0646] In one implementation, if the first information indication cycle mode is in step 3002, the A-IoT device can stop monitoring A-IoT interface signaling or stop using the first resource or go into sleep mode during a second time period (e.g., T1); and resume monitoring A-IoT interface signaling or resume use (or continue use) or release the first resource during a third time period (e.g., T2). For example, if the second time period is time slot 1 to time slot 3 and the third time period is time slot 4 to time slot 8, the A-IoT device can stop monitoring A-IoT interface signaling or stop using the first resource or go into sleep mode during time slots 1 to 3, meaning the A-IoT device cannot use the first resource during time slots 1 to 3; and during time slots 4 to 8, the A-IoT device can resume monitoring A-IoT interface signaling or resume use or continue using the first resource, for example, using the first resource to perform other A-IoT services (e.g., a second A-IoT service).

[0647] In one implementation, if the first information in step 3002 indicates a first duration, the A-IoT device can stop monitoring A-IoT interface signaling, stop using the first resource, or go into sleep mode during the first duration; and after the first duration ends, it can resume monitoring A-IoT interface signaling, resume use (or continue using), or release the first resource. Optionally, the time unit of the first duration (Duration) can be absolute time (e.g., minutes / seconds / milliseconds) or relative time (e.g., superframes / frames / subframes / slots / symbols). Optionally, the first duration can be a period of time, such as 1 hour, or it can be represented by specific time information (e.g., from x o'clock x minutes x seconds to y o'clock y minutes y seconds), etc., and this application does not limit this.

[0648] Optionally, method 3000 may further include: after the time indicated by the ninth information, the A-IoT device associated with the first A-IoT service resumes monitoring A-IoT interface signaling or resumes using the first resource. For example, after the second timer expires, or during the fourth time period, or after the second duration ends, the A-IoT device resumes monitoring A-IoT interface signaling or resumes using the first resource.

[0649] Based on method 3000, the access network device or terminal sends a ninth message to the A-IoT device instructing it to stop monitoring A-IoT interface signaling or to stop using the first resource for a specified period, or to allow the A-IoT device to sleep for a specified time. This causes the A-IoT device to stop monitoring A-IoT interface signaling or to stop using the first resource during the second timer's operation, the second time period, or the first duration, which helps reduce the power consumption of the A-IoT device. Furthermore, if monitoring A-IoT interface signaling continues or the first resource is used or resumed after the second timer expires, or after the third time period or the first duration ends, resource waste can be avoided and resource utilization can be improved.

[0650] The following describes method 3000 in a specific scenario.

[0651] RLF scene

[0652] Figure 31 is a schematic flowchart of a communication method 3100 provided in an embodiment of this application.

[0653] As shown in Figure 31, taking the terminal as UE, the terminal as reader / writer, and the core network element as A-IoT CN as an example, A-IoT CN can be A-IoTF, TMF, A-IoTMF network elements or other core network elements / nodes / devices that support / enable A-IoT, and the specific name is not limited.

[0654] Method 3100 includes at least a portion of the following:

[0655] Optionally, in step 3101, the A-IoT CN sends an A-IoT service request #4 to the previous serving gNB via an XXAP / NGAP message. Correspondingly, the previous serving gNB receives the A-IoT service request #4 from the A-IoT CN.

[0656] Among them, A-IoT service request #4 is used to request the execution of the first A-IoT service. For example, for inventory service, A-IoT service request #4 is an inventory request; for command service, A-IoT service request #4 is a command request, such as a read request, write request, disable request, enable request, deactivate request, or lock request, etc.

[0657] Optionally, in step 3102, the previous serving gNB sends an A-IoT service request #5 to the UE, and correspondingly, the UE receives the A-IoT service request #5 from the previous serving gNB.

[0658] Specifically, A-IoT service request #5 is used to request the execution of a first A-IoT service. Optionally, A-IoT service request #5 may include resource configuration information for configuring a first resource for the UE to execute the first A-IoT service. For example, the resource configuration information of the first resource may include time-domain resource configuration information and / or frequency-domain resource configuration information. Optionally, the resource configuration information may also include the maximum power transmitted by the terminal to the A-IoT device.

[0659] For example, for inventory management services, A-IoT service request #5 is an inventory management request; for command services, A-IoT service request #5 is a command request, such as a read request, write request, disable request, enable request, deactivate request, or lock request.

[0660] Steps 3101 and 3102 above apply to RRC-based solution architectures.

[0661] Optionally, in step 3103, the A-IoT CN sends an A-IoT service request #6 to the UE via a NAS message or a PDU session, and correspondingly, the UE receives the A-IoT service request #6 from the A-IoT CN.

[0662] Among them, A-IoT service request #6 is used to request the execution of the first A-IoT service.

[0663] Step 3103 above applies to NAS / UP-based solution architecture. For NAS / UP-based solution architecture, the first resource for executing the first A-IoT service can be configured for the terminal in the following manner.

[0664] Method 1: The A-IoT CN sends an AIoT resource request to the previous serving gNB to trigger the previous serving gNB to allocate the first resource to the UE.

[0665] Method 2: After receiving AIoT service request #5 included in the NAS / PDU Session, the UE requests AIoT resources from the upstream service gNB, and then the upstream service gNB allocates the first resource to the UE.

[0666] Through steps 3101-3102 or 3103, the UE is configured with a first resource, which is used to perform a first A-Io service.

[0667] Furthermore, the previous serving gNB can pre-configure the first resource to the UE via RRC messages (as in step 3102) for the UE to use in RRC connected state. Optionally, the UE can continue to use the first resource to perform the first A-IoT service when an RLF is discovered. For example, the configuration information for configuring the first resource includes time-domain resource configuration information and / or frequency-domain resource configuration information. Optionally, the configuration information may also include the maximum power transmitted by the terminal to the A-IoT device. Optionally, the configuration information may also include a first timer, during which the UE can use the first resource; if the first timer expires, the UE stops using the first resource. The first timer can be a timer already defined in an existing protocol or a newly defined timer, without limitation.

[0668] Step 3104: During the execution of the first A-IoT service, the UE discovers an RLF.

[0669] Step 3105, the UE determines that the first resource has failed.

[0670] In some implementations, the UE determines that the first resource has failed when at least one of the following conditions is met: the first timer corresponding to the first resource times out, or the duration of the first resource expires. The expiration of the first resource's duration can refer to the expiration of the time-domain resource within the first resource. For example, if the time-domain resource in the first resource is 10 seconds, the first resource will fail after 10 seconds.

[0671] Step 3106: The UE sends the ninth information to the A-IoT device related to the first A-IoT service, and correspondingly, the A-IoT device related to the first A-IoT service receives the ninth information from the UE.

[0672] The ninth message indicates the time for ceasing monitoring of A-IoT interface signaling, or the time for ceasing use of the first resource. A detailed description of the ninth message can be found in Method 3000.

[0673] Step 3107: The A-IoT device related to the first A-IoT service stops or resumes monitoring the A-IoT interface signaling according to the ninth information.

[0674] For the specific implementation of step 3107, please refer to step 3003.

[0675] Figure 32 is a schematic flowchart of a communication method 3200 provided in an embodiment of this application.

[0676] As shown in Figure 32, taking the terminal as UE, the terminal as reader / writer, and the core network element as A-IoT CN as an example, A-IoT CN can be A-IoTF, TMF, A-IoTMF network elements or other core network elements / nodes / devices that support / enable A-IoT, and the specific name is not limited.

[0677] Method 3200 includes at least a portion of the following:

[0678] Optionally, in step 3201, the A-IoT CN sends an A-IoT service request #7 to the previous serving gNB via an XXAP / NGAP message. Correspondingly, the previous serving gNB receives the A-IoT service request #7 from the A-IoT CN.

[0679] Among them, A-IoT service request #4 is used to request the execution of the first A-IoT service.

[0680] Optionally, in step 3202, the previous serving gNB sends an A-IoT service request #8 to the UE, and correspondingly, the UE receives the A-IoT service request #8 from the previous serving gNB. The UE is in connected state.

[0681] Among them, A-IoT service request #8 is used to request the execution of the first A-IoT service.

[0682] Steps 3201 and 3202 above apply to RRC-based solution architectures.

[0683] Optionally, in step 3203, the A-IoT CN sends an A-IoT service request #9 to the UE via a NAS message or a PDU session, and correspondingly, the UE receives the A-IoT service request #9 from the A-IoT CN.

[0684] Among them, A-IoT service request #9 is used to request the execution of the first A-IoT service.

[0685] Step 3203 above applies to NAS / UP-based solution architectures.

[0686] The description of steps 3201-3203 can be found in steps 3101-3103.

[0687] Step 3204: The previous serving gNB sends an RRC release message to the UE, and the UE receives the RRC release message from the previous serving gNB.

[0688] The RRC release message is used to release the UE's RRC connection.

[0689] For example, the RRC release message carries a suspend configuration and is used to configure a first resource for the UE to perform the first A-IoT service.

[0690] Step 3205: The UE enters inactive mode and uses the first resource to execute the first A-IoT service.

[0691] In the embodiments of this application, the gNB can paging a non-connected state (RRC inactive or RRC idle) UE. The paging cause may be that the base station determines that there is interference between UE Readers and needs to allocate / schedule new A-IoT resources and / or NR resources to the UE Readers. For this purpose, it is necessary to paging the non-connected state UE Readers into the RRC connected state so that the UE Readers can receive new A-IoT resources and / or NR resources in the connected state. Optionally, the new A-IoT resources (hereinafter referred to as the first resources) can be used to perform A-IoT services when the UE (again) enters the non-connected state. Further optionally, the new A-IoT resource configuration may include a valid timer, that is, the UE uses the resources to perform A-IoT services during the valid timer operation period, and stops using the resources when the timer expires. The timer may be predefined by the protocol or newly defined.

[0692] Step 3206: UE randomly accesses and receives gNB.

[0693] Step 3207: The UE sends an RRC recovery request message to the receiving gNB, and the receiving gNB receives the RRC recovery request message from the UE.

[0694] Step 3208: The UE determines that the first resource has failed.

[0695] Step 3209: The UE sends the ninth information to the A-IoT device related to the first A-IoT service, and correspondingly, the A-IoT device related to the first A-IoT service receives the ninth information from the UE.

[0696] The ninth message indicates the time for ceasing monitoring of A-IoT interface signaling, or the time for ceasing use of the first resource. A detailed description of the ninth message can be found in Method 3000.

[0697] Step 3210: The A-IoT device related to the first A-IoT service stops or resumes monitoring the A-IoT interface signaling according to the ninth information.

[0698] For a detailed implementation of step 3210, please refer to step 3003.

[0699] It should be understood that, in the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terms and / or descriptions of different embodiments are consistent and can be referenced by each other, and the technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0700] The method embodiments provided in this application have been described in detail above with reference to Figures 18 to 32. The device embodiments of this application will be described below with reference to Figures 33 to 35.

[0701] It is understood that, in order to achieve the functions in the above embodiments, the devices in Figures 33 to 35 include hardware structures and / or software modules corresponding to each function. These devices can be used to implement the functions of the first access network device, the second access network device, the terminal, or the first device in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments. Those skilled in the art should readily recognize that, based on the units and method steps of the various examples described in conjunction with the embodiments disclosed in this application, this application can be implemented in hardware or a combination of hardware and computer software.

[0702] Figure 33 is a schematic diagram of a device provided in an embodiment of this application.

[0703] This application embodiment can divide the first access network device, the second access network device, the terminal, or the first device into functional units according to the above method examples. For example, each function can be divided into different functional units, or two or more functions can be integrated into one unit. Each function can be implemented in hardware or as a software functional module. It should be noted that the division shown in Figure 33 is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0704] As shown in Figure 33, the device 10 includes a transceiver unit 11 and a processing unit 12.

[0705] In one implementation, when device 10 is used to implement the functions of the first access network device in the above method embodiments, transceiver unit 11 is used to execute the transceiver steps of the first access network device, such as steps 1801, 1803, 1804, 1901, 1903, 2002, 2004, 2103, 2105, 2107, 2203, 2204, 2206, 2207, 2208, 2210, 2211, 2301, 2302, 2304, 2306, 2402, and 2404. 2505, 2506, 2507, 2508, 2510, 2511, 2602, 2603, 2604, 2606, 2702, 2704, 2805, 2806, 2807, 2809, 2902, 2903, 2904, 2906. Processing unit 12 is used to execute the processing steps of the first access network device, such as steps 1802, 1902, 2003, 2104, 2305, 2403, 2509, 2605, 2703, 2808, 2905. When device 10 is used to implement the functions of the second access network device in the above method embodiments, transceiver unit 11 is used to execute the transceiver steps of the second access network device, such as steps 1806, 1081, 1804, 1805, 2001, 2002, 2004, 2005, 2101, 2102, 2103, 2105, 2106, 2201, 2202, 2203, 2204, 2205, 2301, 2302, 2501, 2502, 2503, 2507, 2508, 2603, 2604, 2801, 2802, 2803, 2806, 2807, 2903, 2904, and processing unit 12 is used to execute the processing steps of the second access network device. When device 10 is used to implement the functions of the terminal in the above method embodiments, transceiver unit 11 is used to execute the terminal's transceiver steps, such as steps 1806, 1803, 1805, 1901, 1903, 2001, 2005, 2102, 2106, 2107, 2201, 2202, 2205, 2206, 2207, 2211, 2303, 2304, 2306. 2402, 2402, 2502, 2503, 2505, 2526, 2510, 2511, 2602, 2606, 2702, 2704, 2802, 2803, 2805, 2809, 2902, 2906, the processing unit 12 is used to execute the terminal's processing steps, such as steps 2401, 2504, 2601, 2701, 2804, 2901.

[0706] In another implementation, when device 10 is used to implement the functions of the terminal in the above method embodiments, transceiver unit 11 is used to execute the terminal's transceiver steps, such as steps 3002, 3101, 3103, 3106, 3202, 3203, 3204, 3206, 3207, and 3209, and processing unit 12 is used to execute the terminal's processing steps, such as steps 13001, 3104, 3105, 3205, and 3208. When device 10 is used to implement the functions of the first device in the above method embodiments, transceiver unit 11 is used to execute the first device's transceiver steps, such as steps 3002, 3106, and 3209, and processing unit 12 is used to execute the first device's processing steps, such as steps 3003, 3107, and 3210.

[0707] Optionally, the device 10 also includes a storage unit 13 for storing instructions and / or data.

[0708] For a more detailed description of the transceiver unit 11 and the processing unit 12, please refer to the relevant descriptions in the above method embodiments, which will not be repeated here.

[0709] Figure 34 is another structural schematic diagram of the device provided in an embodiment of this application.

[0710] The device 20 includes a processing circuit 21. The processing circuit 21 is coupled to a memory 23, which stores instructions. When the device 20 is used to implement the method described above, the processing circuit 21 executes the instructions in the memory 23 to implement the function of the processing unit 12 described above.

[0711] Optionally, the device 20 further includes a memory 23 for implementing the functions of the aforementioned memory unit 13.

[0712] Optionally, the device 20 further includes a transceiver circuit 22. The transceiver circuit can be referred to as a communication interface. The processing circuit 21 and the transceiver circuit 22 are coupled to each other. It is understood that the transceiver circuit 22 can be a transceiver or an input / output interface. When the device 20 is used to implement the method described above, the processing circuit 21 executes instructions to implement the function of the processing unit 12, and the transceiver circuit 22 implements the function of the transceiver unit 11.

[0713] Optionally, the device 20 can be a first access network device, a second access network device, a terminal, or a first device, and correspondingly, the transceiver circuit can be a transceiver.

[0714] Optionally, the device 20 can be a chip applied to a first access network device, a second access network device, a terminal, or the first device, and correspondingly, the transceiver circuit can be an input / output interface.

[0715] For example, when device 20 is a chip applied to a first access network device, a second access network device, a terminal, or a first device, the chip implements the functions of the first access network device, the second access network device, the terminal, or the first device in the above method embodiments. The chip receives information from other modules (such as radio frequency modules or antennas) in the first access network device, the second access network device, the terminal, or the first device, which is sent to the first access network device, the second access network device, the terminal, or the first device by other devices; or, the chip sends information to other modules (such as radio frequency modules or antennas) in the first access network device, the second access network device, the terminal, or the first device, which is sent to other devices by the first access network device, the second access network device, the terminal, or the first device.

[0716] Figure 35 is a schematic diagram of a chip system provided in an embodiment of this application. The chip system 30 (or processing system) includes logic circuitry 31 and an input / output interface 32.

[0717] The logic circuit 31 can be a processing circuit in the chip system 30. The logic circuit 31 can be coupled to a memory unit, calling instructions from the memory unit, enabling the chip system 30 to implement the methods and functions of the embodiments of this application. The input / output interface 32 can be an input / output circuit in the chip system 30, outputting processed information from the chip system 30, or inputting data or signaling information to be processed into the chip system 30 for processing.

[0718] As an alternative, the chip system 30 may also include a memory unit.

[0719] As one approach, the chip system 30 is used to implement the operations performed by the first access network device, the second access network device, the terminal, or the first device in the various method embodiments described above.

[0720] For example, logic circuit 31 is used to implement processing-related operations performed by the first access network device, the second access network device, the terminal, or the first device in the above method embodiments; input / output interface 32 is used to implement sending and / or receiving-related operations performed by the first access network device, the second access network device, the terminal, or the first device in the above method embodiments.

[0721] This application also provides a communication device including a processing circuit coupled to a memory for storing computer programs or instructions and / or data. The processing circuit is used to execute the computer programs or instructions stored in the memory, or to read the data stored in the memory, to perform the methods in the above-described method embodiments. Optionally, the processing circuit may be one or more. Optionally, the communication device includes a memory. Optionally, the memory may be one or more. Optionally, the memory may be integrated with the processing circuit, or may be separately disposed.

[0722] This application also provides a chip including a processing circuit coupled to a memory. The memory stores computer programs or instructions, and the processing circuit executes the computer programs or instructions stored in the memory to implement the methods performed by the first access network device, the second access network device, the terminal, or the first device in the above-described method embodiments. The memory may be located within the chip or independently of the chip, and is not limited thereto.

[0723] This application also provides a computer-readable storage medium storing computer instructions for implementing the methods executed by the first access network device, the second access network device, the terminal, or the first device in the above-described method embodiments.

[0724] This application also provides a computer program product comprising instructions that, when executed by a computer, implement the methods performed by the first access network device, the second access network device, the terminal, or the first device in the above-described method embodiments.

[0725] This application also provides a computer program that, when executed by a computer, implements the methods performed by the first access network device, the second access network device, the terminal, or the first device in the above-described method embodiments.

[0726] This application also provides a communication system, which includes at least one of a first access network device, a second access network device, a terminal, or a first device in the above embodiments.

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

[0728] It is understood that the processing circuit in the embodiments of this application may be a processor or a circuit in a processor for performing processing operations. The processor may include one or more of the following: a central processing unit (CPU), a digital signal processor (DSP), a microprocessor unit (MPU), a microcontroller unit (MCU), a graphics processing unit (GPU), a field programmable gate array (FPGA), an artificial intelligence processor (AI processor), or a neural processing unit (NPU).

[0729] The aforementioned memory may include one or more of the following storage media: random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), phase-change memory (PCM), resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), cache, register, read-only memory (ROM), flash memory, erasable programmable read-only memory (EPROM), hard disk, etc. In one example, computer program instructions for executing the above embodiments may be stored in non-volatile memory, such as the aforementioned memory 23 or at least a portion of the storage cells (e.g., one or more of ROM, flash memory, EPROM, or hard disk).

[0730] The method steps in the embodiments of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, portable hard disks, compact disc read-only memory (CD-ROM), or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an application-specific integrated circuit (ASIC). Furthermore, the ASIC can reside in a first access network device, a second access network device, a terminal, or a first device. Alternatively, the processor and storage medium can exist as discrete components in the first access network device, the second access network device, the terminal, or the first device.

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

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

[0733] Unless otherwise stated, all technical and scientific terms used in the embodiments of this application have the same meaning as commonly understood by one of ordinary skill in the art. The terminology used in this application is for the purpose of describing specific embodiments only and is not intended to limit the scope of this application. It should be understood that the above are illustrative examples, and the examples above are merely to help those skilled in the art understand the embodiments of this application, and are not intended to limit the embodiments of the application to the specific numerical values ​​or specific scenarios exemplified. Those skilled in the art can obviously make various equivalent modifications or variations based on the examples given above, and such modifications and variations also fall within the scope of the embodiments of this application.

Claims

1. A communication method, characterized in that, The method is applied to a first access network device or a module in the first access network device, and the method includes: Receive a first message from a second access network device. The first message is used to initiate a handover request. The first message includes first information. The first information is used to determine a first resource. The first resource is used by the terminal to execute a first environment Internet of Things (A-IoT) service. Based on the first information, second information is determined, and the second information indicates the first resource; Send a second message to the second access network device, the second message including the second information.

2. A communication method, characterized in that, The method is applied to a second access network device or a module in the second access network device, and the method includes: Send a first message to the first access network device. The first message is used to initiate a handover request. The first message includes first information. The first information is used to determine a first resource. The first resource is used by the terminal to execute the first environment Internet of Things (A-IoT) service. Receive a second message from the first access network device, the second message including second information, the second information indicating the first resource; A third message is sent to the terminal, the third message including the second information.

3. The method according to claim 2, characterized in that, Before sending the first message to the first access network device, the method further includes: A fourth message is received from the terminal, the fourth message including the first information.

4. A communication method, characterized in that, The method is applied to a terminal or a module in the terminal, and the method includes: Send a fourth message to the second access network device. The fourth message includes first information, which is used to determine a first resource. The first resource is used by the terminal to execute the first environment Internet of Things (A-IoT) service. The terminal receives a third message from the second access network device, the third message instructing the terminal to switch to the first access network device, the third message including second information indicating the first resource.

5. The method according to any one of claims 1 to 4, characterized in that, The first message also includes third information, which is used to determine the first carrier configuration information; The second message also includes fourth information, which is the first carrier configuration information.

6. The method according to any one of claims 2 to 4, characterized in that, The fourth message also includes third information, which is used to determine the first carrier configuration information; The third message also includes fourth information, which is the first carrier configuration information.

7. A communication method, characterized in that, The method is applied to a terminal or a module in the terminal, and the method includes: During the execution of the first-environment IoT A-IoT service, a wireless link failure (RLF) was detected. Send a fifth message to the first access network device. The fifth message includes first information, which is used to determine a first resource. The first resource is used by the terminal to execute the first A-IoT service. A sixth message is received from the first access network device, the sixth message including second information, the second information indicating the first resource.

8. A communication method, characterized in that, The method is applied to a first access network device or a module in the first access network device, and the method includes: Receive a fifth message from the terminal, the fifth message including first information, the first information being used to determine a first resource, the first resource being used by the terminal to execute the first A-IoT service; Based on the first information, second information is determined, and the second information indicates the first resource; A sixth message is sent to the terminal, the sixth message including the second information.

9. The method according to claim 7 or 8, characterized in that, The fifth message also includes third information, which is used to determine the first carrier configuration information; The sixth message also includes fourth information, which is the first carrier configuration information.

10. A communication method, characterized in that, The method is applied to a terminal or a module in the terminal, and the method includes: The terminal is in a non-connected state when executing the first-environment Internet of Things (A-IoT) service. In executing the first A-IoT service, a seventh message is sent to the first access network device. The seventh message is used to request the restoration of the suspended Radio Resource Control (RRC) connection of the terminal. The seventh message includes first information, which is used to determine a first resource. The first resource is used by the terminal to execute the first A-IoT service. The eighth message is received from the first access network device, the eighth message including second information, the second information indicating the first resource.

11. A communication method, characterized in that, The method is applied to a first access network device or a module in the first access network device, and the method includes: A seventh message is received from the terminal, the seventh message being used to request the resumption of the terminal's suspended Radio Resource Control (RRC) connection, the seventh message including first information, the first information being used to determine a first resource, the first resource being used by the terminal to execute the first A-IoT service; Based on the first information, second information is determined, and the second information indicates the first resource; Send an eighth message to the terminal, the eighth message including the second information.

12. The method according to claim 10 or 11, characterized in that, The seventh message also includes third information, which is used to determine the first carrier configuration information; The eighth message also includes fourth information, which is the first carrier configuration information.

13. The method according to any one of claims 1 to 12, characterized in that, The first information includes at least one of the following: The fifth piece of information indicates the number of first devices associated with the first A-IoT service; The sixth piece of information indicates the latency related to the first A-IoT service; The seventh piece of information indicates that the first A-IoT service is associated with a first device or indicates that the first A-IoT service is associated with multiple first devices; The frequency bands supported by the first device associated with the first A-IoT service; The cycle for executing the first A-IoT service; The type of the first A-IoT service; The size of the data reported by the first device related to the first AIoT service; The number of identification information of the first device associated with the first A-IoT service.

14. The method according to claim 13, characterized in that, The number of first devices associated with the first A-IoT service includes at least one of the following: The number of first devices that did not perform the first A-IoT service during the period when the terminal accessed the second access network device; The number of first devices that have performed the first A-IoT service during the period when the terminal accesses the second access network device; The number of first devices associated with the first A-IoT service.

15. The method according to claim 13 or 14, characterized in that, The latency associated with the first A-IoT service includes at least one of the following: The remaining latency of the first A-IoT service when the connection between the terminal and the second access network device is disconnected; The duration during which the terminal executes the first A-IoT service while accessing the second access network device; The latency of the first A-IoT service.

16. The method according to claim 5, 6, 9 or 12, characterized in that, The third information includes at least one of the following: The capabilities of the first device related to the first A-IoT service; The type of the first device associated with the first A-IoT service.

17. The method according to claim 16, characterized in that, The capability includes at least one of the following: reflection capability, energy storage capability, signal amplification capability, or signal generation capability; and / or, The type includes at least one of the following: device 1, device 2a, device 2b, device A, device B, or device C.

18. The method according to claim 16 or 17, characterized in that, The third information also includes second carrier configuration information.

19. The method according to claim 5, 6, 9 or 12, characterized in that, The first carrier configuration information includes at least one of the following: first transmission power, first transmission start time, first transmission end time, first transmission period, first duration, first region, and first frequency domain resources, wherein the first region includes the region of the transmission carrier and / or the region related to the first A-IoT service.

20. A communication device, characterized in that, Includes modules or units for performing the method as described in any one of claims 1 to 19.

21. A communication device, characterized in that, The device includes a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices besides the communication device and transmit them to the processor, or to send signals from the processor to other communication devices besides the communication device, and the processor is used to implement the method as described in any one of claims 1 to 19 through logic circuits or by executing code or instructions.

22. The communication device according to claim 21, characterized in that, The communication device is a chip or chip system.

23. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions, which, when executed by a communication device, implement the method as described in any one of claims 1 to 19.

24. A computer program product, characterized in that, Includes a computer program that, when run, implements the method as described in any one of claims 1 to 19.

25. A communication system, characterized in that, include: A first access network device for performing the method as described in any one of claims 1, 5, 13 to 19; a first access network device for performing the method as described in any one of claims 2, 3, 5, 6, 13 to 19; and a terminal for performing the method as described in any one of claims 4-6, 13 to 19; or, A terminal for performing the method as described in any one of claims 7, 9, 13 to 19, and a first access network device for performing the method as described in any one of claims 8, 9, 13 to 19; or, A terminal for performing the method as described in any one of claims 10, 12, 13 to 19, and a first access network device for performing the method as described in any one of claims 11 to 19.

Images