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 technical field of communications. [Background technology]

[0002] Future seamless cellular network deployment requires highly flexible and ultra-dense new radio (NR) cell deployment, and ultra-dense networks are one of the goals of 5G, so the deployment of NR networks that do not require wired backhaul is very important for the realization of 5G ultra-dense networks. As 5G mmWave reduces cell coverage, wireless self-backhaul systems require multiple hops to meet the deployment needs. With 5G's high bandwidth, massive multiple-input multiple-output (MIMO) and beam systems, 5G makes it easier to develop wireless self-backhaul systems for ultra-dense NR cells than LTE. To develop such a multi-hop system with wireless self-backhaul, 3GPP has started research and standardization of 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, a relay node simultaneously supports the functions of access and backhaul, the relay node multiplexes the access link and the backhaul link in the time domain, frequency domain or spatial domain, and the access link and the backhaul link can use the same or different frequency bands.

[0004] In the IAB network architecture, the relay node refers to the IAB-node, which supports access and backhaul functions simultaneously. The last one-hop access node on the network side is called the IAB-donor, which supports gNB function and supports 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 function of the IAB-node is divided into two parts, one part is the gNB-DU function, called IAB-DU (distributed unit), and the other part is the UE function, called IAB-MT (mobile equipment). The IAB-DU realizes the function of the network side equipment, is connected to the child IAB-node (or abbreviated as child node) of the downflow, provides NR air interface access for the UE and the child IAB-node of the downflow, and establishes an F1 connection with the IAB donor-CU (donor centralized unit). The IAB-MT realizes a part of the function of the terminal equipment, is connected to the parent IAB-node (or abbreviated as parent node) or IAB donor-DU of the upflow, and includes the functions of the physical layer, layer 2, RRC (Radio Resource Control), and NAS (Non-Access Stratum), and is indirectly connected to the IAB Donor-CU and the core network (Core Network, CN).

[0006] In the IAB system, an IAB-node can access the network in 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, a parent IAB-node, and a child IAB-node. As shown in Figure 4, the IAB-DU of the IAB node is connected to the IAB-MT of the child node as the network side, and the IAB-MT of the IAB node is connected to the IAB-DU of the parent node as the terminal side.

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

[0009] In the backhaul link, the transport (IP) layer is carried 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. The BAP PDU (Protocol Data Unit) is carried on the RLC (Radio Link Control) channel of the backhaul link, and multiple RLC channels of the backhaul link may be configured by the IAB-donor to carry traffic (services) with different priorities and QoS (Quality of Service), and the BAP entity maps the BAP PDU to different backhaul RLC channels.

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

[0011] The inventor has found that when a change occurs in the characteristics (or service parameters) of traffic, it may be necessary to change the transmission transition setting 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 for migration), so that the second donor-CU can determine whether the new QoS requirements of the traffic are satisfied, and change the resources serving the traffic in the topology of the second donor-CU. However, there is still no corresponding solution for how to change the transmission transition setting of the traffic.

[0012] To address at least one of the above problems, an embodiment of the present invention provides 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, a transmission transition management method is provided, 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 in a topology of a second donor-CU for serving traffic of the IAB node, 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, a transmission transition management method is provided, 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 in a topology of a second donor-CU for serving traffic of the IAB node, 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, a transmission transition management method is 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 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, a transmission transition management method is 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 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 modifies resources serving the traffic in the topology of the second donor-CU.

[0017] According to another aspect of an embodiment of the present invention, an IAB donor device is provided, 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 sender for sending a first transmission transition change request for the traffic to the second donor-CU; and The second donor-CU includes a receiver for receiving a transmission transition change response for the traffic transmitted by the second donor-CU.

[0018] According to another aspect of an embodiment of the present invention, an IAB donor device is provided, 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.

[0019] According to another aspect of an embodiment of the present invention, an IAB donor device is provided, in which an IAB-DU of an IAB node maintains an F1 connection with a first 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 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 for changing resources serving the traffic in the topology of the second donor-CU.

[0020] According to another aspect of an embodiment of the present invention, an IAB donor device is provided, in which an IAB-DU of an IAB node maintains an F1 connection with a first 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 second transmission transition change request for traffic transmitted by the second donor-CU; Wherein, the second donor-CU modifies resources serving the traffic in the topology of the second donor-CU.

[0021] According to another aspect of an embodiment of the present invention, an IAB system is provided, the IAB system including a first donor concentration unit and a second donor concentration unit, the first donor concentrating unit sending a first transmission transition change request for the traffic and receiving a transmission transition change response for the traffic, and the second donor concentrating unit receiving the first transmission transition change request and sending the transmission transition change response; or The second donor concentration unit sends a second transmission shift change request for the traffic and changes 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. Effect 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 according to the change (change) of the service parameters of the traffic, so as to still satisfy the service requirements of the traffic after the change of the service parameters of the traffic.

[0023] Specific embodiments of the present invention are disclosed in detail below with reference to the following description and drawings, which show how the principles of the present invention may be employed, but are not limited in scope to these embodiments, which may include various changes, modifications, and alternatives within the scope of the appended claims.

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

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

[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 the 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 the embodiments of the present invention, and together with the written description, are used to explain the principles of the present invention. Also, it is obvious that the drawings described below are only for illustrating some embodiments of the present invention, and a person skilled in the art can derive other drawings based on these drawings without creative labor. [Figure 1] FIG. 1 illustrates an IAB system. [Diagram 2] A diagram showing the IAB architecture in SA mode. [Diagram 3] A diagram showing the IAB architecture in EN-DC mode. [Figure 4] FIG. 2 is a diagram showing a parent node (parent IAB-node) and a child node (child IAB-node). [Diagram 5] FIG. 2 illustrates the F1-U protocol stack of the IAB system. [Figure 6]FIG. 2 illustrates the F1-C protocol stack of the IAB system. [Figure 7] FIG. 1 illustrates routing in an IAB system. [Figure 8] FIG. 1 illustrates network topology adaptation. [Figure 9] FIG. 2 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. 13 is a diagram showing a 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. 11 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. 13 illustrates another IAB donor device in accordance with an embodiment of the present invention. [Figure 18] FIG. 13 illustrates another IAB donor device in accordance with an embodiment of the present invention. [Figure 19] FIG. 13 illustrates another IAB donor device in accordance with an embodiment of the present invention. [Figure 20] FIG. 2 illustrates an IAB device in accordance with an embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0028] The above and other features of the present invention will become apparent from the following detailed description and the accompanying drawings, in which: While the specification and drawings disclose certain embodiments of the present invention, these are illustrative of 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 an embodiment of the present invention, the term "communication network" or "wireless communication network" may refer to a network conforming to any communication standard, such as Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

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

[0031] In the embodiment of the present invention, the term "network equipment" refers to an apparatus that connects a terminal equipment to a communication network and provides services to the terminal equipment, for example, in a communication system. 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] Among them, the base station may include, but is not limited to, the following: Node B (NodeB or NB), evolved Node B (eNodeB or eNB), 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 also include some or all of the functions thereof, and each base station can provide communication coverage for a specific geographical area. For example, a 5G base station gNB may include one gNB CU and one or more gNB DUs, in which a CU / DU is a logical node of a gNB having some functions of a gNB. The term "cell" may refer to a base station and / or its coverage area, depending on the context in which the term is used.

[0033] In the embodiment 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, through a network device. The user equipment may be fixed or mobile, and may also be called a mobile station (MS), a terminal, a subscriber station (SS), an access terminal (AT), a station, etc. For example, 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, the following: a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a mobile device, a machine type communication device, a laptop computer, a cordless telephone, a smartphone, a smart watch, a digital camera, etc.

[0035] Furthermore, in a scenario such as the Internet of Things (IoT), the user equipment may also be a monitoring or measuring device or apparatus, 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 the BH routing configuration and the BH RLC channel mapping configuration. The BAP entity performs routing based on the routing configuration, the RLC channel mapping configuration, and the routing ID in the BAP layer data packet header. The Routing ID includes the destination BAP address and the route ID (ID / identifier).

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

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

[0039] The IAB-donor DU stores the BH routing configuration and the Downlink Traffic to BH RLC Channel Mapping Configuration. The IAB-donor DU performs routing based on the routing configuration, the RLC channel mapping configuration, and the Routing ID in the BAP layer data packet header. The routing configuration includes the mapping relationship between the Routing ID and the next hop node address. The downlink RLC channel mapping configuration includes the mapping relationship between the target IP address, the DSCP (Differentiated Services Code Point), the 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 according to the Routing ID in the data packet header. In this way, after determining the next-hop node address, it can find the egress link RLC channel ID from the downlink RLC channel mapping configuration according to the IP address and DSCP of the data packet.

[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 the 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, and the network topology update of the IAB system will be further described below. 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 the IAB-node changes its parent node (from IAB-node 1 to IAB-node 2), the donor-CU configures path transition related configuration for the IAB-node through RRC reconfiguration information, allowing the IAB-node to perform F1 transmission path transition.

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

[0045] 3GPP Rel-17 supports network topology update and backhaul (BH) Radio Link Failure (RLF) recovery processes when an IAB-node moves under a different donor-CU, and the IAB-node can switch or re-establish a parent node serving a source donor-CU (which may be called an F1-terminating CU or a first donor-CU) to a parent node serving a target donor-CU (which may be called a non-F1-terminating CU or a second donor-CU), and all of the IAB-node's traffic (and its child nodes' traffic) needs to 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, and the transmission path of some of the IAB-node's traffic can be migrated to the topology of the non-F1-terminating CU.

[0046] After the IAB-node is switched / RLF restored from donor-CU1 (F1-terminating CU) to donor-CU2 (non-F1-terminating CU), or after the RRC connection with donor-CU2 is increased, only the RRC connection of the IAB-MT goes to donor-CU2 and the F1 interface is still terminated on donor-CU1, at this time the IAB-node may be called 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 are also terminated on donor-CU1, so the child nodes of the boundary node still belong to the topology of donor-CU1.

[0047] In order to allow the uplink traffic of the child node to be transmitted in the topology of donor-CU2, the boundary node needs to replace the routing ID (destination address is the donor-DU BAP address of donor-CU1) of the uplink traffic belonging to the topology of donor-CU1 with the routing ID (destination address is the donor-DU BAP address of donor-CU2) of the uplink traffic belonging to the topology of donor-CU2. In order to allow the downlink traffic of the child node to be transmitted in the topology of donor-CU2, the boundary node needs to replace the routing ID (destination address is the donor DU BAP address of donor-CU2) of the downlink traffic belonging to the topology of donor-CU1 with the routing ID (destination address is the donor DU BAP address of donor-CU1) of the downlink traffic belonging to the topology of donor-CU2. In addition, the uplink traffic of the boundary node itself needs to be updated to the routing ID belonging to the topology of donor-CU2.

[0048] 9 is a diagram illustrating transmission transfer in an embodiment of the present invention. As shown in FIG. 9, the IAB-MT of IAB node 3 is transferred from donor-CU1 to donor-CU2. When the traffic of the child node is transferred 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) to the boundary node.

[0049] When the boundary node forwards uplink data to a 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, in the boundary node, a routing table belonging to the topology of donor-CU2 (before the switching, only the routing table of the topology of donor-CU1 is set in the boundary node) and a BH RLC channel mapping table from the topology of donor-CU1 to the topology of donor-CU2.

[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 of 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 to the boundary node, and the information includes a routing ID, an uplink backhaul RLC channel ID, and a next-hop node address.

[0052] When some or all of the traffic transmission is shifted to the donor-CU2 topology, resources for serving the traffic need to be established in the donor-CU2 topology, e.g., a backhaul BH RLC channel and / or BAP sublayer routing is configured 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 flows of the child nodes, it is necessary to further transmit the routing IDs and BH RLC channels in the topology of donor-CU1 (including the egress routing IDs and egress BH RLC channels of the downlink traffic, and the ingress routing IDs and ingress BH RLC channels of the uplink traffic).

[0055] Donor-CU2 sends to 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); - For downlink traffic, the BAP address of the previous hop in the topology of donor-CU2; - 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) It is.

[0056] In the embodiment of the present invention, unless otherwise specified, the IAB node device includes a transition node or a child node thereof. In addition, "resources for serving the traffic of the IAB node in the topology of the donor-CU have been established" may be expressed as "the 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 embodiment of the present invention will be further described below.

[0057] <Example of the first aspect> In an embodiment of the present invention, a transmission transition management method is provided, which is described from a first donor concentration unit (donor-CU), 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 the traffic of the IAB node in the topology of a second donor-CU have already been established.

[0058] 10 is a diagram showing a transmission transition management method in 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] It should be noted that the above-mentioned FIG. 10 is only for illustrative purposes of the embodiment of the present invention, and the present invention is not limited thereto. For example, the execution order between 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-mentioned contents without being limited to the description of the above-mentioned 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, including, but not limited to, F1 control plane (F1-C) traffic, F1 user plane (F1-U) traffic, and non-F1 traffic.

[0063] In some embodiments, a first donor-CU sends a first transmission transition change request to a second donor-CU to request a change to 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 information such as 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 sending to change resources serving the traffic in 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 This is 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; an 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 the 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 transitioning traffic based on the change (change) in the service parameters of the traffic, so that the service requirements of the traffic can still be satisfied 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 the first donor-CU receives a transmission transition change response for the traffic, for example, for the traffic of an IAB node, configures the IAB node to update 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 describes 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 ID and / or donor distribution unit (donor-DU) in the topology of a first donor-CU for a child node's traffic is changed, 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 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. 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 a transport transition change response from the second donor-CU sending 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 transport migration change response includes information such as: 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.

[0083] In some embodiments, after the first donor-CU receives a transmission transition change response for the IAB node, it configures the IAB node with an IP address that is anchored to a 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 a 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 shift change response to deny the second donor-CU's sending first transmission shift change 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 indication of the traffic.

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

[0089] 11 is a signaling flowchart of 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 message or a TRANSPORT MIGRATION MODIFICATION REQUEST message at least one of the following (for each traffic flow for which modification is requested): -- Traffic signs; and -- QoS information of traffic or traffic type.

[0091] After the QoS of the traffic is changed, 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 that the IP address request (which may be included in the above-mentioned request information, for example) for the boundary node and the child node may be further sent, which may include the following: -- a node identifier or IP address request index; and --IP address request (including the new donor-DU BAP address in donor-CU1's topology), and 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 via a TRANSPORT MIGRATION MANAGEMENT RESPONSE message or a TRANSPORT MIGRATION MODIFICATION RESPONSE message at least one of the following (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); -- the 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 the following: -- a node identifier 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 to reject 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, i.e. -- donor-CU1 updates the QoS mapping information for the traffic; --Update L2 configuration information to include: --- 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 child node traffic, 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 with 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 the donor-DU in the topology of traffic donor-CU1, or the donor-DU has changed due to a change in the 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 the new donor-DU BAP address in donor-CU1's topology), and optionally further including the IP address anchored to that donor-DU.

[0100] - donor-CU2 sends an IP address response to donor-CU1 that includes: -- a node identifier 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 illustratively described in relation to the embodiment of the present invention, but the present invention is not limited thereto, and more specific content of the signaling can be further referred to the related art. In addition, for example, the execution order between each operation can be changed, 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. 11 above.

[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 the transition node 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 the one or more traffics.

[0103] For example, the donor-CU1 initiated transmission migration change process can occur 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 has been 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) have been determined in the topology of the second donor-CU, the first donor-CU sends a first transmission transition change request for the one or more traffics.

[0105] For example, the donor-CU1 initiated transmission migration change process can occur after the migration node has been re-established from a parent node under an F1-terminating CU to a parent node under a non-F1-terminating CU, and all traffic has been 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 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 the one or more traffics.

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

[0108] The above-mentioned embodiments are merely for illustrative purposes, and the present invention is not limited thereto, and appropriate modifications can be made based on the above-mentioned embodiments. For example, the above-mentioned embodiments may be used alone, or a combination of the above-mentioned embodiments may be used.

[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 according to the change (change) of the service parameters of the traffic, so that the service requirements of the traffic can still be satisfied after the service parameters of the traffic are changed.

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

[0111] 12 is a diagram showing 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] It should be noted that the above-mentioned FIG. 12 is for illustrative purposes only, but the present invention is not limited thereto. 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-mentioned contents without being limited to the description of the above-mentioned 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 a service parameter of the traffic changes, 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 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 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 L2-related configuration of the traffic, 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 in 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 of the traffic; or The traffic's downlink ingress routing indicator, ingress BH RLC channel, and / or the 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 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 TRANSPORT MIGRATION MANAGEMENT RESPONSE information.

[0124] In some embodiments, the transmission transition change response includes information such as: a traffic indication 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 This is 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; an 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 a first transmission transition change request from the first donor-CU 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, a 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 information such as: 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] Although the above-mentioned embodiments are illustrative of the embodiments of the present invention, the present invention is not limited thereto, and appropriate modifications can be made based on the above-mentioned embodiments. For example, the above-mentioned embodiments may be used alone, or a combination of the above-mentioned 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 according to the change (change) of the service parameters of the traffic, so that the service requirements of the traffic can still be satisfied after the change of 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 from a second donor concentration unit (donor-CU), 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 in the topology of the second donor-CU for serving the traffic of the IAB node.

[0143] 13 is a diagram showing a transmission transition management method in 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 resources serving the traffic in the topology of the second donor-CU.

[0145] It should be noted that the above-mentioned FIG. 13 is an illustrative example of an embodiment of the present invention, but the present invention is not limited thereto. For example, the execution order between 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-mentioned contents 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 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 in the topology of the second donor-CU for the traffic.

[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; an 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; The 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 be carried by other information.

[0153] In this way, 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 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 modifying resources serving the traffic in the topology of the second donor-CU includes the second donor-CU modifying L2-related information in the topology of the second donor-CU of 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 in 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 of the traffic; or The traffic's downlink ingress routing indicator, ingress BH RLC channel, and / or the BAP address of the previous hop node.

[0156] The above describes the case of changes related 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 transition change request includes information such as: 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 a child node's traffic, 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 a transition node's traffic, 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 a transmission transition change process initiated by the second donor-CU through signaling interaction.

[0163] 14 is a signaling flow chart 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 donor-CU2 in the topology, donor-CU2 requests a change in the routing ID or BH RLC channel of the transition traffic, so as to cause donor-CU1 to update L2 information about 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 message or a TRANSPORT MIGRATION MODIFICATION REQUEST message: -- 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 donor-CU2's topology for uplink traffic.

[0165] Because the donor-DU in the topology of the traffic donor-CU2 may change after the traffic routing ID is changed, the donor-CU2 may further send an IP address indication (e.g., included in the above-mentioned request information), which may include the following: -- a node identifier or IP address request index; and -- IP address indication (including the donor-DU BAP address in donor-CU1's topology and the IP address anchored to donor-DU 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 needs to update the relevant configuration based on this information, including: -- Update L2 related information of traffic, including: --- For transition node traffic, update uplink BH information, including routing indicator, BH RLC channel ID and next hop node address; --- For the child node's traffic, update the BAP 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; -- 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: -- a node identifier 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 illustrative of an embodiment of the present invention, but the present invention is not limited thereto, and more specific content of the signaling can be further referred to the related art. In addition, for example, the execution order between 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 above.

[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 occur after the migration node has been switched from a parent node under an F1-terminating CU to a parent node under a non-F1-terminating CU, and all traffic has been 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) 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.

[0176] For example, the transmission migration change process initiated by donor-CU2 can occur after the migration node has been re-established from a parent node under an F1-terminating CU to a parent node under a non-F1-terminating CU, and all traffic has been 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 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.

[0178] For example, the transmission migration change process initiated by donor-CU2 can occur after the migration node establishes dual connections with F1-terminating CUs and non-F1-terminating CUs, and some of the traffic paths are migrated to the topology of the non-F1-terminating CU.

[0179] Although the above-mentioned embodiments are illustrative of the embodiments of the present invention, the present invention is not limited thereto, and appropriate modifications can be made based on the above-mentioned embodiments. For example, the above-mentioned embodiments may be used alone, or a combination of the above-mentioned 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 can change the L2-related information or IP address of the traffic to ensure the normal transmission of the migration traffic in the topology of the second donor-CU.

[0181] <Example of the fourth aspect> In the embodiment of the present invention, a transmission transition management method is provided, which is described from the perspective of a first donor-CU. The description of the same contents as those in the embodiment of the third aspect is omitted. In this embodiment, an IAB-DU of an IAB node 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.

[0182] 15 is a diagram showing 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 in the topology of the second donor-CU.

[0184] It should be noted 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 between 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-mentioned contents 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 topology of the second donor-CU.

[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 information such as: 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; an 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; The 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 handover change request for the traffic, the first donor-CU configures the IAB node to update uplink BH information of the traffic.

[0191] In some embodiments, after receiving a second transmission transition change request for the traffic, the first donor-CU configures at least one of the following updates in the IAB 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.

[0192] In some embodiments, after receiving a second transmission transition change request for the traffic, the first donor-CU 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.

[0193] In some embodiments, the first donor-CU receives a second donor-CU sending a second transport transition change request to change an 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 from the second donor-CU to change the IP address for the IAB node.

[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 transition change request includes information such as: 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] Although the above-mentioned embodiments are illustrative of the embodiments of the present invention, the present invention is not limited thereto, and appropriate modifications can be made based on the above-mentioned embodiments. For example, the above-mentioned embodiments may be used alone, or a combination of the above-mentioned 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 can change the L2-related information or IP address of the traffic to ensure the normal transmission of the migration traffic in the topology of the second donor-CU.

[0200] <Example of the fifth aspect> In the embodiment of the present invention, an IAB donor device is provided, and the description of the same contents 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., a first donor-CU in the embodiments of the first and second aspects), or may be one or more parts, assemblies, or modules disposed in the IAB donor-CU.

[0201] 16 is a diagram illustrating an IAB donor device according to an embodiment of the present invention, in which an IAB node's IAB-DU maintains an F1 connection with a first donor concentration 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: sending 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 sending unit 1601 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.

[0207] For example, when a change occurs in the service parameters of the traffic, the transmitting unit 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.

[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 transport transition change response is received via transport transition management response information.

[0211] In some embodiments, the first transmission transition change request includes information such as: a traffic signature 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 indication of the traffic, and BH information in the topology of the second donor-CU of 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 This is 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; an 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; Configuring 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 an uplink direction, routing information in the topology of the second donor-CU, and BH RLC channel mapping information between topologies in an 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 migration change request to the second donor-CU to request a change of an IP address for the IAB node.

[0218] 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 sending unit 1601 further sends a first transmission migration 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 transition 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.

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

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

[0223] In some embodiments, the transport migration change response includes information such as: 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 indication 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 sends 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 sends 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 sends a first transmission transition change request for the one or more traffics.

[0230] Although the above-mentioned embodiments are illustrative of the embodiments of the present invention, the present invention is not limited thereto, and appropriate modifications can be made based on the above-mentioned embodiments. For example, the above-mentioned embodiments may be used alone, or a combination of the above-mentioned 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 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 referred to in the related art.

[0232] For convenience, Fig. 16 shows only the connection relationships or signal directions between each component or module, but various related technologies such as bus connection may be adopted as understood by those skilled in the art. Each of the above-mentioned components or modules may be realized by hardware such as a processor, a memory, a transmitter, a receiver, etc., and 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 according to the change (change) of the service parameters of the traffic, so that the service requirements of the traffic can still be satisfied after the change of the service parameters of the traffic.

[0234] <Example of the sixth aspect> In the embodiment of the present invention, an IAB donor device is provided, and the description of the same contents 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 parts, assemblies, or modules disposed in the IAB donor-CU.

[0235] 17 illustrates an IAB donor device diagram according to an embodiment of the present invention, in which an IAB-DU of an IAB node 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: receiving a first transmission transition change request for the traffic of 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 for requesting to change resources serving the traffic in the topology of the second donor-CU of the first donor-CU transmission.

[0241] For example, when a change occurs in the service parameters of the traffic, the receiver 1701 receives a first transmission transition change request for the first donor-CU transmission to request a change in 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 the first transmission transition management request information.

[0243] In some embodiments, the first transmission transition 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 a backhaul (BH) radio link control (RLC) channel and / or BAP sublayer routing that the traffic uses on a 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 transport transition change response is sent via transport transition management response information.

[0250] In some embodiments, the transmission transition change response includes information such as: a traffic indication 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 This is 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; an 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 to request a change of IP address for the IAB node.

[0254] For example, when 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 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 transition 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 migration change response to the first donor-CU to change the IP address for the IAB node, where the transmission migration change response is included in the transmission migration management response information.

[0258] In some embodiments, the transport migration change response includes information such as: 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 handover change response to the first donor-CU to deny the transmission handover 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 indication of the traffic.

[0263] Although the above-mentioned embodiments are illustrative of the embodiments of the present invention, the present invention is not limited thereto, and appropriate modifications can be made based on the above-mentioned embodiments. For example, the above-mentioned embodiments may be used alone, or a combination of the above-mentioned 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 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 referred to in the related art.

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

[0266] 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 according to the change (change) of the service parameters of the traffic, so that the service requirements of the traffic are still satisfied after the change of the service parameters of the traffic.

[0267] <Example of the seventh aspect> In the embodiment of the present invention, an IAB donor device is provided, and the description of the same contents as those 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., a 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 according to 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.

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

[0270] A sending unit 1801: sending a second transmission transition change request for traffic to the first donor-CU; and Processing unit 1802: Changes 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: a traffic sign for 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; an 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; The 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 on 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 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.

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

[0280] 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 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 transition change request includes information such as: 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 sends 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 sends a second transmission transition change request for the one or more traffics.

[0286] Although the above-mentioned embodiments are illustrative of the embodiments of the present invention, the present invention is not limited thereto, and appropriate modifications can be made based on the above-mentioned embodiments. For example, the above-mentioned embodiments may be used alone, or a combination of the above-mentioned 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 referred to in the related art.

[0288] For convenience, only the connection relationships or signal directions between each component or module are shown in Fig. 18, but various related technologies such as bus connection may be adopted as understood by those skilled in the art. Each of the above-mentioned components or modules may be realized by hardware such as a processor, a memory, a transmitter, a 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 can change the L2-related information or IP address of the traffic to ensure the normal transmission of the migration traffic in the topology of the second donor-CU.

[0290] <Example of the eighth aspect> In the embodiment of the present invention, an IAB donor device is provided, and the description of the same contents as those 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 parts, assemblies, or modules disposed in the IAB donor-CU.

[0291] 19 illustrates an IAB donor device diagram according to an embodiment of the present invention, in which an IAB-DU of an IAB node 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 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 within the topology of the second donor-CU of the traffic of the second donor-CU transmission.

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

[0296] In some embodiments, the second transmission transition change request includes the following information: a traffic sign for 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; an 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; The 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: Sets the IAB node to update the uplink BH information of the traffic.

[0301] 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 uplink direction, routing information in 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 transition change request includes information such as: 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] Although the above-mentioned embodiments are illustrative of the embodiments of the present invention, the present invention is not limited thereto, and appropriate modifications can be made based on the above-mentioned embodiments. For example, the above-mentioned embodiments may be used alone, or a combination of the above-mentioned 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 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 referred to in the related art.

[0310] 19 shows only the connection relationships or signal directions between each component or module for convenience, but various related technologies such as bus connection may be adopted as understood by those skilled in the art. Each of the above-mentioned components or modules may be realized by hardware such as a processor, a memory, a transmitter, a receiver, etc., and 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 can change the L2-related information or IP address of the traffic to ensure 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): sending a second transmission transition change request for traffic and changing 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] In an embodiment of the present invention, an IAB device is further provided, which may be an IAB donor device or an IAB node device (a transition node or a child node).

[0318] 20 is a diagram showing 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, and the memory 2002 is 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 realize the transmission transition management method in the embodiment of the first aspect. For example, the processor 2001 may be configured to perform the following control: 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.

[0320] Also, for example, the processor 2001 may be configured to execute a program to realize a transmission transition management method in an 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 realize a transmission transition management method in an embodiment of the third aspect. For example, the processor 2001 may be configured to perform the following controls: sending a second transmission transition change request for traffic to a first donor-CU; and changing 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 realize the transmission transition management method in 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 resources serving the traffic in the topology of the second donor-CU.

[0323] Also, as shown in Fig. 20, the IAB device 2000 may further include a transceiver 2003, an antenna 2004, etc., among which, since the functions of these components are similar to those of the prior art, detailed explanations thereof will be omitted here. Note that the IAB device 2000 does not need to include all the components shown in Fig. 20. Also, the IAB device 2000 may further include components not shown in Fig. 20, and for this, reference can be made to the prior art.

[0324] In an embodiment of the present invention, a computer-readable program is further provided, in which, when the program is executed on an IAB device, the program causes a computer to execute a transmission transition management method in an embodiment of the first to fourth aspects 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, wherein the computer readable program causes a computer to perform the transmission transition management method in an IAB device according to the embodiments of the first to fourth aspects.

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

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

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

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

[0330] (Appendix 1) 1. A method for managing transmission transitions, comprising: 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, 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 according to claim 1, comprising: The method, wherein 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.

[0332] (Appendix 3) 3. The method according to claim 1 or 2, The method, wherein 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.

[0333] (Appendix 4) 4. The method according to 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 according to 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 signature of the traffic, a Quality of Service (QoS) of the traffic, and / or a traffic type.

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

[0337] (Appendix 8) 8. The method according to 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 information such as: a traffic indication of the traffic, and BH information in the topology of a second donor-CU of the traffic.

[0339] (Appendix 10) 10. The method according to 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 A method, comprising: QoS mapping information for downlink traffic.

[0340] (Appendix 11) 10. The method according to 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; an egress BH RLC channel for uplink traffic; and The BAP address of the next hop for uplink traffic.

[0341] (Appendix 12) 12. The method according to 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 includes: The first donor-CU updates QoS mapping information for the traffic.

[0342] (Appendix 13) 13. The method according to 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 includes: 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 according to 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 includes: 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 an uplink direction, routing information in the topology of the second donor-CU, and BH RLC channel mapping information between topologies in an uplink direction.

[0344] (Appendix 15) 14. The method according to 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 includes: 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 a downlink direction; and BH RLC channel mapping information between topologies in a downlink direction.

[0345] (Appendix 16) 16. The method according to any one of claims 1 to 15, comprising: The first donor-CU sends the first transport 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, comprising: The first transmission transition change request is included in first transmission transition management request information.

[0347] (Appendix 18) 17. The method of claim 16, comprising: 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 according to claim 18, comprising: The first transmission transition change request further includes an IP address anchored to the donor-DU.

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

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

[0351] (Appendix 22) 21. The method of claim 20, The method, wherein the transmission migration change response includes information such as 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 according to 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 that is anchored to a donor-DU in the topology of the second donor-CU.

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

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

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

[0356] (Appendix 27) 27. The method according to any one of claims 1 to 26, comprising: 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 in the topology of the second donor-CU, the first donor-CU sends a first transmission transition change request for the one or more traffics.

[0357] (Appendix 28) 27. The method according to any one of claims 1 to 26, comprising: a first donor-CU sending a first transmission transition change request for 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 according to any one of claims 1 to 26, comprising: The method of claim 1, wherein 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, the first donor-CU sends a first transmission transition change request for the one or more traffic.

[0359] (Appendix 30) 1. A method for managing transmission transitions, comprising: 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, 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 method, wherein 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.

[0361] (Appendix 32) 32. The method according to claim 30 or 31, The method, wherein 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.

[0362] (Appendix 33) 33. The method according to 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 signature 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 second donor-CU updates a backhaul (BH) radio link control (RLC) channel and / or a BAP sublayer routing that the traffic uses on a path in the topology of the second donor-CU, or updates QoS mapping information of the traffic after receiving the first transmission transition change request.

[0366] (Appendix 37) 37. The method of any one of claims 30 to 36, comprising: The method, wherein the second donor-CU updates uplink BH information of the traffic after receiving the first transmission transition change request, in which 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 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.

[0368] (Appendix 39) 39. The method according to 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 by using transport migration management response information.

[0370] (Appendix 41) The method according to claim 39 or 40, The transmission transition change response includes information such as: a traffic indication of the traffic, and BH information in the topology of a 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 A method, comprising: 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; an egress BH RLC channel for uplink traffic; and The BAP address of the next hop for uplink traffic.

[0373] (Appendix 44) 44. The method according to 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 first transmission transition change request further includes an IP address anchored to the donor-DU.

[0377] (Appendix 48) 48. The method according to 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 according to claim 48, comprising: The transmission transition change response is included in transmission transition management response information.

[0379] (Appendix 50) 49. The method according to claim 48, comprising: The method, wherein the transmission migration change response includes information such as 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 according to any one of claims 33 to 35, comprising: 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 method for managing transmission transitions, 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 second donor-CU modifying resources serving the traffic in a 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, comprising: The second donor-CU sends the second transport migration change request by using second transport migration management request information.

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

[0388] (Appendix 59) 59. The method of claim 58, 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; an egress BH RLC channel for uplink traffic; and The BAP address of the next hop for uplink traffic.

[0389] (Appendix 60) 59. The method of claim 58, 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; The ingress BH RLC channel for downlink traffic; and The BAP address is a previous hop BAP address for downlink traffic.

[0390] (Appendix 61) 61. The method of any one of claims 55 to 60, comprising: The second donor-CU changing 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 a BAP sublayer routing used by the traffic on a path in 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 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, where 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 claims 55 to 62, comprising: The second donor-CU changing resources serving the traffic in the topology of the second donor-CU, 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; 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 claims 55 to 63, comprising: The second donor-CU sends a second transport 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 method, wherein the second transmission transition change request includes information such as: 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 claims 55 to 66, comprising: a second donor-CU sending a second transmission transition change request for the one or more traffic 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 a topology of the second donor-CU.

[0397] (Appendix 68) 67. The method of any one of claims 55 to 66, comprising: a second donor-CU sending a second 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.

[0398] (Appendix 69) 67. The method of any one of claims 55 to 66, comprising: a second donor-CU sending a second transmission transition change request for the one or more traffic 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.

[0399] (Appendix 70) 1. A method for managing transmission transitions, 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 modifies resources serving the traffic in the topology of the second donor-CU.

[0400] (Appendix 71) 71. The method of claim 70, comprising: The first donor-CU receives the second transmission transition change request to change a routing ID and / or a BH RLC channel in the topology of the second donor-CU of the traffic transmitted by 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 according to claim 71 or 72, The second transmission transition change request includes the following information: a traffic sign for said traffic; and The method further comprises the step of: providing BH information in a 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; an egress BH RLC channel for uplink traffic; and The 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; The ingress BH RLC channel for downlink traffic; and The BAP address is a previous hop BAP address for 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 includes: 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 includes: The method, wherein 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 in 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 includes: The method, wherein the first donor-CU configures at least one of the following updates to the IAB node: BAP header rewrite information between topologies in a downlink direction; and BH RLC channel mapping information between topologies in a downlink direction.

[0408] (Appendix 79) 79. The method of any one of claims 70 to 78, comprising: 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 method, wherein the second transmission transition change request includes information such as: 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 that is 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 are included, The storage device stores a computer program, The processor is configured to execute the computer program to implement the transmission transition management method described in any one of claims 1 to 82.

Claims

1. 1. An integrated access and backhaul IAB donor device, comprising: An IAB-DU of an IAB node maintains an F1 connection with a first donor concentration unit, and resources are established in a topology of a second donor concentration unit for serving traffic of the IAB node, and the device a transmitter for transmitting a first transmission transition change request for the traffic to the second donor concentration unit; and The device includes a receiver for receiving a transmission shift change response for the traffic transmitted by the second donor concentration unit.

2. 2. The device of claim 1, The IAB-MT of the IAB node maintains a radio resource control connection with the second donor concentration unit, or the IAB-MT of the IAB node maintains a radio resource control connection with the first donor concentration unit; The traffic includes at least one or a combination of the following: F1 control plane traffic, F1 user plane traffic, and non-F1 traffic.

3. 2. The device of claim 1, The sending unit sends a first transmission transition change request to the second donor concentration unit to request a change in resources serving the traffic in the topology of the second donor concentration unit; Wherein, the device sends the first transmission transition change request according to first transmission transition management request information.

4. 4. The device of claim 3, The receiver receives a transmission transition change response transmitted by the second donor concentration unit for changing resources serving the traffic within the topology of the second donor concentration unit; Wherein, the device receives the transmission transition change response according to transmission transition management response information.

5. 5. The device of claim 4, The first transmission transition request includes information such as a traffic signature of the traffic, and a quality of service and / or traffic type of the traffic; The transmission transition change response includes information such as: a traffic indication of the traffic, and backhaul information within the topology of a second donor concentration unit of the traffic.

6. 6. The device of claim 5, The backhaul information in the topology of the second donor concentration unit includes at least one of the following: Ingress routing indicator for downlink traffic; an ingress backhaul radio link control channel for downlink traffic; The backhaul adaptation negotiation address of the previous hop of the downlink traffic; and The device is a quality of service mapping information of downlink traffic.

7. 6. The device of claim 5, The backhaul information in the topology of the second donor concentration unit includes at least one of the following: Egress routing indicator for uplink traffic; an egress backhaul radio link control channel for uplink traffic; and The device, which is a backhaul adaptation negotiation address of the next hop for uplink traffic.

8. 2. The device of claim 1, The device further includes a processing unit. The processing unit performs at least one of the following operations: updating quality of service mapping information for the traffic; Configuring the IAB node to update uplink BH information of the traffic; Configure the IAB node to update at least one of the following: backhaul adaptation negotiation header rewrite information between topologies in the uplink direction, routing information in the topology of the second donor concentration unit, and backhaul radio link control channel mapping information between topologies in the uplink direction; and Configure the IAB node to update at least one of the following: backhaul adaptation negotiation header rewrite information between topologies in the downlink direction; and backhaul radio link control channel mapping information between topologies in the downlink direction. This is the operation of the equipment.

9. 9. The device of claim 8, The sending unit further sends a first transmission transition change request to the second donor concentration unit to request a change of IP address for the IAB node.

10. 10. The device of claim 9, the first transmission transition change request is included in first transmission transition management request information; The first transmission transition change request includes at least one of the following information: an IAB node identifier or an IP address request index, a backhaul adaptation negotiation address of a donor distribution unit within the topology of the first donor concentration unit, and an IP address anchored to the donor distribution unit, the device.

11. 10. The device of claim 9, The receiving unit further receives a transmission transition change response of the second donor concentration unit transmission to change an IP address for the IAB node.

12. 12. The apparatus of claim 11, The transmission transition change response is included in transmission transition management response information; The transmission migration change response includes information such as: an IAB node identifier or IP address request index, a backhaul adaptation negotiation address of a donor distribution unit in the topology of the first donor concentration unit, and an IP address anchored to a donor distribution unit in the topology of the second donor concentration unit, the device.

13. 12. The apparatus of claim 11, The processing unit configures the IAB node with an IP address that is anchored to a donor distribution unit within the topology of the second donor concentration unit, the device.

14. 4. The device of claim 3, The receiver further receives a transmission shift change response to reject the first transmission shift change request for the traffic transmitted by the second donor concentration unit; Wherein, the device receives the transmission transition change response through transmission transition management response information, and the transmission transition management response information includes a traffic signature of the traffic.

15. 2. The device of claim 1, When an IAB-MT of the IAB node is switched from the first donor concentration unit to the second donor concentration unit and traffic resources for serving one or more of the IAB nodes are established within the topology of the second donor concentration unit, the transmitter transmits a first transmission transition change request for the one or more traffic; or When an IAB-MT of the IAB node is re-established from the first donor concentration unit to the second donor concentration unit and traffic resources for serving one or more of the IAB nodes are established within the topology of the second donor concentration unit, the transmitter transmits a first transmission transition change request for the one or more traffic; or When an IAB-MT of the IAB node establishes a dual connection with the first donor concentration unit and the second donor concentration unit, and traffic resources for serving one or more of the IAB nodes are established within the topology of the second donor concentration unit, the transmitter transmits a first transmission transition change request for the one or more traffic.

16. 1. An integrated access and backhaul IAB donor device, comprising: An IAB-DU of an IAB node maintains an F1 connection with a first donor concentration unit, and resources are established in a topology of a second donor concentration unit for serving traffic of the IAB node, and the device a transmitter for transmitting a second transmission transition change request for traffic to the first donor concentration unit; and and a processor for modifying resources serving the traffic within a topology of the second donor concentration unit.

17. 17. The apparatus of claim 16, The sending unit sends the second transmission transition change request to the first donor concentration unit to change a routing indicator and / or a backhaul radio link control channel in the topology of the second donor concentration unit of the traffic; Wherein, the device sends the second transmission transition change request according to second transmission transition management request information.

18. 17. The apparatus of claim 16, The processing unit performs at least one of the following operations: updating a backhaul radio link control channel and / or a backhaul adaptation negotiation sublayer routing that the traffic uses on a path within the topology of the second donor concentration unit; Updating uplink backhaul information of the traffic, where the uplink backhaul information includes a routing indicator, an uplink backhaul radio link control channel, and / or a backhaul adaptation negotiation address of a next-hop node; and updating an uplink egress routing indicator, an egress backhaul radio link control channel, and / or a backhaul adaptation conference address of a next-hop node of the traffic, or updating a downlink ingress routing indicator, an ingress backhaul radio link control channel, and / or a backhaul adaptation conference address of a previous-hop node of the traffic; This is the operation of the equipment.

19. 17. The apparatus of claim 16, The sending unit further sends a second transmission transition change request to the first donor concentration unit to change an IP address for the IAB node; Wherein, the second transmission transition change request is included in second transmission transition management request information of the device.

20. 1. An integrated access and backhaul IAB system, comprising: A first donor concentration unit and a second donor concentration unit, the first donor concentrating unit sending a first transmission transition change request for the traffic and receiving a transmission transition change response for the traffic, and the second donor concentrating unit receiving the first transmission transition change request and sending the transmission transition change response; or An IAB system, wherein the second donor concentration unit sends a second transmission transition change request for the traffic and changes resources serving the traffic in the topology of the second donor concentration unit, and the first donor concentration unit receives the second transmission transition change request.

Images