Communication method and apparatus

Abstract

The present application provides a communication method and apparatus. According to the communication method provided in the present application, a terminal, a target access network device, or a core network element acquires an area corresponding to an AIoT service and a location of the terminal following an access network device handover, and determines, based on a relationship between the area and the location, whether the terminal will continue executing the AIoT service, thereby reducing the likelihood of AIoT service disruptions.

Description

A communication method and apparatus

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

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

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

[0004] However, if the access network device to which the terminal device is connected switches during the execution of AIoT services, the AIoT services will lose control of the source access network device, and the continuity of the AIoT services may be disrupted. Summary of the Invention

[0005] This application provides a communication method and apparatus that enables a terminal to continue executing AIoT services after switching access network devices during the execution of AIoT services, thereby helping to avoid disruption of the continuity of AIoT services.

[0006] In a first aspect, this application provides a communication method applied to the network side, such as a second access network device or a component (e.g., a chip, chip system, etc.) within the second access network device, or it can also be a logic module or software capable of implementing all or part of the functions of the second access network device. Taking the application of this method to a second access network device as an example, when a terminal switches to the second access network device while performing an AIoT service, the method includes: obtaining first information, the first information indicating the first location of the terminal; obtaining a first area, the first area indicating the area corresponding to the AIoT service; determining whether the terminal should continue performing the AIoT service based on the first location and the first area; and sending second information, the second information indicating whether the terminal should continue performing the AIoT service.

[0007] When a terminal switches from a first access network device to a second access network device, the second access network device determines whether the terminal should continue to perform AIoT services based on the relationship between the first location and the first area, which helps maintain the continuity of AIoT services.

[0008] In some implementations, after determining to continue executing the AIoT service, the method also includes:

[0009] Obtain third information, which indicates the second location of the terminal; determine whether to continue executing the AIoT service based on the second location and the first area; send fourth information, which indicates whether the terminal should continue executing the AIoT service.

[0010] In some implementations, after determining that AIoT services will no longer be executed, the method also includes:

[0011] Obtain the fifth piece of information, which indicates the third location of the terminal; based on the third location and the first region, determine whether to continue executing the AIoT service; send the sixth piece of information, which indicates whether the terminal should continue executing the AIoT service.

[0012] Based on the second and third locations mentioned above, the second access network device determines whether the terminal should continue to execute AIoT services. It can determine whether to continue executing AIoT services in real time after the terminal accesses the second access network device, which is beneficial for maintaining the continuity of AIoT services during the terminal's continued movement.

[0013] In some implementations, the decision to continue executing AIoT services is made based on the first location and the first region, including:

[0014] If the first location is in the first region, it is determined that the AIoT service will continue to be executed; or, if the first location is not in the first region, it is determined that the AIoT service will not continue to be executed.

[0015] In some implementations, the decision to continue executing AIoT services is made based on the first location and the first region, including:

[0016] If the first location is in the first area and the second access network device supports AIoT capabilities, it is determined to continue executing the AIoT service; or, if the first location is in the first area and the second access network device does not support AIoT capabilities, it is determined not to continue executing the AIoT service.

[0017] Whether the access network equipment supports AIoT capabilities includes one or more of the following: whether it can schedule / allocate / control / manage AIoT radio resources, and whether it can transmit (including sending and / or receiving) data / signaling related to AIoT services.

[0018] When the first location is in the first area, the second access network device can further determine whether the terminal should continue to perform AIoT services based on whether it supports AIoT capabilities, thus enabling the continued maintenance of AIoT service continuity.

[0019] In some implementations, the second access network device supports AIoT capabilities, and after determining to continue executing AIoT services, the method also includes:

[0020] Send first resource information, which indicates a first resource used by the terminal to communicate with the AIoT device; and / or send radio bearer (RB) configuration information, which indicates a first RB dedicated to transmitting AIoT service-related data and / or signaling.

[0021] In some implementations, the first resource is the AIoT wireless resource used by the terminal and the AIoT device to communicate in the first cell, which is the cell where the terminal is located after accessing the second access network device; or, the first resource is the AIoT wireless resource used by the terminal and the AIoT device to communicate in the second cell, which includes multiple cells controlled by the second access network device; or, the first resource is the AIoT wireless resource used by the terminal to communicate with the AIoT device during cell handover or access network device handover.

[0022] The second access network, by configuring the first resource used by the terminal to communicate with the AIoT device, enables the terminal to use the above AIoT wireless resources to communicate with the AIoT device after determining that the terminal will continue to perform AIoT services.

[0023] In some implementations, the decision on whether to continue executing AIoT services includes:

[0024] Whether to report data corresponding to AIoT services, and / or whether to transmit data and / or signaling corresponding to AIoT services with AIoT devices.

[0025] Secondly, this application provides a communication method applied to a core network element, wherein a terminal switches to a second access network device while performing an AIoT service. The method includes: receiving request information, the request information requesting whether to continue performing the AIoT service; obtaining first information, the first information indicating the first location of the terminal; obtaining a first area, the first area indicating the area corresponding to the AIoT service; determining whether the terminal should continue performing the AIoT service based on the first location and the first area; and sending second information, the second information indicating whether the terminal should continue performing the AIoT service.

[0026] In some implementations, after determining that the terminal will continue to perform AIoT services, the method also includes:

[0027] Obtain third information, which indicates the second location of the terminal; determine whether the terminal should continue to perform AIoT services based on the second location and the first region; send seventh information, which indicates whether the terminal should continue to perform AIoT services.

[0028] In some implementations, after determining that the terminal will no longer perform AIoT services, the method also includes:

[0029] Obtain the fifth information, which indicates the third location of the terminal; based on the third location and the first region, determine whether the terminal should continue to perform AIoT services; send the eighth information, which indicates whether the terminal should continue to perform AIoT services.

[0030] In some implementations, the decision on whether the terminal should continue performing AIoT services is determined based on the first location and the first region, including:

[0031] If the first location is in the first area, it is determined that the terminal will continue to perform AIoT services; or if the first location is not in the first area, it is determined that the terminal will not continue to perform AIoT services.

[0032] In some implementations, the method also includes:

[0033] Obtain first capability information, which indicates whether the second access network device supports AIoT capabilities.

[0034] Among them, determining whether the terminal should continue to perform AIoT services based on the first location and the first region includes:

[0035] If the first location is in the first area and the second access network supports AIoT capabilities, it is determined that the terminal will continue to perform AIoT services; or, if the first location is in the first area and the second access network does not support AIoT capabilities, it is determined that the terminal will not continue to perform AIoT services.

[0036] In some implementations, the method also includes:

[0037] Send third resource information, which indicates the third resource. The third resource is the AIoT wireless resource used by the terminal to communicate with the AIoT device during cell handover or access network device handover.

[0038] Thirdly, this application provides a communication method applied to the terminal side, such as a terminal or a communication module in the terminal, or a circuit or chip in the terminal responsible for communication functions. Taking the application of this method to a terminal as an example, the terminal accesses a first access network device, and the method includes: receiving a first message while performing an AIoT service; in response to receiving the first message, the terminal accesses a second access network device; obtaining a ninth message, and determining whether to perform an AIoT service based on the ninth message.

[0039] In some implementations, the ninth message indicates whether the terminal should continue performing AIoT services.

[0040] In some implementations, the ninth information includes first information and a first region, where the first information indicates the first location of the terminal and the first region indicates the region corresponding to the AIoT service.

[0041] Among them, determining whether to execute AIoT services based on the ninth piece of information includes:

[0042] Based on the first location and the first region, determine whether to continue executing the AIoT service.

[0043] In some implementations, after determining to continue executing the AIoT service, the method also includes:

[0044] Obtain third information, which indicates the second location of the terminal; based on the second location and the first area, determine whether to continue executing the AIoT service.

[0045] In some implementations, after determining that AIoT services will no longer be executed, the method also includes:

[0046] Obtain the fifth piece of information, which indicates the third location of the terminal; based on the third location and the first region, determine whether to continue executing the AIoT service.

[0047] In some implementations, the decision to continue executing AIoT services is made based on the first location and the first region, including:

[0048] If the first location is in the first region, it is determined that the AIoT service will continue to be executed; or, if the first location is not in the first region, it is determined that the AIoT service will not continue to be executed.

[0049] In some implementations, the method also includes:

[0050] Obtain first capability information, which indicates whether the second access network device supports AIoT capabilities.

[0051] Among these, determining whether to continue executing AIoT services based on the first location and the first region includes:

[0052] If the first location is in the first area and the second access network device supports AIoT capabilities, it is determined to continue executing the AIoT service; or, if the first location is in the first area and the second access network device does not support AIoT capabilities, it is determined not to continue executing the AIoT service.

[0053] In some implementations, after determining that AIoT services will no longer be executed, the method also includes:

[0054] Release the tenth information, which includes data and / or signaling corresponding to AIoT services received by the terminal before it accesses the second access network device; or, retain the tenth information until the terminal accesses the third access network device.

[0055] In some implementations, the tenth piece of information is released, including:

[0056] If the tenth information is retained for a preset duration, the tenth information is released.

[0057] After the terminal decides not to continue executing AIoT services, releasing the tenth piece of information can save storage resources. Retaining the tenth piece of information helps improve its utilization rate.

[0058] In some implementations, the second access network device supports AIoT capabilities, and after determining to continue executing AIoT services, the method also includes:

[0059] Receive first resource information, the first resource information indicating a first resource, the first resource being used for communication between the terminal and the AIoT device; and / or, receive RB configuration information, the RB configuration information being used to indicate a first RB, the first RB being dedicated to transmitting data and / or signaling related to AIoT services.

[0060] In some implementations, the first resource is the AIoT radio resource used by the terminal and the AIoT device to communicate in the first cell, which is the cell where the terminal is located after accessing the second access network device; or, the first resource is the AIoT radio resource used by the terminal and the AIoT device to communicate in the second cell, which includes multiple cells controlled by the second access network device; or, the first resource is the AIoT resource used by the terminal to communicate with the AIoT device during cell handover or access network device handover.

[0061] In some implementations, the method also includes:

[0062] The terminal receives second resource information, which indicates a second resource. The second resource is the AIoT wireless resource used by the terminal to communicate with the AIoT device during cell handover or access network device handover. The second resource information comes from the first access network device.

[0063] In some implementations, the method also includes:

[0064] Receive third resource information. The third resource information indicates the third resource. The third resource is the AIoT wireless resource used by the terminal to communicate with the AIoT device during cell handover or access network device handover. The third resource information comes from the core network element.

[0065] Fourthly, this application provides a communication method applied to the terminal side, such as a terminal or a communication module in the terminal, or a circuit or chip in the terminal responsible for communication functions. Taking the application of this method to a terminal as an example, the terminal accesses a first access network device, and the method includes: receiving a first message while performing AIoT services, the first message instructing the terminal to access or switch to a second access network device; and stopping the performance of AIoT services.

[0066] In some implementations, the method also includes:

[0067] Release the configuration corresponding to the AIoT service, and / or release the terminal's first context, which is used for the terminal to transmit AIoT services with AIoT devices.

[0068] In some implementations, the configuration corresponding to AIoT services includes AIoT wireless resources used to transmit information for AIoT services.

[0069] In some implementations, the terminal accesses the first access network device, including:

[0070] The terminal accesses the third cell, which is a cell controlled by the first access network device.

[0071] The methods also include:

[0072] In response to receiving the first message, the terminal accesses the fourth cell, which is a cell controlled by the first access network device.

[0073] Fifthly, this application provides a communication method applied to the terminal side, such as a terminal or a communication module in the terminal, or a circuit or chip in the terminal responsible for communication functions. Taking the application of this method to a terminal as an example, the terminal accesses a first access network device, and the method includes: receiving a first message while performing an AIoT service, the first message instructing the terminal to access or switch to a second access network device; suspending the AIoT service;

[0074] In some implementations, the method also includes:

[0075] The configuration corresponding to the suspended AIoT service is suspended, and / or the first context of the terminal is suspended. The first context is used for the terminal to transmit AIoT services with AIoT devices.

[0076] In some implementations, the configuration corresponding to AIoT services includes AIoT wireless resources used to transmit information corresponding to AIoT services.

[0077] In some implementations, the terminal accesses the first access network device, including:

[0078] The terminal accesses the third cell, which is a cell controlled by the first access network device.

[0079] The methods also include:

[0080] In response to receiving the first message, the terminal accesses the fourth cell, which is a cell controlled by the first access network device; and receives a second message from the fourth cell, which indicates any one of the following: resuming the AIoT service, stopping the execution of the AIoT service, or indicating the configuration corresponding to the AIoT service.

[0081] Sixthly, this application provides a communication method applied to a terminal side, such as a terminal or a communication module in a terminal, or a circuit or chip in a terminal responsible for communication functions. Taking the application of this method to a terminal as an example, the terminal accesses a third cell controlled by a first access network device. The method includes: receiving a first message while performing an AIoT service; in response to receiving the first message, accessing a fourth cell; if the fourth cell is the third cell, continuing to perform the AIoT service.

[0082] In some implementations, the method also includes:

[0083] If the fourth cell is different from the third cell, stop executing the AIoT service, or suspend the AIoT service.

[0084] Seventhly, this application provides a communication method applied to a terminal side, such as a terminal or a communication module in a terminal, or a circuit or chip in a terminal responsible for communication functions. Taking the application of this method to a terminal as an example, the terminal accesses a third cell controlled by a first access network device. The method includes: in performing an AIoT service, receiving a first message, the first message instructing the terminal to access or switch to a second access network device; in response to receiving the first message, starting a first timer; during the operation of the first timer, continuing to perform the AIoT service, or accessing a fourth cell.

[0085] In some implementations, after accessing the fourth cell, the method also includes:

[0086] Send a third message in the fourth cell, indicating that the RRC reconfiguration is complete; after sending the third message, stop the timer; and / or, after sending the third message, receive the first configuration information in the fourth cell and execute the AIoT service according to the first configuration information.

[0087] In some implementations, the method also includes:

[0088] If the first timer reaches the second preset duration, stop executing the AIoT service, or suspend the AIoT service.

[0089] Eighthly, this application provides a communication device including modules or units for implementing the methods of the first to seventh aspects and any possible implementations of the first to seventh aspects. Each module or unit can implement its corresponding function by executing a computer program.

[0090] For example, the communication device in the eighth aspect is a terminal device or a component configured in a terminal device, such as a chip, chip system, processor, etc.; or, the communication device in the eighth aspect is an access network device or a component configured in an access network device, such as a chip, chip system, processor, etc.; or, the communication device in the eighth aspect is a core network element or a component configured in a core network element.

[0091] Ninthly, this application provides a communication device, including a processor, which is configured to execute the communication methods in the first to seventh aspects and any possible implementations of the first to seventh aspects.

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

[0093] Optionally, the communication device includes a communication interface for communicating with other communication devices. For example, the communication interface may be a transceiver, circuit, bus, module, pin, or other type of communication interface.

[0094] For example, the communication device provided in the ninth aspect is a chip or chip system, and may also be a terminal device or access network device.

[0095] In a tenth aspect, this application provides a computer-readable storage medium including a computer program that, when run on a computer, causes the computer to implement the methods of the first to seventh aspects and any possible implementation of the first to seventh aspects.

[0096] In one aspect, this application provides a computer program product comprising: a computer program (also referred to as code or instructions) that, when run, causes a computer to perform the methods of the first and seventh aspects and any possible implementation thereof.

[0097] The eighth to eleventh aspects of this application correspond to the technical solutions of the first aspect of this application. The beneficial effects achieved by each aspect and the corresponding feasible implementation are similar, and will not be repeated here. Attached Figure Description

[0098] Figure 1 is a schematic diagram of the architecture of the communication system used in the embodiments of this application;

[0099] Figure 2 is a schematic diagram of the access network equipment used in the embodiments of this application;

[0100] Figure 3A is a schematic diagram of the architecture of Topology 1 in the AIoT network architecture;

[0101] Figure 3B is a schematic diagram of the architecture of topology 2 in the AIoT network architecture;

[0102] Figure 3C is a schematic diagram of Topology 3 in the AIoT network architecture;

[0103] Figure 3D is a schematic diagram of Topology 4 in the AIoT network architecture;

[0104] Figure 3E is a schematic diagram of a communication system applicable to an embodiment of this application;

[0105] Figure 3F is a schematic diagram of another communication system applicable to embodiments of this application;

[0106] Figure 3G is a schematic diagram of another communication system applicable to the embodiments of this application;

[0107] Figure 4 is a flowchart illustrating a communication method provided in one embodiment of this application;

[0108] Figure 5 is a flowchart illustrating a communication method provided in one embodiment of this application;

[0109] Figure 6A is a schematic diagram of the protocol stack for the RRC-based transmission solution (Solution 1) under Topology 2 architecture;

[0110] Figure 6B is a schematic diagram of the protocol stack for the solution (Solution 2) based on non-access stratum (NAS) transmission under Topology 2 architecture;

[0111] Figure 6C is a schematic diagram of the protocol stack for the solution (Solution 3) based on user plane (UP) transmission under Topology 2 architecture;

[0112] Figure 7 is a flowchart illustrating a communication method provided in another embodiment of this application;

[0113] Figure 8 is a flowchart illustrating a communication method provided in yet another embodiment of this application;

[0114] Figure 9 is a flowchart illustrating a communication method provided in one embodiment of this application;

[0115] Figure 10 is a flowchart illustrating a communication method provided in another embodiment of this application;

[0116] Figure 11 is a flowchart illustrating a communication method provided in another embodiment of this application;

[0117] Figure 12 is a flowchart illustrating a communication method provided in another embodiment of this application;

[0118] Figure 13 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0119] Figure 14 is a schematic diagram of the structure of a communication device provided in another embodiment of this application. Detailed Implementation

[0120] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0121] It should be understood that in this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates an "or" relationship between the preceding and following related objects, but it does not exclude the possibility of indicating an "and" relationship. The specific meaning can be understood in conjunction with the context. "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 can mean: a, b, c; a and b; a and c; b and c; or a and b and c. Here, a, b, and c can be single or multiple.

[0122] In this application, the use of prefixes such as "first" and "second" is merely for the purpose of distinguishing and describing different things belonging to the same category, and does not constrain the order, size, or quantity of things. For example, "first parameter" and "second parameter" are simply different parameters, and there is no temporal or quantitative relationship between them.

[0123] This application will present various aspects, embodiments, or features relating to systems that may include multiple devices, components, modules, etc. It should be understood and appreciated that individual systems may include additional devices, components, modules, etc., and / or may not include all the devices, components, modules, etc. discussed in conjunction with the accompanying drawings. Furthermore, combinations of these approaches are also possible.

[0124] Furthermore, in the embodiments of this application, words such as "exemplarily" and "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design scheme described as an "example" in this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of the term "example" is intended to present concepts in a concrete manner. In the embodiments of this application, "of," "corresponding, relevant," and "corresponding" may sometimes be used interchangeably, and it should be noted that their intended meanings are consistent unless their distinction is emphasized.

[0125] Figure 1 is a schematic diagram of the architecture of the communication system applied in the embodiments of this application. Figure 1 shows a schematic diagram of a possible, non-limiting system architecture. As shown in Figure 1, the communication system 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 1, collectively referred to as 110) and at least one terminal device (120a-120j in Figure 1, collectively referred to as 120). RAN 100 may also include other RAN nodes, such as wireless relay devices and / or wireless backhaul devices (not shown in Figure 1). Terminal device 120 is wirelessly connected to RAN node 110. RAN node 110 is wirelessly or wired connected to core network 200. The core network device 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.

[0126] RAN 100 can be a cellular system related to the 3rd Generation Partnership Project (3GPP), such as a 5G mobile communication system or a future-oriented evolution system (such as a 6G mobile communication system). RAN 100 can also be an open access network (open RAN, O-RAN, or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (Wi-Fi) system. RAN 100 can also be a communication system that integrates two or more of the above systems.

[0127] RAN node 110, sometimes also referred to as access network equipment, RAN entity, or access node, is part of the communication system used to help terminal devices achieve wireless access. Multiple RAN nodes 110 in the communication system can be of the same type or different types. In some scenarios, the roles of RAN node 110 and terminal device 120 are relative. For example, network element 120i in Figure 1 can be a helicopter or drone, which can be configured as a mobile base station. For terminal devices 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 device. RAN node 110 and terminal device 120 are sometimes both referred to as communication devices. For example, network elements 110a and 110b in Figure 1 can be understood as communication devices with base station functions, and network elements 120a-120j can be understood as communication devices with terminal functions.

[0128] In one possible scenario, a RAN node can be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next-generation NodeB (gNB), a base station in a future mobile communication system, or an access node in a Wi-Fi system. A RAN node can be a macro base station (as shown in Figure 1, 110a), a micro base station or indoor station (as shown in Figure 1, 110b), a relay node or donor node, or a radio controller in a CRAN scenario. Optionally, a 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).

[0129] In another possible scenario, multiple RAN nodes collaborate to assist the terminal in achieving wireless access, with different RAN nodes each implementing some of the base station's functions. For example, RAN nodes can be central units (CUs), distributed units (DUs), CU-control planes (CU-CPs), CU-user planes (CU-UPs), or radio units (RUs). 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).

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

[0131] Terminal devices can also be called terminals, user equipment (UE), mobile stations, mobile terminals, etc. They can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), the Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, and smart cities. Terminals can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc.

[0132] In this embodiment of the application, the access network device may be, for example, the RAN node 110 shown in FIG1, and the terminal device may be, for example, the terminal device 120 shown in FIG1. ​​Multiple network devices may transmit data or control signaling to a single terminal device at the same time. This application does not specifically limit the types of access network devices and terminal devices.

[0133] In addition, terminal devices and access network devices can be hardware devices, software functions running on dedicated hardware, or software functions running on general-purpose hardware. For example, they can be virtualization functions instantiated on a platform (e.g., a cloud platform). Alternatively, they can be entities that include dedicated or general-purpose hardware devices and software functions. This application does not limit the specific form of terminal devices and access network devices.

[0134] Figure 2 is a schematic diagram of the access network device used in the embodiments of this application. As shown in Figure 2, the access network device includes one or more CUs, one or more DUs, and one or more RUs. For clarity, only one CU, DU, and RU are shown in Figure 2. The CU is used to connect to the core network and one or more DUs. Optionally, the CU may have some of the functions of the core network. The CU may include CU-CP and CU-UP.

[0135] The CU and DU can be configured according to the protocol layer functions of the wireless network they implement: for example, the CU can be configured to implement the functions of the Packet Data Convergence Protocol (PDCP) layer and above (such as the Radio Resource Control (RRC) layer and / or the Service Data Adaptation Protocol (SDAP) layer); the DU can be configured to implement the functions of the protocol layers below the PDCP layer (such as the Radio Link Control (RLC) layer, the Medium Access Control (MAC) layer, and / or the Physical (PHY) layer). Alternatively, the CU can be configured to implement the functions of the protocol layers above the PDCP layer (such as the RRC and / or SDAP layers), and the DU can be configured to implement the functions of the protocol layers below the PDCP layer (such as the RLC, MAC, and / or PHY layers).

[0136] When a CU includes CU-CP and CU-UP, CU-CP is used to implement the control plane functions of the CU, and CU-UP is used to implement the user plane functions of the CU. For example, when a CU is configured to implement the functions of the PDCP layer, RRC layer, and SDAP layer, CU-CP is used to implement the RRC layer functions and the control plane functions of the PDCP layer, and CU-UP is used to implement the SDAP layer functions and the user plane functions of the PDCP layer.

[0137] The CU-CP can interact with network elements in the core network used to implement control plane functions. These network elements can be access and mobility function (AMF) network elements, such as the AMF network element in a 5G system. The AMF network element is responsible for mobility management in the mobile network, such as terminal device location updates, terminal device registration with the network, and terminal device handover.

[0138] CU-UP can interact with network elements in the core network used to implement user plane functions. These network elements, such as the user plane function (UPF) network elements in a 5G system, are responsible for forwarding and receiving data in terminal devices.

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

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

[0141] A passive radio frequency identification (RFID) system consists of an interrogator and a tag device, where the tag device can also be understood as an electronic tag. The interrogator reads information from the tag device or writes information that the tag device needs to store into the tag device. Non-contact data communication occurs between the interrogator and the tag device. Given the low power consumption advantage of passive radio frequency identification (RFID) technology, applying RFID technology to the communication system shown in Figure 1 can construct a highly simplified Internet of Things (IoT), namely, an ambient IoT (AIoT).

[0142] Based on the communication system shown in Figure 1, 3GPP defines four AIoT network architectures. Figure 3A is a schematic diagram of Topology 1 in the AIoT network architecture. As shown in Figure 3A, the AIoT network under Topology 1 includes AIoT devices and access network devices.

[0143] In this context, AIoT devices can be understood as extremely low-power, low-complexity Internet of Things (IoT) devices, specifically categorized into active, passive, and semi-active types. AIoT devices are analogous to tags in an RFID system. In Topology 1, AIoT devices communicate directly and bidirectionally with access network devices. The communication between the access network devices and AIoT devices can include AIoT data and / or AIoT-related signaling.

[0144] Figure 3B is a schematic diagram of Topology 2 in the AIoT network architecture. As shown in Figure 3B, the AIoT network in Topology 2 includes AIoT devices, intermediate nodes, and access network devices. Specifically, intermediate nodes can be repeaters, integrated access and backhaul (IAB) nodes, and terminals. It should be noted that terminals can also be described as UE readers or AIoT-enabled UEs.

[0145] In Topology 2 architecture, AIoT devices communicate bidirectionally with intermediate nodes, and intermediate nodes also communicate bidirectionally with access network devices. That is, AIoT devices transmit AIoT data and / or AIoT-related signaling to access network devices through intermediate nodes, achieving indirect bidirectional communication between AIoT devices and access network devices via intermediate nodes. For ease of description, this application embodiment uniformly uses "terminal" to describe the intermediate nodes in Topology 2 architecture.

[0146] Figure 3C is a schematic diagram of Topology 3 in the AIoT network architecture. As shown in Figure 3C, the AIoT network under Topology 3 includes AIoT devices, auxiliary nodes, and access network devices. Auxiliary nodes can specifically include repeaters, IAB nodes, and UEs, etc.

[0147] In Topology 3 architecture, AIoT devices send AIoT data and / or AIoT-related signaling to access network devices and receive AIoT data and / or AIoT-related signaling from auxiliary nodes. Alternatively, AIoT devices receive AIoT data and / or AIoT-related signaling from access network devices and send AIoT data and / or AIoT-related signaling to auxiliary nodes.

[0148] Figure 3D is a schematic diagram of Topology 4 in the AIoT network architecture. As shown in Figure 3D, the AIoT network under Topology 4 includes terminal devices and AIoT devices.

[0149] In the Topology 4 architecture, AIoT devices and terminal devices communicate directly in both directions. The communication content between terminal devices and access network devices may include AIoT data and / or AIoT-related signaling.

[0150] In the above topology, the device communicating with the AIoT device can be understood as a device with read / write capabilities. In this embodiment, devices with read / write capabilities are uniformly described as readers / writers. Specifically, the access network device in topology 1 is equivalent to a reader / writer, the intermediate node in topology 2 is equivalent to a reader / writer, the auxiliary node in topology 3 is equivalent to a reader / writer, and the terminal device in topology 4 is equivalent to a reader / writer.

[0151] AIoT technology can be used to realize one or more AIoT services such as inventory, positioning, sensing, and command. Its typical application scenarios include logistics, warehousing, industrial manufacturing, identity recognition, and environmental monitoring.

[0152] Among them, the inventory management service uses readers to connect to AIoT devices within the coverage area. Devices that successfully connect need to send their unique identifier to the reader. This unique identifier is an identifier that the network can recognize, such as the electronic product code (EPC) in RFID.

[0153] Location services utilize positioning signals to pinpoint the location of AIoT devices. Sensing services involve AIoT devices reporting sensor data, such as temperature data, to access network devices.

[0154] Commands can be operation instructions, and command services can include at least one of the following services:

[0155] Read service: The read service can read the EPC in the tag's storage area, the tag identifier (TID), the content stored in the tag's reserved area, or the content stored in the user's storage area.

[0156] Write operations: Write operations can perform write operations on the tag's storage area. For example, the reader sends a downlink command and data to the tag, instructing the tag to write the data into its own storage area.

[0157] Disable service: Can be temporarily or permanently disabled.

[0158] Kill the tag: The kill tag can make the tag permanently unusable.

[0159] Locking: Locking can lock the information of a tag, thereby preventing the reader from reading or writing to that tag. Alternatively, locking can also lock the tag's storage area, preventing or allowing reading or writing to that storage area.

[0160] It is understandable that AIoT devices and readers can perform other services or operations, which will not be listed here.

[0161] In AIoT technology, the core network can configure corresponding AIoT services according to the specific needs of the application scenario. In the four AIoT network architectures shown in Figures 3A to 3D, after receiving the AIoT services configured by the core network, the access network device configures AIoT radio resources for the corresponding reader / writer, enabling the reader / writer to communicate with the AIoT device using these resources. It can be understood that in topology 4, the terminal device is connected to the access network device and communicates bidirectionally with the AIoT device based on the AIoT radio resources configured by the access network device. Figure 3D omits the access network device to illustrate the transmission direction of AIoT data and / or AIoT-related signaling in this topology.

[0162] In the topology 2 architecture shown in Figure 3B, the terminal may move. During the movement, if the terminal's location is outside the coverage area of ​​the access network device it is currently connected to, the terminal needs to switch from the currently connected access network device to another access network device. In the case of a switch of access network devices connected to the terminal, the currently connected access network device is the source access network device, and the access network device to be connected to is the target access network device.

[0163] As described above, in Topology 2 architecture, the source access network device configures AIoT radio resources for terminals that implement read / write functions, which is equivalent to the source access network device controlling the AIoT services executed by the terminals. However, in the event of a terminal access network device switchover, the AIoT radio resources configured by the source access network device become invalid, and the AIoT services lose the control of the source access network device. Consequently, the AIoT services executed by the terminals are interrupted, and the continuity of the AIoT services may be disrupted.

[0164] To address the aforementioned technical problems, this application provides a communication method and apparatus that enables a terminal to continue executing AIoT services after switching access network devices during the execution of AIoT services, thereby helping to avoid disruption of the continuity of AIoT services.

[0165] The embodiments of this application enable terminals, target access network devices, or core network elements under the Topology 2 architecture to obtain the area corresponding to the AIoT service and the location of the terminal after switching access network devices. Based on the relationship between the above areas and locations, it can determine whether the terminal should continue the AIoT service, thereby reducing the possibility of the continuity of the AIoT service being disrupted.

[0166] In the embodiments described below, the interaction between the terminal, the access network device, and the core network element is used as an example. It should be understood that the terminal can be replaced by components configured in the terminal (such as chips, chip systems, processors, etc.), or by logic modules or software capable of implementing all or part of the functions of the terminal; the access network device can also be replaced by components configured in the access network device (such as chips, chip systems, processors, etc.), or by logic modules or software capable of implementing all or part of the functions of the access network device.

[0167] Figures 3E to 3G are schematic diagrams of several communication systems applicable to embodiments of this application.

[0168] As shown in Figure 3E, the access network device (e.g., gNB) can be directly connected to the AIoT core network (AIoT CN). The AIoT CN can be an AIoT function (AIoTF) network element. Optionally, AIoTF can also be replaced by a tag management function (TMF) or an ambient IoT management function (AIoTMF), or it can have other names. This application does not limit its specific name. It can be a core network element, core network function, core network node, or core network device that supports / enables AIoT.

[0169] Since the interface name between the access network device and the core network element that supports / enables AIoT has not yet been defined, the "XX" is used uniformly in this application embodiment to refer to the interface between the access network device and the core network element that supports AIoT capabilities. The interface between the access network device and the AIoTF is the first interface. Correspondingly, XXAP can be an application protocol on the first interface (or XX interface) used to provide signaling services between the access network device and the AIoTF. One or more of the AIoT messages, data, or / and signaling that the two interact with can be included in the XXAP message.

[0170] As shown in Figure 3F, the access network device and the AIoTF are not directly connected; therefore, the first interface between the access network device and the AIoTF as shown in Figure 3E does not exist. In Figure 3F, information exchange between the access network device and the AIoTF needs to be forwarded through the AMF.

[0171] As shown in Figure 3G, the AMF connected to the access network device can be an enhanced AMF, which can serve both the UE and AIoT devices simultaneously. This can be understood as the AMF having AIoT functionality.

[0172] The AIoT-enabled terminal shown in any of Figures 3E to 3G can provide reader / writer functionality, or in other words, can execute AIoT services. The AIoT device shown in any of Figures 3E to 3G is, for example, an AIoT device. This terminal and the AIoT device can execute AIoT services. By executing these AIoT services, corresponding data can be generated. The terminal can send this data to the access network device serving the terminal, or it may choose not to send the data. Since the terminal may report the data generated from executing AIoT services with the AIoT device to the access network device, it can also be considered that the access network device, the terminal, and the AIoT device can execute AIoT services, or it can be understood that the network elements participating in the execution of AIoT services may include the access network device, the terminal, and the AIoT device. The access network device may include one or more of the following: a first access network device, a second access network device, or a core network device.

[0173] Figure 4 is a flowchart illustrating a communication method provided in an embodiment of this application. Exemplarily, this communication method is applied in a topology 2 architecture. As shown in Figure 4, the communication method may include steps S401 to S406.

[0174] S401, while the terminal is performing AIoT services, the first access network device sends a first message to the terminal, instructing the terminal to switch to the second access network device. Correspondingly, the terminal receives the first message from the first access network device.

[0175] It is understandable that the terminal, acting as an intermediate node in the Topology 2 architecture, communicates and interacts with AIoT devices to execute AIoT services. During the execution of AIoT services, the terminal is currently connected to the first access network device. If the terminal moves from the coverage area of ​​the first access network device to the coverage area of ​​the second access network device, the first access network device instructs the terminal to switch to the second access network device via a first message. Here, the first access network device is equivalent to the source access network device, and the second access network device is equivalent to the target access network device.

[0176] S402, the terminal responds to receiving the first message and accesses the second access network device.

[0177] In this step, after receiving the first message, the terminal disconnects from the first access network device and initiates access to the second access network device indicated in the first message, thereby switching from the first access network device to the second access network device.

[0178] S403, the second access network device obtains the first information, which indicates the first location of the terminal.

[0179] In this step, as one possible implementation, the terminal can obtain the first information through location services.

[0180] For example, the granularity of the first information can be cell granularity, tracking area (TA) granularity, or other base station granularity, base station service area or coverage area, etc., and this application does not impose any restrictions.

[0181] In terms of specific form, the first information can be coordinates, beams, topology (region), or identification information, etc., and this application does not limit it.

[0182] In this step, after obtaining the first information indicating its first location, the terminal can send the first information to the second access network device.

[0183] In another possible implementation, after the terminal switches access network devices, its location is within the coverage area of ​​the second access network device. Therefore, the area corresponding to the coverage area of ​​the second access network device can be used as the first location of the terminal. The second access network device can indicate the first location of the terminal by indicating the first information of the coverage area of ​​the second access network device.

[0184] S404, the second access network device obtains the first area, the first area indicating the area corresponding to the AIoT service.

[0185] Among them, AIoT services are services configured by the core network. According to the actual needs of the application scenario, the core network can configure corresponding AIoT services to serve different areas. For example, the AIoT service executed by the terminal can be an inventory service, and the inventory area corresponding to this inventory service is equivalent to the first area.

[0186] In this step, the second access network device can obtain the first region from the terminal or the first access network device. The first region indicates the region corresponding to the AIoT service executed by the terminal. This will be further explained in the following embodiments.

[0187] It should be noted that the second access network device may obtain the first information first and then the first area, or it may obtain the first area first and then the first information, or it may obtain the first area and the first information simultaneously. The execution order of the above steps S403 and S404 is not limited in this embodiment.

[0188] S405, the second access network device determines whether the terminal should continue to perform AIoT services based on the first location and the first area.

[0189] Whether the terminal continues to perform AIoT services in this application embodiment includes whether the terminal reports data corresponding to the AIoT services, and / or whether the terminal transmits data and / or signaling corresponding to the AIoT services to the AIoT devices.

[0190] It is understandable that in Topology 2 architecture, the terminal acts as an intermediate node between the access network device and the AIoT device. When communicating with the AIoT device as a reader / writer, the terminal transmits one or more of the messages, data, or signaling corresponding to the AIoT service. When communicating with the access network device, the terminal is responsible for reporting the data corresponding to the AIoT service to the access network device, and the terminal can send one or more of the messages, data, or signaling corresponding to the AIoT service to the access network device. Therefore, determining whether the terminal continues to execute the AIoT service can be specifically understood as determining whether the terminal reports the data corresponding to the AIoT service, and / or determining whether the terminal transmits the data and / or signaling corresponding to the AIoT service with the AIoT device.

[0191] In this step, the relationship between the first location and the first area provides a possible basis for the second access network device to determine whether to continue executing AIoT services.

[0192] In some implementations, if the first location is within the first area, the second access network device can determine that the terminal continues to perform AIoT services. Alternatively, if the first location is not within the first area, the second access network device can determine that the terminal does not continue to perform AIoT services.

[0193] As described above, the first area is a range of areas corresponding to the AIoT service, while the first location is a point where the terminal is located. If the first area includes the first location, it is equivalent to the first location being located in the first area. This can be understood as the terminal moving from the coverage area of ​​the first access network device to the coverage area of ​​the second access network device without leaving the area corresponding to the AIoT service. The second access network device can use this to determine whether the terminal continues to perform the AIoT service.

[0194] If the first area does not include the first location, it is equivalent to the first location not being located in the first area. It can be understood that after the terminal moves from the coverage area of ​​the first access network device to the coverage area of ​​the second access network device, it leaves the area corresponding to the AIoT service. The second access network device can use this to determine that the terminal will not continue the AIoT service.

[0195] In one possible implementation, if the first location is within a first area, the second access network device can determine that the terminal will not continue to perform AIoT services. Alternatively, if the first location is not within the first area, the second access network device can determine that the terminal will continue to perform AIoT services.

[0196] S406, the second access network device sends second information to the terminal, indicating whether the terminal should continue to perform AIoT services. Correspondingly, the terminal receives the second information from the second access network device.

[0197] It is understandable that the terminal, as the intermediate node between the second access network device and the AIoT device, is the main body responsible for continuing to execute the AIoT service. Therefore, after the judgment is made in step S405, it is also necessary to indicate to the terminal through the second information whether it should continue to execute the AIoT service.

[0198] In this embodiment, when the terminal switches from the first access network device to the second access network device, the second access network device can determine whether the terminal should continue to perform AIoT services based on the relationship between the first location and the first area, which is beneficial to maintaining the continuity of AIoT services.

[0199] It should be noted that after the terminal switches to the second access network device, it may continue to move. The communication method proposed in this application embodiment can continuously determine whether to continue AIoT services during the terminal's movement.

[0200] As one possible implementation, after determining that the terminal continues to perform AIoT services, the second access network device can obtain third information indicating the second location of the terminal. Based on the second location and the first area, the second access network device can determine whether the terminal continues to perform AIoT services.

[0201] The above determination that the terminal can continue to perform AIoT services refers to the determination that the terminal can continue to perform AIoT services while in the first location. The second location is a different location from the first location; it can be understood as the terminal moving from the first location to the second location after connecting to the second access network device. The second access network device can determine whether the terminal should continue to perform AIoT services based on the relationship between the second location and the first area. The specific determination method can be found in the previous description and will not be repeated here.

[0202] In another possible implementation, after the terminal determines that it will not continue to execute the AIoT service, it can obtain third information indicating the third location where the terminal is located. Based on the third location and the first area, it can determine whether to continue to execute the AIoT service.

[0203] The above determination that the terminal will not continue to perform AIoT services refers to determining that the terminal will not continue to perform AIoT services when it is in the first location. After the terminal connects to the second access network device, it moves from the first location to the third location. When the terminal is currently in the third location, the second access network device can determine again whether the terminal should continue to perform AIoT services based on the relationship between the third location and the first area. The specific determination method can be referred to the previous description and will not be repeated here.

[0204] As one possible implementation, during the terminal's movement, the second access network device can periodically acquire the above second or third information, and use the second or third information to indicate the terminal's current location during the movement, thereby enabling the second access network device to continuously determine whether the terminal should continue to perform AIoT services.

[0205] After the terminal connects to the second access network device, the second access network device continuously obtains the current location of the terminal and determines in real time whether the terminal should continue to perform AIoT services based on the current location of the terminal and the first area, which is conducive to further maintaining the continuity of AIoT services.

[0206] The above embodiments describe the process by which a terminal determines whether to continue executing AIoT services after switching access network devices. It is understood that there are multiple possible implementations for each step in the above process. The following describes the communication method provided in the embodiments of this application, starting with configuring AIoT services in the core network.

[0207] Figure 5 is a flowchart illustrating a communication method provided in an embodiment of this application. Exemplarily, this communication method is applied in a topology 2 architecture. The first access network device is the access network device the terminal accesses before switching access network devices, equivalent to the source access network device; the second network device is the access network device the terminal accesses after switching access network devices, equivalent to the target access network device; and the terminal can be understood as an intermediate node in the topology 2 architecture. As shown in Figure 5, the communication method may include the following steps:

[0208] S501, the core network element sends an AIoT service request to the terminal. The AIoT service request includes the identification information of the AIoT device.

[0209] The core network elements support or enable AIoT capabilities. Specifically, these can be tag management function (TMF) network elements, AIoT function (AIoTF) network elements, AIoT management function network elements, or other core network elements that support AIoT capabilities, such as access and mobility management function (AMF) network elements integrated with TMF. The specific names of these elements are not limited in this embodiment. For ease of description, the core network elements mentioned in the following embodiments are all core network elements that support or enable AIoT capabilities.

[0210] In this step, the core network elements configure the corresponding AIoT services according to the specific requirements of the application scenario and send AIoT service requests to the terminal. The AIoT service request includes the identification information of the AIoT device. This identification information can be used to identify a single AIoT device or a group of AIoT devices; for example, a mask can identify a single AIoT device, and a group ID can identify the entire group of AIoT devices.

[0211] In some implementations, the AIoT service request may also include a first region and / or identification information for the AIoT service. The first region indicates the region corresponding to the AIoT service, and the identification information for the AIoT service can be used to identify the AIoT service.

[0212] As an example, the identification information for AIoT services may include one or more of the following: service ID, session ID, task ID, or transaction ID.

[0213] It should be noted that under the Topology 2 architecture, there are currently three possible transmission solutions. These three solutions can be used to transmit one or more of the following AIoT service-related messages, data, or signaling: The terminals involved in these three transmission solutions are AIoT-enabled terminals, and the access network devices are AIoT-enabled access network devices.

[0214] Figure 6A is a schematic diagram of the protocol stack for the RRC-based transmission solution (Solution 1) under Topology 2 architecture. Since the interface names between access network devices and core network elements supporting AIoT capabilities are not currently defined, this embodiment uses "XX" to refer to the interface between the access network device and the core network elements supporting AIoT capabilities. For example, the interface between the access network device and the AMF network element is a next-generation (NG) interface, and the access network device and the AMF network element communicate via the next-generation application protocol (NGAP). Correspondingly, the access network device communicates with the core network elements supporting AIoT capabilities via the "XX" protocol (XX application protocol, XXAP).

[0215] As shown in Figure 6A, an AIoT device includes AIoT radio protocol layers that communicate with AIoT-enabled terminals. An AIoT-enabled terminal includes the AIoT radio protocol layers that communicate with the AIoT device, as well as the RRC layer, PDCP layer, RLC layer, MAC layer, and physical PHY layer that communicate with access network devices.

[0216] Access network equipment includes the RRC layer, PDCP layer, RLC layer, MAC layer, and PHY layer for communication with AIoT-enabled terminals, and the XXAP layer, Stream Control Transmission Protocol (SCTP) layer, Internet Protocol (IP) layer, Layer 2 (L2), and Layer 1 (L1) layer for communication with AIoT core network equipment. AIoT core network equipment includes the XXAP layer, SCTP layer, IP layer, L2, and L1 layer for communication with access network equipment. This AIoT core network equipment may be, for example, an AIoTF, or an AMF capable of executing AIoT services or implementing AIoT functions.

[0217] When an access network device receives a request related to AIoT services from an AIoT core network device via XXAP, it can further send the relevant information to the AIoT enabling terminal via RRC messages. When an access network device receives AIoT service-related data / signaling from an AIoT enabling terminal via RRC, it can further transmit the relevant information to the AIoT core network device via XXAP.

[0218] Figure 6B is a schematic diagram of the protocol stack for the solution (Solution 2) based on non-access stratum (NAS) transmission under Topology 2 architecture.

[0219] As shown in Figure 6B, an AIoT device includes an AIoT wireless protocol layer that communicates with the AIoT-enabled terminal. The AIoT-enabled terminal includes an AIoT wireless protocol layer that communicates with the AIoT device, a NAS layer that communicates with the AIoT core network device, and 5G-access network protocol layers (AN protocol layers) that communicate with the access network device. The access network device includes a 5G-access network protocol layer that communicates with the AIoT wireless protocol layer, and also includes NGAP, SCTP, IP, L2, and L1 layers that communicate with the AIoT core network device. The AIoT core network device includes a NAS layer that communicates with the AIoT-enabled terminal, and also includes NGAP, SCTP, IP, L2, and L1 layers that communicate with the access network device. This AIoT core network device may be, for example, a TMF (Technology Management Function), or an AMF (Application Function) capable of executing AIoT services or implementing AIoT functions.

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

[0221] Figure 6C is a schematic diagram of the protocol stack for the solution (Solution 3) based on user plane (UP) transmission under Topology 2 architecture.

[0222] As shown in Figure 6C, an AIoT device includes an AIoT radio protocol layer for communicating with the AIoT-enabled terminal. The AIoT-enabled terminal includes the AIoT radio protocol layer for communicating with the AIoT device, a protocol data unit (PDU) layer for communicating with the core network equipment, and a 5G-access network protocol layer for communicating with the access network equipment. The access network equipment includes the 5G-access network protocol layer for communicating with the AIoT-enabled terminal, and also includes the General Packet Radio Service (GPRS) tunneling protocol user plane (GTP-U) layer, user datagram protocol (UDP) layer, IP layer, L2 layer, and L1 layer for communicating with the core network equipment. The core network equipment includes the PDU layer for communicating with the AIoT-enabled terminal, and also includes the GTP-U layer, UDP layer, SCTP layer, IP layer, L2 layer, and L1 layer for communicating with the access network equipment.

[0223] The core network device is, for example, a core network user plane device, such as a UPF. This core network device can communicate with the AIoT core network device, or it can communicate with the AIoT core network device through other network elements (such as an AMF). The AIoT core network device is, for example, a TMF, or an AMF capable of executing AIoT services or implementing AIoT functions. For example, the core network device can send one or more of the AIoT service-related messages, data, or signaling from AIoT-enabled terminals or access network devices to itself; conversely, the core network device can send one or more of the AIoT service-related messages, data, or signaling from the AIoT core network device to AIoT-enabled terminals or access network devices.

[0224] AIoT service-related data / signaling between AIoT core network equipment and AIoT enabled terminals can be carried on the PDU session messages of the AIoT enabled terminal (access network equipment can transmit transparently). The access network equipment can process the user plane data of the AIoT enabled terminal through channels such as next generation user plane (NG-U) and general GTP-U.

[0225] Figures 6A, 6B, and 6C are merely exemplary protocol stacks corresponding to the three solutions described above. Alternatively, any one or more of the three solutions described above may correspond to other forms of protocol stacks, without limitation.

[0226] In step S501, the core network element can combine the above three transmission solutions to send AIoT service requests to the terminal.

[0227] In one possible implementation, the core network element can send an AIoT service request to the terminal based on Solution 1 described above, as shown in step S501a of Figure 5. The core network element can send the AIoT service request to the first access network device via an XXAP message or an NGAP message. The AIoT service request includes the identification information of the AIoT device. Accordingly, the first access network device receives the AIoT service request from the core network element.

[0228] Optionally, the AIoT service request sent by the above core network elements to the first access network device via XXAP or NGAP messages may also include the identification information of the first area and / or the AIoT service.

[0229] The first access network device is the access network device to which the terminal accesses. When the first access network device receives an AIoT service request from a core network element, as shown in step S501b of Figure 5, the first access network device can send an AIoT service request to the terminal via an RRC message. The AIoT service request includes the identification information of the AIoT device. Accordingly, the terminal receives the AIoT service request from the first access network device.

[0230] Optionally, the AIoT service request sent by the first access network device to the terminal via RRC message may also include the identification information of the first region and / or the AIoT service.

[0231] It is understandable that the content included in the AIoT service request sent by the core network element to the first access network device determines the content included in the AIoT service request sent by the first access network device to the terminal. For example, if the AIoT service request sent by the core network element to the first access network device includes the identification information of the first region and / or the AIoT service, then the AIoT service request sent by the first access network device to the terminal can include the identification information of the first region and / or the AIoT service.

[0232] In another possible implementation, the core network element can send an AIoT service request based on Solution 2 or Solution 3 described above. As shown in step S501c of Figure 5, the core network element can send an AIoT service request to the terminal via a NAS message or a PDU session message. The AIoT service request includes the identification information of the AIoT device. Accordingly, the terminal receives the AIoT service request from the core network element.

[0233] Optionally, the AIoT service request sent by the above core network elements to the terminal via NAS message or PDU session message may also include the identification information of the first region and / or the AIoT service.

[0234] It is understandable that during the process of the core network element sending AIoT service requests to the terminal based on the above solution 2 or solution 3, the access network device plays a transparent transmission role.

[0235] In some implementations, the core network element can also send configuration instruction information to the first access network device. This configuration instruction information instructs the first access network device to configure AIoT radio resources for the terminal. In this implementation, the core network element sends the configuration instruction information to the first access network device via NGAP / XXAP on the NG / XX interface. Correspondingly, the first access network device receives the configuration instruction information from the core network element via NGAP / XXAP. As the source access network device, the first access network device can decode the configuration instruction information and configure AIoT radio resources for the terminal according to the configuration instruction information.

[0236] It should be noted that after receiving an AIoT service request, the terminal can identify the corresponding AIoT device based on the identification information of the AIoT device included in the AIoT service request, and start executing the AIoT service. Specifically, this includes transmitting the data and / or signaling corresponding to the AIoT service with the AIoT device, and / or reporting the data corresponding to the AIoT service to the first access network device.

[0237] S502, the first access network device sends a handover request to the second access network device. Correspondingly, the second access network device receives the handover request from the first access network device.

[0238] Suppose that during the execution of AIoT services, the cell controlled by the first access network device moves to the range of the cell controlled by the second access network device, then the terminal needs to switch from the first access network device to the second access network device. During the handover process, the first access network device first sends a handover request to the second access network device.

[0239] In some implementations, the handover request may carry the first region. It is understood that in step S501a above, the first access network device can receive the first region and / or the identification information of the AIoT service from the core network element via XXAP or NGAP messages. Therefore, the first access network device can send the first region to the second access network device via the handover request, which is equivalent to the second access network device obtaining the first region from the first access network device.

[0240] Optionally, the switching request may also include identification information for the AIoT service.

[0241] It is understood that the interface between the first access network device and the second access network device is the Xn interface, and the handover request is equivalent to an XnAP message. The second access network device can also obtain the identification information of the first area and / or AIoT service from the first access network device through other XnAP messages.

[0242] S503, the second access network device sends a handover request acknowledgment to the first access network device. Correspondingly, the second access network device receives the handover request acknowledgment from the first access network device.

[0243] In this step, the second access network device sends a handover request confirmation to the first access network device, indicating that the read / write device is allowed to switch from the first access network device to the second access network device.

[0244] Optionally, the switching request confirmation may also include the identification information of the AIoT service.

[0245] S504, the first access network device sends a first message to the terminal, instructing the terminal to switch to the second access network device. Correspondingly, the terminal receives the first message from the first access network device.

[0246] This step corresponds to step S401 in the embodiment shown in Figure 4, where the first message can be an RRC reconfiguration message. Based on the first message, the terminal can determine that the target access network device after the handover is the second access network device.

[0247] S505 enables random access between the terminal and the second access network device.

[0248] This step corresponds to step S402 in the embodiment shown in Figure 4. In this step, the terminal responds to receiving the first message and initiates random access to the second access network device. The random access process can refer to the existing random access process, and will not be described in detail in this embodiment.

[0249] S506, the terminal sends an RRC reconfiguration complete message to the second access network device. Correspondingly, the second access network device receives the RRC reconfiguration complete message from the terminal.

[0250] In this step, the terminal sends an RRC reconfiguration complete message to the second access network device, indicating that the terminal has switched from the first access network device to the second access network device and has accessed the target cell controlled by the second access network device.

[0251] S507: The terminal determines whether to continue executing the AIoT service based on the first location and the first area.

[0252] It is understandable that the premise for the terminal to make a judgment based on the first location and the first area is to obtain the first information and the first area, and the method by which the terminal obtains the first area is already implicit in the aforementioned steps.

[0253] In some implementations, if the AIoT service request in step S501 includes a first region, it is equivalent to the terminal obtaining the first region from the AIoT service request. For example, if the transmission of AIoT service-related data and / or signaling is implemented in Topology 2 based on Solution 1 above, the terminal can obtain the first region from the first access network device via an RRC message. If the transmission of AIoT service-related data and / or signaling is implemented in Topology 2 based on Solution 1 or Solution 3 above, the terminal can obtain the first region from the core network element via a NAS message or a PDU session message.

[0254] In some implementations, when the first access network device sends a first message to the terminal in step S504 above, the first message may include a first area, which is equivalent to the terminal obtaining the first area from the first message. For example, the first access network device sends an RRC reconfiguration message to the terminal, which includes the first area, and the terminal obtains the first area through a message indicating a switch to the second access network device.

[0255] As one possible implementation, if the second access network device obtains the first area from the first access network device via an XnAP message in step S502, the second access network device can carry the first area in a broadcast system message. Correspondingly, the terminal obtains the first area via the system message broadcast by the second access network device. Alternatively, the second access network device can also directly indicate the first area to the terminal via an RRC message.

[0256] After the terminal connects to the second access network device, it can obtain first information, which indicates the terminal's first location. The steps for the terminal to obtain the first information are omitted in Figure 5. Referring to the embodiment shown in Figure 4, the terminal can obtain this first information through a location service. This application embodiment does not limit the method by which the terminal obtains the first information.

[0257] In this step, after acquiring the first area and the first information, the terminal can determine whether to continue executing the AIoT service based on the relationship between the first location and the first area. It should be noted that, compared to step S405 in the embodiment shown in Figure 4, the subject performing the judgment action in step S707 changes from the second access network device to the terminal, but the underlying judgment logic remains unchanged. The terminal's determination of whether to continue executing the AIoT service can be found in the embodiment shown in Figure 4; to avoid redundancy, further explanation is omitted here.

[0258] As described above, the terminal can continue to move after switching to the second access network device. After determining that it will continue to perform AIoT services at the first location, the terminal moves from the first location to the second location. Furthermore, the terminal can obtain third information indicating the second location and, based on the relationship between the second location and the first area, determine whether the terminal should continue to perform AIoT services at the second location.

[0259] Alternatively, after the terminal determines that it will not continue to perform AIoT services at the first location, it moves from the first location to the third location. Furthermore, the terminal can obtain the fifth information indicating the third location and determine whether the terminal should continue to perform AIoT services at the third location based on the relationship between the third location and the first area.

[0260] It should be noted that if the transmission of AIoT service-related data and / or signaling is implemented based on Solution 1 above in Topology 2 architecture, when the terminal switches access network devices, the terminal also needs to consider whether the second access network device to which the terminal is connected supports AIoT capabilities when determining whether to continue executing AIoT services.

[0261] The access network device in this application embodiment supports AIoT capabilities, which can be understood as the access network device supporting one or more of the following capabilities: scheduling AIoT wireless resources, allocating AIoT wireless resources, controlling AIoT wireless resources, managing and scheduling AIoT wireless resources, and transmitting (including sending and / or receiving) data and / or signaling related to AIoT services. The specific manifestation of the access network device supporting AIoT capabilities is not limited in this application embodiment.

[0262] In one possible implementation, the terminal can obtain first capability information, which indicates whether the second access network device supports AIoT capabilities. Accordingly, in step S507, the terminal determines whether to continue executing the AIoT service based on the first location and the first region, including: if the first location is located in the first region and the second access network device supports AIoT capabilities, the terminal determines to continue executing the AIoT service. Alternatively, if the first location is located in the first region and the second access network device does not support AIoT capabilities, the terminal determines not to continue executing the AIoT service.

[0263] In this implementation, provided that the first location is within the first region, whether the second access network device supports AIoT capabilities provides a new basis for the terminal to determine whether to continue executing AIoT services. The terminal can determine whether the second access network device supports AIoT capabilities through the first capability information.

[0264] If the first location is located in the first area and the second access network device supports AIoT capabilities, then in the subsequent process, the second access network device can allocate AIoT wireless resources required for the terminal to communicate with the AIoT device, and the terminal can then determine whether to continue performing AIoT services.

[0265] If the first location is in the first area and the second access network device supports AIoT capabilities, the second access network device cannot allocate the AIoT wireless resources required for the terminal device to communicate with the AIoT device, and the terminal determines not to continue performing AIoT services based on this.

[0266] Understandably, a terminal can obtain the first capability information in various ways. In some implementations, the second access network device can carry the first capability information in a broadcast system message, and the terminal obtains the first capability information through the system message broadcast by the second access network device. Alternatively, after the terminal accesses the second access network device, the second access network device can send the first capability information to the terminal through an RRC message.

[0267] As one possible implementation, different access network devices can exchange their capability information in advance. As shown in step S500a of Figure 5, the second access network device sends an Xn interface configuration request (SETUP REQUEST) to the first access network device. This Xn interface configuration request may include first capability information; that is, the second network device can send first capability information to the first network device through the Xn interface configuration request. Correspondingly, the first access network device receives the Xn interface configuration request from the second access network device.

[0268] As shown in step S500b of Figure 5, the first access network device sends a response to the second access network device regarding the Xn interface configuration request. This response may include second capability information, which indicates whether the first access network device supports AIoT capabilities. In other words, the first access network device can send first capability information to the second access network device through the response to the Xn interface configuration request. Correspondingly, the second access network device receives the response to the Xn interface configuration request from the first access network device.

[0269] It is understood that the above Xn interface configuration request and / or the response to the Xn interface configuration request are XnAP messages between the first access network device and the second access network device. The second access network device can also send first capability information to the first access network device through other XnAP messages, and the first access network device can also send second capability information to the second access network device through other XnAP messages.

[0270] In this implementation, through interaction between access network devices, the first access network device obtains the first capability information. The first access network device can carry this first capability information in the AIoT service request in step S501b, and the terminal obtains the first capability information through the AIoT service request sent by the first access network device. Alternatively, the first access network device can carry the first capability information in a broadcast system message, and the terminal obtains the first capability information through the system message broadcast by the first access network device. Or, the first access network device can carry the first capability information in the first message in step S504, and the terminal obtains the first capability information through the first message.

[0271] As another possible implementation, the access network device can also interact with the core network element to exchange its capability information. As shown in step S500c of Figure 5, the second access network device sends an XX / NG interface configuration request to the core network element. This XX / NG interface configuration request may include first capability information; that is, the second access network device can send first capability information to the core network element through the XX / NG interface configuration request. Correspondingly, the core network element receives the XX / NG interface configuration request from the second access network device.

[0272] As shown in step S500d of Figure 5, the first access network device sends an XX / NG interface configuration request to the core network element. The XX / NG interface configuration request may include second capability information. Correspondingly, the core network element receives the core network element configuration request from the first access network device.

[0273] In this implementation, the core network element obtains the first capability information through capability information interaction between the access network device and the core network element. The first capability information can be carried in the AIoT service request in step S501c, and the terminal obtains the first capability information through the AIoT service request sent by the core network element.

[0274] It should be noted that the core network element can also send a response to the XX / NG interface configuration request to the first access network device. This response includes first capability information; that is, the core network element sends first capability information to the first access network device through the response to the XX / NG interface configuration request. Correspondingly, the first network device receives the response to the XX / NG interface configuration request from the core network element.

[0275] It is understood that the above XX / NG interface configuration requests and / or responses to XX / NG interface configuration requests are XXAP / NGAP messages between access network devices and core network elements. Network devices and core network elements can also exchange the above capability information through other XXAP / NGAP messages.

[0276] The first access network device can obtain the first capability information from the core network element and carry the above first capability information in the AIoT service request in step S501b. The terminal obtains the first capability information through the AIoT service request sent by the first access network device.

[0277] In one implementation, if the transmission of AIoT service-related data and / or signaling is implemented in the topology 2 architecture based on the above solution 1, and the first access network device determines that the second access network device does not support AIoT capabilities based on the first capability information, then step 502 can be omitted, that is, the first access network device does not send a handover request to the second access network device, and the process terminates.

[0278] In step S508, the second access network device sends a PATH SWITCH REQUEST message to the core network element. Correspondingly, the core network element receives the PATH SWITCH REQUEST message from the second access network device.

[0279] In this step, the second access network device indicates to the core network element that the terminal has switched serving cells via a path change request message. The path change request message may carry the identification information of the target cell accessed by the terminal after switching access network devices and the list of PDU sessions switched. Correspondingly, upon receiving this message, the core network element updates the downlink GTP-U data plane, modifying the GTP-U address on the access network device side to that of the second access network device.

[0280] In step S509, the core network element sends a Path Switch Request Acknowledgment (PATH SWITCH REQUEST ACKNOWLEDGE) message to the second access network device. Correspondingly, the second access network device receives the PATH SWITCH REQUEST ACKNOWLEDGE message from the core network element.

[0281] In some implementations, the path change request confirmation message may carry authorization indication information. The authorization indication information is used to instruct the authorized terminal to act as a reader / writer for the AIoT service, or to instruct the terminal to execute the AIoT service, or to instruct the terminal to act as an AIoT enabling terminal for the AIoT service, or to instruct the terminal to communicate with the AIoT device, or to instruct the terminal to transmit one or more of the messages, data, or signaling related to the AIoT service to the AIoT device.

[0282] Optionally, the path change request confirmation message may also include identification information of the AIoT service.

[0283] It should be noted that there is no strict order between steps S507 and S508 and S509. Step S507 can be executed before step S508 or after step S509.

[0284] As one possible implementation, after the terminal determines in step S507 that it will not continue executing the AIoT service, the terminal can release the tenth information, which includes the data and / or signaling corresponding to the AIoT service stored before the terminal accesses the second access network device. Alternatively, the terminal can retain the tenth information until the terminal accesses the third access network device.

[0285] It is understood that during the execution of AIoT services, the terminal stores the data and / or signaling corresponding to AIoT services that have not yet been reported in the storage space. The tenth information includes the data and / or signaling corresponding to AIoT services stored before accessing the second access network device. After the terminal determines that it will not continue to execute the AIoT service, it can directly release the above tenth information. In this embodiment, "release" can be understood as deleting the information in the storage space.

[0286] It should be noted that if the terminal retains the tenth information until it accesses the third access network device, the terminal can determine whether to continue executing the AIoT service again based on its location and the first area after accessing the third access network device.

[0287] In some implementations, the terminal can also release the tenth information after the retention period reaches a first preset duration. Unlike directly releasing the tenth information, the terminal can retain the tenth information in storage until the retention period reaches the preset duration, after which the terminal deletes the tenth information from storage.

[0288] In some implementations, if the terminal determines to continue performing AIoT services and the second access network device supports AIoT capabilities, step S510 in Figure 5 can be executed. The second access network device sends first resource information and / or radio bearer (RB) configuration information to the terminal. The first resource information is used to indicate the first resource, which is the AIoT radio resource used by the terminal to communicate with the AIoT device. The RB configuration information is used to indicate the first RB, which is dedicated to transmitting data and / or signaling related to AIoT services.

[0289] In this step, the second access network device can send an RRC message to the terminal. The RRC message includes first resource information and / or RB configuration information. That is, the second access network device sends the first resource information and / or RB configuration information to the terminal through the RRC message.

[0290] As one possible implementation, the first resource can be the AIoT wireless resource used by the terminal and the AIoT device to communicate in the first cell, which is the cell that the terminal is currently accessing after switching to the second access network device.

[0291] It is understood that the first resource information indicates the first resource configured by the second access network device for the terminal. This first resource is applicable to device-to-reader (D2R) and / or reader-to-device (D2R) communication between the terminal and AIoT devices on the currently accessed first cell. If the terminal moves from the first cell to another cell controlled by the second access network device, the first resource indicated by the first resource information will not be applicable to the other cell.

[0292] As an example, the first resource information can be used to indicate the AIoT wireless resource configuration, including both time and frequency domains. The time-domain resource configuration can indicate the resource duration. If the terminal determines that the duration of the AIoT wireless resources configured by the second access network device is insufficient to complete the AIoT service, the reader can request AIoT wireless resources from the second access network device. Correspondingly, the second access network device can reallocate or reschedule new AIoT wireless resources for the terminal. Optionally, the first resource information can also be used to indicate the maximum power at which the terminal transmits signals to the AIoT device.

[0293] In another possible implementation, the first resource can also be the AIoT wireless resource used by the terminal and the AIoT device to communicate in the second cell, which includes multiple cells covered by the second access network device.

[0294] In this implementation, the second cell is distinct from the first cell and includes multiple cells controlled by the second access network device. If the terminal moves from the currently accessed cell to another cell controlled by the second access network device, the terminal can communicate with the AIoT device using the first resource indicated by the first resource information.

[0295] In some implementations, the first resource is the AIoT wireless resource used by the terminal to communicate with the AIoT device during cell handover or access network device handover.

[0296] In this implementation, the first resource is equivalent to a special resource pool. When the terminal moves from the currently accessed cell to another cell controlled by the second access network device, or when the terminal moves from the coverage area of ​​the second access network device to the coverage area of ​​another access network device, the terminal can use this special AIoT wireless resource to communicate with AIoT devices.

[0297] The second access network device can configure the special resource pool for the terminal through RRC signaling, or it can configure the special resource pool for the terminal through system messages. This application embodiment does not limit the method by which the second access network device configures the special resource pool for the terminal.

[0298] In some implementations, the first access network device can send second resource information to the terminal. This second resource information indicates a second resource, which is the AIoT radio resource used by the terminal to communicate with the AIoT device during cell handover or access network device handover. Accordingly, the terminal receives the second resource information from the first access network device.

[0299] In this implementation, the second resource indicated by the second resource information is also a special resource pool, the difference being that this special AIoT wireless resource is configured for the terminal by the first access network device. It should be noted that the first access network device can send the second resource information to the terminal before the terminal responds to the first message; that is, the first access network device can configure the special AIoT wireless resource for the terminal before disconnecting from the terminal.

[0300] In some implementations, core network elements can also configure special resource pools for terminals. For example, core network elements can send third resource information to the terminal, which indicates third resources. These third resources are AIoT radio resources used by the terminal to communicate with AIoT devices during cell handover or access network device handover.

[0301] It should be noted that the core network element can send the aforementioned third resource information to the terminal in step S501 or before S501. Alternatively, the core network element can also carry the third resource information in the authorization indication information sent to the second access network device, and the second access network device can send the third resource information to the terminal via an RRC message. The core network element can configure the AIoT radio resources indicated by the third resource information to the terminal's subscriber identity module (SIM), or it can configure the AIoT radio resources indicated by the third resource information to the terminal's mobile equipment (ME) or universal integrated circuit card (UICC).

[0302] One or more of the messages, data or signaling for AIoT services transmitted between the terminal and the second access network device can reuse existing RBs between the terminal and the second access network device, such as reusing existing data radio bearers (DRBs) and / or signaling radio bearers (SRBs) between the terminal and the second access network device.

[0303] Alternatively, in this step, the second access network device can send RB configuration information to the terminal via RRC messages (such as RRC reconfiguration messages). The first RB indicated by the RB configuration information is a dedicated RB for transmitting AIoT services, which can be referred to as a dedicated RB. The RB configuration information can establish a new RB for the terminal to serve the AIoT service, which may include the terminal's current AIoT service and / or other AIoT services of the UE. Here, the first RB indicated by the RB configuration information may include a dedicated SRB and / or a dedicated DRB. The terminal can transmit AIoT service-related data and / or signaling with the AIoT device through the newly established SRB x / DRB x.

[0304] Understandably, terminals can also report AIoT service-related data and / or signaling to the second access network device through existing SRB1 / 2 or DRB.

[0305] It should be noted that, assuming the terminal decides to continue executing the AIoT service, after step S510, if the transmission of AIoT service-related data and / or signaling is implemented based on Solution 1, the terminal can first send AIoT service-related data and / or signaling to the second access network device via RRC message, and then the second access network device can send the AIoT service-related data and / or signaling to the core network element via XXAP / NGAP.

[0306] If the transmission of AIoT service-related data and / or signaling is implemented based on Solution 2 or Solution 3, the terminal can send AIoT service-related data and / or signaling to the core network element through NAS messages or PDU session messages, where the second access network device plays a transparent transmission role.

[0307] In the embodiment shown in Figure 5 above, the terminal determines whether to continue executing the AIoT service based on the first location and the first area. The subject executing the judgment action is the terminal. In some implementations, the subject executing the judgment action can also be a second access network device or a core network element. The following describes the different subjects executing the judgment action.

[0308] Figure 7 is a flowchart illustrating a communication method provided in another embodiment of this application. Exemplarily, this communication method is applied in a topology 2 architecture. The first access network device is the access network device the terminal accesses before switching access network devices, equivalent to the source access network device; the second network device is the access network device the terminal accesses after switching access network devices, equivalent to the target access network device; and the terminal can be understood as an intermediate node in the topology 2 architecture. As shown in Figure 7, the communication method may include the following steps:

[0309] S701, the core network element sends an AIoT service request to the terminal. The AIoT service request includes the identification information of the AIoT device.

[0310] This step is consistent with step S501 in the embodiment shown in Figure 5.

[0311] Referring to the embodiment shown in Figure 5, if the transmission of AIoT service-related data and / or signaling is implemented in Topology 2 based on Solution 1 described above, as shown in step S701a of Figure 7, the core network element can send an AIoT service request to the first access network device via an XXAP message or an NGAP message. The AIoT service request includes the identification information of the AIoT device. Accordingly, the first access network device receives the AIoT service request from the core network element.

[0312] As shown in step S701b of Figure 7, the first access network device can send an AIoT service request to the terminal via an RRC message. The AIoT service request includes the identification information of the AIoT device. Correspondingly, the terminal receives the AIoT service request from the first access network device.

[0313] If the transmission of AIoT service-related data and / or signaling is implemented in Topology 2 based on Solution 2 or Solution 3 as described above, as shown in step S701c of Figure 7, the core network element can send an AIoT service request to the terminal via NAS messages or PDU session messages. The AIoT service request includes the identification information of the AIoT device. Correspondingly, the terminal receives the AIoT service request from the core network element. The access network device plays a transparent transmission role.

[0314] It is understood that the above steps S701a to S701c are the same as steps S501a to 501c in the embodiment shown in Figure 5, and will not be repeated here.

[0315] S702, the first access network device sends a handover request to the second access network device. Correspondingly, the second access network device receives the handover request from the first access network device.

[0316] S703, the second access network device sends a handover request confirmation to the first access network device. Correspondingly, the second access network device receives the handover request confirmation from the first access network device.

[0317] S704, the first access network device sends a first message to the terminal, instructing the terminal device to switch to the second access network device. Correspondingly, the terminal receives the first message from the first access network device.

[0318] S705 enables random access between the terminal and the second access network device.

[0319] S706, the terminal sends an RRC reconfiguration complete message to the second access network device. Correspondingly, the second access network device receives the RRC reconfiguration complete message from the terminal.

[0320] The steps S702 to S706 above are the same as steps S502 to S506 in the embodiment shown in Figure 5, and will not be repeated here.

[0321] S707, the second access network device determines whether the terminal should continue to perform AIoT services based on the first location and the first area.

[0322] This step corresponds to step S405 in the embodiment shown in Figure 4. It can be understood that the second access network device determines whether the terminal should continue to perform AIoT services. The second access network device needs to obtain the first information and the first area. The method by which the second access network device obtains the first area is implicit in the aforementioned steps.

[0323] Referring to the embodiment shown in Figure 5, as a possible implementation, if the transmission of AIoT service-related data and / or signaling is implemented in the topology 2 architecture based on the above-described solution 1, and the AIoT service request in step S701a includes the first region, the first access network device can obtain the first region from the AIoT service request. Correspondingly, the handover request sent by the first access network device to the second access network device in step S702 can include the first region, which is equivalent to the second access network device obtaining the first region from the first access network device via an XnAP message.

[0324] In some implementations, if the AIoT service request in step S701 includes the first region, it is equivalent to the terminal obtaining the first region from the AIoT service request. Accordingly, the RRC reconfiguration completion message in step S706 can carry the first region, which means the second access network device can obtain the first region from the terminal through the RRC message.

[0325] Optionally, the RRC reconfiguration completion message in step S706 may also carry the identification information of the AIoT service.

[0326] After the terminal connects to the second access network device, it can obtain first information, which indicates the terminal's first location. Referring to the embodiment shown in Figure 4, the terminal can obtain this first information through a location service. After obtaining the first information, the terminal sends the first information to the second access network device, which is equivalent to the second access network device obtaining the first information from the terminal. The step of the second access network device obtaining the first information is omitted in Figure 7.

[0327] It should be noted that the RRC reconfiguration completion message in step S706 may also include request information. This request information is used to request whether to continue executing the AIoT service, and it is used to trigger step S707. It is understood that the second access network device can actively execute step S707, or it can be triggered to execute step S707 by the request information included in the RRC reconfiguration completion message in step S706.

[0328] In this step, after obtaining the first area and the first information, the second access network device can determine whether the terminal should continue to perform AIoT services based on the relationship between the first location and the first area. The specific implementation of step S507 can be referred to the embodiment shown in Figure 4.

[0329] As an example, if the first location is within the first area, the second access network device can determine that the terminal continues to perform AIoT services. Alternatively, if the first location is not within the first area, the second access network device can determine that the terminal does not continue to perform AIoT services.

[0330] In another example, if the first location is within the first area, the second access network device can determine that the terminal will not continue to perform AIoT services. Alternatively, if the first location is not within the first area, the second access network device can determine that the terminal will continue to perform AIoT services.

[0331] Referring to the embodiment shown in Figure 5, if the transmission of AIoT service-related data and / or signaling is implemented in Topology 2 based on Solution 1 described above, in the event of a terminal access network device switchover, the second access network device needs to consider whether it supports AIoT capabilities when determining whether the terminal should continue executing AIoT services. It is understood that the second access network device can determine whether it supports AIoT capabilities without needing to exchange capability information with other access network devices or core network elements.

[0332] As one possible implementation, the first location is within a first area, and the second access network device supports AIoT capabilities; the second access network device determines that the terminal will continue to perform AIoT services. Alternatively, the first location is within a first area, and the second access network device does not support AIoT capabilities; the second access network device determines that the terminal will not continue to perform AIoT services.

[0333] S708, the second access network device sends second information to the terminal, indicating whether to continue executing the AIoT service. Correspondingly, the terminal receives the second information from the second access network device.

[0334] This step corresponds to step S406 in the embodiment shown in Figure 4. After the judgment is made in step S707, it is also necessary to send a second message to the terminal through an RRC message to indicate whether to continue to execute the AIoT service.

[0335] In some implementations, if the RRC reconfiguration completion message in step S706 carries the identification information of the AIoT service, the second information may also include the identification information of the AIoT service.

[0336] As described above, the terminal can continue to move when it switches to the second access network device.

[0337] In one possible implementation, after the second access network device determines that the AIoT service will continue to be executed at the first location of the terminal, the terminal moves from the first location to the second location. The second access network device can obtain third information indicating the second location and, based on the relationship between the second location and the first area, determine whether the terminal should continue to execute the AIoT service at the second location. Accordingly, the second access network device sends fourth information to the terminal device, indicating whether to continue executing the AIoT service.

[0338] In another possible implementation, after the second access network device determines that the terminal will not continue performing AIoT services at the first location, the terminal moves from the first location to the third location. The second access network device can obtain fifth information indicating the third location and, based on the relationship between the third location and the first area, determine whether the terminal should continue performing AIoT services at the third location. Accordingly, the second access network device sends sixth information to the terminal, indicating whether to continue performing AIoT services.

[0339] S709, the second access network device sends a path change request message to the core network element. Correspondingly, the core network element receives the path change request message from the second access network device.

[0340] S710, the core network element sends a path change request confirmation message to the second access network device. Correspondingly, the second access network device receives the path change request confirmation message from the core network element.

[0341] The steps S709 and S710 above are the same as steps S508 and S509 in the embodiment shown in Figure 5, and will not be repeated here.

[0342] Optionally, the path change request confirmation message may carry authorization indication information. The authorization indication information is used to instruct the authorized terminal to act as a reader / writer for the AIoT service, or to instruct the terminal to execute the AIoT service, or to instruct the terminal to act as an AIoT enabling terminal for the AIoT service, or to instruct the terminal to communicate with the AIoT device, or to instruct the terminal to transmit one or more of the messages, data, or signaling related to the AIoT service to the AIoT device.

[0343] [Revised according to Rule 91, April 22, 2026] It is understood that the above authorization instruction information may also be carried in other NGAP / XXAP messages.

[0344] It should be noted that there is no strict order between steps S707 and S708 and steps S709 and S710. Steps S707 and S708 can be executed before or after steps S709 and S710.

[0345] In some implementations, when the second access network device determines that the terminal continues to perform AIoT services and the second access network device supports AIoT capabilities, step S711 in Figure 7 can be executed. The second access network device sends first resource information and / or RB configuration information to the terminal. The first resource information is used to indicate the first resource, which is the AIoT wireless resource used by the terminal to communicate with the AIoT device. The RB configuration information is used to indicate the first RB, which is dedicated to transmitting data and / or signaling related to AIoT services.

[0346] Step S711 is the same as step S510 in the embodiment shown in Figure 5, and will not be described in detail here.

[0347] Figure 8 is a flowchart illustrating a communication method provided in another embodiment of this application. Exemplarily, this communication method is applied in a topology 2 architecture. The first access network device is the access network device the terminal accesses before switching access network devices, equivalent to the source access network device; the second network device is the access network device the terminal accesses after switching access network devices, equivalent to the target access network device; and the terminal can be understood as an intermediate node in the topology 2 architecture. As shown in Figure 8, the communication method may include the following steps:

[0348] S801, the core network element sends an AIoT service request to the terminal. The AIoT service request includes the identification information of the AIoT device.

[0349] This step is consistent with step S501 in the embodiment shown in Figure 5.

[0350] Referring to the embodiment shown in Figure 5, if the transmission of AIoT service-related data and / or signaling is implemented in Topology 2 based on Solution 1 described above, as shown in step S801a in Figure 8, the core network element can send an AIoT service request to the first access network device via an XXAP message or an NGAP message. The AIoT service request includes the identification information of the AIoT device. Accordingly, the first access network device receives the AIoT service request from the core network element.

[0351] As shown in step S801b of Figure 8, the first access network device can send an AIoT service request to the terminal via an RRC message. The AIoT service request includes the identification information of the AIoT device. Correspondingly, the terminal receives the AIoT service request from the first access network device.

[0352] If the transmission of AIoT service-related data and / or signaling is implemented in Topology 2 based on Solution 2 or Solution 3 as described above, as shown in step S801c of Figure 8, the core network element can send an AIoT service request to the terminal via NAS messages or PDU session messages. The AIoT service request includes the identification information of the AIoT device. Correspondingly, the terminal receives the AIoT service request from the core network element. The access network device plays a transparent transmission role.

[0353] The steps S801a to S801c above are the same as steps S501a to 501c in the embodiment shown in Figure 5, and will not be repeated here.

[0354] In step S802, the first access network device sends a handover request to the second access network device. Correspondingly, the second access network device receives the handover request from the first access network device.

[0355] S803, the second access network device sends a handover request confirmation to the first access network device. Correspondingly, the second access network device receives the handover request confirmation from the first access network device.

[0356] In step S804, the first access network device sends a first message to the terminal, instructing the terminal device to switch to the second access network device. Correspondingly, the terminal receives the first message from the first access network device.

[0357] S805 enables random access between the terminal and the second access network device.

[0358] The steps S802 to S805 above are the same as steps S502 to 505 in the embodiment shown in Figure 5, and will not be repeated here.

[0359] S806, the terminal sends an RRC reconfiguration complete message to the second access network device. Correspondingly, the second access network device receives the RRC reconfiguration complete message from the terminal.

[0360] This step is the same as step S506 in the embodiment shown in Figure 5.

[0361] In some implementations, the RRC reconfiguration completion message also includes request information, which requests whether to continue executing the AIoT service. Optionally, the RRC reconfiguration completion message may also include identification information for the AIoT service.

[0362] Understandably, the terminal can also send the above request information to the second access network device through other RRC messages.

[0363] S807, the second access network device sends a path change request message to the core network element. Correspondingly, the core network element receives the path change request message from the second access network device.

[0364] In some implementations, the path change request message in this step may include the request information from step S806. Optionally, if the identification information of the AIoT service is received in step S806, the path change request message may also include the identification information of the AIoT service.

[0365] S808: The core network element determines whether the terminal should continue to execute AIoT services based on the first location and the first area.

[0366] Unlike step S507 in the embodiment shown in Figure 5, in this step, the core network element determines whether the terminal should continue executing the AIoT service. The core network element needs to obtain the first information and the first region. It can be understood that in step S501, the core network element configures the corresponding AIoT service according to the specific requirements of the application scenario. The core network element maintains relevant information about the AIoT service, therefore, the core network element can obtain the first region internally.

[0367] After the terminal connects to the second access network device, it can obtain first information, which indicates the terminal's first location. For example, the terminal can obtain this first information through a location service. If the transmission of AIoT service-related data and / or signaling is implemented based on Solution 1 in Topology 2, the terminal can transmit the first information to the second access network device via RRC messages, and the second access network device can send the first information to the core network element via XXAP or NGAP messages. If the transmission of AIoT service-related data and / or signaling is implemented based on Solution 2 or Solution 3 in Topology 2, the terminal can send the first information to the core network element via NAS messages or PDU session messages. The steps related to the core network element obtaining the first information are omitted in Figure 8.

[0368] In this step, after acquiring the first area and the first information, the core network element can determine whether the terminal should continue to execute the AIoT service based on the relationship between the first location and the first area. Similar to the embodiment shown in Figure 7, the entity performing the determination action in step S808 changes from the second access network device to the core network element.

[0369] In some possible implementations, if the first location is located in the first region, the core network element can determine that the terminal continues to perform AIoT services. Alternatively, if the first location is not located in the first region, the core network element can determine that the terminal does not continue to perform AIoT services.

[0370] In some other possible implementations, if the first location is located in the first region, the core network element can determine that the terminal will not continue to execute AIoT services. Alternatively, if the first location is not located in the first region, the core network element can determine that the terminal will continue to execute AIoT services.

[0371] Referring to the embodiment shown in Figure 5, if the transmission of AIoT service-related data and / or signaling is implemented in the topology 2 architecture based on the above solution 1, when the terminal experiences access network device switching, the core network element also needs to consider whether the second access network device supports AIoT capabilities when determining whether the terminal should continue to execute AIoT services.

[0372] As one possible implementation, the core network element can obtain first capability information, which indicates whether the second access network device supports AIoT capabilities. Accordingly, in step S808, the core network element determines whether the terminal should continue executing AIoT services based on the first location and the first region, including: if the first location is within the first region and the second access network device supports AIoT capabilities, the core network element determines that the terminal should continue executing AIoT services. Alternatively, if the first location is within the first region and the second access network device does not support AIoT capabilities, the core network element determines that the terminal should not continue executing AIoT services.

[0373] In some implementations, during the interaction of capability information between the access network device and the core network element, the core network element can obtain the first capability information. As shown in step 800a of Figure 8, the second access network device sends an XX / NG interface configuration request to the core network element. This XX / NG interface configuration request may include the first capability information; that is, the second access network device can send the first capability information to the core network element through the XX / NG interface configuration request. Correspondingly, the core network element receives the XX / NG interface configuration request from the second access network device.

[0374] As shown in step S800b of Figure 8, the first access network device sends an XX / NG interface configuration request to the core network element. The XX / NG interface configuration request may include second capability information. Correspondingly, the core network element receives the core network element configuration request from the first access network device.

[0375] The first capability information and / or the second capability information mentioned above may also be included in other NGAP / XXAP messages.

[0376] It is understandable that the above capability information exchange process occurs before the core network element configures AIoT services, and the access network device to which the terminal is connected has not yet been determined. Therefore, both the first access network device and the second access network device exchange their capability information with the core network element.

[0377] S809, the core network element sends a path change request confirmation message to the second access network device. Correspondingly, the second access network device receives the path change request confirmation message from the core network element.

[0378] In some implementations, the path change request confirmation message may include second information, which indicates whether to continue executing the AIoT service. It is understood that the terminal, as the intermediate node between the second access network device and the AIoT device, is the entity responsible for continuing to execute the AIoT service. Therefore, after the judgment in step S808, the result of the judgment in step S808 also needs to be indicated by a seventh message.

[0379] Optionally, the path change request confirmation message may also carry authorization indication information. The authorization indication information is used to instruct the authorized terminal to act as a reader / writer for the AIoT service, or to instruct the terminal to execute the AIoT service, or to instruct the terminal to act as an AIoT enabling terminal for the AIoT service, or to instruct the terminal to communicate with the AIoT device, or to instruct the terminal to transmit one or more of the messages, data, or signaling related to the AIoT service to the AIoT device.

[0380] S810, the second access network device sends an RRC message to the terminal. Correspondingly, the terminal receives the RRC message from the second access network device.

[0381] The RRC message in this step includes the second information indicated in step S809. The second access network device sends the seventh information to the terminal through the RRC message, thereby indicating whether to continue executing the AIoT service.

[0382] It should be noted that the terminal can continue to move even after switching to the second access network device.

[0383] In one possible implementation, after the core network element determines that AIoT services will continue at the first location of the terminal, the terminal moves from the first location to a second location. The core network element can obtain third information indicating the second location and, based on the relationship between the second location and the first area, determine whether the terminal should continue performing AIoT services at the second location. Accordingly, the core network element sends seventh information to the second access network device, indicating whether to continue performing AIoT services. The second access network device then sends this eighth information to the terminal via an RRC message.

[0384] In another possible implementation, after the core network element determines that the terminal will not continue performing AIoT services at the first location, the terminal moves from the first location to the third location. The core network element can obtain fifth information indicating the third location and, based on the relationship between the third location and the first area, determine whether the terminal should continue performing AIoT services at the third location. Accordingly, the core network element sends eighth information to the second access network device, indicating whether to continue performing AIoT services. The second access network device sends this eighth information to the terminal via an RRC message.

[0385] In some implementations, when the second access network device determines that the terminal continues to perform AIoT services and the second access network device supports AIoT capabilities, the second access network device can send first resource information and / or RB configuration information to the terminal through the RRC message in this step. The first resource information is used to indicate the first resource, which is the AIoT radio resource used by the terminal to communicate with the AIoT device. The RB configuration information is used to indicate the first RB, which is dedicated to transmitting data and / or signaling related to AIoT services.

[0386] For an explanation of the above first resource information and RB configuration information, please refer to the foregoing embodiments; further details will not be provided here.

[0387] It should be noted that if the path change request message in step S807 includes request information, step S808 can be executed above; otherwise, steps S807 and S809 are the same as steps S508 and S509 in the embodiment shown in Figure 5.

[0388] If the transmission of AIoT service-related data and / or signaling is implemented in the topology 2 architecture based on the above solution 2 or solution 3, in some implementations, as shown in step S811 in Figure 8, the terminal sends a request message to the core network element through NAS message or PDU session message. This request message is used to request whether to continue executing the AIoT service.

[0389] It is understandable that after step S811, as shown in step S812 of Figure 8, the core network element can determine whether the terminal should continue to execute the AIoT service based on the first location and the first area. This step is optional, and its specific implementation is the same as step S808, so it will not be described again here.

[0390] Accordingly, as shown in step S813 of Figure 8, the core network element sends a second message to the terminal through a NAS message or a PDU session message. The second message indicates whether to continue executing the AIoT service.

[0391] As can be seen from the embodiments shown in Figures 5, 7 and 8 above, the execution subject of the AIoT service in this embodiment is the terminal. Therefore, after the terminal responds to the first message and accesses the second access network device, it can obtain the ninth information and determine whether to continue executing the AIoT service based on the ninth information.

[0392] In some implementations, the ninth piece of information is used to indicate whether to continue executing the AIoT service. It is understood that the terminal can directly indicate whether to continue executing the AIoT service through the acquired ninth piece of information. Corresponding to the embodiments shown in Figures 7 and 8 above, the ninth piece of information can be the same as the second, fourth, sixth, seventh, or eighth pieces of information.

[0393] In some implementations, the ninth information may include the first information and the first region. That is, corresponding to the embodiment shown in Figure 5 above, the terminal can determine whether to continue to execute the AIoT service after obtaining the first information and the first region.

[0394] In the above embodiments, the concept for solving the technical problem is to obtain the location of the terminal after it accesses the second access network device and the area corresponding to the AIoT service, and determine whether the terminal should continue to execute the AIoT service based on the relationship between the location and the area.

[0395] It should be noted that if a device switch occurs on the access network during the execution of an AIoT service, some basic operations can be performed without considering complex judgments. These include: directly stopping the AIoT service, suspending the AIoT service, or considering resource usage issues during the execution of the AIoT service. These possible basic operations are described below.

[0396] Figure 9 is a flowchart illustrating a communication method provided in an embodiment of this application. The first access network device is the source access network device to which the terminal accesses. The terminal can be understood as an intermediate node in the topology 2 architecture. The communication method shown in Figure 9 may include the following steps:

[0397] S901, when the terminal is performing AIoT services, the first access network device sends a first message to the terminal, instructing the terminal to access the second access network device. Correspondingly, the terminal receives the first message from the first access network device.

[0398] During the execution of AIoT services, the source access network device currently accessed by the terminal is the first access network device, and the second access network device indicated by the first message is the target access network device to which the terminal is to access.

[0399] S902, the terminal stops executing AIoT services.

[0400] In this step, the terminal can respond to receiving the first message by directly stopping the execution of the AIoT service. That is, the terminal stops reporting the data corresponding to the AIoT service to the access network device and stops transmitting the data and / or signaling corresponding to the AIoT service with the AIoT device.

[0401] It should be noted that stopping the AIoT service in this embodiment can be understood as terminating the AIoT service. If the terminal wants to resume the AIoT service later, it needs to start by configuring the AIoT service in the core network element and establishing a new AIoT service from the time the AIoT service request is initiated.

[0402] [Correction 22.04.2026 based on Rule 91] In some implementations, as shown in step S903 of Figure 9, the terminal may also release the configuration corresponding to the AIoT service and / or release the terminal's first context, which is used by the terminal to transmit AIoT services with the AIoT device.

[0403] Among them, the configuration corresponding to AIoT services includes, for example, the AIoT access stratum (AS) configuration. This AIoT AS configuration can be used to configure the terminal, and the terminal can perform AIoT services with AIoT devices according to the AIoT AS configuration.

[0404] Optionally, the AIoT AS configuration may include, for example, the configuration of AIoT radio resources, which are used for the terminal to communicate with the AIoT device, such as for the terminal to transmit one or more of the messages, data or signaling corresponding to the AIoT service to the AIoT device.

[0405] Optionally, in various embodiments of this application, the AIoT AS configuration can also be replaced with an AIoT wireless configuration or an AIoT wireless interface configuration, etc.

[0406] The first context is the context of the terminal. The first context can be used for communication between the terminal and the AIoT device, such as the first context and AIoT services. For example, the first context can be used for the terminal and the AIoT device to transmit one or more of the messages, data, or signaling corresponding to the AIoT service.

[0407] It is understood that the above-mentioned terminals transmit data and / or signaling corresponding to AIoT services with AIoT devices, and the AIoT devices are devices related to AIoT services. In this implementation, the terminal further releases (i.e. deletes) the configuration and / or first context corresponding to the AIoT services, which can save the terminal's storage space.

[0408] Optionally, the configuration corresponding to the above AIoT services may also include AIoT wireless resources for transmitting information corresponding to the AIoT services.

[0409] It should be noted that before receiving the first message, the terminal accesses the third cell, which is a cell controlled by the first access network. After receiving the first message, in response to receiving the first message, the terminal accesses the fourth cell, which is also a cell controlled by the first access network.

[0410] In this system, the third and fourth cells are different cells controlled by the first access network. In response to the first message, the terminal switches from the first access network device to the second access network device. To maintain communication continuity, the terminal can establish a new connection with the fourth cell and gradually disconnect from the third cell. During terminal movement, it can smoothly switch from cells controlled by the first access network to cells controlled by the second access network, thereby responding to the first message and accessing the second access network device.

[0411] Figure 10 is a flowchart illustrating a communication method provided in another embodiment of this application. Exemplarily, as shown in Figure 10, the communication method may include the following steps:

[0412] S1001, while the terminal is performing AIoT services, the first access network device sends a first message to the terminal, instructing the terminal to access or switch to the second access network device. Correspondingly, the terminal receives the first message from the first access network device.

[0413] S1002, the terminal suspends AIoT services.

[0414] In this step, the terminal can suspend the AIoT service in response to receiving the first message. It should be noted that, unlike stopping the execution of the AIoT service, suspending the AIoT service in this embodiment can be understood as terminating the AIoT service. If the terminal wants to resume the AIoT service later, it can restore the suspended AIoT service.

[0415] In some implementations, as shown in step S1003 of Figure 10, the terminal can also suspend the configuration corresponding to the AIoT service, and / or suspend the terminal's first context, which is used for the terminal to transmit AIoT services with the AIoT device.

[0416] In contrast to step S903 in the embodiment shown in Figure 9, if the terminal wants to re-execute the AIoT service when the configuration and / or first context corresponding to the suspended AIoT service are suspended, it can re-enable the configuration and / or the terminal's first context corresponding to the suspended AIoT service.

[0417] Optionally, the configuration corresponding to the above AIoT services may also include AIoT wireless resources for transmitting information of AIoT services.

[0418] As one possible implementation, before receiving the first message, the terminal accesses a third cell, which is a cell controlled by the first access network. After receiving the first message, in response to receiving the first message, the terminal accesses a fourth cell, which is also a cell controlled by the first access network.

[0419] The first access network device can also send a second message to the terminal on the fourth cell. The second message indicates any of the following: resuming the AIoT service, stopping the execution of the AIoT service, or indicating the configuration corresponding to the AIoT service. Accordingly, the terminal receives the second message from the fourth cell.

[0420] Understandably, after the terminal switches from the third cell to the fourth cell, it sends an RRC reconfiguration complete message to the first access network device. Subsequently, the first access network device sends a second message (RRC message) on the fourth cell. Since the terminal suspended the AIoT service in step S1002, the second message can instruct the terminal to resume the AIoT service, enabling the terminal to resume execution of the AIoT service after it was suspended.

[0421] Figure 11 is a flowchart illustrating a communication method provided in another embodiment of this application. Exemplarily, as shown in Figure 11, the communication method may include the following steps:

[0422] S1101, when the terminal is performing AIoT services, the first access network device sends a first message to the terminal, instructing the terminal to access or switch to the second access network device. Correspondingly, the terminal receives the first message from the first access network device.

[0423] It should be noted that before receiving the first message, the terminal accesses the third cell controlled by the first access network device.

[0424] S1102, the terminal responds to receiving the first message and accesses the fourth cell.

[0425] In this step, the terminal responds to receiving the first message and switches from the third cell to the fourth cell.

[0426] S1103, if the fourth cell is the third cell, the terminal continues to execute AIoT services.

[0427] It should be noted that after leaving the third cell, the terminal may return to the third cell during subsequent movement. During this movement, after leaving the third cell, in response to receiving the first message, the fourth cell the terminal accesses may be the same cell it accessed when returning to the third cell; that is, the fourth cell is the third cell. In this case, the terminal can continue to use the previous AIoT radio resources and continue performing AIoT services.

[0428] It is understandable that after the terminal accesses the fourth cell, it determines whether the fourth cell is the same as the third cell. If they are the same, the terminal executes step S1103. If they are different, the terminal executes the following step S1104.

[0429] S1104, If the fourth cell is different from the third cell, the terminal stops executing the AIoT service, or suspends the AIoT service.

[0430] In this step, the AIoT radio resources used by the terminal in the third cell may not be applicable to the fourth cell. Referring to the embodiments shown in Figures 9 and 10, the terminal may stop performing AIoT services or suspend AIoT services.

[0431] Figure 12 is a flowchart illustrating a communication method provided in another embodiment of this application. Exemplarily, as shown in Figure 12, the communication method may include the following steps:

[0432] S1201, while the terminal is performing AIoT services, the first access network device sends a first message to the terminal, instructing the terminal to access or switch to the second access network device. Correspondingly, the terminal receives the first message from the first access network device.

[0433] S1202, the terminal responds to receiving the first message and starts the first timer.

[0434] In this step, the terminal can maintain a first timer internally. In response to receiving the first message, the terminal starts the first timer and the first timer begins to count. The first timer in this step can also be understood as a first timer, which is used to measure the duration.

[0435] S1203, during the first timer operation, continues to execute AIoT services, or accesses the fourth cell.

[0436] In this step, during the first timer's execution, the terminal can continuously use AIoT wireless resources to continue performing AIoT services. Alternatively, during the timer's execution, the terminal can switch from the third cell it accessed before receiving the first message to the fourth cell.

[0437] In one possible implementation, after the terminal accesses the fourth cell, it can also send a third message to the first access network device on the fourth cell, indicating that the RRC reconfiguration is complete. Correspondingly, the first access network device receives the third message from the terminal on the fourth cell.

[0438] After the terminal sends the third message on the fourth cell, the terminal may stop the first timer, and / or the first access network device may send the first configuration information on the fourth cell. Accordingly, the terminal receives the first configuration information on the fourth cell and executes AIoT services according to the first configuration information.

[0439] In another possible implementation, the terminal can also stop executing the AIoT service or suspend the AIoT service when the first timer's duration reaches the second preset duration. It should be noted that the first timer reaching the second preset duration can also be understood as the first timer timing out.

[0440] It is understood that the first access network device and / or the second access network device in the embodiments of this application can be a gNB or an open RAN node. When the first access network device and / or the second access network device is a CU-DU separated architecture, the communication interaction between the terminal and the first access network device and / or the second access network device in the above embodiments can be understood as the terminal communicating with the O-DU in the first access network device and / or the O-DU in the second access network device. In the above embodiments, the communication interaction between the core network element and the first access network device and / or the second access network device can be understood as the core network element communicating with the O-CU in the first access network device and / or the O-CU in the second access network device.

[0441] It should be noted that when the access network equipment adopts a CU-DU separation architecture, the following F1AP impacts may occur:

[0442] When the access network device is a CU-DU separated access network device, after the CU receives the XXAP / NGAP message from the core network, it forwards the XXAP / NGAP message to the DU via an F1AP message, or sends the AIoT information contained in the CU-DU separated AP / NGAP message to the DU via an F1AP message. After the DU receives the RRC message from the UE, it forwards the RRC message to the CU via an F1AP message, or sends the AIoT information contained in the RRC message to the CU via an F1AP message.

[0443] In this scheme, the XXAP / NGAP messages transmitted on the F1 interface F1AP and the xxAP / NGAP messages transmitted on the XX / NG interface XXAP / NGAP can be different. That is, the CU can perform relevant processing on the messages, which can include deletion, filtering, mapping, modification, and adding auxiliary information.

[0444] It should be noted that, in this application embodiment, the topology 2 architecture is used as an example. In the above topology 3 and topology 4 architectures, when the terminal is used as the read and write device for AIoT services, the communication method provided in this application embodiment can also be applied.

[0445] Figures 13 and 14 are schematic diagrams of possible communication devices provided in embodiments of this application. These communication devices can be used to implement the functions of terminals, access network devices, or core network elements in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments. In the embodiments of this application, the communication device can be a terminal or access network device in the above method embodiments, or it can be a component configured in the terminal or access network device (such as a chip, chip system, processor, etc.), or it can be a logic module or software capable of implementing some or all of the functions of the terminal or access network device.

[0446] Figure 13 is a schematic diagram of the structure of a communication device provided in an embodiment of this application. As shown in Figure 13, the communication device 1300 includes a processing module 1310 and a transceiver module 1320.

[0447] The transceiver module 1320 can implement corresponding communication functions and can also be referred to as an input / output interface or communication unit. The processing module 1310 can be used to perform processing operations. It should be understood that if the device 1300 is a component configured in an access network device or terminal, such as a chip, the transceiver module 1320 can be an input / output interface.

[0448] Optionally, the transceiver module 1320 may include a transmitting module and a receiving module. The transmitting module is used to perform the transmitting operation of the access network device or terminal, and the receiving module is used to perform the receiving operation of the access network device or terminal.

[0449] It should be understood that when the device 1300 is a component configured in an access network device or terminal, such as a chip, the transmitting module can be an output interface, and the transmitting operation involved in the embodiments of this application can be performed by the output interface; the receiving module can be an input interface, and the receiving operation involved in the embodiments of this application can be performed by the input interface.

[0450] Optionally, the device 1300 may further include a storage module for storing instructions and / or data, and the processing module 1310 may read the instructions and / or data from the storage module to enable the device to implement the method embodiments shown above.

[0451] In one possible design, the device 1300 can be used to implement the functions of the terminal in the method embodiments shown above. Alternatively, the device 1300 can include a unit for implementing any function or operation of the terminal in the method embodiments shown above. This unit can be implemented entirely or partially by software, hardware, firmware, or any combination thereof.

[0452] When device 1300 is used to implement the terminal function in the method embodiment shown above, transceiver module 1320 (specifically, a receiving module) can be used to execute step S504 in FIG5, receiving a first message from the access network device, the first message instructing the terminal device to switch to the second access network device, and can also be used to execute step S708 in FIG7, receiving second information from the second access network device, the second information indicating whether to continue executing AIoT service; processing module 1310 can be used to execute step S507 in FIG5, the terminal determining whether to continue executing AIoT service based on the first location and the first area; transceiver module 1320 (specifically, a sending module) can also be used to execute step S706 in FIG7, sending an RRC reconfiguration completion message to the second access network device.

[0453] In another possible design, the device 1300 can be used to implement the functions of the access network device in the method embodiments shown above. Alternatively, the device 1300 can include a unit for implementing any function or operation of the access network device in the method embodiments shown above. This unit can be implemented entirely or partially by software, hardware, firmware, or any combination thereof.

[0454] When device 1300 is used to implement the function of the second access network device in the method embodiment shown above, transceiver module 1320 (specifically, a sending module) can be used to execute step S708 in FIG7 to send second information to the terminal, the second information indicating whether to continue to execute AIoT service; processing module 1310 can be used to execute step S707 in FIG7 to determine whether the terminal should continue to execute AIoT service based on the first location and the first area; transceiver module 1320 (specifically, a receiving module) can be used to execute step S706 in FIG7 to receive the RRC reconfiguration completion message from the terminal.

[0455] A more detailed description of the above-mentioned processing module 1310 and transceiver module 1320 can be obtained directly from the relevant descriptions in the above-described method embodiments, and will not be repeated here.

[0456] It should be noted that the transceiver module can also be called a transceiver unit, transceiver, transceiver machine, or transceiver device, etc. The processing module can also be called a processor, processing board, processing unit, or processing device, etc. Optionally, the transceiver module is used to perform the sending and receiving operations on the terminal or access network device side in the above method. The device in the communication module used to implement the receiving function can be considered as the receiving module, and the device in the communication module used to implement the sending function can be considered as the sending module; that is, the transceiver module includes both a receiving module and a sending module.

[0457] In another possible design, the aforementioned transceiver module and / or processing module can be implemented using virtual modules. For example, the processing module can be implemented using software functional modules or virtual devices, and the transceiver module can also be implemented using software functional modules or virtual devices. In another possible design, the processing module or transceiver module can also be implemented using physical devices. For example, if the device is implemented using a chip / chip circuit, the transceiver module can be an input / output circuit and / or a communication interface, performing input operations (corresponding to the aforementioned receiving operation) and output operations (corresponding to the aforementioned sending operation); the processing module is an integrated processor, microprocessor, or integrated circuit.

[0458] It should be understood that the module division in the embodiments of this application is illustrative and only represents a logical functional division. In actual implementation, there may be other division methods. Furthermore, the functional modules in the various embodiments of this application can be integrated into a single processor, exist as separate physical entities, or be integrated into a single module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0459] Figure 14 is a schematic diagram of a communication device provided in another embodiment of this application. This device 1400 can be a chip system, or it can be a device configured with a chip system to implement the above-described method embodiments. In this embodiment, the chip system can be composed of chips, or it can include chips and other discrete devices.

[0460] As shown in Figure 14, device 1400 can be implemented using a processing system including one or more processors 1401. Processor 1401 includes a microprocessor, microcontroller, digital signal processor, field-programmable gate array, graphics processor, programmable logic device, state machine, gated logic, discrete hardware circuitry, and other suitable hardware configured to perform various functions. That is, the processor used in device 1400 can be used to implement any one or more of the embodiments described above.

[0461] The processing system in device 1400 can be implemented using a bus architecture, typically represented by bus 1402. Bus 1402 may include any number of interconnect buses and bridges, depending on the specific application and overall design constraints of the processing system. The bus communicatively couples various circuits together, including one or more processors 1401 (typically represented by a processor), memory 1403, and computer-readable medium 1404 (typically represented by a computer-readable medium). Bus 1402 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further. Bus interface 1405 provides an interface between bus 1402 and transceivers, and between bus 1402 and interfaces. Bus interface 1405 may use, but is not limited to, transceivers to enable communication between device 1400 and other devices or apparatuses.

[0462] A transceiver provides a communication interface or means for communicating with various other devices via a wireless transmission medium. The transceiver may be coupled to an antenna array, and the transceiver and antenna array may be used together for communication with a corresponding network type. At least one interface (e.g., a network interface and / or a user interface) provides a communication interface or means for communication via an internal bus or via an external transmission medium.

[0463] Processor 1401 is responsible for managing bus 1402 and general processing, including executing software stored on computer-readable medium 1404. When executed by processor 1401, the software causes the processing system to perform the various functions described below for any particular device.

[0464] The processor 1401, memory 1403, and computer-readable medium 1404 can perform the following functions: encoding, decoding, rate matching, rate matching removal, scrambling, descrambling, modulation, demodulation, layer mapping, fast Fourier transform, inverse fast Fourier transform, inverse discrete Fourier transform, precoding, resource element (RE) mapping, channel equalization, RE demapping, digital beamforming (BF), adding cyclic prefix (CP), removing CP, etc.

[0465] The steps of the method disclosed in the embodiments of this application can be directly manifested as being executed by a hardware decoding processor, or being executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art.

[0466] This application also provides a computer-readable storage medium storing computer instructions, which, when executed by a processor, implement the steps of the methods described above.

[0467] This application also provides a computer program product, including computer instructions that, when executed by a processor, implement the various steps in the methods described above.

[0468] It should be noted that the modules or components shown in the above embodiments can be one or more integrated circuits configured to implement the above methods, such as one or more application-specific integrated circuits (ASICs), one or more microprocessors, or one or more field-programmable gate arrays (FPGAs). Furthermore, when a module is implemented by a processing element calling program code, the processing element can be a general-purpose processor, such as a central processing unit (CPU) or other processor capable of calling program code, such as a controller. Moreover, these modules can be integrated together to implement a system-on-a-chip (SoC).

[0469] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, software modules, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) 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 (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., a solid-state disk (SSD)).

[0470] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the disclosure herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and intent of this application are indicated by the following claims.

[0471] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A communication method, characterized in that, The method is applied to a second access network device or a chip in the second access network device. When a terminal switches to the second access network device while performing AIoT services in an environment, the method includes: Obtain first information, wherein the first information indicates the first location of the terminal; Obtain a first region, where the first region indicates the region corresponding to the AIoT service; Based on the first location and the first region, determine whether the terminal should continue to execute the AIoT service; Send a second message, which indicates whether the terminal should continue to execute the AIoT service.

2. The method according to claim 1, characterized in that, After determining that the terminal will continue to execute the AIoT service, the method further includes: Obtain third information, which indicates the second location of the terminal; Based on the second location and the first region, determine whether the terminal should continue to execute the AIoT service; A fourth message is sent, indicating whether the terminal should continue to execute the AIoT service.

3. The method according to claim 1, characterized in that, After determining that the terminal will no longer execute the AIoT service, the method further includes: Obtain fifth information, which indicates the third location of the terminal; Based on the third location and the first region, determine whether the terminal should continue to execute the AIoT service; A sixth message is sent, which indicates whether the terminal should continue to execute the AIoT service.

4. The method according to claim 1, characterized in that, The step of determining whether the terminal should continue to execute the AIoT service based on the first location and the first region includes: If the first location is within the first area, it is determined that the terminal will continue to execute the AIoT service; or, If the first location is not located in the first area, it is determined that the terminal will not continue to execute the AIoT service.

5. The method according to claim 1, characterized in that, The step of determining whether the terminal should continue to execute the AIoT service based on the first location and the first region includes: If the first location is within the first area and the second access network supports AIoT capabilities, it is determined that the terminal will continue to execute the AIoT service; or, The first location is within the first region, and the second access network does not support AIoT capabilities, therefore it is determined that the terminal will not continue to execute the AIoT service.

6. The method according to claim 1, characterized in that, The second access network supports AIoT capabilities. After determining that the terminal will continue to execute the AIoT service, the method further includes: Send first resource information, the first resource information indicating a first resource, the first resource being used by the terminal to communicate with the AIoT device; and / or, Send radio bearer (RB) configuration information, which is used to indicate a first RB, which is dedicated to transmitting AIoT service-related data and / or signaling.

7. The method according to claim 6, characterized in that, The first resource is the AIoT wireless resource used by the terminal and the AIoT device to communicate in a first cell, where the first cell is the cell the terminal currently accesses after switching to the second access network device; or, The first resource is the AIoT wireless resource used by the terminal and the AIoT device to communicate in a second cell, where the second cell includes multiple cells controlled by the second access network device; or, The first resource is the AIoT wireless resource used by the terminal to communicate with the AIoT device during cell handover or access network device handover.

8. The method according to any one of claims 1 to 7, characterized in that, Whether the terminal continues to execute the AIoT service includes: Whether the terminal reports the data corresponding to the AIoT service, and / or whether the terminal transmits the data and / or signaling corresponding to the AIoT service to the AIoT device.

9. A communication method, characterized in that, The method is applied to core network elements, and the terminal switches to a second access network device while performing AIoT services. The method includes: Receive a request message, which requests whether to continue executing the AIoT service; Obtain first information, wherein the first information indicates the first location of the terminal; Obtain a first region, where the first region indicates the region corresponding to the AIoT service; Based on the first location and the first region, determine whether the terminal should continue to execute the AIoT service; Send a second message, which indicates whether the terminal should continue to execute the AIoT service.

10. The method according to claim 9, characterized in that, After determining that the terminal will continue to execute the AIoT service, the method further includes: Obtain third information, which indicates the second location of the terminal; Based on the second location and the first region, determine whether the terminal should continue to execute the AIoT service; A seventh message is sent, which indicates whether the terminal should continue to execute the AIoT service.

11. The method according to claim 9, characterized in that, After determining that the terminal will no longer execute the AIoT service, the method further includes: Obtain fifth information, which indicates the third location of the terminal; Based on the third location and the first region, determine whether the terminal should continue to execute the AIoT service; Send an eighth message, which indicates whether the terminal should continue to execute the AIoT service.

12. The method according to claim 9, characterized in that, The step of determining whether the terminal should continue to execute the AIoT service based on the first location and the first region includes: The first location is within the first area, indicating that the terminal continues to execute the AIoT service; or If the first location is not located in the first area, it is determined that the terminal will not continue to execute the AIoT service.

13. The method according to claim 9, characterized in that, The method further includes: Obtain first capability information, which indicates whether the second access network device supports AIoT capabilities; The step of determining whether the terminal should continue to execute the AIoT service based on the first location and the first region includes: If the first location is within the first area and the second access network supports AIoT capabilities, it is determined that the terminal will continue to execute the AIoT service; or, The first location is within the first region, and the second access network does not support AIoT capabilities, therefore it is determined that the terminal will not continue to execute the AIoT service.

14. The method according to any one of claims 9 to 13, characterized in that, The method further includes: Send third resource information, which indicates a third resource, which is the AIoT wireless resource used by the terminal to communicate with the AIoT device during cell handover or access network device handover.

15. A communication method, characterized in that, The method is applied to a terminal or a chip in a terminal, the terminal being connected to a first access network device, and the method includes: In executing AIoT services, receive the first message; In response to receiving the first message, the terminal accesses the second access network device; Obtain the ninth piece of information, and determine whether to execute the AIoT service based on the ninth piece of information.

16. The method according to claim 15, characterized in that, The ninth piece of information indicates whether the terminal should continue to perform AIoT services.

17. The method according to claim 15, characterized in that, The ninth information includes first information and a first region, wherein the first information indicates the first location of the terminal and the first region indicates the region corresponding to the AIoT service; The step of determining whether to execute the AIoT service based on the ninth information includes: Based on the first location and the first region, determine whether to continue executing the AIoT service.

18. The method according to any one of claims 15 to 17, characterized in that, After determining to continue executing the AIoT service, the method further includes: Obtain third information, wherein the second information indicates the second location of the terminal; Based on the second location and the first region, determine whether to continue executing the AIoT service.

19. The method according to any one of claims 15 to 17, characterized in that, After determining that the AIoT service will not continue to be executed, the method further includes: Obtain fifth information, which indicates the third location of the terminal; Based on the third location and the first region, determine whether to continue executing the AIoT service.

20. The method according to claim 17, characterized in that, The step of determining whether to continue executing the AIoT service based on the first location and the first region includes: If the first location is within the first region, it is determined that the AIoT service will continue to be executed; or, If the first location is not located in the first region, it is determined that the AIoT service will not continue to be executed.

21. The method according to claim 17, characterized in that, The method further includes: Obtain first capability information, which indicates whether the second access network device supports AIoT capabilities; The step of determining whether to continue executing the AIoT service based on the first location and the first region includes: If the first location is within the first area and the second access network device supports AIoT capabilities, then it is determined to continue executing the AIoT service; or, The first location is within the first region, and the second access network device does not support AIoT capabilities, therefore it is determined not to continue executing the AIoT service.

22. The method according to claim 17, characterized in that, After determining that the AIoT service will not continue to be executed, the method further includes: Release the tenth information, which includes data and / or signaling corresponding to the AIoT service stored before the terminal accesses the second access network device; or... The tenth information is retained until the terminal accesses the third access network device.

23. The method according to claim 22, characterized in that, The release of the tenth information includes: If the retention time of the tenth information reaches the first preset time, the tenth information is released.

24. The method according to any one of claims 15 to 17, characterized in that, The second access network device supports AIoT capabilities. After determining to continue executing the AIoT service, the method further includes: Receive first resource information, the first resource information indicating a first resource, the first resource being used by the terminal to communicate with the AIoT device; and / or, Receive RB configuration information, which is used to indicate a first RB, which is dedicated to transmitting AIoT service-related data and / or signaling.

25. The method according to claim 24, characterized in that, The first resource is the AIoT wireless resource used by the terminal and the AIoT device to communicate in a first cell, where the first cell is the cell where the terminal is located after accessing the second access network device; or... The first resource is the AIoT wireless resource used by the terminal and the AIoT device to communicate in a second cell, where the second cell includes multiple cells controlled by the second access network device; or, The first resource is the AIoT wireless resource used by the terminal to communicate with the AIoT device during cell handover or access network device handover.

26. The method according to any one of claims 15 to 23, characterized in that, The method further includes: The terminal receives second resource information, which indicates a second resource. The second resource is the AIoT wireless resource used by the terminal to communicate with the AIoT device during cell handover or access network device handover. The second resource information comes from the first access network device.

27. The method according to any one of claims 15 to 23, characterized in that, The method further includes: The terminal receives third resource information, which indicates a third resource. The third resource is the AIoT wireless resource used by the terminal to communicate with the AIoT device during cell handover or access network device handover. The third resource information comes from the core network element.

28. A communication method, characterized in that, The method is applied to a terminal or a chip in a terminal, the terminal being connected to a first access network device, and the method includes: In executing AIoT services, a first message is received, which instructs the terminal to access or switch to a second access network device. Stop executing the aforementioned AIoT service.

29. The method according to claim 28, characterized in that, The method further includes: Release the configuration corresponding to the AIoT service, and / or release the first context of the terminal, which is used by the terminal to transmit the AIoT service with the AIoT device.

30. The method according to claim 29, characterized in that, The configuration corresponding to the AIoT service includes AIoT wireless resources used to transmit information of the AIoT service.

31. The method according to any one of claims 28 to 30, characterized in that, The terminal accesses the first access network device, including: The terminal accesses a third cell, which is a cell controlled by the first access network device; The method further includes: In response to receiving the first message, the terminal accesses the fourth cell, which is the cell controlled by the first access network device.

32. A communication method, characterized in that, The method is applied to a terminal or a chip in a terminal, the terminal being connected to a first access network device, and the method includes: In executing AIoT services, a first message is received, which instructs the terminal to access or switch to a second access network device. Suspend the aforementioned AIoT service.

33. The method according to claim 32, characterized in that, The method further includes: The configuration corresponding to the AIoT service is suspended, and / or the first context of the terminal is suspended, the first context being used by the terminal to transmit the AIoT service with the AIoT device.

34. The method according to claim 33, characterized in that, The configuration corresponding to the AIoT service includes AIoT wireless resources used to transmit information corresponding to the AIoT service.

35. [Correction 22.04.2026 according to Rule 91] The method according to any one of claims 32 to 33, characterized in that, The terminal accesses the first access network device, including: The terminal accesses a third cell, which is a cell controlled by the first access network device; The method further includes: In response to receiving the first message, the terminal accesses the fourth cell, which is the cell controlled by the first access network device; Receive a second message from the fourth cell, the second message indicating any one of the following: resume the AIoT service, stop the execution of the AIoT service, or indicate the configuration corresponding to the AIoT service.

36. A communication method, characterized in that, The method is applied to a terminal or a chip in a terminal, the terminal accessing a third cell controlled by a first access network device, the method comprising: In executing AIoT services, receive the first message; In response to receiving the first message, access is made to the fourth cell; If the fourth cell is the third cell, the AIoT service will continue to be executed.

37. The method according to claim 36, characterized in that, The method further includes: If the fourth cell is different from the third cell, the AIoT service is stopped or suspended.

38. A communication method, characterized in that, The method is applied to a terminal or a chip in a terminal, the terminal accessing a third cell controlled by a first access network device, the method comprising: In executing AIoT services, a first message is received, which instructs the terminal to access or switch to a second access network device. In response to receiving the first message, start the first timer; During the operation of the first timer, the AIoT service continues to be executed, or the fourth cell is accessed.

39. The method according to claim 38, characterized in that, After accessing the fourth cell, the method further includes: The third message is sent in the fourth cell, indicating that the RRC reconfiguration is complete; After sending the third message, stop the timer; and / or, After sending the third message, the fourth cell receives the first configuration information and executes the AIoT service according to the first configuration information.

40. The method according to claim 38, characterized in that, The method further includes: If the duration of the first timer reaches the second preset duration, the AIoT service will be stopped or suspended.

41. A communication device, characterized in that, The communication device includes a module for implementing the communication method as described in any one of claims 1 to 40.

42. A communication device, characterized in that, include: Processor, the processor being coupled to memory; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the communication device to perform the communication method as described in any one of claims 1 to 40.

43. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or instructions that, when executed by a processor, implement the method as described in any one of claims 1 to 40.

44. A computer program product, characterized in that, It includes a computer program or instructions that, when executed, implement the method as described in any one of claims 1 to 40.

Images