COMMUNICATION METHOD APPLIED TO INTEGRATED ACCESS AND BACKHAUL IAB SYSTEM AND COMMUNICATION APPARATUS

Abstract

A communication method applied to an integrated access and backhaul (IAB) system includes: a child node receives a first radio resource control (RRC) reconfiguration message from an access network device via a parent node, where the first RRC reconfiguration message includes a random access-free indication. The child node starts a timer. The child node sends a first RRC reconfiguration complete message to the access network device via the parent node. The child node receives first indication information from the parent node, where the first indication information indicates to stop the timer. The child node stops the timer.

Claims

1. A communication apparatus in an integrated access and backhaul (IAB) system, comprising: at least one processor; and a memory coupled to the at least one processor and configured to store executable instructions for execution by the at least one processor to instruct the at least one processor to: receive a first radio resource control (RRC) reconfiguration message from an access network device via a parent node, wherein the first RRC reconfiguration message comprises a random access-free indication; start a timer; send a first RRC reconfiguration complete message to the access network device via the parent node; receive first indication information from the parent node, wherein the first indication information indicates to stop the timer; and stop the timer.

2. The communication apparatus according to claim 1, wherein the first indication information is a first-type media access control control element (MAC CE), or the first indication information is a MAC CE carrying a contention resolution identity.

3. The communication apparatus according to claim 1, wherein the first RRC reconfiguration message does not comprise a cell radio network temporary identifier of the apparatus; the first RRC reconfiguration message comprises second indication information indicating that a cell radio network temporary identifier of the apparatus remains unchanged; or the first RRC reconfiguration message comprises a cell radio network temporary identifier used before receiving the first RRC reconfiguration message.

4. The communication apparatus according to claim 1, wherein the apparatus is a terminal or an IAB node, and the parent node is an IAB node.

5. A communication apparatus in an integrated access and backhaul (IAB) system, comprising: at least one processor; and a memory coupled to the at least one processor and configured to store executable instructions for execution by the at least one processor to instruct the at least one processor to: receive a first radio resource control (RRC) reconfiguration message from an access network device, wherein the first RRC reconfiguration message comprises a random access-free indication; send the first RRC reconfiguration message to a child node, to trigger the child node to start a timer; receive a first RRC reconfiguration complete message from the child node; send the first RRC reconfiguration complete message to the access network device; and send first indication information to the child node, wherein the first indication information indicates to stop the timer.

6. The communication apparatus according to claim 5, wherein the executable instructions further instruct the at least one processor to: receive second indication information from the access network device; and send the first indication information to the child node in response to the second indication information.

7. The communication apparatus according to claim 6, wherein the second indication information comprises an identifier of the child node.

8. The communication apparatus according to claim 5, wherein the first indication information is a first-type media access control control element (MAC CE), or the first indication information is a MAC CE carrying a contention resolution identity.

9. The communication apparatus according to claim 5 wherein the first RRC reconfiguration message does not comprise a cell radio network temporary identifier of the child node; the first RRC reconfiguration message comprises third indication information indicating that a cell radio network temporary identifier of the child node remains unchanged; or the first RRC reconfiguration message comprises a cell radio network temporary identifier that is of the child node and that is used before sending the first RRC reconfiguration message to the child node.

10. The communication apparatus according to claim 5, wherein the access network device is a target access network device of the child node in a group handover process.

11. The communication apparatus according to claim 10, wherein the executable instructions further instruct the at least one processor to: after receiving the first RRC reconfiguration message from the access network device or sends the first RRC reconfiguration message to the child node, receive a second RRC reconfiguration message from the access network device, and start a timer.

12. The communication apparatus according to claim 11, wherein the executable instructions further instruct the at least one processor to: after receiving the first RRC reconfiguration message from the access network device or sending the first RRC reconfiguration message to the child node, send fourth indication information to a source access network device, so as to trigger the source access network device to send the second RRC reconfiguration message, wherein the source access network device is a source access network device of the child node and the apparatus in the group handover process.

13. The communication apparatus according to claim 5, wherein the child node is a terminal or an IAB node, and the apparatus is an IAB node.

14. A communication apparatus in an integrated access and backhaul (IAB) system, comprising: at least one processor; and a memory coupled to the at least one processor and configured to store executable instructions for execution by the at least one processor to instruct the at least one processor to: send a first radio resource control (RRC) reconfiguration message to a child node via a parent node, so as to trigger the child node to start a timer, wherein the first RRC reconfiguration message comprises a random access-free indication; receive a first RRC reconfiguration complete message from the child node via the parent node; and send second indication information to the parent node, so as to trigger the parent node to send first indication information to the child node, wherein the first indication information indicates to stop the timer.

15. The communication apparatus according to claim 14, wherein the second indication information comprises an identifier of the child node.

16. The communication apparatus according to claim 14, wherein the first indication information is a first-type media access control control element (MAC CE), or the first indication information is a MAC CE carrying a contention resolution identity.

17. The communication apparatus according to claim 14, wherein the first RRC reconfiguration message does not comprise a cell radio network temporary identifier of the child node; the first RRC reconfiguration message comprises third indication information indicating that a cell radio network temporary identifier of the child node remains unchanged; or the first RRC reconfiguration message comprises a cell radio network temporary identifier that is of the child node and that is used before sending the first RRC reconfiguration message to the child node via the parent node.

18. The communication apparatus according to claim 14, wherein the apparatus is a target access network device of the child node in a group handover process.

19. The communication apparatus according to claim 18, wherein the executable instructions further instruct the at least one processor to: receive a handover request message from a source access network device, wherein the handover request message comprises one or more of the following: the cell radio network temporary identifier of the child node before handover, an identifier of a cell accessed by the child node before handover, or hierarchical information of the child node in a network topology, and the source access network device is a source access network device of the child node and the parent node in the group handover process.

20. The communication apparatus according to claim 18, wherein the executable instructions further instruct the at least one processor to: determine duration of the timer based on the hierarchical information, wherein the first RRC reconfiguration message comprises information about the duration of the timer.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0114] To describe the embodiments or the background more clearly, the following briefly describes the accompanying drawings.

[0115] FIG. 1 is a schematic diagram of a mobile communication system 100 according to an embodiment;

[0116] FIG. 2 is a schematic diagram of a CU-DU separation architecture according to an embodiment;

[0117] FIG. 3 is a schematic diagram of an integrated access and backhaul (IAB) network according to an embodiment;

[0118] FIG. 4A is a schematic diagram of a control plane protocol stack in a single air interface scenario according to an embodiment;

[0119] FIG. 4B is a schematic diagram of a user plane protocol stack in a single air interface scenario according to an embodiment;

[0120] FIG. 5A is a schematic diagram of a control plane protocol stack in an IAB network according to an embodiment;

[0121] FIG. 5B is a schematic diagram of a user plane protocol stack in an IAB network according to an embodiment;

[0122] FIG. 6 is a schematic diagram of group handover according to an embodiment;

[0123] FIG. 7 shows a communication method according to an embodiment;

[0124] FIG. 8A, FIG. 8B, and FIG. 8C show a group handover method according to an embodiment;

[0125] FIG. 9 shows another communication method according to an embodiment;

[0126] FIG. 10 is a schematic diagram of a structure of a terminal according to an embodiment;

[0127] FIG. 11 is a schematic diagram of a structure of an access network device according to an embodiment;

[0128] FIG. 12 is a schematic diagram of a structure of a communication apparatus according to an embodiment; and

[0129] FIG. 13 is a schematic diagram of a structure of a communication apparatus according to an embodiment.

DETAILED DESCRIPTION OF THE EMBODIMENTS

[0130] The following describes the embodiments with reference to the accompanying drawings.

[0131] FIG. 1 is a schematic diagram of an architecture of a communication system 100 according to an embodiment. The communication system 100 includes at least one terminal (for example, a terminal 110, a terminal 120, and a terminal 130), at least one relay node (RN) 140, at least one access network device 150, and at least one core network device 160.

[0132] The terminal may be connected to the at least one access network device, or the terminal may be connected to the at least one access network device via the at least one relay node, where the at least one access network device is connected to the at least one core network device. As shown in FIG. 1, both the terminal 110 and the terminal 120 are connected to the relay node 140, the relay node 140 is connected to the access network device 150, and the terminal 130 is connected to the access network device 150. The access network device 150 is connected to the core network device 160. The terminal 110, the terminal 120, the terminal 130, the relay node 140, the access network device 150, and the core network device 160 may be connected in a wireless or wired manner. This is not limited.

[0133] The communication system may be, for example, a long term evolution (LTE) system supporting a 4G access technology, a new radio (NR) system supporting a 5G access technology, any cellular system related to the 3rd generation partnership project (3GPP), a wireless fidelity (Wi-Fi) system, a worldwide interoperability for microwave access (WiMAX) system, a multiple radio access technology (RAT) system, or another future-oriented communication technology. A terminal may be a device having a wireless transceiver function, and the terminal may be deployed on the land, including an indoor or outdoor device, a hand-held device, or a vehicle-mounted device, or may be deployed on the water (for example, on a ship), or may be deployed in the air (for example, on a plane, a balloon, or a satellite). The terminal may be a mobile phone, a tablet computer (Pad), a computer with a wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in remote medical, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, or the like. An application scenario is not limited in the embodiments. Sometimes, the terminal may also be referred to as a terminal device, user equipment (UE), an access terminal device, a station, a UE unit, a UE station, a mobile station, a remote station, a remote terminal device, a mobile device, a UE terminal device, a terminal device, a wireless communication device, a UE agent, a UE apparatus, or another suitable term. The terminal may be fixed or mobile.

[0134] An access network device may be a device configured to support a terminal in accessing a communication system on an access network side. The access network device may be referred to as a base station (BS), for example, an evolved NodeB (eNB) in a 4G access technology communication system, a next generation NodeB (gNB) in a 5G access technology communication system, a transmission reception point (TRP), a relay node, an access point (AP), an access node in a Wi-Fi system, or a wireless backhaul node. Alternatively, the access network device may be referred to as a donor node, an IAB donor, a donor IAB, a donor, a donor gNB (DgNB), or the like. The base station may be a macro base station, a micro base station, a picocell base station, a small cell, a relay station, or the like. A plurality of base stations may support the foregoing networks using a same technology or may support the foregoing networks using different technologies. The base station may include one or more co-site or non-co-site transmission/reception points (TRPs). The access network device may alternatively be a radio controller, a central unit (CU), and/or a distributed unit (DU) in a cloud radio access network (CRAN) scenario. The access network device may alternatively be a server, a wearable device, a vehicle-mounted device, or the like. The following uses an example in which the access network device is a base station for description. A plurality of access network devices in the communication system may be base stations of a same type or may be base stations of different types. The base station may communicate with the terminal or may communicate with the terminal device via a relay station. The terminal may communicate with a plurality of base stations using different technologies. For example, the terminal device may communicate with a base station supporting an LTE network, may communicate with a base station supporting a 5G network, or may support dual connectivity to a base station in an LTE network and a base station in a 5G network.

[0135] A core network device may be connected to one or more access network devices, and may provide one or more functions of session management, access authentication, internet protocol (IP) address allocation, and data transmission for a terminal in a system. For example, the core network device may be a mobility management entity (MME) or a serving gateway (SGW) in a 4G access technology communication system, or an access and mobility management function (AMF) network element or a user plane function (UPF) network element in a 5G access technology communication system. The core network device may also be referred to as a core network element.

[0136] A relay node may be a node that provides a wireless access service and/or a wireless backhaul service. The wireless access service means providing data and/or signaling through a wireless access link, and the wireless backhaul service refers to a data and/or signaling backhaul service provided through a wireless backhaul link. The relay node is configured to forward data and/or signaling between a terminal and an access network device. The relay node provides the wireless access service for the terminal through an access link (AL). In addition, the relay node is connected to the access network device through a one-hop or multi-hop backhaul link (BL).

[0137] The relay node may have different names in different communication systems. For example, the relay node may be referred to as a wireless backhaul node or a wireless backhaul device. For example, in a 5G system, the relay node may be referred to as an integrated access and backhaul (IAB) node. Further, in a future communication system, the relay node may further have different names. This is not limited herein.

[0138] Optionally, the relay node may alternatively be a terminal device. Alternatively, the relay node may also be a CPE in a home access scenario. For example, the IAB node may be a device such as customer premises equipment (CPE) or a residential gateway (RG). In this case, the method provided in the embodiments may further be applied to a home access scenario.

[0139] FIG. 2 is a schematic diagram of a CU-DU separation architecture according to an embodiment. The access network device 150 in FIG. 1 may use the CU-DU separation architecture. In FIG. 2, an example in which the access network device is a next-generation NodeB (gNB) is used for description.

[0140] The gNB may be implemented in a cloud radio access network (C-RAN) architecture. Some functions of the gNB are implemented by a central unit (CU), and the other functions are implemented by a distributed unit (DU). CU-DU division may be performed by protocol stacks. In a possible manner, a radio resource control (RRC) layer, a service data mapping protocol stack (SDAP) layer, and a packet data convergence protocol (PDCP) layer are deployed in the CU, and a radio link control (RLC) layer, a media access control (MAC) layer, and a physical (PHY) layer are deployed in the DU.

[0141] One CU may be connected to one or more DUs, to facilitate network extension. The CU and the DU are connected through an interface (for example, an F1 interface), and the CU and a core network (for example, a 5G core network (5GC)) are connected through an interface (for example, an NG interface).

[0142] In an implementation, the CU includes a user plane (UP for short) (CU-UP for short) and a control plane (CP for short) (CU-CP for short).

[0143] FIG. 3 is a schematic diagram of an integrated access and backhaul (IAB) network according to an embodiment. FIG. 3 is an application scenario of the communication system 100 shown in FIG. 1. With reference to FIG. 3, the following further describes the terminal, the relay node, and the access network device in FIG. 1.

[0144] The IAB network includes one or more terminals (for clarity, FIG. 3 shows only a terminal 1), one or more IAB nodes (for clarity, FIG. 3 shows two IAB nodes: an IAB node 1 and an IAB node 2), and one or more donor nodes (for clarity, FIG. 3 shows only an IAB donor 1).

[0145] The terminal 1 may be connected to the one or more IAB nodes, each IAB node may be connected to one or more other IAB nodes, and the one or more IAB nodes may be connected to the one or more donor nodes. Optionally, the one or more IAB nodes may be alternatively connected to each other. This is not limited in the embodiments.

[0146] An IAB donor may be referred to as a donor node, a donor gNodeB (DgNB), or another proper name. This is not limited in the embodiments.

[0147] In FIG. 3, the terminal 1 may be the terminal 110 in FIG. 1. The IAB node 1 and the IAB node 2 may be the relay node 140 in FIG. 1. The IAB donor 1 may be the access network device 150 in FIG. 1. A 5G core network (5GC) and an evolved packet core network (EPC) may be core networks including at least one core network device shown in FIG. 1.

[0148] The IAB donor 1 in FIG. 3 may be the gNB in FIG. 2, and the IAB donor 1 may use the CU-DU separation architecture in FIG. 2. The IAB donor 1 may include a central unit (which may be referred to as an IAB donor CU 1) and a distributed unit (which may be referred to as an IAB donor DU 1), and the IAB donor CU 1 may include a CP (which may be referred to as an IAB donor CU 1-CP) and a UP (which may be referred to as an IAB donor CU 1-UP). For details, refer to content in FIG. 2.

[0149] The IAB network supports a networking mode of standalone (SA) or non-standalone (NSA).

[0150] For example, in the SA networking mode in FIG. 3, the IAB donor 1 may be connected to the 5GC. The IAB donor CU 1-CP may be connected to a control plane network element in the 5GC, for example, an access and mobility management function (AMF), and the IAB donor CU 1-UP may be connected to a user plane network element in the 5GC, for example, a user plane function (UPF).

[0151] For example, in the NSA networking mode in FIG. 3, the IAB donor 1 serves as a secondary gNB (SgNB), and establishes dual connectivity to a master eNB (MeNB). Both the IAB node 1 and the IAB node 2 are connected to the MeNB, the IAB donor CU 1-CP is connected to the MeNB, the MeNB is connected to the EPC, and the IAB donor CU 1-UP is connected to a network element in the EPC, for example, a service gateway (SGW).

[0152] It may be understood that, in the IAB network, one transmission path between the terminal and the donor node may include one or more IAB nodes. If one IAB node is a node accessed by the terminal, a link between the IAB node and a child node (namely, the terminal) may be referred to as an access link. If one IAB node is a node that provides a backhaul service for a terminal accessing another IAB node, a link between the IAB node and a child node (namely, the another IAB node) may be referred to as a backhaul link. For example, as shown in FIG. 3, the terminal 1 is connected to the IAB node 1 through a wireless access link, the IAB node 1 is connected to the IAB node 2 through a wireless backhaul link, and the IAB node 2 is connected to the IAB donor 1 through a wireless backhaul link.

[0153] To ensure service transmission reliability, optionally, in the IAB network, multi-hop IAB node networking and multi-connectivity IAB node networking are supported. There may be a plurality of transmission paths between the terminal and the IAB donor. On a path, there is a determined hierarchical relationship between IAB nodes, and between an IAB node and a donor node serving the IAB node. Each IAB node or terminal considers, as a parent node, a node providing an access service for the IAB node or terminal. Correspondingly, each IAB node or terminal may be considered as a child node of the parent node of the IAB node or terminal.

[0154] In addition, in the embodiments, a parent node of a parent node of an IAB node is referred to as a grandparent node of the IAB node, and a child node of a child node of the IAB node is considered as a grandchild node of the IAB node.

[0155] It may be understood that a parent node and a child node are relative concepts. A node may be a child node of one node, and may be a parent node of another node. For example, in FIG. 3, the IAB node 1 is a parent node of the terminal 1, and the terminal 1 is a child node of the IAB node 1. The IAB node 2 is a parent node of the IAB node 1, and the IAB node 1 is a child node of the IAB node 2. The IAB donor 1 (which may be an IAB donor DU) is a parent node of the IAB node 2, and the IAB node 2 is a child node of the IAB donor 1 (which may be the IAB donor DU).

[0156] An uplink data packet of the terminal may be transmitted to the donor node via the one or more IAB nodes, and then sent by the donor node to a core network device, for example, a mobile gateway device (for example, a user plane function (UPF) network element in a 5G network). A downlink data packet of the terminal is received by the donor node from the core network device (mobile gateway device), and then sent to the terminal via the one or more IAB nodes.

[0157] For example, in FIG. 3, a transmission path of an uplink data packet between the terminal 1 and the IAB donor 1 is: terminal 1.fwdarw.IAB node 1.fwdarw.IAB node 2.fwdarw.IAB donor 1, and a transmission path of a downlink data packet between the terminal 1 and the IAB donor 1 is: IAB donor 1.fwdarw.IAB node 2.fwdarw.IAB node 1.fwdarw.terminal 1.

[0158] In the IAB network, on a transmission path, an IAB node accessed by the terminal may be referred to as an access IAB node, and another IAB node on the transmission path is referred to as an intermediate IAB node. The intermediate IAB node may provide a backhaul service for the terminal. An IAB node may serve as an access IAB node of a terminal, or may serve as an intermediate IAB node of another terminal.

[0159] For example, in FIG. 3, on the path “terminal 1.fwdarw.IAB node 1.fwdarw.IAB node 2.fwdarw.IAB donor 1”, the IAB node 1 is an access IAB node, and the IAB node 2 is an intermediate IAB node. If a terminal 2 (not shown in FIG. 3) accesses an IAB node 3 (not shown in FIG. 3), and the IAB node 3 accesses the IAB node 1, for the terminal 2, the IAB node 3 is an access IAB node, and the IAB node 1 is an intermediate IAB node.

[0160] In the IAB network, one or more IAB nodes and one or more terminals served by an IAB node may be referred to as a descendant node of the IAB node. It may be understood that the descendant node may include the IAB node served by the IAB node, or it may be understood that the descendant node includes a subordinate IAB node connected to the IAB node through at least one-hop link. For example, the descendant node includes a child node and a grandchild node, and terminals accessing these IAB nodes, for example, terminals accessing the child node and the grandchild node.

[0161] For example, in FIG. 3, a descendant node of the IAB node 2 includes the terminal 1 and the IAB node 1.

[0162] The foregoing IAB network is merely an example. In an IAB network with multi-hop and multi-connectivity, there are more other possibilities in the IAB network. For example, a donor node and an IAB node accessing another donor node form dual connectivity to serve a terminal. The possibilities are not listed one by one herein.

[0163] In the IAB network, when serving as a parent node, an IAB node may play a role similar to that of an access network device, to provide an access service for a child node of the IAB node. For example, the IAB node may allocate, to the child node of the IAB node through scheduling, an uplink resource for transmitting uplink data. When the IAB node serves as a child node, a parent node that provides a service for the IAB node may play a role of a terminal device. For example, the IAB node establishes a connection to the parent node by performing operations such as cell selection and random access, to obtain an uplink resource that is scheduled by the parent node for the IAB node and that is for transmitting uplink data.

[0164] By way of example, and not limitation, in the embodiments, a functional unit that is in the IAB node and that supports the IAB node in playing the role of the terminal device is referred to as a mobile terminal (MT) functional unit of the IAB node, and is an IAB-MT or IAB-UE for short; and a functional unit that is in the IAB node and that supports the IAB node in playing the role of the access network device is referred to as a DU functional unit of the IAB node, and is an IAB-DU for short. The IAB-MT and the IAB-DU may be logical functional units, and functions of the IAB-MT and the IAB-DU are both implemented by the IAB node. Alternatively, the IAB-MT and the IAB-DU may be physically divided, and the IAB-MT and the IAB-DU may be different physical devices in the IAB node.

[0165] For example, in FIG. 3, the IAB node 1 includes an MT functional unit and a DU functional unit, and the IAB node 2 includes an MT functional unit and a DU functional unit.

[0166] FIG. 4A is a schematic diagram of a control plane protocol stack in a single air interface scenario according to an embodiment, and FIG. 4B is a schematic diagram of a user plane protocol stack in a single air interface scenario according to an embodiment.

[0167] The single air interface scenario may be understood as follows: A terminal is directly connected to an access network device and does not need to be connected to the access network device via a relay node. UE in FIG. 4A and FIG. 4B may be the terminal 130 in FIG. 1, and a gNB in FIG. 4A and FIG. 4B may be the access network device 150 in FIG. 1 and may use the CU-DU separation architecture shown in FIG. 2.

[0168] In the single-air-interface scenario, the UE may access a CU via a DU. Functions of peers of an RLC layer, a MAC layer, and a PHY layer that are of the UE are implemented by the DU, and functions of peers of an RRC layer, an SDAP layer, and a PDCP layer that are of the UE can be implemented by the CU.

[0169] For a control plane, as shown in FIG. 4A, peers of the RRC layer and the PDCP layer that are of the UE are established in the CU. The UE and the DU are connected through an interface (for example, a Uu interface), and peers of the RLC layer, the MAC layer, and the PHY layer that are of the UE are established in the DU. The DU and the CU are connected through a control plane interface (for example, an F1-control plane interface, F1-C interface), and peers of an F1 application protocol (FLAP) layer, a stream control transmission protocol (SCTP) layer, an internet protocol (IP) layer, a layer (L) 2, and a layer (L) 1 that are of the DU are established in the CU.

[0170] For a user plane, as shown in FIG. 4B, peers of the SDAP layer and the PDCP layer that are of the UE are established in the CU. The UE and the DU are connected through a Uu interface, and peers of the RLC layer, the MAC layer, and the PHY layer that are of the UE are established in the DU. The DU and the CU are connected through an F1-user plane (F1-U) interface, and peers of a general packet radio service (GPRS) tunneling protocol-user plane (GTP-U) layer, a user datagram protocol (UDP) layer, an IP layer, an L2, and an L1 that are of the DU are established in the CU.

[0171] FIG. 5A is a schematic diagram of a control plane protocol stack in an IAB network according to an embodiment, and FIG. 5B is a schematic diagram of a user plane protocol stack in an IAB network according to an embodiment. FIG. 5A and FIG. 5B are described by using the scenario in FIG. 3 as an example.

[0172] In the IAB network, peers of a PHY layer, a MAC layer, and an RLC layer that are of a terminal are located on an access IAB node, and peers of a PDCP layer, an SDAP layer, and an RRC layer that are of the UE are located on an IAB donor CU. If the IAB donor CU includes a CP and a UP, a peer of the RRC layer of the UE is located on the CP (namely, a donor-CU-CP) of the IAB donor CU, and peers of the PDCP layer and the SDAP layer that are of the UE are located on the UP (namely, a donor-CU-UP) of the IAB donor CU.

[0173] For a control plane, as shown in FIG. 5A, a Uu interface is established between a terminal 1 and a DU of an IAB node 1, and protocol layers that have peers include an RLC layer, a MAC layer, and a PHY layer. An F1-C interface is established between the DU of the IAB node 1 and an IAB donor CU 1, and protocol layers that have peers include an F1AP layer, an SCTP layer, and an IP layer. An F1 interface in an IAB donor is established between an IAB donor DU 1 and the IAB donor CU 1, and protocol layers that have peers include an IP layer, an L2, and an L1. A BL is established between the IAB node 1 and an IAB node 2, and between the IAB node 2 and the IAB donor DU 1, and protocol layers that have peers include a backhaul adaptation protocol (BAP) layer, an RLC layer, a MAC layer, and a PHY layer. In addition, peers of an RRC layer and a PDCP layer that are of the terminal 1 are established in the IAB donor CU 1, and a peer of an IP layer of the DU of the IAB node 1 is established in the IAB donor DU 1.

[0174] In the embodiments, the BAP layer has one or more of the following capabilities: adding, to a data packet, routing information that can be identified by a wireless backhaul node (an IAB node), performing route selection based on the routing information that can be identified by the wireless backhaul node, adding, to the data packet, identification information that is related to a quality of service (QoS) requirement and that can be identified by the wireless backhaul node, performing, for the data packet, QoS mapping on a plurality of links including the wireless backhaul node, adding data packet type indication information to the data packet, and sending flow control feedback information to a node that has a flow control capability. It should be noted that a protocol layer having these capabilities is not necessarily named as the BAP layer and may also have another name A person skilled in the art may understand that any protocol layer having these capabilities may be understood as the BAP layer in the embodiments.

[0175] It can be understood that, compared with a control plane protocol stack in the single air interface scenario, in the control plane protocol stack in the IAB network, a DU of the access IAB node implements functions of a DU of a gNB in the single air interface scenario, namely, functions of establishing the peers of the RLC layer, the MAC layer, and the PHY layer that are of the terminal and establishing the peers of the F1AP layer, the SCTP layer, and the IP layer that are of the CU. The IAB donor CU implements functions of a CU of the gNB in the single air interface scenario.

[0176] For a user plane, as shown in FIG. 5B, a Uu interface is established between a terminal 1 and a DU of an IAB node 1, and protocol layers that have peers include an RLC layer, a MAC layer, and a PHY layer. An F1-U interface is established between the DU of the IAB node 1 and an IAB donor CU 1, and protocol layers that have peers include a GTP-U layer, a UDP layer, and an IP layer. An F1 interface in an IAB donor is established between an IAB donor DU 1 and the IAB donor CU 1, and protocol layers that have peers include an IP layer, an L2, and an L1. A BL is established between the IAB node 1 and an IAB node 2, and between the IAB node 2 and the IAB donor DU 1, and protocol layers that have peers include a BAP layer, an RLC layer, a MAC layer, and a PHY layer. In addition, peers of an SDAP layer and a PDCP layer that are of the terminal 1 are established in the IAB donor CU 1, and a peer of an IP layer of the DU of the IAB node 1 is established in the IAB donor DU 1.

[0177] It can be understood that, compared with a user plane protocol stack in the single air interface scenario, in the user plane protocol stack in the IAB network, a DU of the access IAB node implements partial functions of a DU of a gNB in the single air interface scenario, namely, functions of establishing the peers of the RLC layer, the MAC layer, and the PHY layer that are of the terminal and establishing the peers of the GTP-U layer, the UDP layer, and the IP layer that are of the IAB donor CU 1. The IAB donor CU implements functions of a CU of the gNB in the single air interface scenario.

[0178] FIG. 5A and FIG. 5B are described by using only the protocol stack in the IAB scenario shown in FIG. 3 as an example. It should be noted that one IAB node may play one or more roles. The IAB node may have a protocol stack of the one or more roles. Alternatively, the IAB node may have a set of protocol stacks, and for different roles of the IAB node, protocol layers corresponding to different roles in the protocol stacks may be used to perform processing. The following uses an example in which the IAB node has the protocol stack of the one or more roles for description.

[0179] (1) Protocol Stack of a Terminal

[0180] When starting to access an IAB network or after accessing the IAB network, the IAB node may play a role of a terminal. An MT of the IAB node has a protocol stack of the terminal, for example, a protocol stack of the terminal 1 in FIG. 5A and FIG. 5B. The IAB node may transmit an uplink and/or downlink data packet (for example, an OAM data packet) of the IAB node to an IAB donor, perform measurement via an RRC layer, and the like.

[0181] (2) Protocol Stack of an Access IAB Node

[0182] After accessing an IAB network, the IAB node may provide an access service for a terminal, to play a role of an access IAB node. In this case, the IAB node has a protocol stack of the access IAB node, for example, the protocol stack of the IAB node 1 in FIG. 5A and FIG. 5B.

[0183] (3) Protocol Stack of an Intermediate IAB Node

[0184] After accessing an IAB network, the IAB node may play a role of an intermediate IAB node. In this case, the IAB node has a protocol stack of the intermediate IAB node, for example, the protocol stack of the IAB node 2 in FIG. 5A and FIG. 5B.

[0185] The IAB node may have the protocol stack of one or more of the terminal, the access IAB node, and the intermediate IAB node.

[0186] FIG. 6 is a schematic diagram of group handover according to an embodiment. The following provides descriptions with reference to FIG. 6.

[0187] In FIG. 6, an IAB node 1 may provide an access and/or backhaul service for one or more terminals and/or another IAB node. For ease of description, the one or more terminals and/or the another IAB node may be referred to as a descendant node or a subordinate node. For clarity, FIG. 6 shows a case in which the IAB node 1 is connected to a terminal 1 and an IAB node 4, and an IAB node 3 is connected to a terminal 2. The IAB node 1 provides an access service for the terminal 1 and the IAB node 4, the IAB node 4 provides an access service for the terminal 2, and the IAB node 1 provides a backhaul service for the terminal 2. It should be noted that in an actual network deployment scenario, the IAB node 1 may further have one or more grandchild nodes, and the IAB node 4 may provide access and/or backhaul services for more terminals or IAB nodes. This is not limited in this embodiment.

[0188] The IAB node 1 may be handed over due to link quality change, load change, or the like. The IAB node 1 is handed over from an IAB node 2 to the IAB node 3 (in other words, the IAB node 1 is handed over from a cell served by the IAB node 2 to a cell served by the IAB node 3), the IAB node 2 is connected to an IAB donor 1, and the IAB node 3 is connected to an IAB donor 2.

[0189] Because an IAB donor connected to the IAB node 1 before the handover and after the handover changes, the handover of the IAB node 1 may be referred to as cross-donor node handover.

[0190] First, the IAB node 1 may play a role of a terminal and be handed over from the IAB node 2 to the IAB node 3. In addition, because the IAB node 1 further serves descendant nodes, these descendant nodes may change, along with the IAB node 1, from connecting to the IAB node 2 to connecting to the IAB node 3. Because a donor node of the descendant nodes also changes, it may be considered that the descendant nodes are also handed over. The IAB node 1 and the descendant nodes may be referred to as a group, and handover of the IAB node 1 and the descendant nodes is referred to as group handover.

[0191] A group on which group handover is performed may include one or more IAB nodes. For ease of description, in the embodiments, a node whose parent node changes in group handover is referred to as a migrating IAB node or a migrating node, a parent node of the migrating IAB node before group handover is a source parent node, and a parent node of the migrating IAB node after group handover is a target parent node. For example, in FIG. 6, the IAB node 1 may be referred to as a migrating IAB node, the IAB node 2 may be referred to as a source parent node of the IAB node 1, and the IAB node 3 may be referred to as a target parent node of the IAB node 1.

[0192] The IAB donor 1 may be referred to as a source IAB donor of group handover, a source IAB donor of one or more nodes in a group, or a source IAB donor of one or more nodes in a group in a group handover process. Similarly, the IAB donor 2 may be referred to as a target IAB donor of group handover, a target IAB donor of one or more nodes in a group, or a target IAB donor of one or more nodes in a group in a group handover process.

[0193] The group handover process may be understood as a process in which group handover is performed, and may include a process from determining, by the source IAB donor, that handover is to be performed to performing handover on the one or more nodes in the group. The one or more nodes in the group may be successfully handed over or fail to be handed over. This is not limited in the embodiments.

[0194] The source IAB donor may be referred to as a source donor node or a source access network device, and the target IAB donor may be referred to as a target donor node or a target access network device. This is not limited in the embodiments.

[0195] During group handover, because an access network device connected to each node changes, each node in the group needs to perform a handover procedure, and re-initiate random access in a new cell after the handover. Re-initiating random access by each node in the group causes impact on limited random access resources, and a large amount of signaling in a random access procedure causes a signaling storm. To resolve this problem, it is considered that, in the group, except the migrating IAB node, all descendant nodes of the migrating IAB node are handed over together with the migrating IAB node, a parent node of each descendant node may not change, and a serving cell that is of the parent node and that is accessed by each descendant node may not change (where an identifier of the cell may change or may not change, for example, an NCGI or ECGI of the cell may change, and a physical cell identifier PCI of the cell may not change). Therefore, this may be considered as that the descendant nodes of the migrating IAB node in the group do not need to perform random access in a handover process (in other words, random access-free handover is performed on the descendant nodes). However, the random access-free handover may cause a case in which the node is uncertain about when the handover succeeds, and consequently, a timer used to detect whether the handover succeeds cannot be stopped in a timely manner. Timeout of the timer causes a handover failure, and the node may initiate a process such as RRC reestablishment, causing an unnecessary delay. According to a solution, a node on which random access-free handover is performed and that is in a group can receive indication information and stop a timer in a timely manner based on the indication information, thereby improving a handover success rate, reducing a handover delay, and ensuring communication performance after the handover.

[0196] FIG. 7 shows a communication method according to an embodiment. The communication method may be applied to relay systems such as an IAB system.

[0197] Optionally, in a relay system in FIG. 7, group handover may occur. A group may be handed over from a source access network device to a target access network device. A group on which group handover is performed includes at least a child node and a parent node. It may be understood that, in a group handover process, the parent node of the child node does not change. Optionally, the group may further include one or more other IAB nodes. For example, a migrating IAB node in the group may be the parent node, and the group may further include a descendant node of the parent node other than the child node. Alternatively, a migrating IAB node in the group may be a node between the parent node and the source access network device, and the group may further include a descendant node of the node other than the parent node and the child node.

[0198] Optionally, the child node may be an IAB node or a terminal, the parent node may be an IAB node, an upper-level node of the parent node may be an IAB node, the source access network device may be a source IAB donor, and the target access network device may be a target IAB donor.

[0199] FIG. 6 is used as an example. The group on which group handover is performed includes an IAB node 1, a terminal 1, an IAB node 4, and a terminal 2. The child node is the terminal 1 or the IAB node 4, and the parent node is the IAB node 1; or the child node is the terminal 2, the parent node is the IAB node 4, the source access network device is an IAB donor 1, and the target access network device is an IAB donor 2.

[0200] As shown in FIG. 7, the method includes the following steps.

[0201] S701: An access network device sends a first message to the parent node.

[0202] The access network device may be the target access network device of the parent node and the child node of the parent node in the group handover process.

[0203] Optionally, the parent node may be referred to as a first node, and the child node may be referred to as a second node. Optionally, there may be one or more other nodes between the second node and the access network device. For ease of description, the following uses the child node and the parent node for description.

[0204] In a possible implementation, S701 may include: The target access network device sends the first message to the source access network device, and the source access network device sends the first message to the parent node.

[0205] It may be understood that, the source access network device may be the source access network device of the parent node and the child node of the parent node in the group handover process.

[0206] It may be understood that there may be one or more other nodes between the source access network device and the parent node, and the source access network device may send the first message to the parent node via the one or more other nodes.

[0207] Optionally, the first message sent by the target access network device to the source access network device may be included in a handover request response message, and the first message sent by the source access network device to the parent node may be included in an F1AP message (for example, a UE context modification request message).

[0208] S702: The parent node sends the first message to the child node.

[0209] Optionally, S701 and S702 may be expressed as follows: The access network device sends the first message to the child node via the parent node, or the child node receives the first message from the access network device via the parent node.

[0210] Optionally, after receiving the first message, the child node may perform random access-free handover. In the embodiments, handover may also be referred to as RRC reconfiguration, master cell group (MCG) change, or secondary cell group (SCG) change.

[0211] Optionally, the description “before the child node receives the first message” may be referred to as before handover.

[0212] Optionally, the first message may be a first RRC reconfiguration message. An RRC reconfiguration message may be referred to as a handover command message.

[0213] Optionally, the first message may not include random access configuration information.

[0214] Optionally, the first message may indicate that the child node does not perform random access, and the indication may be explicit or implicit.

[0215] For example, the indication is explicit. The first message may include a random access-free indication, and the child node does not perform random access based on the indication.

[0216] For another example, the indication is implicit. The first message may not include a random access-free indication. The child node and the target access network device may agree that the child node does not perform random access when the child node receives the first message. Alternatively, the child node and the target access network device may agree that the child node does not perform random access when the first message does not include the random access configuration information. Alternatively, another manner is used for indication during implementation. This is not limited in the embodiments.

[0217] Optionally, the first message may include a reconfiguration with sync information element.

[0218] Optionally, the foregoing random access-free indication may be carried in the reconfiguration with sync information element.

[0219] Optionally, the reconfiguration with sync information element does not include the random access configuration information.

[0220] Optionally, the child node may determine, via the reconfiguration with sync information element, that the child node needs to be handed over, and does not perform random access during the handover.

[0221] Because group handover is performed on the child node along with the parent node, the child node and the parent node do not need to be resynchronized. In an IAB network, a parent node may have one or more child nodes. The child node does not need to perform random access in a cell of the parent node, so that a quantity of times of initiating random access by the child node can be greatly reduced. Therefore, a delay caused by the handover can be reduced. In addition, a case in which random access resources are limited when a large quantity of child nodes initiate random access can be avoided.

[0222] Optionally, a cell radio network temporary identifier (C-RNTI) of the child node before and after the handover may remain unchanged.

[0223] Optionally, the C-RNTI uniquely identifies the child node in the cell of the parent node or may be understood as an identifier of the child node in the accessed cell of the parent node. A name of the C-RNTI is not limited in the embodiments. The C-RNTI may be replaced with another identifier identifying the child node in the cell.

[0224] In an implementation, the first message may not include the C-RNTI of the child node.

[0225] In this manner, the first message does not include the C-RNTI of the child node. After receiving the first message, the child node may continue to use, by default, the C-RNTI used before the child node receives the first message.

[0226] In another implementation, the first message may include indication information indicating that the C-RNTI of the child node remains unchanged.

[0227] In this manner, the child node may determine, based on the indication information, that the C-RNTI of the child node remains unchanged. Therefore, after receiving the first message, the child node continues to use the C-RNTI used before the child node receives the first message.

[0228] In still another implementation, the first message may include the C-RNTI used before the child node receives the first message.

[0229] In this manner, the child node may use the C-RNTI based on the C-RNTI carried in the first message.

[0230] Although the parent node of the child node does not change before and after the handover of the child node, an access network device serving the child node changes. For example, the access network device serving the child node changes from the source access network device to the target access network device, and some identifiers (for example, an NCGI) of the cell accessed by the child node are identifiers of the access network device. Therefore, before and after the handover of the child node, although the accessed cell does not change, the identifiers of the accessed cell change, in other words, some configurations of the cell accessed by the child node change. In the foregoing several implementations, the C-RNTI of the child node may remain unchanged, and therefore a process of configuring the C-RNTI by the child node is simplified, a large amount of C-RNTI reconfiguration in IAB group handover is avoided, power consumption of the child node is reduced, and power of the child node is saved.

[0231] Optionally, the C-RNTI of the child node before and after the handover may change. For example, the first message may include an updated C-RNTI, and the child node may use the updated C-RNTI in the first message in a handover process and after completing the handover. This is not limited.

[0232] S703: The child node starts a timer.

[0233] After receiving the first message, the child node may start the timer.

[0234] Optionally, the timer may be used to monitor whether the handover of the child node succeeds. Optionally, duration of the timer may be included in the first message.

[0235] S704: The child node sends a second message to the parent node.

[0236] Optionally, after the child node receives the first message, random access-free handover may be performed on the child node. After the handover is completed, the child node sends the second message to the parent node.

[0237] S705: The parent node sends the second message to the target access network device.

[0238] Optionally, S705 and S706 may be described as: The child node sends the second message to the target access network device via the parent node, or the target access network device receives the second message from the child node via the parent node.

[0239] Optionally, the second message may be a first RRC reconfiguration complete message, and the first RRC reconfiguration complete message may be referred to as a handover complete message.

[0240] S706: The target access network device sends first indication information to the parent node.

[0241] Optionally, after parsing the second message, the target access network device may determine that reconfiguration of the child node is completed, and the target access network device may send the first indication information to the parent node, so as to trigger the parent node to send second indication information to the child node.

[0242] Optionally, the first indication information may indicate the parent node to send the second indication information to the child node, may indicate that reconfiguration of the child node is completed, may indicate that the child node may stop the timer, or the first indication information may indicate other content. Indication information that can trigger the parent node to send the second indication information to the child node may be the first indication information.

[0243] Optionally, the first indication information may include an identifier of the child node. It may be understood that the parent node may have a plurality of child nodes. The first indication information carries identifiers of the child nodes. After receiving the first indication information, the parent node may determine a child node to which the parent node sends the second indication information.

[0244] S706 is optional.

[0245] S707: The parent node sends the second indication information to the child node.

[0246] In an implementation, S706 is performed. In response to the first indication information, the parent node sends the second indication information to the child node.

[0247] In another implementation, S706 is omitted. After receiving the second message from the child node, or after sending the second message to the target access network device, the parent node may determine that reconfiguration of the child node is completed, and the parent node may send the second indication information to the child node.

[0248] In the foregoing two implementations, the second indication information may indicate to stop the timer. In the embodiments, the timer may be a T304 timer or may have another name. This is not limited.

[0249] For example, indication may be performed based on the second indication information in an explicit manner. The second indication information occupies one bit or more bits, and information about the one bit or more bits indicates to stop the timer.

[0250] For another example, indication may be performed based on the second indication information in an implicit manner. The second indication information may be a first-type MAC CE, and the first-type MAC CE may be understood as a MAC CE of a type. When receiving the MAC CE of such a type, the child node may stop the timer. The first-type MAC CE may carry no information or carry information. This is not limited in the embodiments. Optionally, a type of the MAC CE may be identified by a protocol-specified logical channel identifier (LCID) corresponding to the MAC CE. The type of the MAC CE is not limited.

[0251] For another example, indication may be performed based on the second indication information in an implicit manner. The second indication information may be a MAC CE carrying a UE contention resolution identity. Optionally, the MAC CE may be a MAC CE of a type. Optionally, a type of the MAC CE may be identified by a protocol-specified logical channel identifier (LCID) corresponding to the MAC CE.

[0252] Optionally, the MAC CE carrying the UE contention resolution identity may be transmitted on a PDSCH, and the PDSCH is scheduled through a PDCCH, where the PDCCH is scrambled using the C-RNTI of the child node. Therefore, after the child node successfully parses the MAC CE carrying the UE contention resolution identity, it may be considered that the child node receives the second indication information, and therefore stops the timer.

[0253] Optionally, the MAC CE carrying the UE contention resolution identity may be a MAC CE of any type. This is not limited in the embodiments.

[0254] Optionally, the UE contention resolution identity may be any value. For example, the value may be the C-RNTI of the child node, or may be a value of one or more bits in the C-RNTI, or may be any value. The value may not have meaning. This is not limited.

[0255] S708: The child node stops the timer.

[0256] After receiving the second indication information, the child node stops the timer based on the second indication information.

[0257] In the method in FIG. 7, the parent node sends the second indication information to the child node, and the child node may stop the timer in a timely manner. This avoids a handover failure and subsequent failure processing (for example, performing a recovery operation such as RRC reestablishment) caused by timeout of the timer, reduces a delay, and improves service transmission continuity.

[0258] Optionally, the method in FIG. 7 may further include: The target access network device sends a third message to the parent node. The method may include: The target access network device sends the third message to the source access network device, and the source access network device sends the third message to the parent node.

[0259] Optionally, the third message may be a third RRC reconfiguration message.

[0260] In an implementation, the parent node may perform random access-free handover based on the third message. The third message may explicitly or implicitly indicate the parent node not to perform random access. For details, refer to content in the first message, and details are not described herein again. Optionally, the C-RNTI of the parent node before and after the handover may remain unchanged or may change. For details, refer to content in S702. Details are not described herein again.

[0261] In another implementation, the parent node may perform handover with random access based on the third message. The third RRC reconfiguration message may include the random access configuration information.

[0262] In the foregoing two implementations, after receiving the third message, the parent node may start a timer. The timer is used to monitor whether handover of the parent node succeeds.

[0263] Optionally, the parent node may first receive the first message or first send the first message to the child node, and then receive the third message. In this way, the following case can be avoided: Handover is performed on the parent node after the parent node receives the third message, and consequently the parent node stops receiving a message and/or data from a source donor node and cannot forward the first message for the child node. This may be implemented in the following implementations.

[0264] In an implementation, after the parent node receives the first message or sends the first message to the child node, the parent node sends third indication information to the source access network device, to trigger the source access network device to send the third message to the parent node.

[0265] Optionally, the third indication information may indicate that the source access network device sends the third message to the parent node, or may indicate that the parent node has received the first message from the source access network device, or has sent the first message to the child node, or may indicate that the parent node is ready to receive the third message, or the like. It should be noted that information for triggering the source access network device to send the third message to the parent node may all be considered as the third indication information, and the third indication information may further indicate other content. This is not limited in the embodiments.

[0266] One child node may be used for description. It may be understood that the parent node may have one or more child nodes, and each child node receives a first message of the child node via the parent node.

[0267] Optionally, the parent node may receive first messages of all the child nodes from the source access network device. Alternatively, after sending the first message of each child node to the child node, the parent node sends the third indication information to the source access network device.

[0268] Optionally, the third indication information may be carried in an F1AP message, and the F1AP message may be a non-UE associated F1AP message.

[0269] Alternatively, optionally, after the parent node receives the first messages of all the child nodes or sends the first message of each child node to the child node, the parent node may send an F1AP message to the source access network device, for example, a UE context modification response message for the child node. The third indication information may be carried in a UE context modification response message sent by the parent node for the last child node.

[0270] In another implementation, after the parent node receives the first message or sends the first message to the child node, the parent node may send an F1AP message to the source access network device, for example, a UE context modification response message for the child node. The source access network device may send the third message to the parent node after receiving the UE context modification response message.

[0271] It may be understood that, if the parent node has a plurality of child nodes, after the parent node receives the first message of each child node or sends the first message of each child node to the child node, the parent node may send the F1AP message to the source access network device, for example, a UE context modification response message for the child node. The source access network device may send the third message to the parent node after receiving UE context modification response messages for all the child nodes sent by the parent node.

[0272] Optionally, the method in FIG. 7 may further include: The source access network device sends a handover request message to the target access network device. The handover request message includes one or more of the following: a cell radio network temporary identifier of one or more nodes, an identifier of a cell accessed by one or more nodes, and hierarchical information of one or more descendant nodes in a network topology. The one or more nodes are one or more nodes in the group, and include the child node and the parent node.

[0273] Optionally, the hierarchical information of the one or more nodes in the network topology is used to determine duration of one or more timers of the one or more nodes.

[0274] Optionally, the first message and/or the third message may be carried in the handover request response message sent by the target access network device to the source access network device.

[0275] Optionally, the first message includes information about the duration of the timer. In S703, the child node may set the timer based on the information about the duration of the timer, and may start the timer.

[0276] Optionally, the third message includes information about duration of the timer. After receiving the third message, the parent node may set the timer based on the information about the duration of the timer in the first message, and may start the timer.

[0277] FIG. 8A, FIG. 8B, and FIG. 8C show a group handover method according to an embodiment. The method may be applied to relay systems such as an IAB system. FIG. 7 is further described below with reference to FIG. 8A, FIG. 8B, and FIG. 8C.

[0278] In FIG. 8A, FIG. 8B, and FIG. 8C, group handover is performed on a group, and handover from a source access network device to a target access network device is performed. The group includes at least a first node, a second node, and a third node. The third node is a migrating IAB node, the third node is a parent node of the second node, and the second node is a parent node of the first node. The third node is connected to a source parent node before the handover, and the third node is connected to a target parent node after the handover. Optionally, the source parent node may be the source access network device, and the target parent node may be the target access network device. The migrating IAB node is an IAB node whose parent node needs to be replaced in a handover process.

[0279] Optionally, the first node and the second node in FIG. 8A, FIG. 8B, and FIG. 8C may be respectively the child node and the parent node in FIG. 7, or the second node and the third node in FIG. 8A, FIG. 8B, and FIG. 8C may be respectively the child node and the parent node in FIG. 7.

[0280] It should be noted that, optionally, the third node may further have one or more other child nodes. Content of the second node may also be applicable to the one or more other child nodes of the third node. Optionally, the second node may further have one or more other child nodes. Content of the first node may also be applicable to the one or more other child nodes of the second node.

[0281] FIG. 6 is used as an example. The first node is a terminal 2, the second node is an IAB node 4, the third node is an IAB node 1, the source access network device is an IAB donor 1, the target access network device is an IAB donor 2, the source parent node is an IAB node 2, and the target parent node is an IAB node 3. In FIG. 6, the IAB node 1 further has a child node terminal 1, and content of the IAB node 4 is also applicable to the terminal 1. If the IAB node 4 further has a child node IAB node 5 (not shown in the figure), content of the terminal 2 is also applicable to the IAB node 5.

[0282] As shown in FIG. 8A, FIG. 8B, and FIG. 8C, the method includes the following steps.

[0283] S801: The third node sends a measurement report to the source parent node.

[0284] S802: The source parent node sends the measurement report to the source access network device.

[0285] S803: The source access network device sends a handover request message to the target access network device.

[0286] Optionally, the source access network device determines, based on the measurement report, that the third node is handed over from the source access network device to the target access network device, and sends a handover request message to the target access network device.

[0287] Optionally, the group handover request message includes one or more of the following: a cell identifier of a cell accessed by each node (for example, an IAB node or a terminal) in the group, a C-RNTI of the node in the accessed cell, and hierarchical information of the node in a network topology.

[0288] Optionally, the cell identifier of the cell accessed by each node may be a cell identifier of a primary cell accessed by the node, and the primary cell may be referred to as a special cell (SpCell).

[0289] Optionally, in the foregoing plurality of implementations, the cell identifier may include one or more of a physical cell identifier (PCI), an NR cell identity (NCI), an NR cell global identifier (NCGI), and an E-UTRAN cell global identifier (ECGI).

[0290] Optionally, a cell identifier of a cell accessed by the migrating IAB node (namely, the third node) may be a cell identifier of a target cell of the third node. It may be understood that, after determining that handover is to be performed, the source access network device may determine to carry the cell identifier of the target cell of the third node in the handover request message and send the handover request message to the target access network device. Optionally, the cell identifier of the target cell may be an NCGI or an ECGI.

[0291] Optionally, a parent node of a descendant node of the migrating IAB node does not change in a group handover process. A cell identifier of a cell accessed by the descendant node may be a cell identifier of a cell accessed by the descendant node before the handover.

[0292] Optionally, a cell identifier of a cell accessed by a node and a C-RNTI of the node in the accessed cell may uniquely identify the node.

[0293] Optionally, the hierarchical information indicates a relative location of a node in a network topology or a connection relationship between the node and another node.

[0294] For example, the hierarchical information may be a hierarchy or a location relative to that of the migrating relay node (namely, the third node). For example, assuming that a hierarchy of the third node is 0 (which may be another value, and is not limited in the embodiments), a hierarchy of one or more child nodes of the third node is 1, that is, a hierarchy of the second node is 1; a hierarchy of one or more grandchild nodes of the third node is 2, that is, a hierarchy of the first node is 2; and so on. For example, if a descendant node is connected to the third node through an X-hop link, hierarchical information of the descendant node may be denoted as X, where X is a positive integer. Alternatively, the hierarchical information may be a hierarchy relative to that of another node. The another node may be the second node, the first node, a node on a path from the source parent node to the source donor node, or the like. This is not limited in embodiments.

[0295] In an implementation, the handover request message may be a group handover request message, and the group handover request message is used to request handover for a group.

[0296] Table 1 is a schematic diagram of a group handover request message. As shown in Table 1, the group handover request message includes a plurality of items, each item corresponds to one node, an item of each node further includes one or more items, and the one or more items include a cell identifier of a cell accessed by each node, a C-RNTI of each node, and/or hierarchical information of each node. In Table 1, the item of each node is parallel.

TABLE-US-00001 TABLE 1 >Handover request message  >>Third node   >>>Cell identifier of the accessed cell, a C-RNTI, and/or hierarchical information  >>Second node   >>>Cell identifier of an accessed cell, a C-RNTI, and/or hierarchical information  >>First node  >>>Cell identifier of an accessed cell, a C-RNTI, and/or hierarchical information

[0297] Table 2 is another schematic diagram of a group handover request message. As shown in Table 2, the group handover request message includes one item, the item corresponds to the third node, the item of the third node further includes one or more items, the one or more items include the cell identifier of the cell accessed by the third node, a C-RNTI of the third node, and/or hierarchical information of the third node, and the second node. An item of the second node includes a cell identifier of a cell accessed by the second node, a C-RNTI of the second node, and/or hierarchical information of the second node, and the first node. An item of the second node includes a cell identifier of a cell accessed by the second node, a C-RNTI of the second node, and/or hierarchical information of the second node. In Table 2, an item of each node includes an item of a child node of the node.

TABLE-US-00002 TABLE 2 >Handover request message  >>Third node   >>>Cell identifier of the accessed cell, the C-RNTI, and/or the hierarchical information   >>>Second node    >>>>Cell identifier of the accessed cell, the C-RNTI, and/or the hierarchical    information   >>>>First node    >>>>>Cell identifier of the accessed cell, the C-RNTI, and/or the hierarchical    information

[0298] Optionally, when the item of each node shown in Table 2 includes the item of the child node of the node, the item of each node may not carry hierarchical information of the node, and hierarchical information of nodes may be obtained based on a mutual inclusion relationship between items of the nodes. For example, a relative topology relationship between the first node, the second node, and the third node (where the second node is a child node of the third node, and the first node is a child node of the second node) may be deduced based on a structure of the information in Table 2, and the hierarchical information of the nodes may be further learned (where for example, if a hierarchy of the third node is 0, a hierarchy of the second node level is 1, and a hierarchy of the first node is 2).

[0299] Table 1 and Table 2 are merely examples. The group handover request message may exist in another form. This is not limited in the embodiments.

[0300] In another implementation, the handover request message may include one or more independent handover request messages, where one handover request message corresponds to one node, or this may be understood as that one handover request message is for requesting handover for one node.

[0301] Optionally, in this implementation, a handover request message of each node includes a cell identifier of a cell accessed by the node, a C-RNTI of the node in the accessed cell, and/or hierarchical information of the node in a network topology.

[0302] S804: The target access network device sends a handover request response message to the source access network device.

[0303] In an implementation, if the handover request message in S803 is a group handover request message, the handover request response message in S804 may be a group handover request response message.

[0304] Optionally, the group handover request response message includes an RRC reconfiguration message of each node.

[0305] For clarity, an RRC reconfiguration message of the first node is referred to as a first RRC reconfiguration message, an RRC reconfiguration message of the second node is referred to as a second RRC reconfiguration message, and an RRC reconfiguration message of the third node is referred to as a third RRC reconfiguration message.

[0306] In this implementation, the group handover request response message includes the first RRC reconfiguration message, the second RRC reconfiguration message, and the third RRC reconfiguration message.

[0307] In another implementation, for example, the handover request message in S803 includes one or more independent handover request messages, and the handover request response message in S804 may include one or more independent handover request response messages, where each handover request response message corresponds to one node, and a handover request response message of each node includes an RRC reconfiguration message of the node.

[0308] In the another implementation, the handover request message in S803 includes a first handover request message, a second handover request message, and a third handover request message, and the handover request response message in S804 includes a first handover request response message, a second handover request response message, and a third handover request response message. The first handover request response message is a handover request response message of the first node, and includes a first RRC reconfiguration message; the second handover request response message is a handover request response message of the second node, and includes a second RRC reconfiguration message; and the third handover request response message is a handover request response message of the third node, and includes a third RRC reconfiguration message.

[0309] Optionally, in the foregoing plurality of implementations, the RRC reconfiguration message of each node may include information about duration of a timer of the node. The following further describes the information about the duration of the timer of the node.

[0310] Optionally, the target access network device may determine duration of a timer of each node based on the hierarchical information of the node in the handover request response message in S803.

[0311] Optionally, a descendant node of a higher hierarchy may be understood as a node with a larger hop quantity of a backhaul link between the node and the migrating node (namely, the third node), and duration of a timer is longer. A node of a lower hierarchy may be understood as a node with a smaller hop quantity of a backhaul link between the node and the third node, and duration of a timer is shorter.

[0312] For example, the hierarchy of the first node is 2, and duration of a timer of the first node is 200 ms; the hierarchy of the second node is 1, and duration of a timer of the second node is 150 ms; and the hierarchy of the third node is 0, and duration of a timer of the third node is 100 ms.

[0313] In an implementation, the information about the duration of the timer may directly indicate the duration of the timer.

[0314] For example, information about the duration of the timer of the first node indicates 200 ms, information about the duration of the timer of the second node indicates 150 ms, and information about the duration of the timer of the third node indicates 100 ms.

[0315] In another implementation, the information about the duration of the timer may include one or more parameters, and the one or more parameters are used to determine the duration of the timer. After receiving the information about the duration of the timer of each node, the node may obtain the duration of the timer based on the one or more parameters.

[0316] Optionally, the duration of the timer may be obtained by performing an operation on the one or more parameters. The operation may include multiplication, exponentiation, or the like. An operation manner is not limited.

[0317] For example, the one or more parameters include duration of a basic timer and a scale factor, and each node may perform an operation based on the duration of the basic timer and the scale factor, to obtain the duration of the timer of the node.

[0318] For example, the information about the duration of the timer of the first node includes duration 50 ms of the basic timer and a scale factor 4, and the first node may obtain duration 200 ms of the timer of the first node by multiplying 50 by 4. The information about the duration of the timer of the second node includes the duration 50 ms of the basic timer and a scale factor 3, and the first node may obtain duration 150 ms of the timer of the first node by multiplying 50 by 3. The information about the duration of the timer of the first node includes the duration 50 ms of the basic timer and a scale factor 2, and the first node may obtain duration 100 ms of the timer of the first node by multiplying 50 by 2.

[0319] The source access network device sends the hierarchical information to the target access network device, so that the target access network device can properly determine duration of a timer based on a hierarchy of a node, thereby avoiding a handover failure caused by improper setting of the duration of the timer, reducing a handover delay, and reducing signaling overheads.

[0320] Optionally, mutual reference may be made to the handover request message and the handover request response message in S803 and S804 and the handover request message and the handover request response message in FIG. 7.

[0321] S805: The source access network device sends a downlink F1AP message to the second node, for example, a UE context modification request message, where the message includes the first RRC reconfiguration message. Optionally, the downlink F1AP message (for example, the UE context modification request message) may further include indication information indicating the second node to stop data transmission with the first node.

[0322] Optionally, the indication information may be carried in a transmission action indicator information element. The second node may read the indication information, and then stop data transmission with the first node, where the data transmission includes downlink data transmission and/or uplink data transmission with the first node. After performing step S806, the second node may stop data transmission with the first node.

[0323] S806: The second node sends the first RRC reconfiguration message to the first node.

[0324] Optionally, the first RRC reconfiguration message may not include random access configuration information. Optionally, the first RRC reconfiguration message may indicate a child node not to perform random access. The indication may be explicit or implicit. For details, refer to content of the first message in S702.

[0325] Optionally, the C-RNTI of the first node before and after the handover may remain unchanged. The first RRC reconfiguration message may not include the C-RNTI of the first node, or may include indication information indicating that the C-RNTI of the first node remains unchanged, or may include the C-RNTI that is of the first node and that is used before the first node receives the first message. Alternatively, the C-RNTI of the first node before and after the handover may change. For details, refer to content in S702.

[0326] S807: The first node starts the timer.

[0327] After receiving the first RRC reconfiguration message, the first node may start the timer. For details, refer to content in S703.

[0328] Optionally, if the first RRC reconfiguration message includes the information about the duration of the timer, the first node may obtain the duration of the timer based on the information about the duration of the timer, set the timer, and then start the timer.

[0329] S808: The second node sends an uplink F1AP message to the source donor node, for example, a UE context modification response (UE CONTEXT MODIFICATION RESPONSE) message.

[0330] Step S808 is an optional step. If the downlink F1AP message in step S805 is a UE context modification request message, step S808 is required.

[0331] The UE context modification response message in S808 may be understood as a UE context modification response message fed back by the second node for the first node.

[0332] S809: The first node sends a first RRC reconfiguration complete message to the second node.

[0333] S810: The source access network device sends a downlink F1AP message to the third node, for example, a UE context modification request message, where the message includes the second RRC reconfiguration message. Optionally, the downlink F1AP message (for example, the UE context modification request message) may further include indication information indicating the third node to stop data transmission with the second node. The third node may read the indication information, and then stop data transmission with the second node, where the data transmission includes downlink data transmission and/or uplink data transmission with the second node. For content of the indication information, refer to content in S805.

[0334] Optionally, S810 may be performed after S805 and/or S806. The following manners may be used.

[0335] In an implementation, after S805 or S806, the second node may send indication information to the source access network device, to trigger the source access network device to send the second RRC reconfiguration message to the second node, that is, trigger the source access network device to perform S810. For the indication information, refer to content of the third indication information in FIG. 7.

[0336] Optionally, if the second node has a child node in addition to the first node, the second node may send indication information to the source access network device after receiving RRC reconfiguration messages of all child nodes from the source access network device or sending RRC reconfiguration messages to all child nodes.

[0337] For example, FIG. 6 is used as an example. The second node is the IAB node 4, and the first node may be the terminal 2. The IAB node 4 may further include the child node IAB node 5 (not shown in FIG. 6) in addition to the child node terminal 2. After the IAB node 4 receives the first RRC reconfiguration message (an RRC reconfiguration message of the terminal 2) and an RRC reconfiguration message of the IAB node 5 from the IAB donor 1, the IAB node 4 sends the indication information to the IAB donor 1. Alternatively, after the IAB node 4 sends the first RRC reconfiguration message to the terminal 2, and the IAB node 4 sends an RRC reconfiguration message of the IAB node 5 to the IAB node 5, the IAB node 4 sends the indication information to the IAB donor 1.

[0338] Optionally, the indication information may be carried in the uplink F1AP message sent to the source access network device.

[0339] Optionally, the indication information may be carried in an uplink F1AP message (for example, a response to the UE context modification request message) sent by the second node for the last child node.

[0340] For example, the IAB node 4 first receives a UE context modification request message of the terminal 2 from the IAB donor 1, where the UE context modification request message includes the RRC reconfiguration message of the terminal 2. The IAB node 4 sends the RRC reconfiguration message to the terminal 2. The IAB node 4 sends a response to the UE context modification request message to the IAB donor 1 for the terminal 2. Then, the IAB node 4 receives a UE context modification request message of the IAB node 5 from the IAB donor 1, where the UE context modification request message includes the RRC reconfiguration message of the IAB node 5. The IAB node 4 sends the RRC reconfiguration information to the IAB node 5. The IAB node 4 sends a response to the UE context modification request message to the IAB donor 1 for the IAB node 5. The indication information may be carried in the response to the UE context modification request message sent by the IAB node 4 to the IAB donor 1 for the IAB node 5.

[0341] In another implementation, the source access network device may perform S810 after S808.

[0342] Optionally, if the second node has a child node in addition to the first node, the source access network device may perform S810 after receiving UE context modification response messages for all child nodes from the second node.

[0343] For example, after receiving, from the IAB node 4, the response to the UE context modification request message for the terminal 2 and the response to the UE context modification request message for the IAB node 5 that are sent by the IAB node 4, the IAB donor 1 performs S810.

[0344] The foregoing two implementations are for avoiding the following case: If S810 is performed before S805, after the second node receives the second RRC reconfiguration message, a handover action is performed on the second node, the second node stops data transmission with the source access network device, and consequently the second node cannot receive the first RRC reconfiguration message and cannot forward the first RRC reconfiguration message to the first node. The implementations can ensure that the second node can forward the first RRC reconfiguration message to the first node, so that a handover success rate of the first node is ensured.

[0345] S811: The third node sends the second RRC reconfiguration message to the second node.

[0346] Optionally, the second RRC reconfiguration message may not include the random access configuration information. Optionally, the second RRC reconfiguration message may indicate a child node not to perform random access. The indication may be explicit or implicit. For details, refer to content of the first message in FIG. 7.

[0347] Optionally, the C-RNTI of the second node before and after the handover may remain unchanged. The second RRC reconfiguration message may not include the C-RNTI of the second node, may include indication information indicating that the C-RNTI of the second node remains unchanged, or may include the C-RNTI of the second node used before the second node receives the first message. Alternatively, the C-RNTI of the second node before and after the handover may change. For details, refer to content in S702.

[0348] S812: The second node starts the timer.

[0349] After receiving the second RRC reconfiguration message, the second node may start the timer. For details, refer to content in S703.

[0350] Optionally, if the second RRC reconfiguration message includes the information about the duration of the timer, the second node may obtain the duration of the timer based on the information about the duration of the timer, set the timer, and then start the timer.

[0351] S813: The third node sends an uplink F1AP message to the source donor node, for example, a UE context modification response message.

[0352] Step S813 is an optional step. If the downlink F1AP message in step S810 is a UE context modification request message, step S813 is required. The UE context modification response message in S813 may be understood as a UE context modification response message fed back by the third node for the second node.

[0353] S814: The second node sends a second RRC reconfiguration complete message to the third node.

[0354] S815: The source access network device sends a downlink F1AP message to the source parent node, for example, a UE context modification request message, where the message includes the third RRC reconfiguration message.

[0355] Optionally, the downlink F1AP message (for example, the UE context modification request message) may further include indication information indicating the source parent node to stop data transmission with the third node. The source parent node may read the indication information, and then stop data transmission with the third node, where the data transmission includes downlink data transmission and/or uplink data transmission with the third node. For content of the indication information, refer to content in S805 and S810.

[0356] Optionally, similar to the foregoing case in which S810 is performed after S805 and/or S806, S815 may be performed after S810 and/or S811. This may be implemented in the following manners.

[0357] In an implementation, after S810 or S811, the third node may send indication information to the source access network device, to trigger the source access network device to send the third RRC reconfiguration message to the third node. For the indication information, refer to content of the third indication information in FIG. 7.

[0358] Optionally, if the third node has a child node in addition to the second node, the third node may send the indication information to the source access network device after receiving RRC reconfiguration messages of all child nodes from the source access network device or sending RRC reconfiguration messages to all child nodes.

[0359] For example, FIG. 6 is used as an example. The third node is the IAB node 1, the second node is the IAB node 4, and the IAB node 1 may have the child node terminal 1 in addition to the child node IAB node 4. After the IAB node 1 receives the second RRC reconfiguration message (an RRC reconfiguration message of the IAB node 4) and an RRC reconfiguration message of the terminal 1 from the IAB donor 1, the IAB node 1 may send the indication information to the IAB donor 1. Alternatively, after the IAB node 1 sends the second RRC reconfiguration message to the IAB node 4, and the IAB node 1 sends an RRC reconfiguration message of the terminal 1 to the terminal 1, the IAB node 1 sends the indication information to the IAB donor 1.

[0360] In another implementation, the source access network device may perform S815 after S813.

[0361] Optionally, if the third node has a child node in addition to the second node, the source access network device may perform S815 after receiving UE context modification response messages for all child nodes from the third node.

[0362] For example, after receiving, from the IAB node 1, a response to the UE context modification request message for the terminal 1 and a response to the UE context modification request message for the IAB node 4 that are sent by the IAB node 1, the IAB donor 1 performs S815.

[0363] S816: The source parent node sends the third RRC reconfiguration message to the third node.

[0364] In an implementation, the third RRC reconfiguration message may indicate the third node to perform random access in the target cell, and the third RRC reconfiguration message may include the cell identifier (for example, a PCI of the target cell) of the target cell. The target cell is a cell served by the target parent node of the third node.

[0365] Optionally, the third RRC reconfiguration message may include the random access configuration information and/or a new C-RNTI.

[0366] In another implementation, the third RRC reconfiguration message may indicate the third node not to perform random access.

[0367] Optionally, the third RRC reconfiguration message may not include the random access configuration information. Optionally, the third RRC reconfiguration message may indicate a child node not to perform random access. The indication may be explicit or implicit. For details, refer to content of the first message in FIG. 7.

[0368] Although the parent node of the third node changes, in other words, the parent node changes from the source parent node to the target parent node, if the source parent node is synchronized with the target parent node, the third node may not need to re-synchronize with the target parent node. The third node does not perform random access, so that a delay caused by random access can be avoided, a handover delay can be reduced, and a case in which random access resources are limited can be avoided.

[0369] Optionally, the C-RNTI of the third node before and after the handover may remain unchanged. The third RRC reconfiguration message may not include the C-RNTI of the third node, may include indication information indicating that the C-RNTI of the third node remains unchanged, or may include the C-RNTI of the third node before the third node receives the third RRC reconfiguration message. Alternatively, the C-RNTI of the third node before and after the handover may change. For details, refer to content in S702.

[0370] S817: The third node starts the timer.

[0371] After receiving the third RRC reconfiguration message, the third node may start the timer. For details, refer to content in S703.

[0372] Optionally, if the third RRC reconfiguration message includes the information about the duration of the timer, the third node may obtain the duration of the timer based on the information about the duration of the timer, set the timer, and then start the timer.

[0373] S818: The source parent node sends an uplink F1AP message to the source donor node, for example, a UE context modification response message.

[0374] Step S818 is an optional step. If the downlink F1AP message in step S815 is a UE context modification request message, step S818 is required. The UE context modification response message in S818 may be understood as a UE context modification response message fed back by the source parent node for the third node.

[0375] Optionally, after the third node receives the third RRC reconfiguration message, the third node may perform or not perform random access in the target cell based on the third RRC reconfiguration message. The following provides descriptions with reference to Manner 1 and Manner 2. It should be noted that either Manner 1 or Manner 2 is performed. Manner 1 includes S819 and S820, and Manner 2 includes S823 to S825. Both S821 and S822 exist regardless of Manner 1 or Manner 2.

[0376] S819: The third node may perform random access based on the third RRC reconfiguration message.

[0377] In this implementation, the parent node of the third node changes, and the third node may re-synchronize with the target parent node in a random access procedure, so as to ensure performance of communication between the third node and the target parent node.

[0378] S820: The third node stops the timer.

[0379] After the third node successfully performs random access in S819, the third node may stop the timer.

[0380] S821: The third node sends a third RRC reconfiguration complete message to the target parent node.

[0381] S822: The target parent node sends the third RRC reconfiguration complete message to the target access network device.

[0382] Optionally, the third RRC reconfiguration complete message in S822 may be carried in an uplink F1AP message, for example, an uplink RRC message transfer (UL RRC message transfer) message.

[0383] S823: The target access network device sends first indication information to the target parent node.

[0384] In Manner 2, the third node does not perform random access, and S819 and S820 do not exist. After S821 and S822, the target access network device may determine, after parsing the third RRC reconfiguration complete message, that the handover of the third node is completed, and the target access network device may send the first indication information to the target parent node, to trigger S824.

[0385] S823 is optional.

[0386] S824: The target parent node sends second indication information to the third node.

[0387] In an implementation, S823 is performed. In response to the first indication information, the target parent node sends the second indication information to the third node.

[0388] In another implementation, S823 is omitted. After S821 or S822, the target parent node sends the second indication information to the third node.

[0389] S825: The third node stops the timer.

[0390] After receiving the second indication information, the third node stops the timer based on the second indication information.

[0391] S826: The source access network device sends, to the target access network device, a message including a data packet transfer status, for example, a sequence number (SN) status transfer message.

[0392] The message includes transfer status information of an uplink data packet and/or a downlink data packet of the source access network device, and the uplink data packet and/or downlink data packet may be a PDCP packet data unit (PDU).

[0393] After receiving the SN Status Transfer message, the target access network device may continue uplink and/or downlink data transmission based on the data packet transfer status in the SN Status Transfer message after the handover of the third node is completed, to avoid a loss of service data of the terminal.

[0394] Optionally, if a CU of the source access network device is in a CP-UP separation architecture, a CP of the CU of the source access network device may initiate a bearer context modification procedure, to obtain an uplink/a downlink data packet transfer status (for example, SN status information of a PDCP PDU corresponding to a data radio bearer of each UE), and exchange endpoint configuration information used for data forwarding between the source access network device and the target access network device. For example, the CP of the CU of the source access network device may send a bearer context modification request message to an UP of the CU of the source access network device, and the UP of the CU of the source access network device may send a bearer context modification response message to the CP of the CU of the source access network device. The bearer context modification response message may include SN status information of an uplink/downlink PDCP PDU and may further include tunnel endpoint information used by the UP of the CU of the source access network device for data forwarding.

[0395] Optionally, if the target access network device is in an architecture with separation of a CP of a CU and a UP of the CU, the source access network device sends data and an SN status to the CP of the CU of the target access network device. The CP of the CU of the target access network device may initiate a bearer context modification procedure, to send downlink transport network layer address information (DL TNL address information) of an F1-U interface and/or a transfer status of a data packet (for example, the SN status information of the PDCP PDU corresponding to the data radio bearer of each UE) to the UP of the CU of the target access network device. For example, the CP of the CU of the target access network device may send a bearer context modification request message to the UP of the CU of the target access network device, where the context modification request message includes the transmission status of the data packet, and the UP of the CU of the target access network device may send a bearer context modification response message to the CP of the CU of the target access network device.

[0396] Optionally, the method in FIG. 8A, FIG. 8B, and FIG. 8C may further include: The target access network device sends an RRC reconfiguration message to the third node, where the RRC reconfiguration message may include configuration information of a BAP layer of the third node and/or configuration information of a backhaul RLC channel between the third node and the target parent node.

[0397] Optionally, the configuration information of the BAP layer of the third node and/or the configuration information of the backhaul RLC channel between the third node and the target parent node may be included in the third RRC reconfiguration message in S815 and S816.

[0398] Optionally, the configuration information of the BAP layer of the third node may include a BAP layer identifier allocated by the target access network device to the third node, and a default uplink BAP routing identity (BAP routing ID). The configuration information of the BAP layer of the third node may further include one or more other non-default uplink BAP layer routing identities, and a BAP layer identifier that is of a next hop (namely, the target parent node) of the third node and that corresponds to each uplink BAP routing identity. Each uplink BAP routing identity (including a default uplink BAP routing identity) includes a BAP address and a BAP path identity (BAP path ID). The BAP address is used to identify the target access network device or a DU of the target access network device. The BAP path ID is used to identify a transmission path from the third node to the device identified by the BAP address.

[0399] It may be understood that the configuration information of the BAP layer of the third node included in the RRC reconfiguration message may be for transmitting a corresponding data packet in step S827, where the data packet includes, for example, an F1AP message for establishing an F1 interface between the third node and the target access network device, and an SCTP handshake message related to a process of establishing an SCTP association between the third node and the target access network device.

[0400] Optionally, the configuration information of the backhaul RLC channel between the third node and the target parent node may include configuration information of a default backhaul RLC channel between the third node and the target parent node, and the like.

[0401] S827: The third node establishes the F1 interface with the target access network device.

[0402] Optionally, before establishing the F1 interface, the third node establishes the SCTP association with the target access network device.

[0403] For example, the third node may initiate an F1 interface establishment process to the target access network device. For another example, the third node may initiate an F1 interface re-establishment process to the target access network device, to trigger the target access network device to request, from the source access network device, a context that is of an F1 interface between the source access network device and the third node and that is maintained by the source access network device, and then the target access network device updates the context of the F1 interface. For another example, the target access network device first obtains, from the source access network device, the context that is of the F1 interface between the source access network device and the third node and that is maintained by the source access network device, and then the target access network device may initiate a context update process of the F1 interface, to update the context of the F1 interface between the source access network device and the third node.

[0404] Optionally, after S827, the method may further include: The target access network device sends updated configuration information of the BAP layer to the third node. The configuration information in this step may include one or more of the following content:

[0405] an uplink mapping configuration used when the third node serves as an access IAB node, a BAP routing identity for sending an uplink data packet, an identifier of a next-hop node corresponding to the routing identity, and an identifier of a BH RLC channel that is between the third node and the next-hop node and that is for carrying the uplink data packet of such a type, where the uplink data packet herein may be any one of the following: a UE-associated F1AP message, a non-UE associated F1AP message, a non-F1 interface message, and an F1-U data packet; and a bearer mapping relationship used when the third node serves as an intermediate IAB node, where the bearer mapping relationship includes: an identifier of a previous-hop node of the third node, an identifier of a BH RLC channel on a link between the third node and the previous-hop node, an identifier of the next-hop node of the third node, and an identifier of a BH RLC channel on a link between the third node and the next-hop node.

[0406] S828: The third node sends an uplink F1AP message to the target access network device, where the uplink F1AP message includes the second RRC reconfiguration complete message.

[0407] Optionally, the second RRC reconfiguration complete message in S828 may be carried in a UL RRC message transfer message.

[0408] S829: The target access network device sends third indication information to the third node.

[0409] In S829, after receiving the second RRC reconfiguration complete message and parsing the second RRC reconfiguration complete message, the target access network device may determine that the handover of the second node is completed, and the target access network device may send the third indication information to the third node, to trigger S830.

[0410] S829 is optional.

[0411] S830: The third node sends fourth indication information to the second node.

[0412] In an implementation, S829 is performed. In response to the third indication information, the third node sends the fourth indication information to the second node.

[0413] In another implementation, S829 is omitted. After S828, the third node sends the fourth indication information to the second node.

[0414] S831: The second node stops the timer.

[0415] After receiving the fourth indication information, the second node stops the timer based on the fourth indication information.

[0416] S832: The second node establishes an F1 interface with the target access network device.

[0417] For details, refer to the foregoing process of establishing the F1 interface between the third node and the target access network device. Details are not described herein again.

[0418] Optionally, the target access network device may further send BAP layer configuration information and/or backhaul RLC channel configuration information to the second node. For details, refer to content of descriptions of the third node. The third node in S827 may be replaced with the second node.

[0419] S833: The second node sends an uplink F1AP message to the target access network device, where the uplink F1AP message includes the first RRC reconfiguration complete message.

[0420] Optionally, the first RRC reconfiguration complete message in S833 may be carried in a UL RRC message transfer message.

[0421] S834: The target access network device sends fifth indication information to the second node.

[0422] In S833, after receiving the first RRC reconfiguration complete message and parsing the first RRC reconfiguration complete message, the target access network device may determine that the handover of the first node is completed, and the target access network device may send the fifth indication information to the second node, to trigger S835.

[0423] S835: The second node sends the fifth indication information to the first node.

[0424] In an implementation, S834 is performed. In response to the fourth indication information, the second node sends the fifth indication information to the first node.

[0425] In another implementation, S834 is omitted. After S833, the second node sends the fourth indication information to the first node.

[0426] S836: The first node stops the timer.

[0427] After receiving the fifth indication information, the first node stops the timer based on the fifth indication information.

[0428] S837: The target access network device and a core network complete path switching.

[0429] Optionally, the core network changes a node from the source access network device to the target access network device, where the node is on a user plane path for transmitting a service of the third node and the descendant node of the third node.

[0430] S838: The target access network device sends a UE context release message to the source access network device.

[0431] Optionally, if the CU of the source access network device is in the CP-UP separation architecture, the CP of the CU of the source access network device may receive the UE context release message from the target access network device, and the CP of the CU of the source access network device may send a bearer context release command to the UP of the CU of the source access network device.

[0432] S839 and S840 describe a UE context release process of an F1 interface between the source access network device and the source parent node.

[0433] S839: The source access network device sends a UE context release command message to the source parent node.

[0434] S840: The source parent node sends a UE context release complete message to the source access network device.

[0435] S841: Release a BAP routing configuration on a path between the source access network device and the third node.

[0436] Nodes on the path between the source access network device and the third node include the source access network device and another node, for example, the source parent node, between the source access network device and the third node. The source access network device in this step may be a DU part of the source access network device.

[0437] Optionally, S841 may include: The source access network device sends, to the node on the path, an F1AP message for releasing a BAP layer configuration related to the third node, the first node, or the second node. After receiving the F1AP message, the node on the path releases the corresponding BAP layer configuration of the node.

[0438] Optionally, in FIG. 7 and FIG. 8A, FIG. 8B, and FIG. 8C, an action performed by an access network device (for example, the source access network device or the target access network device) may be performed by a CU or a CP of the CU of the access network device.

[0439] Optionally, the first node in FIG. 8A, FIG. 8B, and FIG. 8C may be the child node in FIG. 7, and the second node may be the parent node in FIG. 7. Mutual reference may be made to content in S804 to S807 and content in S701 to S703, mutual reference may be made to S809 and S704, mutual reference may be made to S833 and S705, and mutual reference may be made to S834 to S836 and S706 to S708. Mutual reference may be made to content of the second RRC reconfiguration message in S810 and S811 and content of the third message in FIG. 7.

[0440] Optionally, the second node in FIG. 8A, FIG. 8B, and FIG. 8C may be the child node in FIG. 7, and the third node in FIG. 8A, FIG. 8B, and FIG. 8C may be the parent node in FIG. 7. Mutual reference may be made to content in S804 and S810 to S812 and content in S701 to S703, mutual reference may be made to S814 and S704, mutual reference may be made to S828 and S705, and mutual reference may be made to S829 to S831 and S706 to S708. Mutual reference may be made to content of the third RRC reconfiguration message in S815 and S816 and content of the third message in FIG. 7.

[0441] Optionally, in FIG. 8A, FIG. 8B, and FIG. 8C, methods of the first node, the second node, and the third node may all be separately implemented. For example, the method of the third node may be separately implemented.

[0442] Optionally, in FIG. 8A, FIG. 8B, and FIG. 8C, the methods of the first node, the second node, and the third node may be implemented in a combination manner. For example, the combination may include the first node and the second node, the second node and the third node, the first node and the third node, or the first node, the second node, and the third node.

[0443] Optionally, one or more steps in FIG. 8A, FIG. 8B, and FIG. 8C may be combined in different manners.

[0444] The method in FIG. 8A, FIG. 8B, and FIG. 8C may include only S804, S805, and S806. The first node may receive the first RRC reconfiguration information from the target access network device via the second node, where the first RRC reconfiguration message indicates not to perform random access. Optionally, the C-RNTI of the first node before and after the handover may remain unchanged. For details, refer to content in S804, S805, and S806. Optionally, one or more other steps in FIG. 8A, FIG. 8B, and FIG. 8C may be further included.

[0445] The first RRC reconfiguration message indicates not to perform random access, so that node handover time can be reduced, a handover delay can be reduced, and signaling overheads can be saved, thereby avoiding frequent conflicts caused by limited resources used when a large quantity of nodes initiate random access or avoiding excessively long time for the nodes to wait for random access resources. In addition, the C-RNTI remains unchanged, so that a large amount of reconfiguration work can be avoided, and power consumption of the first node can be saved.

[0446] The method in FIG. 8A, FIG. 8B, and FIG. 8C may include only S805, S806, S810, and S811, and S810 may be performed after S805 and/or S806. For details, refer to content in FIG. 8A, FIG. 8B, and FIG. 8C. Optionally, the first RRC reconfiguration message and/or the second RRC reconfiguration message may indicate to perform or not to perform random access. This is not limited in the embodiments. Optionally, one or more other steps in FIG. 8A, FIG. 8B, and FIG. 8C may be further included.

[0447] S810 may occur after S805 and/or S806, so that it can be ensured that a child node sends an RRC reconfiguration message to a parent node only after receiving the RRC reconfiguration message, thereby avoiding a case in which the parent node cannot provide a service for the child node because the parent node is handed over in advance.

[0448] The method in FIG. 8A, FIG. 8B, and FIG. 8C may include only S803, in other words, the source access network device sends the handover request message to the target access network device, where the handover request message includes a C-RNTI of one or more nodes, a cell identifier of an accessed cell of the one or more nodes, and/or hierarchical information of the one or more nodes in a network topology. Optionally, the target access network device determines information about duration of a timer based on the hierarchical information, carries the information about the duration in an RRC reconfiguration message, and sends the RRC reconfiguration message to the one or more nodes. For details, refer to content in FIG. 8A, FIG. 8B, and FIG. 8C. Optionally, one or more other steps in FIG. 8A, FIG. 8B, and FIG. 8C may be further included.

[0449] It can be understood from FIG. 8A, FIG. 8B, and FIG. 8C that, in group handover, in a handover start phase, an RRC reconfiguration message is first sent to a farthest node (for example, the first node in FIG. 8A, FIG. 8B, and FIG. 8C) in a group, then an RRC reconfiguration message is sent to an upper-level node level by level, and finally an RRC reconfiguration message is sent to a migrating IAB node; and in a handover completion phase, an RRC reconfiguration complete message of the migrating IAB node is first sent to the target access network device, then an RRC reconfiguration complete message of a next level-node is sent level by level, and finally an RRC reconfiguration complete message of the farthest node is sent. Therefore, it may be understood that, in the group handover, a node with a larger hop quantity of a wireless backhaul link between the node and the migrating IAB node occupies longer time in a process from a handover start to handover completion.

[0450] If duration of a timer is set improperly, a node in the group handover may fail to be handed over due to timeout of the timer. After determining that the node fails to be handed over, the node initiates RRC reestablishment. However, initiating an RRC reestablishment process causes a delay, and causes unnecessary signaling overheads. In addition, after a child node initiates RRC reestablishment, if handover of a parent node is not completed, the parent node cannot provide a service for the child node. Consequently, RRC reestablishment of the child node may fail, and the child node enters an idle state and then re-accesses a network. However, a delay required for re-accessing the network is long, and user experience is seriously affected.

[0451] The source access network device sends hierarchical information to the target access network device, and the target access network device may properly determine duration of a timer based on a hierarchy of a node. For example, a node with a larger hop quantity of a wireless backhaul link between the node and the migrating IAB node has larger duration of a timer, and a node with a smaller hop quantity of a wireless backhaul link between the node and the migrating IAB node has smaller duration of a timer. This avoids consequences caused by improper setting of the duration of the timer, reduces a handover delay, and reduces signaling overheads.

[0452] Optionally, as shown in FIG. 8A, FIG. 8B, and FIG. 8C, during group handover, each node may receive a reconfiguration message of the node. Some information in the reconfiguration message of each node may be the same. In a solution, the target access network device may send the same information in a broadcast manner.

[0453] For example, the target access network device broadcasts a group reconfiguration message, where the group reconfiguration message includes a common configuration of a primary serving cell, a random access-free indication, and/or information about duration of a timer.

[0454] Optionally, the group reconfiguration message may be referred to as a group handover command

[0455] Optionally, the information about the duration of the timer may indicate the duration of the basic timer in S804. Then, the target access network device may send a message to each node in a group, where the message includes a scale factor. The node in the group obtains duration of a timer based on the duration of the basic timer and the scale factor.

[0456] Optionally, the target access network device may further send a message to each node in the group. The message includes different information of each node, for example, a PDCP layer configuration (for example, a security-related configuration) of each node.

[0457] The same information of each node is sent in a broadcast manner, so that air interface signaling overheads can be reduced. Particularly, in an IAB system, overheads caused by separately sending signaling to a plurality of nodes in the group can be avoided in the foregoing broadcast manner.

[0458] In FIG. 7 and FIG. 8A, FIG. 8B, and FIG. 8C, a relay system is used as an example for description. It should be noted that the method in the embodiments is also applicable to a single-air-interface scenario in which a terminal directly accesses an access network device, for example, a scenario in which the terminal 130 directly accesses the access network device 150 in FIG. 1 for communication.

[0459] FIG. 9 shows another communication method according to an embodiment. The communication method may be applied to the scenario in which the terminal directly accesses the access network device. The following provides descriptions with reference to FIG. 9. The access network device 150 may use the CU-DU separation architecture shown in FIG. 2.

[0460] Optionally, the terminal 130 may be handed over from the access network device 150 to another access network device (not shown in FIG. 1). The access network device 150 is referred to as a source access network device below, and the another access network device is referred to as a target access network device. The target access network device may use the CU-DU separation architecture shown in FIG. 2. A CU of the target access network device may be referred to as a target CU, and a DU of the target access network device may be referred to as a target DU.

[0461] S901: The target CU sends a first message to the source access network device.

[0462] Optionally, the source access network device may use the CU-DU separation architecture, where a CU of the source access network device may be referred to as a source CU, and a DU of the source access network device may be referred to as a source DU. S901 may include: The target CU sends the first message to the source CU.

[0463] S902: The source access network device sends the first message to the terminal.

[0464] Optionally, if the source access network device may use the CU-DU separation architecture, S902 may include: The source CU sends the first message to the source DU, and the source DU sends the first message to the terminal.

[0465] S903: The terminal starts a timer.

[0466] S904: The terminal sends a second message to the target DU.

[0467] S905: The target DU sends the second message to the target CU.

[0468] For the first message and the second message in S901 to S905, refer to content of the first message and the second message in FIG. 7.

[0469] S906: The target CU sends first indication information to the target DU.

[0470] S907: The target DU sends second indication information to the terminal.

[0471] For the first indication information and the second indication information in S906 and S907, refer to content of the first indication information and the second indication information in FIG. 7.

[0472] S908: The terminal stops the timer.

[0473] The target DU in FIG. 9 may perform an action of the parent node in FIG. 7, the target CU in FIG. 9 may perform an action of the access network device in FIG. 7, and the terminal in FIG. 9 may perform an action of the child node in FIG. 7. For other content in FIG. 9, refer to FIG. 7. Details are not described herein again.

[0474] With reference to FIG. 10 to FIG. 13, the following describes apparatuses provided in the embodiments. The apparatuses in FIG. 10 to FIG. 13 may complete the methods in FIG. 7 to FIG. 9. Mutual reference may be made to content of the apparatuses and content of the methods.

[0475] FIG. 10 is a schematic diagram of a structure of a terminal according to an embodiment. The terminal may implement functions of the terminal in the foregoing method embodiments. For ease of description, FIG. 10 shows main components of the terminal. As shown in FIG. 10,

[0476] the terminal includes at least one processor 611, at least one transceiver 612, and at least one memory 613. The processor 611, the memory 613, and the transceiver 612 are connected. Optionally, the terminal may further include an output device 614, an input device 615, and one or more antennas 616. The antenna 616 is connected to the transceiver 612, and the output device 614 and the input device 615 are connected to the processor 611.

[0477] The processor 611 may be configured to: process a communication protocol and communication data, control the entire terminal, execute a software program, and process data of the software program.

[0478] In an optional implementation, the terminal device may include a baseband processor and a central processing unit. The baseband processor may be configured to process a communication protocol and communication data. The central processing unit may be configured to control the entire terminal device, execute a software program, and process data of the software program.

[0479] Functions of the baseband processor and the central processing unit may be integrated into the processor in FIG. 10. A person skilled in the art may understand that the baseband processor and the central processing unit each may be an independent processor and may be interconnected by using a technology such as a bus. A person skilled in the art may understand that the terminal device may include a plurality of baseband processors to adapt to different network standards, the terminal device may include a plurality of central processing units to improve a processing capability of the terminal device, and the components of the terminal device may be connected through various buses. The baseband processor may also be expressed as a baseband processing circuit or a baseband processing chip. The central processing unit may alternatively be expressed as a central processing circuit or a central processing chip. A function of processing the communication protocol and the communication data may be embedded in the processor, or may be stored in the memory in a form of the software program. The processor executes the software program to implement a baseband processing function.

[0480] The memory 613 may be configured to store the software program and the data. The memory 613 may exist independently, and is connected to the processor 611. Optionally, the memory 613 and the processor 611 may be integrated together, for example, integrated in a chip, that is, the memory 613 may be an on-chip memory; or the memory 613 is an independent storage element. This is not limited in the embodiments. The memory 613 can store program code for executing the embodiments and the processor 611 controls execution of the program code. Various types of executed computer program code may also be considered as drivers of the processor 611.

[0481] The transceiver 612 may be configured to: perform conversion between a baseband signal and a radio frequency signal and process the radio frequency signal. The transceiver 612 may be connected to the antenna 616. The transceiver 612 includes a transmitter (Tx) and a receiver (Rx). The one or more antennas 616 may receive a radio frequency signal. The receiver Rx in the transceiver 612 is configured to: receive the radio frequency signal from the antenna, convert the radio frequency signal into a digital baseband signal or a digital intermediate frequency signal, and provide the digital baseband signal or the digital intermediate frequency signal for the processor 611, so that the processor 611 further processes the digital baseband signal or the digital intermediate frequency signal, for example, performs demodulation processing and decoding processing. In addition, the transmitter Tx of the transceiver 612 is configured to: receive a modulated digital baseband signal or digital intermediate frequency signal from the processor 611, convert the modulated digital baseband signal or digital intermediate frequency signal into a radio frequency signal, and send the radio frequency signal through the one or more antennas 616. The receiver Rx may selectively perform one or more levels of downmixing processing and analog-to-digital conversion processing on the radio frequency signal to obtain the digital baseband signal or the digital intermediate frequency signal. A sequence of the downmixing processing and the analog-to-digital conversion processing is adjustable. The transmitter Tx may selectively perform one or more levels of upmixing processing and digital-to-analog conversion processing on the modulated digital baseband signal or digital intermediate frequency signal to obtain the radio frequency signal. A sequence of the upmixing processing and the digital-to-analog conversion processing is adjustable. The digital baseband signal and the digital intermediate frequency signal may be collectively referred to as a digital signal. Optionally, the transmitter Tx and the receiver Rx may be implemented by different physical structures/circuits, or may be implemented by a same physical structure/circuit, that is, the transmitter Tx and the receiver Rx may be integrated together.

[0482] The transceiver may also be referred to as a transceiver unit, a transceiver machine, a transceiver apparatus, or the like. Optionally, a component that is configured to implement a receiving function and that is in the transceiver unit may be considered as a receiving unit, and a component that is configured to implement a sending function and that is in the transceiver unit may be considered as a sending unit. That is, the transceiver unit includes the receiving unit and the sending unit. The receiving unit may also be referred to as a receiver, an input port, a receiving circuit, or the like. The sending unit may be referred to as a transmitter, a transmitting circuit, or the like. Alternatively, the Tx, the Rx, and the antenna may be combined into the transceiver.

[0483] The output device 614 displays information in a plurality of manners. For example, the output device 614 may be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. The input device 615 may receive an input of a user in a plurality of manners. For example, the input device 615 may be a mouse, a keyboard, a touchscreen device, or a sensor device.

[0484] FIG. 11 is a schematic diagram of a structure of an access network device according to an embodiment. For example, FIG. 11 may be a schematic diagram of a structure of an access network device that may use a CU-DU separation architecture. As shown in FIG. 11, a base station may be applied to the system shown in FIG. 1, FIG. 2, or FIG. 3, to implement a function of the access network device (the source access network device and/or the target access network device) in the foregoing method embodiments.

[0485] The access network device may include one or more DUs 1101 and one or more CUs 1102. The DU 1101 may include at least one antenna 11011, at least one radio frequency unit 11012, at least one processor 11013, and at least one memory 11014. The DU 1101 may be configured to: send and receive a radio frequency signal, perform conversion between a radio frequency signal and a baseband signal, and perform partial baseband processing. The CU 1102 may include at least one processor 11022 and at least one memory 11021. The CU 1102 and the DU 1101 may communicate with each other through an interface. A control plane interface may be F1-C, and a user plane interface may be F1-U.

[0486] The CU 1102 may be configured to: perform baseband processing, control the base station, and the like. The DU 1101 and the CU 1102 may be physically disposed together, or may be physically disposed separately, that is, a distributed base station. The CU 1102 is a control center of the base station, may also be referred to as a processing unit, and may be configured to complete a baseband processing function. For example, the CU 1102 may be configured to control the base station to perform an operation procedure related to the network device in the foregoing method embodiments.

[0487] Baseband processing on the CU and the DU may be divided based on a protocol layer of a wireless network. For details, refer to the foregoing content.

[0488] In an instance, the CU 1102 may include one or more boards, and a plurality of boards may jointly support a radio access network (for example, a 5G network) of a single access standard, or may separately support radio access networks (for example, an LTE network, a 5G network, or another access network) of different access standards. The memory 11021 and the processor 11022 may serve one or more boards. In other words, a memory and a processor may be disposed on each board. Alternatively, a plurality of boards may share a same memory and a same processor. In addition, a necessary circuit may further be disposed on each board. The DU 1101 may include one or more boards, and a plurality of boards may jointly support a radio access network (for example, a 5G network) of a single access standard, or may separately support radio access networks (for example, an LTE network, a 5G network, or another access network) of different access standards. The memory 11014 and the processor 11013 may serve one or more boards. In other words, a memory and a processor may be disposed on each board. Alternatively, a plurality of boards may share a same memory and a same processor. In addition, a necessary circuit may further be disposed on each board.

[0489] Optionally, the CU 1102 may perform transmission with a child node of the access network device via the DU 1101. The CU 1102 may be connected to another access network device through an interface. The CU 1102 may receive data and/or a message from the another access network device (for example, a CU of the another access network device) through the interface, or the CU 1102 may send data and/or a message to the another access network device through the interface.

[0490] FIG. 12 is a schematic diagram of a structure of a communication apparatus according to an embodiment. The communication apparatus may be a relay node, and may implement a function of the relay node (for example, an IAB node) in the foregoing method embodiments. Alternatively, the communication apparatus may be an access network device, and may implement a function of the source access network device or the target access network device in the foregoing method embodiments. For ease of description, FIG. 12 shows main components of a communication apparatus. As shown in FIG. 12,

[0491] the communication apparatus includes at least one processor 711, at least one memory 712, at least one transceiver 713, at least one network interface 714, and one or more antennas 715. The processor 711, the memory 712, the transceiver 713, and the network interface 714 are connected to each other, for example, through a bus. In the embodiments, the connection may include various types of interfaces, transmission lines, buses, or the like. This is not limited in embodiments. The antennas 715 are connected to the transceiver 713. The network interface 714 is configured to enable the communication apparatus to communicate with another network device through a communication link.

[0492] For the transceiver 713, the memory 712, and the antennas 716, refer to related descriptions in FIG. 10, to implement similar functions.

[0493] FIG. 13 is a schematic diagram of a structure of a communication apparatus according to an embodiment. The communication apparatus may perform the method described in the foregoing method embodiments. For details, refer to the descriptions in the foregoing method embodiments. The communication apparatus may be used in a communication device, a circuit, a hardware component, or a chip. For example, the communication apparatus may be a terminal, a chip in a terminal, a donor node (including a source donor node or a target donor node), or a chip in a donor node (including a source donor node or a target donor node).

[0494] The communication apparatus 1300 includes a processing unit 1301 and a communication unit 1302. Optionally, the communication apparatus 1300 further includes a storage unit 1303.

[0495] The processing unit 1301 may be an apparatus having a processing function and may include one or more processors. The processor may be a general-purpose processor, a dedicated processor, or the like. The processor may be a baseband processor or a central processing unit. The baseband processor may be configured to process a communication protocol and communication data, and the central processing unit may be configured to: control an apparatus (such as a donor node, a terminal, or a chip), execute a software program, and process data of the software program.

[0496] The communication unit 1302 may be an apparatus for inputting (receiving) or outputting (sending) a signal and may be configured to perform signal transmission with another network device or another component in a device.

[0497] The storage unit 1303 may be an apparatus having a storage function, and may include one or more memories.

[0498] Optionally, the processing unit 1301, the communication unit 1302, and the storage unit 1303 are connected through a communication bus.

[0499] Optionally, the storage unit 1303 may exist independently, and is connected to the processing unit 1301 through the communication bus. The storage unit 1303 may alternatively be integrated into the processing unit 1301.

[0500] Optionally, the communication apparatus 1300 may be a chip in the terminal or the donor node in the embodiments. The communication unit 1302 may be an input/output interface, a pin, a circuit, or the like. The storage unit 1303 may be a register, a cache, a RAM, or the like, and the storage unit 1303 may be integrated into the processing unit 1301. The storage unit 1303 may be a ROM or another type of static storage device that can store static information and instructions. The storage unit 1303 may be independent of the processing unit 1301. Optionally, with development of wireless communication technologies, the transceiver may be integrated into the communication apparatus 1300. For example, the transceiver 612 shown in FIG. 10 is integrated into the communication unit 1302.

[0501] The processing unit 1301 may include instructions, and the instructions may be run on the processor, so that the communication apparatus 1300 performs the method of the terminal or the donor node in the foregoing embodiments.

[0502] The storage unit 1303 may store instructions, and the instructions may be run on the processing unit 1301, so that the communication apparatus 1300 performs the method of the terminal or the donor node in the foregoing embodiments. Optionally, the storage unit 1303 may further store data. Optionally, the processing unit 1301 may also store instructions and/or data.

[0503] The communication apparatus 1300 may be the terminal in the embodiments. FIG. 10 may be a schematic diagram of the terminal. Optionally, the communication unit 1302 of the apparatus 1300 may include an antenna and a transceiver of the terminal, for example, the antenna and the transceiver in FIG. 10. Optionally, the communication unit 1302 may further include an output device and an input device, for example, the output device and the input device in FIG. 10.

[0504] When the communication apparatus 1300 may be the terminal in the embodiments or the chip of the terminal, the communication apparatus 1300 may implement functions implemented by the terminal in the foregoing method embodiments.

[0505] When the communication apparatus 1300 may be the relay node in embodiments or a chip of the relay node, the communication apparatus 1300 may implement functions implemented by the relay node in the foregoing method embodiments.

[0506] When the communication apparatus 1300 may be a chip of the access network device (for example, the source access network device or the target access network device) in the embodiments, the communication apparatus 1300 may implement a function of the donor node in the foregoing method embodiments.

[0507] The foregoing describes the method flowcharts in the embodiments. It should be understood that the terminal may have a functional unit corresponding to a method or step of the terminal, the relay node may have a functional unit corresponding to a method or step of the relay node, a source donor node (for example, a CU and/or a DU) may have a functional unit corresponding to a method or step of the source donor node (for example, the CU and/or the DU), the target donor node (for example, a CU and/or a DU) may have a functional unit corresponding to a method or a step of the target donor node (for example, the CU and/or the DU), and a CU of the source donor node may have a functional unit corresponding to a method or a step of the CU of the source donor node. In addition, another node in the relay system may have a functional unit corresponding to the another node. One or more of the foregoing modules or units may be implemented by using software, hardware, or a combination thereof. When any one of the foregoing modules or units is implemented by using software, the software exists in a form of computer program instructions, and is stored in a memory. A processor may be configured to execute the program instructions to implement the foregoing method procedure.

[0508] The processor may include, but is not limited to, at least one of the following computing devices that run software: a central processing unit (CPU), a microprocessor, a digital signal processor, a microcontroller unit (MCU), or an artificial intelligence processor. Each computing device may include one or more cores configured to perform an operation or processing by executing software instructions. The processor may be an independent semiconductor chip, or may be integrated with another circuit into a semiconductor chip. For example, the processor and another circuit (such as a codec circuit, a hardware acceleration circuit, or various buses and interface circuits) may form a system-on-a-chip (SoC). Alternatively, the processor may be integrated into an application-specific integrated circuit (ASIC) as a built-in processor of the ASIC. The ASIC integrated with the processor may be independently packaged or may be packaged with another circuit. The processor includes a core for executing software instructions to perform an operation or processing, and may further include a necessary hardware accelerator, for example, a field programmable gate array (FPGA), a programmable logic device (PLD), or a logic circuit that implements a special-purpose logic operation.

[0509] The memory in the embodiments may include at least one of the following types: a read-only memory (ROM) or another type of static storage device that can store static information and instructions, a random access memory (RAM) or another type of dynamic storage device that can store information and instructions, or may be an electrically erasable programmable read-only memory (EEPROM). In some scenarios, the memory may alternatively be a compact disc read-only memory (CD-ROM) or another compact disc storage, an optical disc storage (including a compact optical disc, a laser disc, an optical disc, a digital versatile disc, a Blu-ray disc, or the like), a magnetic disk storage medium or another magnetic storage device, or any other medium that can be used to carry or store expected program code in a form of instructions or a data structure and that can be accessed by a computer. However, the memory is not limited thereto.

[0510] In addition to a data bus, the bus may further include a power bus, a control bus, a status signal bus, and the like. However, for clear description, various types of buses in the figures are marked as the bus.

[0511] In an implementation process, steps in the foregoing methods can be implemented by using a hardware integrated logical circuit in the processor, or by using instructions in a form of software. The steps of the methods with reference to the embodiments may be directly performed by a hardware processor, or may be performed by using a combination of hardware in the processor and a software module. The software module may be located in a mature storage medium in the field, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, or a register. The storage medium is located in the memory, and the processor reads information in the memory and completes the steps in the foregoing methods in combination with hardware of the processor. To avoid repetition, details are not described herein again.

[0512] According to the methods provided in the embodiments, an embodiment may further provide a system, including the foregoing apparatuses and one or more network devices.

[0513] It should be further understood that first, second, third, fourth, and various numbers are differentiated merely for ease of description, but are not used to limit the scope of the embodiments. The numbers may be replaced with other numbers.

[0514] It should be understood that the term “and/or” describes an association relationship between associated objects and represents that three relationships may exist. For example, A and/or B may represent the following three cases: only A exists, both A and B exist, and only B exists. In addition, the character “/” generally indicates an “or” relationship between the associated objects.

[0515] It should be understood that sequence numbers of the foregoing processes do not mean execution sequences in the embodiments. The execution sequences of the processes should be determined based on functions and internal logic of the processes and should not constitute any limitation on implementation processes of the embodiments.

[0516] A person of ordinary skill in the art may be aware that, in combination with illustrative logical blocks described in embodiments and steps may be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether the functions are performed by hardware or software depends on particular applications. A person skilled in the art may use different methods to implement the described functions for each particular application, but it should not be considered that the implementation goes beyond the scope of the embodiments.

[0517] In the several embodiments, it should be understood that the system, apparatuses, and methods may be implemented in other manners. For example, the described apparatus embodiments are merely examples. For example, division into the units is merely logical function division and may be other division in an actual implementation. For example, a plurality of units or components may be combined or integrated into another system, or some features may be ignored or not performed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections may be implemented through some interfaces. The indirect couplings or communication connections between the apparatuses or units may be implemented in electronic, mechanical, or other forms.

[0518] All or some of the foregoing embodiments may be implemented by using software, hardware, firmware, or any combination thereof. When software is used to implement embodiments, all or a part of embodiments may be implemented in a form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the procedure or functions according to the embodiments are all or partially generated. The computer may be a general-purpose computer, a dedicated computer, a computer network, or other programmable apparatuses. The computer instructions may be stored in a non-transitory computer-readable storage medium or may be transmitted from a non-transitory computer-readable storage medium to another non-transitory computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center in a wired (for example, a coaxial cable, an optical fiber, or a digital subscriber line (DSL)) or wireless (for example, infrared, radio, or microwave) manner. The non-transitory computer-readable storage medium may be any usable medium accessible by the computer, or a data storage device, for example, a server or a data center, integrating one or more usable media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a digital versatile disc (DVD)), a semiconductor medium (for example, a solid-state drive), or the like.

[0519] The foregoing descriptions are merely implementations, but are not intended to limit the scope of the embodiments. Any variation or replacement readily figured out by a person skilled in the art shall fall within the scope of the embodiments.