[go: up one dir, main page]

WO2023150975A1 - Dispositif donneur d'iab et procédé de transmission et de retour en arrière de la migration - Google Patents

Dispositif donneur d'iab et procédé de transmission et de retour en arrière de la migration Download PDF

Info

Publication number
WO2023150975A1
WO2023150975A1 PCT/CN2022/075879 CN2022075879W WO2023150975A1 WO 2023150975 A1 WO2023150975 A1 WO 2023150975A1 CN 2022075879 W CN2022075879 W CN 2022075879W WO 2023150975 A1 WO2023150975 A1 WO 2023150975A1
Authority
WO
WIPO (PCT)
Prior art keywords
donor
iab
migration
topology
node
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2022/075879
Other languages
English (en)
Chinese (zh)
Inventor
路杨
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Fujitsu Ltd
Original Assignee
Fujitsu Ltd
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 Fujitsu Ltd filed Critical Fujitsu Ltd
Priority to PCT/CN2022/075879 priority Critical patent/WO2023150975A1/fr
Publication of WO2023150975A1 publication Critical patent/WO2023150975A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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.
  • the inventors have found that after migrating the traffic of a migrating node and its child nodes from the network topology of the first donor-CU to the network topology of the second donor-CU, it is possible to transfer from the second donor-CU
  • the network topology of the first donor-CU is then migrated back to the network topology of the first donor-CU, which may be referred to as topology regression or transmission migration regression.
  • the service transmission paths of the migrated nodes and sub-nodes need to be migrated back to the network topology of the first donor-CU.
  • embodiments of the present application provide an IAB host device and a transmission migration rollback method.
  • a transmission migration fallback method wherein the IAB-DU of the IAB node maintains an F1 connection with the first donor central unit (donor-CU), and the topology of the second donor-CU has Establishing resources for serving the business of the IAB node, the method comprising:
  • the first donor-CU sends a transmission migration fallback request to the second donor-CU, and the transmission migration fallback request is used to trigger migration of one or more services to the first donor-CU topology;
  • the first donor-CU receives the transmission migration fallback response 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 the topology of the second donor-CU has established Resources for serving the business of the IAB node, the device includes:
  • a sending unit which sends a transmission migration fallback request to the second donor-CU, where the transmission migration fallback request is used to trigger migration of one or more services to the topology of the first donor-CU;
  • a receiving unit configured to receive the transmission migration fallback response sent by the second donor-CU.
  • a transmission migration fallback method 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 for service
  • the resource of the service of the IAB node includes:
  • the second donor-CU receives a transmission migration fallback request sent by the first donor-CU, and the transmission migration fallback request is used to trigger the migration of one or more services to the first donor-CU topology;
  • the second donor-CU sends a transmission migration fallback response 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 the The service resource of the IAB node, the device includes:
  • a receiving unit which receives a transmission migration fallback request sent by the first donor-CU, where the transmission migration fallback request is used to trigger the migration of one or more services to the topology of the first donor-CU; as well as
  • a sending unit which sends a transmission migration fallback response to the first donor-CU.
  • an IAB system including:
  • a first host centralized unit which sends a transmission migration fallback request, the transmission migration fallback request is used to trigger the migration of one or more services to the topology of the first host centralized unit; and receives a transmission migration fallback response;
  • the second host centralization unit receives the transmission migration fallback request; and sends the transmission migration fallback response.
  • One of the beneficial effects of the embodiments of the present application is that: when the IAB-DU of the IAB node maintains an F1 connection with the first donor-CU, the topology of the second donor-CU has been established to serve the IAB node When there are resources of the business, the first donor-CU sends a transmission migration fallback request to the second donor-CU, and the transmission migration fallback request is used to trigger the migration of one or more services to the topology of the first donor-CU; And the first donor-CU receives the transmission migration fallback response sent by the second donor-CU.
  • the transmission paths of some or all services can be Migrating back to the topology of the first donor-CU enables the network side to continue serving the service through resources in the topology of the first donor-CU, so as to avoid service interruption or data being discarded.
  • 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 rollback according to an embodiment of the present application.
  • FIG. 10 is another example diagram of transmission migration rollback according to the embodiment of the present application.
  • FIG. 11 is a schematic diagram of a transmission migration fallback method according to an embodiment of the present application.
  • FIG. 12 is a signaling flow chart of transmission migration rollback according to an embodiment of the present application.
  • FIG. 13 is another signaling flowchart of transmission migration rollback according to the embodiment of the present application.
  • FIG. 14 is another schematic diagram of the transmission migration fallback method according to the embodiment of the present application.
  • FIG. 15 is a schematic diagram of an IAB host device according to an embodiment of the present application.
  • FIG. 16 is another schematic diagram of an IAB host device according to an embodiment of the present application.
  • FIG. 17 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 data packet header (header) of the uplink service according to the uplink BH information and selects the BH RLC channel and the next hop node for the 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 (migrating node) can be transferred from The parent node served by the source donor-CU (also called F1-terminating CU or the first donor-CU) is switched or re-established to the target donor-CU (also called non-F1-terminating CU or the second donor-CU ) service, it is necessary to migrate all the business of IAB-node (and the business of its child 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 restores 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 uplink service of the child node in the donor-CU 2 topology, the boundary node needs to replace the routing ID of the uplink service belonging to the topology of donor-CU 1 (the destination address is the donor-DU BAP address of donor-CU 1) with 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 business of the child node in the topology of donor-CU 2, the boundary node transfers the downlink traffic belonging to the donor - The routing ID of the topology of CU 2 (the destination address is the donor-DU BAP address of donor-CU 2) is replaced by 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 rollback according to an embodiment of the present application
  • FIG. 10 is another schematic diagram of transmission migration rollback according to an embodiment of the present application.
  • the IAB-MT of IAB node 3 migrates from donor-CU 1 to donor-CU 2.
  • the IAB-MT of IAB node 3 migrates from donor-CU 2 back to donor-CU 1.
  • the IAB-MT of IAB node 3 migrates from donor-CU 1 to donor-CU 2. If the business of the child node is migrated to the donor-CU 2 topology, the network device will configure the routing ID mapping relationship between the topologies (such as BAP Header Rewriting Information) to the boundary node.
  • the topologies such as BAP Header Rewriting Information
  • the network device When the boundary node forwards uplink data to the parent node in the donor-CU 2 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 routing selection and BH based on the replaced routing ID RLC channel selection, so the network device will configure the routing table of the topology belonging to the donor-CU 2 for the boundary node (only the routing table of the donor-CU 1 topology is configured in the boundary node before the switchover) and from the topology of the donor-CU 1 to the donor-CU 1 Uplink BH RLC channel mapping table for CU 2 topology.
  • 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 . If the business of the boundary node is migrated to the donor-CU 2 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.
  • routing ID routing ID
  • the uplink backhaul RLC channel ID the next Hop node address
  • the transmission of some or all services is migrated to the donor-CU 2 topology, resources for serving the service need to be established in the topology of donor-CU 2, for example, the service is configured to be used on the path in the topology of donor-CU1 Backhaul BH RLC channel and/or BAP sublayer routing.
  • 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 fallback method, which is described from the perspective of the 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. 11 is a schematic diagram of a transmission migration rollback method according to an embodiment of the present application. As shown in Figure 11, the method includes:
  • the first donor-CU sends a transmission migration fallback request to the second donor-CU, where the transmission migration fallback request is used to trigger migration of one or more services to the topology of the first donor-CU;
  • the first donor-CU receives a transmission migration fallback response sent by the second donor-CU.
  • FIG. 11 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. 11 .
  • 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 IAB-MT of the IAB node migrates from the first donor-CU to the second donor-CU
  • the IAB-MT of the IAB node migrates from the second donor-CU back to the first donor-CU.
  • the migration of the IAB-MT of the IAB node from the first donor-CU to the second donor-CU includes, for example: switching the IAB-MT of the IAB node from the first donor-CU to the second donor-CU, or switching from the first donor-CU to the second donor-CU.
  • the CU re-establishes an RRC connection to the second donor-CU, or establishes a dual connection with the second donor-CU.
  • the migration of the IAB-MT of the IAB node from the second donor-CU back to the first donor-CU includes, for example: switching from the second donor-CU or re-establishing an RRC connection to 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 transmission migration rollback request is sent through a UE context acquisition request (RETRIEVE UE CONTEXT REQUEST) message
  • the transmission migration rollback response is sent through a UE context acquisition response (RETRIEVE UE CONTEXT RESPONSE) message.
  • RETRIEVE UE CONTEXT REQUEST UE context acquisition request
  • RETRIEVE UE CONTEXT RESPONSE UE context acquisition response
  • the present application is not limited thereto, and what bears the transmission migration fallback request and/or the transmission migration fallback response may also be other messages.
  • the UE context acquisition request message includes indication information for releasing one or more services, or includes indication information for releasing all services.
  • the first donor-CU may explicitly indicate or implicitly request the transmission path rollback of one or more services.
  • the UE context acquisition response message is used to indicate that the backhaul (BH) radio link control (RLC) channel and/or BAP sublayer routing used by one or more services on the path in the topology of the second donor-CU has been released.
  • BH backhaul
  • RLC radio link control
  • the first donor-CU can be configured for the service in the first donor-CU A backhaul (BH) radio link control (RLC) channel and/or BAP sublayer routing is used on the path in the topology of a donor-CU.
  • BH backhaul
  • RLC radio link control
  • the first donor-CU may configure a BH RLC channel and/or a BAP sublayer route.
  • the first donor-CU may also configure and update uplink backhaul (BH) information of one or more services to the IAB node.
  • uplink backhaul (BH) information For example, for the uplink service of the IAB node migrated back to the first donor-CU, uplink backhaul (BH) information belonging to the first donor-CU topology is configured to the IAB node.
  • the uplink backhaul (BH) information includes, for example, the routing ID of the service, the BH RLC channel ID and the address of the next hop node.
  • the uplink backhaul (BH) information may be sent by the first donor-CU to the relocation node through an F1AP message or an RRC message.
  • the method may also include at least one of the following:
  • the first donor-CU configures and releases the BAP header rewriting information (BAP header rewriting information) between the topology of the first donor-CU and the topology of the second donor-CU to the IAB node;
  • the first donor-CU configures and releases BH RLC channel mapping information between the topology of the first donor-CU and the topology of the second donor-CU to the IAB node;
  • the first donor-CU configures and releases routing information in the topology of the second donor-CU to the IAB node.
  • the migration node After the service of the child node is migrated back to the first donor-CU, the migration node needs to release the configuration information between topologies.
  • the first donor-CU can configure and release BAP header rewriting information, release routing information, and release RLC channel mapping to the migration node.
  • One of the configurations may be any two, or all three configurations, and the present application is not limited thereto.
  • the uplink service of the child node migrated back to the first donor-CU configure and release the corresponding uplink BAP header rewriting information in the uplink direction, the routing information in the topology of the second donor-CU and the information from the first donor-CU to the migrated node.
  • RLC channel mapping information from the CU topology to the second donor-CU topology For example, for the uplink service of the child node migrated back to the first donor-CU, configure and release the corresponding uplink BAP header rewriting information in the uplink direction, the routing information in the topology of the second donor-CU and the information from the first donor-CU to the migrated node.
  • the downlink service of the child node migrated back to the first donor-CU configure and release the BAP header rewriting information in the corresponding downlink direction and the information from the second donor-CU topology to the first donor-CU topology to the migrated node.
  • RLC channel mapping information For another example, for the downlink service of the child node migrated back to the first donor-CU, configure and release the BAP header rewriting information in the corresponding downlink direction and the information from the second donor-CU topology to the first donor-CU topology to the migrated node.
  • the method may also include at least one of the following:
  • the first donor-CU adds routing information in the topology of the first donor-CU to the IAB node configuration
  • the first donor-CU configures and adds BH RLC channel mapping information in the topology of the first donor-CU to the IAB node.
  • routing information or BH RLC channel mapping information in the topology of the first donor-CU is added to the migration node configuration.
  • the first donor-CU configures the IP address of the donor-DU anchored to the first donor-CU for the IAB node (including the migration node and the child node); wherein, the IP address is used for the F1 user plane data, F1 control plane data or non-F1 data of the IAB node.
  • the donor-DU of the first donor-CU has the source IP address filtering function, it will discard the uplink data containing the IP address assigned by other donor-DUs.
  • the migration node needs to set the IP address carried in the uplink service as the IP address assigned by the donor-DU of the first donor-CU. Therefore, the first donor-CU configures the migration node with the IP address assigned by the donor-DU of the first donor-CU topology.
  • 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 routing ID of the child node's business (including uplink and downlink business) always belongs to the routing ID of the first donor-CU topology, but when the child node's business migrates back to the first donor-CU topology, it is anchored to the donor of the second donor-CU -
  • the IP address of the DU needs to be replaced with the IP address of the donor-DU anchored to the first donor-CU.
  • the child node selects the IP address to use according to the address of the donor-DU of the first donor-CU, so the configuration of the IP address of the service needs to be directed at the BAP address of the donor-DU of the first donor-CU, including adding anchors to The IP address of the donor-DU of the first donor-CU and the IP address of the donor-DU anchored to the second donor-CU.
  • the first donor-CU sends an RRC message to the IAB node (including a transition node and a child node) to configure the IP address of the donor-DU anchored to the first donor-CU to replace the anchor Configuration information about the IP address of the donor-DU of the second donor-CU.
  • Fig. 12 is a signaling flow chart of transmission migration rollback according to the embodiment of the present application, which exemplarily shows after the IAB-MT of the IAB node (boundary node) migrates to the non-F1-terminating CU (the second donor-CU) , and re-establish the RRC connection to the F1-terminating CU (the first donor-CU) after returning the link RLF from the non-F1-terminating CU (the second donor-CU), the case of performing transmission migration and fallback.
  • the migration node After the migration node detects the BH RLF, it sends an RRC connection re-establishment request to the second donor-CU.
  • the first donor-CU F1-terminating CU/source donor-CU
  • a UE context acquisition request RETRIEVE UE CONTEXT REQUEST
  • the transmission migration rollback of the request service RETRIEVE UE CONTEXT REQUEST
  • the first donor-CU may explicitly indicate or implicitly request service transmission migration rollback through the UE context acquisition request message.
  • the UE context acquisition request message may explicitly include an instruction to release all services (because if the first donor-CU is re-established, all services need to be transferred back).
  • the second donor-CU After the second donor-CU receives the UE context acquisition request message for the transition node, and learns that the transition node has accessed the first donor-CU, it sends a UE context acquisition response (RETRIEVE UE CONTEXT RESPONSE) message. Release the BH RLC channel and routing of the traffic on the path in the second donor-CU topology.
  • RETRIEVE UE CONTEXT RESPONSE UE context acquisition response
  • the first donor-CU After the first donor-CU receives the UE context acquisition response message, it considers that the second donor-CU has confirmed the transmission migration of the service and rolls back, then configures the BH RLC channel and route of the service on the path in the first donor-CU topology .
  • the first donor-CU configures the uplink BH information (including routing ID, BH RLC channel ID and downlink BH information belonging to the first donor-CU) for the migration node business (including user plane and non-user plane business) to the migration node through the F1AP message.
  • One-hop node address configure the IP address of the donor-DU anchored under the first donor-CU to the migration node and the child node through the RRC message.
  • the first donor-CU can configure and release the BAP header rewriting information between the topologies, the BH RLC channel mapping information between the topologies, and the routing information of the second donor-CU topology to the migration node.
  • the service transmission path falls back from the second donor-CU topology to the first donor-CU topology.
  • the transmission migration rollback request is sent through a transmission migration management request (TRANSPORT MIGRATION MANAGEMENT REQUEST) message
  • the transmission migration rollback response is sent through a transmission migration management response (TRANSPORT MIGRATION MANAGEMENT RESPONSE) message.
  • TRANSPORT MIGRATION MANAGEMENT REQUEST a transmission migration management request
  • TRANSPORT MIGRATION MANAGEMENT RESPONSE a transmission migration management response
  • the present application is not limited thereto, and what bears the transmission migration fallback request and/or the transmission migration fallback response may also be other messages.
  • the transmission migration management request message includes indication information for releasing one or more services, or includes indication information for releasing all services.
  • the first donor-CU may explicitly indicate or implicitly request transmission migration and rollback of one or more services.
  • the transport migration management response message is used to indicate that the backhaul (BH) radio link control (RLC) channel and/or BAP sublayer routing used by one or more services on the path in the topology of the second donor-CU has been terminated. released.
  • BH backhaul
  • RLC radio link control
  • the first donor-CU may configure a backhaul (BH) radio link control (RLC) channel and/or BAP used on paths in the topology of the first donor-CU for the traffic Sublayer routing.
  • BH backhaul
  • RLC radio link control
  • the first donor-CU may configure a BH RLC channel and/or a BAP sublayer route.
  • the first donor-CU may also configure and update uplink backhaul (BH) information of one or more services to the IAB node.
  • uplink backhaul (BH) information For example, for the uplink service of the IAB node migrated back to the first donor-CU, uplink backhaul (BH) information belonging to the first donor-CU topology is configured to the IAB node.
  • the uplink backhaul (BH) information includes, for example, the routing ID of the service, the BH RLC channel, and the BAP route.
  • the uplink backhaul (BH) information may be sent by the first donor-CU to the relocation node through an F1AP message or an RRC message.
  • the method may also include at least one of the following:
  • the first donor-CU configures and releases the BAP header rewriting information between the topology of the first donor-CU and the topology of the second donor-CU to the IAB node;
  • the first donor-CU configures and releases BH RLC channel mapping information between the topology of the first donor-CU and the topology of the second donor-CU to the IAB node;
  • the first donor-CU configures and releases routing information in the topology of the second donor-CU to the IAB node.
  • the migration node Since the service of the child node is migrated back to the first donor-CU1, the migration node no longer needs configuration information between topologies, and can be configured to release BAP header rewriting information, release routing information, and release RLC channel mapping configuration to the migration node.
  • One, any two, or all three configurations, the present application is not limited thereto.
  • the uplink service of the child node migrated back to the first donor-CU, it is necessary to release the corresponding uplink BAP header rewriting information, the routing information in the topology of the second donor-CU, and the topology from the first donor-CU to the RLC channel mapping information of the second donor-CU topology.
  • the method may also include at least one of the following:
  • the first donor-CU adds routing information in the topology of the first donor-CU to the IAB node configuration
  • the first donor-CU adds the BH RLC channel mapping information in the topology of the first donor-CU to the IAB node configuration.
  • the uplink and/or downlink services of the subnodes migrated back to the first donor-CU add routing information or BH RLC channel mapping information in the topology of the first donor-CU to the IAB node configuration.
  • the first donor-CU configures the IP address of the donor-DU anchored in the first donor-CU for the IAB node or the IAB node (including migration nodes and child nodes); wherein, the IP The address is used for F1 user plane data, F1 control plane data or non-F1 data of the IAB node.
  • the donor-DU of the first donor-CU has a source IP address filtering function, it will discard uplink data containing IP addresses allocated by other donor-DUs.
  • the migration node needs to configure the IP address carried by the uplink service as the IP address allocated by the donor-DU of the first donor-CU. Therefore, the first donor-CU configures the migration node with the IP address assigned by the donor-DU of the first donor-CU topology.
  • 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 routing ID of the child node's business (including uplink and downlink business) always belongs to the routing ID of the first donor-CU topology, but when the child node's business migrates back to the first donor-CU topology, it is anchored to the donor of the second donor-CU -
  • the IP address of the DU needs to be replaced with the IP address of the donor-DU anchored to the first donor-CU.
  • the child node selects the IP address to use according to the address of the donor-DU of the first donor-CU, so the configuration of the IP address of the service needs to be directed at the BAP address of the donor-DU of the first donor-CU, including adding anchors to The IP address of the donor-DU of the first donor-CU and the IP address of the donor-DU anchored to the second donor-CU.
  • the first donor-CU sends an RRC message to the IAB node (including a transition node and a child node) to configure the IP address of the donor-DU anchored to the first donor-CU to replace the anchor Configuration information about the IP address of the donor-DU of the second donor-CU.
  • Fig. 13 is another signaling flowchart of transmission migration rollback according to the embodiment of the present application, which exemplarily shows that the IAB-MT of the IAB node (boundary node) migrates to the non-F1-terminating CU (the second donor-CU) After that, when the link RLF is returned from the non-F1-terminating CU (the second donor-CU) and the RRC connection is re-established to the F1-terminating CU (the first donor-CU), the transmission migration is backed up.
  • the migration node After the migration node detects the BH RLF, it sends an RRC connection re-establishment request to the second donor-CU.
  • the first donor-CU acquires the context of the migrated node from the second donor-CU.
  • the migration node completes the RRC re-establishment process to the second donor-CU.
  • the first donor-CU (F1-terminating CU/source donor-CU) sends a transmission migration management request (IAB TRANSPORT MIGRATION MANAGEMENT REQUEST) message to the second donor-CU (non-F1-terminating CU/target donor-CU) , to request the transport migration rollback of the service.
  • a transmission migration management request IAB TRANSPORT MIGRATION MANAGEMENT REQUEST
  • the first donor-CU may explicitly instruct the rollback of the transmission path of the service through the IAB transmission migration management request message.
  • the IAB transmission migration management request message explicitly contains an instruction to release all services, or the IAB transmission migration management request message contains one or more service identifiers, and the release of all services is indicated by the identifier of each service .
  • the second donor-CU After receiving the transmission migration management request message, the second donor-CU knows that it needs to release the service or migrate the service transmission path back to the first donor-CU topology, and then sends a transmission migration management response (IAB TRANSPORT MIGRATION) to the first donor-CU MANAGEMENT RESPONSE) message. Release the BH RLC channels and routes on the path of the migrated node in the second donor-CU topology.
  • the first donor-CU After the first donor-CU receives the transmission migration management response message, it considers that the second donor-CU has confirmed the transmission migration of the service and rolls back, then configures the BH RLC channel and route of the service on the path in the first donor-CU topology .
  • the first donor-CU configures the uplink BH information (including routing ID, BH RLC channel ID and downlink BH information belonging to the first donor-CU) for the migration node business (including user plane and non-user plane business) to the migration node through the F1AP message.
  • One-hop node address configure the IP address of the donor-DU anchored under the first donor-CU to the migration node and the child node through the RRC message.
  • the first donor-CU can configure and release the BAP header rewriting information between the topologies, the BH RLC channel mapping information between the topologies, and the routing information of the second donor-CU topology to the migration node.
  • the service transmission path falls back from the second donor-CU topology to the first donor-CU topology.
  • the above signaling process 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 adjusted appropriately, for example, the step of sending the transmission migration management request message from the first donor-CU to the second donor-CU can be advanced after obtaining the context of the migration node from the second donor-CU.
  • some other operations may be added or some of them may 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 first donor-CU sends a transmission migration fallback request to the second donor-CU, and the transmission migration fallback request is used to trigger the migration of one or more services to the topology of the first donor-CU; and the first The donor-CU receives the transmission migration fallback response sent by the second donor-CU.
  • the transmission paths of some or all services can be Migrate back to the topology of the first donor-CU to avoid service interruption or data loss.
  • An embodiment of the present application provides a transmission migration rollback method, which is described from 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. 14 is another schematic diagram of the transmission migration fallback method according to the embodiment of the present application. As shown in Figure 14, the method includes:
  • the second donor-CU receives a transmission migration fallback request sent by the first donor-CU, where the transmission migration fallback request is used to trigger migration of one or more services to the topology of the first donor-CU;
  • the second donor-CU sends a transmission migration fallback response to the first donor-CU.
  • FIG. 14 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 description in FIG. 14 above.
  • 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 IAB-MT of the IAB node migrates from the first donor-CU to the second donor-CU
  • the IAB-MT of the IAB node migrates from the second donor-CU Return to the first donor-CU.
  • the migration of the IAB-MT of the IAB node from the first donor-CU to the second donor-CU includes, for example: switching the IAB-MT of the IAB node from the first donor-CU to the second donor-CU, or switching from the first donor-CU to the second donor-CU.
  • the CU re-establishes an RRC connection to the second donor-CU, or establishes a dual connection with the second donor-CU.
  • the migration of the IAB-MT of the IAB node from the second donor-CU back to the first donor-CU includes, for example: switching from the second donor-CU or re-establishing an RRC connection back to 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 transmission migration rollback request is sent through a UE context acquisition request (RETRIEVE UE CONTEXT REQUEST) message
  • the transmission migration rollback response is sent through a UE context acquisition response (RETRIEVE UE CONTEXT RESPONSE) message.
  • the UE context acquisition request message includes indication information for instructing release of one or more services, or, the UE context acquisition request message includes indication information for instructing release of all services.
  • the UE context acquisition response message is used to indicate the backhaul (BH) radio link control (RLC) channel used by one or more services on the path in the topology of the second donor-CU and/or BAP sublayer routing has been released.
  • BH backhaul
  • RLC radio link control
  • the transmission migration rollback request is sent through a transmission migration management request (TRANSPORT MIGRATION MANAGEMENT REQUEST) message
  • the transmission migration rollback response is sent through a transmission migration management response (TRANSPORT MIGRATION MANAGEMENT RESPONSE) message.
  • the transmission migration management request message includes indication information for instructing the release of one or more services, or, the transmission migration management request message includes indication information for instructing the release of all services.
  • the transport migration management response message is used to indicate the backhaul (BH) radio link control (RLC) channel used by one or more traffic on the path in the topology of the second donor-CU and/or BAP sublayer routing has been released.
  • BH backhaul
  • RLC radio link control
  • the second donor-CU releases backhaul (BH) radio link control (RLC) channels and / or BAP sublayer routing.
  • BH backhaul
  • RLC radio link control
  • the first donor-CU sends a transmission migration fallback request to the second donor-CU, and the transmission migration fallback request is used to trigger the migration of one or more services to the topology of the first donor-CU; and the first The donor-CU receives the transmission migration fallback response sent by the second donor-CU.
  • the transmission paths of some or all services can be Migrating back to the topology of the first donor-CU enables the network side to continue serving the service through resources in the topology of the first donor-CU, so as to avoid service interruption or data being discarded.
  • 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 may be, for example, the IAB donor-CU in the IAB system, or may be one or some components or components or modules configured in the IAB donor-CU.
  • FIG. 15 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 1500 includes:
  • the sending unit 1501 which sends a transmission migration fallback request to the second donor-CU, where the transmission migration fallback request is used to trigger the migration of one or more services to the topology of the first donor-CU; as well as
  • the receiving unit 1502 is configured to receive a transmission migration fallback response 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 IAB-MT of the IAB node migrates from the first donor-CU to the second donor-CU
  • the IAB-MT of the IAB node migrates from the second donor-CU Return to the first donor-CU.
  • the migration of the IAB-MT of the IAB node from the first donor-CU to the second donor-CU includes, for example: switching the IAB-MT of the IAB node from the first donor-CU to the second donor-CU, or switching from the first donor-CU to the second donor-CU.
  • the CU re-establishes an RRC connection to the second donor-CU, or establishes a dual connection with the second donor-CU.
  • the migration of the IAB-MT of the IAB node from the second donor-CU back to the first donor-CU includes, for example: switching from the second donor-CU or re-establishing an RRC connection back to 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 transmission migration fallback request is sent through a UE context acquisition request message
  • the transmission migration fallback response is sent through a UE context acquisition response message
  • the UE context acquisition request message includes indication information for releasing one or more services, or, the UE context acquisition request message includes indication information for releasing all services.
  • the UE context acquisition response message is used to indicate the backhaul radio link control channel and/or BAP used by the one or more services on the path in the topology of the second donor-CU Sublayer routing has been released.
  • the transmission migration fallback request is sent by a transmission migration management request message
  • the transmission migration fallback response is sent by a transmission migration management response message.
  • the transmission migration management request message includes indication information for instructing the release of one or more services, or, the transmission migration management request message includes indication information for instructing the release of all services.
  • the transmission migration management response message is used to indicate the backhaul radio link control channel and/or BAP used by the one or more services on the path in the topology of the second donor-CU Sublayer routing has been released.
  • the IAB host device 1500 further includes:
  • the processing unit 1503 configures, for the service, the backhaul radio link control channel and/or the BAP sublayer route used on the path in the topology of the first donor-CU.
  • the processing unit 1503 is further configured to: configure and update the uplink feedback information of the one or more services to the IAB node.
  • the processing unit 1503 also performs at least one of the following:
  • the processing unit 1503 also performs at least one of the following:
  • the processing unit 1503 is further configured to: configure the IP address of the donor-DU anchored to the first donor-CU for the IAB node; wherein the IP address is used for the IAB node F1 user plane data, F1 control plane data or non-F1 data.
  • the sending unit 1501 sends an RRC message to the IAB node for configuring the IP address of the donor-DU anchored in the first donor-CU to replace the IP address anchored in the second donor-CU The configuration information of the donor-DU's IP address.
  • the IAB host device 1500 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. 15 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 transmission migration fallback request to the second donor-CU, and the transmission migration fallback request is used to trigger the migration of one or more services to the topology of the first donor-CU; and the first The donor-CU receives the transmission migration fallback response sent by the second donor-CU.
  • the transmission paths of some or all services can be Migrate back to the topology of the first donor-CU to avoid service interruption or data loss.
  • 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 may be, for example, the IAB donor-CU in the IAB system, or may be one or some components or components or modules configured in the IAB donor-CU.
  • 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-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 1600 includes:
  • the receiving unit 1601 is configured to receive a transmission migration fallback request sent by the first donor-CU, where the transmission migration fallback request is used to trigger the migration of one or more services to the topology of the first donor-CU ;as well as
  • the sending unit 1602 which sends a transmission migration fallback response 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 IAB-MT of the IAB node migrates from the first donor-CU to the second donor-CU
  • the IAB-MT of the IAB node migrates from the second donor-CU Return to the first donor-CU.
  • the migration of the IAB-MT of the IAB node from the first donor-CU to the second donor-CU includes, for example: switching the IAB-MT of the IAB node from the first donor-CU to the second donor-CU, or switching from the first donor-CU to the second donor-CU.
  • the CU re-establishes an RRC connection to the second donor-CU, or establishes a dual connection with the second donor-CU.
  • the migration of the IAB-MT of the IAB node from the second donor-CU back to the first donor-CU includes, for example: switching from the second donor-CU or re-establishing an RRC connection back to 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 transmission migration rollback request is sent through a UE context acquisition request (RETRIEVE UE CONTEXT REQUEST) message
  • the transmission migration rollback response is sent through a UE context acquisition response (RETRIEVE UE CONTEXT RESPONSE) message.
  • the UE context acquisition request message includes indication information for instructing release of one or more services, or, the UE context acquisition request message includes indication information for instructing release of all services.
  • the UE context acquisition response message is used to indicate the backhaul (BH) radio link control (RLC) channel used by one or more services on the path in the topology of the second donor-CU and/or BAP sublayer routing has been released.
  • BH backhaul
  • RLC radio link control
  • the transmission migration rollback request is sent through a transmission migration management request (TRANSPORT MIGRATION MANAGEMENT REQUEST) message
  • the transmission migration rollback response is sent through a transmission migration management response (TRANSPORT MIGRATION MANAGEMENT RESPONSE) message.
  • the transmission migration management request message includes indication information for instructing the release of one or more services, or, the transmission migration management request message includes indication information for instructing the release of all services.
  • the transport migration management response message is used to indicate the backhaul (BH) radio link control (RLC) channel used by one or more traffic on the path in the topology of the second donor-CU and/or BAP sublayer routing has been released.
  • BH backhaul
  • RLC radio link control
  • the IAB host device 1600 further includes:
  • the processing unit 1603 which releases the backhaul (BH) radio link control (RLC) channel and/or BAP sublayer route used on the path in the topology of the second donor-CU for the one or more services .
  • BH backhaul
  • RLC radio link control
  • 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 transmission migration fallback request to the second donor-CU, and the transmission migration fallback request is used to trigger the migration of one or more services to the topology of the first donor-CU; and the first The donor-CU receives the transmission migration fallback response sent by the second donor-CU.
  • the transmission paths of some or all services can be Migrate back to the topology of the first donor-CU to avoid service interruption or data loss.
  • 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:
  • the first donor central unit (first donor-CU), which sends a transmission migration fallback request, and the transmission migration fallback request is used to trigger the migration of one or more services to the topology of the first donor central unit ; and receive transport migration fallback response;
  • a second donor central unit (second donor-CU), which receives the transmission migration fallback request; and sends the transmission migration fallback response.
  • 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).
  • an IAB device 1700 may include: a processor (such as a central processing unit CPU) 1701 and a memory 1702 ; the memory 1702 is coupled to the processor 1701 .
  • the memory 1702 can store various data; in addition, it also stores a program 1705 for information processing, and executes the program 1705 under the control of the central processing unit 1701 .
  • the processor 1701 may be configured to execute a program to implement the transmission migration rollback method in the embodiment of the first aspect.
  • the processor 1701 may be configured to perform the following control: send a transmission migration fallback request to the second donor-CU, where the transmission migration fallback request is used to trigger the migration of one or more of the services to the first donor - a topology of CUs; and the first donor-CU receives a transport migration fallback response sent by the second donor-CU.
  • the processor 1701 may be configured to execute a program to implement the transmission migration rollback method in the embodiment of the second aspect.
  • the processor 1701 may be configured to perform the following control: receive a transmission migration fallback request sent by the first donor-CU, where the transmission migration fallback request is used to trigger migration of one or more services to the The topology of the first donor-CU; and sending a transport migration fallback response to the first donor-CU.
  • the IAB device 1700 may further include: a transceiver 1703 and an antenna 1704 , etc.; where 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 1700 does not necessarily include all components shown in FIG. 17 ; in addition, the IAB device 1700 may also include components not shown in FIG. 17 , 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 first and second embodiments in the IAB device. return method.
  • the embodiment of the present application also provides a storage medium storing a computer-readable program, wherein the computer-readable program causes the computer to execute the transmission migration rollback method in the embodiments of the first aspect and the second aspect 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 fallback method 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 the IAB node resources of the business, the method includes:
  • the first donor-CU sends a transmission migration fallback request to the second donor-CU, and the transmission migration fallback request is used to trigger migration of one or more services to the first donor-CU topology;
  • the first donor-CU receives the transmission migration fallback response sent by the second donor-CU.
  • the UE context acquisition request message includes indication information for releasing one or more services, or the UE context acquisition request message includes indication information for releasing all services information.
  • the transmission migration management request message includes indication information for instructing the release of one or more services, or, the transmission migration management request message includes indication information for instructing the release of all services instructions for the .
  • the transmission migration management response message is used to indicate the backhaul (BH) used by the one or more services on the path in the topology of the second donor-CU ) Radio Link Control (RLC) channel and/or BAP sublayer routing has been released.
  • BH backhaul
  • RLC Radio Link Control
  • the first donor-CU configures a backhaul (BH) radio link control (RLC) channel and/or a BAP sublayer route used on a path in the topology of the first donor-CU for the service.
  • BH backhaul
  • RLC radio link control
  • the first donor-CU configures and updates uplink backhaul (BH) information of the one or more services to the IAB node.
  • BH uplink backhaul
  • the first donor-CU configures and releases the BAP header rewriting information between the topology of the first donor-CU and the topology of the second donor-CU to the IAB node;
  • the first donor-CU configures and releases BH RLC channel mapping information between the topology of the first donor-CU and the topology of the second donor-CU to the IAB node;
  • the first donor-CU configures and releases routing information in the topology of the second donor-CU to the IAB node.
  • the first donor-CU configures and adds routing information in the topology of the first donor-CU to the IAB node;
  • the first donor-CU configures and adds BH RLC channel mapping information in the topology of the first donor-CU to the IAB node.
  • the first donor-CU configures the IP address of the donor-DU anchored to the first donor-CU for the IAB node; wherein the IP address is used for the F1 user plane data of the IAB node, the F1 Control surface data or non-F1 data.
  • a transmission migration fallback 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 receives a transmission migration fallback request sent by the first donor-CU, and the transmission migration fallback request is used to trigger the migration of one or more services to the first donor-CU topology;
  • the second donor-CU sends a transmission migration fallback response 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 CU maintains the RRC connection.
  • the UE context acquisition request message includes indication information for instructing the release of one or more services, or the UE context acquisition request message includes indication information for instructing the release of all services instructions for the .
  • UE context acquisition response message is used to indicate the backhaul (BH) radio used by one or more services on the path in the topology of the second donor-CU Link Control (RLC) channel and/or BAP sublayer routing has been released.
  • BH backhaul
  • the transmission migration management request message includes indication information for instructing the release of one or more services, or the transmission migration management request message includes indication information for instructing the release of all services instructions for the .
  • the second donor-CU releases backhaul (BH) radio link control (RLC) channels and/or BAP sub-channels used on paths in the topology of the second donor-CU for the one or more services layer routing.
  • BH backhaul
  • RLC radio link control
  • 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 27 The transport migration fallback method described above.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne, selon les modes de réalisation, un dispositif donneur d'IAB (accès intégré et liaison terrestre) et un procédé de transmission et de retour en arrière (« rollback ») de la migration. Une unité distribuée d'IAB (IAB-DU) d'un nœud IAB maintient une connexion F1 avec une première unité centrale (CU) doneur (donor-CU), une ressource pour servir un service du nœud IAB a été établie dans une topologie d'une seconde « donor-CU », et le procédé comprend : la première « donor-CU » envoie une demande de transmission et de retour en arrière de la migration à la seconde « donor-CU », la demande de transmission et de retour en arrière de la migration étant utilisée pour déclencher la migration d'un ou de plusieurs services vers la topologie de la première « donor-CU » ; et la réception d'une réponse de transmission et de retour en arrière de la migration envoyée par la seconde « donor-CU ».
PCT/CN2022/075879 2022-02-10 2022-02-10 Dispositif donneur d'iab et procédé de transmission et de retour en arrière de la migration Ceased WO2023150975A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/075879 WO2023150975A1 (fr) 2022-02-10 2022-02-10 Dispositif donneur d'iab et procédé de transmission et de retour en arrière de la migration

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/075879 WO2023150975A1 (fr) 2022-02-10 2022-02-10 Dispositif donneur d'iab et procédé de transmission et de retour en arrière de la migration

Publications (1)

Publication Number Publication Date
WO2023150975A1 true WO2023150975A1 (fr) 2023-08-17

Family

ID=87563444

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/075879 Ceased WO2023150975A1 (fr) 2022-02-10 2022-02-10 Dispositif donneur d'iab et procédé de transmission et de retour en arrière de la migration

Country Status (1)

Country Link
WO (1) WO2023150975A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2025055673A1 (fr) * 2023-09-13 2025-03-20 华为技术有限公司 Procédé et appareil de communication
WO2025066740A1 (fr) * 2023-09-27 2025-04-03 华为技术有限公司 Procédé de communication et appareil associé

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170060616A1 (en) * 2015-09-01 2017-03-02 Fujitsu Limited Migration controlling method and migration controller
CN113940112A (zh) * 2019-03-28 2022-01-14 中兴通讯股份有限公司 用于iab切换的系统和方法
WO2022015230A1 (fr) * 2020-07-17 2022-01-20 Telefonaktiebolaget Lm Ericsson (Publ) Migration inter-cu dans la migration inter-cu de réseau iab dans un réseau iab
WO2022019825A1 (fr) * 2020-07-24 2022-01-27 Telefonaktiebolaget Lm Ericsson (Publ) Traitement de trafic mis en mémoire tampon pendant la migration inter-cu d'un nœud de liaison terrestre à accès intégré (iab)

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170060616A1 (en) * 2015-09-01 2017-03-02 Fujitsu Limited Migration controlling method and migration controller
CN113940112A (zh) * 2019-03-28 2022-01-14 中兴通讯股份有限公司 用于iab切换的系统和方法
WO2022015230A1 (fr) * 2020-07-17 2022-01-20 Telefonaktiebolaget Lm Ericsson (Publ) Migration inter-cu dans la migration inter-cu de réseau iab dans un réseau iab
WO2022019825A1 (fr) * 2020-07-24 2022-01-27 Telefonaktiebolaget Lm Ericsson (Publ) Traitement de trafic mis en mémoire tampon pendant la migration inter-cu d'un nœud de liaison terrestre à accès intégré (iab)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2025055673A1 (fr) * 2023-09-13 2025-03-20 华为技术有限公司 Procédé et appareil de communication
WO2025066740A1 (fr) * 2023-09-27 2025-04-03 华为技术有限公司 Procédé de communication et appareil associé

Similar Documents

Publication Publication Date Title
JP7708302B2 (ja) アクセスバックホール統合通信装置及び方法
CN116235543A (zh) 群组切换的方法、装置和系统
US20240349166A1 (en) Iab-node device, iab-donor device and topology revoking method
JP7639945B2 (ja) 信号の送受信方法、装置及び通信システム
WO2023150975A1 (fr) Dispositif donneur d'iab et procédé de transmission et de retour en arrière de la migration
WO2022205251A1 (fr) Procédé d'envoi et de réception d'informations, procédé d'envoi de données et appareil
WO2023060401A1 (fr) Procédé et appareil de routage sans fil
JP7741617B2 (ja) Ｉａｂドナー機器及び伝送移行管理方法
CN116724589A (zh) 群组迁移方法、装置和系统
WO2023150976A1 (fr) Dispositif donneur iab et procédé de gestion de migration de transfert
JP7758880B2 (ja) Ｉａｂノード装置、ｉａｂドナー装置及び経路移行方法
WO2024164214A1 (fr) Procédé et appareil de traitement d'informations
JP2025511986A (ja) Ｉａｂノード機器、ｉａｂドナー機器及び伝送アドレス確定方法
JP2025511113A (ja) Ｉａｂドナー機器及び伝送アドレス設定方法
JP2025510617A (ja) 情報を設定する方法と装置及び通信システム
CN121040098A (zh) 信号的收发方法、装置和通信系统
CN120982153A (zh) 分布式单元迁移的方法、控制装置和通信系统
WO2024026803A1 (fr) Procédé de configuration de nœud mobile, et dispositif donneur
WO2023130260A1 (fr) Procédé, appareil et système de configuration de message rrc
WO2023019527A1 (fr) Appareil de communication et procédé pour une défaillance de liaison radio

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: 22925337

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22925337

Country of ref document: EP

Kind code of ref document: A1