IAB node device, IAB donor device and topology regression method

The method for managing route migration configurations in IAB nodes and donor devices during topology regression in 5G wireless self-backhaul systems addresses data loss and delays by maintaining F1 connections and updating addresses, enhancing network stability.

JP2024545537AActive Publication Date: 2024-12-091FINITY INC
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2024539883
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2022-01-04
Publication Date
2024-12-09
Estimated Expiration
2042-01-04

AI Technical Summary

Technical Problem

In the context of 5G wireless self-backhaul systems with IAB nodes, topology regression can result in uplink data being dropped due to IP address filtering, leading to transmission delays and service interruptions when migrating nodes change donor-CUs.

Method used

A method and device for IAB nodes and donor devices that manage route migration configurations to maintain F1 connections during topology regression, ensuring seamless transition of uplink services across different donor-CUs, including updating routing and IP addresses to avoid data loss.

Benefits of technology

This approach reduces the likelihood of uplink data loss, minimizes transmission delays, and decreases service interruption times during topology regression in IAB networks.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024545537000001_ABST
    Figure 2024545537000001_ABST
Patent Text Reader

Abstract

In the embodiment of the present application, an IAB node device, an IAB donor device and a topology regression method are provided, in which the transmission path of an uplink service of an IAB node transitions from a first donor centralized unit to a second donor centralized unit, and then transitions from the second donor centralized unit to the first donor centralized unit, the method includes: an IAB node or a child node receives a path transition setting of uplink data sent by a network device; and an IAB node or a child node applies the path transition setting, and an IAB-DU of the IAB node maintains an F1 connection with a first donor-CU.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to the technical field of communications. [Background technology]

[0002] The deployment of future seamless cellular networks requires the deployment of highly flexible and ultra-high density new radio (NR) cells, and ultra-high density networks are one of the goals of 5G. The deployment of NR networks that do not require wired backhaul is very important for ultra-high density networks that realize 5G. As 5G mmWave reduces cell coverage, wireless self-backhaul systems require multi-hop to meet the deployment needs. Compared with LTE, 5G's high bandwidth, massive multiple-input multiple-output (MIMO) and beam systems make it easier to develop wireless self-backhaul systems for ultra-high density NR cells. To develop such a multi-hop system with wireless self-backhaul, 3GPP has started research and standardization of the IAB (Integrated access and backhaul) project in Rel-16.

[0003] Figure 1 is a diagram showing an IAB system. As shown in Figure 1, in the IAB system, access and backhaul adopt the NR Uu air interface for wireless transmission, a relay node (relay node) simultaneously supports the functions of access and backhaul, the relay node multiplexes the access link and the backhaul link in the time domain, frequency domain or spatial domain, and the access link and the backhaul link can use the same or different frequency bands.

[0004] In the IAB network architecture, the relay node refers to the IAB-node, which supports both access and backhaul functions. The last one-hop access node on the network side is called the IAB-donor, which supports gNB functions and access for the IAB-node. All UE data can be backhauled to the IAB-donor via the IAB-node by single-hop or multi-hop.

[0005] The function of the IAB-node is divided into two parts, one part is the gNB-DU function, called IAB-DU (distributed unit), and the other part is the UE function, called IAB-MT (mobile terminal). The IAB-DU realizes the function of the network side device, is connected to the downstream child IAB-node (child IAB node or abbreviated as child node), provides NR air interface access for the UE and the downstream child IAB-node, and establishes an F1 connection with the IAB donor-CU (donor centralized unit). The IAB-MT realizes the function of some terminal device, is connected to the upstream parent IAB-node (parent IAB node or abbreviated as parent node) or IAB donor-DU, and the IAB-MT includes the functions of the physical layer, layer 2, RRC (Radio Resource Control) and NAS (Non-Access Stratum), and is indirectly connected to the IAB Donor-CU and the core network (Core Network, CN).

[0006] In the IAB system, an IAB-node can access the network through a Standalone (SA) mode or an E-UTRA-NR Dual Connectivity (EN-DC) mode. Figure 2 shows the IAB architecture in the SA mode. Figure 3 shows the IAB architecture in the EN-DC mode.

[0007] Figure 4 shows one IAB-node, a parent IAB-node, and a child IAB-node. As shown in Figure 4, the IAB-DU of the IAB node is connected to the IAB-MT of the child node as the network side, and the IAB-MT of the IAB node is connected to the IAB-DU of the parent node as the terminal side.

[0008] Figure 5 shows the F1 user plane (F1-U) protocol stack between the IAB-DU and the IAB donor-CU. Figure 6 shows the F1 control plane (F1-C) protocol stack between the IAB-DU and the IAB donor-CU. As shown in Figures 5 and 6, F1-U and F1-C are established on top of the transport (IP) layer between the IAB-DU and the IAB donor-CU, and two hop wireless backhaul and one hop wired backhaul are shown in Figures 5 and 6.

[0009] In the backhaul link, the transport (IP) layer is carried to the backhaul adaptation protocol (BAP) sublayer, the BAP entity in the IAB-node realizes the routing function of the IAB system, and the IAB donor-CU provides the routing table. The BAP PDU (Protocol Data Unit) is transmitted on the RLC (Radio Link Control) channel of the backhaul link, and multiple RLC channels of the backhaul link may be configured by the IAB-donor to carry services (traffic) with different priorities and QoS (Quality of Service), and the BAP entity maps the BAP PDU to different backhaul RLC channels.

[0010] It should be noted that the introduction of the above background art is intended to clearly and completely explain the technical solutions of the present invention, and to facilitate understanding thereof by those skilled in the art, and these technical solutions are described in the background art of the present invention, and therefore should not be construed as being known to those skilled in the art. Summary of the Invention [Problem to be solved by the invention]

[0011] The inventor has found that, after a migrating node migrates from the network topology domain of a source dornor-CU to the network topology domain of a target dornor-CU, it may migrate from the network topology domain of the target dornor-CU to the network topology domain of the source dornor-CU, which may be called topology revoking. Because the migrating node may change the donor-DU after topology revoking, the uplink data of the migrating node may not be sent to the donor-CU, and if the donor-DU after topology revoking has an IP address filtering function, it may drop the uplink data including the IP address assigned by the donor-DU before topology revoking, which may cause a relatively long transmission delay and service interruption time.

[0012] To solve at least one of the above problems, embodiments of the present application provide an IAB node device, an IAB donor device, and a topology regression method. [Means for solving the problem]

[0013] According to one aspect of an embodiment of the present application, a topology regression method is provided, in which a transmission path of an uplink service of an IAB node is migrated from a first donor centralization unit (donor-CU) to a second donor centralization unit, and then migrated from the second donor centralization unit to the first donor centralization unit, the method comprising: The IAB node or child node receives a route transition configuration of uplink data transmitted by a network device; and the IAB node or a child node applies the path transition configuration; Wherein, the IAB-DU of the IAB node maintains an F1 connection with the first donor-CU.

[0014] According to another aspect of the embodiment of the present application, an IAB node device is provided, and a transmission path of an uplink service of the IAB node device is migrated from a first donor centralized unit to a second donor centralized unit, and then the transmission path of the uplink service of the IAB node device is migrated from the second donor centralized unit to the first donor centralized unit, and the IAB node device includes: A receiving unit for receiving a route transition setting of uplink data transmitted by the network device; and a processor for applying the path transition configuration; Wherein, the IAB-DU of the IAB node maintains an F1 connection with the first donor concentration unit.

[0015] According to another aspect of the embodiment of the present application, a topology regression method is provided, in which a transmission path of an uplink service of an IAB node is migrated from a first donor centralization unit (donor-CU) to a second donor centralization unit, and then migrated from the second donor centralization unit to the first donor centralization unit, the method comprising: The first donor-CU receives a topology regression request sent by the second donor-CU; and The first donor-CU sends a route transition configuration of uplink data; Wherein, the IAB-DU of the IAB node maintains an F1 connection with the first donor-CU.

[0016] According to another aspect of the embodiment of the present application, an IAB donor device is provided, and after a transmission path of an uplink service of an IAB node is migrated from a first donor centralized unit to a second donor centralized unit, the transmission path is migrated from the second donor centralized unit to the first donor centralized unit, and the device includes: a receiving unit for receiving a topology regression request transmitted by the second donor concentrating unit; and A transmitter for transmitting a route transition configuration of uplink data, Wherein, the IAB-DU of the IAB node maintains an F1 connection with the first donor concentration unit.

[0017] According to another aspect of an embodiment of the present application, an IAB system is provided, the IAB system including an IAB donor device and an IAB node device, After the transmission path of the uplink service of the IAB node device is shifted from a first donor centralized unit to a second donor centralized unit, the transmission path is shifted from the second donor centralized unit to the first donor centralized unit; Wherein, the IAB node device receives a route transition configuration for uplink data sent by a network device; and applies the route transition configuration; Wherein, the IAB-DU of the IAB node maintains an F1 connection with the first donor concentration unit. Effect of the Invention

[0018] The advantageous effects of the embodiment of the present invention are at least as follows: an IAB node or a child node receives a path transition configuration for uplink data sent by a network device; and the IAB node or the child node applies the path transition configuration, in which an IAB-DU of the IAB node maintains an F1 connection with the first donor-CU, thereby reducing or avoiding the problem of uplink data being dropped, reducing transmission delay, and shortening service (traffic) interruption time.

[0019] With reference to the following description and drawings, specific embodiments of the present invention are disclosed in detail and show the manner in which the principles of the present invention may be employed. However, the scope of the present invention is not limited thereto. Within the scope of the appended claims, the embodiments of the present invention may include various changes, modifications, and alternatives.

[0020] Additionally, features described and / or illustrated in one embodiment may be used in the same or similar manner in one or more other embodiments, may be combined with features in the other embodiments, or may be substituted for features in the other embodiments.

[0021] It should be noted that terms such as "comprise / have" when used in this specification refer to the presence of a feature, element, step, or assembly, but do not exclude the presence or addition of one or more other features, elements, steps, or assemblies. [Brief description of the drawings]

[0022] Elements and features described in one drawing or one embodiment of the invention may be combined with elements and features shown in one or more other drawings or embodiments, and in the drawings, like reference numerals are used to indicate corresponding parts in the several drawings and to indicate corresponding parts used in several embodiments.

[0023] The included drawings are used to provide a further understanding of the embodiments of the present invention, and these drawings constitute a part of this specification, illustrate the embodiments of the present invention, and together with the written description, are used to explain the principles of the present invention. Also, it is obvious that the drawings described below are only for illustrating some embodiments of the present invention, and a person skilled in the art can derive other drawings based on these drawings without creative labor. [Figure 1] FIG. 1 illustrates an IAB system. [Diagram 2] A diagram showing the IAB architecture in SA mode. [Diagram 3] A diagram showing the IAB architecture in EN-DC mode. [Figure 4] FIG. 2 is a diagram showing a parent node (parent IAB-node) and a child node (child IAB-node). [Diagram 5] FIG. 2 illustrates the F1-U protocol stack of the IAB system. [Figure 6] FIG. 2 illustrates the F1-C protocol stack of the IAB system. [Figure 7] FIG. 1 illustrates routing in an IAB system. [Figure 8] FIG. 1 illustrates network topology adaptation. [Figure 9]FIG. 1 illustrates topology regression in an embodiment of the present application. [Figure 10] FIG. 2 is another diagram illustrating topology degeneracy in an embodiment of the present application. [Figure 11] FIG. 2 illustrates a topology regression method in an embodiment of the present application. [Figure 12] FIG. 1 illustrates an example of topology regression in an embodiment of the present application. [Figure 13] FIG. 13 illustrates another example of topology regression in an embodiment of the present application. [Figure 14] 1 is a flowchart of signaling topology regression in an embodiment of the present application; [Figure 15] 11 is another signaling flowchart of topology regression in an embodiment of the present application; [Figure 16] FIG. 2 is a diagram showing an IAB node device in an embodiment of the present application. [Figure 17] FIG. 1 shows an IAB donor device in an embodiment of the present application. [Figure 18] FIG. 1 shows an IAB device in an embodiment of the present application. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0024] The above and other features of the present invention will become apparent from the following detailed description and drawings, in which: Although the specification and drawings disclose specific embodiments of the present invention, they are merely illustrative of some of the embodiments that may employ the principles of the present invention, and it is to be understood that the present invention is not limited to the described embodiments, and that the present invention also includes all modifications, variations, and alternatives within the scope of the appended claims.

[0025] In embodiments of the present invention, the term "communications network" or "wireless communication network" may refer to a network conforming to any communication standard, such as New Radio (NR), Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0026] Additionally, communications between devices in a communications system may occur according to any stage of communications protocol, including, but not limited to, the following communications protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, 5G, New Radio (NR), and / or other conventional or future developed communications protocols.

[0027] In the embodiment of the present invention, the term "network device" refers to a device that connects a terminal device to a communication network and provides services to the terminal device in a communication system, for example. The network device may include, but is not limited to, an IAB-node, a base station (BS), an access point (AP), a transmission reception point (TRP), a broadcast transmitter, a mobile management entity (MME), a network gateway, a server, a radio network controller (RNC), a base station controller (BSC), etc.

[0028] Among them, the base station may include, but is not limited to, a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), a 5G base station (gNB), and may further include a Remote Radio Head (RRH), a Remote Radio Unit (RRU), a relay, or a low power node (e.g., femto, pico, etc.). The term "base station" may include some or all of the functions thereof, and each base station may provide communication coverage for a particular geographical area. The term "cell" may refer to a base station and / or the area it covers, depending on the context of the term.

[0029] In the embodiments of the present invention, the term "User Equipment" (UE) or "Terminal Equipment" (TE) refers to a device that accesses a communication network and receives services from the network, for example, via a network device. The User Equipment may be fixed or mobile, and may also be called a Mobile Station (MS), a terminal, a Subscriber Station (SS), an Access Terminal (AT), a station, etc.

[0030] Among these, user devices may include, but are not limited to, the following: cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, mobile devices, machine type communication devices, laptop computers, cordless telephones, smartphones, smart watches, digital cameras, etc.

[0031] Furthermore, in scenarios such as the Internet of Things (IoT), the user equipment may also be a monitoring or measuring device or equipment, including, but not limited to, a Machine Type Communication (MTC) terminal, an in-vehicle communication terminal, a Device to Device (D2D) terminal, a Machine to Machine (M2M) terminal, etc.

[0032] The routing function of the IAB system is realized by the BAP layer, and each IAB-node stores the BH routing configuration and the BH RLC channel mapping configuration. The BAP entity performs routing based on the routing configuration, the RLC channel mapping configuration, and the routing ID in the BAP layer data packet header. The Routing ID includes the destination BAP address and the route indicator.

[0033] The routing configuration includes a mapping relationship between the Routing ID and the BAP address of the next-hop node. The RLC channel mapping configuration includes a mapping relationship between the BAP address of the prior-hop node, the ingress link RLC channel ID, and the BAP address of the next-hop node and the egress link RLC channel ID.

[0034] Figure 7 is a diagram of IAB system routing. As shown in Figure 7, for each data packet, the BAP address of the next hop node can be found from the routing configuration according to the routing ID in the data packet header. The BAP address and the ingress link RLC channel ID of the preceding hop node (the node of the previous hop) are all known. In this way, after the BAP address of the next hop node is determined, the egress link RLC channel ID can be found according to the BAP address of the preceding hop node + the ingress link RLC channel ID + the BAP address of the next hop node through the RLC channel mapping configuration.

[0035] The IAB-donor DU stores the BH routing configuration and the Downlink Traffic to BH RLC Channel Mapping Configuration. The IAB-donor DU performs routing based on the routing configuration, the RLC channel mapping configuration, and the Routing ID in the BAP layer data packet header. The routing configuration includes the mapping relationship between the Routing ID and the address of the next hop node. The downlink RLC channel mapping configuration includes the mapping relationship between the target IP address, the DSCP (Differentiated Services Code Point), the address of the next hop node, and the egress link RLC channel ID.

[0036] For each downlink data packet arriving at the IAB-donor DU, the IAB-donor DU can find the address of the next hop node from the routing configuration according to the Routing ID in the data packet header. In this way, after determining the address of the next hop node, it can find the egress link RLC channel ID from the downlink RLC channel mapping configuration according to the IP address and DSCP of the data packet.

[0037] The above is an exemplary description of the routing of the IAB system, and the following describes the update of the network topology of the IAB system. Rel-16 NR has already standardized the topology adaptation process when an IAB-node moves under the same donor-CU.

[0038] Figure 8 illustrates intra-CU topology adaptation. When the IAB-node changes its parent node (from IAB-node 1 to IAB-node 2), the donor-CU configures path transition related settings for the IAB-node through an RRC reconfiguration message, allowing the IAB-node to perform F1 transmission path transition.

[0039] The route transition related configuration includes updating the default backhaul RLC channel for uplink F1-C, F1-U and non-F1 data, updating the default BAP routing ID, and updating the IP address for routing to Donor-DU. When the IAB-node accesses a new parent node, it starts applying the above route transition related configuration, and the child nodes of the IAB-node also perform route transition related configuration in the same manner.

[0040] 3GPP R17 supports topology adaptation when an IAB-node moves under a different donor-CU, and a migrating node can switch from a parent node serving a source donor-CU (also referred to as an F1-terminating CU or a first donor-CU) to a parent node serving a target donor-CU (also referred to as a non-F1-terminating CU or a second donor-CU).

[0041] After the transition node is switched from an F1-terminating CU to a non-F1-terminating CU, only the RRC connection of the IAB-MT is switched to the non-F1-terminating CU, the F1 interface still belongs to the F1-terminating CU, and the RRC connections of its serving child nodes and UEs still belong to the F1-terminating CU, at this time the transition node may be referred to as a boundary node.

[0042] The routing IDs of the boundary node's F1 and non-F1 data and the routing IDs of the child nodes' F1 and non-F1 data may be kept unchanged, but the boundary node needs to replace the original routing ID of the uplink traffic with a target routing ID, where the original routing ID belongs to the topological domain of the F1-terminating CU and its destination BAP address is the original donor-DU under the F1-terminating CU, and the replaced routing ID belongs to the topological domain of the non-F1-terminating CU and its destination BAP address is the target donor-DU under the non-F1-terminating CU.

[0043] In addition, a boundary node may switch from a non-F1-terminating CU to an F1-terminating CU, i.e., perform topology degradation. When a boundary node switches to an F1-terminating CU, the boundary node does not need to replace the original routing ID with the routing ID of the non-F1-terminating CU domain, but it needs to have routing configuration for the original routing ID and BH RLC channel mapping configuration from the boundary node to the parent node on the F1-terminating CU side.

[0044] The inventor has found that when a boundary node is switched to an F1-terminating CU, if a donor-DU of the F1-terminating CU has an IP address filtering function, uplink data carrying an IP address assigned by a donor-DU of a non-F1-terminating CU cannot be transmitted to the donor-CU, which may result in a relatively long transmission delay and service interruption.

[0045] Figure 9 is a diagram showing topology regression in an embodiment of the present application. As shown in Figure 9, the IAB node 3 is migrated from dornor-DU 1 of the source dornor-CU to dornor-DU 2 of the target dornor-CU, and then is regressed from dornor-DU 2 of the target dornor-CU to dornor-DU 1 of the source dornor-CU. If donor-DU 1 of the source dornor-CU has an IP address filtering function, the uplink data having an IP address assigned by donor-CU 2 of the target dornor-CU side cannot be sent to the source dornor-CU, because it may be dropped by donor-DU 2 of the source dornor-CU side. The dropped uplink data may be retransmitted by the UE, which may result in a relatively long transmission delay and service interruption time.

[0046] The inventors further discovered that when a boundary node is switched to an F1-terminating CU, if a donor-DU after the boundary node is switched is different from an original donor-DU, the uplink data generated by the transition node and child node based on the original routing ID cannot be transmitted to the F1-terminating CU, which may result in a relatively long transmission delay and service interruption.

[0047] FIG. 10 is another diagram showing topology regression in an embodiment of the present application. As shown in FIG. 10, IAB node 3 is migrated from dornor-DU 1 of source dornor-CU to dornor-DU 2 of target dornor-CU, and then regressed from dornor-DU 2 of target dornor-CU to dornor-DU 3 of source dornor-CU. Because donor-DU 3 after switching (regressing) is different from original donor-DU 1, uplink data generated by transition node and child node based on original routing ID cannot be sent to source dornor-CU. The reason is as follows: the uplink data generated based on original routing ID carries the BAP address of donor-DU 1, which is different from the BAP address of donor-DU 3, and these uplink data may be dropped by target donor-DU 3. The dropped uplink data may be retransmitted by UE, which may cause a relatively long transmission delay and service interruption time.

[0048] In view of at least one of the above problems or similar problems, an IAB node or a child node in an embodiment of the present application receives a path transition configuration of uplink data transmitted by a network device before an IAB-MT of the IAB node is switched from a second donor-CU to a first donor-CU or after the IAB-MT is switched to the first donor-CU, and a detailed description is given below. In the embodiment of the present application, unless otherwise specified, the transition node is an IAB node, and the IAB node device includes an IAB node or its child node.

[0049] <Example of the first aspect> In the embodiment of the present application, a topology regression method is provided, which is described from the IAB node or child node side, in which the transmission path of the uplink service of the IAB node is migrated from a first donor centralized unit (donor-CU) to a second donor centralized unit, and then migrated from the second donor centralized unit to the first donor centralized unit.

[0050] 11 is a diagram showing a topology regression method in an embodiment of the present application. As shown in FIG. 11, the method includes the following steps:

[0051] 1101: An IAB node or a child node receives a route transition setting of uplink data transmitted by a network device; and 1102: The IAB node or the child node applies the path transition configuration, in which the IAB-DU of the IAB node maintains an F1 connection with the first donor-CU.

[0052] Note that, although the above-mentioned FIG. 11 is for illustrative purposes of the embodiment of the present application, the present application is not limited thereto. For example, the execution order between each operation (step) can be appropriately adjusted, or some other operations can be increased or decreased. Those skilled in the art can make appropriate modifications based on the above-mentioned contents without being limited to the description of the above-mentioned FIG. 11.

[0053] Below, we will explain the case where the transmission path of the IAB node's uplink service (including F1-C, F1-U and non-F1 services (traffic)) is transitioned from the first donor centralized unit (donor-CU) to the second donor centralized unit.

[0054] When the uplink service of an IAB node is migrated from an F1-terminating CU to a non-F1-terminating CU, the network device can set a mapping relationship between the original routing ID and the target routing ID, i.e., donor centralized unit inter-routing indicator rewriting information (BAP Header Rewriting Information), in the IAB node.

[0055] After that, when the IAB node forwards uplink data, it replaces the original routing ID with the target routing ID, and because the target routing ID belongs to the non-F1-terminating CU area, the IAB node needs to make a routing selection based on the target routing ID and the routing information of the topology domain of the target donor-CU. Therefore, the network device can configure the IAB node with routing information in which the BAP address of the next hop node belongs to the topology domain of the non-F1-terminating CU (in the routing information before the path transition, the BAP address of the next hop node of the egress link belongs to the topology domain of the F1-terminating CU).

[0056] Since the BAP address of the IAB node's preceding hop node belongs to the topological domain of an F1-terminating CU and the BAP address of the next hop node belongs to the topological domain of a non-F1-terminating CU, the network device can reconfigure the RLC channel mapping information in the IAB node (in the RLC channel mapping information before the route transition, the addresses of the preceding hop node and the next hop node all belong to the topological domain of an F1-terminating CU).

[0057] Hereinafter, the embodiments of the present application will be further described according to different scenarios in which the transmission paths of the uplink services (including F1-C, F1-U and non-F1 services) of the IAB node are migrated (regressed) from the second donor-CU to the first donor-CU. Hereinafter, the handover (switching) scenario will be taken as an example for explanation, in which the IAB node or child node receives a path transition configuration for uplink data sent by a network device before or after the IAB-MT of the IAB node is switched from the second donor-CU to the first donor-CU. In the handover scenario, the transmission paths of all the uplink services of the IAB node need to be migrated from the second donor-CU to the first donor-CU.

[0058] In some embodiments, the transmission path of the uplink service of the IAB node transitions from a first donor distribution unit (donor-DU) of a first donor-CU to a second donor-DU of a second donor-CU, and then transitions from a second donor-DU of the second donor-CU to a first donor-DU of the first donor-CU.

[0059] In some embodiments, the route transition configuration is sent from the first donor-CU to the IAB node or child node via an F1AP message or an RRC message.

[0060] In some embodiments, for an uplink service that needs to be switched to the first donor-CU, the route transition configuration includes: an augmentation (addition) of a routing configuration to indicate a mapping relationship between a first routing indicator and a BAP address of a next hop node of the IAB node; and an augmentation of a first RLC channel mapping configuration to indicate a mapping relationship between the BAP address of a preceding hop node of the IAB node, an ingress link Radio Link Control (RLC) channel indicator, the BAP address of the next hop node of the IAB node, and an egress link RLC channel indicator, wherein the first routing indicator, the BAP address of the preceding hop node of the IAB node, and the BAP address of the next hop node of the IAB node belong to the network topology domain of the first donor-CU, and the destination BAP address of the first routing indicator is the BAP address of the first donor-DU.

[0061] For example, when a boundary node is switched from a non-F1-terminating CU to an F1-terminating CU, if the parent node after the switch still uses the original donor-DU, the network device only needs to configure the routing information belonging to the F1-terminating CU topology domain for the original routing ID and the RLC channel mapping information from the boundary node to the parent node after the switch in the boundary node (the address of the previous hop node and the address of the next hop node all belong to the F1-terminating CU area).

[0062] In some embodiments, the IAB node or child node receives the path transition configuration before the IAB-MT switches from the second donor-CU to the first donor-CU.

[0063] In addition, to avoid uplink data loss due to the absence of available routing or egress RLC channel after the regression, the network device needs to configure the routing information belonging to the F1-terminating CU topology domain for the original routing ID and the RLC channel mapping information from the boundary node to the parent node after the regression (the address of the preceding hop node and the address of the next hop node all belong to the topology domain of the F1-terminating CU) before the boundary node performs the regression. Therefore, the non-F1-terminating CU can start the topology regression before or during the regression preparation, so as to complete the application of these parameters after the regression.

[0064] For an uplink service to be migrated (degraded) to the first donor-CU, the corresponding routing indicator rewrite indicator, routing information and RLC channel mapping information need to be released. In some embodiments, the route transition configuration further includes: releasing a donor-CU inter-routing indicator rewrite configuration to indicate a mapping relationship between the first routing indicator and the second routing indicator; releasing a routing configuration to indicate a mapping relationship between the second routing indicator and the BAP address of the next hop node of the IAB node; or releasing a second RLC channel mapping configuration to indicate a mapping relationship between the address of the previous hop node of the IAB node, the ingress link RLC channel indicator and the BAP address of the next hop node of the IAB node, and the egress link RLC channel indicator, wherein the first routing indicator and the BAP address of the previous hop node of the IAB node belong to the network topology domain of the first donor-CU, the destination BAP address of the first routing indicator is the BAP address of the first donor-DU, the second routing indicator and the BAP address of the next hop node of the IAB node belong to the network topology domain of the second donor-CU, and the destination BAP address of the second routing indicator is the BAP address of the second donor-DU.

[0065] For example, the route transition configuration may include one of a routing indicator rewrite configuration release, a routing configuration release, and a second RLC channel mapping configuration release, or may include any two of the three configurations, but the present application is not limited thereto.

[0066] Figure 12 is a diagram showing an example of topology regression in an embodiment of the present application. As shown in Figure 12, IAB node 3 (including IAB-MT 3 and IAB-DU 3) is a transition node, and its serving transmission path is transitioned from donor-DU 1 of source donor-CU to donor-DU 2 of target donor-CU. IAB-MT 3 of IAB node 3 is transitioned from donor-DU 2 of target donor-CU to donor-DU 1 of source donor-CU after the switching is completed.

[0067] As shown by the solid lines in the right part of Figure 12, the routing IDs of the uplink services of IAB node 3 and child nodes (e.g., IAB node 4, IAB node 5, etc. shown in Figure 12) can remain unchanged, that is, the routing ID whose destination address is donor-DU 1 can still be used.

[0068] The above explains the case of routing ID, and the following explains the case of IP address.

[0069] In some embodiments, to migrate services back to the first donor-CU, the IAB node or child node receives configuration information sent by the first donor-CU, and the configuration information is used to configure replacing the configuration information of the IP address anchored in the second donor-DU with an IP address anchored in the first donor-DU, where the IP address is used for F1 user plane data, F1 control plane data or non-F1 data of the IAB node or child node.

[0070] For example, if the first donor-DU has a source IP address filtering function, that is, it may drop uplink data containing an IP address assigned by another donor-DU, the transition node needs to change the IP address carried by the uplink service to the IP address assigned by the first donor-DU. Therefore, the donor-CU sets the IP address assigned by the target donor-DU in the transition node before the transition node performs the switchover.

[0071] In the embodiments of the present application, an "IP address anchored to IAB donor-DU" may be understood as an "IP address assigned by the donor-DU" or a "Transport Network Layer (TNL) address(es) that is (are) routable via the IAB-donor-DU", and these terms are interchangeable and the present application is not limited thereto.

[0072] The routing IDs of the services (including uplink and downlink services) can be kept unchanged in the transition node and child nodes, but the IP addresses anchored to the second donor-DU need to be replaced with the IP addresses anchored to the first donor-DU. Also, since the IP addresses used by the IAB nodes and child nodes are selected based on the address of the first donor-DU, the configuration of the IP addresses of the services needs to be done on the BAP address of the first donor-DU, including the increment of the IP addresses anchored to the first donor-DU and the release of the IP addresses anchored to the second donor-DU.

[0073] In some embodiments, the configuration information is IP address configuration information for the BAP address of the first donor-DU, for example, the configuration information is used to change the IP address anchored to the second donor-DU for the BAP address of the first donor-DU to an IP address anchored to the first donor-DU.

[0074] In some embodiments, the IAB node or child node receives the configuration information before the IAB-MT switches from the second donor-CU to the first donor-CU.

[0075] In some embodiments, the IAB node or child node replaces the IP address anchored to the second donor-DU with the IP address anchored to the first donor-DU when the IAB-MT completes the switch from the second donor-CU to the first donor-CU.

[0076] For example, the transition node needs to immediately apply the IP address assigned by the first donor-DU when the switchover is completed, and for example, the above "replace" may be further understood as "increasing the IP address anchored to the first donor-DU and releasing the IP address anchored to the second donor-DU".

[0077] In some embodiments, the configuration information of the IAB node is sent by the donor centralized unit through a switch command radio resource control (RRC) message or an RRC reconfiguration message, and the configuration information of the child node is sent by the donor centralized unit through an RRC reconfiguration message.

[0078] For example, when a donor-DU under an F1-terminating CU has an IP address filtering function, in order to reduce uplink data drops, the network device needs to configure the IP address allocated for the boundary node by the donor-DU of the F1-terminating CU to the boundary node before the boundary node performs a switchover, so that the boundary node can immediately apply the IP address when the switchover is completed.

[0079] In addition, the network device must configure the IP address allocated for the child node by the donor-DU under the F1-terminating CU to the child node before the boundary node switches, so that the child node can immediately apply the allocated IP address when the boundary node switches.

[0080] Also, for example, upon completion of the regression, the boundary node can send instructions to the child node to cause the child node to apply the above-mentioned IP address settings; or, before completing the switch, the parent node of the node can cache the above-mentioned IP address configured for the child node until the boundary node completes the regression and then send it to the child node.

[0081] The above describes the case where the transmission path of the uplink service of the transition node is transitioned to the original donor-DU. Below, we will explain the case where the transmission path of the uplink service of the transition node is transitioned (regressed) to another donor-DU.

[0082] In some embodiments, the transmission path of the uplink service of the IAB node transitions from a first donor-DU of a first donor-CU to a second donor-DU of a second donor-CU, and then transitions from a second donor-DU of the second donor-CU to a third donor-DU of the first donor-CU.

[0083] In some embodiments, for an uplink service to be migrated to the first donor-CU, the route transition configuration includes: an increase in an inter-donor-DU routing indicator rewrite configuration to indicate a mapping relationship between the first routing indicator and a third routing indicator; an increase in a routing configuration to indicate a mapping relationship between the third routing indicator and a BAP address of the next hop node of the IAB node; and an increase in a first RLC channel mapping configuration to indicate a mapping relationship between the BAP address of the preceding hop node of the IAB node, the ingress link RLC channel indicator, the BAP address of the next hop node of the IAB node, and the egress link RLC channel indicator, wherein the first routing indicator, the third routing indicator, the BAP address of the preceding hop node of the IAB node, and the BAP address of the next hop node of the IAB node belong to the network topology domain of the first donor-CU, the destination BAP address of the third routing indicator is the BAP address of the third donor-DU, and the destination BAP address of the first routing indicator is the BAP address of the first donor-DU.

[0084] In some embodiments, the IAB node or child node receives the path transition configuration before the IAB-MT switches from the second donor-CU to the third donor-CU.

[0085] For an uplink service that transitions back to the first donor-CU, it is necessary to release the corresponding routing indicator rewrite indicator, routing information and RLC channel mapping information. In some embodiments, the route transition configuration further includes: releasing a donor-CU inter-routing indicator rewrite configuration to indicate a mapping relationship between the first routing indicator and the second routing indicator; releasing a routing configuration to indicate a mapping relationship between the second routing indicator and the BAP address of the next hop node of the IAB node; or releasing a second RLC channel mapping configuration to indicate a mapping relationship between the address of the IAB node's preceding hop node, the ingress link RLC channel indicator and the BAP address of the next hop node of the IAB node, and the egress link RLC channel indicator, wherein the first routing indicator and the BAP address of the IAB node's preceding hop node belong to the network topology domain of the first donor-CU, the destination BAP address of the first routing indicator is the BAP address of the first donor-DU, the second routing indicator and the BAP address of the IAB node's next hop node belong to the network topology domain of the second donor-CU, and the destination BAP address of the second routing indicator is the BAP address of the second donor-DU.

[0086] For example, the route transition configuration may include one of the release of a routing indicator rewrite configuration, the release of a routing configuration, and the release of a second RLC channel mapping configuration, or may include any two of them, or may even include all three of them, but the present application is not limited thereto.

[0087] Figure 13 is a diagram showing another example of topology regression in an embodiment of the present application. As shown in Figure 13, IAB node 3 (including IAB-MT 3 and IAB-DU 3) is a transition node, whose serving transmission path transitions from donor-DU 1 of source donor-CU to donor-DU 2 of target donor-CU, and then transitions from donor-DU 2 of target donor-CU back to donor-DU 3 of source donor-CU.

[0088] After the regression of IAB-MT 3 of IAB node 3 is completed, the routing IDs of the uplink services of IAB node 3 and its child nodes (e.g., IAB node 4, IAB node 5, etc. shown in Figure 13) can be kept unchanged, as shown by the solid lines in the right part.

[0089] In some embodiments, since the IAB node has already received the mapping relationship information (inter-donor-DU rewriting information) transmitted by the network device, the IAB node can rewrite the first routing indicator carried in the BAP header of the uplink data to a third routing indicator.

[0090] For example, as shown by the dotted line in the right part of Fig. 13, IAB node 3 needs to replace the original routing IDs of the uplink services and the uplink services of child nodes (such as IAB node 4 and IAB node 5 shown in Fig. 13) with the target routing IDs, in which the destination BAP address of the original routing ID is donor-DU 1 of the source donor-CU, and the destination BAP address of the replaced routing ID is donor-DU 3 of the source donor-CU.

[0091] Also, for example, after replacing the source routing ID with the target routing ID, routing selection and backhaul RLC channel selection can be made based on the target routing ID, and the donor-CU updates the routing information and RLC channel mapping information in the transition node (because the original routing information does not include available routing for the target routing ID).

[0092] The transition node can apply the inter-donor-DU rewriting information, new routing information, and RLC channel mapping information when the switching is completed or when the configuration is received. The donor-CU can instruct the transition node to cache the above-mentioned path transition configuration first, and then apply the above-mentioned path transition configuration when the IAB-MT switching is completed.

[0093] The above explains the case of routing ID, but below we will explain the case of IP address.

[0094] In some embodiments, to migrate services back to the first donor-CU, the IAB node or child node receives configuration information to configure it to replace an IP address anchored in the second donor-DU with an IP address anchored in a third donor-DU, where the IP address is used for F1 user plane data, F1 control plane data, or non-F1 data of the IAB node or child node.

[0095] For example, if donor-DU 3 has IP address filtering function, i.e., it may drop uplink data containing IP addresses assigned by other donor-DUs, the transition node needs to change the IP address carried in the uplink F1-U data to the IP address assigned by donor-DU 3. Therefore, donor-CU configures the IP address assigned by donor-DU 3 of F1-U in the transition node before the transition node performs switching.

[0096] In the embodiments of the present application, an "IP address anchored to IAB donor-DU" may be understood as an "IP address assigned by the donor-DU" or a "Transport Network Layer (TNL) address(es) that is (are) routable via the IAB-donor-DU", and these terms may be used interchangeably, but the present application is not limited thereto.

[0097] In some embodiments, the IAB node or child node receives the above configuration information before the IAB-MT switches from the second donor-CU to the first donor-CU.

[0098] The routing ID of the service (including uplink and downlink services) can be kept unchanged in the transition node and child node, but the IP address anchored to the second Donor-DU needs to be replaced with the IP address anchored to the third Donor-DU. Also, since the IP address used by the IAB node and child node is selected based on the address of the first Donor-DU, the configuration of the IP address of the service needs to be done on the BAP address of the first Donor-DU, including the increment of the IP address anchored to the third donor-DU and the release of the IP address anchored to the second donor-DU.

[0099] In some embodiments, the configuration information is IP address configuration information for the BAP address of the first donor-DU, for example, the configuration information is used to change the IP address for the BAP address of the first donor-DU anchored to the second donor-DU to an IP address anchored to the third donor-DU.

[0100] In some embodiments, the IAB node or child node replaces the IP address anchored to the second donor-DU with the IP address anchored to the third donor-DU when the IAB-MT completes the switch from the second donor-CU to the first donor-CU.

[0101] For example, the transition node needs to immediately apply the IP address assigned by donor-DU 3 upon completion of the switchover. Also, for example, the above "replace" may be further understood as "increasing the IP address anchored to the third donor-DU and releasing the IP address anchored to the second donor-DU".

[0102] In some embodiments, the configuration information of the IAB node is sent by the donor centralized unit through a switch command radio resource control (RRC) message or an RRC reconfiguration message, and the configuration information of the child node is sent by the donor centralized unit through an RRC reconfiguration message.

[0103] The above describes the handover scenario as an example, but the re-establishment scenario and the dual connection scenario will be described below, where the same content as the handover scenario will not be described.

[0104] In some embodiments, the IAB node or child node receives a path transition configuration for uplink data sent from a network device after the IAB-MT of the IAB node is re-established to the second donor-CU; and the IAB node or child node applies the path transition configuration, during which the IAB-DU of the IAB node maintains an F1 connection with the first donor-CU. In the re-establishment scenario, the transmission paths of all services of the IAB node need to be migrated back from the second donor-CU to the first donor-CU.

[0105] In some embodiments, an IAB node or a child node receives a path transition configuration for uplink data transmitted by a network device; and the IAB node or a child node applies the path transition configuration, in which an IAB-MT of the IAB node establishes a dual connection with the first donor-CU and the second donor-CU, and an IAB-DU of the IAB node maintains an F1 connection with the first donor-CU. In a dual connection scenario, only the transmission paths of services of some IAB nodes may be migrated back from the second donor-CU to the first donor-CU.

[0106] Although the above-mentioned embodiments are provided to exemplify the embodiments of the present application, the present application is not limited thereto, and furthermore, appropriate modifications can be made based on the above-mentioned embodiments. For example, the above-mentioned embodiments may be used alone, or a plurality of the above-mentioned embodiments may be used in combination.

[0107] As can be seen from the above embodiment, an IAB node or a child node receives a path transition configuration for uplink data sent by a network device; and the IAB node or the child node applies the path transition configuration, in which the IAB-DU of the IAB node maintains an F1 connection with the first donor-CU, thereby reducing or avoiding the problem of uplink data being dropped, reducing transmission delay, and shortening service interruption time.

[0108] <Example of the second aspect> In the embodiment of the present application, a topology regression method is provided, and the description is made from the donor concentration unit side, and the description of the same contents as those in the embodiment of the first aspect is omitted.

[0109] In some embodiments, the transmission path of the uplink service of the IAB node is migrated from a first donor centralized unit (donor-CU) to a second donor centralized unit, and then migrated from the second donor centralized unit to the first donor centralized unit. The first donor-CU receives a topology regression request sent by the second donor-CU; and the first donor-CU sends a path transition configuration for uplink data, during which the IAB-DU of the IAB node maintains an F1 connection with the first donor-CU.

[0110] In some embodiments, the transmission path of the uplink service of the IAB node is migrated from a first donor distribution unit (donor-DU) of a first donor-CU to a second donor-DU of a second donor-CU, and then migrated (regressed) from the second donor-DU of the second donor-CU back to the first donor-DU of the first donor-CU.

[0111] In some embodiments, the transmission path of the uplink service of the IAB node is shifted from a first donor-DU of a first donor-CU to a second donor-DU of a second donor-CU, and then shifted (regressed) from the second donor-DU of the second donor-CU to a third donor-DU of the first donor-CU.

[0112] In some embodiments, the first donor-CU sends a route transition configuration to the IAB node or the child node through an F1AP message or an RRC message.

[0113] In some embodiments, the topology regression request includes an IP address anchored to the second donor-DU for the BAP address of the first donor-DU, where the IP address is used for F1 user plane data, F1 control plane data or non-F1 data of the IAB node or child node.

[0114] In some embodiments, the first donor-CU sends to the second donor-CU configuration information for configuring the replacement of an IP address anchored to the second donor-DU with an IP address anchored to the first donor-DU, or for configuring the replacement of an IP address anchored to the second donor-DU with an IP address anchored to the third donor-DU.

[0115] First, a handover scenario will be used as an example below.

[0116] In some embodiments, the first donor-CU sends a route transition configuration in the uplink data before or after the IAB-MT of the IAB node is switched from the second donor-CU to the first donor-CU.

[0117] In some embodiments, the second donor-CU sends a topology degrade request to the first donor-CU after sending a switch request for switching the IAB-MT to the first donor-CU.

[0118] FIG. 14 is a flowchart of signaling of topology regression in an embodiment of the present application, and illustrates an example of a case where topology regression is performed after switching preparation when an IAB node (boundary node) is switched from a non-F1-terminating CU to an F1-terminating CU.

[0119] - The boundary node sends a measurement report to the target donor-CU, triggering switchover preparation, in which the non-F1-terminating CU (target donor-CU) starts degenerating to the F1-terminating CU (source donor-CU).

[0120] - After the boundary node has completed its degradation, the target donor-CU sends a UE context release request for the boundary node-MT to the source donor-CU.

[0121] - The target donor-CU sends a topology degrade request Xn message (UE-associated message for the boundary node and uses the boundary node's XnAP indicator) to the source donor-CU, which contains a request to allocate IP addresses for F1 or non-F1 services in case of a transition node, and a request to allocate IP addresses for F1 and non-F1 services in case of a child node.

[0122] - When the boundary node is switched to the original donor-DU, configure the boundary node with routing information in the F1-terminating CU topology domain for the original routing ID, configure new RLC channel mapping information belonging to the F1-terminating CU topology, request the original donor-DU to allocate IP addresses for the boundary node's F1 and non-F1 services, and request the original donor-DU to allocate IP addresses for the child node's F1 and non-F1 services. When the boundary node is not switched to the original donor-DU, configure the boundary node with inter-donor-DU rewriting information in the F1-terminating CU area, configure the boundary node with routing information in the F1-terminating CU topology domain for the target routing ID after switching, configure new RLC channel mapping information belonging to the F1-terminating CU topology, request the new donor-DU to allocate IP addresses for the boundary node's F1 and non-F1 services, and request the new donor-DU to allocate IP addresses for the child node's F1 and non-F1 services.

[0123] - The source donor-CU uses an F1AP message to send the above-mentioned inter-donor-DU rewriting information, routing information and RLC channel mapping information to the boundary node, and releases the following configuration: BAP Header Rewriting Information, routing information of the non-F1-terminating CU area, and RLC channel mapping information in which the address of the previous hop node belongs to the F1-terminating CU topology and the address of the next hop node belongs to the non-F1-terminating CU topology.

[0124] - The source donor-CU sends an RRC reconfiguration message to the boundary node (including the IP address assigned by the new donor-DU or the original donor-DU under the F1-terninating-CU for F1 and non-F1 services).

[0125] - The source donor-CU sends an RRC reconfiguration message to the child node (including the IP address assigned by the new donor-DU or the original donor-DU under the F1-terninating-CU for F1 and non-F1 services).

[0126] - (Optional) The source donor-CU updates the routing and RLC channel mapping information to the nodes on the original path.

[0127] - The boundary node applies the configured IP address.

[0128] - The child node applies the configured IP address.

[0129] - The source donor-CU sends a topology regression response Xn message (a UA (UE-associated message) for the boundary node and uses the XnAP indicator of the boundary node) to the target donor-CU.

[0130] - Target donor-CU / source donor-CU releases XnAP tag for boundary node.

[0131] The above signaling process is for illustrative purposes only to explain the embodiments of the present application, but the present application is not limited thereto, and more specific content of the signaling may be further referred to in the related art.

[0132] In some embodiments, the second donor-CU includes a topology degrade request in the switch request for switching the IAB-MT to the first donor-CU.

[0133] In some embodiments, the configuration information is included in an RRC reconfiguration message that is included in a switch request response message for the IAB-MT to be switched to the first donor-CU.

[0134] 15 is another signaling flow chart of topology regression in an embodiment of the present application, which illustrates a case where an IAB node (boundary node) prepares for switching and simultaneously performs topology regression when switching from a non-F1-terminating CU to an F1-terminating CU. That is, the switching request message includes a topology regression request, which can further reduce uplink data drops and service interruptions compared to FIG. 14.

[0135] - The boundary node sends a measurement report to the target donor-CU, triggering switch preparation for the non-F1-terminating CU (target donor-CU) to start reverting to the F1-terminating CU (source donor-CU). The switch request message includes a topology revert request, which may include the following information: in case of a transition node, a request to allocate IP addresses for F1 or non-F1 services; and in case of a child node, a request to allocate IP addresses for F1 and non-F1 services.

[0136] - When the boundary node is switched to the original donor-DU, configure the boundary node with routing information in the F1-terminating CU topology domain for the original routing ID, configure new RLC channel mapping information belonging to the F1-terminating CU topology, request the original donor-DU to allocate IP addresses for the boundary node's F1 and non-F1 services, and request the original donor-DU to allocate IP addresses for the child node's F1 and non-F1 services. When the boundary node is not switched to the original donor-DU, configure the boundary node with inter-donor-DU rewriting information in the F1-terminating CU domain for the replaced routing ID, configure the boundary node with new RLC channel mapping information belonging to the F1-terminating CU topology, request the new donor-DU to allocate IP addresses for the boundary node's F1 and non-F1 services, and request the new donor-DU to allocate IP addresses for the child node's F1 and non-F1 services.

[0137] - The source donor-CU uses an F1AP message to send the above-mentioned inter-donor-DU rewriting information, routing information and RLC channel mapping information to the boundary node, and releases the following configurations: BAP Header Rewriting Information, a routing table for the non-F1-terminating CU area, and RLC channel mapping information in which the address of the previous hop node belongs to the F1-terminating CU topology and the address of the next hop node belongs to the non-F1-terminating CU topology.

[0138] - The source donor-CU sends an RRC reconfiguration message (including the IP addresses assigned by the new donor-DU or the original donor-DU under the F1-terminating-CU for F1 and non-F1 services) to the child node.

[0139] - The source donor-CU sends a switching request response Xn message to the target donor-CU, which includes a switching command RRC message for the boundary node.

[0140] - The target donor-CU sends an order RRC reconfiguration message to switch to the boundary node (including the IP address assigned by the new donor-DU or the original donor-DU under the F1-terminating-CU for F1 and non-F1 services).

[0141] - The boundary node executes the random access procedure of switching.

[0142] - (Optional) The source donor-CU updates the routing tables and RLC channel mapping tables for the nodes on the original path.

[0143] - The boundary node will apply the configured IP address when the switchover is complete.

[0144] - The child node will apply the configured IP address when the boundary node switch is completed.

[0145] After the boundary node has completed its degradation, the source donor-CU sends a UE context release request for the boundary node-MT to the target donor-CU.

[0146] - Source donor-CU / target donor-CU releases XnAP tag for boundary node.

[0147] The above signaling process is for illustrative purposes only to explain the embodiments of the present application, but the present application is not limited thereto, and more specific content of the signaling may be further referred to in the related art.

[0148] In some embodiments, the second donor-CU sends a topology degrade request to the first donor-CU before sending a switch request for switching the IAB-MT to the first donor-CU.

[0149] When topology regression is performed before switch preparation, the signaling process is similar to that in Fig. 15. The difference is, for example, that the topology regression request is an independent Xn message. Also, because it is an independent Xn message, the topology regression request can instruct the source donor-CU to carry the assigned IP address in the switch command RRC message included in the switch preparation response, rather than in the topology regression response message, so that the boundary node can immediately apply the configured IP address when the switch is completed.

[0150] Although the handover scenario has been described above as an example, the present application is not limited thereto. Below, a re-establishment scenario and a dual connection scenario will be described, but the same content will not be described here.

[0151] In some embodiments, the first donor-CU sends a route transition configuration for uplink data after the IAB-MT of the IAB node is re-established to the second donor-CU. In such a scenario, the first donor-CU can trigger the second donor-CU to initiate a topology revert request, for example, when the IAB-MT is re-established to the first donor-CU, the first donor-CU can trigger the second donor-CU to initiate a topology revert request when the first donor-CU requests the second donor-CU to obtain context information of the IAB-MT.

[0152] In some embodiments, the IAB-MT of the IAB node has established a dual connection with the first donor-CU and the second donor-CU. In such a scenario, for example, the topology decommissioning request includes indication information of the service whose transmission path is to be migrated from the second donor-CU to the first donor-CU.

[0153] Although the above-mentioned embodiments are provided to exemplify the embodiments of the present application, the present application is not limited thereto, and furthermore, appropriate modifications can be made based on the above-mentioned embodiments. For example, the above-mentioned embodiments may be used alone, or a plurality of the above-mentioned embodiments may be used in combination.

[0154] As can be seen from the above embodiment, when an uplink service transmission path of an IAB node or a child node is migrated from a second donor-CU to a first donor-CU, receiving a path transition configuration for uplink data sent by a network device; and the IAB node or child node applies the path transition configuration, in which the IAB-DU of the IAB node maintains an F1 connection with the first donor-CU, thereby reducing or avoiding the problem of uplink data being dropped, reducing transmission delay, and shortening service interruption time.

[0155] <Example of the third aspect> In the embodiment of the present application, an IAB node device is provided, and the description of the same contents as those in the embodiments of the first and second aspects is omitted here. The device may be, for example, an IAB node or a child node in an IAB system, or may be one or more parts, assemblies, or modules arranged in the IAB node or the child node. The transmission path of the uplink service of the IAB node device is transferred from a first donor centralized unit to a second donor centralized unit, and then transferred from the second donor centralized unit to the first donor centralized unit.

[0156] Figure 16 is a diagram illustrating an IAB node device in an embodiment of the present application. As shown in Figure 16, an IAB node device 1600 includes a receiving unit 1601 and a processing unit 1602. The receiving unit 1601 receives a path transition setting of uplink data sent by a network device, and the processing unit 1602 applies the path transition setting, during which the IAB-DU of the IAB node maintains an F1 connection with the first Donor-CU.

[0157] In some embodiments, the transmission path of the uplink service of the IAB node transitions from a first donor distribution unit (donor-DU) of a first donor-CU to a second donor-DU of a second donor-CU, and then transitions from a second donor-DU of the second donor-CU to a first donor-DU of the first donor-CU.

[0158] In some embodiments, the route transition configuration is sent from the first donor-CU to the IAB node or child node via an F1AP message or an RRC message.

[0159] In some embodiments, the route transition configuration includes: an augmentation of a routing configuration to indicate a mapping relationship between a first routing indicator and a BAP address of a next hop node of the IAB node; and an augmentation of a first RLC channel mapping configuration to indicate a mapping relationship between a BAP address of a preceding hop node of the IAB node, an ingress link Radio Link Control (RLC) channel indicator, a BAP address of the next hop node of the IAB node, and an egress link RLC channel indicator, wherein the first routing indicator, the BAP address of the preceding hop node of the IAB node, and the BAP address of the next hop node of the IAB node belong to the network topology domain of the first Donor-CU, and the destination BAP address of the first routing indicator is the BAP address of the first donor-DU.

[0160] In some embodiments, the receiver 1601 receives a path transition configuration before the IAB-MT switches from the second donor-CU to the first donor-CU.

[0161] In some embodiments, the route transition configuration further includes: releasing a donor-CU inter-routing indicator rewrite configuration to indicate a mapping relationship between a first routing indicator and a second routing indicator; releasing a routing configuration to indicate a mapping relationship between a second routing indicator and a BAP address of a next hop node of the IAB node; or releasing a second RLC channel mapping configuration to indicate a mapping relationship between an address of a previous hop node of the IAB node, an ingress link RLC channel indicator and a BAP address of a next hop node of the IAB node, and an egress link RLC channel indicator, wherein the first routing indicator and the BAP address of the previous hop node of the IAB node belong to a network topology domain of the first donor-CU, a destination BAP address of the first routing indicator is a BAP address of the first donor-DU, the second routing indicator and the BAP address of the next hop node of the IAB node belong to a network topology domain of the second donor-CU, and a destination BAP address of the second routing indicator is a BAP address of the second donor-DU.

[0162] In some embodiments, the receiving unit 1601 further receives configuration information for configuring an IP address anchored to the first donor-DU to replace an IP address anchored to the second donor-DU, wherein the IP address is used for F1 user plane data, F1 control plane data or non-F1 data of the IAB node or the child node.

[0163] In some embodiments, the receiver 1601 receives the configuration information before the IAB-MT performs a switch from the second donor-CU to the first donor-CU.

[0164] When switching of the IAB-MT from the second donor-CU to the first donor-CU is completed, the processing unit 1602 replaces the IP address anchored in the second donor-DU with the IP address anchored in the first donor-DU.

[0165] In some embodiments, the configuration information of the IAB node is sent via a switching command Radio Resource Control (RRC) message or an RRC reconfiguration message, and the configuration information of the child node is sent via an RRC reconfiguration message.

[0166] In some embodiments, the configuration information is IP address configuration information for the BAP address of the first donor-DU, for example, the configuration information is used to change the IP address anchored to the second donor-DU for the BAP address of the first donor-DU to an IP address anchored to the first donor-DU.

[0167] In some embodiments, the transmission path of the uplink service of the IAB node is migrated from a first donor-DU of a first donor-CU to a second donor-DU of a second donor-CU, and then from the second donor-DU of the second donor-CU to a third donor-DU of the first donor-CU, and the path transition configuration is sent by the first donor-CU to the IAB node or child node via an F1AP message.

[0168] In some embodiments, the route transition configuration includes: an augmentation of a donor-DU inter-routing indicator rewrite configuration to indicate a mapping relationship between a first routing indicator and a third routing indicator; an augmentation of a routing configuration to indicate a mapping relationship between a third routing indicator and a BAP address of a next hop node of the IAB node; and an augmentation of a first RLC channel mapping configuration to indicate a mapping relationship between a BAP address of a preceding hop node of the IAB node, an ingress link RLC channel indicator, a BAP address of a next hop node of the IAB node, and an egress link RLC channel indicator, wherein the first routing indicator, the third routing indicator, the BAP address of the preceding hop node of the IAB node, and the BAP address of the next hop node of the IAB node belong to a network topology domain of the first donor-CU, a destination BAP address of the third routing indicator is a BAP address of the third donor-DU, and a destination BAP address of the first routing indicator is a BAP address of the first donor-DU.

[0169] In some embodiments, the receiver 1601 receives a path transition configuration before the IAB-MT switches from the second donor-CU to the third donor-CU.

[0170] In some embodiments, the route transition configuration further includes: releasing a donor-CU inter-routing indicator rewrite configuration to indicate a mapping relationship between a first routing indicator and a second routing indicator; releasing a routing configuration to indicate a mapping relationship between a second routing indicator and a BAP address of a next hop node of the IAB node; or releasing a second RLC channel mapping configuration to indicate a mapping relationship between an address of a previous hop node of the IAB node, an ingress link RLC channel indicator and a BAP address of a next hop node of the IAB node, and an egress link RLC channel indicator, wherein the first routing indicator and the BAP address of the previous hop node of the IAB node belong to a network topology domain of the first donor-CU, a destination BAP address of the first routing indicator is a BAP address of the first donor-DU, the second routing indicator and the BAP address of the next hop node of the IAB node belong to a network topology domain of the second donor-CU, and a destination BAP address of the second routing indicator is a BAP address of the second donor-DU.

[0171] In some embodiments, the receiving unit 1601 further receives configuration information for configuring an IP address anchored to the second donor-DU to be replaced with an IP address anchored to the third donor-DU, wherein the IP address is used for F1 user plane data, F1 control plane data or non-F1 data of the IAB node or the child node.

[0172] In some embodiments, the receiving unit 1601 receives configuration information before the IAB-MT switches from the second donor-CU to the first donor-CU, and the processing unit 1602 replaces the IP address anchored to the second donor-DU with the IP address anchored to the third donor-DU when the IAB-MT switches from the second donor-CU to the first donor-CU, and

[0173] In some embodiments, the configuration information of the IAB node is sent via a switching command Radio Resource Control (RRC) message or an RRC reconfiguration message, and the configuration information of the child node is sent via an RRC reconfiguration message.

[0174] In some embodiments, the configuration information is IP address configuration information for the BAP address of the first donor-DU, for example, the configuration information is used to change the IP address for the BAP address of the first donor-DU anchored to the second donor-DU to an IP address anchored to the third donor-DU.

[0175] Although the above-mentioned embodiments are provided to exemplify the embodiments of the present application, the present application is not limited thereto, and furthermore, appropriate modifications can be made based on the above-mentioned embodiments. For example, the above-mentioned embodiments may be used alone, or a plurality of the above-mentioned embodiments may be used in combination.

[0176] In addition, only the components or modules related to the present application are described above, but the present application is not limited thereto. The IAB node device 1600 in the embodiment of the present application may further include other components or modules, and the specific contents of these components or modules can be referred to in the related art.

[0177] For convenience, Fig. 16 only shows the connection relationships or signal directions between each component or module, but as can be understood by those skilled in the art, various related technologies such as bus connection may be adopted. Each of the above-mentioned components or modules may be realized by hardware such as a processor, a memory, a transmitter, a receiver, etc., but the implementation of the present application is not limited thereto.

[0178] As can be seen from the above embodiment, an IAB node or a child node receives a path transition configuration for uplink data sent by a network device; and the IAB node or the child node applies the path transition configuration, in which the IAB-DU of the IAB node maintains an F1 connection with the first donor-CU, thereby reducing or avoiding the problem of uplink data being dropped, reducing transmission delay, and shortening service interruption time.

[0179] <Example of the fourth aspect> In the embodiment of the present application, an IAB donor device is provided, and description of the same contents as those in the embodiments of the first to third aspects will be omitted here. The device may be, for example, an IAB donor-CU in an IAB system, or may be one or more components, assemblies, or modules disposed in the IAB donor-CU.

[0180] The IAB system includes an IAB-donor device and an IAB node, the transmission path of the uplink service of the IAB node transitions from a first donor centralized unit to a second donor centralized unit, and then transitions from the second donor centralized unit to the first donor centralized unit.

[0181] Figure 17 is a diagram of an IAB donor device in an embodiment of the present application. As shown in Figure 17, the IAB donor device 1700 includes a receiving unit 1701 and a sending unit 1702. The receiving unit 1701 receives a topology regression request sent by the second donor-CU; and the sending unit 1702 sends a path transition configuration of uplink data, in which the IAB-DU of the IAB node maintains an F1 connection with the first donor-CU.

[0182] In some embodiments, the sender 1702 sends the path transition configuration to the IAB node or the child node via an F1AP message or an RRC message.

[0183] In some embodiments, the topology regression request includes an IP address anchored to the second donor-DU for the BAP address of the first donor-DU, where the IP address is used for F1 user plane data, F1 control plane data or non-F1 data of the IAB node or child node.

[0184] In some embodiments, the second donor-CU sends a topology regression request to the first donor-CU before sending a switch request for switching the IAB-MT to the first donor-CU; or the second donor-CU includes the topology regression request in the switch request for switching the IAB-MT to the first donor-CU; or the second donor-CU sends a topology regression request to the first donor-CU after sending a switch request for switching the IAB-MT to the first donor-CU.

[0185] In some embodiments, the sending unit 1702 sends, to the second donor-CU, configuration information for configuring the IP address anchored to the first donor-DU to replace the IP address anchored to the second donor-DU, or configuration information for configuring the IP address anchored to the third donor-DU to replace the IP address anchored to the second donor-DU.

[0186] In some embodiments, the configuration information is included in an RRC reconfiguration message that is included in a switch request response message for switching the IAB-MT to the first donor-CU.

[0187] Although the above-mentioned embodiments are provided to exemplify the embodiments of the present application, the present application is not limited thereto, and furthermore, appropriate modifications can be made based on the above-mentioned embodiments. For example, the above-mentioned embodiments may be used alone, or a plurality of the above-mentioned embodiments may be used in combination.

[0188] In addition, only the components or modules related to the present application are described above, but the present application is not limited thereto. The IAB donor device 1700 in the embodiment of the present application may further include other components or modules, and the specific contents of these components or modules can be referred to in the related art.

[0189] For convenience, Fig. 17 shows only the connection relationships or signal directions between each component or module, but as can be understood by those skilled in the art, various related technologies such as bus connection may be adopted. Each of the above-mentioned components or modules may be realized by hardware such as a processor, a memory, a transmitter, a receiver, etc., but the implementation of the present application is not limited thereto.

[0190] As can be seen from the above embodiment, when the transmission path of the uplink service of the IAB node is migrated from the second donor-CU to the first donor-CU, the IAB node or child node receives a path transition configuration for uplink data sent by a network device; and the IAB node or child node applies the path transition configuration, in which the IAB-DU of the IAB node maintains an F1 connection with the first donor-CU, thereby reducing or avoiding the problem of uplink data being dropped, reducing transmission delay, and shortening service interruption time.

[0191] <Example of the fifth aspect> In an embodiment of the present application, a communication system is provided, which includes a donor device and an IAB node. Note that the network architecture of the donor device and the IAB node can be further referred to in the related art, so detailed description thereof is omitted here.

[0192] In an embodiment of the present application, an IAB device is further provided, which may be an IAB donor device or an IAB node device (IAB node or child node).

[0193] Figure 18 is a diagram showing an IAB device in an embodiment of the present application. As shown in Figure 18, the IAB device 1800 may include a processor (e.g., a central processing unit CPU) 1801 and a memory 1802, and the memory 1802 is connected to the processor 1801. The memory 1802 can store various data, and can further store a program 1805 for information processing, and can execute the program 1805 under the control of the central processing unit 1801.

[0194] For example, the processor 1801 may be configured to execute a program to realize the topology regression method in the embodiment of the first aspect. For example, the processor 1801 may be configured to perform the following control: receive a path transition setting in uplink data sent by a network device; and apply the path transition setting, in which the IAB-DU of the IAB node maintains an F1 connection with a first donor-CU.

[0195] Also, for example, the processor 1801 may be configured to execute a program to realize the topology regression method in the embodiment of the second aspect. For example, the processor 1801 may be configured to perform the following control: receive a topology regression request sent by the second donor-CU; and send a path transition configuration of uplink data, in which the IAB-DU of the IAB node maintains an F1 connection with the first donor-CU.

[0196] Also, as shown in Fig. 18, the IAB device 1800 may further include a transceiver 1803, an antenna 1804, etc., among which the functions of these components are similar to those of the prior art, and detailed descriptions thereof will be omitted here. It is not necessary for the IAB device 1800 to include all the components shown in Fig. 18. Also, the IAB device 1800 may further include components not shown in Fig. 18, and for this, reference can be made to the prior art.

[0197] In an embodiment of the present application, a computer-readable program is further provided, in which, when the program is executed in an IAB node device, the program causes a computer to execute the topology regression method in the embodiment of the first aspect in the IAB node device.

[0198] In an embodiment of the present application, a storage medium storing a computer readable program is further provided, in which the computer readable program causes a computer to execute the topology regression method in the embodiment of the first aspect in an IAB node device.

[0199] In an embodiment of the present application, a computer readable program is further provided, which, when executed on an IAB donor device, causes a computer to execute the topology regression method in an embodiment of the second aspect on the IAB donor device.

[0200] An embodiment of the present application further provides a storage medium storing a computer readable program, wherein the computer readable program causes a computer to execute the topology regression method in the embodiment of the second aspect in an IAB donor device.

[0201] The above-mentioned devices and methods may be realized by software or hardware, or may be realized by a combination of hardware and software. The present invention further relates to a computer-readable program, which, when executed by a logic component, causes the logic component to realize the above-mentioned devices or components, or causes the logic component to realize the above-mentioned methods or steps. The logic component may be, for example, a Field Programmable Gate Array (FPGA), a microprocessor, a processor for use in a computer, etc. The present invention also relates to a storage medium, such as a hard disk, a magnetic disk, an optical hard disk, a DVD, a flash memory, etc., storing the above-mentioned program.

[0202] Additionally, one or more combinations of the functional blocks illustrated in the figures and / or one or more combinations of the functional blocks may be implemented as a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic component, a discrete gate or transistor logic component, a discrete hardware assembly, or any other suitable combination for performing the functions described herein. Also, one or more combinations of the functional blocks illustrated in the figures and / or one or more combinations of the functional blocks may be further configured as a combination of computing devices, such as a combination of a DSP and a microprocessor, a combination of multiple microprocessors, one or more microprocessors in communication with a DSP, or any other configuration.

[0203] Although the preferred embodiments of the present invention have been described above, the present invention is not limited to such embodiments, and any modifications to the present invention fall within the technical scope of the present invention as long as they do not depart from the spirit of the present invention.

[0204] Furthermore, with respect to the above-mentioned embodiments, the following supplementary notes are disclosed.

[0205] (Appendix 1) 1. A topology regression method comprising the steps of: Transitioning a transmission path of an uplink service of an IAB node from a first donor centralized unit (donor-CU) to a second donor centralized unit, and then transitioning from the second donor centralized unit to the first donor centralized unit; The method comprises: The IAB node or child node receives a route transition configuration of uplink data transmitted by a network device; and the IAB node or a child node applies the path transition configuration; wherein an IAB-DU of the IAB node maintains an F1 connection with the first donor-CU.

[0206] (Appendix 2) 2. The method according to claim 1, comprising: A method in which the IAB node or child node receives a path transition configuration for uplink data transmitted by the network device before or after the IAB-MT of the IAB node is switched from the second donor-CU to the first donor-CU.

[0207] (Appendix 3) 3. The method according to claim 2, comprising: A method in which the transmission path of the uplink service of the IAB node is migrated from a first donor distribution unit (donor-DU) of a first donor-CU to a second donor-DU of a second donor-CU, and then from the second donor-DU of the second donor-CU to the first donor-DU of the first donor-CU.

[0208] (Appendix 4) 4. The method according to claim 3, comprising: The method, wherein the path transition configuration is sent by the first donor-CU to the IAB node or child node via an F1AP message or an RRC message.

[0209] (Appendix 5) 5. The method according to claim 3 or 4, The path transition configuration includes: an augmentation of a routing configuration for indicating a mapping relationship between a first routing indicator and a BAP address of a next hop node of the IAB node; and an augmentation of a first RLC channel mapping configuration for indicating a mapping relationship between a BAP address of a previous hop node of the IAB node, an ingress link Radio Link Control (RLC) channel indicator, and a BAP address of a next hop node of the IAB node and an egress link RLC channel indicator; The first routing indicator, the BAP address of the IAB node's preceding hop node, and the BAP address of the IAB node's next hop node belong to the network topology domain of the first Donor-CU, and the destination BAP address of the first routing indicator is the BAP address of the first donor-DU.

[0210] (Appendix 6) 6. The method according to claim 5, The IAB node or child node receives the path transition configuration before the IAB-MT performs a switch from the second donor-CU to the first donor-CU.

[0211] (Appendix 7) 6. The method according to claim 5, The route transition configuration further includes: releasing a donor-CU inter-routing indicator rewrite configuration to indicate a mapping relationship between a first routing indicator and a second routing indicator; releasing a routing configuration to indicate a mapping relationship between a second routing indicator and a BAP address of a next hop node of the IAB node; or releasing a second RLC channel mapping configuration to indicate a mapping relationship between an address of a preceding hop node of the IAB node, an entry link RLC channel indicator, and a BAP address of a next hop node of the IAB node and an exit link RLC channel indicator; wherein the first routing indicator and the BAP address of the preceding hop node of the IAB node belong to a network topology domain of the first donor-CU, the destination BAP address of the first routing indicator is the BAP address of the first donor-DU, the second routing indicator and the BAP address of the next hop node of the IAB node belong to a network topology domain of the second donor-CU, and the destination BAP address of the second routing indicator is the BAP address of the second donor-DU.

[0212] (Appendix 8) The method according to any one of claims 5 to 7, further comprising: The IAB node or child node receives configuration information for configuring an IP address anchored to the second donor-DU to be replaced with an IP address anchored to the first donor-DU, wherein the IP address is used for F1 user plane data, F1 control plane data or non-F1 data of the IAB node or child node.

[0213] (Appendix 9) 9. The method according to claim 8, comprising: The IAB node or child node receives the configuration information before the IAB-MT performs a switchover from the second donor-CU to the first donor-CU.

[0214] (Appendix 10) The method according to claim 8, further comprising: The IAB node or child node replaces an IP address anchored to the second donor-DU with an IP address anchored to the first donor-DU.

[0215] (Appendix 11) 11. The method according to any one of claims 8 to 10, comprising: The method, wherein the configuration information of the IAB node is transmitted by a switching command Radio Resource Control (RRC) message or an RRC reconfiguration message, and the configuration information of the child node is transmitted by an RRC reconfiguration message.

[0216] (Appendix 12) 12. The method according to any one of claims 8 to 11, comprising: The method, wherein the configuration information is IP address configuration information for a BAP address of the first donor-DU.

[0217] (Appendix 13) 13. The method of claim 12, The method, wherein the configuration information is used to change an IP address anchored to the second donor-DU for a BAP address of the first donor-DU to an IP address anchored to the first donor-DU.

[0218] (Appendix 14) 3. The method according to claim 2, comprising: A method in which the transmission path of the uplink service of the IAB node is transferred from a first donor-DU of a first donor-CU to a second donor-DU of a second donor-CU, and then from the second donor-DU of the second donor-CU to a third donor-DU of the first donor-CU.

[0219] (Appendix 15) 15. The method according to claim 14, The method, wherein the path transition configuration is sent by the first donor-CU to the IAB node or child node via an F1AP message or an RRC message.

[0220] (Appendix 16) 16. The method according to claim 14 or 15, the route transition configuration includes: an increase in a donor-DU inter-routing indicator rewrite configuration to indicate a mapping relationship between a first routing indicator and a third routing indicator; an increase in a routing configuration to indicate a mapping relationship between the third routing indicator and a BAP address of a next hop node of the IAB node; and an increase in a first RLC channel mapping configuration to indicate a mapping relationship between the BAP address of a preceding hop node of the IAB node, an entry link RLC channel indicator, the BAP address of the next hop node of the IAB node, and an exit link RLC channel indicator, wherein the first routing indicator, the third routing indicator, the BAP address of the preceding hop node of the IAB node, and the BAP address of the next hop node of the IAB node belong to a network topology domain of the first donor-CU, a destination BAP address of the third routing indicator is a BAP address of the third donor-DU, and a destination BAP address of the first routing indicator is a BAP address of the first donor-DU.

[0221] (Appendix 17) 17. The method according to any one of claims 14 to 16, comprising: The IAB node or child node receives the path transition configuration before the IAB-MT performs a switch from the second donor-CU to the third donor-CU.

[0222] (Appendix 18) 17. The method of claim 16, comprising: The route transition configuration further includes: releasing a donor-CU inter-routing indicator rewrite configuration to indicate a mapping relationship between a first routing indicator and a second routing indicator; releasing a routing configuration to indicate a mapping relationship between a second routing indicator and a BAP address of a next hop node of the IAB node; or releasing a second RLC channel mapping configuration to indicate a mapping relationship between an address of a preceding hop node of the IAB node, an entry link RLC channel indicator, and a BAP address of a next hop node of the IAB node and an exit link RLC channel indicator; wherein the first routing indicator and the BAP address of the preceding hop node of the IAB node belong to a network topology domain of the first donor-CU, the destination BAP address of the first routing indicator is the BAP address of the first donor-DU, the second routing indicator and the BAP address of the next hop node of the IAB node belong to a network topology domain of the second donor-CU, and the destination BAP address of the second routing indicator is the BAP address of the second donor-DU.

[0223] (Appendix 19) 20. The method of any one of claims 16 to 19, further comprising: The IAB node or child node receives configuration information for configuring an IP address anchored to the second donor-DU to be replaced with an IP address anchored to the third donor-DU, wherein the IP address is used for F1 user plane data, F1 control plane data or non-F1 data of the IAB node or child node.

[0224] (Appendix 20) 20. The method of claim 19, The IAB node or child node receives the configuration information before the IAB-MT performs a switchover from the second donor-CU to the first donor-CU.

[0225] (Appendix 21) 20. The method of claim 19, further comprising: the IAB node or child node replaces the IP address anchored to the second donor-DU with the IP address anchored to the third donor-DU.

[0226] (Appendix 22) 22. The method according to any one of claims 19 to 21, comprising: The method, wherein the configuration information of the IAB node is transmitted by a switching command Radio Resource Control (RRC) message or an RRC reconfiguration message, and the configuration information of the child node is transmitted by an RRC reconfiguration message.

[0227] (Appendix 23) 23. The method according to any one of claims 19 to 22, comprising: The configuration information is IP address configuration information for a BAP address of a first donor-DU.

[0228] (Appendix 24) 24. The method according to claim 23, comprising: The method, wherein the configuration information is used to change an IP address for a BAP address of the first donor-DU, anchored to the second donor-DU, to an IP address anchored to the third donor-DU.

[0229] (Appendix 25) 2. The method according to claim 1, comprising: The IAB node or child node receives a path transition configuration for uplink data transmitted by the network device after an IAB-MT of the IAB node is re-established to the second donor-CU.

[0230] (Appendix 26) 26. The method according to claim 25, The method, wherein the transmission path of the uplink service of the IAB node transitions from a first donor distribution unit (donor-DU) of a first donor-CU to a second donor-DU of a second donor-CU, and then transitions from a second donor-DU of the second donor-CU to a first donor-DU of the first donor-CU.

[0231] (Appendix 27) 27. The method according to claim 26, comprising: The method, wherein the path transition configuration is sent by the first donor-CU to the IAB node or child node via an F1AP message or an RRC message.

[0232] (Appendix 28) 28. The method according to claim 26 or 27, The path transition configuration includes: an augmentation of a routing configuration for indicating a mapping relationship between a first routing indicator and a BAP address of a next hop node of the IAB node; and an augmentation of a first RLC channel mapping configuration for indicating a mapping relationship between a BAP address of a previous hop node of the IAB node, an ingress link Radio Link Control (RLC) channel indicator, and a BAP address of a next hop node of the IAB node and an egress link RLC channel indicator; The first routing indicator, the BAP address of the IAB node's preceding hop node, and the BAP address of the IAB node's next hop node belong to the network topology domain of the first Donor-CU, and the destination BAP address of the first routing indicator is the BAP address of the first donor-DU.

[0233] (Appendix 29) 29. The method according to claim 28, comprising: The route transition configuration further includes: releasing a donor-CU inter-routing indicator rewrite configuration to indicate a mapping relationship between a first routing indicator and a second routing indicator; releasing a routing configuration to indicate a mapping relationship between a second routing indicator and a BAP address of a next hop node of the IAB node; or releasing a second RLC channel mapping configuration to indicate a mapping relationship between an address of a preceding hop node of the IAB node, an entry link RLC channel indicator, and a BAP address of a next hop node of the IAB node and an exit link RLC channel indicator; wherein the first routing indicator and the BAP address of the preceding hop node of the IAB node belong to a network topology domain of the first donor-CU, the destination BAP address of the first routing indicator is the BAP address of the first donor-DU, the second routing indicator and the BAP address of the next hop node of the IAB node belong to a network topology domain of the second donor-CU, and the destination BAP address of the second routing indicator is the BAP address of the second donor-DU.

[0234] (Appendix 30) 30. The method according to claim 28 or 29, further comprising: The IAB node or child node receives configuration information for configuring an IP address anchored to the second donor-DU to be replaced with an IP address anchored to the first donor-DU, wherein the IP address is used for F1 user plane data, F1 control plane data or non-F1 data of the IAB node or child node.

[0235] (Appendix 31) 31. The method of claim 30, The method, wherein the configuration information is IP address configuration information for a BAP address of the first donor-DU.

[0236] (Appendix 32) 32. The method according to claim 31, The method, wherein the configuration information is used to change an IP address anchored to the second donor-DU for a BAP address of the first donor-DU to an IP address anchored to the first donor-DU.

[0237] (Appendix 33) 26. The method according to claim 25, The method, wherein the transmission path of the uplink service of the IAB node transitions from a first donor-DU of a first donor-CU to a second donor-DU of a second donor-CU, and then transitions from the second donor-DU of the second donor-CU to a third donor-DU of the first donor-CU.

[0238] (Appendix 34) 34. The method of claim 33, The method, wherein the path transition configuration is sent by the first donor-CU to the IAB node or child node via an F1AP message or an RRC message.

[0239] (Appendix 35) 35. The method according to claim 33 or 34, The path transition configuration includes the following: an increase in a donor-DU inter-routing indicator rewrite configuration to indicate a mapping relationship between a first routing indicator and a third routing indicator; an increase in a routing configuration to indicate a mapping relationship between a third routing indicator and a BAP address of a next hop node of the IAB node; and an increase in a first RLC channel mapping configuration to indicate a mapping relationship between a BAP address of a preceding hop node of the IAB node, an entry link RLC channel indicator, and a BAP address of a next hop node of the IAB node and an exit link RLC channel indicator; the first routing indicator, the third routing indicator, the BAP address of the IAB node's preceding hop node, and the BAP address of the IAB node's next hop node belong to a network topology domain of the first donor-CU, a destination BAP address of the third routing indicator is a BAP address of the third donor-DU, and a destination BAP address of the first routing indicator is a BAP address of the first donor-DU.

[0240] (Appendix 36) 36. The method of claim 35, The route transition configuration further includes: releasing a donor-CU inter-routing indicator rewrite configuration to indicate a mapping relationship between a first routing indicator and a second routing indicator; releasing a routing configuration to indicate a mapping relationship between a second routing indicator and a BAP address of a next hop node of the IAB node; or releasing a second RLC channel mapping configuration to indicate a mapping relationship between an address of a preceding hop node of the IAB node, an entry link RLC channel indicator, and a BAP address of a next hop node of the IAB node and an exit link RLC channel indicator; wherein the first routing indicator and the BAP address of the preceding hop node of the IAB node belong to a network topology domain of the first donor-CU, the destination BAP address of the first routing indicator is the BAP address of the first donor-DU, the second routing indicator and the BAP address of the next hop node of the IAB node belong to a network topology domain of the second donor-CU, and the destination BAP address of the second routing indicator is the BAP address of the second donor-DU.

[0241] (Appendix 37) The method according to claim 35 or 36, further comprising: The IAB node or child node receives configuration information for configuring an IP address anchored to the second donor-DU to be replaced with an IP address anchored to the third donor-DU, wherein the IP address is used for F1 user plane data, F1 control plane data or non-F1 data of the IAB node or child node.

[0242] (Appendix 38) 38. The method according to claim 37, The method, wherein the configuration information is IP address configuration information for a BAP address of the first donor-DU.

[0243] (Appendix 39) 39. The method according to claim 38, comprising: The method, wherein the configuration information is used to change an IP address for a BAP address of the first donor-DU, anchored to the second donor-DU, to an IP address anchored to the third donor-DU.

[0244] (Appendix 40) 2. The method according to claim 1, comprising: The IAB-MT of the IAB node establishes a dual connection with the first donor-CU and the second donor-CU.

[0245] (Appendix 41) 41. The method of claim 40, The method, wherein the transmission path of the uplink service of the IAB node transitions from a first donor distribution unit (donor-DU) of a first donor-CU to a second donor-DU of a second donor-CU, and then transitions from a second donor-DU of the second donor-CU to a first donor-DU of the first donor-CU.

[0246] (Appendix 42) 42. The method of claim 41, The method, wherein the path transition configuration is sent by the first donor-CU to the IAB node or child node via an F1AP message or an RRC message.

[0247] (Appendix 43) 43. The method according to claim 41 or 42, The path transition configuration includes: an augmentation of a routing configuration for indicating a mapping relationship between a first routing indicator and a BAP address of a next hop node of the IAB node; and an augmentation of a first RLC channel mapping configuration for indicating a mapping relationship between a BAP address of a previous hop node of the IAB node, an ingress link Radio Link Control (RLC) channel indicator, and a BAP address of a next hop node of the IAB node and an egress link RLC channel indicator; The first routing indicator, the BAP address of the IAB node's preceding hop node, and the BAP address of the IAB node's next hop node belong to the network topology domain of the first Donor-CU, and the destination BAP address of the first routing indicator is the BAP address of the first donor-DU.

[0248] (Appendix 44) 44. The method of claim 43, comprising: The route transition configuration further includes: releasing a donor-CU inter-routing indicator rewrite configuration to indicate a mapping relationship between a first routing indicator and a second routing indicator; releasing a routing configuration to indicate a mapping relationship between a second routing indicator and a BAP address of a next hop node of the IAB node; or releasing a second RLC channel mapping configuration to indicate a mapping relationship between an address of a preceding hop node of the IAB node, an entry link RLC channel indicator, and a BAP address of a next hop node of the IAB node and an exit link RLC channel indicator; wherein the first routing indicator and the BAP address of the preceding hop node of the IAB node belong to a network topology domain of the first donor-CU, the destination BAP address of the first routing indicator is the BAP address of the first donor-DU, the second routing indicator and the BAP address of the next hop node of the IAB node belong to a network topology domain of the second donor-CU, and the destination BAP address of the second routing indicator is the BAP address of the second donor-DU.

[0249] (Appendix 45) 45. The method according to claim 43 or 44, further comprising: The IAB node or child node receives configuration information for configuring an IP address anchored to the second donor-DU to be replaced with an IP address anchored to the first donor-DU, wherein the IP address is used for F1 user plane data, F1 control plane data or non-F1 data of the IAB node or child node.

[0250] (Appendix 46) 46. ​​The method of claim 45, The method, wherein the configuration information is IP address configuration information for a BAP address of the first donor-DU.

[0251] (Appendix 47) 47. The method of claim 46, The method, wherein the configuration information is used to change an IP address anchored to the second donor-DU for a BAP address of the first donor-DU to an IP address anchored to the first donor-DU.

[0252] (Appendix 48) 41. The method of claim 40, The method, wherein the transmission path of the uplink service of the IAB node transitions from a first donor-DU of a first donor-CU to a second donor-DU of a second donor-CU, and then transitions from the second donor-DU of the second donor-CU to a third donor-DU of the first donor-CU.

[0253] (Appendix 49) 49. The method according to claim 48, comprising: The method, wherein the path transition configuration is sent by the first donor-CU to the IAB node or child node via an F1AP message or an RRC message.

[0254] (Appendix 50) 49. The method according to claim 48, The path transition configuration includes the following: an increase in a donor-DU inter-routing indicator rewrite configuration to indicate a mapping relationship between a first routing indicator and a third routing indicator; an increase in a routing configuration to indicate a mapping relationship between a third routing indicator and a BAP address of a next hop node of the IAB node; and an increase in a first RLC channel mapping configuration to indicate a mapping relationship between a BAP address of a preceding hop node of the IAB node, an entry link RLC channel indicator, and a BAP address of a next hop node of the IAB node and an exit link RLC channel indicator; the first routing indicator, the third routing indicator, the BAP address of the IAB node's preceding hop node, and the BAP address of the IAB node's next hop node belong to a network topology domain of the first donor-CU, a destination BAP address of the third routing indicator is a BAP address of the third donor-DU, and a destination BAP address of the first routing indicator is a BAP address of the first donor-DU.

[0255] (Appendix 51) 51. The method of claim 50, The route transition configuration further includes: releasing a donor-CU inter-routing indicator rewrite configuration to indicate a mapping relationship between a first routing indicator and a second routing indicator; releasing a routing configuration to indicate a mapping relationship between a second routing indicator and a BAP address of a next hop node of the IAB node; or releasing a second RLC channel mapping configuration to indicate a mapping relationship between an address of a preceding hop node of the IAB node, an entry link RLC channel indicator, and a BAP address of a next hop node of the IAB node and an exit link RLC channel indicator; wherein the first routing indicator and the BAP address of the preceding hop node of the IAB node belong to a network topology domain of the first donor-CU, the destination BAP address of the first routing indicator is the BAP address of the first donor-DU, the second routing indicator and the BAP address of the next hop node of the IAB node belong to a network topology domain of the second donor-CU, and the destination BAP address of the second routing indicator is the BAP address of the second donor-DU.

[0256] (Appendix 52) 52. The method of claim 50 or 51, further comprising: The IAB node or child node receives configuration information for configuring an IP address anchored to the second donor-DU to be replaced with an IP address anchored to the third donor-DU, wherein the IP address is used for F1 user plane data, F1 control plane data or non-F1 data of the IAB node or child node.

[0257] (Appendix 53) 53. The method of claim 52, comprising: The method, wherein the configuration information is IP address configuration information for a BAP address of the first donor-DU.

[0258] (Appendix 54) 54. The method of claim 53, comprising: The method, wherein the configuration information is used to change an IP address for a BAP address of the first donor-DU, anchored to the second donor-DU, to an IP address anchored to the third donor-DU.

[0259] (Appendix 55) 1. A topology regression method comprising the steps of: Transitioning a transmission path of an uplink service of an IAB node from a first donor centralized unit (donor-CU) to a second donor centralized unit, and then transitioning from the second donor centralized unit to the first donor centralized unit; The method comprises: The first donor-CU receives the second donor-CU sending a topology regression request; and The first donor-CU sends a route transition configuration of uplink data; wherein an IAB-DU of the IAB node maintains an F1 connection with the first donor-CU.

[0260] (Appendix 56) 56. The method of claim 55, The method, wherein the transmission path of the uplink service of the IAB node transitions from a first donor distribution unit (donor-DU) of a first donor-CU to a second donor-DU of a second donor-CU, and then transitions from a second donor-DU of the second donor-CU to a first donor-DU of the first donor-CU.

[0261] (Appendix 57) 56. The method of claim 55, The method, wherein the transmission path of the uplink service of the IAB node transitions from a first donor-DU of a first donor-CU to a second donor-DU of a second donor-CU, and then transitions from the second donor-DU of the second donor-CU to a third donor-DU of the first donor-CU.

[0262] (Appendix 58) 58. The method of any one of claims 55 to 57, comprising: The first donor-CU sends the path transition configuration to the IAB node or the child node via an F1AP message or an RRC message.

[0263] (Appendix 59) 59. The method of any one of claims 55 to 58, comprising: the topology regression request includes an IP address anchored to the second donor-DU for the BAP address of the first donor-DU; wherein the IP address is used for F1 user plane data, F1 control plane data or non-F1 data of the IAB node or child node.

[0264] (Appendix 60) 60. The method of any one of claims 55 to 59, further comprising: the first donor-CU transmits to the second donor-CU configuration information for configuring the second donor-CU to replace an IP address anchored to the first donor-DU with an IP address anchored to the second donor-DU, or for configuring the second donor-CU to replace an IP address anchored to the third donor-DU with an IP address anchored to the second donor-DU.

[0265] (Appendix 61) 61. The method of any one of claims 55 to 60, comprising: The first donor-CU sends a path transition configuration of uplink data before or after an IAB-MT of the IAB node is switched from the second donor-CU to the first donor-CU.

[0266] (Appendix 62) 62. The method of claim 61, The second donor-CU sends the topology degrade request to the first donor-CU before sending a switch request for switching the IAB-MT to the first donor-CU.

[0267] (Appendix 63) 62. The method of claim 61, The second donor-CU includes the topology degeneration request in a switch request for switching the IAB-MT to the first donor-CU.

[0268] (Appendix 64) 64. The method of claim 63, comprising: The method, wherein the configuration information is included in an RRC reconfiguration message included in a switching request response message for switching the IAB-MT to the first donor-CU.

[0269] (Appendix 65) 62. The method of claim 61, the second donor-CU sends the topology degrade request to the first donor-CU after sending a switch request for switching the IAB-MT to the first donor-CU.

[0270] (Appendix 66) 61. The method of any one of claims 55 to 60, comprising: The first donor-CU sends a path transition configuration for uplink data after an IAB-MT of the IAB node is re-established to the second donor-CU.

[0271] (Appendix 67) 67. The method of claim 66, comprising: The first donor-CU triggers the second donor-CU to send the topology degeneration request to the first donor-CU.

[0272] (Appendix 68) 61. The method of any one of claims 55 to 60, comprising: The IAB-MT of the IAB node establishes a dual connection with the first donor-CU and the second donor-CU.

[0273] (Appendix 69) 69. The method of claim 68, comprising: The topology degradation request includes identification information of a service whose transmission path is to be migrated from the second donor-CU to the first donor-CU.

[0274] (Appendix 70) An IAB node device, A memory and a processor are included, The storage device stores a computer program, The processor is configured to execute the computer program to implement the topology regression method described in any one of Supplementary Notes 1 to 54. An IAB node device.

[0275] (Appendix 71) 1. An IAB donor device, comprising: A memory and a processor are included, The storage device stores a computer program, 70. An IAB donor device, wherein the processor is configured to execute the computer program to implement the topology regression method of any one of claims 55 to 69.

[0276] (Appendix 72) 1. A communication system comprising: An IAB donor device and an IAB-node device, A communication system, wherein the IAB node device is configured to perform the topology regression method described in any one of Supplementary Notes 1 to 54, and the IAB donor device is configured to perform the topology regression method described in any one of Supplementary Notes 55 to 69.

Claims

1. An IAB node device, the transmission path of the uplink service is transferred from the first donor centralization unit to the second donor centralization unit, and then transferred from the second donor centralization unit to the first donor centralization unit; The apparatus comprises: A receiving unit for receiving a path transition setting of uplink data transmitted by the network device; and a processor for applying the path transition configuration; The IAB-DU of the IAB node maintains an F1 connection with the first donor concentration unit.

2. 2. The apparatus of claim 1, The transmission path of the uplink service of the IAB node transitions from a first donor distribution unit of a first donor concentration unit to a second donor distribution unit of a second donor concentration unit, and then transitions from the second donor distribution unit of the second donor concentration unit to the first donor distribution unit of the first donor concentration unit; The route transition configuration is sent by the first donor concentrator unit to the IAB node or child node via an F1AP message or a radio resource control message.

3. 3. The apparatus of claim 2, The path transition configuration includes: an augmentation of a routing configuration for indicating a mapping relationship between a first routing indicator and a next-hop node backhaul adaptation protocol address of the IAB node; and an augmentation of a first radio link control channel mapping configuration for indicating a mapping relationship between a previous hop node backhaul adaptation protocol address of the IAB node, an ingress link radio link control channel indicator, and a next-hop node backhaul adaptation protocol address of the IAB node and an egress link radio link control channel indicator; the first routing indicator, the previous hop node backhaul adaptation protocol address of the IAB node, and the next hop node backhaul adaptation protocol address of the IAB node belong to a network topology domain of the first donor concentration unit, and a destination backhaul adaptation protocol address of the first routing indicator is a backhaul adaptation protocol address of the first donor distribution unit.

4. 4. The apparatus of claim 3, the receiving unit receives the path transition configuration before the IAB-MT executes a switch from the second donor concentration unit to the first donor concentration unit; The path transition configuration further includes: releasing an inter-donor concentration unit routing indicator rewrite configuration to indicate a mapping relationship between a first routing indicator and a second routing indicator; releasing a routing configuration to indicate a mapping relationship between a second routing indicator and a backhaul adaptation protocol address of a next hop node of the IAB node; or releasing a second radio link control channel mapping configuration to indicate a mapping relationship between an address of a previous hop node of the IAB node, an ingress link radio link control channel indicator, and a next hop node backhaul adaptation protocol address of the IAB node and an egress link radio link control channel indicator; the first routing indicator and the previous hop node backhaul adaptation protocol address of the IAB node belong to a network topology domain of the first donor concentration unit, a destination backhaul adaptation protocol address of the first routing indicator is a backhaul adaptation protocol address of the first donor distribution unit, the second routing indicator and the next hop node backhaul adaptation protocol address of the IAB node belong to a network topology domain of the second donor concentration unit, and a destination backhaul adaptation protocol address of the second routing indicator is a backhaul adaptation protocol address of the second donor distribution unit.

5. 4. The apparatus of claim 3, The receiving unit is further used for receiving configuration information for configuring an IP address anchored to the second donor distribution unit to be replaced with an IP address anchored to the first donor distribution unit, the IP address being used for F1 user plane data, F1 control plane data or non-F1 data of the IAB node or the child node.

6. 6. The apparatus of claim 5, the receiving unit is used to receive the setting information before the IAB-MT performs a switch from the second donor concentration unit to the first donor concentration unit; The processing unit is used to replace an IP address anchored to the second donor distribution unit with an IP address anchored to the first donor distribution unit.

7. 6. The apparatus of claim 5, The configuration information of the IAB node is transmitted by a switching command radio resource control message or a radio resource control reconfiguration message, and the configuration information of the child node is transmitted by a radio resource control reconfiguration message.

8. 6. The apparatus of claim 5, The configuration information is IP address configuration information for a backhaul adaptation protocol address of the first donor distribution unit; The device, wherein the configuration information is used to change an IP address anchored to the second donor distribution unit for a backhaul adaptation protocol address of the first donor distribution unit to an IP address anchored to the first donor distribution unit.

9. 2. The apparatus of claim 1, The transmission path of the uplink service of the IAB node transitions from a first donor distribution unit of a first donor concentration unit to a second donor distribution unit of a second donor concentration unit, and then transitions from the second donor distribution unit of the second donor concentration unit to a third donor distribution unit of the first donor concentration unit; The route transition configuration is sent by the first donor concentrator unit to the IAB node or child node via an F1AP message or a radio resource control message.

10. 10. The apparatus of claim 9, the path transition configuration includes: an augmentation of a donor distribution unit inter-routing indicator rewrite configuration for indicating a mapping relationship between a first routing indicator and a third routing indicator; an augmentation of a routing configuration for indicating a mapping relationship between a third routing indicator and a next-hop node backhaul adaptation protocol address of the IAB node; and an augmentation of a first radio link control channel mapping configuration for indicating a mapping relationship between a previous-hop node backhaul adaptation protocol address of the IAB node, an ingress link radio link control channel indicator, and a next-hop node backhaul adaptation protocol address of the IAB node and an egress link radio link control channel indicator; the first routing indicator, the third routing indicator, the previous hop node backhaul adaptation protocol address of the IAB node, and the next hop node backhaul adaptation protocol address of the IAB node belong to a network topology domain of the first donor concentration unit, the destination backhaul adaptation protocol address of the third routing indicator is a backhaul adaptation protocol address of the third donor distribution unit, and the destination backhaul adaptation protocol address of the first routing indicator is a backhaul adaptation protocol address of the first donor distribution unit.

11. 11. The apparatus of claim 10, the receiving unit receives the path transition configuration before the IAB-MT executes a switch from the second donor concentration unit to the third donor concentration unit; The path transition configuration further includes: releasing an inter-donor concentration unit routing indicator rewrite configuration to indicate a mapping relationship between a first routing indicator and a second routing indicator; releasing a routing configuration to indicate a mapping relationship between a second routing indicator and a backhaul adaptation protocol address of a next hop node of the IAB node; or releasing a second radio link control channel mapping configuration to indicate a mapping relationship between an address of a previous hop node of the IAB node, an ingress link radio link control channel indicator, and a next hop node backhaul adaptation protocol address of the IAB node and an egress link radio link control channel indicator; the first routing indicator and the previous hop node backhaul adaptation protocol address of the IAB node belong to a network topology domain of the first donor concentration unit, a destination backhaul adaptation protocol address of the first routing indicator is a backhaul adaptation protocol address of the first donor distribution unit, the second routing indicator and the next hop node backhaul adaptation protocol address of the IAB node belong to a network topology domain of the second donor concentration unit, and a destination backhaul adaptation protocol address of the second routing indicator is a backhaul adaptation protocol address of the second donor distribution unit.

12. 11. The apparatus of claim 10, The receiving unit is further used for receiving configuration information for configuring an IP address anchored to the second donor distribution unit to be replaced with an IP address anchored to the third donor distribution unit, the IP address being used for F1 user plane data, F1 control plane data or non-F1 data of the IAB node or the child node.

13. 13. The apparatus of claim 12, The receiving unit receives the setting information before the IAB-MT executes a switch from the second donor concentration unit to the first donor concentration unit; The processing unit replaces the IP address anchored to the third donor distribution unit with the IP address anchored to the second donor distribution unit.

14. 13. The apparatus of claim 12, The configuration information of the IAB node is transmitted by a switching command radio resource control message or a radio resource control reconfiguration message, and the configuration information of the child node is transmitted by a radio resource control reconfiguration message.

15. 13. The apparatus of claim 12, The configuration information is an IP address configuration information of a backhaul adaptation protocol address for the first donor distribution unit; The device, wherein the configuration information is used to change an IP address anchored to the second donor distribution unit for a backhaul adaptation protocol address of the first donor distribution unit to an IP address anchored to the third donor distribution unit.

16. 1. An IAB donor device comprising: After the transmission path of the uplink service of the IAB node transitions from a first donor concentration unit to a second donor concentration unit, the transmission path transitions from the second donor concentration unit to the first donor concentration unit; The apparatus comprises: A receiver for receiving the topology regression request transmitted by the second donor concentration unit; and A transmitter for transmitting a route transition configuration of uplink data, The IAB-DU of the IAB node maintains an F1 connection with the first donor concentration unit.

17. 17. The apparatus of claim 16, The sending unit sends the path transition configuration to the IAB node or child node by an F1AP message or a radio resource control message; The topology regression request includes an IP address anchored to the second donor distribution unit for a backhaul adaptation protocol address of the first donor distribution unit, the IP address being used for F1 user plane data, F1 control plane data or non-F1 data of the IAB node or child node.

18. 17. The apparatus of claim 16, The transmitting unit is used for transmitting, to the second donor concentration unit, configuration information for configuring the second donor distribution unit to replace an IP address anchored to the second donor distribution unit with an IP address anchored to the first donor distribution unit, or configuration information for configuring the second donor distribution unit to replace an IP address anchored to the second donor distribution unit with an IP address anchored to a third donor distribution unit.

19. 17. The apparatus of claim 16, The transmitter transmits a route transition configuration of uplink data before or after the IAB-MT of the IAB node switches from the second donor centralization unit to the first donor centralization unit; or The transmitter sends a path transition configuration of uplink data after the IAB-MT of the IAB node is re-established with the second donor concentration unit; or An IAB-MT of the IAB node establishes a dual connection with the first donor concentration unit and the second donor concentration unit.

20. An IAB system, comprising: An IAB donor device and an IAB node device, After the transmission path of the uplink service of the IAB node device transitions from a first donor concentration unit to a second donor concentration unit, the transmission path transitions from the second donor concentration unit to the first donor concentration unit; The IAB node device receives a path transition configuration from the network device sending uplink data, and applies the path transition configuration, during which the IAB node's IAB-DU maintains an F1 connection with the first donor concentration unit.

Citation Information

Patent Citations

  • IAB-node handover in inter-CU migration, recursive f1 and RRC signaling aspects

    WO2021262077A1