IAB Donor Device and Transmission Transition Management Method

Abstract

In an embodiment of the present invention, an IAB donor device and a transmission transition management method are provided, in which an IAB-DU of an IAB node maintains an F1 connection with a first donor-CU and resources are established in a topology of a second donor-CU for serving traffic of the IAB node, the method includes: a first donor-CU sending a first transmission transition change request for the traffic to a second donor-CU; and receiving a transmission transition change response for the traffic sent by the second donor-CU.

Description

[Technical Field]

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

[0002] Future seamless cellular network deployment requires highly flexible and ultra-dense new radio (NR) cell deployment. Ultra-dense networks are one of the goals of 5G, and the deployment of NR networks without wired backhaul is crucial to achieving this. Because 5G millimeter wave reduces cell coverage, wireless self-backhaul systems require multiple hops to meet deployment needs. 5G's high bandwidth, massive multiple-input multiple-output (MIMO), and beam systems make it easier to develop wireless self-backhaul systems for ultra-dense NR cells than LTE. To develop such multi-hop systems with wireless self-backhaul, 3GPP (registered trademark) launched the Integrated Access and Backhaul (IAB) 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 wireless transmission over the NR Uu air interface, and a relay node simultaneously supports the functions of access and backhaul. The relay node multiplexes the access link and backhaul link in the time domain, frequency domain, or spatial domain, and the access link and 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 simultaneously supports access and backhaul functions. The last one-hop access node on the network side is called the IAB-donor, which supports gNB functions and IAB-node access. All UE data can be backhauled to the IAB-donor via the IAB-node by one hop or multiple hops.

[0005] The IAB-node functions are divided into two parts: one part is the gNB-DU function and is called the IAB-DU (Distributed Unit), and the other part is the UE function and is called the IAB-MT (Mobile Equipment). The IAB-DU realizes the functions of network side equipment and is connected to the child IAB-node (child IAB node) of the downstream flow. It provides NR air interface access for the UE and the child IAB-node of the downstream flow and establishes an F1 connection with the IAB donor-CU (Donor Centralized Unit). The IAB-MT realizes part of the functions of terminal equipment and is connected to the parent IAB-node (parent node) or IAB donor-DU of the upstream flow. The IAB-MT includes functions of the physical layer, Layer 2, RRC (Radio Resource Control), and NAS (Non-Access Stratum) layers, and is indirectly connected to the IAB Donor-CU and the core network (CN).

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

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

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

[0009] In the backhaul link, the transport (IP) layer is carried by 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. BAP PDUs (Protocol Data Units) are transmitted over RLC (Radio Link Control) channels of the backhaul link, and multiple RLC channels of the backhaul link may be configured by the IAB-donor to carry traffic (services) with different priorities and QoS (Quality of Service), and the BAP entity maps the BAP PDUs 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 by those skilled in the art, and these technical solutions described in the background art of the present invention 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 inventors have discovered that when a change occurs in the characteristics (or service parameters) of traffic, it may be necessary to change the transmission transition settings of the migrated traffic. For example, when a change occurs in the Quality of Service (QoS) of the traffic, the first donor-CU needs to update the QoS information of the migrated traffic (traffic to be migrated), so that the second donor-CU can determine whether the traffic's new QoS requirements are met and change the resources serving the traffic in the topology of the second donor-CU. However, there is currently no corresponding solution for how to change the transmission transition settings of traffic.

[0012] To address at least one of the above-mentioned problems, embodiments of the present invention provide an IAB donor device and transmission transition management method. [Means for solving the problem]

[0013] According to one aspect of an embodiment of the present invention, there is provided a transmission transition management method, in which an IAB-DU of an IAB node maintains an F1 connection with a first donor concentration unit (donor-CU), and resources for serving traffic of the IAB node are established in a topology of a second donor-CU, the method comprising: The first donor-CU sends a first transmission transition change request for the traffic to the second donor-CU; and The first donor-CU receives a transmission transition change response for the traffic transmitted by the second donor-CU.

[0014] According to another aspect of an embodiment of the present invention, there is provided a transmission transition management method, in which an IAB-DU of an IAB node maintains an F1 connection with a first donor concentration unit (donor-CU), and resources for serving traffic of the IAB node are established in a topology of a second donor-CU, the method comprising: the second donor-CU receives a first transmission transition change request for the traffic transmitted by the first donor-CU; and The second donor-CU sends a transmission transition change response for the traffic to the first donor-CU.

[0015] According to another aspect of an embodiment of the present invention, there is provided a transmission transition management method, in which an IAB-DU of an IAB node maintains an F1 connection with a first donor-CU, and resources for serving traffic of the IAB node are established in a topology of a second donor-CU, the method comprising: The second donor-CU sends a second transmission transition change request for traffic to the first donor-CU; and The second donor-CU modifies resources serving the traffic in the topology of the second donor-CU.

[0016] According to another aspect of an embodiment of the present invention, there is provided a transmission transition management method, in which an IAB-DU of an IAB node maintains an F1 connection with a first donor-CU, and resources for serving traffic of the IAB node are established in a topology of a second donor-CU, the method comprising: receiving a second transmission transition change request for traffic transmitted by the second donor-CU by the first donor-CU; Wherein, the second donor-CU changes the resources serving the traffic in the topology of the second donor-CU.

[0017] According to another aspect of an embodiment of the present invention, there is provided an IAB donor device, in which an IAB-DU of an IAB node maintains an F1 connection with a first donor concentration unit (donor-CU), and resources are established for serving traffic of the IAB node in a topology of a second donor-CU, the device comprising: a transmitter for transmitting a first transmission transition change request for the traffic to the second donor-CU; and A receiver for receiving a transmission transition change response for the traffic of the second donor-CU transmission is also included.

[0018] According to another aspect of an embodiment of the present invention, there is provided an IAB donor device, in which an IAB-DU of an IAB node maintains an F1 connection with a first donor concentration unit (donor-CU), and resources are established for serving traffic of the IAB node in a topology of a second donor-CU, the device comprising: a receiver for receiving a first transmission transition change request for the traffic of the first donor-CU transmission; and A transmitter for transmitting a transmission transition change response for the traffic to the first donor-CU is included.

[0019] According to another aspect of an embodiment of the present invention, there is provided an IAB donor device, in which an IAB-DU of an IAB node maintains an F1 connection with a first donor-CU, and resources are established in a topology of a second donor-CU for serving traffic of the IAB node, the device comprising: a sender for sending a second transmission transition change request for traffic to the first donor-CU; and The second donor-CU includes a processing unit that changes resources serving the traffic in the topology of the second donor-CU.

[0020] According to another aspect of an embodiment of the present invention, there is provided an IAB donor device, in which an IAB-DU of an IAB node maintains an F1 connection with a first donor-CU, and resources are established in a topology of a second donor-CU for serving traffic of the IAB node, the device comprising: a receiving unit for receiving a second transmission transition change request for traffic transmitted by the second donor-CU; Wherein, the second donor-CU changes the resources serving the traffic in the topology of the second donor-CU.

[0021] According to another aspect of an embodiment of the present invention, there is provided an IAB system, comprising a first donor concentration unit and a second donor concentration unit; the first donor concentrating unit sending a first transmission shift change request for traffic and receiving a transmission shift change response for the traffic, and the second donor concentrating unit receiving the first transmission shift change request and sending the transmission shift change response; or The second donor concentration unit sends a second transmission shift change request for the traffic and changes the resources serving the traffic in the topology of the second donor concentration unit, and the first donor concentration unit receives the second transmission shift change request. [Effects of the Invention]

[0022] The advantageous effects of the embodiment of the present invention are at least as follows: a first donor-CU sends a first transmission transition change request for traffic to a second donor-CU, and the first donor-CU receives a transmission transition change response for the traffic sent by the second donor-CU, so that the second donor-CU can change the transmission resources serving the transition traffic based on the change (change) in the service parameters of the traffic, so that the service requirements of the traffic can still be met after the change in the service parameters of the traffic.

[0023] The following description and reference to the drawings disclose in detail particular embodiments of the present invention, illustrating ways in which the principles of the present invention may be employed, but the scope of the present invention is not limited thereto, and various changes, modifications, and alternatives may be included within the scope of the appended claims.

[0024] Additionally, features described and / or illustrated with respect to 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.

[0025] It should be noted that when used in this specification, terms such as "comprise / have" 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 explanation of the drawings]

[0026] 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 several drawings and to indicate corresponding parts used in several embodiments.

[0027] 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 embodiments of the present invention, and together with the written description, serve to explain the principles of the present invention. Also, it is apparent that the drawings described below are only for illustrating some embodiments of the present invention, and those skilled in the art can derive other drawings based on these drawings without any creative effort. [Figure 1] FIG. 1 illustrates an IAB system. [Figure 2] FIG. 1 illustrates the IAB architecture in SA mode. [Figure 3] FIG. 1 illustrates an IAB architecture in EN-DC mode. [Figure 4] FIG. 1 is a diagram showing a parent node (parent IAB-node) and a child node (child IAB-node). [Figure 5] FIG. 1 illustrates the F1-U protocol stack of the IAB system. [Figure 6]FIG. 1 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. 10 is a diagram illustrating an example of a transmission transition in an embodiment of the present invention. [Figure 10] FIG. 2 illustrates a transmission transition management method according to an embodiment of the present invention. [Figure 11] FIG. 10 is a diagram showing the signaling flow of a transmission transition change in an embodiment of the present invention. [Figure 12] FIG. 10 illustrates another transmission transition management method in an embodiment of the present invention. [Figure 13] FIG. 10 illustrates another transmission transition management method in an embodiment of the present invention. [Figure 14] FIG. 10 is a diagram showing another signaling flow of a transmission transition change in an embodiment of the present invention. [Figure 15] FIG. 10 illustrates another transmission transition management method in an embodiment of the present invention. [Figure 16] FIG. 1 illustrates an IAB donor device in accordance with an embodiment of the present invention. [Figure 17] FIG. 10 illustrates another IAB donor device in accordance with an embodiment of the present invention. [Figure 18] FIG. 10 illustrates another IAB donor device in accordance with an embodiment of the present invention. [Figure 19] FIG. 10 illustrates another IAB donor device in accordance with an embodiment of the present invention. [Figure 20] FIG. 1 illustrates an IAB device in accordance with an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0028] The foregoing and other features of the present invention will become more apparent from a consideration of the accompanying drawings and the following description. While the specification and drawings disclose particular embodiments of the present invention, they illustrate only some of the embodiments which 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, but rather includes all modifications, variations, and alternatives which fall within the scope of the appended claims.

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

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

[0031] In an embodiment of the present invention, the term "network equipment" refers to, for example, a device in a communication system that connects a terminal device to a communication network and provides services to the terminal device. The network equipment may include, but is not limited to, a "node" and / or a "donor" under the IAB architecture, 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.

[0032] 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), etc., 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 these functions, and each base station can provide communication coverage for a specific geographic area. For example, a 5G base station gNB may include one gNB CU and one or more gNB DUs, where a CU / DU is a logical node of the gNB that has some of the functions of a gNB. The term "cell" may refer to a base station and / or the area it covers, depending on the context in which the term is used.

[0033] 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 network equipment. The user equipment may be fixed or mobile, and may also be referred to as a mobile station (MS), terminal, subscriber station (SS), access terminal (AT), station, etc. For example, it is a terminal equipment served by an IAB node or an IAB donor under the IAB architecture.

[0034] Among these, user equipment may include, but is not limited to, cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, mobile devices, machine-type communication devices, laptop computers, cordless phones, smartphones, smart watches, digital cameras, etc.

[0035] Furthermore, for example, in a scenario such as the Internet of Things (IoT), the user equipment may also be a monitoring or measuring device or apparatus, for example, 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.

[0036] The routing function of the IAB system is realized by the BAP layer, and each IAB-node stores a routing configuration (BH routing configuration) and an RLC channel mapping configuration (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 ID (ID).

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

[0038] Figure 7 is a diagram illustrating 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 using the routing ID in the data packet header. The BAP address of the previous hop node and the ingress link RLC channel ID are all known. After the BAP address of the next hop node is determined, the egress link RLC channel ID can be found through the RLC channel mapping configuration based on the BAP address of the previous hop node + ingress link RLC channel ID + BAP address of the next hop node.

[0039] The IAB-donor DU stores the routing configuration (BH routing configuration) and downlink RLC channel mapping configuration (Downlink Traffic to BH RLC Channel Mapping Configuration). The IAB-donor DU performs routing based on the routing configuration, 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 next-hop node address. The downlink RLC channel mapping configuration includes the mapping relationship between the target IP address, DSCP (Differentiated Services Code Point), and next-hop node address and the egress link RLC channel ID.

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

[0041] The access IAB node stores uplink backhaul information (BH information), which includes the routing ID used by the traffic, the uplink backhaul RLC channel ID, and the next-hop node address. The access IAB node sets the routing ID in the BAP layer data packet header of the uplink traffic based on the uplink BH information, and selects the BH RLC channel and next-hop node for transmitting the uplink traffic.

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

[0043] Figure 8 illustrates intra-CU topology adaptation. When an 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 RRC reconfiguration information, allowing the IAB node to transition its F1 transmission path.

[0044] The route transition related configurations include updating the default backhaul RLC channel for uplink F1-C, F1-U and non-F1 data, updating the default BH RLC channel, and updating the IP address for routing to the Donor-DU. When the IAB-node accesses a new parent node, it starts applying the above route transition related configurations, and the IAB-node's child nodes also perform route transition related configurations in the same way.

[0045] 3GPP Rel-17 supports network topology updates and backhaul (BH) radio link failure (RLF) recovery processes when an IAB-node moves under a different donor-CU. The IAB-node can switch or re-establish a connection from the parent node serving the source donor-CU (also referred to as the F1-terminating CU or first donor-CU) to the parent node serving the target donor-CU (also referred to as the non-F1-terminating CU or second donor-CU). All of the IAB-node's traffic (and that of its child nodes) must be migrated to the topology of the non-F1-terminating CU. Rel-17 also supports a topology redundancy process when an IAB-node establishes a dual connection with a non-F1-terminating CU. Some of the IAB-node's traffic transmission paths can be migrated to the topology of the non-F1-terminating CU.

[0046] After the IAB-node switches / RLF restores from donor-CU1 (F1-terminating CU) to donor-CU2 (non-F1-terminating CU), or after the RRC connection with donor-CU2 increases, only the RRC connection of the IAB-MT goes to donor-CU2, and the F1 interface still terminates on donor-CU1. At this time, the IAB-node may be referred to as a boundary node. The RRC connections of its serving child nodes and UEs still belong to donor-CU1, and the F1 interfaces of the child nodes also terminate on donor-CU1, so the boundary node's child nodes still belong to the topology of donor-CU1.

[0047] To ensure that the child node's uplink traffic is transmitted in the donor-CU2 topology, the boundary node must replace the routing ID belonging to the donor-CU1 topology (the destination address is the donor-DU BAP address of donor-CU1) with the routing ID belonging to the donor-CU2 topology (the destination address is the donor-DU BAP address of donor-CU2). To ensure that the child node's downlink traffic is transmitted in the donor-CU2 topology, the boundary node must replace the routing ID belonging to the donor-CU2 topology (the destination address is the donor DU BAP address of donor-CU2) with the routing ID belonging to the donor-CU1 topology (the destination address is the donor DU BAP address of donor-CU1). In addition, the boundary node's own uplink traffic must be updated to the routing ID belonging to the donor-CU2 topology.

[0048] 9 is a diagram illustrating transmission transition in an embodiment of the present invention. As shown in FIG. 9, the IAB-MT of IAB node 3 is transitioned from donor-CU1 to donor-CU2. When the traffic of the child node is transitioned to the topology of donor-CU2, the network device can set the mapping relationship of the routing ID between the topologies (e.g., BAP Header Rewriting information) in the boundary node.

[0049] When the boundary node forwards uplink data to the parent node in the topology of donor-CU2, it needs to replace the routing ID belonging to donor-CU1 with the routing ID belonging to donor-CU2, and then perform routing selection and BH RLC channel selection based on the replaced routing ID. Therefore, the network device can set up a routing table belonging to the topology of donor-CU2 (before switching, only the routing table of the topology of donor-CU1 is set up in the boundary node) and a BH RLC channel mapping table from the topology of donor-CU1 to the topology of donor-CU2 in the boundary node.

[0050] Similarly, when forwarding downlink data, routing and BH RLC channel selection need to be performed based on the replaced routing ID, so the network device can configure a downlink BH RLC channel mapping table from the topology of donor-CU2 to the topology of donor-CU1 in the boundary node.

[0051] When traffic from the boundary node is migrated to the topology of donor-CU2, the network device needs to configure uplink backhaul information belonging to the topology of donor-CU2 in the boundary node, including a routing ID, an uplink backhaul RLC channel ID, and a next-hop node address.

[0052] When transferring some or all of the traffic to the donor-CU2 topology, resources for serving the traffic must be established in the donor-CU2 topology, e.g., by configuring a backhaul BH RLC channel and / or BAP sublayer routing for the traffic on a path in the donor-CU2 topology.

[0053] Donor-CU1 sends a transmission transition establishment request to donor-CU2 to set up a routing table belonging to donor-CU2's topology and a BH RLC channel mapping table between the topologies of the two donor-CUs in the boundary node, and to establish resources for serving transition traffic in donor-CU2's topology.

[0054] Donor-CU1 sends to donor-CU2 the following information of the traffic flow to be traversed for each request and the IP address request (including the donor-DU BAP address and the IP address anchored to the donor-DU in donor-CU1's topology): - Traffic signs; - Traffic quality of service (QoS) information or traffic type and - In addition, for the traffic flow of the child node, it is necessary to further transmit the routing ID and BH RLC channel in the topology of donor-CU1 (including the egress routing ID and egress BH RLC channel for downlink traffic, and the ingress routing ID and ingress BH RLC channel for uplink traffic).

[0055] Donor-CU2 sends donor-CU1 the following information (for each traffic flow) and IP address response (including the donor-DU BAP address in donor-CU1's topology and the IP address anchored to donor-DU of donor-CU2): - Traffic signs; - the routing ID and BH RLC channel of the traffic in the topology of donor-CU2 (including the ingress routing ID and ingress BH RLC channel of the downlink traffic, or the egress routing ID and egress BH RLC channel of the uplink traffic); - The BAP address of the previous hop in the topology of donor-CU2 for downlink traffic; - the BAP address of the next hop in the topology of donor-CU2 for uplink traffic; and - QoS mapping information used by downlink traffic (e.g., DSCP or IPv6 flow label) is.

[0056] In the embodiments of the present invention, unless otherwise specified, the IAB node device includes a transition node or its child node. Also, "resources for serving the traffic of the IAB node have already been established in the topology of the donor-CU" may be expressed as "traffic of the IAB node has been transitioned to the topology of the donor-CU," and the present invention is not limited to these expressions. The following describes the embodiments of the present invention in further detail.

[0057] <Example of the first aspect> In an embodiment of the present invention, a transmission transition management method is provided, which is described starting from a first donor centralization unit (donor-CU), in which an IAB node's IAB-DU maintains an F1 connection with a first donor centralization unit (donor-CU), and resources for serving the traffic of the IAB node in the topology of a second donor-CU have already been established.

[0058] 10 is a diagram illustrating a transmission transition management method according to an embodiment of the present invention. As shown in FIG. 10, the method includes the following steps:

[0059] 1001: A first donor-CU sends a first transmission transition change request for traffic to a second donor-CU; and 1002: The first donor-CU receives a transmission transition change response for the traffic sent by the second donor-CU.

[0060] Note that the above-described FIG. 10 is merely for illustrative purposes of an embodiment of the present invention, and the present invention is not limited thereto. For example, the execution order of each operation (step) can be appropriately adjusted, or some operations can be added or removed. Those skilled in the art can make appropriate modifications based on the above content without being limited to the description of the above-described FIG. 10.

[0061] In some embodiments, the IAB-MT of the IAB node maintains an RRC connection with the second donor-CU, e.g., the IAB-MT of the transition node maintains an RRC connection with the second donor-CU, or the IAB-MT of the IAB node maintains an RRC connection with the first donor-CU, e.g., a child node of the transition node maintains an RRC connection with the first donor-CU.

[0062] In some embodiments, the traffic includes one or a combination of the following: F1 control plane (F1-C) traffic, F1 user plane (F1-U) traffic, and non-F1 traffic, although embodiments of the present invention are not limited thereto.

[0063] In some embodiments, a first donor-CU sends a first transmission transition change request to a second donor-CU to request a change in resources serving the traffic in the topology of the second donor-CU.

[0064] For example, when a change occurs in the service parameters of the traffic, the first donor-CU sends a first transmission transition change request to the second donor-CU to request a change in resources serving the traffic in the topology of the second donor-CU. For example, the service parameters include QoS (user plane traffic) and / or traffic type (non-user plane traffic). The first transmission transition change request includes the following information: the traffic indicator of the traffic, the Quality of Service (QoS) of the traffic, and / or the traffic type.

[0065] In some embodiments, the first donor-CU receives a transmission transition change response from the second donor-CU to change resources serving the traffic within the second donor-CU's topology.

[0066] For example, the transmission transition change response includes the following information: a traffic indicator of the traffic, and BH information in the topology of the second donor-CU of the traffic.

[0067] In some embodiments, the BH information in the topology of the second donor-CU includes at least one of the following: Ingress routing indicator (routing ID) for downlink traffic; Ingress BH RLC channel for downlink traffic; The BAP address of the previous hop for downlink traffic; and QoS mapping information for downlink traffic.

[0068] In some embodiments, the BH information in the topology of the second donor-CU includes at least one of the following: Egress routing indicator (routing ID) for uplink traffic; egress BH RLC channel for uplink traffic; and This is the BAP address of the next hop for uplink traffic.

[0069] In some embodiments, the first donor-CU sends the first transport migration change request via first transport migration management request information and / or the first donor-CU receives the transport migration change response via transport migration management response information, although the present invention is not limited thereto and the transport migration change request and / or transport migration change response may carry other information.

[0070] This allows the first transmission transition change request and the transmission transition change response to be used to change the transmission resources serving the transition traffic based on the change (change) in the service parameters of the traffic, so that the service requirements of the traffic can still be met after the service parameters of the traffic have changed.

[0071] The following further describes the case after the first donor-CU receives a transmission transition change response for the traffic.

[0072] In some embodiments, after receiving the transmission transition change response for the traffic, the first donor-CU configures, for example, for the traffic of an IAB node, the IAB node to update the uplink BH information of the traffic.

[0073] In some embodiments, after receiving the transmission transition change response for the traffic, the first donor-CU configures at least one of the following updates in the IAB node, for example, for the uplink traffic of the child node: BAP header rewrite information between topologies in the uplink direction, routing information in the topology of the second donor-CU, and BH RLC channel mapping information between topologies in the uplink direction.

[0074] In some embodiments, after receiving the transmission transition change response for the traffic, the first donor-CU configures at least one of the following updates in the IAB node, for example, for the downlink traffic of the child node: BAP header rewrite information between topologies in the downlink direction, and BH RLC channel mapping information between topologies in the downlink direction.

[0075] The above has explained the case of settings related to layer 2 (L2), but below we will explain the case of IP addresses.

[0076] In some embodiments, a first donor-CU sends a first transport migration change request to a second donor-CU to request a change of IP address for the IAB node.

[0077] For example, if the routing identifier (routing ID) and / or donor distribution unit (donor-DU) in the topology of a first donor-CU for a child node's traffic changes, the first donor-CU sends a first transmission migration change request to a second donor-CU to request a change of IP address for the child node.

[0078] In some embodiments, the first transmission transition change request is included in first transmission transition management request information.

[0079] In some embodiments, the first transmission migration change request includes the following information: an IAB node identifier or IP address request index, and a BAP address of a donor-DU in the topology of the first donor-CU. Optionally, the IP address request may further include an IP address anchored to the donor-DU.

[0080] In some embodiments, the first donor-CU receives the second donor-CU sending a transport transition change response to change the IP address for the IAB node.

[0081] In some embodiments, the transport transition change response is included in transport transition management response information.

[0082] In some embodiments, the transmission migration change response includes the following information: an IAB node identifier or IP address request index, a BAP address of the donor-DU in the topology of the first donor-CU, and an IP address anchored to the donor-DU in the topology of the second donor-CU.

[0083] In some embodiments, after receiving the transmission transition change response for the IAB node, the first donor-CU configures the IAB node with an IP address anchored to the donor-DU in the topology of the second donor-CU.

[0084] In an embodiment of the present invention, 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 invention is not limited thereto.

[0085] The above describes the case where the second donor-CU receives the transmission transition change request. The second donor-CU determines that it cannot accept the transmission transition change request, for example, it can reject the transmission transition change request if the QoS requirements of the traffic cannot be met after the change.

[0086] In some embodiments, the first donor-CU receives a transmission transition response from the second donor-CU to deny the first transmission transition request for the traffic.

[0087] For example, the first donor-CU receives the transmission transition change response through transmission transition management response information, and for example, the transmission transition management response information includes a traffic indicator of the traffic.

[0088] The transmission transition change process initiated by the first donor-CU through signaling interaction will be further described below.

[0089] 11 is a flowchart illustrating a signaling process for a transmission transition change in an embodiment of the present invention. For example, when a change occurs in the QoS of traffic, donor-CU1 needs to change the QoS of the transition traffic, and donor-CU1 requests a change in the QoS of the transition traffic.

[0090] donor-CU1 sends to donor-CU2 via a TRANSPORT MIGRATION MANAGEMENT REQUEST or TRANSPORT MIGRATION MODIFICATION REQUEST message at least one of the following information (for each traffic flow for which modification is requested): -- traffic signs; and -- QoS information of traffic or traffic type.

[0091] After the QoS change of the traffic, the routing ID in the topology of donor-CU1 of the traffic and the donor-DU in the topology of donor-CU1 may also change, so it may further send IP address requests (e.g., which may be included in the above request information) for the boundary node and child nodes, which may include the following: -- Node identification or IP address request index; and --IP address request (including the new donor-DU BAP address in donor-CU1's topology), which may optionally further include the IP address anchored to that donor-DU.

[0092] - donor-CU2 receives the transmission transition change request and updates the BH RLC channel and routing on the path in donor-CU2's topology of the traffic based on the changed QoS of the traffic, and donor-CU2 may change the routing ID or BH RLC channel in donor-CU2's topology of the traffic, or downlink QoS mapping information (e.g., DSCP value or IPv6 flow label).

[0093] donor-CU2 may send to donor-CU1 by means of a TRANSPORT MIGRATION MANAGEMENT RESPONSE or TRANSPORT MIGRATION MODIFICATION RESPONSE message at least one of the following information (for each traffic flow for which modification is requested): -- Traffic signs; -- the routing ID and BH RLC channel in the topology of traffic donor-CU2 (including the ingress routing ID and ingress BH RLC channel of downlink traffic, or the egress routing ID and egress BH RLC channel of uplink traffic); -- BAP address of the previous hop in the topology of donor-CU2 for downlink traffic; -- the BAP address of the next hop in donor-CU2's topology for uplink traffic; and -- QoS mapping information used by downlink traffic (e.g., DSCP or IPv6 flow label).

[0094] When donor-CU2 receives the IP address request, it must further send an IP address response (which may be included in the response information described above, for example), which includes: -- Node identification or IP address request index; and -- IP address response (including the new donor-DU BAP address in donor-CU1's topology and the IP address of the donor-DU anchored to donor-CU2).

[0095] If donor-CU2 determines that the QoS requirements of the traffic cannot be met after the change, it can reject the transmission shift change request, and donor-CU2 sends a traffic indication to donor-CU1 rejecting the change.

[0096] - When donor-CU2 sends a successful transmission transition change response to donor-CU1, donor-CU1 must make the following updates based on the information sent by donor-CU2: -- donor-CU1 updates the traffic QoS mapping information; -- Update L2 configuration information, including: --- For the traffic of the transition node, donor-CU1 configures the transition node to update the uplink BH information of the traffic; and --- For the traffic of the child node, donor-CU1 configures the transition node to update the BAB header rewrite information between topologies, the routing table belonging to donor-CU2's topology, and the BH RLC channel mapping table between the two topologies; -- If an IP address response is received, donor-CU1 further updates the IP addresses of the transition node and / or child node according to the RRC reconfiguration information.

[0097] Although the above description has been given taking QoS change as an example, the present invention is not limited to this.

[0098] Also, for example, donor-CU1 needs to change donor-DU in the topology of traffic donor-CU1, or the donor-DU has changed due to a change in routing ID in the topology of traffic donor-CU1.

[0099] - donor-CU1 sends an IP address request to donor-CU2, which includes: -- Node ID or IP address request index; --IP address request (including new donor-DU BAP address in donor-CU1's topology), and optionally may further include the IP address anchored to that donor-DU.

[0100] - donor-CU2 sends an IP address response to donor-CU1, which contains: -- Node identification or IP address request index; and -- IP address response (including the new donor-DU BAP address in donor-CU1's topology and the IP address of the donor-DU anchored to donor-CU2).

[0101] The above signaling process is illustrative of an embodiment of the present invention, but the present invention is not limited thereto. For more specific details of the signaling, please refer to the related art. For example, the execution order of each operation may be changed, or some operations may be added or removed. Those skilled in the art can make appropriate modifications based on the above content, without being limited to the description of FIG. 11.

[0102] In some embodiments, when the IAB-MT of an IAB node is switched from a first donor-CU to a second donor-CU and resources for serving one or more traffics of the IAB node (including transition nodes and child nodes) have been determined in the topology of the second donor-CU, the first donor-CU sends a first transmission transition change request for one or more traffics.

[0103] For example, the transmission migration change process initiated by donor-CU1 can be performed after the migration node is switched from a parent node under an F1-terminating CU to a parent node under a non-F1-terminating CU, and all traffic is migrated to the topology of the non-F1-terminating CU.

[0104] In some embodiments, when the IAB-MT of an IAB node is re-established from a first donor-CU to the second donor-CU and resources for serving one or more traffics of the IAB node (including transition nodes and child nodes) are determined in the topology of the second donor-CU, the first donor-CU sends a first transmission transition change request for one or more traffics.

[0105] For example, the transmission migration change process initiated by donor-CU1 can occur after the migration node is re-established from the parent node under the F1-terminating CU to the parent node under the non-F1-terminating CU, and all traffic is migrated to the topology of the non-F1-terminating CU.

[0106] In some embodiments, when the IAB-MT of an IAB node establishes a dual connection with a first donor-CU and a second donor-CU, and resources for serving one or more traffics of an IAB node (including transition nodes and child nodes) have been determined in the topology of the second donor-CU, the first donor-CU sends a first transmission transition change request for one or more traffics.

[0107] For example, the transmission migration change process initiated by donor-CU1 can be performed after the migration node establishes dual connections with F1-terminating CUs and non-F1-terminating CUs, and the transmission path diameter of some traffic is migrated to the topology of the non-F1-terminating CU.

[0108] The above-described embodiments are merely illustrative of the present invention, and the present invention is not limited thereto. Appropriate modifications can be made based on the above-described embodiments. For example, each of the above-described embodiments may be used alone, or a plurality of the above-described embodiments may be used in combination.

[0109] As can be seen from the above embodiment, the first donor-CU sends a first transmission transition change request for traffic to the second donor-CU, and the first donor-CU receives a transmission transition change response for the traffic sent by the second donor-CU, so that the second donor-CU can change the transmission resources serving the transition traffic based on the change (change) in the service parameters of the traffic, so that the service requirements of the traffic can still be met after the service parameters of the traffic change.

[0110] <Example of the second aspect> In an embodiment of the present invention, a transmission transition management method is provided, which will be described starting from the second donor-CU. The same content as in the embodiment of the first aspect will be omitted. In this embodiment, the IAB-DU of the IAB node maintains an F1 connection with the first donor-CU, and resources for serving the traffic of the IAB node are established within the topology of the second donor-CU.

[0111] 12 is a diagram illustrating another transmission transition management method in an embodiment of the present invention. As shown in FIG. 12, the method includes the following steps:

[0112] 1201: A second donor-CU receives a first transmission transition change request for traffic transmitted by a first donor-CU; and 1202: The second donor-CU sends a transmission transition change response for the traffic to the first donor-CU.

[0113] Note that the above-described FIG. 12 is provided for illustrative purposes only to explain an embodiment of the present invention, and the present invention is not limited thereto. For example, the execution order of each operation may be appropriately adjusted, or some operations may be added or removed. Those skilled in the art may make appropriate modifications based on the above content, without being limited to the description of FIG. 12.

[0114] In some embodiments, an IAB-MT of the IAB node maintains an RRC connection with the second donor-CU, or an IAB-MT of the IAB node maintains an RRC connection with the first donor-CU.

[0115] In some embodiments, the traffic includes a combination of at least one or more of the following: F1 control plane (F1-C) traffic, F1 user plane (F1-U) traffic, and non-F1 traffic.

[0116] In some embodiments, the second donor-CU receives a first transmission transition change request from the first donor-CU to request a change in resources serving the traffic within the topology of the second donor-CU.

[0117] For example, if the service parameters of the traffic change, the second donor-CU receives a first transmission transition change request from the first donor-CU to request a change in resources serving the traffic within the topology of the second donor-CU.

[0118] In some embodiments, the second donor-CU receives the first transport migration change request through first transport migration management request information.

[0119] In some embodiments, the first transmission transition change request includes information such as: a traffic signature of the traffic, a quality of service (QoS) of the traffic, and / or a traffic type.

[0120] In some embodiments, the second donor-CU updates the QoS mapping information of the traffic after receiving the first transmission transition change request.

[0121] In some embodiments, after receiving the first transmission transition change request, the second donor-CU updates the traffic L2-related configuration, which includes at least one of the following: A backhaul (BH) radio link control (RLC) channel and / or BAP sublayer routing used on a path within the topology of the second donor-CU; uplink BH information of the traffic (wherein the uplink BH information includes a routing indicator, an uplink BH RLC channel, and / or a BAP address of a next-hop node); an uplink egress routing indicator, an egress BH RLC channel, and / or a BAP address of a next-hop node for said traffic; or The traffic's downlink ingress routing indicator, ingress BH RLC channel, and / or BAP address of the previous hop node.

[0122] In some embodiments, the second donor-CU sends a transmission transition change response to the first donor-CU to change the resources serving the traffic in the topology of the second donor-CU.

[0123] In some embodiments, the second donor-CU sends the transport migration change response via a transport migration management response.

[0124] In some embodiments, the transmission transition change response includes the following information: a traffic indicator of the traffic, and BH information in the topology of the second donor-CU of the traffic.

[0125] In some embodiments, the BH information in the topology of the second donor-CU includes at least one of the following: Ingress routing indicator (routing ID) for downlink traffic; Ingress BH RLC channel for downlink traffic; The BAP address of the previous hop for downlink traffic; and QoS mapping information for downlink traffic.

[0126] In some embodiments, the BH information in the topology of the second donor-CU includes at least one of the following: Egress routing indicator (routing ID) for uplink traffic; egress BH RLC channel for uplink traffic; and This is the BAP address of the next hop for uplink traffic.

[0127] In some embodiments, the second donor-CU receives the first donor-CU sending a first transmission transition change request to request a change of IP address for the IAB node.

[0128] For example, if the routing ID and / or donor distribution unit (donor-DU) in the topology of the first donor-CU of the traffic changes, the second donor-CU receives a first transmission transition change request to request a change of IP address for the IAB node of the first donor-CU transmission.

[0129] In some embodiments, the first transmission transition change request is included in first transmission transition management request information.

[0130] In some embodiments, the first transmission migration change request includes the following information: an IAB node identifier or IP address request index, and a BAP address of a donor-DU in the topology of the first donor-CU.

[0131] In some embodiments, the first transmission migration change request further includes an IP address anchored to the donor-DU.

[0132] In some embodiments, the second donor-CU sends a transport migration change response to the first donor-CU to change the IP address for the IAB node.

[0133] In some embodiments, the transmission change response is included in transmission transition management response information.

[0134] In some embodiments, the transmission change response includes the following information: an IAB node identifier or IP address request index, a BAP address of a donor-DU in the topology of the first donor-CU, and an IP address anchored to the donor-DU in the topology of the second donor-CU.

[0135] In some embodiments, the second donor-CU, after receiving the first transmission transition change request, rejects the first transmission transition change request for the traffic.

[0136] For example, if the Quality of Service (QoS) of the traffic cannot be satisfied, the second donor-CU rejects the first transmission transition change request for the traffic after receiving the first transmission transition change request.

[0137] In some embodiments, the second donor-CU sends a transmission shift change response to the first donor-CU to deny the transmission shift change request for the traffic.

[0138] In some embodiments, the second donor-CU sends the transmission transition change response with transmission transition management information.

[0139] In some embodiments, the transmission transition change response includes a traffic indication for the traffic.

[0140] The above-described embodiments are merely illustrative of the present invention, but the present invention is not limited thereto, and appropriate modifications can be made based on the above-described embodiments. For example, each of the above-described embodiments may be used alone, or a combination of two or more of the above-described embodiments may be used.

[0141] As can be seen from the above embodiment, the first donor-CU sends a first transmission transition change request for traffic to the second donor-CU, and the first donor-CU receives a transmission transition change response for the traffic sent by the second donor-CU, so that the second donor-CU can change the transmission resources serving the transition traffic based on the change (change) in the service parameters of the traffic, so that the service requirements of the traffic can still be met after the change in the service parameters of the traffic.

[0142] <Example of the third aspect> In an embodiment of the present invention, a transmission transition management method is provided, which is described starting from a second donor centralization unit (donor-CU), in which an IAB node's IAB-DU maintains an F1 connection with a first donor centralization unit (donor-CU), and resources are established in the topology of the second donor-CU to serve the traffic of the IAB node.

[0143] 13 is a diagram illustrating a transmission transition management method according to an embodiment of the present invention. As shown in FIG. 13, the method includes the following steps:

[0144] 1301: A second donor-CU sends a second transmission transition change request for traffic to a first donor-CU; and 1302: The second donor-CU changes the resources serving the traffic in the topology of the second donor-CU.

[0145] Note that, although the above-mentioned FIG. 13 is an illustrative example of an embodiment of the present invention, the present invention is not limited thereto. For example, the execution order of each operation may be appropriately adjusted, or some operations may be added or removed. Those skilled in the art may make appropriate modifications based on the above content without being limited to the description of the above-mentioned FIG. 13.

[0146] In some embodiments, the IAB-MT of the IAB node maintains an RRC connection with the second donor-CU, e.g., the IAB-MT of the transition node maintains an RRC connection with the second donor-CU, or the IAB-MT of the IAB node maintains an RRC connection with the first donor-CU, e.g., a child node of the transition node maintains an RRC connection with the first donor-CU.

[0147] In some embodiments, the traffic includes at least one or a combination of the following: F1 control plane (F1-C) traffic, F1 user plane (F1-U) traffic, and non-F1 traffic, although embodiments of the present invention are not limited thereto.

[0148] In some embodiments, the second donor-CU sends the second transmission transition change request to the first donor-CU to request a change in the routing ID and / or BH RLC channel of the traffic in the topology of the second donor-CU.

[0149] In some embodiments, the second transmission transition change request includes the following information: a traffic indicator of the traffic, and BH information in the topology of the second donor-CU of the traffic.

[0150] In some embodiments, the BH information in the topology of the second donor-CU includes at least one of the following: Egress routing indicator (routing ID) for uplink traffic; egress BH RLC channel for uplink traffic; and This is the BAP address of the next hop for uplink traffic.

[0151] In some embodiments, the BH information in the topology of the second donor-CU includes at least one of the following: Ingress routing indicator (routing ID) for downlink traffic; Ingress BH RLC channel for downlink traffic; and This is the BAP address of the previous hop for downlink traffic.

[0152] In some embodiments, the second donor-CU sends the second transport migration change request via second transport migration management request information, although the present invention is not limited thereto and the transport migration change request may carry other information.

[0153] Thus, when the second donor-CU changes the resources for serving the traffic, the first donor-CU can change the L2-related information of the traffic through a second transmission transition change request, thereby ensuring the normal transmission of the transition traffic within the topology of the second donor-CU.

[0154] The following describes the case after the second donor-CU has sent a transmission transition change request for traffic.

[0155] In some embodiments, the second donor-CU changing the resources serving the traffic in the topology of the second donor-CU includes the second donor-CU changing L2-related information in the topology of the second donor-CU for the traffic, where the L2-related information includes at least one of the following information: BH RLC channel and / or BAP sublayer routing used on paths within the second donor-CU topology; uplink BH information of the traffic (wherein the uplink BH information includes a routing indicator, an uplink BH RLC channel, and / or a BAP address of a next-hop node); an uplink egress routing indicator, an egress BH RLC channel, and / or a BAP address of a next-hop node for said traffic; or The traffic's downlink ingress routing indicator, ingress BH RLC channel, and / or BAP address of the previous hop node.

[0156] The above has explained the case of changes relating to layer 2 (L2) information, but below we will explain the case of IP addresses.

[0157] In some embodiments, the second donor-CU sends a second transport migration change request to the first donor-CU to change the IP address for the IAB node.

[0158] For example, if the routing ID and / or donor distribution unit (donor-DU) in the topology of the second donor-CU for the traffic (including the transition node traffic or the child node traffic) changes, the second donor-CU sends a second transmission transition change request to the first donor-CU to change the IP address for the IAB node (including the transition node or the child node).

[0159] In some embodiments, the second transmission transition change request is included in second transmission transition management request information.

[0160] In some embodiments, the second transmission migration change request includes the following information: an IAB node identifier or IP address request index, a BAP address of a donor-DU in the topology of the first donor-CU or a BAP address of a donor-DU in the topology of the second donor-CU, and an IP address anchored to the donor-DU in the topology of the second donor-CU.

[0161] For example, for traffic of a child node, the second transmission transition change request includes the following information: an IAB node identifier or IP address request index, a BAP address of a donor-DU in the topology of the first donor-CU, and an IP address anchored to the donor-DU in the topology of the second donor-CU. Also, for traffic of a transition node, the second transmission transition change request includes the following information: an IAB node identifier or IP address request index, a BAP address of a donor-DU in the topology of the second donor-CU, and an IP address anchored to the donor-DU in the topology of the second donor-CU.

[0162] The following further exemplarily describes the transmission transition change process initiated by the second donor-CU through signaling interactions.

[0163] 14 is a signaling flowchart of a transmission transition change in an embodiment of the present invention. For example, when a change occurs in the routing ID or BH RLC channel of traffic in donor-CU2's topology, donor-CU2 requests a change in the routing ID or BH RLC channel of the transition traffic, causing donor-CU1 to update L2 information related to the traffic.

[0164] Donor-CU2 may send the following information (for each traffic flow for which modification is requested) to donor-CU1 via a TRANSPORT MIGRATION MANAGEMENT REQUEST or TRANSPORT MIGRATION MODIFICATION REQUEST: -- Traffic signs; -- the routing ID and BH RLC channel in the topology of traffic donor-CU2 (including the ingress routing ID and ingress BH RLC channel of downlink traffic, or the egress routing ID and egress BH RLC channel of uplink traffic); -- the BAP address of the previous hop in the topology of donor-CU2 for downlink traffic; and -- The BAP address of the next hop in the topology of donor-CU2 for uplink traffic.

[0165] After the routing ID of the traffic is changed, the donor-DU in the topology of the traffic donor-CU2 may change, so the donor-CU2 may further send an IP address indication (e.g., included in the above-mentioned request information), which may include the following: -- Node identification or IP address request index; and -- IP address indication (including donor-DU BAP address in donor-CU1's topology and donor-DU anchored IP address of donor-CU2).

[0166] - Donor-CU2 needs to change the BH RLC channel and routing on the path in donor-CU2's topology of the traffic based on the new routing ID or BH RLC channel in donor-CU2's topology of the traffic.

[0167] When donor-CU1 receives a transmission transition change request, it does not need to respond, but only updates the relevant configuration based on this information, including: -- Update L2 related information for traffic, including: --- For transition node traffic, update uplink BH information, including routing indicator, BH RLC channel ID and next hop node address; --- For the traffic of the child node, update the BAP header rewrite information between topologies, the routing table belonging to the topology of donor-CU2, and the BH RLC channel mapping table between the two topologies; -- Or, update the IP addresses of the transition node and child node according to the RRC reconfiguration information.

[0168] Although the above description has been given taking the change in L2 related information as an example, the present invention is not limited to this.

[0169] Also, for example, donor-CU2 may need to change the IP address of its traffic, or the IP address of the traffic may need to be changed by a donor-DU in donor-CU2's topology.

[0170] donor-CU2 sends an IP address instruction to donor-CU1, which includes: -- Node identification or IP address request index; and -- IP address indication (including the donor-DU BAP address in donor-CU1's topology or the donor-DU BAP address in donor-CU2's topology, and the IP address anchored to donor-DU of donor-CU2).

[0171] After donor-CU1 receives the above information, it does not need to respond, and only needs to update the IP addresses of the transition node and child node according to the RRC reconfiguration information.

[0172] The above signaling process is an illustrative example of an embodiment of the present invention, but the present invention is not limited thereto. For more specific details of the signaling, please refer to the related art. For example, the execution order of each operation can be appropriately adjusted, or some operations can be added or removed. Those skilled in the art can make appropriate modifications based on the above content, without being limited to the description of FIG. 14.

[0173] In some embodiments, when the IAB-MT of an IAB node is switched from a first donor-CU to a second donor-CU and resources for serving one or more traffics of the IAB node (including transition nodes and child nodes) have been determined in the topology of the second donor-CU, the second donor-CU sends a second transmission transition change request for the one or more traffics.

[0174] For example, the transmission migration change process initiated by donor-CU2 can be performed after the migration node is switched from the parent node under the F1-terminating CU to the parent node under the non-F1-terminating CU, and all traffic is migrated to the topology of the non-F1-terminating CU.

[0175] In some embodiments, when the IAB-MT of an IAB node is re-established from a first donor-CU to the second donor-CU and resources for serving one or more traffics of the IAB node (including transition nodes and child nodes) are determined in the topology of the second donor-CU, the second donor-CU sends a second transmission transition change request for one or more traffics.

[0176] For example, the transmission migration change process initiated by donor-CU2 can occur after the migration node is re-established from the parent node under the F1-terminating CU to the parent node under the non-F1-terminating CU, and all traffic is migrated to the topology of the non-F1-terminating CU.

[0177] In some embodiments, when the IAB-MT of an IAB node establishes a dual connection with a first donor-CU and a second donor-CU, and resources for serving one or more traffics of an IAB node (including transition nodes and child nodes) have been determined in the topology of the second donor-CU, the second donor-CU sends a second transmission transition change request for one or more traffics.

[0178] For example, the transmission migration change process initiated by donor-CU2 can be performed after the migration node establishes a dual connection with the F1-terminating CU and the non-F1-terminating CU, and the transmission path diameter of some traffic is migrated to the topology of the non-F1-terminating CU.

[0179] The above-described embodiments are merely illustrative of the present invention, but the present invention is not limited thereto, and appropriate modifications can be made based on the above-described embodiments. For example, each of the above-described embodiments may be used alone, or a combination of two or more of the above-described embodiments may be used.

[0180] As can be seen from the above embodiment, the second donor-CU sends a second transmission migration change request for the traffic to the first donor-CU, and the second donor-CU changes the resources serving the traffic in the topology of the second donor-CU, so that when the second donor-CU changes the resources serving the traffic or changes the IP address of the IAB node, the first donor-CU changes the L2-related information or IP address of the traffic, thereby ensuring the normal transmission of the migration traffic in the topology of the second donor-CU.

[0181] <Example of the fourth aspect> In this embodiment of the present invention, a transmission transition management method is provided, which will be described starting from the first donor-CU. The same content as in the embodiment of the third aspect will be omitted. In this embodiment, the IAB-DU of the IAB node maintains an F1 connection with the first donor-CU, and resources for serving the traffic of the IAB node are established in the topology of the second donor-CU.

[0182] 15 is a diagram illustrating another transmission transition management method in an embodiment of the present invention. As shown in FIG. 15, the method includes the following steps:

[0183] 1501: A first donor-CU receives a second transmission transition change request for traffic transmitted by a second donor-CU, in which the second donor-CU changes resources serving the traffic within the topology of the second donor-CU.

[0184] Note that, although the above-mentioned FIG. 15 is an illustrative example of an embodiment of the present invention, the present invention is not limited thereto. For example, the execution order of each operation may be appropriately adjusted, or some operations may be added or removed. Those skilled in the art may make appropriate modifications based on the above content without being limited to the description of the above-mentioned FIG. 15.

[0185] In some embodiments, a first donor-CU receives the second transmission transition change request to change the routing ID and / or BH RLC channel of the traffic transmitted by a second donor-CU within the second donor-CU's topology.

[0186] In some embodiments, the first donor-CU receives the second transport migration change request via second transport migration management request information.

[0187] In some embodiments, the second transmission transition change request includes the following information: a traffic indicator of the traffic, and BH information in the topology of the second donor-CU of the traffic.

[0188] In some embodiments, the BH information in the topology of the second donor-CU includes at least one of the following: Egress routing indicator (routing ID) for uplink traffic; egress BH RLC channel for uplink traffic; and This is the BAP address of the next hop for uplink traffic.

[0189] In some embodiments, the BH information in the topology of the second donor-CU includes at least one of the following: Ingress routing indicator (routing ID) for downlink traffic; Ingress BH RLC channel for downlink traffic; and This is the BAP address of the previous hop for downlink traffic.

[0190] In some embodiments, after receiving a second transmission transition change request for the traffic, the first donor-CU configures the IAB node to update uplink BH information for the traffic.

[0191] In some embodiments, after receiving the second transmission transition change request for the traffic, the first donor-CU configures the IAB node to update at least one of the following: BAP header rewrite information between topologies in the uplink direction, routing information within the topology of the second donor-CU, and BH RLC channel mapping information between topologies in the uplink direction.

[0192] In some embodiments, after receiving the second transmission transition change request for the traffic, the first donor-CU configures the IAB node to perform at least one of the following updates: BAP header rewrite information between topologies in the downlink direction, and BH RLC channel mapping information between topologies in the downlink direction.

[0193] In some embodiments, the first donor-CU receives a second donor-CU sending a second transport transition change request to change the IP address for the IAB node.

[0194] For example, if the routing ID and / or donor distribution unit (donor-DU) in the topology of the second donor-CU for the traffic changes, the first donor-CU receives a second transmission transition change request to change the IP address for the IAB node sent by the second donor-CU.

[0195] In some embodiments, the second transmission transition change request is included in second transmission transition management request information.

[0196] In some embodiments, the second transmission migration change request includes the following information: an IAB node identifier or IP address request index, a BAP address of a donor-DU in the topology of the first donor-CU or a BAP address of a donor-DU in the topology of the second donor-CU, and an IP address anchored to the donor-DU in the topology of the second donor-CU.

[0197] In some embodiments, the first donor-CU configures the IAB node with an IP address that is anchored to a donor-DU in the topology of the second donor-CU.

[0198] The above-described embodiments are merely illustrative of the present invention, but the present invention is not limited thereto, and appropriate modifications can be made based on the above-described embodiments. For example, each of the above-described embodiments may be used alone, or a combination of two or more of the above-described embodiments may be used.

[0199] As can be seen from the above embodiment, the second donor-CU sends a second transmission migration change request for the traffic to the first donor-CU, and the second donor-CU changes the resources serving the traffic in the topology of the second donor-CU, so that when the second donor-CU changes the resources serving the traffic or changes the IP address of the IAB node, the first donor-CU changes the L2-related information or IP address of the traffic, thereby ensuring the normal transmission of the migration traffic in the topology of the second donor-CU.

[0200] <Example of the fifth aspect> In an embodiment of the present invention, an IAB donor device is provided, and description of the same content as in the embodiment of the first aspect will be omitted. The device may be, for example, an IAB donor-CU in an IAB system (e.g., the first donor-CU in the embodiments of the first and second aspects), or may be one or more components, assemblies, or modules disposed in the IAB donor-CU.

[0201] 16 illustrates an IAB donor device in an embodiment of the present invention, in which an IAB node's IAB-DU maintains an F1 connection with a first donor centralization unit (donor-CU), and resources are established in the topology of a second donor-CU to serve the traffic of the IAB node.

[0202] As shown in FIG. 16, the IAB donor device 1600 includes:

[0203] A sending unit 1601: sends a first transmission transition change request for the traffic to the second donor-CU; and A receiving unit 1602: receives a transmission transition change response for the traffic transmitted by the second donor-CU.

[0204] In some embodiments, an IAB-MT of the IAB node maintains an RRC connection with the second donor-CU, or an IAB-MT of the IAB node maintains an RRC connection with the first donor-CU.

[0205] In some embodiments, the traffic includes a combination of at least one or more of the following: F1 control plane traffic, F1 user plane traffic, and non-F1 traffic.

[0206] In some embodiments, the transmitter 1601 transmits a first transmission transition change request to the second donor-CU to request a change in resources serving the traffic in the topology of the second donor-CU.

[0207] For example, when a change occurs in the service parameters of the traffic, the sending unit 1601 sends a first transmission transition change request to the second donor-CU to request a change in the resources serving the traffic in the topology of the second donor-CU.

[0208] In some embodiments, the first transmission transition management request information is used to send the first transmission transition change request.

[0209] In some embodiments, the receiver 1602 receives a transmission transition change response from the second donor-CU to change resources serving the traffic in the topology of the second donor-CU.

[0210] In some embodiments, the transmission transition change response is received via transmission transition management response information.

[0211] In some embodiments, the first transmission transition change request includes information such as: a traffic indicator for the traffic, and a quality of service and / or traffic type for the traffic.

[0212] In some embodiments, the transmission transition change response includes the following information: a traffic indicator for the traffic, and BH information in the topology of the second donor-CU for the traffic.

[0213] In some embodiments, the BH information in the topology of the second donor-CU includes at least one of the following: Ingress routing indicator (routing ID) for downlink traffic; Ingress BH RLC channel for downlink traffic; The BAP address of the previous hop for downlink traffic; and QoS mapping information for downlink traffic.

[0214] In some embodiments, the BH information in the topology of the second donor-CU includes at least one of the following: Egress routing indicator (routing ID) for uplink traffic; egress BH RLC channel for uplink traffic; and This is the BAP address of the next hop for uplink traffic.

[0215] In some embodiments, as shown in FIG. 16, the IAB donor device 1600 further includes:

[0216] Processing unit 1603: Performs at least one of the following operations: updating QoS mapping information for the traffic; Configure the IAB node to update uplink BH information of the traffic; Configure the IAB node to update at least one of the following: BAP header rewrite information between topologies in the uplink direction, routing information within the topology of the second donor-CU, and BH RLC channel mapping information between topologies in the uplink direction; and The IAB node is configured to update at least one of the following: BAP header rewrite information between topologies in the downlink direction; and BH RLC channel mapping information between topologies in the downlink direction.

[0217] In some embodiments, the sending unit 1601 further sends a first transmission transition change request to the second donor-CU to request a change of IP address for the IAB node.

[0218] For example, if the routing ID and / or donor distribution unit (donor-DU) of the traffic in the topology of the first donor-CU changes, the sending unit 1601 further sends a first transmission transition change request to the second donor-CU to request a change of the IP address for the IAB node.

[0219] In some embodiments, the first transmission transition change request is included in first transmission transition management request information.

[0220] In some embodiments, the first transmission migration change request includes at least one of the following information: an IAB node identifier or an IP address request index, a BAP address of a donor-DU in the topology of the first donor-CU, and an IP address anchored to the donor-DU.

[0221] In some embodiments, the receiver 1602 further receives a transmission transition change response to change the IP address for the IAB node of the second donor-CU transmission.

[0222] In some embodiments, the transport transition change response is included in transport transition management response information.

[0223] In some embodiments, the transmission migration change response includes the following information: an IAB node identifier or IP address request index, a BAP address of a donor-DU in the topology of the first donor-CU, and an IP address anchored to the donor-DU in the topology of the second donor-CU.

[0224] In some embodiments, the processing unit 1603 configures the IAB node with an IP address anchored to a donor-DU in the topology of the second donor-CU.

[0225] In some embodiments, the receiver 1602 further receives a transmission shift change response to reject the first transmission shift change request for the traffic of the second donor-CU transmission.

[0226] In some embodiments, the transmission transition change response is received with transmission transition management response information, the transmission transition management response information including a traffic indicator for the traffic.

[0227] In some embodiments, when the IAB-MT of the IAB node is switched from the first donor-CU to the second donor-CU and resources for serving one or more traffics of the IAB node are established within the topology of the second donor-CU, the transmitter 1601 transmits a first transmission transition change request for the one or more traffics.

[0228] In some embodiments, when the IAB-MT of the IAB node is re-established from the first donor-CU to the second donor-CU and resources for serving one or more traffics of the IAB node are established within the topology of the second donor-CU, the transmitter 1601 transmits a first transmission transition change request for the one or more traffics.

[0229] In some embodiments, when the IAB-MT of the IAB node establishes a dual connection with the first donor-CU and the second donor-CU, and resources for serving one or more traffics of the IAB node are established within the topology of the second donor-CU, the transmitter 1601 transmits a first transmission transition change request for the one or more traffics.

[0230] The above-described embodiments are merely illustrative of the present invention, but the present invention is not limited thereto, and appropriate modifications can be made based on the above-described embodiments. For example, each of the above-described embodiments may be used alone, or a combination of two or more of the above-described embodiments may be used.

[0231] Although the above describes each component or module related to the present invention, the present invention is not limited thereto. The IAB donor device 1600 according to the embodiment of the present invention may further include other components or modules, and the specific contents of these components or modules can be found in the related art.

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

[0233] As can be seen from the above embodiment, the first donor-CU sends a first transmission transition change request for traffic to the second donor-CU, and the first donor-CU receives a transmission transition change response for the traffic sent by the second donor-CU, so that the second donor-CU can change the transmission resources serving the transition traffic based on the change (change) in the service parameters of the traffic, so that the service requirements of the traffic can still be met after the change in the service parameters of the traffic.

[0234] <Example of the sixth aspect> In an embodiment of the present invention, an IAB donor device is provided, and description of the same content as in the embodiment of the second aspect will be omitted. The device may be, for example, an IAB donor-CU in an IAB system (e.g., the second donor-CU in the embodiments of the first and second aspects), or may be one or more components, assemblies, or modules disposed in the IAB donor-CU.

[0235] 17 illustrates an IAB donor device in an embodiment of the present invention, in which an IAB node's IAB-DU maintains an F1 connection with a first donor-CU, and resources are established in the topology of a second donor-CU to serve the traffic of the IAB node.

[0236] As shown in FIG. 17, the IAB donor device 1700 includes:

[0237] A receiving unit 1701: receives a first transmission transition change request for the traffic transmitted by the first donor-CU; and A transmitting unit 1702: transmits a transmission shift change response for the traffic to the first donor-CU.

[0238] In some embodiments, an IAB-MT of the IAB node maintains an RRC connection with the second donor-CU, or an IAB-MT of the IAB node maintains an RRC connection with the first donor-CU.

[0239] In some embodiments, the traffic includes a combination of at least one or more of the following: F1 control plane (F1-C) traffic, F1 user plane (F1-U) traffic, and non-F1 traffic.

[0240] In some embodiments, the receiver 1701 receives a first transmission transition change request from the first donor-CU to request a change in resources serving the traffic in the topology of the second donor-CU.

[0241] For example, when a change occurs in the service parameters of the traffic, the receiving unit 1701 receives a first transmission transition change request from the first donor-CU to request a change in the resources serving the traffic in the topology of the second donor-CU.

[0242] In some embodiments, the first transmission transition change request is received via first transmission transition management request information.

[0243] In some embodiments, the first transmission transition change request includes information such as: a traffic signature of the traffic, a quality of service (QoS) of the traffic, and / or a traffic type.

[0244] In some embodiments, as shown in FIG. 17, the IAB donor device 1700 further includes:

[0245] Processing unit 1703: Updates the backhaul (BH) radio link control (RLC) channel and / or BAP sublayer routing that the traffic uses on the path in the topology of the second donor-CU, or updates QoS mapping information of the traffic.

[0246] In some embodiments, the processing unit 1703 updates uplink BH information of the traffic, where the uplink BH information includes a routing indicator, an uplink BH RLC channel, and / or a BAP address of a next-hop node.

[0247] In some embodiments, the processing unit 1703 updates the uplink egress routing indicator, the egress BH RLC channel, and / or the BAP address of the next hop node of the traffic, or updates the downlink ingress routing indicator, the ingress BH RLC channel, and / or the BAP address of the previous hop node of the traffic.

[0248] In some embodiments, the sender 1702 sends a transmission transition change response to the first donor-CU to change resources serving the traffic in the topology of the second donor-CU.

[0249] In some embodiments, the transmission transition change response is sent via transmission transition management response information.

[0250] In some embodiments, the transmission transition change response includes the following information: a traffic indicator of the traffic, and BH information in the topology of the second donor-CU of the traffic.

[0251] In some embodiments, the BH information in the topology of the second donor-CU includes at least one of the following: Ingress routing indicator (routing ID) for downlink traffic; Ingress BH RLC channel for downlink traffic; The BAP address of the previous hop for downlink traffic; and QoS mapping information for downlink traffic.

[0252] In some embodiments, the BH information in the topology of the second donor-CU includes at least one of the following: Egress routing indicator (routing ID) for uplink traffic; egress BH RLC channel for uplink traffic; and This is the BAP address of the next hop for uplink traffic.

[0253] In some embodiments, the receiver 1701 receives a first transmission transition change request from the first donor-CU transmission to request a change of IP address for the IAB node.

[0254] For example, if the routing ID and / or donor distribution unit (donor-DU) in the topology of the first donor-CU of the traffic changes, the receiver 1701 receives a first transmission transition change request to request a change of the IP address for the IAB node of the first donor-CU transmission.

[0255] In some embodiments, the first transmission transition change request is included in first transmission transition management request information.

[0256] In some embodiments, the first transmission migration change request includes at least one of the following information: an IAB node identifier or IP address request index, a BAP address of a donor-DU in the topology of the first donor-CU, and an IP address anchored to the donor-DU.

[0257] In some embodiments, the sending unit 1702 further sends a transmission transition change response to the first donor-CU to change the IP address of the IAB node, where the transmission transition change response is included in the transmission transition management response information.

[0258] In some embodiments, the transmission migration change response includes the following information: an IAB node identifier or IP address request index, a BAP address of a donor-DU in the topology of the first donor-CU, and an IP address anchored to the donor-DU in the topology of the second donor-CU.

[0259] In some embodiments, after receiving the first transmission transition change request, the processing unit 1703 rejects the first transmission transition change request for the traffic.

[0260] For example, if the Quality of Service (QoS) of the traffic cannot be satisfied, after receiving the first transmission transition change request, the processing unit 1703 rejects the first transmission transition change request for the traffic.

[0261] In some embodiments, the sender 1702 sends a transmission shift change response to the first donor-CU to deny the transmission shift change request for the traffic.

[0262] In some embodiments, the second donor-CU sends the transmission transition change response according to transmission transition management information, where the transmission transition change response includes a traffic indicator of the traffic.

[0263] The above-described embodiments are merely illustrative of the present invention, but the present invention is not limited thereto, and appropriate modifications can be made based on the above-described embodiments. For example, each of the above-described embodiments may be used alone, or a combination of two or more of the above-described embodiments may be used.

[0264] Although the above describes each component or module related to the present invention, the present invention is not limited thereto. The IAB donor device 1700 according to the embodiment of the present invention may further include other components or modules, and the specific contents of these components or modules can be found in the related art.

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

[0266] As can be seen from the above embodiment, a first donor-CU sends a first transmission transition change request for traffic to a second donor-CU, and the first donor-CU receives a transmission transition change response for the traffic sent by the second donor-CU, so that the second donor-CU can change the transmission resources serving the transition traffic based on the change (change) in the service parameters of the traffic, so that the service requirements of the traffic can still be met after the change in the service parameters of the traffic.

[0267] <Example of the seventh aspect> In an embodiment of the present invention, an IAB donor device is provided, and description of the same content as in the embodiment of the third aspect will be omitted. The device may be, for example, an IAB donor-CU in an IAB system (e.g., the second donor-CU in the embodiments of the third and fourth aspects), or may be one or more parts, assemblies, or modules disposed in the IAB donor-CU.

[0268] 18 illustrates an IAB donor device in an embodiment of the present invention, in which an IAB node's IAB-DU maintains an F1 connection with a first donor centralization unit (donor-CU), and resources are established in the topology of a second donor-CU to serve the IAB node's traffic.

[0269] As shown in FIG. 18, the IAB donor device 1800 includes:

[0270] A sending unit 1801: sends a second transmission transition change request for traffic to the first donor-CU; and A processing unit 1802: changes the resources serving the traffic in the topology of the second donor-CU.

[0271] In some embodiments, the transmitter 1801 sends the second transmission transition change request to the first donor-CU to change the routing ID and / or BH RLC channel of the traffic in the topology of the second donor-CU.

[0272] In some embodiments, the second transport migration change request is sent via second transport migration management request information.

[0273] In some embodiments, the second transmission transition change request includes the following information: traffic signs of said traffic; and The BH information in the topology of the second donor-CU of the traffic.

[0274] In some embodiments, the BH information in the topology of the second donor-CU includes at least one of the following: Egress routing indicator (routing ID) for uplink traffic; egress BH RLC channel for uplink traffic; and This is the BAP address of the next hop for uplink traffic.

[0275] In some embodiments, the BH information in the topology of the second donor-CU includes at least one of the following: Ingress routing indicator (routing ID) for downlink traffic; Ingress BH RLC channel for downlink traffic; and This is the BAP address of the previous hop for downlink traffic.

[0276] In some embodiments, the processing unit 1802 updates the BH RLC channel and / or BAP sublayer routing that the traffic uses over a path in the topology of the second donor-CU.

[0277] In some embodiments, the processing unit 1802 updates uplink BH information of the traffic, where the uplink BH information includes a routing indicator, an uplink BH RLC channel, and / or a BAP address of a next-hop node.

[0278] In some embodiments, the processing unit 1802 updates the traffic's uplink egress routing indicator, egress BH RLC channel, and / or BAP address of the next hop node, or updates the traffic's downlink ingress routing indicator, ingress BH RLC channel, and / or BAP address of the previous hop node.

[0279] In some embodiments, the sending unit 1801 further sends a second transmission migration change request to the first donor-CU to change the IP address for the IAB node.

[0280] For example, if the routing ID and / or donor distribution unit (donor-DU) of the traffic in the topology of the second donor-CU changes, the sending unit 1801 further sends a second transmission transition change request to the first donor-CU to change the IP address for the IAB node.

[0281] In some embodiments, the second transmission transition change request is included in second transmission transition management request information.

[0282] In some embodiments, the second transmission migration change request includes the following information: an IAB node identifier or IP address request index, a BAP address of a donor-DU in the topology of the first donor-CU or a BAP address of a donor-DU in the topology of the second donor-CU, and an IP address anchored to the donor-DU in the topology of the second donor-CU.

[0283] In some embodiments, when the IAB-MT of the IAB node is switched from the first donor-CU to the second donor-CU and resources for serving one or more traffics of the IAB node have already been established within the topology of the second donor-CU, the transmitter 1801 transmits a second transmission transition change request for the one or more traffics.

[0284] In some embodiments, when the IAB-MT of the IAB node is re-established from the first donor-CU to the second donor-CU and resources for serving one or more traffics of the IAB node are established within the topology of the second donor-CU, the transmitter 1801 transmits a second transmission transition change request for the one or more traffics.

[0285] In some embodiments, when the IAB-MT of the IAB node establishes a dual connection with the first donor-CU and the second donor-CU, and resources for serving one or more traffics of the IAB node are established within the topology of the second donor-CU, the transmitter 1801 transmits a second transmission transition change request for the one or more traffics.

[0286] The above-described embodiments are merely illustrative of the present invention, but the present invention is not limited thereto, and appropriate modifications can be made based on the above-described embodiments. For example, each of the above-described embodiments may be used alone, or a combination of two or more of the above-described embodiments may be used.

[0287] Although the above describes each component or module related to the present invention, the present invention is not limited thereto. The IAB donor device 1800 in the embodiment of the present invention may further include other components or modules, and the specific contents of these components or modules can be found in the related art.

[0288] 18 shows only the connection relationships or signal directions between each component or module, but as will be understood by those skilled in the art, various related technologies such as bus connection may be adopted. Each of the above-described components or modules may be realized by hardware such as a processor, memory, transmitter, receiver, etc., and the implementation of the present invention is not limited thereto.

[0289] As can be seen from the above embodiment, the second donor-CU sends a second transmission migration change request for the traffic to the first donor-CU, and the second donor-CU changes the resources serving the traffic in the topology of the second donor-CU, so that when the second donor-CU changes the resources serving the traffic or changes the IP address of the IAB node, the first donor-CU changes the L2-related information or IP address of the traffic, thereby ensuring the normal transmission of the migration traffic in the topology of the second donor-CU.

[0290] <Example of the eighth aspect> In an embodiment of the present invention, an IAB donor device is provided, and description of the same content as in the embodiment of the fourth aspect will be omitted. The device may be, for example, an IAB donor-CU in an IAB system (e.g., the first donor-CU in the embodiments of the third and fourth aspects), or may be one or more components, assemblies, or modules disposed in the IAB donor-CU.

[0291] 19 illustrates an IAB donor device in an embodiment of the present invention, in which an IAB node's IAB-DU maintains an F1 connection with a first donor-CU, and resources are established in the topology of a second donor-CU to serve the traffic of the IAB node.

[0292] As shown in FIG. 19, the IAB donor device 1900 includes:

[0293] A receiving unit 1901 receives a second transmission transition change request for traffic transmitted by a second donor-CU, in which the second donor-CU changes the resources serving the traffic in the topology of the second donor-CU.

[0294] In some embodiments, the receiver 1901 receives the second transmission transition change request to change the routing ID and / or BH RLC channel of the traffic within the topology of the second donor-CU for the second donor-CU transmission.

[0295] In some embodiments, the second transport migration change request is received by second transport migration management request information.

[0296] In some embodiments, the second transmission transition change request includes the following information: traffic signs of said traffic; and The BH information in the topology of the second donor-CU of the traffic.

[0297] In some embodiments, the BH information in the topology of the second donor-CU includes at least one of the following: Egress routing indicator (routing ID) for uplink traffic; egress BH RLC channel for uplink traffic; and This is the BAP address of the next hop for uplink traffic.

[0298] In some embodiments, the BH information in the topology of the second donor-CU includes at least one of the following: Ingress routing indicator (routing ID) for downlink traffic; Ingress BH RLC channel for downlink traffic; and This is the BAP address of the previous hop for downlink traffic.

[0299] In some embodiments, as shown in FIG. 19, the IAB donor device 1900 further includes:

[0300] Processing unit 1902: Configures the IAB node to update the uplink BH information of the traffic.

[0301] In some embodiments, the processing unit 1902 configures the IAB node with at least one of the following updates: BAP header rewrite information between topologies in the uplink direction, routing information within the topology of the second donor-CU, and BH RLC channel mapping information between topologies in the uplink direction.

[0302] In some embodiments, the processing unit 1902 configures at least one of the following updates in the IAB node: BAP header rewrite information between topologies in the downlink direction, and BH RLC channel mapping information between topologies in the downlink direction.

[0303] In some embodiments, the receiver 1901 further receives a second transmission transition change request to change an IP address for the IAB node of the second donor-CU transmission.

[0304] For example, if the routing ID and / or donor distribution unit (donor-DU) in the topology of the second donor-CU of the traffic changes, the receiving unit 1901 further receives a second transmission transition change request to change the IP address for the IAB node of the second donor-CU transmission.

[0305] In some embodiments, the second transmission transition change request is included in second transmission transition management request information.

[0306] In some embodiments, the second transmission migration change request includes the following information: an IAB node identifier or IP address request index, a BAP address of a donor-DU in the topology of the first donor-CU or a BAP address of a donor-DU in the topology of the first donor-CU, and an IP address anchored to the donor-DU in the topology of the second donor-CU.

[0307] In some embodiments, the processing unit 1902 further configures the IAB node with an IP address anchored to a donor-DU in the topology of the second donor-CU.

[0308] The above-described embodiments are merely illustrative of the present invention, but the present invention is not limited thereto, and appropriate modifications can be made based on the above-described embodiments. For example, each of the above-described embodiments may be used alone, or a combination of two or more of the above-described embodiments may be used.

[0309] Although the above describes each component or module related to the present invention, the present invention is not limited thereto. The IAB donor device 1900 according to the embodiment of the present invention may further include other components or modules, and the specific contents of these components or modules can be found in the related art.

[0310] 19 only shows the connection relationships or signal directions between each component or module, but as will be understood by those skilled in the art, various related technologies such as bus connection may be adopted. Each of the above-described components or modules may be realized by hardware such as a processor, memory, transmitter, receiver, etc., and the implementation of the present invention is not limited thereto.

[0311] As can be seen from the above embodiment, the second donor-CU sends a second transmission migration change request for the traffic to the first donor-CU, and the second donor-CU changes the resources serving the traffic in the topology of the second donor-CU, so that when the second donor-CU changes the resources serving the traffic or changes the IP address of the IAB node, the first donor-CU changes the L2-related information or IP address of the traffic, thereby ensuring the normal transmission of the migration traffic in the topology of the second donor-CU.

[0312] <Example of the ninth aspect> In an embodiment of the present invention, a communication system is provided, which includes a donor device and an IAB node. The network architecture of the donor device and the IAB node can be referred to in the related art, and detailed description thereof will be omitted here.

[0313] In some embodiments, the IAB system includes:

[0314] A first donor centralization unit (first donor-CU): sending a first transmission shift change request for traffic and receiving a transmission shift change response for the traffic; and Second donor centralization unit (second donor-CU): receives the first transmission transition change request and sends the transmission transition change response.

[0315] In some embodiments, the IAB system includes:

[0316] A second donor concentration unit (second donor-CU): sends a second transmission transition change request for traffic and changes the resources serving the traffic in the topology of the second donor concentration unit; and First donor centralization unit (first donor-CU): receives the second transmission transition change request.

[0317] An embodiment of the present invention further provides an IAB device, which may be an IAB donor device or an IAB node device (transition node or child node).

[0318] 20 is a diagram illustrating an IAB device according to an embodiment of the present invention. As shown in FIG. 20, the IAB device 2000 may include a processor (e.g., a central processing unit (CPU)) 2001 and a memory 2002, the memory 2002 being connected to the processor 2001. The memory 2002 can store various data and can further store a program 2005 for information processing, and can execute the program 2005 under the control of the central processing unit 2001.

[0319] For example, the processor 2001 may be configured to execute a program to implement the transmission transition management method according to the first aspect of the present invention. For example, the processor 2001 may be configured to perform the following control: send a first transmission transition change request for the traffic to a second donor-CU; and receive a transmission transition change response for the traffic sent by the second donor-CU.

[0320] Also, for example, the processor 2001 may be configured to execute a program to implement the transmission transition management method according to the embodiment of the second aspect. For example, the processor 2001 may be configured to perform the following control: receive a first transmission transition change request for the traffic sent by a first donor-CU; and send a transmission transition change response for the traffic to the first donor-CU.

[0321] Also, for example, the processor 2001 may be configured to execute a program to implement the transmission transition management method according to the embodiment of the third aspect. For example, the processor 2001 may be configured to perform the following control: send a second transmission transition change request for traffic to a first donor-CU; and change resources serving the traffic in the topology of the second donor-CU.

[0322] Also, for example, the processor 2001 may be configured to execute a program to implement the transmission transition management method according to the embodiment of the fourth aspect. For example, the processor 2001 may be configured to perform the following control: receive a second transmission transition change request for traffic sent by a second donor-CU, in which the second donor-CU changes the resources serving the traffic in the topology of the second donor-CU.

[0323] 20, the IAB device 2000 may further include a transceiver 2003, an antenna 2004, etc., and the functions of these components are similar to those of the prior art, so detailed descriptions thereof will be omitted here. Note that the IAB device 2000 does not need to include all of the components shown in FIG. 20. The IAB device 2000 may further include components not shown in FIG. 20, and reference can be made to the prior art for such components.

[0324] An embodiment of the present invention further provides a computer-readable program, which, when executed by an IAB device, causes a computer to perform a transmission transition management method according to any of the first to fourth aspects of the present invention on the IAB device.

[0325] In a further embodiment of the present invention, a storage medium is provided having a computer-readable program stored thereon, the computer-readable program causing a computer to execute the transmission transition management method in an IAB device according to the embodiments of the first to fourth aspects.

[0326] The above-described devices and methods may be realized by software or hardware, or by a combination of hardware and software. The present invention further relates to a computer-readable program as described below, which, when executed by a logic component, causes the logic component to realize the above-described devices or components, or to perform each of the above-described methods or steps. The logic component may be, for example, an FPGA (Field Programmable Gate Array), a microprocessor, or a processing unit used in a computer. The present invention also relates to a storage medium, such as a hard disk, magnetic disk, optical hard disk, DVD, or flash memory, that stores the above-described program.

[0327] Furthermore, 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 implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors communicatively coupled with a DSP, or any other configuration.

[0328] Although the preferred embodiments of the present invention have been described above, the present invention is not limited to these embodiments, and any modifications to the present invention that do not depart from the spirit of the present invention fall within the technical scope of the present invention.

[0329] Furthermore, the following additional notes are disclosed regarding the above-described embodiments.

[0330] (Appendix 1) 1. A transmission transition management method, comprising: An IAB-DU of an IAB node maintains an F1 connection with a first donor concentration unit (donor-CU), and resources are established in a topology of a second donor-CU for serving traffic of the IAB node, and the method includes: The first donor-CU sends a first transmission transition change request for the traffic to the second donor-CU; and The method includes the first donor-CU receiving a transmission transition change response for the traffic transmitted by the second donor-CU.

[0331] (Appendix 2) 2. The method of claim 1, comprising: The IAB-MT of the IAB node maintains an RRC connection with the second donor-CU, or the IAB-MT of the IAB node maintains an RRC connection with the first donor-CU.

[0332] (Appendix 3) 10. The method according to claim 1 or 2, The method, wherein the traffic includes a combination of at least one or more of the following: F1 control plane (F1-C) traffic, F1 user plane (F1-U) traffic, and non-F1 traffic.

[0333] (Appendix 4) 4. The method of any one of claims 1 to 3, comprising: The first donor-CU sends a first transmission transition change request to the second donor-CU to request a change in resources serving the traffic in the topology of the second donor-CU.

[0334] (Appendix 5) 5. The method of claim 4, The first donor-CU sends the first transport migration change request by first transport migration management request information.

[0335] (Appendix 6) 6. The method according to claim 4 or 5, The first transmission transition change request includes information such as a traffic indicator of the traffic, a Quality of Service (QoS) of the traffic, and / or a traffic type.

[0336] (Appendix 7) 7. The method of any one of claims 4 to 6, comprising: The first donor-CU receives a transmission transition change response from the second donor-CU to change resources serving the traffic in the topology of the second donor-CU.

[0337] (Appendix 8) 8. The method of claim 7, The first donor-CU receives the transport migration change response through transport migration management response information.

[0338] (Appendix 9) 9. The method according to claim 7 or 8, The transmission transition change response includes the following information: a traffic indicator of the traffic, and BH information in the topology of the second donor-CU of the traffic.

[0339] (Appendix 10) 10. The method of claim 9, The BH information in the topology of the second donor-CU includes at least one of the following: Ingress routing indicator (routing ID) for downlink traffic; Ingress BH RLC channel for downlink traffic; The BAP address of the previous hop for downlink traffic; and The method is QoS mapping information for downlink traffic.

[0340] (Appendix 11) 10. The method of claim 9, The BH information in the topology of the second donor-CU includes at least one of the following: Egress routing indicator (routing ID) for uplink traffic; egress BH RLC channel for uplink traffic; and The method includes a BAP address of the next hop for uplink traffic.

[0341] (Appendix 12) 12. The method of any one of claims 1 to 11, comprising: After the first donor-CU receives a transmission transition change response for the traffic, the method further comprises: The method includes the first donor-CU updating QoS mapping information for the traffic.

[0342] (Appendix 13) 13. The method of any one of claims 1 to 12, comprising: After the first donor-CU receives a transmission transition change response for the traffic, the method further comprises: The method includes the first donor-CU configuring the IAB node to update uplink BH information of the traffic.

[0343] (Appendix 14) 14. The method of any one of claims 1 to 13, comprising: After the first donor-CU receives a transmission transition change response for the traffic, the method further comprises: The method includes the first donor-CU configuring at least one of the following updates to the IAB node: BAP header rewrite information between topologies in the uplink direction, routing information within the topology of the second donor-CU, and BH RLC channel mapping information between topologies in the uplink direction.

[0344] (Appendix 15) 14. The method of any one of claims 1 to 13, comprising: After the first donor-CU receives a transmission transition change response for the traffic, the method further comprises: The method includes the first donor-CU configuring at least one of the following updates to the IAB node: BAP header rewrite information between topologies in the downlink direction, and BH RLC channel mapping information between topologies in the downlink direction.

[0345] (Appendix 16) 16. The method of any one of claims 1 to 15, comprising: The first donor-CU sends the first transmission transition change request to the second donor-CU to request a change of IP address for the IAB node.

[0346] (Appendix 17) 17. The method of claim 16, The first transmission transition change request is included in first transmission transition management request information.

[0347] (Appendix 18) 17. The method of claim 16, The first transmission transition change request includes the following information: an IAB node identifier or IP address request index, and a BAP address of a donor-DU in the topology of the first donor-CU.

[0348] (Appendix 19) 19. The method of claim 18, The method, wherein the first transmission transition change request further includes an IP address anchored to the donor-DU.

[0349] (Appendix 20) 20. The method of any one of claims 16 to 19, comprising: The first donor-CU receives the second donor-CU's transmitted transport transition change response to change the IP address for the IAB node.

[0350] (Appendix 21) 21. The method of claim 20, The method, wherein the transmission transition change response is included in transmission transition management response information.

[0351] (Appendix 22) 21. The method of claim 20, The transmission migration change response includes the following information: an IAB node identifier or IP address request index, a BAP address of a donor-DU in the topology of the first donor-CU, and an IP address anchored to the donor-DU in the topology of the second donor-CU.

[0352] (Appendix 23) 23. The method of any one of claims 20 to 22, comprising: After the first donor-CU receives the transmission transition change response for the IAB node, the method further comprises: The method includes the first donor-CU configuring the IAB node with an IP address anchored to a donor-DU in the topology of the second donor-CU.

[0353] (Appendix 24) 7. The method of any one of claims 4 to 6, comprising: The first donor-CU receives a transmission transition change response from the second donor-CU to deny the first transmission transition change request for the traffic.

[0354] (Appendix 25) 25. The method of claim 24, The first donor-CU receives the transmission transition change response through transmission transition management response information.

[0355] (Appendix 26) 26. The method of claim 25, The method, wherein the transmission transition management response information includes a traffic signature for the traffic.

[0356] (Appendix 27) 27. The method of any one of claims 1 to 26, comprising: a first donor-CU sending a first transmission transition change request for one or more traffics when an IAB-MT of the IAB node is switched from the first donor-CU to the second donor-CU and resources for serving one or more traffics of the IAB node are established within the topology of the second donor-CU.

[0357] (Appendix 28) 27. The method of any one of claims 1 to 26, comprising: a first donor-CU sending a first transmission transition change request for the one or more traffic when an IAB-MT of the IAB node is re-established from the first donor-CU to the second donor-CU and traffic resources for serving one or more of the IAB nodes are established within the topology of the second donor-CU.

[0358] (Appendix 29) 27. The method of any one of claims 1 to 26, comprising: a first donor-CU sending a first transmission transition change request for the one or more traffics when an IAB-MT of the IAB node establishes a dual connection with the first donor-CU and the second donor-CU and traffic resources for serving one or more of the IAB nodes are established within the topology of the second donor-CU.

[0359] (Appendix 30) 1. A transmission transition management method, comprising: An IAB-DU of an IAB node maintains an F1 connection with a first donor concentration unit (donor-CU), and resources are established in a topology of a second donor-CU for serving traffic of the IAB node, and the method includes: the second donor-CU receives a first transmission transition change request for the traffic transmitted by the first donor-CU; and The method includes the second donor-CU sending a transmission transition change response for the traffic to the first donor-CU.

[0360] (Appendix 31) 31. The method of claim 30, The IAB-MT of the IAB node maintains an RRC connection with the second donor-CU, or the IAB-MT of the IAB node maintains an RRC connection with the first donor-CU.

[0361] (Appendix 32) 32. The method of claim 30 or 31, The method, wherein the traffic includes a combination of at least one or more of the following: F1 control plane (F1-C) traffic, F1 user plane (F1-U) traffic, and non-F1 traffic.

[0362] (Appendix 33) 33. The method of any one of claims 30 to 32, comprising: The second donor-CU receives a first transmission transition change request from the first donor-CU to request a change in resources for serving the traffic in the topology of the second donor-CU.

[0363] (Appendix 34) 34. The method of claim 33, The second donor-CU receives the first transport migration change request through first transport migration management request information.

[0364] (Appendix 35) 35. The method according to claim 33 or 34, The first transmission transition change request includes information such as a traffic indicator of the traffic, a Quality of Service (QoS) of the traffic, and / or a traffic type.

[0365] (Appendix 36) 36. The method of any one of claims 30 to 35, comprising: The method wherein, after receiving the first transmission transition change request, the second donor-CU updates a backhaul (BH) radio link control (RLC) channel and / or BAP sublayer routing that the traffic uses on a path within the topology of the second donor-CU, or updates QoS mapping information of the traffic.

[0366] (Appendix 37) 37. The method of any one of claims 30 to 36, comprising: The second donor-CU updates uplink BH information of the traffic after receiving the first transmission transition change request, wherein the uplink BH information includes a routing indicator, an uplink BH RLC channel, and / or a BAP address of a next-hop node.

[0367] (Appendix 38) 37. The method of any one of claims 30 to 36, comprising: The second donor-CU updates the uplink egress routing indicator, the egress BH RLC channel, and / or the BAP address of the next-hop node of the traffic after receiving the first transmission transition change request; or The method further comprises updating a downlink ingress routing indicator, an ingress BH RLC channel, and / or a BAP address of a previous hop node of the traffic.

[0368] (Appendix 39) 39. The method of any one of claims 33 to 38, comprising: The second donor-CU sends a transmission transition change response to the first donor-CU to change resources serving the traffic in the topology of the second donor-CU.

[0369] (Appendix 40) 39. The method of claim 39, The second donor-CU sends the transport migration change response using transport migration management response information.

[0370] (Appendix 41) 41. The method according to claim 39 or 40, The transmission transition change response includes the following information: a traffic indicator of the traffic, and BH information in the topology of the second donor-CU of the traffic.

[0371] (Appendix 42) 42. The method of claim 41, The BH information in the topology of the second donor-CU includes at least one of the following: Ingress routing indicator (routing ID) for downlink traffic; Ingress BH RLC channel for downlink traffic; The BAP address of the previous hop for downlink traffic; and The method is QoS mapping information for downlink traffic.

[0372] (Appendix 43) 42. The method of claim 41, The BH information in the topology of the second donor-CU includes at least one of the following: Egress routing indicator (routing ID) for uplink traffic; egress BH RLC channel for uplink traffic; and The method includes a BAP address of a next hop for uplink traffic.

[0373] (Appendix 44) 44. The method of any one of claims 30 to 43, comprising: The second donor-CU receives a first transmission transition change request from the first donor-CU to request a change of IP address for the IAB node.

[0374] (Appendix 45) 45. The method of claim 44, The first transmission transition change request is included in first transmission transition management request information.

[0375] (Appendix 46) 45. The method of claim 44, The first transmission transition change request includes the following information: an IAB node identifier or IP address request index, and a BAP address of a donor-DU in the topology of the first donor-CU.

[0376] (Appendix 47) 47. The method of claim 46, The method, wherein the first transmission transition change request further includes an IP address anchored to the donor-DU.

[0377] (Appendix 48) 48. The method of any one of claims 44 to 47, comprising: The second donor-CU sends a transport migration change response to the first donor-CU to change the IP address for the IAB node.

[0378] (Appendix 49) 49. The method of claim 48, The method, wherein the transmission transition change response is included in transmission transition management response information.

[0379] (Appendix 50) 49. The method of claim 48, The transmission migration change response includes the following information: an IAB node identifier or IP address request index, a BAP address of a donor-DU in the topology of the first donor-CU, and an IP address anchored to the donor-DU in the topology of the second donor-CU.

[0380] (Appendix 51) 36. The method of any one of claims 33 to 35, comprising: The method wherein the second donor-CU rejects the first transmission transition change request for the traffic after receiving the first transmission transition change request.

[0381] (Appendix 52) 52. The method of claim 51, The second donor-CU sends a transmission transition change response to the first donor-CU to deny the transmission transition change request for the traffic.

[0382] (Appendix 53) 53. The method of claim 52, comprising: The second donor-CU sends the transmission transition change response according to transmission transition management information.

[0383] (Appendix 54) 53. The method of claim 52, comprising: The transmission transition change response includes a traffic indication for the traffic.

[0384] (Appendix 55) 1. A transmission transition management method, comprising: An IAB-DU of an IAB node maintains an F1 connection with a first donor-CU, and resources are established in a topology of a second donor-CU for serving traffic of the IAB node, and the method includes: The second donor-CU sends a second transmission transition change request for traffic to the first donor-CU; and The method includes the second donor-CU changing resources serving the traffic in the topology of the second donor-CU.

[0385] (Appendix 56) 56. The method of claim 55, The second donor-CU sends the second transmission transition change request to the first donor-CU to change the routing ID and / or BH RLC channel of the traffic in the topology of the second donor-CU.

[0386] (Appendix 57) 57. The method of claim 56, The second donor-CU sends the second transport migration change request using second transport migration management request information.

[0387] (Appendix 58) 58. The method of claim 56 or 57, The second transmission transition change request includes the following information: traffic signs of said traffic; and The method further comprises the step of: providing BH information in the topology of a second donor-CU of the traffic;

[0388] (Appendix 59) 59. The method of claim 58, The BH information in the topology of the second donor-CU includes at least one of the following: Egress routing indicator (routing ID) for uplink traffic; egress BH RLC channel for uplink traffic; and The method includes a BAP address of a next hop for uplink traffic.

[0389] (Appendix 60) 59. The method of claim 58, The BH information in the topology of the second donor-CU includes at least one of the following: Ingress routing indicator (routing ID) for downlink traffic; Ingress BH RLC channel for downlink traffic; and The method is a BAP address of a previous hop of downlink traffic.

[0390] (Appendix 61) 61. The method of any one of clauses 55 to 60, comprising: The second donor-CU changing the resources serving the traffic in the topology of the second donor-CU, The method includes the second donor-CU modifying a BH RLC channel and / or BAP sublayer routing used by the traffic on a path within the topology of the second donor-CU.

[0391] (Appendix 62) 62. The method of any one of claims 55 to 61, comprising: The second donor-CU changing the resources serving the traffic in the topology of the second donor-CU, The method includes the second donor-CU updating uplink BH information of the traffic, wherein the uplink BH information includes a routing indicator, an uplink BH RLC channel, and / or a BAP address of a next-hop node.

[0392] (Appendix 63) 63. The method of any one of clauses 55 to 62, comprising: The second donor-CU changing the resources serving the traffic in the topology of the second donor-CU, The second donor-CU updates the traffic's uplink egress routing indicator, egress BH RLC channel, and / or next-hop node BAP address; or The method includes updating a downlink ingress routing indicator, an ingress BH RLC channel, and / or a BAP address of a previous hop node of the traffic.

[0393] (Appendix 64) 64. The method of any one of clauses 55 to 63, comprising: The second donor-CU sends a second transmission transition change request to the first donor-CU to change the IP address for the IAB node.

[0394] (Appendix 65) 65. The method of claim 64, The second transmission transition change request is included in second transmission transition management request information.

[0395] (Appendix 66) 65. The method of claim 64, The second transmission transition change request includes the following information: an IAB node identifier or an IP address request index, a BAP address of a donor-DU in the topology of the first donor-CU or a BAP address of a donor-DU in the topology of the second donor-CU, and an IP address anchored to the donor-DU in the topology of the second donor-CU.

[0396] (Appendix 67) 67. The method of any one of clauses 55 to 66, comprising: a second donor-CU sending a second transmission transition change request for the one or more traffics when an IAB-MT of the IAB node is switched from the first donor-CU to the second donor-CU and traffic resources for serving one or more of the IAB nodes are established within the topology of the second donor-CU.

[0397] (Appendix 68) 67. The method of any one of clauses 55 to 66, comprising: a second donor-CU sending a second transmission transition change request for the one or more traffic when the IAB-MT of the IAB node is re-established from the first donor-CU to the second donor-CU and traffic resources for serving one or more of the IAB nodes are established within the topology of the second donor-CU.

[0398] (Appendix 69) 67. The method of any one of clauses 55 to 66, comprising: a second donor-CU sending a second transmission transition change request for the one or more traffics when an IAB-MT of the IAB node establishes a dual connection with the first donor-CU and the second donor-CU and traffic resources for serving one or more of the IAB nodes within the topology of the second donor-CU are established.

[0399] (Appendix 70) 1. A transmission transition management method, comprising: An IAB-DU of an IAB node maintains an F1 connection with a first donor-CU, and resources are established in a topology of a second donor-CU for serving traffic of the IAB node, and the method includes: receiving a second transmission transition change request for traffic transmitted by the second donor-CU by the first donor-CU; wherein the second donor-CU changes the resources serving the traffic in the topology of the second donor-CU.

[0400] (Appendix 71) 71. The method of claim 70, The first donor-CU receives the second transmission transition change request to change the routing ID and / or BH RLC channel of the traffic transmitted by the second donor-CU within the topology of the second donor-CU.

[0401] (Appendix 72) 72. The method of claim 71, The first donor-CU receives the second transport migration change request through second transport migration management request information.

[0402] (Appendix 73) 73. The method of claim 71 or 72, The second transmission transition change request includes the following information: traffic signs of said traffic; and The method further comprises the step of: providing BH information in the topology of a second donor-CU of the traffic;

[0403] (Appendix 74) 74. The method of claim 73, comprising: The BH information in the topology of the second donor-CU includes at least one of the following: Egress routing indicator (routing ID) for uplink traffic; egress BH RLC channel for uplink traffic; and The method includes a BAP address of the next hop for uplink traffic.

[0404] (Appendix 75) 74. The method of claim 73, comprising: The BH information in the topology of the second donor-CU includes at least one of the following: Ingress routing indicator (routing ID) for downlink traffic; Ingress BH RLC channel for downlink traffic; and The method is a BAP address of a previous hop of downlink traffic.

[0405] (Appendix 76) 76. The method of any one of claims 71 to 75, comprising: After the first donor-CU receives a second transmission transition change request for the traffic, the method further comprises: The method includes the first donor-CU configuring the IAB node to update uplink BH information of the traffic.

[0406] (Appendix 77) 77. The method of any one of claims 71 to 76, comprising: After the first donor-CU receives a second transmission transition change request for the traffic, the method further comprises: The first donor-CU configures at least one of the following updates to the IAB node: BAP header rewrite information between topologies in the uplink direction, routing information within the topology of the second donor-CU, and BH RLC channel mapping information between topologies in the uplink direction.

[0407] (Appendix 78) 78. The method of any one of claims 71 to 77, comprising: After the first donor-CU receives a second transmission transition change request for the traffic, the method further comprises: The method in which the first donor-CU configures the IAB node to perform at least one of the following updates: BAP header rewrite information between topologies in the downlink direction; and BH RLC channel mapping information between topologies in the downlink direction.

[0408] (Appendix 79) 79. The method of any one of clauses 70 to 78, comprising: The method of claim 1, wherein the first donor-CU receives the second donor-CU sending the second transmission transition change request to change the IP address for the IAB node.

[0409] (Appendix 80) 79. The method of claim 79, The second transmission transition change request is included in second transmission transition management request information.

[0410] (Appendix 81) 79. The method of claim 79, The second transmission transition change request includes the following information: an IAB node identifier or an IP address request index, a BAP address of a donor-DU in the topology of the first donor-CU or a BAP address of a donor-DU in the topology of the second donor-CU, and an IP address anchored to the donor-DU in the topology of the second donor-CU.

[0411] (Appendix 82) 82. The method of any one of claims 79 to 81, comprising: The method further comprises: The method includes the first donor-CU configuring the IAB node with an IP address anchored to a donor-DU in the topology of the second donor-CU.

[0412] (Appendix 83) An IAB donor device, a memory and a processor; The storage device stores a computer program, 83. An IAB donor device, wherein the processor is configured to execute the computer program to implement the transmission transition management method described in any one of Supplementary Notes 1 to 82.

Claims

1. An IAB (Integrated Access and Backhaul) donor device in a second donor-CU, a transmitter that sends an IAB transport migration modification request for traffic for the IAB node migration to a first donor-CU; and a processor for changing resources serving the traffic within the topology of the second donor-CU; An IAB donor device, wherein an IAB-DU of the IAB node maintains an F1 connection with the first donor-CU, and resources serving the traffic are established within the topology of the second donor-CU.

2. 10. The IAB donor device of claim 1, The transmitter sends the IAB transmission transition change request to the first donor-CU to change the routing ID and / or backhaul radio link control channel of the traffic within the topology of the second donor-CU, IAB donor equipment.

3. 10. The IAB donor device of claim 1, The processor includes: updating the backhaul radio link control channel and / or backhaul adaptation protocol sublayer routing that the traffic uses on a path within the topology of the second donor-CU; updating uplink backhaul information of the traffic, the uplink backhaul information including a routing ID, an uplink backhaul radio link control channel, and / or a backhaul adaptation protocol address of a next-hop node; and updating an uplink egress routing ID, an egress backhaul radio link control channel, and / or a backhaul adaptation protocol address of a next-hop node for the traffic, or updating a downlink ingress routing ID, an ingress backhaul radio link control channel, and / or a backhaul adaptation protocol address of a previous-hop node for the traffic; an IAB donor device that performs at least one of the operations.

4. 10. The IAB donor device of claim 1, The IAB transport migration change request is used to change the IP address for the IAB node, IAB donor device.

5. The IAB donor device of claim 4, The IAB transport transition change request includes a Backhaul Adaptation Protocol (BAP) address of a donor-DU in the topology of the second donor-CU, and an IP address anchored to the donor-DU.

6. The IAB donor device of claim 1, The IAB transmission transition change request includes an ID of the traffic and backhaul information (BH information) of the traffic within the topology of the second donor-CU.

7. An IAB (Integrated Access and Backhaul) donor device in a first donor-CU, comprising: a receiver for receiving an IAB transport migration modification request for traffic for migration of the IAB node from the second donor-CU; and a processor for modifying Layer 2 information of the traffic and / or an IP address of the IAB node based on the received IAB transmission transition change request; An IAB donor device, wherein an IAB-DU of the IAB node maintains an F1 connection with the first donor-CU, and resources serving the traffic are established within the topology of the second donor-CU.

8. An IAB (Integrated Access and Backhaul) system, An IAB system comprising: a first donor-CU according to claim 7; and a second donor-CU according to any one of claims 1 to 6.

Images