WO2023150974A1 - Iab宿主设备以及传输迁移管理方法 - Google Patents

Iab宿主设备以及传输迁移管理方法 Download PDF

Info

Publication number
WO2023150974A1
WO2023150974A1 PCT/CN2022/075878 CN2022075878W WO2023150974A1 WO 2023150974 A1 WO2023150974 A1 WO 2023150974A1 CN 2022075878 W CN2022075878 W CN 2022075878W WO 2023150974 A1 WO2023150974 A1 WO 2023150974A1
Authority
WO
WIPO (PCT)
Prior art keywords
donor
service
iab
topology
transmission
Prior art date
Application number
PCT/CN2022/075878
Other languages
English (en)
French (fr)
Inventor
路杨
Original Assignee
富士通株式会社
路杨
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 富士通株式会社, 路杨 filed Critical 富士通株式会社
Priority to PCT/CN2022/075878 priority Critical patent/WO2023150974A1/zh
Publication of WO2023150974A1 publication Critical patent/WO2023150974A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements

Definitions

  • the embodiment of the present application relates to the communication field.
  • Ultra-dense networks are one of the goals of 5G. Deploying an NR network that does not require wired backhaul is essential for achieving 5G ultra-dense Networking is very important. Since 5G mmWave reduces the coverage area of the cell, the wireless self-backhaul system requires multiple hops to meet the deployment requirements. 5G's high bandwidth, massive multiple-input multiple-output (MIMO) and beam system make it easier for 5G than LTE to develop a wireless self-backhaul system for ultra-dense NR cells. In order to develop this multi-hop system with wireless self-backhaul, 3GPP started the research and standardization of the integrated access and backhaul (IAB, Integrated access and backhaul) project in Rel-16.
  • IAB integrated access and backhaul
  • FIG. 1 is a schematic diagram of the IAB system.
  • the access and backhaul use the Uu air interface wireless transmission of NR
  • the relay node supports both access and backhaul functions
  • the relay node multiplexes the access link (access link) and the backhaul link (backhaul link) in the time domain, frequency domain or air domain
  • the access link and the backhaul link can use the same or different frequency bands.
  • a relay node refers to an IAB-node (IAB node), which supports both access and backhaul functions.
  • IAB node The last hop access node on the network side is called IAB-donnor (IAB host), which supports gNB function and supports IAB-node access. All UE data can be transmitted back to IAB-donor via IAB-node via one or more hops.
  • IAB-node The function of IAB-node is divided into two parts, one part is gNB-DU function, called IAB-DU (distribution unit), and the other part is UE function, called IAB-MT (mobile terminal).
  • the IAB-DU realizes the function of the network side equipment, connects to the downstream child IAB-node (child IAB node or simply called the child node), provides NR air interface access to the UE and the downstream child IAB-node and communicates with the IAB donor-CU (host centralized Units) have F1 connections established between them.
  • IAB-MT implements part of the terminal equipment functions and connects to the upstream parent IAB-node (parent IAB node or simply referred to as parent node) or IAB donor-DU.
  • IAB-MT includes physical layer, layer 2, RRC (Radio Resource Control, wireless resource control) and NAS (Non-Access Stratum, non-access stratum) layer functions, and is also indirectly connected to the IAB Donor-CU and the core network (Core Network, CN).
  • RRC Radio Resource Control, wireless resource control
  • NAS Non-Access Stratum, non-access stratum
  • the IAB-node can access the network through the independent networking (SA, Standalone) mode or the non-independent networking (EN-DC, E-UTRA-NRDualConnectivity) mode.
  • SA independent networking
  • EN-DC non-independent networking
  • FIG. 2 is a schematic diagram of an IAB architecture in SA mode.
  • Fig. 3 is a schematic diagram of the IAB architecture of the EN-DC mode.
  • Fig. 4 is a schematic diagram of an IAB node (IAB-node), a parent node (parent IAB-node) and a child node (child IAB-node).
  • IAB-node IAB node
  • parent IAB-node parent node
  • child IAB-node child node
  • the IAB-DU of the IAB node is connected to the IAB-MT of the child node as the network side
  • the IAB-MT of the IAB node is connected to the IAB-DU of the parent node as the terminal side.
  • Figure 5 is a schematic diagram of the F1 user plane (F1-U) protocol stack between the IAB-DU and the IAB donor-CU.
  • Figure 6 is a schematic diagram of the F1 control plane (F1-C) protocol stack between the IAB-DU and the IAB donor-CU.
  • F1-U and F1-C are established on the transport (IP) layer between IAB-DU and IAB donor-CU, and in Figure 5 and Figure 6, the two-hop wireless backhaul and one-hop wired backhaul.
  • the transport (IP) layer is carried on the Backhaul Adaptive Protocol (BAP) sublayer, and the BAP entity in the IAB-node realizes the routing function of the IAB system, and the IAB donor-CU provides the routing table.
  • BAP PDU Protocol Data Unit
  • RLC Radio Link Control
  • Multiple RLC channels of the backhaul link can be configured by the IAB-donor to carry different priorities and QoS (Quality of Service) ) business, the BAP entity maps the BAP PDU to different backhaul RLC channels.
  • QoS quality of service
  • embodiments of the present application provide an IAB host device and a method for managing transmission migration.
  • a transmission migration management method wherein, the IAB-DU of the IAB node maintains an F1 connection with the first donor-CU, and in the topology of the second donor-CU Establishing resources for serving the business of the IAB node, the method comprising:
  • the first donor-CU sends a first transmission migration modification request for the service to the second donor-CU;
  • the first donor-CU receives a transmission migration modification response for the service sent by the second donor-CU.
  • a transmission migration management method wherein the IAB-DU of the IAB node maintains an F1 connection with the first donor-CU, and in the topology of the second donor-CU resources for serving the business of the IAB node have been established, the method comprising:
  • the second donor-CU receives the first transmission migration modification request for the service sent by the first donor-CU;
  • the second donor-CU sends a transmission migration modification response for the service to the first donor-CU.
  • a transmission migration management method wherein, the IAB-DU of the IAB node maintains an F1 connection with the first donor-CU, and is established in the topology of the second donor-CU for service
  • the resource of the service of the IAB node includes:
  • the second donor-CU sends a second transmission migration modification request for services to the first donor-CU;
  • the second donor-CU modifies resources serving the service in the topology of the second donor-CU.
  • a transmission migration management method wherein, the IAB-DU of the IAB node maintains an F1 connection with the first donor-CU, and is established in the topology of the second donor-CU for service
  • the resource of the service of the IAB node includes:
  • the first donor-CU receives the second transmission migration modification request for the service sent by the second donor-CU; wherein, the second donor-CU modifies the service in the topology of the second donor-CU resources of the business.
  • an IAB host device wherein the IAB-DU of the IAB node maintains an F1 connection with the first donor central unit (donor-CU), and in the topology of the second donor-CU Establishing resources for serving the business of the IAB node, the device includes:
  • a sending unit which sends a first transmission migration modification request for the service to the second donor-CU;
  • a receiving unit configured to receive a transmission migration modification response for the service sent by the second donor-CU.
  • an IAB host device wherein the IAB-DU of the IAB node maintains an F1 connection with the first donor central unit (donor-CU), and in the topology of the second donor-CU Establishing resources for serving the business of the IAB node, the device includes:
  • a receiving unit which receives the first transmission migration modification request for the service sent by the first donor-CU;
  • a sending unit which sends a transmission migration modification response for the service to the first donor-CU.
  • an IAB host device wherein the IAB-DU of the IAB node maintains an F1 connection with the first donor-CU, and the topology of the second donor-CU has been established to serve all The resource of the service of the IAB node, the device includes:
  • a sending unit which sends a second transmission migration modification request for services to the first donor-CU;
  • a processing unit that modifies resources serving the service in the topology of the second donor-CU.
  • an IAB host device wherein the IAB-DU of the IAB node maintains an F1 connection with the first donor-CU, and the topology of the second donor-CU has been established to serve all The resource of the service of the IAB node, the device includes:
  • a receiving unit which receives a second transmission migration modification request for a service sent by the second donor-CU; wherein, the second donor-CU modifies the service of the service in the topology of the second donor-CU H.
  • an IAB system including a first host centralized unit and a second host centralized unit;
  • the first hosting central unit sends a first transmission migration modification request for the service, and receives a transmission migration modification response for the service;
  • the second hosting centralization unit receives the first transmission migration modification request, and sends the The above transport migration modification response;
  • the second hosting central unit sends a second transmission migration modification request for the service, and modifies resources serving the service in the topology of the second hosting central unit; the first hosting central unit receives the first Two transmit the migration modification request.
  • the first donor-CU sends a first transmission migration modification request for services to the second donor-CU; and the first donor-CU receives the request for the service sent by the second donor-CU The transport migration modification response for the business.
  • the second donor-CU can modify the transmission resource of the service migration service according to the change of the service parameter of the service, so that the service requirement of the service can still be met after the service parameter of the service changes.
  • Fig. 1 is a schematic diagram of the IAB system
  • FIG. 2 is a schematic diagram of the IAB architecture of the SA mode
  • FIG. 3 is a schematic diagram of the IAB architecture of the EN-DC mode
  • Fig. 4 is a schematic diagram of a parent node (parent IAB-node) and a child node (child IAB-node);
  • Fig. 5 is a schematic diagram of the F1-U protocol stack of the IAB system
  • Fig. 6 is a schematic diagram of the F1-C protocol stack of the IAB system
  • Fig. 7 is a schematic diagram of IAB system routing
  • Fig. 8 is a schematic diagram of network topology self-adaptation
  • FIG. 9 is an example diagram of transmission migration in the embodiment of the present application.
  • FIG. 10 is a schematic diagram of a transmission migration management method according to an embodiment of the present application.
  • Fig. 11 is a signaling flowchart of transmission migration modification according to the embodiment of the present application.
  • FIG. 12 is another schematic diagram of the transmission migration management method according to the embodiment of the present application.
  • FIG. 13 is another schematic diagram of the transmission migration management method according to the embodiment of the present application.
  • Fig. 14 is another signaling flowchart of transmission migration modification according to the embodiment of the present application.
  • FIG. 15 is another schematic diagram of the transmission migration management method according to the embodiment of the present application.
  • FIG. 16 is a schematic diagram of an IAB host device according to an embodiment of the present application.
  • FIG. 17 is another schematic diagram of an IAB host device according to an embodiment of the present application.
  • FIG. 18 is another schematic diagram of an IAB host device according to an embodiment of the present application.
  • FIG. 19 is another schematic diagram of an IAB host device according to an embodiment of the present application.
  • FIG. 20 is a schematic diagram of an IAB device according to an embodiment of the present application.
  • the terms “first”, “second”, etc. are used to distinguish different elements from the title, but do not indicate the spatial arrangement or time order of these elements, and these elements should not be referred to by these terms restricted.
  • the term “and/or” includes any and all combinations of one or more of the associated listed items.
  • the terms “comprising”, “including”, “having” and the like refer to the presence of stated features, elements, elements or components, but do not exclude the presence or addition of one or more other features, elements, elements or components.
  • the term “communication network” or “wireless communication network” may refer to a network conforming to any of the following communication standards, such as New Radio (NR, New Radio), Long Term Evolution (LTE, Long Term Evolution), Enhanced Long-term evolution (LTE-A, LTE-Advanced), wideband code division multiple access (WCDMA, Wideband Code Division Multiple Access), high-speed packet access (HSPA, High-Speed Packet Access), etc.
  • NR New Radio
  • New Radio Long Term Evolution
  • LTE-A Long-term evolution
  • LTE-A Long-term evolution
  • WCDMA Wideband Code Division Multiple Access
  • HSPA High-Speed Packet Access
  • the communication between devices in the communication system can be carried out according to any stage of communication protocol, for example, it can include but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and future 5G, 6G, etc., and/or other communication protocols that are currently known or will be developed in the future.
  • 1G generation
  • 2G 2.5G
  • 2.75G 3G
  • 4G 4G
  • 4.5G future 5G, 6G, etc.
  • future 5G, 6G, etc. and/or other communication protocols that are currently known or will be developed in the future.
  • Network device refers to, for example, a device in a communication system that connects a terminal device to a communication network and provides services for the terminal device.
  • Network equipment may include but not limited to the following equipment: base station (BS, Base Station), access point (AP, Access Point), transmission and reception point (TRP, Transmission Reception Point), broadcast transmitter, mobile management entity (MME, Mobile Management Entity), gateway, server, radio network controller (RNC, Radio Network Controller), base station controller (BSC, Base Station Controller) and so on.
  • the base station may include but not limited to: Node B (NodeB or NB), evolved Node B (eNodeB or eNB), and 5G base station (gNB), etc., and may also include Remote Radio Head (RRH, Remote Radio Head) , Remote Radio Unit (RRU, Remote Radio Unit), relay (relay) or low-power node (such as femto, pico, etc.).
  • NodeB Node B
  • eNodeB or eNB evolved Node B
  • gNB 5G base station
  • RRH Remote Radio Head
  • RRU Remote Radio Unit
  • relay relay
  • low-power node such as femto, pico, etc.
  • base station may include some or all of their functions, each base station may provide communication coverage for a particular geographic area.
  • the term "cell” can refer to a base station and/or its coverage area depending on the context in which the term is used.
  • the term "User Equipment” refers to, for example, a device that accesses a communication network through a network device and receives network services, and may also be called “Terminal Equipment” (TE, Terminal Equipment).
  • a terminal device may be fixed or mobile, and may also be referred to as a mobile station (MS, Mobile Station), terminal, user, subscriber station (SS, Subscriber Station), access terminal (AT, Access Terminal), station, etc. wait.
  • the terminal equipment may include but not limited to the following equipment: Cellular Phone (Cellular Phone), Personal Digital Assistant (PDA, Personal Digital Assistant), wireless modem, wireless communication equipment, handheld equipment, machine type communication equipment, laptop computer, Cordless phones, smartphones, smart watches, digital cameras, and more.
  • Cellular Phone Cellular Phone
  • PDA Personal Digital Assistant
  • wireless modem wireless communication equipment
  • handheld equipment machine type communication equipment
  • laptop computer Cordless phones
  • Cordless phones smartphones, smart watches, digital cameras, and more.
  • the terminal device can also be a machine or device for monitoring or measurement, such as but not limited to: a machine type communication (MTC, Machine Type Communication) terminal, Vehicle communication terminal, device to device (D2D, Device to Device) terminal, machine to machine (M2M, Machine to Machine) terminal, etc.
  • MTC Machine Type Communication
  • Vehicle communication terminal device to device (D2D, Device to Device) terminal
  • M2M Machine to Machine
  • the routing function of the IAB system is implemented by the BAP layer, and each IAB-node saves routing configuration (BH routing configuration) and RLC channel mapping configuration (BH RLC Channel Mapping Configuration).
  • the BAP entity performs routing according to the routing configuration, the RLC channel mapping configuration and the routing ID in the BAP layer packet header. Routing ID contains the destination BAP address and route identification.
  • the routing configuration includes the mapping relationship between the Routing ID and the BAP address of the next-hop node.
  • the RLC channel mapping configuration includes the mapping relationship between the BAP address of the previous-hop (prior-hop) node, the RLC channel ID of the ingress link, and the BAP address of the next-hop node and the RLC channel ID of the egress link.
  • Fig. 7 is a schematic diagram of IAB system routing.
  • the next-hop node BAP address can be found from the routing configuration through the routing ID of the data packet header. Both the BAP address of the last hop node and the RLC channel ID of the ingress link are known. In this way, after the BAP address of the next hop node is determined, the RLC channel ID of the egress link can be found through the RLC channel mapping configuration based on the BAP address of the previous hop node + the RLC channel ID of the ingress link + the BAP address of the next hop node.
  • IAB-donor DU saves routing configuration (BH routing configuration) and downlink RLC channel mapping configuration (Downlink Traffic to BH RLC Channel Mapping Configuration).
  • the IAB-donor DU is routed according to the routing configuration, RLC channel mapping configuration and the Routing ID in the BAP layer packet header.
  • the routing configuration includes the mapping relationship between Routing ID and next-hop node address.
  • the downlink RLC channel mapping configuration includes the mapping relationship between the target IP address, DSCP (Differentiated Services Code Point, Differentiated Services Code Point) and the address of the next-hop node and the RLC channel ID of the egress link.
  • 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 the address of the next-hop node is determined, the RLC channel ID of the egress link is found from the downlink RLC channel mapping configuration according to the IP address and DSCP of the data packet.
  • the access IAB node stores uplink backhaul information (BH information), including the routing ID (routing ID) used by the service, uplink backhaul RLC channel ID and next-hop node address.
  • BH information uplink backhaul information
  • the access IAB node configures the routing ID in the BAP layer header of the uplink service according to the uplink BH information and selects the BH RLC channel and next-hop node for uplink service transmission.
  • FIG. 8 is a schematic diagram of intra-CU (intra-CU) topology adaptation.
  • the donor-CU configures the path migration related configuration for the IAB-node through the RRC reconfiguration message, so that the IAB-node performs the migration of the F1 transmission path .
  • Path migration-related configurations include updating the default backhaul RLC channel (default BH RLC channel) for uplink F1-C, F1-U and non-F1 data, updating the default BAP routing ID (default BAP routing ID), and updating Update of IP address routed to Donor-DU.
  • the configuration related to the above-mentioned path migration is applied.
  • the configuration related to the path migration is also performed in the same way.
  • 3GPP Rel-17 supports the network topology update and backhaul (BH) radio link failure (RLF, Radio Link Failure) recovery process when the IAB-node moves under different donor-CUs.
  • the IAB-node can be transferred from the source donor-CU (also known as F1-terminating CU or first donor-CU) service parent switch or re-establish to the parent of target donor-CU (also known as non-F1-terminating CU or second donor-CU) service node, it is necessary to migrate all the services of IAB-node (and the services of its sub-nodes) to the topology of non-F1-terminating CU.
  • Rel-17 also supports the topology redundancy process when IAB-node and non-F1-terminating CU establish dual connections. The transmission path of some services of IAB-node can be migrated to non-F1-terminating CU topology.
  • the IAB-node switches/RLF from donor-CU 1 (F1-terminating CU) to donor-CU 2 (non-F1-terminating CU), or after increasing the RRC connection with donor-CU 2, only the IAB-MT RRC is connected to donor-CU 2, and the F1 interface is still terminated at donor-CU 1.
  • the IAB-node can also be called the boundary node.
  • the RRC connection between the child node it serves and the UE still belongs to donor-CU 1, and the F1 interface of the child node also terminates at donor-CU 1, so the child node of the boundary node still belongs to the topology of donor-CU 1.
  • the boundary node In order to transmit the upstream service of the child node in the topology of donor-CU 2, the boundary node needs to replace the routing ID of the upstream service belonging to the topology of donor-CU 1 (the destination address is the donor-DU BAP address of donor-CU 1) The routing ID of the topology belonging to donor-CU 2 (the destination address is the donor-DU BAP address of donor-CU 2). In order to transmit the downlink service of the child node in the topology of donor-CU 2, the boundary node replaces the routing ID of the downlink service belonging to the topology of donor-CU 2 (the destination address is the donor-DU BAP address of donor-CU 2) with The routing ID of the topology belonging to donor-CU 1 (the destination address is the donor-DU BAP address of donor-CU1). The uplink service of the boundary node itself needs to be updated to the routing ID belonging to the topology of donor-CU 2.
  • FIG. 9 is a schematic diagram of transmission migration according to an embodiment of the present application.
  • the IAB-MT of IAB node 3 migrates from donor-CU 1 to donor-CU 2. If the service of the child node is migrated to the topology of donor-CU 2, the network device will configure the routing ID mapping relationship between the topologies (such as BAP Header Rewriting information) to the boundary node.
  • the network device When the boundary node forwards uplink data to the parent node in the donor-CU2 topology, after replacing the routing ID belonging to donor-CU 1 with the routing ID belonging to donor-CU 2, it is necessary to perform route selection and BH RLC based on the replaced routing ID Channel selection, so the network device will configure the boundary node with a routing table belonging to the topology of donor-CU 2 (before switching, only the routing table of donor-CU 1 topology is configured in the boundary node) and from the topology of donor-CU 1 to donor-CU 2 Topological BH RLC channel mapping table.
  • the network device when forwarding downlink data, it is necessary to perform routing and BH RLC channel selection according to the replaced routing ID, so the network device will configure the boundary node with a downlink BH RLC channel mapping table from the donor-CU 2 topology to the donor-CU 1 topology .
  • the network device needs to configure the uplink feedback information belonging to the donor-CU 2 topology to the boundary node, including the routing ID (routing ID), the uplink backhaul RLC channel ID, and the next Hop node address.
  • resources for serving the service need to be established in the topology of donor-CU 2, for example, the path configured for the service in the topology of donor-CU 1 Backhaul BH RLC channel and/or BAP sublayer routing used on the
  • donor-CU 1 In order to configure the boundary node with the routing table belonging to the donor-CU 2 topology and the BH RLC channel mapping table between the two donor-CU topologies, and to establish resources for service migration services in the donor-CU 2 topology, donor-CU 1 Send transfer migration establishment request to donor-CU 2.
  • donor-CU 1 sends to donor-CU 2 the following information for each service flow requesting migration and an IP address request (including the donor-DU BAP address in the topology of donor-CU 1 and the IP address anchored to the donor-DU ):
  • QoS service quality
  • the service flow for the child node also needs to send the routing ID and BH RLC channel in the topology of donor-CU 1 (including the egress routing ID and egress BH RLC channel of the downlink service, the ingress routing ID and ingress BH RLC channel of the uplink service).
  • donor-CU 2 sends to donor-CU 1 the following information (for each service flow) and an IP address response (including the donor-DU BAP address in the topology of donor-CU 1 and the address of the donor-DU anchored in donor-CU 2 IP address):
  • the routing ID and BH RLC channel of the business in the donor-CU 2 topology (including the ingress routing ID and ingress BH RLC channel of the downlink business, or the egress routing ID and egress BH RLC channel of the uplink business);
  • the IAB node device includes a migration node or its child nodes.
  • “resources established in the topology of the donor-CU to serve the business of the IAB node” may also be referred to as "the business of the IAB node is migrated to the topology of the donor-CU", and the present application is not limited to these expressions. The embodiments of the present application will be further described below.
  • An embodiment of the present application provides a transmission migration management method, which is described from a first donor central unit (donor-CU).
  • the IAB-DU of the IAB node maintains an F1 connection with the first donor central unit (donor-CU), and resources for serving the business of the IAB node have been established in the topology of the second donor-CU.
  • FIG. 10 is a schematic diagram of a transmission migration management method according to an embodiment of the present application. As shown in Figure 10, the method includes:
  • the first donor-CU sends a first transmission migration modification request for services to the second donor-CU;
  • the first donor-CU receives a service transmission migration modification response sent by the second donor-CU.
  • FIG. 10 only schematically illustrates the embodiment of the present application, but the present application is not limited thereto.
  • the execution order of various operations can be appropriately adjusted, and some other operations can be added or some of them can be reduced.
  • Those skilled in the art can make appropriate modifications according to the above content, and are not limited to the above description in FIG. 10 .
  • the IAB-MT of the IAB node maintains an RRC connection with the second donor-CU; for example, the IAB-MT of the migration node maintains an RRC connection with the second donor-CU.
  • the IAB-MT of the IAB node maintains the RRC connection with the first donor-CU; for example, the child node of the transition node maintains the RRC connection with the first donor-CU.
  • the services include at least one or a combination of the following: F1 control plane (F1-C) services, F1 user plane (F1-U) services, and non-F1 services; this embodiment of the application is not limited thereto.
  • F1-C F1 control plane
  • F1-U F1 user plane
  • non-F1 services this embodiment of the application is not limited thereto.
  • the first donor-CU sends to the second donor-CU a first transmission migration modification request for requesting modification of resources serving the service in the second donor-CU topology.
  • the first donor-CU when the service parameter of the service changes, the first donor-CU sends a first transmission to the second donor-CU for requesting modification of resources serving the service in the second donor-CU topology Migrating modification requests.
  • service parameters include QoS (user plane service) and/or service type (non-user plane service).
  • the first transmission migration modification request includes the following information: the service identifier of the service, the quality of service (QoS) and/or service type of the service.
  • the first donor-CU receives a transmission migration modification response sent by the second donor-CU for modifying resources serving the service in the topology of the second donor-CU.
  • the transmission migration modification response includes the following information: the service identifier of the service, and the BH information of the service in the topology of the second donor-CU.
  • the BH information in the topology of the second donor-CU includes at least one of the following:
  • the ingress routing ID (routing ID) of the downlink service is the ingress routing ID (routing ID) of the downlink service
  • the BH information in the topology of the second donor-CU includes at least one of the following:
  • Egress routing ID (routing ID) of uplink service
  • the first donor-CU sends the first transmission migration modification request through the first transmission migration management request (TRANSPORT MIGRATION MANAGEMENT REQUEST) message, and/or, the first donor-CU sends the first transmission migration modification request through the transmission migration management response (TRANSPORT MIGRATION MANAGEMENT RESPONSE) message receives transport migration modification response.
  • the present application is not limited thereto, and what bears the transmission relocation modification request and/or the transmission relocation modification response may also be other messages.
  • the transmission resource of the service migration service can be modified according to the change of the service parameter of the service, so that the service requirement of the business can still be met after the service parameter of the business changes.
  • the following schematically illustrates the situation after the first donor-CU receives the service transmission migration modification response.
  • the first donor-CU after receiving the transmission migration modification response for the service, for example, for the service of the IAB node, the first donor-CU configures and updates the uplink BH information of the service to the IAB node.
  • the first donor-CU receives the transmission migration modification response for the service, for example, for the uplink service of the child node
  • at least one of the following is updated to the IAB node configuration: inter-topology in the uplink direction BAP header rewriting information, routing information in the topology of the second donor-CU, and BH RLC channel mapping information between topologies in the uplink direction.
  • the first donor-CU receives the transmission migration modification response for the service, for example, for the downlink service of the child node, at least one of the following is updated to the IAB node configuration: the topology between the downlink direction BAP header rewriting information, BH RLC channel mapping information between topologies in the downlink direction.
  • the first donor-CU sends to the second donor-CU a first transport migration modification request requesting modification of the IP address for the IAB node.
  • the first donor-CU sends the second donor-CU
  • the CU sends a first transport migration modification request requesting modification of the IP address for the child node.
  • the first transport migration modification request is included in a first transport migration management request message.
  • the first transmission migration modification request includes the following information: an IAB node identifier or an IP address request index, and a BAP address of a donor-DU in the topology of the first donor-CU.
  • the IP address request may further include: an IP address anchored to the donor-DU.
  • the first donor-CU receives a transport migration modification response sent by the second donor-CU for modifying the IP address for the IAB node.
  • the Transport Migration Modification Response is included in a Transport Migration Management Response message.
  • the transport migration modification response includes the following information: IAB node identifier or IP address request index, BAP address of the donor-DU in the topology of the first donor-CU and anchored to the second IP address of the donor-DU in the donor-CU topology.
  • the first donor-CU configures the IP address of the donor-DU anchored in the topology of the second donor-CU to the IAB node after receiving the transmission migration modification response for the IAB node.
  • IP address anchored to IAB donor-DU can be understood as “IP address assigned by donor-DU” or “routable via donor-DU Transport Network Layer (TNL) address (TNL address(es)that is(are)routable via the IAB-donor-DU)", the above terms can be replaced with each other, and this application is not limited thereto.
  • TNL Transport Network Layer
  • the second donor-CU accepts the transmission migration modification request. If the second donor-CU determines that the transmission migration modification request cannot be accepted, for example, the QoS requirement of the modified service cannot be met, the transmission migration modification request may be rejected.
  • the first donor-CU receives the transmission migration modification response sent by the second donor-CU for rejecting the first transmission migration modification request for the service.
  • the first donor-CU receives the transmission migration modification response through a transmission migration management response message.
  • the transmission migration management response message includes the service identifier of the service.
  • the transmission migration modification process initiated by the first donor-CU is further exemplified below through signaling interaction.
  • Fig. 11 is a signaling flowchart of transmission migration modification according to the embodiment of the present application.
  • donor-CU 1 needs to update the QoS of the migrated service, and donor-CU 1 requests to modify the QoS of the migrated service.
  • -donor-CU 1 sends at least one of the following information to donor-CU 2 through the TRANSPORT MIGRATION MANAGEMENT REQUEST message or TRANSPORT MIGRATION MODIFICATION REQUEST message (for each service flow requested to be modified):
  • the routing ID of the service in the topology of donor-CU 1 and the donor-DU in the topology of donor-CU 1 may also change, so it is also possible to send IP address requests for boundary nodes and child nodes (for example, it can be included in the above request message), including:
  • IP address request (including the new donor-DU BAP address in the donor-CU1 topology), optionally, may also include the IP address anchored to the donor-DU.
  • -donor-CU 2 receives the transmission migration modification request, and updates the BH RLC channel and routing of the service on the path in the topology of donor-CU 2 according to the QoS of the modified service; donor-CU 2 may modify the service in the donor-CU Routing ID or BH RLC channel in the topology of 2, or downlink QoS mapping information (such as DSCP value or IPv6 flow label).
  • -donor-CU 2 can send at least one of the following information to donor-CU 1 through the TRANSPORT MIGRATION MANAGEMENT RESPONSE message or TRANSPORT MIGRATION MODIFICATION RESPONSE message (for each service flow requested to be modified):
  • the routing ID and BH RLC channel of the business in the topology of donor-CU 2 (including the ingress routing ID and ingress BH RLC channel of the downlink business, or the egress routing ID and egress BH RLC channel of the uplink business);
  • donor-CU 2 If donor-CU 2 receives an IP address request, it also needs to send an IP address response (for example, it can be included in the above response message), including:
  • the donor-CU 2 determines that it cannot meet the QoS requirements of the modified service, it can reject the transmission migration modification request, and the donor-CU 2 sends a service identification of rejecting the modification to donor-CU 1.
  • donor-CU 1 needs to perform the following updates based on the above information sent by donor-CU 2:
  • --L2 configuration information including:
  • donor-CU 1 configures and updates the uplink BH information of the service to the relocated node.
  • donor-CU1 configures and updates the BAB header rewriting information between the topologies, the routing table belonging to the donor-CU2 topology, and the BH RLC channel mapping table between the two topologies to the migration node.
  • the donor-CU1 also updates the IP address of the migration node and/or child node through an RRC reconfiguration message.
  • donor-CU 1 needs to modify the donor-DU of the service in the topology of donor-CU 1, or modify the routing ID of the service in the topology of donor-CU 1, resulting in a change in the donor-DU.
  • -donor-CU 1 sends an IP address request to donor-CU 2, including:
  • -donor-CU 2 sends an IP address response to donor-CU 1, including:
  • the IAB-MT at the IAB node is switched from the first donor-CU to the second donor-CU, and the topology of the second donor-CU has been established for serving the IAB node (including the migration node and child nodes)
  • the first donor-CU sends a first transmission migration modification request for one or more services.
  • the transmission migration modification process initiated by donor-CU 1 can be switched from the parent node under the F1-terminating CU to the parent node under the non-F1-terminating CU when the migration node is switched, and all services are migrated to the non-F1-terminating CU after the topology.
  • the IAB-MT at the IAB node is re-established from the first donor-CU to the second donor-CU, and the topology of the second donor-CU has been established for serving the IAB node (including the migration node In the case of resources of one or more services of a child node), the first donor-CU sends a first transmission migration modification request for one or more services.
  • the transmission migration modification process initiated by donor-CU 1 can be re-established at the migration node from the parent node under the F1-terminating CU to the parent node under the non-F1-terminating CU, and all services are migrated to the non-F1-terminating CU after the topology.
  • the IAB-MT of the IAB node has dual connections established with the first donor-CU and the second donor-CU, and the topology of the second donor-CU has been established for serving the IAB node (including the migration node and child node), the first donor-CU sends a first transmission migration modification request for one or more services.
  • the transmission migration modification process initiated by donor-CU 1 can be performed after the migration node establishes dual connections with F1-terminating CU and non-F1-terminating CU, and the transmission path of some services is migrated to the topology of non-F1-terminating CU .
  • the first donor-CU sends a first transmission migration modification request for the service to the second donor-CU; and the first donor-CU receives the transmission migration modification for the service sent by the second donor-CU response.
  • the second donor-CU can modify the transmission resource of the service migration service according to the change of the service parameter of the service, so that the service requirement of the service can still be met after the service parameter of the service changes.
  • the embodiment of the present application provides a transmission migration management method, which is described from the perspective of the second donor-CU. The same content as the embodiment of the first aspect will not be repeated.
  • the IAB-DU of the IAB node maintains an F1 connection with the first donor-CU, and resources for serving the business of the IAB node have been established in the topology of the second donor-CU.
  • Fig. 12 is another schematic diagram of the transmission migration management method according to the embodiment of the present application. As shown in Figure 12, the method includes:
  • the second donor-CU receives the first service migration modification request sent by the first donor-CU;
  • the second donor-CU sends a transmission migration modification response for the service to the first donor-CU.
  • FIG. 12 only schematically illustrates the embodiment of the present application, but the present application is not limited thereto.
  • the execution order of various operations can be appropriately adjusted, and some other operations can be added or some of them can be reduced.
  • Those skilled in the art can make appropriate modifications according to the above content, and are not limited to the above description in FIG. 12 .
  • the IAB-MT of the IAB node maintains an RRC connection with the second donor-CU, or, the IAB-MT of the IAB node maintains an RRC connection with the first donor-CU.
  • the services include at least one or a combination of the following: F1 control plane (F1-C) services, F1 user plane (F1-U) services, and non-F1 services.
  • F1-C F1 control plane
  • F1-U F1 user plane
  • non-F1 services F1 control plane
  • the second donor-CU receives a first transmission migration modification sent by the first donor-CU for requesting modification of resources serving the service in the second donor-CU topology ask.
  • the second donor-CU receives the message sent by the first donor-CU for requesting to modify the resource serving the service in the second donor-CU topology A migration modification request is first transmitted.
  • the second donor-CU receives the first transmission migration modification request through a first transmission migration management request (TRANSPORT MIGRATION MANAGEMENT REQUEST) message.
  • TRANSPORT MIGRATION MANAGEMENT REQUEST a first transmission migration management request
  • the first transmission migration modification request includes the following information: a service identifier of the service, a quality of service (QoS) and/or a service type of the service.
  • QoS quality of service
  • the second donor-CU updates the QoS mapping information of the service after receiving the first transmission migration modification request.
  • the second donor-CU updates the L2-related configuration of the service, including at least one of the following:
  • BH radio link control
  • the uplink BH information of the service includes a routing identifier, an uplink BH RLC channel and/or a BAP address of a next-hop node;
  • the downlink ingress (ingress) routing identifier of the service the ingress BH RLC channel and/or the BAP address of the last hop node.
  • the second donor-CU sends to the first donor-CU a transport migration modification response for modifying resources serving the traffic in the topology of the second donor-CU.
  • the second donor-CU sends the transmission migration modification response through a transmission migration management response (TRANSPORT MIGRATION MANAGEMENT RESPONSE) message.
  • TRANSPORT MIGRATION MANAGEMENT RESPONSE transmission migration management response
  • the transmission migration modification response includes the following information: a service identifier of the service, and BH information of the service in the topology of the second donor-CU.
  • the BH information in the topology of the second donor-CU includes at least one of the following:
  • the ingress routing ID (routing ID) of the downlink service is the ingress routing ID (routing ID) of the downlink service
  • the BH information in the topology of the second donor-CU includes at least one of the following:
  • Egress routing ID (routing ID) of uplink service
  • the second donor-CU receives a first transmission migration modification request sent by the first donor-CU for requesting modification of the IP address for the IAB node.
  • the second donor-CU receives the first donor-CU A first transmission migration modification request sent by a donor-CU for requesting modification of the IP address of the IAB node.
  • the first transport migration modification request is included in a first transport migration management request message.
  • the first transmission migration modification request includes the following information: an IAB node identifier or an IP address request index, and a BAP address of a donor-DU in the topology of the first donor-CU.
  • the first transmission migration modification request further includes: an IP address anchored to the donor-DU.
  • the second donor-CU sends a Transport Migration Modification Response to the first donor-CU for modifying the IP address for the IAB node.
  • the Transport Modification Response is included in a Transport Migration Management Response message.
  • the transmission modification response includes the following information: IAB node identification or IP address request index, the BAP address of the donor-DU in the topology of the first donor-CU and the BAP address anchored to the second donor-CU - The IP address of the donor-DU of the CU topology.
  • the second donor-CU after receiving the first transmission migration modification request, rejects the first transmission migration modification request for the service.
  • the second donor-CU rejects the first transmission relocation and modification request for the service after receiving the first transmission relocation and modification request.
  • the second donor-CU sends a transmission migration modification response for rejecting the transmission migration modification request for the service to the first donor-CU.
  • the second donor-CU sends the transport migration modification response through a transport migration management message.
  • the transport migration modification response includes a service identification of the service.
  • the first donor-CU sends a first transmission migration modification request for the service to the second donor-CU; and the first donor-CU receives the transmission migration modification for the service sent by the second donor-CU response.
  • the second donor-CU can modify the transmission resource of the service migration service according to the change of the service parameter of the service, so that the service requirement of the service can still be met after the service parameter of the service changes.
  • the embodiment of the present application provides a transmission migration management method, which is described from the perspective of the second donor central unit (donor-CU).
  • the IAB-DU of the IAB node maintains an F1 connection with the first donor central unit (donor-CU), and resources for serving the business of the IAB node have been established in the topology of the second donor-CU.
  • FIG. 13 is a schematic diagram of a transmission migration management method according to an embodiment of the present application. As shown in Figure 13, the method includes:
  • the second donor-CU sends a second transmission migration modification request for services to the first donor-CU;
  • the second donor-CU modifies resources serving the service in the topology of the second donor-CU.
  • FIG. 13 only schematically illustrates the embodiment of the present application, but the present application is not limited thereto.
  • the execution order of various operations can be appropriately adjusted, and some other operations can be added or some of them can be reduced.
  • Those skilled in the art can make appropriate modifications according to the above content, and are not limited to the above description in FIG. 13 .
  • the IAB-MT of the IAB node maintains an RRC connection with the second donor-CU; for example, the IAB-MT of the migration node maintains an RRC connection with the second donor-CU.
  • the IAB-MT of the IAB node maintains the RRC connection with the first donor-CU; for example, the child node of the transition node maintains the RRC connection with the first donor-CU.
  • the services include at least one or a combination of the following: F1 control plane (F1-C) services, F1 user plane (F1-U) services, and non-F1 services; this embodiment of the application is not limited thereto.
  • F1-C F1 control plane
  • F1-U F1 user plane
  • non-F1 services this embodiment of the application is not limited thereto.
  • the second donor-CU sends to the first donor-CU the first donor-CU for modifying the routing ID (routing ID) and/or BH RLC channel of the service in the topology of the second donor-CU Two transmit the migration modification request.
  • the second transmission migration modification request includes the following information: a service identifier of the service; and BH information of the service in the topology of the second donor-CU.
  • the BH information in the topology of the second donor-CU includes at least one of the following:
  • Egress routing ID (routing ID) of uplink service
  • the BH information in the topology of the second donor-CU includes at least one of the following:
  • the ingress routing ID (routing ID) of the downlink service is the ingress routing ID (routing ID) of the downlink service
  • the last hop BAP address of the downlink service is the last hop BAP address of the downlink service.
  • the second donor-CU sends the second transmission migration modification request through a second transmission migration management request (TRANSPORT MIGRATION MANAGEMENT REQUEST) message.
  • TRANSPORT MIGRATION MANAGEMENT REQUEST a second transmission migration management request
  • the present application is not limited thereto, and other messages may also be used to carry the transmission migration modification request.
  • the first donor-CU can modify the L2 related information of the service through the second transmission migration modification request, so as to ensure that the migrated service can be transferred to the second donor.
  • - Normal transfer in CU topology
  • the second donor-CU modifies resources serving the service in the topology of the second donor-CU, including updating the L2 of the service in the topology of the second donor-CU by the second donor-CU Relevant information, for example, L2 related information includes at least one of the following information:
  • the uplink BH information of the service wherein, the uplink BH information includes a route identifier, an uplink BH RLC channel and/or a BAP address of a next-hop node.
  • the downlink ingress (ingress) routing identifier of the service the ingress BH RLC channel and/or the BAP address of the last hop node.
  • the second donor-CU sends to the first donor-CU a second transport migration modification request for modifying the IP address for the IAB node.
  • the second donor-CU sends to the first donor-CU a second transmission migration modification request for modifying the IP address of the IAB node (including the migration node or child node).
  • the second transport migration modification request is included in a second transport migration management request message.
  • the second transmission migration modification request includes the following information: IAB node identifier or IP address request index, the BAP address of the donor-DU in the topology of the first donor-CU or the second donor - the BAP address of the donor-DU in the topology of the CU, and the IP address of the donor-DU anchored to said second donor-CU topology.
  • the second transmission migration modification request includes the following information: IAB node identifier or IP address request index, the BAP address of the donor-DU in the topology of the first donor-CU, and the BAP address anchored in the first donor-CU The IP address of the donor-DU in the second donor-CU topology.
  • the second transmission relocation modification request includes the following information: IAB node identifier or IP address request index, the BAP address of the donor-DU in the topology of the second donor-CU, and anchored in The IP address of the donor-DU of the second donor-CU topology.
  • the transmission migration modification process initiated by the second donor-CU is further exemplified below through signaling interaction.
  • Fig. 14 is a signaling flowchart of transmission migration modification according to the embodiment of the present application. For example, when the routing ID or BH RLC channel of the service in the topology of donor-CU 2 changes, donor-CU 2 requests to modify the routing ID or BH RLC channel of the migrated service, so that donor-CU 1 updates the service-related L2 information.
  • -donor-CU 2 can send the following information to donor-CU 1 through the TRANSPORT MIGRATION MANAGEMENT REQUEST message or the TRANSPORT MIGRATION MODIFICATION REQUEST message (for the business flow modified by each request):
  • the routing ID and BH RLC channel of the business in the topology of donor-CU 2 (including the ingress routing ID and ingress BH RLC channel of the downlink business, or the egress routing ID and egress BH RLC channel of the uplink business);
  • the donor-CU 2 may also send IP address indications (e.g. included in the request message above), including:
  • -donor-CU 2 needs to update the BH RLC channel and route of the service on the path in the topology of donor-CU 2 according to the new routing ID or BH RLC channel of the service in the topology of donor-CU 2.
  • -donor-CU 1 does not need to respond when it receives the transmission migration modification request, it only needs to update the relevant configuration according to the information, including:
  • the donor-CU 2 needs to modify the IP address of the service, or changing the donor-DU in the topology of the donor-CU 2 results in the need to update the IP address of the service.
  • -donor-CU 2 sends an IP address indication to donor-CU 1, including:
  • -donor-CU 1 does not need to respond after receiving the above information, and only needs to update the IP addresses of the migration node and child nodes through the RRC reconfiguration message.
  • the IAB-MT at the IAB node is switched from the first donor-CU to the second donor-CU, and the topology of the second donor-CU has been established for serving the IAB node (including the migration node and child nodes)
  • the second donor-CU sends a second transmission migration modification request for one or more services.
  • the transmission migration modification process initiated by donor-CU 2 can be switched from the parent node under the F1-terminating CU to the parent node under the non-F1-terminating CU when the migration node is switched, and all services are migrated to the non-F1-terminating CU after the topology.
  • the IAB-MT at the IAB node is re-established from the first donor-CU to the second donor-CU, and the topology of the second donor-CU has been established for serving the IAB node (including the migration node In the case of resources of one or more services of a child node), the second donor-CU sends a second transmission migration modification request for one or more services.
  • the transmission migration modification process initiated by donor-CU 2 can be re-established at the migration node from the parent node under the F1-terminating CU to the parent node under the non-F1-terminating CU, and all services are migrated to the non-F1-terminating CU after the topology.
  • the IAB-MT of the IAB node has dual connections established with the first donor-CU and the second donor-CU, and the topology of the second donor-CU has been established for serving the IAB node (including the migration node and child node), the second donor-CU sends a second transmission migration modification request for one or more services.
  • the transmission migration modification process initiated by donor-CU 2 can be performed after the migration node establishes dual connections with F1-terminating CU and non-F1-terminating CU, and the transmission path of some services is migrated to the topology of non-F1-terminating CU .
  • the second donor-CU sends a second transmission migration modification request for the service to the first donor-CU; resource. Therefore, when the second donor-CU modifies the resources used to serve the service or modifies the IP address of the IAB node, the first donor-CU can modify the L2 related information or IP address of the service to ensure that the migrated service is Normal transfer in the second donor-CU topology.
  • the embodiment of the present application provides a transmission migration management method, which is described from the perspective of the first donor-CU. The same content as the embodiment of the third aspect will not be repeated.
  • the IAB-DU of the IAB node maintains an F1 connection with the first donor-CU, and resources for serving the business of the IAB node have been established in the topology of the second donor-CU.
  • Fig. 15 is another schematic diagram of the transmission migration management method according to the embodiment of the present application. As shown in Figure 15, the method includes:
  • the first donor-CU receives a second transmission migration modification request for a service sent by a second donor-CU; wherein, the second donor-CU modifies resources serving the service in the topology of the second donor-CU.
  • FIG. 15 only schematically illustrates the embodiment of the present application, but the present application is not limited thereto.
  • the execution order of various operations can be appropriately adjusted, and some other operations can be added or some of them can be reduced.
  • Those skilled in the art can make appropriate modifications according to the above content, and are not limited to the above description in FIG. 15 .
  • the first donor-CU receives the information sent by the second donor-CU for modifying the routing ID (routing ID) and/or BH RLC channel of the service in the topology of the second donor-CU
  • the second transmits a migration modification request.
  • the first donor-CU receives the second transmission migration modification request through a second transmission migration management request (TRANSPORT MIGRATION MANAGEMENT REQUEST) message.
  • TRANSPORT MIGRATION MANAGEMENT REQUEST a second transmission migration management request
  • the second transmission migration modification request includes the following information: a service identifier of the service; BH information of the service in the topology of the second donor-CU.
  • the BH information in the topology of the second donor-CU includes at least one of the following:
  • Egress routing ID (routing ID) of uplink service
  • the BH information in the topology of the second donor-CU includes at least one of the following:
  • the ingress routing ID (routing ID) of the downlink service is the ingress routing ID (routing ID) of the downlink service
  • the last hop BAP address of the downlink service is the last hop BAP address of the downlink service.
  • the first donor-CU after receiving the second transmission migration modification request for the service, configures and updates the uplink BH information of the service to the IAB node.
  • the first donor-CU after receiving the second transmission migration modification request for the service, updates at least one of the following configurations to the IAB node: BAP header rewriting between topologies in the uplink direction information, routing information in the topology of the second donor-CU, and BH RLC channel mapping information between topologies in the uplink direction.
  • the first donor-CU after receiving the second transmission migration modification request for the service, updates at least one of the following configurations to the IAB node: BAP header rewriting between topologies in the downlink direction Information, BH RLC channel mapping information between topologies in the downlink direction.
  • the first donor-CU receives a second transmission migration modification request sent by the second donor-CU for modifying the IP address for the IAB node.
  • the first donor-CU receives the second donor - a second transmission migration modification request sent by the CU for modifying the IP address of the IAB node.
  • the second transport migration modification request is included in a second transport migration management request message.
  • the second transmission migration modification request includes the following information: IAB node identifier or IP address request index, the BAP address of the donor-DU in the topology of the first donor-CU or the second donor - the BAP address of the donor-DU in the topology of the CU, and the IP address of the donor-DU anchored to said second donor-CU topology.
  • the first donor-CU configures the IAB node with the IP address of the donor-DU anchored to the second donor-CU topology.
  • the second donor-CU sends a second transmission migration modification request for the service to the first donor-CU; resource. Therefore, when the second donor-CU modifies the resources used to serve the service or modifies the IP address of the IAB node, the first donor-CU can modify the L2 related information or IP address of the service to ensure that the migrated service is Normal transfer in the second donor-CU topology.
  • the embodiment of the present application provides an IAB host device, and the same content as the embodiment of the first aspect will not be repeated.
  • the device can be, for example, an IAB donor-CU in the IAB system (such as the first donor-CU in the first and second embodiments), or it can be one or some components configured in the IAB donor-CU Or components or modules.
  • FIG. 16 is a schematic diagram of an IAB host device according to an embodiment of the present application.
  • the IAB-DU of the IAB node maintains an F1 connection with the first donor central unit (donor-CU), and resources for serving the business of the IAB node have been established in the topology of the second donor-CU.
  • donor-CU first donor central unit
  • the IAB host device 1600 includes:
  • a sending unit 1601 which sends a first transmission migration modification request for the service to the second donor-CU;
  • the receiving unit 1602 is configured to receive a transmission migration modification response for the service sent by the second donor-CU.
  • the IAB-MT of the IAB node maintains an RRC connection with the second donor-CU, or, the IAB-MT of the IAB node maintains an RRC connection with the first donor-CU.
  • the services include at least one or a combination of the following: F1 control plane services, F1 user plane services, and non-F1 services.
  • the sending unit 1601 sends to the second donor-CU a first transmission migration modification request for requesting modification of resources serving the service in the second donor-CU topology.
  • the sending unit 1601 sends to the second donor-CU the first message for requesting modification of resources serving the business in the topology of the second donor-CU. - Transmitting a migration modification request.
  • the first transport migration modification request is sent via a first transport migration management request message.
  • the receiving unit 1602 receives a transmission migration modification response sent by the second donor-CU for modifying resources serving the service in the topology of the second donor-CU.
  • the Transport Migration Modification Response is received via a Transport Migration Management Response message.
  • the first transmission migration modification request includes the following information: a service identifier of the service, a quality of service and/or a service type of the service.
  • the transmission migration modification response includes the following information: a service identifier of the service, and BH information of the service in the topology of the second donor-CU.
  • the BH information in the topology of the second donor-CU includes at least one of the following:
  • the ingress routing ID (routing ID) of the downlink service is the ingress routing ID (routing ID) of the downlink service
  • the BH information in the topology of the second donor-CU includes at least one of the following:
  • Egress routing ID (routing ID) of uplink service
  • the IAB host device 1600 further includes:
  • BAP header rewriting information between topologies in the downlink direction BAP header rewriting information between topologies in the downlink direction
  • BH RLC channel mapping information between topologies in the downlink direction.
  • the sending unit 1601 further sends to the second donor-CU a first transmission migration modification request for requesting modification of the IP address for the IAB node.
  • the sending unit 1601 when the routing ID (routing ID) and/or donor distribution unit (donor-DU) in the topology of the first donor-CU of the service is changed, the sending unit 1601 also sends a message to the second The donor-CU sends a first transport migration modification request for requesting modification of the IP address for the IAB node.
  • routing ID routing ID
  • donor-DU donor distribution unit
  • the first transport migration modification request is included in a first transport migration management request message.
  • the first transmission migration modification request includes at least one of the following information: IAB node identifier or IP address request index, BAP address of the donor-DU in the topology of the first donor-CU, anchor Set to the IP address of the donor-DU.
  • the receiving unit 1602 also receives a transmission migration modification response sent by the second donor-CU for modifying the IP address of the IAB node.
  • the Transport Migration Modification Response is included in a Transport Migration Management Response message.
  • the transport migration modification response includes the following information: IAB node identifier or IP address request index, BAP address of the donor-DU in the topology of the first donor-CU and anchored to the second IP address of the donor-DU in the donor-CU topology.
  • the processing unit 1603 configures the IP address of the topology donor-DU anchored to the second donor-CU to the IAB node.
  • the receiving unit 1602 further receives a transmission migration modification response sent by the second donor-CU for rejecting the first transmission migration modification request for the service.
  • the transport migration modification response is received through a transport migration management response message; the transport migration management response message includes a service identifier of the service.
  • the IAB-MT at the IAB node is switched from the first donor-CU to the second donor-CU, and the topology of the second donor-CU has been established to serve the In the case of resources of one or more services of the IAB node, the sending unit 1601 sends a first transmission migration modification request for the one or more services.
  • the IAB-MT at the IAB node is re-established from the first donor-CU to the second donor-CU, and the topology of the second donor-CU is established for serving
  • the sending unit 1601 sends a first transmission migration modification request for the one or more services.
  • the IAB-MT of the IAB node establishes a dual connection with the first donor-CU and the second donor-CU, and the topology of the second donor-CU is established for
  • the sending unit 1601 sends a first transmission migration modification request for the one or more services.
  • the IAB host device 1600 in the embodiment of the present application may also include other components or modules, and for specific content of these components or modules, reference may be made to related technologies.
  • FIG. 16 only exemplarily shows the connection relationship or signal direction between various components or modules, but it should be clear to those skilled in the art that various related technologies such as bus connection can be used.
  • the above-mentioned components or modules may be implemented by hardware facilities such as processors, memories, transmitters, receivers, etc.; the implementation of the present application is not limited thereto.
  • the first donor-CU sends a first transmission migration modification request for the service to the second donor-CU; and the first donor-CU receives the transmission migration modification for the service sent by the second donor-CU response.
  • the second donor-CU can modify the transmission resource of the service migration service according to the change of the service parameter of the service, so that the service requirement of the service can still be met after the service parameter of the service changes.
  • the embodiment of the present application provides an IAB host device, and the same content as the embodiment of the second aspect will not be repeated.
  • the device can be, for example, an IAB donor-CU in the IAB system (such as the second donor-CU in the embodiments of the first and second aspects), or it can be one or some components configured in the IAB donor-CU Or components or modules.
  • FIG. 17 is a schematic diagram of an IAB host device according to an embodiment of the present application.
  • the IAB-DU of the IAB node maintains an F1 connection with the first donor-CU, and resources for serving the business of the IAB node have been established in the topology of the second donor-CU.
  • the IAB host device 1700 includes:
  • a receiving unit 1701 which receives a first transmission migration modification request for the service sent by the first donor-CU;
  • the sending unit 1702 which sends a transmission migration modification response for the service to the first donor-CU.
  • the IAB-MT of the IAB node maintains an RRC connection with the second donor-CU, or, the IAB-MT of the IAB node maintains an RRC connection with the first donor-CU.
  • the services include at least one or a combination of the following: F1 control plane (F1-C) services, F1 user plane (F1-U) services, and non-F1 services.
  • F1-C F1 control plane
  • F1-U F1 user plane
  • non-F1 services F1 control plane
  • the receiving unit 1701 receives a first transmission migration modification request sent by the first donor-CU for requesting modification of resources serving the service in the second donor-CU topology.
  • the receiving unit 1701 receives the request for modifying the resource serving the service in the topology of the second donor-CU sent by the first donor-CU.
  • a migration modification request is first transmitted.
  • the first transport migration modification request is received via a first transport migration management request message.
  • the first transmission migration modification request includes the following information: a service identifier of the service, a quality of service (QoS) and/or a service type of the service.
  • QoS quality of service
  • the IAB host device 1700 further includes:
  • the processing unit 1703 which updates the backhaul (BH) radio link control (RLC) channel and/or BAP sublayer route used by the service on the path in the topology of the second donor-CU, or updates the Service QoS mapping information.
  • BH backhaul
  • RLC radio link control
  • the processing unit 1703 updates the uplink BH information of the service; wherein the uplink BH information includes a routing identifier, an uplink BH RLC channel and/or a BAP address of a next-hop node.
  • the processing unit 1703 updates the uplink exit (egress) routing identifier of the service, the exit BH RLC channel and/or the BAP address of the next hop node; or, updates the downlink entry (ingress) route of the service Identification, BAP address of the entry BH RLC channel and/or previous hop node.
  • the sending unit 1702 sends a transmission migration modification response for modifying resources serving the service in the topology of the second donor-CU to the first donor-CU.
  • the Transport Migration Modification Response is sent via a Transport Migration Management Response message.
  • the transmission migration modification response includes the following information: a service identifier of the service, and BH information of the service in the topology of the second donor-CU.
  • the BH information in the topology of the second donor-CU includes at least one of the following:
  • the ingress routing ID (routing ID) of the downlink service is the ingress routing ID (routing ID) of the downlink service
  • the BH information in the topology of the second donor-CU includes at least one of the following:
  • Egress routing ID (routing ID) of uplink service
  • the receiving unit 1701 receives a first transmission migration modification request sent by the first donor-CU for requesting modification of the IP address of the IAB node.
  • the receiving unit 1701 receives the first donor - A first transport migration modification request sent by the CU for requesting modification of the IP address for the IAB node.
  • the first transport migration modification request is included in a first transport migration management request message.
  • the first transmission migration modification request includes at least one of the following information: IAB node identifier or IP address request index, BAP address of the donor-DU in the topology of the first donor-CU, anchor Set to the IP address of the donor-DU.
  • the sending unit 1702 also sends a transmission migration modification response for modifying the IP address of the IAB node to the first donor-CU.
  • the transmission migration modification response is included in the transmission migration management response message.
  • the transport migration modification response includes the following information: IAB node identifier or IP address request index, BAP address of the donor-DU in the topology of the first donor-CU and anchored to the second IP address of the donor-DU in the donor-CU topology.
  • the processing unit 1703 after receiving the first transmission migration modification request, rejects the first transmission migration modification request for the service.
  • the processing unit 1703 rejects the first transmission relocation modification request for the service.
  • the sending unit 1702 sends a transmission migration modification response for rejecting the transmission migration modification request for the service to the first donor-CU.
  • the second donor-CU sends the transport migration modification response through a transport migration management message.
  • the transmission migration modification response includes the service identifier of the service.
  • the IAB host device 1700 in the embodiment of the present application may also include other components or modules, and for specific content of these components or modules, reference may be made to related technologies.
  • FIG. 17 only exemplarily shows the connection relationship or signal direction between various components or modules, but it should be clear to those skilled in the art that various related technologies such as bus connection can be used.
  • the above-mentioned components or modules may be implemented by hardware facilities such as processors, memories, transmitters, receivers, etc.; the implementation of the present application is not limited thereto.
  • the first donor-CU sends a first transmission migration modification request for the service to the second donor-CU; and the first donor-CU receives the transmission migration modification for the service sent by the second donor-CU response.
  • the second donor-CU can modify the transmission resource of the service migration service according to the change of the service parameter of the service, so that the service requirement of the service can still be met after the service parameter of the service changes.
  • the embodiment of the present application provides an IAB host device, and the same content as the embodiment of the third aspect will not be repeated.
  • the device can be, for example, an IAB donor-CU in the IAB system (such as the second donor-CU in the embodiments of the third and fourth aspects), or it can be one or some components configured in the IAB donor-CU Or components or modules.
  • FIG. 18 is a schematic diagram of an IAB host device according to an embodiment of the present application.
  • the IAB-DU of the IAB node maintains an F1 connection with the first donor central unit (donor-CU), and resources for serving the business of the IAB node have been established in the topology of the second donor-CU.
  • donor-CU first donor central unit
  • the IAB host device 1800 includes:
  • a sending unit 1801 which sends a second transmission migration modification request for services to the first donor-CU;
  • a processing unit 1802 which modifies resources serving the service in the topology of the second donor-CU.
  • the sending unit 1801 sends to the first donor-CU the first donor-CU for modifying the routing ID (routing ID) and/or BH RLC channel of the service in the topology of the second donor-CU. Two transmit the migration modification request.
  • the second transport migration modification request is sent through a second transport migration management request (TRANSPORT MIGRATION MANAGEMENT REQUEST) message.
  • TRANSPORT MIGRATION MANAGEMENT REQUEST a second transport migration management request
  • the second transmission migration modification request includes the following information:
  • the BH information in the topology of the second donor-CU includes at least one of the following:
  • Egress routing ID (routing ID) of uplink service
  • the BH information in the topology of the second donor-CU includes at least one of the following:
  • the ingress routing ID (routing ID) of the downlink service is the ingress routing ID (routing ID) of the downlink service
  • the last hop BAP address of the downlink service is the last hop BAP address of the downlink service.
  • the processing unit 1802 updates the BH RLC channel and/or BAP sublayer route used by the service on the path in the topology of the second donor-CU.
  • the processing unit 1802 updates the uplink BH information of the service; wherein, the uplink BH information includes a routing identifier, an uplink BH RLC channel and/or a BAP address of a next-hop node.
  • the processing unit 1802 updates the uplink exit (egress) routing identifier of the service, the exit BH RLC channel and/or the BAP address of the next hop node; or, updates the downlink entry (ingress) route of the service Identification, BAP address of the entry BH RLC channel and/or previous hop node.
  • the sending unit 1801 further sends a second transmission migration modification request for modifying the IP address of the IAB node to the first donor-CU.
  • the sending unit 1801 when the routing ID (routing ID) and/or the donor distribution unit (donor-DU) in the topology of the second donor-CU of the service is changed, the sending unit 1801 also sends a message to the first The donor-CU sends a second transport migration modification request for modifying the IP address for the IAB node.
  • the second transport migration modification request is included in a second transport migration management request message.
  • the second transmission migration modification request includes the following information: IAB node identifier or IP address request index, the BAP address of the donor-DU in the topology of the first donor-CU or the second donor-CU The BAP address of the donor-DU in the topology of the first donor-CU, and the IP address of the donor-DU anchored to the second donor-CU topology.
  • the IAB-MT at the IAB node is switched from the first donor-CU to the second donor-CU, and the topology of the second donor-CU has been established to serve the In the case of resources of one or more services of the IAB node, the sending unit 1801 sends a second transmission migration modification request for the one or more services.
  • the IAB-MT at the IAB node is re-established from the first donor-CU to the second donor-CU, and the topology of the second donor-CU is established for serving
  • the sending unit 1801 sends a second transmission migration modification request for the one or more services.
  • the IAB-MT of the IAB node establishes a dual connection with the first donor-CU and the second donor-CU, and the topology of the second donor-CU is established for
  • the sending unit 1801 sends a second transmission migration modification request for the one or more services.
  • the IAB host device 1800 in the embodiment of the present application may also include other components or modules, and for specific content of these components or modules, reference may be made to related technologies.
  • FIG. 18 only exemplarily shows the connection relationship or signal direction between various components or modules, but it should be clear to those skilled in the art that various related technologies such as bus connection can be used.
  • the above-mentioned components or modules may be implemented by hardware facilities such as processors, memories, transmitters, receivers, etc.; the implementation of the present application is not limited thereto.
  • the second donor-CU sends a second transmission migration modification request for the service to the first donor-CU; resource. Therefore, when the second donor-CU modifies the resources used to serve the service or modifies the IP address of the IAB node, the first donor-CU can modify the L2 related information or IP address of the service to ensure that the migrated service is Normal transfer in the second donor-CU topology.
  • the embodiment of the present application provides an IAB host device, and the same content as the embodiment of the fourth aspect will not be repeated.
  • the device can be, for example, an IAB donor-CU in the IAB system (such as the first donor-CU in the third and fourth embodiments), or it can be one or some components configured in the IAB donor-CU Or components or modules.
  • FIG. 19 is a schematic diagram of an IAB host device according to an embodiment of the present application.
  • the IAB-DU of the IAB node maintains an F1 connection with the first donor-CU, and resources for serving the business of the IAB node have been established in the topology of the second donor-CU.
  • the IAB host device 1900 includes:
  • the receiving unit 1901 receives a second transmission migration modification request for a service sent by the second donor-CU; wherein the second donor-CU modifies resources serving the service in the topology of the second donor-CU.
  • the receiving unit 1901 receives the information sent by the second donor-CU for modifying the routing ID (routing ID) and/or BH RLC channel of the service in the topology of the second donor-CU.
  • the second transmits a migration modification request.
  • the second transport migration modification request is received through a second transport migration management request (TRANSPORT MIGRATION MANAGEMENT REQUEST) message.
  • TRANSPORT MIGRATION MANAGEMENT REQUEST a second transport migration management request
  • the second transmission migration modification request includes the following information:
  • the BH information in the topology of the second donor-CU includes at least one of the following:
  • Egress routing ID (routing ID) of uplink service
  • the BH information in the topology of the second donor-CU includes at least one of the following:
  • the ingress routing ID (routing ID) of the downlink service is the ingress routing ID (routing ID) of the downlink service
  • the last hop BAP address of the downlink service is the last hop BAP address of the downlink service.
  • the IAB host device 1900 further includes:
  • the processing unit 1902 configures and updates the uplink BH information of the service to the IAB node.
  • the processing unit 1902 configures and updates at least one of the following items to the IAB node: BAP header rewriting information between topologies in the uplink direction, routing information in the topology of the second donor-CU, and uplink BH RLC channel mapping information between topologies.
  • the processing unit 1902 configures and updates at least one of the following items to the IAB node: BAP header rewriting information between topologies in the downlink direction, BH RLC channel mapping information between topologies in the downlink direction.
  • the receiving unit 1901 further receives a second transmission migration modification request sent by the second donor-CU for modifying the IP address of the IAB node.
  • the receiving unit 1901 when the routing ID (routing ID) and/or donor distribution unit (donor-DU) in the topology of the second donor-CU of the service is changed, the receiving unit 1901 also receives the second The second transmission migration modification request sent by the donor-CU for modifying the IP address of the IAB node.
  • the second transport migration modification request is included in a second transport migration management request message.
  • the second transmission migration modification request includes the following information: IAB node identifier or IP address request index, the BAP address of the donor-DU in the topology of the first donor-CU or the first donor-CU The BAP address of the donor-DU in the topology of the first donor-CU, and the IP address of the donor-DU anchored to the second donor-CU topology.
  • the processing unit 1902 further configures the IP address of the donor-DU anchored in the second donor-CU topology to the IAB node.
  • the IAB host device 1900 in the embodiment of the present application may also include other components or modules, and for specific content of these components or modules, reference may be made to related technologies.
  • FIG. 19 only exemplarily shows the connection relationship or signal direction between various components or modules, but it should be clear to those skilled in the art that various related technologies such as bus connection can be used.
  • the above-mentioned components or modules may be implemented by hardware facilities such as processors, memories, transmitters, receivers, etc.; the implementation of the present application is not limited thereto.
  • the second donor-CU sends a second transmission migration modification request for the service to the first donor-CU; resource. Therefore, when the second donor-CU modifies the resources used to serve the service or modifies the IP address of the IAB node, the first donor-CU can modify the L2 related information or IP address of the service to ensure that the migrated service is Normal transfer in the second donor-CU topology.
  • An embodiment of the present application provides a communication system, including a donor device and an IAB node (IAB-node); for the network architecture of the donor device and the IAB node, reference may also be made to related technologies, and descriptions are omitted here.
  • IAB-node IAB node
  • the IAB system includes:
  • a first donor centralized unit (first donor-CU), which sends a first transmission migration modification request for a service, and receives a transmission migration modification response for the business;
  • a second donor central unit (second donor-CU), which receives the first transmission migration modification request, and sends the transmission migration modification response.
  • the IAB system includes:
  • second donor-CU which sends a second transmission migration modification request for the service, and modifies resources serving the service in the topology of the second donor central unit
  • the first donor central unit (first donor-CU), which receives the second transmission migration modification request.
  • the embodiment of the present application also provides an IAB device, and the IAB device may be an IAB host device or an IAB node device (a migration node or a child node).
  • FIG. 20 is a schematic diagram of an IAB device according to an embodiment of the present application.
  • an IAB device 2000 may include: a processor (such as a central processing unit CPU) 2001 and a memory 2002 ; the memory 2002 is coupled to the processor 2001 .
  • the memory 2002 can store various data; in addition, it also stores a program 2005 for information processing, and executes the program 2005 under the control of the central processing unit 2001 .
  • the processor 2001 may be configured to execute a program to implement the transmission migration management method in the embodiment of the first aspect.
  • the processor 2001 may be configured to perform the following control: send a first transmission migration modification request for the service to the second donor-CU; and receive a transmission for the service sent by the second donor-CU Migration modifies the response.
  • the processor 2001 may be configured to execute a program to implement the transmission migration management method in the embodiment of the second aspect.
  • the processor 2001 may be configured to perform the following control: receive a first transmission migration modification request for the service sent by the first donor-CU; and send a transmission for the service to the first donor-CU Migration modifies the response.
  • the processor 2001 may be configured to execute a program to implement the transmission migration management method in the embodiment of the third aspect.
  • the processor 2001 may be configured to perform the following control: send a second transmission migration modification request for the service to the first donor-CU; and modify the service in the topology of the second donor-CU resource.
  • the processor 2001 may be configured to execute a program to implement the transmission migration management method in the embodiment of the fourth aspect.
  • the processor 2001 may be configured to perform the following control: receive a second transmission migration modification request for services sent by the second donor-CU; The resources in the topology that serve the business.
  • the IAB device 2000 may further include: a transceiver 2003 and an antenna 2004 ; wherein, the functions of the above components are similar to those of the prior art, and will not be repeated here. It should be noted that the IAB device 2000 does not necessarily include all components shown in FIG. 20 ; in addition, the IAB device 2000 may also include components not shown in FIG. 20 , and reference may be made to the prior art.
  • the embodiment of the present application also provides a computer-readable program, wherein when the program is executed in the IAB device, the program causes the computer to perform the transmission migration in the embodiments of the first to fourth aspects in the IAB device Management method.
  • the embodiment of the present application also provides a storage medium storing a computer-readable program, wherein the computer-readable program enables the computer to execute the transmission migration management methods in the embodiments of the first to fourth aspects in the IAB device.
  • the above devices and methods in this application can be implemented by hardware, or by combining hardware and software.
  • the present application relates to a computer-readable program that, when executed by a logic component, enables the logic component to realize the above-mentioned device or constituent component, or enables the logic component to realize the above-mentioned various methods or steps.
  • Logic components such as field programmable logic components, microprocessors, processors used in computers, and the like.
  • the present application also relates to storage media for storing the above programs, such as hard disks, magnetic disks, optical disks, DVDs, flash memories, and the like.
  • the method/device described in conjunction with the embodiments of the present application may be directly embodied as hardware, a software module executed by a processor, or a combination of both.
  • one or more of the functional block diagrams shown in the figure and/or one or more combinations of the functional block diagrams may correspond to each software module or each hardware module of the computer program flow.
  • These software modules may respectively correspond to the steps shown in the figure.
  • These hardware modules for example, can be realized by solidifying these software modules by using a Field Programmable Gate Array (FPGA).
  • FPGA Field Programmable Gate Array
  • a software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM or any other form of storage medium known in the art.
  • a storage medium can be coupled to the processor such that the processor can read information from, and write information to, the storage medium, or it can be an integral part of the processor.
  • the processor and storage medium can be located in the ASIC.
  • the software module can be stored in the memory of the mobile terminal, or can be stored in a memory card that can be inserted into the mobile terminal.
  • the software module can be stored in the MEGA-SIM card or large-capacity flash memory device.
  • One or more of the functional blocks described in the accompanying drawings and/or one or more combinations of the functional blocks can be implemented as a general-purpose processor, a digital signal processor (DSP) for performing the functions described in this application ), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or any suitable combination thereof.
  • DSP digital signal processor
  • ASICs application specific integrated circuits
  • FPGAs field programmable gate arrays
  • One or more of the functional blocks described in the drawings and/or one or more combinations of the functional blocks can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors processor, one or more microprocessors in communication with a DSP, or any other such configuration.
  • a transmission migration management method wherein the IAB-DU of the IAB node maintains an F1 connection with the first donor-CU, and has been established in the topology of the second donor-CU to serve the IAB node resources of the business, the method includes:
  • the first donor-CU sends a first transmission migration modification request for the service to the second donor-CU;
  • the first donor-CU receives a transmission migration modification response for the service sent by the second donor-CU.
  • the first transmission migration modification request includes the following information: a service identifier of the service, a quality of service (QoS) and/or a service type of the service.
  • QoS quality of service
  • the transmission migration modification response includes the following information: a service identifier of the service, and BH information of the service in the topology of the second donor-CU.
  • BH information in the topology of the second donor-CU includes at least one of the following:
  • the ingress routing ID (routing ID) of the downlink service is the ingress routing ID (routing ID) of the downlink service
  • BH information in the topology of the second donor-CU includes at least one of the following:
  • Egress routing ID (routing ID) of uplink service
  • the first donor-CU updates the QoS mapping information of the service.
  • the first donor-CU configures and updates the uplink BH information of the service to the IAB node.
  • the first donor-CU configures and updates at least one of the following items to the IAB node: BAP header rewriting information between topologies in the uplink direction, routing information in the topology of the second donor-CU, and topology in the uplink direction BH RLC channel mapping information among them.
  • the first donor-CU configures and updates at least one of the following items to the IAB node: BAP header rewriting information between topologies in the downlink direction, and BH RLC channel mapping information between topologies in the downlink direction.
  • the first transmission migration modification request includes the following information: IAB node identifier or IP address request index, BAP of the donor-DU in the topology of the first donor-CU address.
  • the first transmission migration modification request further includes: an IP address anchored to the donor-DU.
  • the transmission migration modification response includes the following information: IAB node identifier or IP address request index, the BAP address of the donor-DU in the topology of the first donor-CU, and The IP address of the donor-DU anchored in the second donor-CU topology.
  • the first donor-CU configures the IP address of the donor-DU anchored in the second donor-CU topology to the IAB node.
  • a transmission migration management method wherein the IAB-DU of the IAB node maintains an F1 connection with the first donor-CU, and has been established in the topology of the second donor-CU to serve the IAB node resources of the business, the method includes:
  • the second donor-CU receives the first transmission migration modification request for the service sent by the first donor-CU;
  • the second donor-CU sends a transmission migration modification response for the service to the first donor-CU.
  • the first transmission migration modification request includes the following information: a service identifier of the service, a quality of service (QoS) and/or a service type of the service.
  • QoS quality of service
  • the second donor-CU updates the service in the second donor-CU
  • BH backhaul
  • RLC radio link control
  • the second donor-CU updates the uplink BH information of the service after receiving the first transmission migration modification request; wherein, the The uplink BH information includes a routing identifier, an uplink BH RLC channel and/or a BAP address of a next-hop node.
  • the transmission migration modification response includes the following information: the service identifier of the service, and the BH information of the service in the topology of the second donor-CU.
  • BH information in the topology of the second donor-CU includes at least one of the following:
  • the ingress routing ID (routing ID) of the downlink service is the ingress routing ID (routing ID) of the downlink service
  • BH information in the topology of the second donor-CU includes at least one of the following:
  • Egress routing ID (routing ID) of uplink service
  • the first transmission migration modification request includes the following information: IAB node identifier or IP address request index, BAP of the donor-DU in the topology of the first donor-CU address.
  • the first transmission migration modification request further includes: an IP address anchored to the donor-DU.
  • the transmission migration modification response includes the following information: IAB node identifier or IP address request index, the BAP address of the donor-DU in the topology of the first donor-CU, and The IP address of the donor-DU anchored in the second donor-CU topology.
  • a transmission migration management method wherein the IAB-DU of the IAB node maintains an F1 connection with the first donor-CU, and resources for serving the business of the IAB node have been established in the topology of the second donor-CU,
  • the methods include:
  • the second donor-CU sends a second transmission migration modification request for services to the first donor-CU;
  • the second donor-CU modifies resources serving the service in the topology of the second donor-CU.
  • the second donor-CU sends to the first donor-CU a routing identifier for modifying the service in the topology of the second donor-CU ( routing ID) and/or the second transmission relocation modification request of the BH RLC channel.
  • BH information in the topology of the second donor-CU includes at least one of the following:
  • Egress routing ID (routing ID) of uplink service
  • BH information in the topology of the second donor-CU includes at least one of the following:
  • the ingress routing ID (routing ID) of the downlink service is the ingress routing ID (routing ID) of the downlink service
  • the last hop BAP address of the downlink service is the last hop BAP address of the downlink service.
  • the second donor-CU updates the BH RLC channel and/or BAP sublayer route used by the service on the path in the topology of the second donor-CU.
  • the second donor-CU updates the uplink BH information of the service; wherein the uplink BH information includes a routing identifier, an uplink BH RLC channel and/or a BAP address of a next-hop node.
  • the second donor-CU updates the uplink egress routing identifier of the service, the egress BH RLC channel and/or the BAP address of the next hop node;
  • the second transmission migration modification request includes the following information: IAB node identifier or IP address request index, BAP of the donor-DU in the topology of the first donor-CU address or the BAP address of the donor-DU in the topology of the second donor-CU, and the IP address of the donor-DU anchored in the topology of the second donor-CU.
  • a transmission migration management method wherein the IAB-DU of the IAB node maintains an F1 connection with the first donor-CU, and resources for serving the business of the IAB node have been established in the topology of the second donor-CU,
  • the methods include:
  • the first donor-CU receives the second transmission migration modification request for the service sent by the second donor-CU; wherein, the second donor-CU modifies the service in the topology of the second donor-CU resources of the business.
  • BH information in the topology of the second donor-CU includes at least one of the following:
  • Egress routing ID (routing ID) of uplink service
  • BH information in the topology of the second donor-CU includes at least one of the following:
  • the ingress routing ID (routing ID) of the downlink service is the ingress routing ID (routing ID) of the downlink service
  • the last hop BAP address of the downlink service is the last hop BAP address of the downlink service.
  • the first donor-CU configures and updates the uplink BH information of the service to the IAB node.
  • the first donor-CU configures and updates at least one of the following items to the IAB node: BAP header rewriting information between topologies in the uplink direction, routing information in the topology of the second donor-CU, and topology in the uplink direction BH RLC channel mapping information among them.
  • the first donor-CU configures and updates at least one of the following items to the IAB node: BAP header rewriting information between topologies in the downlink direction, and BH RLC channel mapping information between topologies in the downlink direction.
  • the second transmission migration modification request includes the following information: IAB node identifier or IP address request index, BAP of the donor-DU in the topology of the first donor-CU The address or the BAP address of the donor-DU in the topology of the second donor-CU, and the IP address of the donor-DU anchored in the topology of the second donor-CU.
  • the first donor-CU configures the IP address of the donor-DU anchored in the second donor-CU topology to the IAB node.
  • An IAB donor device comprising a memory and a processor, the memory stores a computer program, wherein the processor is configured to execute the computer program to achieve any one of Supplements 1 to 82 The transmission migration management method described above.

Abstract

本申请实施例提供了一种IAB宿主设备以及传输迁移管理方法。IAB节点的IAB-DU与第一donor-CU保持F1连接，在第二donor-CU的拓扑中已建立用于服务所述IAB节点的业务的资源，所述方法包括：第一donor-CU向第二donor-CU发送针对所述业务的第一传输迁移修改请求；以及接收所述第二donor-CU发送的针对所述业务的传输迁移修改响应。

Description

IAB宿主设备以及传输迁移管理方法 技术领域
本申请实施例涉及通信领域。
背景技术
未来无缝的蜂窝网络部署需要非常灵活和超密集的新无线(NR，new radio)小区部署，超密集网络是5G的目标之一，部署一个无需有线回传的NR网络对于实现5G的超密集网络非常重要。由于5G毫米波使小区覆盖范围缩小，无线自回传系统需要多跳才能满足部署需求。5G的高带宽、大规模多输入多输出(MIMO)和波束系统使5G比LTE更容易开发超密集NR小区的无线自回传系统，为了开发这种带有无线自回传的多跳系统，3GPP在Rel-16开始了集成的接入和回传(IAB，Integrated access and backhaul)项目的研究和标准化。
图1是IAB系统的一示意图，如图1所示，在IAB系统中，接入和回传采用NR的Uu空口无线传输，中继节点同时支持接入(access)和回传(backhaul)功能，中继节点在时域、频域或空域上复用接入链路(access link)和回传链路(backhaul link)，接入链路和回传链路可以使用相同或不同的频段。
在IAB网络架构如下，中继节点指的是IAB-node(IAB节点)，其同时支持接入和回传功能。网络侧最后一跳接入节点称为IAB-donnor(IAB宿主)，其支持gNB功能并支持IAB-node接入。所有的UE数据可以通过一跳或多跳经由IAB-node回传到IAB-donor。
IAB-node的功能分为两部分，一部分是gNB-DU功能，称作IAB-DU(分布单元)，另一部分是UE功能，称作IAB-MT(移动终端)。IAB-DU实现网络侧设备功能，连接到下游的child IAB-node(子IAB节点或简称为子节点)，对UE以及下游child IAB-node提供NR空口接入并与IAB donor-CU(宿主集中单元)之间建立有F1连接。IAB-MT实现部分终端设备功能，连接到上游的parent IAB-node(父IAB节点或简称为父节点)或IAB donor-DU，IAB-MT包括物理层、层二、RRC(Radio Resource Control，无线资源控制)和NAS(Non-Access Stratum，非接入层)层功能，还间接地连接到IAB Donor-CU以及核心网(Core Network，CN)。
在IAB系统中，IAB-node可以通过独立组网(SA，Standalone)模式或非独立 组网(EN-DC，E-UTRA-NRDualConnectivity)模式接入网络。图2是SA模式的IAB架构的示意图。图3是EN-DC模式的IAB架构的示意图。
图4是一个IAB节点(IAB-node)与父节点(parent IAB-node)和子节点(child IAB-node)的示意图。如图4所示，IAB节点的IAB-DU作为网络侧与子节点的IAB-MT连接，IAB节点的IAB-MT作为终端侧与父节点的IAB-DU连接。
图5是IAB-DU和IAB donor-CU之间的F1用户面(F1-U)协议栈的示意图。图6是IAB-DU和IAB donor-CU之间的F1控制面(F1-C)协议栈的示意图。如图5和图6所示，F1-U和F1-C是建立在IAB-DU和IAB donor-CU之间的传输(IP)层之上，图5和图6中经过两跳无线回传和一跳有线回传。
在回传链路上，传输(IP)层承载在回传自适应协议(BAP)子层上，IAB-node中的BAP实体实现IAB系统的路由功能，由IAB donor-CU提供路由表。BAP PDU(协议数据单元)在回传链路的RLC(无线链路控制)信道中传输，回传链路的多个RLC信道可以被IAB-donor配置为承载不同的优先级和QoS(服务质量)的业务，由BAP实体将BAP PDU映射到不同的回传RLC信道上。
应该注意，上面对技术背景的介绍只是为了方便对本申请的技术方案进行清楚、完整的说明，并方便本领域技术人员的理解而阐述的，不能仅仅因为这些方案在本申请的背景技术部分进行了阐述而认为上述技术方案为本领域技术人员所公知。
发明内容
发明人发现，如果业务的特征(或服务参数)发生变化，可能需要对已迁移的业务的传输迁移配置进行修改。例如，当业务的服务质量(QoS)发生变化，第一donor-CU需要更新迁移业务的QoS信息，使得第二donor-CU确定是否满足业务新的QoS要求以及修改在第二donor-CU拓扑中的服务该业务的资源。但是，如何对业务的传输迁移配置进行修改，目前并没有相应的方案。
为了解决上述问题的至少之一，本申请实施例提供一种IAB宿主设备以及传输迁移管理方法。
根据本申请实施例的一方面，提供一种传输迁移管理方法，其中，IAB节点的IAB-DU与第一宿主集中单元(donor-CU)保持F1连接，在第二donor-CU的拓扑中已建立用于服务所述IAB节点的业务的资源，所述方法包括：
所述第一donor-CU向所述第二donor-CU发送针对所述业务的第一传输迁移修改 请求；以及
所述第一donor-CU接收所述第二donor-CU发送的针对所述业务的传输迁移修改响应。
根据本申请实施例的另一方面，提供一种传输迁移管理方法，其中，IAB节点的IAB-DU与第一宿主集中单元(donor-CU)保持F1连接，在第二donor-CU的拓扑中已建立用于服务所述IAB节点的业务的资源，所述方法包括：
所述第二donor-CU接收所述第一donor-CU发送的针对所述业务的第一传输迁移修改请求；以及
所述第二donor-CU向所述第一donor-CU发送针对所述业务的传输迁移修改响应。
根据本申请实施例的另一方面，提供一种传输迁移管理方法，其中，IAB节点的IAB-DU与第一donor-CU保持F1连接，在第二donor-CU的拓扑中已建立用于服务所述IAB节点的业务的资源，所述方法包括：
所述第二donor-CU向所述第一donor-CU发送针对业务的第二传输迁移修改请求；以及
所述第二donor-CU修改在所述第二donor-CU的拓扑中的服务所述业务的资源。
根据本申请实施例的另一方面，提供一种传输迁移管理方法，其中，IAB节点的IAB-DU与第一donor-CU保持F1连接，在第二donor-CU的拓扑中已建立用于服务所述IAB节点的业务的资源，所述方法包括：
所述第一donor-CU接收所述第二donor-CU发送的针对业务的第二传输迁移修改请求；其中，所述第二donor-CU修改在所述第二donor-CU的拓扑中的服务所述业务的资源。
根据本申请实施例的另一方面，提供一种IAB宿主设备，其中，IAB节点的IAB-DU与第一宿主集中单元(donor-CU)保持F1连接，在第二donor-CU的拓扑中已建立用于服务所述IAB节点的业务的资源，所述设备包括：
发送部，其向所述第二donor-CU发送针对所述业务的第一传输迁移修改请求；以及
接收部，其接收所述第二donor-CU发送的针对所述业务的传输迁移修改响应。
根据本申请实施例的另一方面，提供一种IAB宿主设备，其中，IAB节点的IAB-DU与第一宿主集中单元(donor-CU)保持F1连接，在第二donor-CU的拓扑中已建立用于服务所述IAB节点的业务的资源，所述设备包括：
接收部，其接收所述第一donor-CU发送的针对所述业务的第一传输迁移修改请求；以及
发送部，其向所述第一donor-CU发送针对所述业务的传输迁移修改响应。
根据本申请实施例的另一方面，提供一种IAB宿主设备，其中，IAB节点的IAB-DU与第一donor-CU保持F1连接，在第二donor-CU的拓扑中已建立用于服务所述IAB节点的业务的资源，所述设备包括：
发送部，其向所述第一donor-CU发送针对业务的第二传输迁移修改请求；以及
处理部，其修改在所述第二donor-CU的拓扑中的服务所述业务的资源。
根据本申请实施例的另一方面，提供一种IAB宿主设备，其中，IAB节点的IAB-DU与第一donor-CU保持F1连接，在第二donor-CU的拓扑中已建立用于服务所述IAB节点的业务的资源，所述设备包括：
接收部，其接收所述第二donor-CU发送的针对业务的第二传输迁移修改请求；其中，所述第二donor-CU修改在所述第二donor-CU的拓扑中的服务所述业务的资源。
根据本申请实施例的另一方面，提供一种IAB系统，包括第一宿主集中单元和第二宿主集中单元；
所述第一宿主集中单元发送针对业务的第一传输迁移修改请求，以及接收针对所述业务的传输迁移修改响应；所述第二宿主集中单元接收所述第一传输迁移修改请求，以及发送所述传输迁移修改响应；
或者，
所述第二宿主集中单元发送针对业务的第二传输迁移修改请求，以及修改在所述第二宿主集中单元的拓扑中的服务所述业务的资源；所述第一宿主集中单元接收所述第二传输迁移修改请求。
本申请实施例的有益效果之一在于：第一donor-CU向第二donor-CU发送针对业务的第一传输迁移修改请求；以及第一donor-CU接收第二donor-CU发送的针对所述业务的传输迁移修改响应。由此，第二donor-CU能够根据业务的服务参数的改变对服务迁移业务的传输资源进行修改，使得当业务的服务参数变化后依然能满足业务的服务要求。
参照后文的说明和附图，详细公开了本申请的特定实施方式，指明了本申请的原理可以被采用的方式。应该理解，本申请的实施方式在范围上并不因而受到限制。在所附附记的精神和条款的范围内，本申请的实施方式包括许多改变、修改和等同。
针对一种实施方式描述和/或示出的特征可以以相同或类似的方式在一个或更多个其它实施方式中使用，与其它实施方式中的特征相组合，或替代其它实施方式中的特征。
应该强调，术语“包括/包含”在本文使用时指特征、整件、步骤或组件的存在，但并不排除一个或更多个其它特征、整件、步骤或组件的存在或附加。
附图说明
在本申请实施例的一个附图或一种实施方式中描述的元素和特征可以与一个或更多个其它附图或实施方式中示出的元素和特征相结合。此外，在附图中，类似的标号表示几个附图中对应的部件，并可用于指示多于一种实施方式中使用的对应部件。
所包括的附图用来提供对本申请实施例的进一步的理解，其构成了说明书的一部分，用于例示本申请的实施方式，并与文字描述一起来阐释本申请的原理。显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其它的附图。在附图中：
图1是IAB系统的一示意图；
图2是SA模式的IAB架构的一示意图；
图3是EN-DC模式的IAB架构的一示意图；
图4是父节点(parent IAB-node)和子节点(child IAB-node)的一示意图；
图5是IAB系统的F1-U协议栈的一示意图；
图6是IAB系统的F1-C协议栈的一示意图；
图7是IAB系统路由的一示意图；
图8是网络拓扑自适应的一示意图；
图9是本申请实施例的传输迁移的一示例图；
图10是本申请实施例的传输迁移管理方法的一示意图；
图11是本申请实施例的传输迁移修改的一信令流程图；
图12是本申请实施例的传输迁移管理方法的另一示意图；
图13是本申请实施例的传输迁移管理方法的另一示意图；
图14是本申请实施例的传输迁移修改的另一信令流程图；
图15是本申请实施例的传输迁移管理方法的另一示意图；
图16是本申请实施例的IAB宿主设备的一示意图；
图17是本申请实施例的IAB宿主设备的另一示意图；
图18是本申请实施例的IAB宿主设备的另一示意图；
图19是本申请实施例的IAB宿主设备的另一示意图；
图20是本申请实施例的IAB设备的一示意图。
具体实施方式
参照附图，通过下面的说明书，本申请的前述以及其它特征将变得明显。在说明书和附图中，具体公开了本申请的特定实施方式，其表明了其中可以采用本申请的原则的部分实施方式，应了解的是，本申请不限于所描述的实施方式，相反，本申请包括落入所附附记的范围内的全部修改、变型以及等同物。
在本申请实施例中，术语“第一”、“第二”等用于对不同元素从称谓上进行区分，但并不表示这些元素的空间排列或时间顺序等，这些元素不应被这些术语所限制。术语“和/或”包括相关联列出的术语的一种或多个中的任何一个和所有组合。术语“包含”、“包括”、“具有”等是指所陈述的特征、元素、元件或组件的存在，但并不排除存在或添加一个或多个其他特征、元素、元件或组件。
在本申请实施例中，单数形式“一”、“该”等包括复数形式，应广义地理解为“一种”或“一类”而并不是限定为“一个”的含义；此外术语“所述”应理解为既包括单数形式也包括复数形式，除非上下文另外明确指出。此外术语“根据”应理解为“至少部分根据……”，术语“基于”应理解为“至少部分基于……”，除非上下文另外明确指出。
在本申请实施例中，术语“通信网络”或“无线通信网络”可以指符合如下任意通信标准的网络，例如新无线(NR，New Radio)、长期演进(LTE，Long Term Evolution)、增强的长期演进(LTE-A，LTE-Advanced)、宽带码分多址接入(WCDMA，Wideband Code Division Multiple Access)、高速报文接入(HSPA，High-Speed Packet Access)等等。
并且，通信系统中设备之间的通信可以根据任意阶段的通信协议进行，例如可以包括但不限于如下通信协议：1G(generation)、2G、2.5G、2.75G、3G、4G、4.5G以及未来的5G、6G等等，和/或其他目前已知或未来将被开发的通信协议。
在本申请实施例中，术语“网络设备”例如是指通信系统中将终端设备接入通信网络并为该终端设备提供服务的设备。网络设备可以包括但不限于如下设备：基站 (BS，Base Station)、接入点(AP、Access Point)、发送接收点(TRP，Transmission Reception Point)、广播发射机、移动管理实体(MME、Mobile Management Entity)、网关、服务器、无线网络控制器(RNC，Radio Network Controller)、基站控制器(BSC，Base Station Controller)等等。
其中，基站可以包括但不限于：节点B(NodeB或NB)、演进节点B(eNodeB或eNB)以及5G基站(gNB)，等等，此外还可包括远端无线头(RRH，Remote Radio Head)、远端无线单元(RRU，Remote Radio Unit)、中继(relay)或者低功率节点(例如femto、pico等等)。并且术语“基站”可以包括它们的一些或所有功能，每个基站可以对特定的地理区域提供通信覆盖。术语“小区”可以指的是基站和/或其覆盖区域，这取决于使用该术语的上下文。
在本申请实施例中，术语“用户设备”(UE，User Equipment)例如是指通过网络设备接入通信网络并接收网络服务的设备，也可以称为“终端设备”(TE，Terminal Equipment)。终端设备可以是固定的或移动的，并且也可以称为移动台(MS，Mobile Station)、终端、用户、用户台(SS，Subscriber Station)、接入终端(AT，Access Terminal)、站，等等。
其中，终端设备可以包括但不限于如下设备：蜂窝电话(Cellular Phone)、个人数字助理(PDA，Personal Digital Assistant)、无线调制解调器、无线通信设备、手持设备、机器型通信设备、膝上型计算机、无绳电话、智能手机、智能手表、数字相机，等等。
再例如，在物联网(IoT，Internet of Things)等场景下，终端设备还可以是进行监控或测量的机器或装置，例如可以包括但不限于：机器类通信(MTC，Machine Type Communication)终端、车载通信终端、设备到设备(D2D，Device to Device)终端、机器到机器(M2M，Machine to Machine)终端，等等。
IAB系统的路由功能由BAP层实现，每个IAB-node节点保存有路由配置(BH routing configuration)和RLC信道映射配置(BH RLC Channel Mapping Configuration)。BAP实体根据路由配置、RLC信道映射配置和BAP层数据包头中的路由标识(Routing ID)进行路由。Routing ID包含目的BAP地址和路径标识。
路由配置包含Routing ID与下一跳(next-hop)节点BAP地址的映射关系。RLC信道映射配置包含上一跳(prior-hop)节点BAP地址、入口链路RLC信道ID和下一跳节点BAP地址与出口链路RLC信道ID的映射关系。
图7是IAB系统路由的一示意图。如图7所示，对于每个数据包，可以通过数据包头的routing ID从路由配置查找到下一跳节点BAP地址。上一跳节点BAP地址、入口链路RLC信道ID都是已知的。这样，下一跳节点BAP地址确定之后，就可以通过RLC信道映射配置，根据上一跳节点BAP地址+入口链路RLC信道ID+下一跳节点BAP地址查到出口链路RLC信道ID。
IAB-donor DU保存有路由配置(BH routing configuration)和下行RLC信道映射配置(Downlink Traffic to BH RLC Channel Mapping Configuration)。IAB-donor DU根据路由配置、RLC信道映射配置和BAP层数据包头中的Routing ID进行路由。路由配置包含Routing ID与下一跳节点地址的映射关系。下行RLC信道映射配置包含目标IP地址、DSCP(Differentiated Services Code Point，差分服务代码点)和下一跳节点地址与出口链路RLC信道ID的映射关系。
对于每个到达IAB-donor DU的下行数据包，IAB-donor DU可根据数据包头中的Routing ID从路由配置查到下一跳节点地址。这样，下一跳节点地址确定之后，再根据数据包的IP地址和DSCP，从下行RLC信道映射配置查到出口链路RLC信道ID。
接入IAB节点保存有上行回传信息(BH information)，包括业务使用的路由标识(routing ID)、上行回传RLC信道ID和下一跳节点地址。接入IAB节点根据上行BH information配置上行业务的BAP层数据包头中的routing ID并选择上行业务传输的BH RLC信道和下一跳节点。
以上示意性说明了IAB系统的路由和BH RLC信道映射，以下再说明IAB系统的网络拓扑的更新。Rel-16NR已经对IAB-node在同一个donor-CU下移动时拓扑自适应(topology adaptation)过程进行了标准化。
图8是CU内(intra-CU)拓扑自适应的一示意图。IAB-node改变父节点(从IAB-node 1改变为IAB-node 2)时，donor-CU通过RRC重配置消息为IAB-node配置路径迁移相关的配置，使IAB-node进行F1传输路径的迁移。
路径迁移相关的配置包括对上行F1-C、F1-U和非F1数据的默认回传RLC信道(default BH RLC channel)的更新，对默认BAP路由标识(default BAP routing ID)的更新，以及对路由至Donor-DU的IP地址的更新。IAB-node接入到新的父节点时开始应用上述路径迁移相关的配置，对于IAB-node的子节点，也通过相同的方法进行路径迁移相关的配置。
3GPP Rel-17支持IAB-node在不同donor-CU下移动时的网络拓扑更新和回传 (BH)无线链路失败(RLF，Radio Link Failure)的恢复过程，IAB-node可以从源donor-CU(也可称为F1-terminating CU或第一donor-CU)服务的父节点切换或重建立到目标donor-CU(也可称为non-F1-terminating CU或第二donor-CU)服务的父节点，需要将IAB-node的全部业务(以及其子节点的业务)迁移至non-F1-terminating CU的拓扑。Rel-17也支持IAB-node与non-F1-terminating CU建立双连接时的拓扑冗余(topology redundancy)过程，IAB-node的部分业务的传输路径可迁移至non-F1-terminating CU拓扑。
IAB-node从donor-CU 1(F1-terminating CU)切换/RLF恢复到donor-CU 2(non-F1-terminating CU)后，或增加与donor-CU 2的RRC连接后，只是IAB-MT的RRC连接到donor-CU 2，F1接口仍然终止于donor-CU 1，此时IAB-node也可称为boundary node。而其服务的子节点和UE的RRC连接仍属于donor-CU 1，子节点的F1接口也终止于donor-CU 1，因此boundary node的子节点仍然属于donor-CU 1的拓扑。
为了让子节点的上行业务在donor-CU 2的拓扑中传输，boundary node需要将上行业务的属于donor-CU 1的拓扑的routing ID(目的地址为donor-CU 1的donor-DU BAP地址)替换成属于donor-CU 2的拓扑的routing ID(目的地址为donor-CU 2的donor-DU BAP地址)。为了让子节点的下行业务在donor-CU 2的拓扑中传输，boundary node将下行业务的属于donor-CU 2的拓扑的routing ID(目的地址为donor-CU 2的donor-DU BAP地址)替换成属于donor-CU 1的拓扑的routing ID(目的地址为donor-CU1的donor-DU BAP地址)。而boundary node自身的上行业务需要更新为属于donor-CU 2的拓扑的routing ID。
图9是本申请实施例的传输迁移的一示意图。如图9所示，IAB节点3的IAB-MT从donor-CU 1迁移到donor-CU 2。若子节点的业务迁移至donor-CU 2的拓扑，网络设备会将拓扑间的routing ID映射关系(例如BAP Header Rewriting information)配置给boundary node。
boundary node转发上行数据至donor-CU2拓扑中的父节点时，将属于donor-CU 1的routing ID替换成属于donor-CU 2的routing ID后，需要根据替换后的routing ID进行路由选择和BH RLC信道选择，因此网络设备会给boundary node配置属于donor-CU 2的拓扑的路由表(切换前boundary node中只配置有donor-CU 1拓扑的路由表)以及从donor-CU 1拓扑至donor-CU 2拓扑的BH RLC信道映射表。
同理，转发下行数据时，需要根据替换后的routing ID进行路由和BH RLC信道选择，因此网络设备会给boundary node配置从donor-CU 2拓扑至donor-CU 1拓扑的下行BH RLC信道映射表。
若boundary node的业务迁移至donor-CU 2拓扑，网络设备需要将属于donor-CU 2拓扑的上行回传信息配置给boundary node，包括路由标识(routing ID)、上行回传RLC信道ID和下一跳节点地址。
若将部分或全部业务的传输迁移至donor-CU 2的拓扑，在donor-CU 2的拓扑中需要建立用于服务该业务的资源，例如，为业务配置在donor-CU 1的拓扑中的路径上使用的回传BH RLC信道和/或BAP子层路由。
为了给boundary node配置属于donor-CU 2拓扑的路由表和两个donor-CU拓扑之间的BH RLC信道映射表，以及在donor-CU 2的拓扑中建立服务迁移业务的资源，donor-CU 1向donor-CU 2发送传输迁移建立请求。
donor-CU 1向donor-CU 2发送针对每个请求迁移的业务流的以下信息以及IP地址请求(包括donor-CU 1拓扑中的donor-DU BAP地址以及锚定于该donor-DU的IP地址)：
-业务标识；
-业务的服务质量(QoS)信息或业务类型；
-针对子节点的业务流还需要发送donor-CU 1拓扑中的routing ID和BH RLC信道(包括下行业务的出口routing ID和出口BH RLC信道、上行业务的入口routing ID和入口BH RLC信道)。
donor-CU 2向donor-CU 1发送如下(针对每个业务流)信息以及IP地址响应(包括donor-CU 1拓扑中的donor-DU BAP地址以及锚定于donor-CU 2的donor-DU的IP地址)：
-业务标识；
-业务在donor-CU 2拓扑中的routing ID和BH RLC信道(包括下行业务的入口routing ID和入口BH RLC信道，或者，上行业务的出口routing ID和出口BH RLC信道)；
-下行业务在donor-CU 2拓扑中的上一跳BAP地址；
-上行业务在donor-CU 2拓扑中的下一跳BAP地址；
-下行业务使用的QoS映射信息(如DSCP或IPv6的流标识flow label)。
在本申请实施例中，在没有特别说明的情况下，IAB节点设备包括迁移节点或其子节点。此外，“donor-CU的拓扑中已建立用于服务IAB节点的业务的资源”也可称为“IAB节点的业务迁移到donor-CU的拓扑中”等，本申请不限于这些表述。以下对本申请实施例进行进一步说明。
第一方面的实施例
本申请实施例提供一种传输迁移管理方法，从第一宿主集中单元(donor-CU)进行说明。其中，IAB节点的IAB-DU与第一宿主集中单元(donor-CU)保持F1连接，第二donor-CU的拓扑中已建立用于服务所述IAB节点的业务的资源。
图10是本申请实施例的传输迁移管理方法的一示意图。如图10所示，该方法包括：
1001，第一donor-CU向第二donor-CU发送针对业务的第一传输迁移修改请求；以及
1002，第一donor-CU接收第二donor-CU发送的针对业务的传输迁移修改响应。
值得注意的是，以上附图10仅对本申请实施例进行了示意性说明，但本申请不限于此。例如可以适当地调整各个操作之间的执行顺序，此外还可以增加其他的一些操作或者减少其中的某些操作。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图10的记载。
在一些实施例中，IAB节点的IAB-MT与第二donor-CU保持RRC连接；例如迁移节点的IAB-MT与第二donor-CU保持RRC连接。或者，IAB节点的IAB-MT与第一donor-CU保持RRC连接；例如迁移节点的子节点与第一donor-CU保持RRC连接。
在一些实施例中，所述业务包括如下至少之一或组合：F1控制面(F1-C)业务、F1用户面(F1-U)业务、非F1业务；本申请实施例不限于此。
在一些实施例中，第一donor-CU向第二donor-CU发送用于请求修改在所述第二donor-CU拓扑中的服务所述业务的资源的第一传输迁移修改请求。
例如，在业务的服务参数发生变化的情况下，第一donor-CU向第二donor-CU发送用于请求修改在所述第二donor-CU拓扑中的服务所述业务的资源的第一传输迁移修改请求。例如，服务参数包括QoS(用户面业务)和/或业务类型(非用户面业务)。第一传输迁移修改请求包括如下信息：所述业务的业务标识，所述业务的服务质量 (QoS)和/或业务类型。
在一些实施例中，第一donor-CU接收第二donor-CU发送的用于修改在第二donor-CU的拓扑中的服务所述业务的资源的传输迁移修改响应。
例如，传输迁移修改响应包括如下信息：所述业务的业务标识，所述业务在第二donor-CU的拓扑中的BH信息。
在一些实施例中，所述在第二donor-CU的拓扑中的BH信息包括以下至少一项：
下行业务的入口路由标识(routing ID)；
下行业务的入口BH RLC信道；
下行业务的上一跳BAP地址；
下行业务的QoS映射信息。
在一些实施例中，所述在第二donor-CU的拓扑中的BH信息包括以下至少一项：
上行业务的出口路由标识(routing ID)；
上行业务的出口BH RLC信道；
上行业务的下一跳BAP地址。
在一些实施例中，第一donor-CU通过第一传输迁移管理请求(TRANSPORT MIGRATION MANAGEMENT REQUEST)消息发送第一传输迁移修改请求，和/或，第一donor-CU通过传输迁移管理响应(TRANSPORT MIGRATION MANAGEMENT RESPONSE)消息接收传输迁移修改响应。但本申请不限于此，承载传输迁移修改请求和/或传输迁移修改响应的还可以是其他消息。
由此，通过第一传输迁移修改请求和传输迁移修改响应，能够根据业务的服务参数的改变对服务迁移业务的传输资源进行修改，使得当业务的服务参数变化后依然能满足业务的服务要求。
以下再示意性说明第一donor-CU接收针对业务的传输迁移修改响应后的情况。
在一些实施例中，第一donor-CU接收针对所述业务的传输迁移修改响应后，例如，针对IAB节点的业务，向所述IAB节点配置更新所述业务的上行BH信息。
在一些实施例中，第一donor-CU接收针对所述业务的传输迁移修改响应后，例如，针对子节点的上行业务，向所述IAB节点配置更新以下至少一项：上行方向的拓扑间的BAP头部重写信息、所述第二donor-CU的拓扑中的路由信息、上行方向的拓扑间的BH RLC信道映射信息。
在一些实施例中，第一donor-CU接收针对所述业务的传输迁移修改响应后，例 如，针对子节点的下行业务，向所述IAB节点配置更新以下至少一项：下行方向的拓扑间的BAP头部重写信息、下行方向的拓扑间的BH RLC信道映射信息。
以上对于层2(L2)相关配置的情况进行了说明，以下再对IP地址的情况进行说明。
在一些实施例中，第一donor-CU向第二donor-CU发送用于请求修改针对所述IAB节点的IP地址的第一传输迁移修改请求。
例如，在子节点的业务在第一donor-CU的拓扑中的路由标识(routing ID)和/或宿主分布单元(donor-DU)发生改变的情况下，第一donor-CU向第二donor-CU发送用于请求修改针对所述子节点的IP地址的第一传输迁移修改请求。
在一些实施例中，所述第一传输迁移修改请求包含在第一传输迁移管理请求消息中。
在一些实施例中，所述第一传输迁移修改请求包括如下信息：IAB节点标识或IP地址请求索引，所述第一donor-CU的拓扑中的donor-DU的BAP地址。可选地，所述IP地址请求还可以包括：锚定于所述donor-DU的IP地址。
在一些实施例中，第一donor-CU接收第二donor-CU发送的用于修改针对所述IAB节点的IP地址的传输迁移修改响应。
在一些实施例中，所述传输迁移修改响应包含在传输迁移管理响应消息中。
在一些实施例中，所述传输迁移修改响应包括如下信息：IAB节点标识或IP地址请求索引，所述第一donor-CU的拓扑中的donor-DU的BAP地址以及锚定于所述第二donor-CU拓扑的donor-DU的IP地址。
在一些实施例中，第一donor-CU接收针对IAB节点的传输迁移修改响应之后，向所述IAB节点配置锚定于第二donor-CU拓扑的donor-DU的IP地址。
在本申请实施例中，“锚定于donor-DU的IP地址(IP address anchored to IAB donor-DU)”可以理解为“由donor-DU分配的IP地址”或者“经由donor-DU可路由的传输网络层(TNL)地址(TNL address(es)that is(are)routable via the IAB-donor-DU)”，以上术语可以相互替换，本申请不限于此。
以上说明了第二donor-CU接受传输迁移修改请求的情况。如果第二donor-CU确定无法接受传输迁移修改请求，例如无法满足修改之后业务的QoS要求，可以拒绝传输迁移修改请求。
在一些实施例中，第一donor-CU接收第二donor-CU发送的用于拒绝针对所述业 务的第一传输迁移修改请求的传输迁移修改响应。
例如，第一donor-CU通过传输迁移管理响应消息接收所述传输迁移修改响应。再例如，所述传输迁移管理响应消息包含所述业务的业务标识。
以下再通过信令交互进一步示例性说明第一donor-CU发起的传输迁移修改过程。
图11是本申请实施例的传输迁移修改的一信令流程图。例如，当业务的QoS发生变化，donor-CU 1需要更新迁移业务的QoS，donor-CU 1请求修改迁移业务的QoS。
-donor-CU 1通过TRANSPORT MIGRATION MANAGEMENT REQUEST消息或者TRANSPORT MIGRATION MODIFICATION REQUEST消息向donor-CU 2发送如下至少之一的信息(针对每个请求修改的业务流)：
--业务标识；
--业务的QoS信息或业务类型。
因为业务的QoS修改之后，业务在donor-CU 1的拓扑中的routing ID和在donor-CU 1的拓扑中的donor-DU也可能改变，因此还可能发送针对boundary node和子节点的IP地址请求(例如可以包括在上述的请求消息中)，包括：
--节点标识或IP地址请求索引；
--IP地址请求(包括donor-CU1拓扑中的新donor-DU BAP地址)，可选地，还可以包括锚定于该donor-DU的IP地址。
-donor-CU 2收到传输迁移修改请求，根据修改的业务的QoS来更新业务在donor-CU 2的拓扑中的路径上的BH RLC信道和路由；donor-CU 2可能修改业务在donor-CU 2的拓扑中的routing ID或BH RLC信道，或下行QoS映射信息(例如DSCP值或IPv6的流标识flow label)。
-donor-CU 2可通过TRANSPORT MIGRATION MANAGEMENT RESPONSE消息或TRANSPORT MIGRATION MODIFICATION RESPONSE消息向donor-CU 1发送如下至少之一的信息(针对每个请求修改的业务流)：
--业务标识；
--业务在donor-CU 2的拓扑中的routing ID和BH RLC信道(包括下行业务的入口routing ID和入口BH RLC信道，或者，上行业务的出口routing ID和出口BH RLC信道)；
--下行业务在donor-CU 2的拓扑中的上一跳BAP地址；
--上行业务在donor-CU2拓扑中的下一跳BAP地址；
--下行业务使用的QoS映射信息(如DSCP或IPv6的flow label)。
如果donor-CU 2收到IP地址请求，则还需要发送IP地址响应(例如可以包括在上述的响应消息中)，包括：
--节点标识或IP地址请求索引；
--IP地址响应(包括donor-CU1拓扑中的新donor-DU BAP地址以及锚定于donor-CU2的donor-DU的IP地址)。
-如果donor-CU 2确定无法满足修改之后业务的QoS要求，可以拒绝该传输迁移修改请求，donor-CU 2向donor-CU 1发送拒绝修改的业务标识。
-如果donor-CU 2向donor-CU 1发送传输迁移修改成功响应，donor-CU 1需要根据donor-CU 2发送的以上信息进行如下更新：
--donor-CU 1更新业务的QoS映射信息。
--L2配置信息，包括：
---针对迁移节点的业务，donor-CU 1向迁移节点配置更新业务的上行BH信息。
---针对子节点的业务，donor-CU1向迁移节点配置更新拓扑间的BAB头部重写信息、属于donor-CU2拓扑的路由表以及两个拓扑间的BH RLC信道映射表。
--如果收到IP地址响应，donor-CU1还通过RRC重配置消息更新迁移节点和/或子节点的IP地址。
以上以QoS修改为例进行了说明，但本申请不限于此。
再例如，donor-CU 1需要修改业务在donor-CU 1的拓扑中的donor-DU，或修改业务在donor-CU 1的拓扑中的routing ID导致改变了donor-DU。
-donor-CU 1向donor-CU 2发送IP地址请求，包括：
--节点标识或IP地址请求索引；
--IP地址请求(包括donor-CU 1的拓扑中的新donor-DU BAP地址)，可选地，还可以包括锚定于该donor-DU的IP地址。
-donor-CU 2向donor-CU 1发送IP地址响应，包括：
--节点标识或IP地址请求索引；
--IP地址响应(包括donor-CU 1的拓扑中的新donor-DU BAP地址以及锚定于donor-CU 2的donor-DU的IP地址)。
以上信令过程仅示意性对本申请实施例进行了说明，但本申请不限于此，关于信令的更具体的内容，还可以参考相关技术。此外，例如可以适当地调整各个操作之间的执行顺序，此外还可以增加其他的一些操作或者减少其中的某些操作。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图11的记载。
在一些实施例中，在IAB节点的IAB-MT由第一donor-CU切换到第二donor-CU，并且第二donor-CU的拓扑中已建立用于服务IAB节点(包括迁移节点和子节点)的一个或多个业务的资源的情况下，第一donor-CU发送针对一个或多个业务的第一传输迁移修改请求。
例如，donor-CU 1发起的传输迁移修改过程可以在迁移节点从F1-terminating CU下的父节点切换到non-F1-terminating CU下的父节点，且所有业务迁移至non-F1-terminating CU的拓扑之后进行。
在一些实施例中，在IAB节点的IAB-MT由第一donor-CU重建立到所述第二donor-CU，并且第二donor-CU的拓扑中已建立用于服务IAB节点(包括迁移节点和子节点)的一个或多个业务的资源的情况下，第一donor-CU发送针对一个或多个业务的第一传输迁移修改请求。
例如，donor-CU 1发起的传输迁移修改过程可以在迁移节点从F1-terminating CU下的父节点重建立到non-F1-terminating CU下的父节点，且所有业务迁移至non-F1-terminating CU的拓扑之后进行。
在一些实施例中，IAB节点的IAB-MT与第一donor-CU和第二donor-CU建立有双连接，在第二donor-CU的拓扑中已建立用于服务IAB节点(包括迁移节点和子节点)的一个或多个业务的资源的情况下，第一donor-CU发送针对一个或多个业务的第一传输迁移修改请求。
例如，donor-CU 1发起的传输迁移修改过程可以在迁移节点与F1-terminating CU和non-F1-terminating CU建立双连接，且部分业务的传输路径迁移至non-F1-terminating CU的拓扑之后进行。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
由上述实施例可知，第一donor-CU向第二donor-CU发送针对业务的第一传输迁移修改请求；以及第一donor-CU接收第二donor-CU发送的针对所述业务的传输迁移 修改响应。由此，第二donor-CU能够根据业务的服务参数的改变对服务迁移业务的传输资源进行修改，使得当业务的服务参数变化后依然能满足业务的服务要求。
第二方面的实施例
本申请实施例提供一种传输迁移管理方法，从第二donor-CU进行说明。与第一方面的实施例相同的内容不再赘述。IAB节点的IAB-DU与第一donor-CU保持F1连接，第二donor-CU的拓扑中已建立用于服务所述IAB节点的业务的资源。
图12是本申请实施例的传输迁移管理方法的另一示意图。如图12所示，该方法包括：
1201，第二donor-CU接收第一donor-CU发送的针对业务的第一传输迁移修改请求；以及
1202，第二donor-CU向第一donor-CU发送针对所述业务的传输迁移修改响应。
值得注意的是，以上附图12仅对本申请实施例进行了示意性说明，但本申请不限于此。例如可以适当地调整各个操作之间的执行顺序，此外还可以增加其他的一些操作或者减少其中的某些操作。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图12的记载。
在一些实施例中，所述IAB节点的IAB-MT与所述第二donor-CU保持RRC连接，或者，所述IAB节点的IAB-MT与所述第一donor-CU保持RRC连接。
在一些实施例中，所述业务包括如下至少之一或组合：F1控制面(F1-C)业务、F1用户面(F1-U)业务、非F1业务。
在一些实施例中，所述第二donor-CU接收所述第一donor-CU发送的用于请求修改在所述第二donor-CU拓扑中的服务所述业务的资源的第一传输迁移修改请求。
例如，在所述业务的服务参数发生变化的情况下，第二donor-CU接收第一donor-CU发送的用于请求修改在所述第二donor-CU拓扑中的服务所述业务的资源的第一传输迁移修改请求。
在一些实施例中，所述第二donor-CU通过第一传输迁移管理请求(TRANSPORT MIGRATION MANAGEMENT REQUEST)消息接收所述第一传输迁移修改请求。
在一些实施例中，所述第一传输迁移修改请求包括如下信息：所述业务的业务标识，所述业务的服务质量(QoS)和/或业务类型。
在一些实施例中，所述第二donor-CU在接收到所述第一传输迁移修改请求后， 更新所述业务的QoS映射信息。
在一些实施例中，所述第二donor-CU在接收到所述第一传输迁移修改请求后，更新所述业务的L2相关的配置，包括以下至少一项：
在所述第二donor-CU的拓扑中的路径上使用的回传(BH)无线链路控制(RLC)信道和/或BAP子层路由；
所述业务的上行BH信息；其中，所述上行BH信息包括路由标识、上行BH RLC信道和/或下一跳节点的BAP地址；
所述业务的上行出口(egress)路由标识、出口BH RLC信道和/或下一跳节点的BAP地址；
或者，所述业务的下行入口(ingress)路由标识、入口BH RLC信道和/或上一跳节点的BAP地址。
在一些实施例中，所述第二donor-CU向所述第一donor-CU发送用于修改在所述第二donor-CU的拓扑中的服务所述业务的资源的传输迁移修改响应。
在一些实施例中，所述第二donor-CU通过传输迁移管理响应(TRANSPORT MIGRATION MANAGEMENT RESPONSE)消息发送所述传输迁移修改响应。
在一些实施例中，所述传输迁移修改响应包括如下信息：所述业务的业务标识，所述业务在第二donor-CU的拓扑中的BH信息。
在一些实施例中，在第二donor-CU的拓扑中的BH信息包括以下至少一项：
下行业务的入口路由标识(routing ID)；
下行业务的入口BH RLC信道；
下行业务的上一跳BAP地址；
下行业务的QoS映射信息。
在一些实施例中，在第二donor-CU的拓扑中的BH信息包括以下至少一项：
上行业务的出口路由标识(routing ID)；
上行业务的出口BH RLC信道；
上行业务的下一跳BAP地址。
在一些实施例中，所述第二donor-CU接收所述第一donor-CU发送的用于请求修改针对所述IAB节点的IP地址的第一传输迁移修改请求。
例如，在所述业务的所述第一donor-CU的拓扑中的路由标识(routing ID)和/或宿主分布单元(donor-DU)发生改变的情况下，第二donor-CU接收所述第一 donor-CU发送的用于请求修改针对所述IAB节点的IP地址的第一传输迁移修改请求。
在一些实施例中，所述第一传输迁移修改请求包含在第一传输迁移管理请求消息中。
在一些实施例中，所述第一传输迁移修改请求包括如下信息：IAB节点标识或IP地址请求索引，所述第一donor-CU的拓扑中的donor-DU的BAP地址。
在一些实施例中，所述第一传输迁移修改请求还包括：锚定于所述donor-DU的IP地址。
在一些实施例中，所述第二donor-CU向所述第一donor-CU发送用于修改针对所述IAB节点的IP地址的传输迁移修改响应。
在一些实施例中，所述传输修改响应包含在传输迁移管理响应消息中。
在一些实施例中，所述传输修改响应包括如下信息：IAB节点标识或IP地址请求索引，所述第一donor-CU的拓扑中的donor-DU的BAP地址以及锚定于所述第二donor-CU拓扑的donor-DU的IP地址。
在一些实施例中，所述第二donor-CU在接收到所述第一传输迁移修改请求后，拒绝针对所述业务的第一传输迁移修改请求。
例如，在无法满足所述业务的服务质量(QoS)的情况下，第二donor-CU在接收到所述第一传输迁移修改请求后，拒绝针对所述业务的第一传输迁移修改请求。
在一些实施例中，所述第二donor-CU向所述第一donor-CU发送用于拒绝针对所述业务的传输迁移修改请求的传输迁移修改响应。
在一些实施例中，所述第二donor-CU通过传输迁移管理消息发送所述传输迁移修改响应。
在一些实施例中，所述传输迁移修改响应包含所述业务的业务标识。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
由上述实施例可知，第一donor-CU向第二donor-CU发送针对业务的第一传输迁移修改请求；以及第一donor-CU接收第二donor-CU发送的针对所述业务的传输迁移修改响应。由此，第二donor-CU能够根据业务的服务参数的改变对服务迁移业务的传输资源进行修改，使得当业务的服务参数变化后依然能满足业务的服务要求。
第三方面的实施例
本申请实施例提供一种传输迁移管理方法，从第二宿主集中单元(donor-CU)进行说明。其中，IAB节点的IAB-DU与第一宿主集中单元(donor-CU)保持F1连接，第二donor-CU的拓扑中已建立用于服务所述IAB节点的业务的资源。
图13是本申请实施例的传输迁移管理方法的一示意图。如图13所示，该方法包括：
1301，第二donor-CU向第一donor-CU发送针对业务的第二传输迁移修改请求；以及
1302，第二donor-CU修改在第二donor-CU的拓扑中的服务所述业务的资源。
值得注意的是，以上附图13仅对本申请实施例进行了示意性说明，但本申请不限于此。例如可以适当地调整各个操作之间的执行顺序，此外还可以增加其他的一些操作或者减少其中的某些操作。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图13的记载。
在一些实施例中，IAB节点的IAB-MT与第二donor-CU保持RRC连接；例如迁移节点的IAB-MT与第二donor-CU保持RRC连接。或者，IAB节点的IAB-MT与第一donor-CU保持RRC连接；例如迁移节点的子节点与第一donor-CU保持RRC连接。
在一些实施例中，所述业务包括如下至少之一或组合：F1控制面(F1-C)业务、F1用户面(F1-U)业务、非F1业务；本申请实施例不限于此。
在一些实施例中，第二donor-CU向第一donor-CU发送用于修改所述业务在第二donor-CU的拓扑中的路由标识(routing ID)和/或BH RLC信道的所述第二传输迁移修改请求。
在一些实施例中，第二传输迁移修改请求包括如下信息：所述业务的业务标识；所述业务在第二donor-CU的拓扑中的BH信息。
在一些实施例中，在第二donor-CU的拓扑中的BH信息包括以下至少一项：
上行业务的出口路由标识(routing ID)；
上行业务的出口BH RLC信道；
上行业务的下一跳BAP地址。
在一些实施例中，在第二donor-CU的拓扑中的BH信息包括以下至少一项：
下行业务的入口路由标识(routing ID)；
下行业务的入口BH RLC信道；
下行业务的上一跳BAP地址。
在一些实施例中，第二donor-CU通过第二传输迁移管理请求(TRANSPORT MIGRATION MANAGEMENT REQUEST)消息发送所述第二传输迁移修改请求。但本申请不限于此，承载传输迁移修改请求的还可以是其他消息。
由此，在第二donor-CU修改用于服务所述业务的资源时，第一donor-CU通过第二传输迁移修改请求能够对业务的L2相关信息进行修改，以保障迁移业务在第二donor-CU拓扑中的正常传输。
以下再示意性说明第二donor-CU发送针对业务的传输迁移修改请求后的情况。
在一些实施例中，第二donor-CU修改在第二donor-CU的拓扑中的服务所述业务的资源，包括第二donor-CU更新所述业务在第二donor-CU的拓扑中的L2相关信息，例如，L2相关信息例如包括以下至少一项信息：
在第二donor-CU的拓扑中路径上使用的BH RLC信道和/或BAP子层路由；
所述业务的上行BH信息；其中，所述上行BH信息包括路由标识，上行BH RLC信道和/或下一跳节点的BAP地址。
所述业务的上行出口(egress)路由标识、出口BH RLC信道和/或下一跳节点的BAP地址；
或者，所述业务的下行入口(ingress)路由标识、入口BH RLC信道和/或上一跳节点的BAP地址。
以上对于层2(L2)信息相关的修改情况进行了说明，以下再对IP地址的情况进行说明。
在一些实施例中，第二donor-CU向第一donor-CU发送用于修改针对所述IAB节点的IP地址的第二传输迁移修改请求。
例如，在所述业务(包括迁移节点的业务或子节点的业务)在第二donor-CU的拓扑中的路由标识(routing ID)和/或宿主分布单元(donor-DU)发生改变的情况下，第二donor-CU向第一donor-CU发送用于修改针对所述IAB节点(包括迁移节点或子节点)的IP地址的第二传输迁移修改请求。
在一些实施例中，所述第二传输迁移修改请求包含在第二传输迁移管理请求消息中。
在一些实施例中，所述第二传输迁移修改请求包括如下信息：IAB节点标识或IP 地址请求索引，所述第一donor-CU的拓扑中的donor-DU的BAP地址或所述第二donor-CU的拓扑中的donor-DU的BAP地址，以及锚定于所述第二donor-CU拓扑的donor-DU的IP地址。
例如，针对子节点的业务，第二传输迁移修改请求包括如下信息：IAB节点标识或IP地址请求索引，所述第一donor-CU的拓扑中的donor-DU的BAP地址，以及锚定于所述第二donor-CU拓扑的donor-DU的IP地址。又例如，针对迁移节点的业务，第二传输迁移修改请求包括如下信息：IAB节点标识或IP地址请求索引，所述第二donor-CU的拓扑中的donor-DU的BAP地址，以及锚定于所述第二donor-CU拓扑的donor-DU的IP地址。
以下再通过信令交互进一步示例性说明第二donor-CU发起的传输迁移修改过程。
图14是本申请实施例的传输迁移修改的一信令流程图。例如，当业务在donor-CU 2的拓扑中的routing ID或BH RLC信道发生变化，donor-CU 2请求修改迁移业务的routing ID或BH RLC信道，使得donor-CU 1更新与所述业务相关的L2信息。
-donor-CU 2可通过TRANSPORT MIGRATION MANAGEMENT REQUEST消息或者TRANSPORT MIGRATION MODIFICATION REQUEST)消息向donor-CU 1发送如下信息(针对每个请求修改的业务流)：
--业务标识；
--业务在donor-CU 2的拓扑中的routing ID和BH RLC信道(包括下行业务的入口routing ID和入口BH RLC信道，或者，上行业务的出口routing ID和出口BH RLC信道)；
--下行业务在donor-CU 2的拓扑中的上一跳BAP地址；
--上行业务在donor-CU 2的拓扑中的下一跳BAP地址。
因为业务的routing ID修改之后，业务在donor-CU 2的拓扑中的donor-DU也可能改变。donor-CU 2还可能发送IP地址指示(例如包括在上述请求消息中)，包括：
--节点标识或IP地址请求索引；
--IP地址指示(包括donor-CU 1的拓扑中的donor-DU BAP地址以及锚定于donor-CU 2的donor-DU的IP地址)。
-donor-CU 2需要根据业务在donor-CU 2的拓扑中的新routing ID或BH RLC信道，更新业务在donor-CU 2的拓扑中的路径上的BH RLC信道和路由。
-donor-CU 1收到传输迁移修改请求时，可以无需响应，只需根据这些信息来更 新相关配置，包括：
--更新业务的L2相关信息，包括：
---针对迁移节点的业务，更新上行BH信息，包括路由标识、BH RLC信道ID和下一跳节点地址。
---针对子节点的业务，更新在拓扑间的BAP头部重写信息、属于donor-CU 2的拓扑的路由表以及两个拓扑间的BH RLC信道映射表，
--或者，通过RRC重配置消息更新迁移节点和子节点的IP地址。
以上以L2相关信息变化为例进行了说明，但本申请不限于此。
再例如，donor-CU 2需要修改业务的IP地址，或改变在donor-CU 2的拓扑中的donor-DU导致需要更新业务的IP地址。
-donor-CU 2向donor-CU 1发送IP地址指示，包括：
--节点标识或IP地址请求索引；
--IP地址指示(包括donor-CU 1的拓扑中的donor-DU BAP地址或donor-CU2的拓扑中的donor-DU BAP地址，以及锚定于donor-CU 2的donor-DU的IP地址)。
-donor-CU 1收到以上信息后无需响应，只需通过RRC重配置消息更新迁移节点和子节点的IP地址。
以上信令过程仅示意性对本申请实施例进行了说明，但本申请不限于此，关于信令的更具体的内容，还可以参考相关技术。此外，例如可以适当地调整各个操作之间的执行顺序，此外还可以增加其他的一些操作或者减少其中的某些操作。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图14的记载。
在一些实施例中，在IAB节点的IAB-MT由第一donor-CU切换到第二donor-CU，并且第二donor-CU的拓扑中已建立用于服务IAB节点(包括迁移节点和子节点)的一个或多个业务的资源的情况下，第二donor-CU发送针对一个或多个业务的第二传输迁移修改请求。
例如，donor-CU 2发起的传输迁移修改过程可以在迁移节点从F1-terminating CU下的父节点切换到non-F1-terminating CU下的父节点，且所有业务迁移至non-F1-terminating CU的拓扑之后进行。
在一些实施例中，在IAB节点的IAB-MT由第一donor-CU重建立到所述第二donor-CU，并且第二donor-CU的拓扑中已建立用于服务IAB节点(包括迁移节点和子节点)的一个或多个业务的资源的情况下，第二donor-CU发送针对一个或多个业 务的第二传输迁移修改请求。
例如，donor-CU 2发起的传输迁移修改过程可以在迁移节点从F1-terminating CU下的父节点重建立到non-F1-terminating CU下的父节点，且所有业务迁移至non-F1-terminating CU的拓扑之后进行。
在一些实施例中，IAB节点的IAB-MT与第一donor-CU和第二donor-CU建立有双连接，在第二donor-CU的拓扑中已建立用于服务IAB节点(包括迁移节点和子节点)的一个或多个业务的资源的情况下，第二donor-CU发送针对一个或多个业务的第二传输迁移修改请求。
例如，donor-CU 2发起的传输迁移修改过程可以在迁移节点与F1-terminating CU和non-F1-terminating CU建立双连接，且部分业务的传输路径迁移至non-F1-terminating CU的拓扑之后进行。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
由上述实施例可知，第二donor-CU向第一donor-CU发送针对业务的第二传输迁移修改请求；以及第二donor-CU修改在第二donor-CU的拓扑中的服务所述业务的资源。由此，在第二donor-CU修改用于服务所述业务的资源或修改IAB节点的IP地址时，第一donor-CU能够对业务的L2相关信息或IP地址进行修改，以保障迁移业务在第二donor-CU拓扑中的正常传输。
第四方面的实施例
本申请实施例提供一种传输迁移管理方法，从第一donor-CU进行说明。与第三方面的实施例相同的内容不再赘述。IAB节点的IAB-DU与第一donor-CU保持F1连接，第二donor-CU的拓扑中已建立用于服务所述IAB节点的业务的资源。
图15是本申请实施例的传输迁移管理方法的另一示意图。如图15所示，该方法包括：
1501，第一donor-CU接收第二donor-CU发送的针对业务的第二传输迁移修改请求；其中，第二donor-CU修改在第二donor-CU的拓扑中的服务所述业务的资源。
值得注意的是，以上附图15仅对本申请实施例进行了示意性说明，但本申请不限于此。例如可以适当地调整各个操作之间的执行顺序，此外还可以增加其他的一些 操作或者减少其中的某些操作。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图15的记载。
在一些实施例中，第一donor-CU接收第二donor-CU发送的用于修改所述业务在所述第二donor-CU的拓扑中的路由标识(routing ID)和/或BH RLC信道的所述第二传输迁移修改请求。
在一些实施例中，第一donor-CU通过第二传输迁移管理请求(TRANSPORT MIGRATION MANAGEMENT REQUEST)消息接收所述第二传输迁移修改请求。
在一些实施例中，所述第二传输迁移修改请求包括如下信息：所述业务的业务标识；所述业务在第二donor-CU的拓扑中的BH信息。
在一些实施例中，在第二donor-CU的拓扑中的BH信息包括以下至少一项：
上行业务的出口路由标识(routing ID)；
上行业务的出口BH RLC信道；
上行业务的下一跳BAP地址。
在一些实施例中，在第二donor-CU的拓扑中的BH信息包括以下至少一项：
下行业务的入口路由标识(routing ID)；
下行业务的入口BH RLC信道；
下行业务的上一跳BAP地址。
在一些实施例中，第一donor-CU在接收到针对所述业务的第二传输迁移修改请求后，向所述IAB节点配置更新所述业务的上行BH信息。
在一些实施例中，第一donor-CU在接收到针对所述业务的第二传输迁移修改请求后，向所述IAB节点配置更新以下至少一项：上行方向的拓扑间的BAP头部重写信息、所述第二donor-CU的拓扑中的路由信息、上行方向的拓扑间的BH RLC信道映射信息。
在一些实施例中，第一donor-CU在接收到针对所述业务的第二传输迁移修改请求后，向所述IAB节点配置更新以下至少一项：下行方向的拓扑间的BAP头部重写信息、下行方向的拓扑间的BH RLC信道映射信息。
在一些实施例中，第一donor-CU接收第二donor-CU发送的用于修改针对所述IAB节点的IP地址的第二传输迁移修改请求。
例如，在所述业务的所述第二donor-CU的拓扑中的路由标识(routing ID)和/或宿主分布单元(donor-DU)发生改变的情况下，第一donor-CU接收第二donor-CU 发送的用于修改针对所述IAB节点的IP地址的第二传输迁移修改请求。
在一些实施例中，所述第二传输迁移修改请求包含在第二传输迁移管理请求消息中。
在一些实施例中，所述第二传输迁移修改请求包括如下信息：IAB节点标识或IP地址请求索引，所述第一donor-CU的拓扑中的donor-DU的BAP地址或所述第二donor-CU的拓扑中的donor-DU的BAP地址，以及锚定于所述第二donor-CU拓扑的donor-DU的IP地址。
在一些实施例中，第一donor-CU向所述IAB节点配置锚定于所述第二donor-CU拓扑的donor-DU的IP地址。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
由上述实施例可知，第二donor-CU向第一donor-CU发送针对业务的第二传输迁移修改请求；以及第二donor-CU修改在第二donor-CU的拓扑中的服务所述业务的资源。由此，在第二donor-CU修改用于服务所述业务的资源或修改IAB节点的IP地址时，第一donor-CU能够对业务的L2相关信息或IP地址进行修改，以保障迁移业务在第二donor-CU拓扑中的正常传输。
第五方面的实施例
本申请实施例提供一种IAB宿主设备，与第一方面的实施例相同的内容不再赘述。该设备例如可以是IAB系统中的IAB donor-CU(如第一、二方面的实施例中的第一donor-CU)，也可以是配置于该IAB donor-CU中的某个或某些部件或者组件或者模块。
图16是本申请实施例的IAB宿主设备的一示意图。IAB节点的IAB-DU与第一宿主集中单元(donor-CU)保持F1连接，第二donor-CU的拓扑中已建立用于服务所述IAB节点的业务的资源。
如图16所示，IAB宿主设备1600包括：
发送部1601，其向所述第二donor-CU发送针对所述业务的第一传输迁移修改请求；以及
接收部1602，其接收所述第二donor-CU发送的针对所述业务的传输迁移修改响 应。
在一些实施例中，所述IAB节点的IAB-MT与所述第二donor-CU保持RRC连接，或者，所述IAB节点的IAB-MT与所述第一donor-CU保持RRC连接。
在一些实施例中，所述业务包括如下至少之一或组合：F1控制面业务、F1用户面业务、非F1业务。
在一些实施例中，发送部1601向所述第二donor-CU发送用于请求修改在所述第二donor-CU拓扑中的服务所述业务的资源的第一传输迁移修改请求。
例如，在所述业务的服务参数发生变化的情况下，发送部1601向所述第二donor-CU发送用于请求修改在所述第二donor-CU拓扑中的服务所述业务的资源的第一传输迁移修改请求。
在一些实施例中，通过第一传输迁移管理请求消息发送第一传输迁移修改请求。
在一些实施例中，接收部1602接收第二donor-CU发送的用于修改在第二donor-CU的拓扑中的服务所述业务的资源的传输迁移修改响应。
在一些实施例中，通过传输迁移管理响应消息接收所述传输迁移修改响应。
在一些实施例中，第一传输迁移修改请求包括如下信息：所述业务的业务标识，所述业务的服务质量和/或业务类型。
在一些实施例中，传输迁移修改响应包括如下信息：所述业务的业务标识，所述业务在第二donor-CU的拓扑中的BH信息。
在一些实施例中，在第二donor-CU的拓扑中的BH信息包括以下至少一项：
下行业务的入口路由标识(routing ID)；
下行业务的入口BH RLC信道；
下行业务的上一跳BAP地址；
下行业务的QoS映射信息。
在一些实施例中，在第二donor-CU的拓扑中的BH信息包括以下至少一项：
上行业务的出口路由标识(routing ID)；
上行业务的出口BH RLC信道；
上行业务的下一跳BAP地址。
在一些实施例中，如图16所示，IAB宿主设备1600还包括：
处理部1603，其执行如下至少之一的操作：
更新所述业务的QoS映射信息；
向所述IAB节点配置更新所述业务的上行BH信息；
向所述IAB节点配置更新以下至少一项：上行方向的拓扑间的BAP头部重写信息、所述第二donor-CU的拓扑中的路由信息、上行方向的拓扑间的BH RLC信道映射信息；
向所述IAB节点配置更新以下至少一项：下行方向的拓扑间的BAP头部重写信息、下行方向的拓扑间的BH RLC信道映射信息。
在一些实施例中，发送部1601还向所述第二donor-CU发送用于请求修改针对所述IAB节点的IP地址的第一传输迁移修改请求。
例如，在所述业务的所述第一donor-CU的拓扑中的路由标识(routing ID)和/或宿主分布单元(donor-DU)发生改变的情况下，发送部1601还向所述第二donor-CU发送用于请求修改针对所述IAB节点的IP地址的第一传输迁移修改请求。
在一些实施例中，所述第一传输迁移修改请求包含在第一传输迁移管理请求消息中。
在一些实施例中，所述第一传输迁移修改请求包括如下至少之一的信息：IAB节点标识或IP地址请求索引，所述第一donor-CU的拓扑中的donor-DU的BAP地址，锚定于所述donor-DU的IP地址。
在一些实施例中，接收部1602还接收所述第二donor-CU发送的用于修改针对所述IAB节点的IP地址的传输迁移修改响应。
在一些实施例中，所述传输迁移修改响应包含在传输迁移管理响应消息中。
在一些实施例中，所述传输迁移修改响应包括如下信息：IAB节点标识或IP地址请求索引，所述第一donor-CU的拓扑中的donor-DU的BAP地址以及锚定于所述第二donor-CU拓扑的donor-DU的IP地址。
在一些实施例中，处理部1603向所述IAB节点配置锚定于所述第二donor-CU的拓扑donor-DU的IP地址。
在一些实施例中，接收部1602还接收所述第二donor-CU发送的用于拒绝针对所述业务的第一传输迁移修改请求的传输迁移修改响应。
在一些实施例中，通过传输迁移管理响应消息接收所述传输迁移修改响应；所述传输迁移管理响应消息包含所述业务的业务标识。
在一些实施例中，在所述IAB节点的IAB-MT由所述第一donor-CU切换到所述第二donor-CU，并且所述第二donor-CU的拓扑中已建立用于服务所述IAB节点的一 个或多个业务的资源的情况下，发送部1601发送针对所述一个或多个业务的第一传输迁移修改请求。
在一些实施例中，在所述IAB节点的IAB-MT由所述第一donor-CU重建立到所述第二donor-CU，并且所述第二donor-CU的拓扑中已建立用于服务所述IAB节点的一个或多个业务的资源的情况下，发送部1601发送针对所述一个或多个业务的第一传输迁移修改请求。
在一些实施例中，所述IAB节点的IAB-MT与所述第一donor-CU和所述第二donor-CU建立有双连接，在所述第二donor-CU的拓扑中已建立用于服务所述IAB节点的一个或多个业务的资源的情况下，发送部1601发送针对所述一个或多个业务的第一传输迁移修改请求。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
值得注意的是，以上仅对与本申请相关的各部件或模块进行了说明，但本申请不限于此。本申请实施例的IAB宿主设备1600还可以包括其它部件或者模块，关于这些部件或者模块的具体内容，可以参考相关技术。
此外，为了简单起见，图16中仅示例性示出了各个部件或模块之间的连接关系或信号走向，但是本领域技术人员应该清楚的是，可以采用总线连接等各种相关技术。上述各个部件或模块可以通过例如处理器、存储器、发射机、接收机等硬件设施来实现；本申请实施并不对此进行限制。
由上述实施例可知，第一donor-CU向第二donor-CU发送针对业务的第一传输迁移修改请求；以及第一donor-CU接收第二donor-CU发送的针对所述业务的传输迁移修改响应。由此，第二donor-CU能够根据业务的服务参数的改变对服务迁移业务的传输资源进行修改，使得当业务的服务参数变化后依然能满足业务的服务要求。
第六方面的实施例
本申请实施例提供一种IAB宿主设备，与第二方面的实施例相同的内容不再赘述。该设备例如可以是IAB系统中的IAB donor-CU(如第一、二方面的实施例中的第二donor-CU)，也可以是配置于该IAB donor-CU中的某个或某些部件或者组件或者模块。
图17是本申请实施例的IAB宿主设备的一示意图。其中，IAB节点的IAB-DU与第一donor-CU保持F1连接，第二donor-CU的拓扑中已建立用于服务所述IAB节点的业务的资源。
如图17所示，IAB宿主设备1700包括：
接收部1701，其接收所述第一donor-CU发送的针对所述业务的第一传输迁移修改请求；以及
发送部1702，其向所述第一donor-CU发送针对所述业务的传输迁移修改响应。
在一些实施例中，所述IAB节点的IAB-MT与所述第二donor-CU保持RRC连接，或者，所述IAB节点的IAB-MT与所述第一donor-CU保持RRC连接。
在一些实施例中，所述业务包括如下至少之一或组合：F1控制面(F1-C)业务、F1用户面(F1-U)业务、非F1业务。
在一些实施例中，所述接收部1701接收所述第一donor-CU发送的用于请求修改在所述第二donor-CU拓扑中的服务所述业务的资源的第一传输迁移修改请求。
例如，在所述业务的服务参数发生变化的情况下，接收部1701接收所述第一donor-CU发送的用于请求修改在所述第二donor-CU拓扑中的服务所述业务的资源的第一传输迁移修改请求。
在一些实施例中，通过第一传输迁移管理请求消息接收第一传输迁移修改请求。
在一些实施例中，所述第一传输迁移修改请求包括如下信息：所述业务的业务标识，所述业务的服务质量(QoS)和/或业务类型。
在一些实施例中，如图17所示，IAB宿主设备1700还包括：
处理部1703，其更新所述业务在所述第二donor-CU的拓扑中的路径上使用的回传(BH)无线链路控制(RLC)信道和/或BAP子层路由，或者更新所述业务的QoS映射信息。
在一些实施例中，处理部1703更新所述业务的上行BH信息；其中，所述上行BH信息包括路由标识、上行BH RLC信道和/或下一跳节点的BAP地址。
在一些实施例中，处理部1703更新所述业务的上行出口(egress)路由标识、出口BH RLC信道和/或下一跳节点的BAP地址；或者，更新所述业务的下行入口(ingress)路由标识、入口BH RLC信道和/或上一跳节点的BAP地址。
在一些实施例中，所述发送部1702向所述第一donor-CU发送用于修改在所述第二donor-CU的拓扑中的服务所述业务的资源的传输迁移修改响应。
在一些实施例中，通过传输迁移管理响应消息发送所述传输迁移修改响应。
在一些实施例中，所述传输迁移修改响应包括如下信息：所述业务的业务标识，所述业务在第二donor-CU的拓扑中的BH信息。
在一些实施例中，所述在第二donor-CU的拓扑中的BH信息包括以下至少一项：
下行业务的入口路由标识(routing ID)；
下行业务的入口BH RLC信道；
下行业务的上一跳BAP地址；
下行业务的QoS映射信息。
在一些实施例中，所述在第二donor-CU的拓扑中的BH信息包括以下至少一项：
上行业务的出口路由标识(routing ID)；
上行业务的出口BH RLC信道；
上行业务的下一跳BAP地址。
在一些实施例中，所述接收部1701接收所述第一donor-CU发送的用于请求修改针对所述IAB节点的IP地址的第一传输迁移修改请求。
例如，在所述业务的所述第一donor-CU的拓扑中的路由标识(routing ID)和/或宿主分布单元(donor-DU)发生改变的情况下，接收部1701接收所述第一donor-CU发送的用于请求修改针对所述IAB节点的IP地址的第一传输迁移修改请求。
在一些实施例中，所述第一传输迁移修改请求包含在第一传输迁移管理请求消息中。
在一些实施例中，所述第一传输迁移修改请求包括如下至少之一的信息：IAB节点标识或IP地址请求索引，所述第一donor-CU的拓扑中的donor-DU的BAP地址，锚定于所述donor-DU的IP地址。
在一些实施例中，发送部1702还向第一donor-CU发送用于修改针对所述IAB节点的IP地址的传输迁移修改响应。其中，所述传输迁移修改响应包含在传输迁移管理响应消息中。
在一些实施例中，所述传输迁移修改响应包括如下信息：IAB节点标识或IP地址请求索引，所述第一donor-CU的拓扑中的donor-DU的BAP地址以及锚定于所述第二donor-CU拓扑的donor-DU的IP地址。
在一些实施例中，处理部1703在接收到所述第一传输迁移修改请求后，拒绝针对所述业务的第一传输迁移修改请求。
例如，在无法满足所述业务的服务质量(QoS)的情况下，在接收到所述第一传输迁移修改请求后，处理部1703拒绝针对所述业务的第一传输迁移修改请求。
在一些实施例中，发送部1702向所述第一donor-CU发送用于拒绝针对所述业务的传输迁移修改请求的传输迁移修改响应。
在一些实施例中，所述第二donor-CU通过传输迁移管理消息发送所述传输迁移修改响应。其中，所述传输迁移修改响应包含所述业务的业务标识。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
值得注意的是，以上仅对与本申请相关的各部件或模块进行了说明，但本申请不限于此。本申请实施例的IAB宿主设备1700还可以包括其它部件或者模块，关于这些部件或者模块的具体内容，可以参考相关技术。
此外，为了简单起见，图17中仅示例性示出了各个部件或模块之间的连接关系或信号走向，但是本领域技术人员应该清楚的是，可以采用总线连接等各种相关技术。上述各个部件或模块可以通过例如处理器、存储器、发射机、接收机等硬件设施来实现；本申请实施并不对此进行限制。
由上述实施例可知，第一donor-CU向第二donor-CU发送针对业务的第一传输迁移修改请求；以及第一donor-CU接收第二donor-CU发送的针对所述业务的传输迁移修改响应。由此，第二donor-CU能够根据业务的服务参数的改变对服务迁移业务的传输资源进行修改，使得当业务的服务参数变化后依然能满足业务的服务要求。
第七方面的实施例
本申请实施例提供一种IAB宿主设备，与第三方面的实施例相同的内容不再赘述。该设备例如可以是IAB系统中的IAB donor-CU(如第三、四方面的实施例中的第二donor-CU)，也可以是配置于该IAB donor-CU中的某个或某些部件或者组件或者模块。
图18是本申请实施例的IAB宿主设备的一示意图。IAB节点的IAB-DU与第一宿主集中单元(donor-CU)保持F1连接，第二donor-CU的拓扑中已建立用于服务所述IAB节点的业务的资源。
如图18所示，IAB宿主设备1800包括：
发送部1801，其向所述第一donor-CU发送针对业务的第二传输迁移修改请求；以及
处理部1802，其修改在所述第二donor-CU的拓扑中的服务所述业务的资源。
在一些实施例中，发送部1801向所述第一donor-CU发送用于修改所述业务在第二donor-CU的拓扑中的路由标识(routing ID)和/或BH RLC信道的所述第二传输迁移修改请求。
在一些实施例中，通过第二传输迁移管理请求(TRANSPORT MIGRATION MANAGEMENT REQUEST)消息发送所述第二传输迁移修改请求。
在一些实施例中，所述第二传输迁移修改请求包括如下信息：
所述业务的业务标识；
所述业务在第二donor-CU的拓扑中的BH信息。
在一些实施例中，所述在第二donor-CU的拓扑中的BH信息包括以下至少一项：
上行业务的出口路由标识(routing ID)；
上行业务的出口BH RLC信道；
上行业务的下一跳BAP地址。
在一些实施例中，所述在第二donor-CU的拓扑中的BH信息包括以下至少一项：
下行业务的入口路由标识(routing ID)；
下行业务的入口BH RLC信道；
下行业务的上一跳BAP地址。
在一些实施例中，处理部1802更新所述业务在所述第二donor-CU的拓扑中的路径上使用的BH RLC信道和/或BAP子层路由。
在一些实施例中，处理部1802更新所述业务的上行BH信息；其中，所述上行BH信息包括路由标识，上行BH RLC信道和/或下一跳节点的BAP地址。
在一些实施例中，处理部1802更新所述业务的上行出口(egress)路由标识、出口BH RLC信道和/或下一跳节点的BAP地址；或者，更新所述业务的下行入口(ingress)路由标识、入口BH RLC信道和/或上一跳节点的BAP地址。
在一些实施例中，发送部1801还向所述第一donor-CU发送用于修改针对所述IAB节点的IP地址的第二传输迁移修改请求。
例如，在所述业务的所述第二donor-CU的拓扑中的路由标识(routing ID)和/或宿主分布单元(donor-DU)发生改变的情况下，发送部1801还向所述第一donor-CU 发送用于修改针对所述IAB节点的IP地址的第二传输迁移修改请求。
在一些实施例中，所述第二传输迁移修改请求包含在第二传输迁移管理请求消息中。
在一些实施例中，所述第二传输迁移修改请求包括如下信息：IAB节点标识或IP地址请求索引，所述第一donor-CU的拓扑中的donor-DU的BAP地址或第二donor-CU的拓扑中的donor-DU的BAP地址，以及锚定于所述第二donor-CU拓扑的donor-DU的IP地址。
在一些实施例中，在所述IAB节点的IAB-MT由所述第一donor-CU切换到所述第二donor-CU，并且所述第二donor-CU的拓扑中已建立用于服务所述IAB节点的一个或多个业务的资源的情况下，发送部1801发送针对所述一个或多个业务的第二传输迁移修改请求。
在一些实施例中，在所述IAB节点的IAB-MT由所述第一donor-CU重建立到所述第二donor-CU，并且所述第二donor-CU的拓扑中已建立用于服务所述IAB节点的一个或多个业务的资源的情况下，发送部1801发送针对所述一个或多个业务的第二传输迁移修改请求。
在一些实施例中，所述IAB节点的IAB-MT与所述第一donor-CU和所述第二donor-CU建立有双连接，在所述第二donor-CU的拓扑中已建立用于服务所述IAB节点的一个或多个业务的资源的情况下，发送部1801发送针对所述一个或多个业务的第二传输迁移修改请求。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
值得注意的是，以上仅对与本申请相关的各部件或模块进行了说明，但本申请不限于此。本申请实施例的IAB宿主设备1800还可以包括其它部件或者模块，关于这些部件或者模块的具体内容，可以参考相关技术。
此外，为了简单起见，图18中仅示例性示出了各个部件或模块之间的连接关系或信号走向，但是本领域技术人员应该清楚的是，可以采用总线连接等各种相关技术。上述各个部件或模块可以通过例如处理器、存储器、发射机、接收机等硬件设施来实现；本申请实施并不对此进行限制。
由上述实施例可知，第二donor-CU向第一donor-CU发送针对业务的第二传输迁 移修改请求；以及第二donor-CU修改在第二donor-CU的拓扑中的服务所述业务的资源。由此，在第二donor-CU修改用于服务所述业务的资源或修改IAB节点的IP地址时，第一donor-CU能够对业务的L2相关信息或IP地址进行修改，以保障迁移业务在第二donor-CU拓扑中的正常传输。
第八方面的实施例
本申请实施例提供一种IAB宿主设备，与第四方面的实施例相同的内容不再赘述。该设备例如可以是IAB系统中的IAB donor-CU(如第三、四方面的实施例中的第一donor-CU)，也可以是配置于该IAB donor-CU中的某个或某些部件或者组件或者模块。
图19是本申请实施例的IAB宿主设备的一示意图。其中，IAB节点的IAB-DU与第一donor-CU保持F1连接，第二donor-CU的拓扑中已建立用于服务所述IAB节点的业务的资源。
如图19所示，IAB宿主设备1900包括：
接收部1901，其接收第二donor-CU发送的针对业务的第二传输迁移修改请求；其中，第二donor-CU修改在第二donor-CU的拓扑中的服务所述业务的资源。
在一些实施例中，接收部1901接收所述第二donor-CU发送的用于修改所述业务在第二donor-CU的拓扑中的路由标识(routing ID)和/或BH RLC信道的所述第二传输迁移修改请求。
在一些实施例中，通过第二传输迁移管理请求(TRANSPORT MIGRATION MANAGEMENT REQUEST)消息接收所述第二传输迁移修改请求。
在一些实施例中，所述第二传输迁移修改请求包括如下信息：
所述业务的业务标识；
所述业务在第二donor-CU的拓扑中的BH信息。
在一些实施例中，所述在第二donor-CU的拓扑中的BH信息包括以下至少一项：
上行业务的出口路由标识(routing ID)；
上行业务的出口BH RLC信道；
上行业务的下一跳BAP地址。
在一些实施例中，所述在第二donor-CU的拓扑中的BH信息包括以下至少一项：
下行业务的入口路由标识(routing ID)；
下行业务的入口BH RLC信道；
下行业务的上一跳BAP地址。
在一些实施例中，如图19所示，IAB宿主设备1900还包括：
处理部1902，其向所述IAB节点配置更新所述业务的上行BH信息。
在一些实施例中，处理部1902向所述IAB节点配置更新以下至少一项：上行方向的拓扑间的BAP头部重写信息、所述第二donor-CU的拓扑中的路由信息、上行方向的拓扑间的BH RLC信道映射信息。
在一些实施例中，处理部1902向所述IAB节点配置更新以下至少一项：下行方向的拓扑间的BAP头部重写信息、下行方向的拓扑间的BH RLC信道映射信息。
在一些实施例中，接收部1901还接收所述第二donor-CU发送的用于修改针对所述IAB节点的IP地址的第二传输迁移修改请求。
例如，在所述业务的所述第二donor-CU的拓扑中的路由标识(routing ID)和/或宿主分布单元(donor-DU)发生改变的情况下，接收部1901还接收所述第二donor-CU发送的用于修改针对所述IAB节点的IP地址的第二传输迁移修改请求。
在一些实施例中，所述第二传输迁移修改请求包含在第二传输迁移管理请求消息中。
在一些实施例中，所述第二传输迁移修改请求包括如下信息：IAB节点标识或IP地址请求索引，所述第一donor-CU的拓扑中的donor-DU的BAP地址或者第一donor-CU的拓扑中的donor-DU的BAP地址，以及锚定于所述第二donor-CU拓扑的donor-DU的IP地址。
在一些实施例中，处理部1902还向所述IAB节点配置锚定于所述第二donor-CU拓扑的donor-DU的IP地址。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。
值得注意的是，以上仅对与本申请相关的各部件或模块进行了说明，但本申请不限于此。本申请实施例的IAB宿主设备1900还可以包括其它部件或者模块，关于这些部件或者模块的具体内容，可以参考相关技术。
此外，为了简单起见，图19中仅示例性示出了各个部件或模块之间的连接关系或信号走向，但是本领域技术人员应该清楚的是，可以采用总线连接等各种相关技术。 上述各个部件或模块可以通过例如处理器、存储器、发射机、接收机等硬件设施来实现；本申请实施并不对此进行限制。
由上述实施例可知，第二donor-CU向第一donor-CU发送针对业务的第二传输迁移修改请求；以及第二donor-CU修改在第二donor-CU的拓扑中的服务所述业务的资源。由此，在第二donor-CU修改用于服务所述业务的资源或修改IAB节点的IP地址时，第一donor-CU能够对业务的L2相关信息或IP地址进行修改，以保障迁移业务在第二donor-CU拓扑中的正常传输。
第九方面的实施例
本申请实施例提供了一种通信系统，包括宿主(donor)设备和IAB节点(IAB-node)；关于宿主(donor)设备、IAB节点的网络架构还可以参考相关技术，此处省略说明。
在一些实施例中，IAB系统包括：
第一宿主集中单元(第一donor-CU)，其发送针对业务的第一传输迁移修改请求，以及接收针对所述业务的传输迁移修改响应；
第二宿主集中单元(第二donor-CU)，其接收所述第一传输迁移修改请求，以及发送所述传输迁移修改响应。
在一些实施例中，IAB系统包括：
第二宿主集中单元(第二donor-CU)，其发送针对业务的第二传输迁移修改请求，以及修改在所述第二宿主集中单元的拓扑中的服务所述业务的资源；
第一宿主集中单元(第一donor-CU)，其接收所述第二传输迁移修改请求。
本申请实施例还提供一种IAB设备，该IAB设备可以是IAB宿主设备，也可以是IAB节点设备(迁移节点或者子节点)。
图20是本申请实施例的IAB设备的示意图。如图20所示，IAB设备2000可以包括：处理器(例如中央处理器CPU)2001和存储器2002；存储器2002耦合到处理器2001。其中该存储器2002可存储各种数据；此外还存储信息处理的程序2005，并且在中央处理器2001的控制下执行该程序2005。
例如，处理器2001可以被配置为执行程序而实现如第一方面的实施例中的传输迁移管理方法。例如，处理器2001可以被配置为进行如下的控制：向第二donor-CU发送针对所述业务的第一传输迁移修改请求；以及接收所述第二donor-CU发送的针 对所述业务的传输迁移修改响应。
再例如，处理器2001可以被配置为执行程序而实现如第二方面的实施例中的传输迁移管理方法。例如，处理器2001可以被配置为进行如下的控制：接收第一donor-CU发送的针对所述业务的第一传输迁移修改请求；以及向所述第一donor-CU发送针对所述业务的传输迁移修改响应。
再例如，处理器2001可以被配置为执行程序而实现如第三方面的实施例中的传输迁移管理方法。例如，处理器2001可以被配置为进行如下的控制：向第一donor-CU发送针对业务的第二传输迁移修改请求；以及修改在所述第二donor-CU的拓扑中的服务所述业务的资源。
再例如，处理器2001可以被配置为执行程序而实现如第四方面的实施例中的传输迁移管理方法。例如，处理器2001可以被配置为进行如下的控制：接收第二donor-CU发送的针对业务的第二传输迁移修改请求；其中，所述第二donor-CU修改在所述第二donor-CU的拓扑中的服务所述业务的资源。
此外，如图20所示，IAB设备2000还可以包括：收发机2003和天线2004等；其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，IAB设备2000也并不是必须要包括图20中所示的所有部件；此外，IAB设备2000还可以包括图20中没有示出的部件，可以参考现有技术。
本申请实施例还提供一种计算机可读程序，其中当在IAB设备中执行所述程序时，所述程序使得计算机在所述IAB设备中执行第一至第四方面的实施例中的传输迁移管理方法。
本申请实施例还提供一种存储有计算机可读程序的存储介质，其中所述计算机可读程序使得计算机在IAB设备中执行第一至第四方面的实施例中的传输迁移管理方法。
本申请以上的装置和方法可以由硬件实现，也可以由硬件结合软件实现。本申请涉及这样的计算机可读程序，当该程序被逻辑部件所执行时，能够使该逻辑部件实现上文所述的装置或构成部件，或使该逻辑部件实现上文所述的各种方法或步骤。逻辑部件例如现场可编程逻辑部件、微处理器、计算机中使用的处理器等。本申请还涉及用于存储以上程序的存储介质，如硬盘、磁盘、光盘、DVD、flash存储器等。
结合本申请实施例描述的方法/装置可直接体现为硬件、由处理器执行的软件模块或二者组合。例如，图中所示的功能框图中的一个或多个和/或功能框图的一个或 多个组合，既可以对应于计算机程序流程的各个软件模块，亦可以对应于各个硬件模块。这些软件模块，可以分别对应于图中所示的各个步骤。这些硬件模块例如可利用现场可编程门阵列(FPGA)将这些软件模块固化而实现。
软件模块可以位于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、移动磁盘、CD-ROM或者本领域已知的任何其它形式的存储介质。可以将一种存储介质耦接至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息；或者该存储介质可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。该软件模块可以存储在移动终端的存储器中，也可以存储在可插入移动终端的存储卡中。例如，若设备(如移动终端)采用的是较大容量的MEGA-SIM卡或者大容量的闪存装置，则该软件模块可存储在该MEGA-SIM卡或者大容量的闪存装置中。
针对附图中描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，可以实现为用于执行本申请所描述功能的通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其它可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件或者其任意适当组合。针对附图描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，还可以实现为计算设备的组合，例如，DSP和微处理器的组合、多个微处理器、与DSP通信结合的一个或多个微处理器或者任何其它这种配置。
以上结合具体的实施方式对本申请进行了描述，但本领域技术人员应该清楚，这些描述都是示例性的，并不是对本申请保护范围的限制。本领域技术人员可以根据本申请的精神和原理对本申请做出各种变型和修改，这些变型和修改也在本申请的范围内。
关于本实施例公开的上述实施方式，还公开了如下的附记：
1.一种传输迁移管理方法，其中，IAB节点的IAB-DU与第一宿主集中单元(donor-CU)保持F1连接，在第二donor-CU的拓扑中已建立用于服务所述IAB节点的业务的资源，所述方法包括：
所述第一donor-CU向所述第二donor-CU发送针对所述业务的第一传输迁移修改请求；以及
所述第一donor-CU接收所述第二donor-CU发送的针对所述业务的传输迁移修改响应。
2.根据附记1所述的方法，其中，所述IAB节点的IAB-MT与所述第二donor-CU保持RRC连接，或者，所述IAB节点的IAB-MT与所述第一donor-CU保持RRC连接。
3.根据附记1或2所述的方法，其中，所述业务包括如下至少之一或组合：F1控制面(F1-C)业务、F1用户面(F1-U)业务、非F1业务。
4.根据附记1至3任一项所述的方法，其中，所述第一donor-CU向所述第二donor-CU发送用于请求修改在所述第二donor-CU拓扑中的服务所述业务的资源的第一传输迁移修改请求。
5.根据附记4所述的方法，其中，所述第一donor-CU通过第一传输迁移管理请求(TRANSPORT MIGRATION MANAGEMENT REQUEST)消息发送所述第一传输迁移修改请求。
6.根据附记4或5所述的方法，其中，所述第一传输迁移修改请求包括如下信息：所述业务的业务标识，所述业务的服务质量(QoS)和/或业务类型。
7.根据附记4至6任一项所述的方法，其中，所述第一donor-CU接收所述第二donor-CU发送的用于修改在所述第二donor-CU的拓扑中的服务所述业务的资源的传输迁移修改响应。
8.根据附记7所述的方法，其中，所述第一donor-CU通过传输迁移管理响应(TRANSPORT MIGRATION MANAGEMENT RESPONSE)消息接收所述传输迁移修改响应。
9.根据附记7或8所述的方法，其中，所述传输迁移修改响应包括如下信息：所述业务的业务标识，所述业务在第二donor-CU的拓扑中的BH信息。
10.根据附记9所述的方法，其中，所述在第二donor-CU的拓扑中的BH信息包括以下至少一项：
下行业务的入口路由标识(routing ID)；
下行业务的入口BH RLC信道；
下行业务的上一跳BAP地址；
下行业务的QoS映射信息。
11.根据附记9所述的方法，其中，所述在第二donor-CU的拓扑中的BH信息包括以下至少一项：
上行业务的出口路由标识(routing ID)；
上行业务的出口BH RLC信道；
上行业务的下一跳BAP地址。
12.根据附记1至11任一项所述的方法，其中，所述第一donor-CU接收所述针对所述业务的传输迁移修改响应后，所述方法还包括：
所述第一donor-CU更新所述业务的QoS映射信息。
13.根据附记1至12任一项所述的方法，其中，所述第一donor-CU接收所述针对所述业务的传输迁移修改响应后，所述方法还包括：
所述第一donor-CU向所述IAB节点配置更新所述业务的上行BH信息。
14.根据附记1至13任一项所述的方法，其中，所述第一donor-CU接收所述针对所述业务的传输迁移修改响应后，所述方法还包括：
所述第一donor-CU向所述IAB节点配置更新以下至少一项：上行方向的拓扑间的BAP头部重写信息、所述第二donor-CU的拓扑中的路由信息、上行方向的拓扑间的BH RLC信道映射信息。
15.根据附记1至13任一项所述的方法，其中，所述第一donor-CU接收所述针对所述业务的传输迁移修改响应后，所述方法还包括：
所述第一donor-CU向所述IAB节点配置更新以下至少一项：下行方向的拓扑间的BAP头部重写信息、下行方向的拓扑间的BH RLC信道映射信息。
16.根据附记1至15任一项所述的方法，其中，所述第一donor-CU向所述第二donor-CU发送用于请求修改针对所述IAB节点的IP地址的所述第一传输迁移修改请求。
17.根据附记16所述的方法，其中，所述第一传输迁移修改请求包含在第一传输迁移管理请求消息中。
18.根据附记16所述的方法，其中，所述第一传输迁移修改请求包括如下信息：IAB节点标识或IP地址请求索引，所述第一donor-CU的拓扑中的donor-DU的BAP地址。
19.根据附记18所述的方法，其中，所述第一传输迁移修改请求还包括：锚定于所述donor-DU的IP地址。
20.根据附记16至19任一项所述的方法，其中，所述第一donor-CU接收所述第二donor-CU发送的用于修改针对所述IAB节点的IP地址的传输迁移修改响应。
21.根据附记20所述的方法，其中，所述传输迁移修改响应包含在传输迁移管 理响应消息中。
22.根据附记20所述的方法，其中，所述传输迁移修改响应包括如下信息：IAB节点标识或IP地址请求索引，所述第一donor-CU的拓扑中的donor-DU的BAP地址以及锚定于所述第二donor-CU拓扑的donor-DU的IP地址。
23.根据附记20至22任一项所述的方法，其中，所述第一donor-CU接收所述针对IAB节点的传输迁移修改响应之后，所述方法还包括：
所述第一donor-CU向所述IAB节点配置锚定于所述第二donor-CU拓扑的donor-DU的IP地址。
24.根据附记4至6任一项所述的方法，其中，所述第一donor-CU接收所述第二donor-CU发送的用于拒绝针对所述业务的第一传输迁移修改请求的传输迁移修改响应。
25.根据附记24所述的方法，其中，所述第一donor-CU通过传输迁移管理响应消息接收所述传输迁移修改响应。
26.根据附记25所述的方法，其中，所述传输迁移管理响应消息包含所述业务的业务标识。
27.根据附记1至26任一项所述的方法，其中，在所述IAB节点的IAB-MT由所述第一donor-CU切换到所述第二donor-CU，并且所述第二donor-CU的拓扑中已建立用于服务所述IAB节点的一个或多个业务的资源的情况下，所述第一donor-CU发送针对所述一个或多个业务的第一传输迁移修改请求。
28.根据附记1至26任一项所述的方法，其中，在所述IAB节点的IAB-MT由所述第一donor-CU重建立到所述第二donor-CU，并且所述第二donor-CU的拓扑中已建立用于服务所述IAB节点的一个或多个业务的资源的情况下，所述第一donor-CU发送针对所述一个或多个业务的第一传输迁移修改请求。
29.根据附记1至26任一项所述的方法，其中，所述IAB节点的IAB-MT与所述第一donor-CU和所述第二donor-CU建立有双连接，在所述第二donor-CU的拓扑中已建立用于服务所述IAB节点的一个或多个业务的资源的情况下，所述第一donor-CU发送针对所述一个或多个业务的第一传输迁移修改请求。
30.一种传输迁移管理方法，其中，IAB节点的IAB-DU与第一宿主集中单元(donor-CU)保持F1连接，在第二donor-CU的拓扑中已建立用于服务所述IAB节点的业务的资源，所述方法包括：
所述第二donor-CU接收所述第一donor-CU发送的针对所述业务的第一传输迁移修改请求；以及
所述第二donor-CU向所述第一donor-CU发送针对所述业务的传输迁移修改响应。
31.根据附记30所述的方法，其中，所述IAB节点的IAB-MT与所述第二donor-CU保持RRC连接，或者，所述IAB节点的IAB-MT与所述第一donor-CU保持RRC连接。
32.根据附记30或31所述的方法，其中，所述业务包括如下至少之一或组合：F1控制面(F1-C)业务、F1用户面(F1-U)业务、非F1业务。
33.根据附记30至32任一项所述的方法，其中，所述第二donor-CU接收所述第一donor-CU发送的用于请求修改在所述第二donor-CU拓扑中的服务所述业务的资源的第一传输迁移修改请求。
34.根据附记33所述的方法，其中，所述第二donor-CU通过第一传输迁移管理请求(TRANSPORT MIGRATION MANAGEMENT REQUEST)消息接收所述第一传输迁移修改请求。
35.根据附记33或34所述的方法，其中，所述第一传输迁移修改请求包括如下信息：所述业务的业务标识，所述业务的服务质量(QoS)和/或业务类型。
36.根据附记30至35任一项所述的方法，其中，所述第二donor-CU在接收到所述第一传输迁移修改请求后，更新所述业务在所述第二donor-CU的拓扑中的路径上使用的回传(BH)无线链路控制(RLC)信道和/或BAP子层路由，或者更新所述业务的QoS映射信息。
37.根据附记30至36任一项所述的方法，其中，所述第二donor-CU在接收到所述第一传输迁移修改请求后，更新所述业务的上行BH信息；其中，所述上行BH信息包括路由标识、上行BH RLC信道和/或下一跳节点的BAP地址。
38.根据附记30至36任一项所述的方法，其中，所述第二donor-CU在接收到所述第一传输迁移修改请求后，更新所述业务的上行出口(egress)路由标识、出口BH RLC信道和/或下一跳节点的BAP地址；
或者，更新所述业务的下行入口(ingress)路由标识、入口BH RLC信道和/或上一跳节点的BAP地址。
39.根据附记33至38任一项所述的方法，其中，所述第二donor-CU向所述第一donor-CU发送用于修改在所述第二donor-CU的拓扑中的服务所述业务的资源的传 输迁移修改响应。
40.根据附记39所述的方法，其中，所述第二donor-CU通过传输迁移管理响应(TRANSPORT MIGRATION MANAGEMENT RESPONSE)消息发送所述传输迁移修改响应。
41.根据附记39或40所述的方法，其中，所述传输迁移修改响应包括如下信息：所述业务的业务标识，所述业务在第二donor-CU的拓扑中的BH信息。
42.根据附记41所述的方法，其中，所述在第二donor-CU的拓扑中的BH信息包括以下至少一项：
下行业务的入口路由标识(routing ID)；
下行业务的入口BH RLC信道；
下行业务的上一跳BAP地址；
下行业务的QoS映射信息。
43.根据附记41所述的方法，其中，所述在第二donor-CU的拓扑中的BH信息包括以下至少一项：
上行业务的出口路由标识(routing ID)；
上行业务的出口BH RLC信道；
上行业务的下一跳BAP地址。
44.根据附记30至43任一项所述的方法，其中，所述第二donor-CU接收所述第一donor-CU发送的用于请求修改针对所述IAB节点的IP地址的第一传输迁移修改请求。
45.根据附记44所述的方法，其中，所述第一传输迁移修改请求包含在第一传输迁移管理请求消息中。
46.根据附记44所述的方法，其中，所述第一传输迁移修改请求包括如下信息：IAB节点标识或IP地址请求索引，所述第一donor-CU的拓扑中的donor-DU的BAP地址。
47.根据附记46所述的方法，其中，所述第一传输迁移修改请求还包括：锚定于所述donor-DU的IP地址。
48.根据附记44至47任一项所述的方法，其中，所述第二donor-CU向所述第一donor-CU发送用于修改针对所述IAB节点的IP地址的传输迁移修改响应。
49.根据附记48所述的方法，其中，所述传输迁移修改响应包含在传输迁移管 理响应消息中。
50.根据附记48所述的方法，其中，所述传输迁移修改响应包括如下信息：IAB节点标识或IP地址请求索引，所述第一donor-CU的拓扑中的donor-DU的BAP地址以及锚定于所述第二donor-CU拓扑的donor-DU的IP地址。
51.根据附记33至35任一项所述的方法，其中，所述第二donor-CU在接收到所述第一传输迁移修改请求后，拒绝针对所述业务的第一传输迁移修改请求。
52.根据附记51所述的方法，其中，所述第二donor-CU向所述第一donor-CU发送用于拒绝针对所述业务的传输迁移修改请求的传输迁移修改响应。
53.根据附记52所述的方法，其中，所述第二donor-CU通过传输迁移管理消息发送所述传输迁移修改响应。
54.根据附记52所述的方法，其中，所述传输迁移修改响应包含所述业务的业务标识。
55.一种传输迁移管理方法，其中，IAB节点的IAB-DU与第一donor-CU保持F1连接，在第二donor-CU的拓扑中已建立用于服务所述IAB节点的业务的资源，所述方法包括：
所述第二donor-CU向所述第一donor-CU发送针对业务的第二传输迁移修改请求；以及
所述第二donor-CU修改在所述第二donor-CU的拓扑中的服务所述业务的资源。
56.根据附记55所述的方法，其中，所述第二donor-CU向所述第一donor-CU发送用于修改所述业务在所述第二donor-CU的拓扑中的路由标识(routing ID)和/或BH RLC信道的所述第二传输迁移修改请求。
57.根据附记56所述的方法，其中，所述第二donor-CU通过第二传输迁移管理请求(TRANSPORT MIGRATION MANAGEMENT REQUEST)消息发送所述第二传输迁移修改请求。
58.根据附记56或57所述的方法，其中，所述第二传输迁移修改请求包括如下信息：
所述业务的业务标识；
所述业务在第二donor-CU的拓扑中的BH信息。
59.根据附记58所述的方法，其中，所述在第二donor-CU的拓扑中的BH信息包括以下至少一项：
上行业务的出口路由标识(routing ID)；
上行业务的出口BH RLC信道；
上行业务的下一跳BAP地址。
60.根据附记58所述的方法，其中，所述在第二donor-CU的拓扑中的BH信息包括以下至少一项：
下行业务的入口路由标识(routing ID)；
下行业务的入口BH RLC信道；
下行业务的上一跳BAP地址。
61.根据附记55至60任一项所述的方法，其中，所述第二donor-CU修改在所述第二donor-CU的拓扑中的服务所述业务的资源，包括：
所述第二donor-CU更新所述业务在所述第二donor-CU的拓扑中的路径上使用的BH RLC信道和/或BAP子层路由。
62.根据附记55至61任一项所述的方法，其中，所述第二donor-CU修改在所述第二donor-CU的拓扑中的服务所述业务的资源，包括：
所述第二donor-CU更新所述业务的上行BH信息；其中，所述上行BH信息包括路由标识，上行BH RLC信道和/或下一跳节点的BAP地址。
63.根据附记55至62任一项所述的方法，其中，所述第二donor-CU修改在所述第二donor-CU的拓扑中的服务所述业务的资源，包括：
所述第二donor-CU更新所述业务的上行出口(egress)路由标识、出口BH RLC信道和/或下一跳节点的BAP地址；
或者，更新所述业务的下行入口(ingress)路由标识、入口BH RLC信道和/或上一跳节点的BAP地址。
64.根据附记55至63任一项所述的方法，其中，所述第二donor-CU向所述第一donor-CU发送用于修改针对所述IAB节点的IP地址的第二传输迁移修改请求。
65.根据附记64所述的方法，其中，所述第二传输迁移修改请求包含在第二传输迁移管理请求消息中。
66.根据附记64所述的方法，其中，所述第二传输迁移修改请求包括如下信息：IAB节点标识或IP地址请求索引，所述第一donor-CU的拓扑中的donor-DU的BAP地址或所述第二donor-CU的拓扑中的donor-DU的BAP地址，以及锚定于所述第二donor-CU拓扑中的donor-DU的IP地址。
67.根据附记55至66任一项所述的方法，其中，在所述IAB节点的IAB-MT由所述第一donor-CU切换到所述第二donor-CU，并且所述第二donor-CU的拓扑中已建立用于服务所述IAB节点的一个或多个业务的资源的情况下，所述第二donor-CU发送针对所述一个或多个业务的第二传输迁移修改请求。
68.根据附记55至66任一项所述的方法，其中，在所述IAB节点的IAB-MT由所述第一donor-CU重建立到所述第二donor-CU，并且所述第二donor-CU的拓扑中已建立用于服务所述IAB节点的一个或多个业务的资源的情况下，所述第二donor-CU发送针对所述一个或多个业务的第二传输迁移修改请求。
69.根据附记55至66任一项所述的方法，其中，所述IAB节点的IAB-MT与所述第一donor-CU和所述第二donor-CU建立有双连接，在所述第二donor-CU的拓扑中已建立用于服务所述IAB节点的一个或多个业务的资源的情况下，所述第二donor-CU发送针对所述一个或多个业务的第二传输迁移修改请求。
70.一种传输迁移管理方法，其中，IAB节点的IAB-DU与第一donor-CU保持F1连接，在第二donor-CU的拓扑中已建立用于服务所述IAB节点的业务的资源，所述方法包括：
所述第一donor-CU接收所述第二donor-CU发送的针对业务的第二传输迁移修改请求；其中，所述第二donor-CU修改在所述第二donor-CU的拓扑中的服务所述业务的资源。
71.根据附记70所述的方法，其中，所述第一donor-CU接收所述第二donor-CU发送的用于修改所述业务在所述第二donor-CU的拓扑中的路由标识(routing ID)和/或BH RLC信道的所述第二传输迁移修改请求。
72.根据附记71所述的方法，其中，所述第一donor-CU通过第二传输迁移管理请求(TRANSPORT MIGRATION MANAGEMENT REQUEST)消息接收所述第二传输迁移修改请求。
73.根据附记71或72所述的方法，其中，所述第二传输迁移修改请求包括如下信息：
所述业务的业务标识；
所述业务在第二donor-CU的拓扑中的BH信息。
74.根据附记73所述的方法，其中，所述在第二donor-CU的拓扑中的BH信息包括以下至少一项：
上行业务的出口路由标识(routing ID)；
上行业务的出口BH RLC信道；
上行业务的下一跳BAP地址。
75.根据附记73所述的方法，其中，所述在第二donor-CU的拓扑中的BH信息包括以下至少一项：
下行业务的入口路由标识(routing ID)；
下行业务的入口BH RLC信道；
下行业务的上一跳BAP地址。
76.根据附记71至75任一项所述的方法，其中，所述第一donor-CU在接收到针对所述业务的第二传输迁移修改请求后，所述方法还包括：
所述第一donor-CU向所述IAB节点配置更新所述业务的上行BH信息。
77.根据附记71至76任一项所述的方法，其中，所述第一donor-CU在接收到针对所述业务的第二传输迁移修改请求后，所述方法还包括：
所述第一donor-CU向所述IAB节点配置更新以下至少一项：上行方向的拓扑间的BAP头部重写信息、所述第二donor-CU的拓扑中的路由信息、上行方向的拓扑间的BH RLC信道映射信息。
78.根据附记71至77任一项所述的方法，其中，所述第一donor-CU在接收到针对所述业务的第二传输迁移修改请求后，所述方法还包括：
所述第一donor-CU向所述IAB节点配置更新以下至少一项：下行方向的拓扑间的BAP头部重写信息、下行方向的拓扑间的BH RLC信道映射信息。
79.根据附记70至78任一项所述的方法，其中，所述第一donor-CU接收所述第二donor-CU发送的用于修改针对所述IAB节点的IP地址的所述第二传输迁移修改请求。
80.根据附记79所述的方法，其中，所述第二传输迁移修改请求包含在第二传输迁移管理请求消息中。
81.根据附记79所述的方法，其中，所述第二传输迁移修改请求包括如下信息：IAB节点标识或IP地址请求索引，所述第一donor-CU的拓扑中的donor-DU的BAP地址或者所述第二donor-CU的拓扑中的donor-DU的BAP地址，以及锚定于所述第二donor-CU拓扑中的donor-DU的IP地址。
82.根据附记79至81任一项所述的方法，其中，所述方法还包括：
所述第一donor-CU向所述IAB节点配置锚定于所述第二donor-CU拓扑中的donor-DU的IP地址。
83.一种IAB宿主(donor)设备，包括存储器和处理器，所述存储器存储有计算机程序，其中，所述处理器被配置为执行所述计算机程序而实现如附记1至82任一项所述的传输迁移管理方法。

Claims (20)

  1. 一种集成的接入和回传IAB宿主设备，其中，IAB节点的IAB-DU与第一宿主集中单元保持F1连接，在第二宿主集中单元的拓扑中已建立用于服务所述IAB节点的业务的资源，所述设备包括：
    发送部，其向所述第二宿主集中单元发送针对所述业务的第一传输迁移修改请求；以及
    接收部，其接收所述第二宿主集中单元发送的针对所述业务的传输迁移修改响应。
  2. 根据权利要求1所述的设备，其中，所述IAB节点的IAB-MT与所述第二宿主集中单元保持无线资源控制连接，或者，所述IAB节点的IAB-MT与所述第一宿主集中单元保持无线资源控制连接；
    所述业务包括如下至少之一或组合：F1控制面业务、F1用户面业务、非F1业务。
  3. 根据权利要求1所述的设备，其中，所述发送部向所述第二宿主集中单元发送用于请求修改在所述第二宿主集中单元拓扑中的服务所述业务的资源的第一传输迁移修改请求；
    其中，通过第一传输迁移管理请求消息发送所述第一传输迁移修改请求。
  4. 根据权利要求3所述的设备，其中，所述接收部接收所述第二宿主集中单元发送的用于修改在所述第二宿主集中单元的拓扑中的服务所述业务的资源的传输迁移修改响应；
    其中，通过传输迁移管理响应消息接收所述传输迁移修改响应。
  5. 根据权利要求4所述的设备，其中，所述第一传输迁移修改请求包括如下信息：所述业务的业务标识，所述业务的服务质量和/或业务类型；
    所述传输迁移修改响应包括如下信息：所述业务的业务标识，所述业务在第二宿主集中单元的拓扑中的回传信息。
  6. 根据权利要求5所述的设备，其中，所述在第二宿主集中单元的拓扑中的回传信息包括以下至少一项：
    下行业务的入口路由标识；
    下行业务的入口回传无线链路控制信道；
    下行业务的上一跳回传自适应协议地址；
    下行业务的服务质量映射信息。
  7. 根据权利要求5所述的设备，其中，所述在第二宿主集中单元的拓扑中的回传信息包括以下至少一项：
    上行业务的出口路由标识；
    上行业务的出口回传无线链路控制信道；
    上行业务的下一跳回传自适应协议地址。
  8. 根据权利要求1所述的设备，其中，所述设备还包括：
    处理部，其执行如下至少之一的操作：
    更新所述业务的服务质量映射信息；
    向所述IAB节点配置更新所述业务的上行BH信息；
    向所述IAB节点配置更新以下至少一项：上行方向的拓扑间的回传自适应协议头部重写信息、所述第二宿主集中单元的拓扑中的路由信息、上行方向的拓扑间的回传无线链路控制信道映射信息；
    向所述IAB节点配置更新以下至少一项：下行方向的拓扑间的回传自适应协议头部重写信息、下行方向的拓扑间的回传无线链路控制信道映射信息。
  9. 根据权利要求8所述的设备，其中，所述发送部还向所述第二宿主集中单元发送用于请求修改针对所述IAB节点的IP地址的第一传输迁移修改请求。
  10. 根据权利要求9所述的设备，其中，所述第一传输迁移修改请求包含在第一传输迁移管理请求消息中；
    所述第一传输迁移修改请求包括如下至少之一的信息：IAB节点标识或IP地址请求索引，所述第一宿主集中单元的拓扑中的宿主分布单元的回传自适应协议地址，锚定于所述宿主分布单元的IP地址。
  11. 根据权利要求9所述的设备，其中，所述接收部还接收所述第二宿主集中单元发送的用于修改针对所述IAB节点的IP地址的传输迁移修改响应。
  12. 根据权利要求11所述的设备，其中，所述传输迁移修改响应包含在传输迁移管理响应消息中；
    所述传输迁移修改响应包括如下信息：IAB节点标识或IP地址请求索引，所述第一宿主集中单元的拓扑中的宿主分布单元的回传自适应协议地址以及锚定于所述第二宿主集中单元拓扑的宿主分布单元的IP地址。
  13. 根据权利要求11所述的设备，其中，所述处理部向所述IAB节点配置锚定于所述第二宿主集中单元拓扑中的宿主分布单元的IP地址。
  14. 根据权利要求3所述的设备，其中，所述接收部还接收所述第二宿主集中单元发送的用于拒绝针对所述业务的第一传输迁移修改请求的传输迁移修改响应；
    其中，通过传输迁移管理响应消息接收所述传输迁移修改响应，所述传输迁移管理响应消息包含所述业务的业务标识。
  15. 根据权利要求1所述的设备，其中，在所述IAB节点的IAB-MT由所述第一宿主集中单元切换到所述第二宿主集中单元，并且所述第二宿主集中单元的拓扑中已建立用于服务所述IAB节点的一个或多个业务的资源的情况下，所述发送部发送针对所述一个或多个业务的第一传输迁移修改请求；
    或者，在所述IAB节点的IAB-MT由所述第一宿主集中单元重建立到所述第二宿主集中单元，并且所述第二宿主集中单元的拓扑中已建立用于服务所述IAB节点的一个或多个业务的资源的情况下，所述发送部发送针对所述一个或多个业务的第一传输迁移修改请求；
    或者，所述IAB节点的IAB-MT与所述第一宿主集中单元和所述第二宿主集中单元建立有双连接，在所述第二宿主集中单元的拓扑中已建立用于服务所述IAB节点的一个或多个业务的资源的情况下，所述发送部发送针对所述一个或多个业务的第一传输迁移修改请求。
  16. 一种集成的接入和回传IAB宿主设备，其中，IAB节点的IAB-DU与第一宿主集中单元保持F1连接，在第二宿主集中单元的拓扑中已建立用于服务所述IAB节点的业务的资源，所述设备包括：
    发送部，其向所述第一宿主集中单元发送针对业务的第二传输迁移修改请求；以及
    处理部，其修改在所述第二宿主集中单元的拓扑中的服务所述业务的资源。
  17. 根据权利要求16所述的设备，其中，所述发送部向所述第一宿主集中单元发送用于修改所述业务在所述第二宿主集中单元的拓扑中的路由标识和/或回传无线链路控制信道的所述第二传输迁移修改请求；
    其中，通过第二传输迁移管理请求消息发送所述第二传输迁移修改请求。
  18. 根据权利要求16所述的设备，其中，所述处理部执行如下至少之一的操作：
    更新所述业务在所述第二宿主集中单元的拓扑中的路径上使用的回传无线链路控制信道和/或回传自适应协议子层路由；
    更新所述业务的上行回传信息；其中，所述上行回传信息包括路由标识，上行回传无线链路控制信道和/或下一跳节点的回传自适应协议地址；
    更新所述业务的上行出口路由标识、出口回传无线链路控制信道和/或下一跳节点的回传自适应协议地址；或者，更新所述业务的下行入口路由标识、入口回传无线链路控制信道和/或上一跳节点的回传自适应协议地址。
  19. 根据权利要求16所述的设备，其中，所述发送部还向所述第一宿主集中单元发送用于修改针对所述IAB节点的IP地址的第二传输迁移修改请求；
    其中，所述第二传输迁移修改请求包含在第二传输迁移管理请求消息中。
  20. 一种集成的接入和回传IAB系统，包括第一宿主集中单元和第二宿主集中单元；
    所述第一宿主集中单元发送针对业务的第一传输迁移修改请求，以及接收针对所述业务的传输迁移修改响应；所述第二宿主集中单元接收所述第一传输迁移修改请求，以及发送所述传输迁移修改响应；
    或者，
    所述第二宿主集中单元发送针对业务的第二传输迁移修改请求，以及修改在所述第二宿主集中单元的拓扑中的服务所述业务的资源；所述第一宿主集中单元接收所述第二传输迁移修改请求。
PCT/CN2022/075878 2022-02-10 2022-02-10 Iab宿主设备以及传输迁移管理方法 WO2023150974A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/075878 WO2023150974A1 (zh) 2022-02-10 2022-02-10 Iab宿主设备以及传输迁移管理方法

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/075878 WO2023150974A1 (zh) 2022-02-10 2022-02-10 Iab宿主设备以及传输迁移管理方法

Publications (1)

Publication Number Publication Date
WO2023150974A1 true WO2023150974A1 (zh) 2023-08-17

Family

ID=87563426

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/075878 WO2023150974A1 (zh) 2022-02-10 2022-02-10 Iab宿主设备以及传输迁移管理方法

Country Status (1)

Country Link
WO (1) WO2023150974A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113556794A (zh) * 2020-04-23 2021-10-26 华为技术有限公司 通信方法、装置及系统
CN113873587A (zh) * 2020-06-30 2021-12-31 华为技术有限公司 一种用于iab网络通信的方法及相关设备
WO2022019825A1 (en) * 2020-07-24 2022-01-27 Telefonaktiebolaget Lm Ericsson (Publ) Handling of buffered traffic during inter-cu migration of an integrated access backhaul (iab) node
WO2022021300A1 (en) * 2020-07-31 2022-02-03 Zte Corporation Methods and devices for enhancing mobility robustness to integrated access and backhaul for new radio

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113556794A (zh) * 2020-04-23 2021-10-26 华为技术有限公司 通信方法、装置及系统
CN113873587A (zh) * 2020-06-30 2021-12-31 华为技术有限公司 一种用于iab网络通信的方法及相关设备
WO2022019825A1 (en) * 2020-07-24 2022-01-27 Telefonaktiebolaget Lm Ericsson (Publ) Handling of buffered traffic during inter-cu migration of an integrated access backhaul (iab) node
WO2022021300A1 (en) * 2020-07-31 2022-02-03 Zte Corporation Methods and devices for enhancing mobility robustness to integrated access and backhaul for new radio

Similar Documents

Publication Publication Date Title
US10893459B2 (en) Wireless base station, first wireless control apparatus, second wireless control apparatus, and wireless apparatus
WO2022082601A1 (en) Method and apparatus for inter-donor mobility
US20230254922A1 (en) Multipath transmission method and communication apparatus
US20230362779A1 (en) Communication method and related device
US20230370898A1 (en) Communication method and apparatus
US20230199885A1 (en) Signaling exchange schemes in wireless communications
CN113728676A (zh) 在集成接入和回程网络中的子节点处和父节点处的资源对准
US20220182910A1 (en) Data Processing Method, Apparatus, And System
WO2023150974A1 (zh) Iab宿主设备以及传输迁移管理方法
WO2023150976A1 (zh) Iab宿主设备以及传输迁移管理方法
WO2023150975A1 (zh) Iab宿主设备以及传输迁移回退方法
WO2023130232A1 (zh) Iab节点设备、iab宿主设备以及路径迁移方法
WO2023130231A1 (zh) Iab节点设备、iab宿主设备以及拓扑退行方法
WO2023197184A1 (zh) Iab宿主设备以及传输地址配置方法
WO2024026803A1 (zh) 移动节点的配置方法和宿主设备
WO2024026804A1 (zh) 移动节点的配置方法、移动节点和宿主设备
WO2023184542A1 (zh) 配置信息的方法、装置和通信系统
WO2023197185A1 (zh) Iab节点设备、iab宿主设备以及传输地址确定方法
WO2023010364A1 (zh) 集成的接入和回传的通信装置以及方法
WO2022236644A1 (zh) 发送和接收信号的方法、装置和通信系统
WO2022205251A1 (zh) 信息收发方法，数据发送方法以及装置
WO2023065180A1 (zh) 路由方法、装置和系统
WO2023197105A1 (zh) 配置信息的方法、装置和通信系统
WO2023060401A1 (zh) 无线路由方法及装置
WO2023130260A1 (zh) Rrc消息的配置方法、装置和系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22925336

Country of ref document: EP

Kind code of ref document: A1