[go: up one dir, main page]

WO2025065621A1 - Systèmes et procédés de migration inter-donneurs - Google Patents

Systèmes et procédés de migration inter-donneurs Download PDF

Info

Publication number
WO2025065621A1
WO2025065621A1 PCT/CN2023/122902 CN2023122902W WO2025065621A1 WO 2025065621 A1 WO2025065621 A1 WO 2025065621A1 CN 2023122902 W CN2023122902 W CN 2023122902W WO 2025065621 A1 WO2025065621 A1 WO 2025065621A1
Authority
WO
WIPO (PCT)
Prior art keywords
migration
information
network node
donor
target
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.)
Pending
Application number
PCT/CN2023/122902
Other languages
English (en)
Inventor
Ying Huang
Lin Chen
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.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Priority to PCT/CN2023/122902 priority Critical patent/WO2025065621A1/fr
Publication of WO2025065621A1 publication Critical patent/WO2025065621A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H04W36/083—Reselecting an access point wherein at least one of the access points is a moving node
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H04W36/085—Reselecting an access point involving beams of access points
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H04W36/087—Reselecting an access point between radio units of access points
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H04W88/085—Access point devices with remote components

Definitions

  • the disclosure relates generally to wireless communications, including but not limited to systems and methods for inter-donor migration and apparatus.
  • the standardization organization Third Generation Partnership Project (3GPP) is currently in the process of specifying a new Radio Interface called 5G New Radio (5G NR) as well as a Next Generation Packet Core Network (NG-CN or NGC) .
  • the 5G NR will have three main components: a 5G Access Network (5G-AN) , a 5G Core Network (5GC) , and a User Equipment (UE) .
  • 5G-AN 5G Access Network
  • 5GC 5G Core Network
  • UE User Equipment
  • the elements of the 5GC also called Network Functions, have been simplified with some of them being software based so that they could be adapted according to need.
  • example embodiments disclosed herein are directed to solving the issues relating to one or more of the problems presented in the prior art, as well as providing additional features that will become readily apparent by reference to the following detailed description when taken in conjunction with the accompany drawings.
  • example systems, methods, devices and computer program products are disclosed herein. It is understood, however, that these embodiments are presented by way of example and are not limiting, and it will be apparent to those of ordinary skill in the art who read the present disclosure that various modifications to the disclosed embodiments can be made while remaining within the scope of this disclosure.
  • At least one aspect is directed to a system, a method, an apparatus, or a computer-readable medium for migrating integrated access and backhaul (IAB) nodes.
  • a network node e.g., IAB-node
  • the donor may include a donor of the network node’s distributed unit (DU) .
  • the migration may include a migration of the network node’s mobile termination (MT) .
  • the information can be sent via signaling through a F1 interface.
  • the information may include an indication of at least one of the following: start of the migration, a trigger of the migration, completion of the migration, success of the migration, failure of the migration, cancellation of the migration, start of a random access procedure, completion of the random access procedure, success of the random access procedure, suspension of data transmission, or resumption of data transmission.
  • the donor may include a donor of the network node’s mobile termination (MT) .
  • the migration may include a migration of the network node’s distributed unit (DU) .
  • the information can be sent via radio resource control (RRC) signaling.
  • the information may include an indication of at least one of the following: start of the migration, trigger of the migration, completion of the migration, success of the migration, failure of the migration, cancellation of the migration, or information of at least one cell belonging to the network node.
  • the information of at least one cell belonging to the network node may include at least one of the following: a cell identifier (ID) , a physical cell ID (PCI) , a public land mobile network (PLMN) ID, a tracking area code (TAC) , an ID of the DU, or an ID of a donor of the network node’s DU.
  • ID cell identifier
  • PCI physical cell ID
  • PLMN public land mobile network
  • TAC tracking area code
  • a wireless communication device e.g., UE
  • a network node when a wireless communication device (e.g., UE) served by a network node performs handover from a source cell to a target cell, information of a beam used by the wireless communication device in the source cell can be sent from a source centralized unit (CU) to a target CU, and information of the beam can be sent from the target CU to a target distributed unit (DU) .
  • CU source centralized unit
  • DU target distributed unit
  • information of the beam may include at least one of the following: a transmission configuration indicator (TCI) state identifier (ID) , a synchronization signal block (SSB) ID, a channel state information reference signal (CSI-RS) index, a sounding reference signal resource indicator (SRI) , a cell identity, a bandwidth part (BWP) ID, a ControlResourceSetId, a physical uplink control channel (PUCCH) resource ID, or a PUCCH spatial relation ID.
  • TCI transmission configuration indicator
  • ID a transmission configuration indicator
  • SSB synchronization signal block
  • CSI-RS channel state information reference signal
  • SRI sounding reference signal resource indicator
  • BWP bandwidth part
  • ControlResourceSetId a physical uplink control channel (PUCCH) resource ID
  • PUCCH physical uplink control channel
  • the network node when a wireless communication device served by a network node performs a handover from a source cell to a target cell, the network node can send/transmit information of beam mapping between a source distributed unit (DU) and a target distributed unit (DU) to a source centralized unit (CU) of the wireless communication device.
  • beam mapping information may include at least one of the following: first beam information of the source DU or second beam information of the target DU.
  • the first or second beam information may include at least one of the following: a transmission configuration indicator (TCI) state identifier (ID) , a synchronization signal block (SSB) ID, a channel state information reference signal (CSI-RS) index, a sounding reference signal resource indicator (SRI) , a cell identity, a bandwidth part (BWP) ID, a ControlResourceSetId, a physical uplink control channel (PUCCH) resource ID, or a PUCCH spatial relation ID.
  • TCI transmission configuration indicator
  • ID a transmission configuration indicator
  • SSB synchronization signal block
  • CSI-RS channel state information reference signal
  • SRI sounding reference signal resource indicator
  • BWP bandwidth part
  • ControlResourceSetId a physical uplink control channel (PUCCH) resource ID
  • PUCCH physical uplink control channel
  • a distributed unit (DU) of a network node can send/transmit a F1 setup request message to a donor.
  • the F1 setup request message may include at least one of the following: quality of service (QoS) information of traffic of wireless communication devices served by the network node, a number of wireless communication devices served by the network node, a mobility status of the network node, a speed or velocity of the network node, or a location of the network node.
  • the DU of the network node can receive a F1 setup response message from the donor.
  • the F1 setup response message may include at least one of the following: QoS information of traffic of wireless communication devices that can be accepted or served by the donor, or a number of wireless communication devices that can be accepted or served by the donor.
  • At least one aspect is directed to a system, a method, an apparatus, or a computer-readable medium for migrating integrated access and backhaul (IAB) nodes.
  • a donor can receive/obtain/collect/acquire information related to migration of the network node from a network node.
  • FIG. 1 illustrates an example cellular communication network in which techniques disclosed herein may be implemented, in accordance with an embodiment of the present disclosure
  • FIG. 2 illustrates a block diagram of an example base station and a user equipment device, in accordance with some embodiments of the present disclosure
  • FIG. 3 illustrates a block diagram of an environment for a mobile integrated access and backhaul (IAB) , in accordance with an illustrative embodiment
  • FIG. 4A illustrates a block diagram of an integrated access and backhaul (IAB) architecture using standalone (SA) mode with a next generation core (NGC) , in accordance with an illustrative embodiment
  • FIG. 4B illustrates a block diagram of an integrated access and backhaul (IAB) architecture using Evolved Universal Mobile Telecommunications System New Radio (EN-DC) , in accordance with an illustrative embodiment
  • FIG. 5 illustrates a block diagram of integrated access and backhaul (IAB) nodes in a parent and child relationship, in accordance with an illustrative embodiment
  • FIG. 6 illustrates a flow diagram of a method for inter-donor migration and apparatus, in accordance with an illustrative embodiment.
  • FIG. 1 illustrates an example wireless communication network, and/or system, 100 in which techniques disclosed herein may be implemented, in accordance with an embodiment of the present disclosure.
  • the wireless communication network 100 may be any wireless network, such as a cellular network or a narrowband Internet of things (NB-IoT) network, and is herein referred to as “network 100.
  • NB-IoT narrowband Internet of things
  • Such an example network 100 includes a base station 102 (hereinafter “BS 102” ; also referred to as wireless communication node) and a user equipment device 104 (hereinafter “UE 104” ; also referred to as wireless communication device) that can communicate with each other via a communication link 110 (e.g., a wireless communication channel) , and a cluster of cells 126, 130, 132, 134, 136, 138 and 140 overlaying a geographical area 101.
  • the BS 102 and UE 104 are contained within a respective geographic boundary of cell 126.
  • Each of the other cells 130, 132, 134, 136, 138 and 140 may include at least one base station operating at its allocated bandwidth to provide adequate radio coverage to its intended users.
  • the BS 102 may operate at an allocated channel transmission bandwidth to provide adequate coverage to the UE 104.
  • the BS 102 and the UE 104 may communicate via a downlink radio frame 118, and an uplink radio frame 124 respectively.
  • Each radio frame 118/124 may be further divided into sub-frames 120/127 which may include data symbols 122/128.
  • the BS 102 and UE 104 are described herein as non-limiting examples of “communication nodes, ” generally, which can practice the methods disclosed herein. Such communication nodes may be capable of wireless and/or wired communications, in accordance with various embodiments of the present solution.
  • FIG. 2 illustrates a block diagram of an example wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., OFDM/OFDMA signals) in accordance with some embodiments of the present solution.
  • the system 200 may include components and elements configured to support known or conventional operating features that need not be described in detail herein.
  • system 200 can be used to communicate (e.g., transmit and receive) data symbols in a wireless communication environment such as the wireless communication environment 100 of FIG. 1, as described above.
  • the System 200 generally includes a base station 202 (hereinafter “BS 202” ) and a user equipment device 204 (hereinafter “UE 204” ) .
  • the BS 202 includes a BS (base station) transceiver module 210, a BS antenna 212, a BS processor module 214, a BS memory module 216, and a network communication module 218, each module being coupled and interconnected with one another as necessary via a data communication bus 220.
  • the UE 204 includes a UE (user equipment) transceiver module 230, a UE antenna 232, a UE memory module 234, and a UE processor module 236, each module being coupled and interconnected with one another as necessary via a data communication bus 240.
  • the BS 202 communicates with the UE 204 via a communication channel 250, which can be any wireless channel or other medium suitable for transmission of data as described herein.
  • system 200 may further include any number of modules other than the modules shown in FIG. 2.
  • modules other than the modules shown in FIG. 2.
  • the various illustrative blocks, modules, circuits, and processing logic described in connection with the embodiments disclosed herein may be implemented in hardware, computer-readable software, firmware, or any practical combination thereof.
  • various illustrative components, blocks, modules, circuits, and steps are described generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software can depend upon the particular application and design constraints imposed on the overall system. Those familiar with the concepts described herein may implement such functionality in a suitable manner for each particular application, but such implementation decisions should not be interpreted as limiting the scope of the present disclosure.
  • the UE transceiver 230 may be referred to herein as an “uplink” transceiver 230 that includes a radio frequency (RF) transmitter and a RF receiver each comprising circuitry that is coupled to the antenna 232.
  • a duplex switch (not shown) may alternatively couple the uplink transmitter or receiver to the uplink antenna in time duplex fashion.
  • the BS transceiver 210 may be referred to herein as a “downlink” transceiver 210 that includes a RF transmitter and a RF receiver each comprising circuity that is coupled to the antenna 212.
  • a downlink duplex switch may alternatively couple the downlink transmitter or receiver to the downlink antenna 212 in time duplex fashion.
  • the operations of the two transceiver modules 210 and 230 may be coordinated in time such that the uplink receiver circuitry is coupled to the uplink antenna 232 for reception of transmissions over the wireless transmission link 250 at the same time that the downlink transmitter is coupled to the downlink antenna 212. Conversely, the operations of the two transceivers 210 and 230 may be coordinated in time such that the downlink receiver is coupled to the downlink antenna 212 for reception of transmissions over the wireless transmission link 250 at the same time that the uplink transmitter is coupled to the uplink antenna 232. In some embodiments, there is close time synchronization with a minimal guard time between changes in duplex direction.
  • the UE transceiver 230 and the base station transceiver 210 are configured to communicate via the wireless data communication link 250, and cooperate with a suitably configured RF antenna arrangement 212/232 that can support a particular wireless communication protocol and modulation scheme.
  • the UE transceiver 210 and the base station transceiver 210 are configured to support industry standards such as the Long Term Evolution (LTE) and emerging 5G standards, and the like. It is understood, however, that the present disclosure is not necessarily limited in application to a particular standard and associated protocols. Rather, the UE transceiver 230 and the base station transceiver 210 may be configured to support alternate, or additional, wireless data communication protocols, including future standards or variations thereof.
  • LTE Long Term Evolution
  • 5G 5G
  • the BS 202 may be an evolved node B (eNB) , a serving eNB, a target eNB, a femto station, or a pico station, for example.
  • eNB evolved node B
  • the UE 204 may be embodied in various types of user devices such as a mobile phone, a smart phone, a personal digital assistant (PDA) , tablet, laptop computer, wearable computing device, etc.
  • PDA personal digital assistant
  • the processor modules 214 and 236 may be implemented, or realized, with a general purpose processor, a content addressable memory, a digital signal processor, an application specific integrated circuit, a field programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein.
  • a processor may be realized as a microprocessor, a controller, a microcontroller, a state machine, or the like.
  • a processor may also be implemented as a combination of computing devices, e.g., a combination of a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other such configuration.
  • the steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in firmware, in a software module executed by processor modules 214 and 236, respectively, or in any practical combination thereof.
  • the memory modules 216 and 234 may be realized as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
  • memory modules 216 and 234 may be coupled to the processor modules 210 and 230, respectively, such that the processors modules 210 and 230 can read information from, and write information to, memory modules 216 and 234, respectively.
  • the memory modules 216 and 234 may also be integrated into their respective processor modules 210 and 230.
  • the memory modules 216 and 234 may each include a cache memory for storing temporary variables or other intermediate information during execution of instructions to be executed by processor modules 210 and 230, respectively.
  • Memory modules 216 and 234 may also each include non-volatile memory for storing instructions to be executed by the processor modules 210 and 230, respectively.
  • the network communication module 218 generally represents the hardware, software, firmware, processing logic, and/or other components of the base station 202 that enable bi-directional communication between base station transceiver 210 and other network components and communication nodes configured to communication with the base station 202.
  • network communication module 218 may be configured to support internet or WiMAX traffic.
  • network communication module 218 provides an 802.3 Ethernet interface such that base station transceiver 210 can communicate with a conventional Ethernet based computer network.
  • the network communication module 218 may include a physical interface for connection to the computer network (e.g., Mobile Switching Center (MSC) ) .
  • MSC Mobile Switching Center
  • the Open Systems Interconnection (OSI) Model (referred to herein as, “open system interconnection model” ) is a conceptual and logical layout that defines network communication used by systems (e.g., wireless communication device, wireless communication node) open to interconnection and communication with other systems.
  • the model is broken into seven subcomponents, or layers, each of which represents a conceptual collection of services provided to the layers above and below it.
  • the OSI Model also defines a logical network and effectively describes computer packet transfer by using different layer protocols.
  • the OSI Model may also be referred to as the seven-layer OSI Model or the seven-layer model.
  • a first layer may be a physical layer.
  • a second layer may be a Medium Access Control (MAC) layer.
  • MAC Medium Access Control
  • a third layer may be a Radio Link Control (RLC) layer.
  • a fourth layer may be a Packet Data Convergence Protocol (PDCP) layer.
  • PDCP Packet Data Convergence Protocol
  • a fifth layer may be a Radio Resource Control (RRC) layer.
  • a sixth layer may be a Non Access Stratum (NAS) layer or an Internet Protocol (IP) layer, and the seventh layer being the other layer.
  • NAS Non Access Stratum
  • IP Internet Protocol
  • FIG. 3 depicted is a block diagram of an environment for a mobile integrated access and backhaul (IAB) .
  • An Integrated Access and Backhaul (IAB) may support wireless backhauling via new radio (NR) enabling flexible and very dense deployment of NR cells while reducing the need for wireline transport infrastructure.
  • Intra-donor centralized unit (CU) migration procedure may be provided in which both the source and the target parent node are served by the same IAB-donor-CU.
  • the inter-donor CU migration in the migrating (mobile) IAB node may be static. It may be difficult to perform inter-donor migration in a mobile IAB use scenario as depicted.
  • IAB nodes are mounted in vehicles and can provide coverage and capacity enhancement to onboard or surrounding user equipment (UEs) .
  • UEs user equipment
  • FIG. 4A depicted is a block diagram of an integrated access and backhaul (IAB) architecture using standalone (SA) mode with a next generation core (NGC) .
  • the integrated access and backhaul (IAB) can enable wireless relaying in NG-RAN.
  • the relaying node referred to as IAB node
  • the relaying node may support access and backhauling via NR.
  • the terminating node of NR backhauling on network side may be referred to as the IAB-donor, which can represent a gNB with additional functionality to support IAB.
  • Backhauling can occur via a single or via multiple hops.
  • the IAB node may support gNB-DU functionality, to terminate the NR access interface to UEs and next-hop IAB nodes, and/or to terminate the F1 protocol to the gNB-CU functionality, on the IAB-donor.
  • the gNB-DU functionality on the IAB node may be also referred to as IAB distributed unit (DU) (IAB-DU) .
  • the IAB node may also support a subset of the UE functionality referred to as IAB-mobile termination (MT) , which can include, e.g., physical layer, layer-2, radio resource control (RRC) and non-access stratum (NAS) functionality to connect to the gNB-DU of another IAB node or the IAB-donor, to connect to the gNB-CU on the IAB-donor, and to the core network, among others.
  • IAB-mobile termination e.g., physical layer, layer-2, radio resource control (RRC) and non-access stratum (NAS) functionality to connect to the gNB-DU of another IAB node or the IAB-donor, to connect to the gNB-CU on the IAB-donor, and to the core network, among others.
  • RRC radio resource control
  • NAS non-access stratum
  • FIG. 4B depicted is a block diagram of an integrated access and backhaul (IAB) architecture using Evolved Universal Mobile Telecommunications System New Radio (EN-DC) .
  • the IAB node can access the network using either SA-mode or EN-DC.
  • EN-DC the IAB node also connects via E-UTRA to a MeNB, and the IAB-donor terminates X2-C as SgNB (e.g., as defined in TS 37.340) .
  • FIG. 5 depicted is a block diagram of integrated access and backhaul (IAB) nodes in a parent and child relationship.
  • IAB integrated access and backhaul
  • All IAB nodes that are connected to an IAB-donor via one or multiple hops can form a directed acyclic graph (DAG) topology with the IAB-donor at its root.
  • DAG directed acyclic graph
  • the neighbor node on the IAB-DU’s interface may be referred to as child node and the neighbor node on the IAB-MT’s interface is referred to as parent node.
  • the direction toward the child node may be further referred to as downstream while the direction toward the parent node is referred to as upstream.
  • the IAB-donor may perform centralized resource, topology and route management for the IAB topology.
  • a group of UEs e.g., on/in/onboard the vehicle
  • RACH collision e.g., between RACH procedure transmissions/messages
  • RACH-less HO can be used for the onboard UEs (e.g., UE can skip the RACH procedure during the handover procedure) .
  • a target logical DU e.g., a target parent IAB node's DU, or a target gNB-DU
  • the systems, methods, apparatuses, and/or computer-readable media implemented approaches discussed herein can be used to determine the beam used by the UE at the target cell for the UE handover.
  • the UE’s source centralized unit (e.g., a source parent IAB node's CU, or a source gNB-CU) can send the source beam information to the UE’s target CU (e.g., a target parent IAB node's CU, or a target gNB-CU) .
  • the source beam information can include information about the beam used by the UE in the source cell and/or a beam used by the source CU) .
  • the source beam information (e.g., information of the source CU’s beam) may include at least one of the following: TCI state ID, beam state ID, SSB ID, CSI-RS index, SRI, cell identity, BWP ID, ControlResourceSetId, PUCCH Resource ID, or PUCCH Spatial Relation ID.
  • the source beam information can be sent from the UE’s target CU to the UE’s target distributed unit (DU) (e.g., the target parent IAB node's DU, or the target gNB-DU) .
  • DU target distributed unit
  • the UE’s target DU may determine the beam for the UE used at the target cell based on the source beam information (e.g., based on the relationship between the UE, the source cell and/or the target cell) .
  • the UE’s target DU may send the target beam information (e.g., information of the beam used by the UE in the target cell, and/or a beam used by the target CU) to the UE’s target CU.
  • the information of the beam may include at least one of the following: TCI state ID, SSB ID, CSI-RS index, SRI, cell identity, BWP ID, ControlResourceSetId, PUCCH Resource ID, or PUCCH Spatial Relation ID.
  • the UE’s target CU may send the target beam information to the UE.
  • the UE’s target CU may send the target beam information to the UE’s source CU, which may send the target beam information to the UE’s source DU.
  • the UE’s source DU may then send the target beam information to the UE.
  • an IAB node may send the beam mapping information to the UE’s source CU.
  • the beam mapping information can include information about beam mapping between the source logical DU and the target logical DU.
  • the beam mapping information may include the beam information in the source logical DU/cell and the beam information in the target logical DU/cell.
  • the respective beam information may include at least one of the following: TCI state ID, SSB ID, CSI-RS index, SRI, cell identity, BWP ID, ControlResourceSetId, PUCCH Resource ID, or PUCCH Spatial Relation ID.
  • the UE’s source CU may determine/identify the beam to be used for the UE in the target cell, and can send the target beam information to the UE’s target CU.
  • the UE’s source CU may send the beam mapping information to the UE’s target CU, which may then determine the beam to be used for the UE in the target cell.
  • the UE’s target CU may send the target beam information beam to the UE’s target DU.
  • the UE’s target DU may send the target beam information (e.g., information of the beam used by the UE in the target cell, and/or a beam used by the target CU) to the UE’s target CU.
  • the information of the beam may include at least one of the following: TCI state ID, SSB ID, CSI-RS index, SRI, cell identity, BWP ID, ControlResourceSetId, PUCCH Resource ID, or PUCCH Spatial Relation ID.
  • the UE’s target CU may send the target beam information to the UE.
  • the UE’s target CU may send the target beam information to the UE’s source CU, which may send the target beam information to the UE’s source DU.
  • the UE’s source DU may then send the target beam information to the UE.
  • the MT part of the mobile IAB node when a mobile IAB node performs handover from one parent IAB node to another, the MT part of the mobile IAB node is to be migrated from a source IAB donor to a target IAB donor (e.g., perform MT migration) , and the DU part of the mobile IAB node is also to be migrated (e.g., DU migration) .
  • the source and target donors for the MT e.g., MT part
  • the MT’s donor may not be aware of the DU migration, and/or the DU’s donor may not be aware of the MT migration.
  • the MT migration may be initiated while the DU migration is ongoing, and vice versa. Therefore, the systems, methods, apparatuses, and/or computer-readable media implemented approaches discussed herein can allow the IAB donor (s) to know/determine the status of MT migration and/or DU migration, e.g., to avoid concurrent MT and/or DU migrations.
  • an IAB node may send the MT migration related information to the IAB-DU’s donor, e.g., via F1 signaling.
  • the MT migration related information may provide/indicate a state/stage/status of the MT migration.
  • the MT migration related information may include an indication at least one of the following: start of MT migration, trigger of MT migration, completion of MT migration, success of MT migration, failure of MT migration, cancellation of MT migration, start of random access procedure, completion of random access, success of random access, suspension of data transmission, or resumption of data transmission.
  • the IAB-DU’s donor may take corresponding actions based on the MT migration related information, e.g., determine when to initiate the DU migration or determine whether to suspend or resume the data transmission to the IAB node.
  • the IAB node may send the DU migration related information to the IAB-MT’s donor, e.g., via RRC signaling.
  • the DU migration related information may provide/indicate a state/stage/status of the DU migration.
  • the DU migration related information may include an indication of at least one of the following: start of DU migration, trigger of DU migration, completion of DU migration, success of DU migration, failure of DU migration, cancellation of DU migration, or information of cells belonging to the mobile IAB node.
  • information of cells belonging to the mobile IAB node may include at least one of the following: cell ID, PCI, PLMN ID, TAC, DU ID, or gNB ID of the IAB donor connected with the IAB-MT’s co-located IAB-DU.
  • the IAB-MT’s donor may take corresponding actions based on the DU migration related information, e.g., determine when to initiate the MT migration.
  • the MT part of the mobile IAB node when a mobile IAB node performs handover from one parent IAB node to another parent IAB node, the MT part of the mobile IAB node is to be migrated from a source IAB donor to a target IAB donor, and the DU part of the mobile IAB node is to be migrated as well.
  • the MT’s source and target donors may be different from the DU’s source and target donors.
  • the DU migration may be triggered by operations, administration and maintenance (OAM) or the DU’s source CU.
  • the mobile IAB node may initiate DU migration towards the DU’s target CU, and the UEs served by the mobile IAB node are to be handed over to the DU’s target CU as well.
  • the UE’s handover may be rejected, or only a part of the UE traffic can be accepted at the DU’s target CU. Therefore, the systems, methods, apparatuses, and/or computer-readable media implemented approaches discussed herein can allow the DU’s target CU to access/receive/know/determine the UE traffic information before the UE handover procedure during DU migration.
  • the IAB-DU may send an F1 setup request message to an IAB donor (e.g., the DU’s target CU) .
  • the F1 setup request message may include the UE traffic information.
  • the F1 setup request message may include at least one of the following: QoS information of traffic of UEs served by the mobile IAB node, the number of UEs served by the mobile IAB node, the mobility status of the mobile IAB node, speed/velocity of the mobile IAB node, or the location of the mobile IAB node.
  • the IAB donor may send an F1 setup response or F1 setup failure message to the IAB-DU.
  • the F1 setup response message or the F1 setup failure message may include at least one of the following: Qos information of UE traffic that could be accepted/served by the IAB donor or the number of UEs that can be accepted/served by the IAB donor.
  • the F1 setup failure message may include a cause value of the F1 setup failure, e.g., to indicate/explain/reflect that the IAB donor cannot (or may not) accept all of the UE traffic served by the IAB-DU or the admission control.
  • a parent node that supports a mobile IAB node can broadcast mobile IAB support information to indicate that the cell supports the mobile IAB node. If the cell broadcasts mobile IAB support information, the mobile IAB node can consider the cell as a candidate cell (e.g., the mobile IAB node/MT can try to connect to this cell) .
  • the IAB donor which connects with the parent node, may detect/determine that the load in the cell of the parent node is high. In this case, the cell of the parent node may not (or cannot) serve any more mobile IAB nodes. Therefore, the systems, methods, apparatuses, and/or computer-readable media implemented approaches discussed herein can be used to determine whether the parent node can broadcast mobile IAB support information.
  • the IAB donor CU can send/transmit the mobile IAB barred information to a gNB-DU (e.g. an IAB node) , e.g., via F1 signaling.
  • the mobile IAB barred information indicates whether the corresponding cell is barred or not barred for mobile IAB nodes.
  • the gNB-DU can use the mobile IAB barred information to determine whether the cell allows mobile IAB-node access or not.
  • the gNB-DU can determine whether to broadcast mobile IAB support information based on the mobile IAB barred information.
  • the gNB-DU may not broadcast mobile IAB support information. If the mobile IAB barred information is set to “not barred” , the gNB-DU may broadcast mobile IAB support information.
  • a network node can send/transmit/provide/signal information related to the migration of the network node, to a donor (602) .
  • a donor can receive/obtain/collect/acquire information related to migration (e.g., MT migration, DU migration) of a network node, from the network node (604) .
  • a network node e.g., IAB-node
  • the donor may include a donor of the network node’s distributed unit (DU) .
  • the migration may include a migration of the network node’s mobile termination (MT) .
  • the information can be sent via signaling through a F1 interface.
  • the information may include an indication (e.g., indication of a status/stage of migration) of at least one of the following: start of the migration (e.g., MT or DU migration) , a trigger of the migration, completion of the migration, success of the migration, failure of the migration, cancellation of the migration, start of a random access procedure, completion of the random access procedure, success of the random access procedure, suspension of data transmission, or resumption of data transmission.
  • start of the migration e.g., MT or DU migration
  • the donor may include a donor of the network node’s mobile termination (MT) .
  • the migration may include a migration of the network node’s distributed unit (DU) .
  • the information can be sent via radio resource control (RRC) signaling.
  • the information may include an indication of at least one of the following: start of the migration, trigger of the migration, completion of the migration, success of the migration, failure of the migration, cancellation of the migration, or information of at least one cell belonging to the network node.
  • the information of at least one cell belonging to the network node may include at least one of the following: a cell identifier (ID) , a physical cell ID (PCI) , a public land mobile network (PLMN) ID, a tracking area code (TAC) , an ID of the DU, or an ID of a donor of the network node’s DU.
  • ID cell identifier
  • PCI physical cell ID
  • PLMN public land mobile network
  • TAC tracking area code
  • a wireless communication device e.g., UE
  • a network node when a wireless communication device (e.g., UE) served by a network node performs handover from a source cell to a target cell, information of a beam used by the wireless communication device in the source cell can be sent from a source centralized unit (CU) to a target CU, and information of the beam can be sent from the target CU to a target distributed unit (DU) .
  • CU source centralized unit
  • DU target distributed unit
  • information of the beam may include at least one of the following: a transmission configuration indicator (TCI) state identifier (ID) , a synchronization signal block (SSB) ID, a channel state information reference signal (CSI-RS) index, a sounding reference signal resource indicator (SRI) , a cell identity, a bandwidth part (BWP) ID, a ControlResourceSetId, a physical uplink control channel (PUCCH) resource ID, or a PUCCH spatial relation ID.
  • TCI transmission configuration indicator
  • ID transmission configuration indicator
  • SSB synchronization signal block
  • CSI-RS channel state information reference signal
  • SRI sounding reference signal resource indicator
  • BWP bandwidth part
  • ControlResourceSetId a physical uplink control channel (PUCCH) resource ID
  • PUCCH physical uplink control channel
  • the network node when a wireless communication device served by a network node performs a handover from a source cell to a target cell, the network node can send/transmit information of beam mapping between a source distributed unit (DU) and a target distributed unit (DU) to a source centralized unit (CU) of the wireless communication device.
  • beam mapping information may include at least one of the following: first beam information of the source DU or second beam information of the target DU.
  • the first or second beam information may include at least one of the following: a transmission configuration indicator (TCI) state identifier (ID) , a synchronization signal block (SSB) ID, a channel state information reference signal (CSI-RS) index, a sounding reference signal resource indicator (SRI) , a cell identity, a bandwidth part (BWP) ID, a ControlResourceSetId, a physical uplink control channel (PUCCH) resource ID, or a PUCCH spatial relation ID.
  • TCI transmission configuration indicator
  • ID a transmission configuration indicator
  • SSB synchronization signal block
  • CSI-RS channel state information reference signal
  • SRI sounding reference signal resource indicator
  • BWP bandwidth part
  • ControlResourceSetId a physical uplink control channel (PUCCH) resource ID
  • PUCCH physical uplink control channel
  • a distributed unit (DU) of a network node can send/transmit a F1 setup request message to a donor.
  • the F1 setup request message may include UE traffic related information.
  • the F1 setup request message may include at least one of the following: quality of service (QoS) information of traffic of wireless communication devices served by the network node, a number of wireless communication devices served by the network node, a mobility status of the network node, a speed or velocity of the network node, or a location of the network node.
  • the DU of the network node can receive a F1 setup response message from the donor.
  • the F1 setup response message may include at least one of the following: QoS information of traffic of wireless communication devices that can be accepted or served by the donor, or a number of wireless communication devices that can be accepted or served by the donor.
  • At least one aspect is directed to a system, a method, an apparatus, or a computer-readable medium based approach for migrating integrated access and backhaul (IAB) nodes.
  • a donor can receive/obtain/collect/acquire information related to migration of the network node from a network node.
  • any reference to an element herein using a designation such as “first, ” “second, ” and so forth does not generally limit the quantity or order of those elements. Rather, these designations can be used herein as a convenient means of distinguishing between two or more elements or instances of an element. Thus, a reference to first and second elements does not mean that only two elements can be employed, or that the first element must precede the second element in some manner.
  • any of the various illustrative logical blocks, modules, processors, means, circuits, methods and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two) , firmware, various forms of program or design code incorporating instructions (which can be referred to herein, for convenience, as “software” or a “software module) , or any combination of these techniques.
  • firmware e.g., a digital implementation, an analog implementation, or a combination of the two
  • firmware various forms of program or design code incorporating instructions
  • software or a “software module”
  • IC integrated circuit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • the logical blocks, modules, and circuits can further include antennas and/or transceivers to communicate with various components within the network or within the device.
  • a general purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, or state machine.
  • a processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other suitable configuration to perform the functions described herein.
  • Computer-readable media includes both computer storage media and communication media including any medium that can be enabled to transfer a computer program or code from one place to another.
  • a storage media can be any available media that can be accessed by a computer.
  • such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer.
  • module refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. Additionally, for purpose of discussion, the various modules are described as discrete modules; however, as would be apparent to one of ordinary skill in the art, two or more modules may be combined to form a single module that performs the associated functions according embodiments of the present solution.
  • memory or other storage may be employed in embodiments of the present solution.
  • memory or other storage may be employed in embodiments of the present solution.
  • any suitable distribution of functionality between different functional units, processing logic elements or domains may be used without detracting from the present solution.
  • functionality illustrated to be performed by separate processing logic elements, or controllers may be performed by the same processing logic element, or controller.
  • references to specific functional units are only references to a suitable means for providing the described functionality, rather than indicative of a strict logical or physical structure or organization.

Landscapes

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

Abstract

L'invention concerne des systèmes, des procédés, des appareils, ou des supports lisibles par ordinateur destinés à la migration inter-donneurs et un appareil. Un nœud de réseau peut envoyer des informations relatives à la migration du nœud de réseau à un donneur. Le donneur peut recevoir des informations relatives à la migration du nœud de réseau à partir du nœud de réseau.
PCT/CN2023/122902 2023-09-28 2023-09-28 Systèmes et procédés de migration inter-donneurs Pending WO2025065621A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/122902 WO2025065621A1 (fr) 2023-09-28 2023-09-28 Systèmes et procédés de migration inter-donneurs

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/122902 WO2025065621A1 (fr) 2023-09-28 2023-09-28 Systèmes et procédés de migration inter-donneurs

Publications (1)

Publication Number Publication Date
WO2025065621A1 true WO2025065621A1 (fr) 2025-04-03

Family

ID=95204576

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/122902 Pending WO2025065621A1 (fr) 2023-09-28 2023-09-28 Systèmes et procédés de migration inter-donneurs

Country Status (1)

Country Link
WO (1) WO2025065621A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210044958A1 (en) * 2019-08-08 2021-02-11 Qualcomm Incorporated Signaling to support mobile integrated access and backhaul
US20210315043A1 (en) * 2018-08-09 2021-10-07 Zte Corporation Information Transmission Method and Apparatus, Storage Medium, and Electronic Apparatus
WO2022030770A1 (fr) * 2020-08-04 2022-02-10 Samsung Electronics Co., Ltd. Nœuds dans un réseau de communication et procédés associés
CN114390601A (zh) * 2020-10-16 2022-04-22 大唐移动通信设备有限公司 控制信令传输方法、装置、iab节点、源宿主和目标宿主
US20220141894A1 (en) * 2020-11-02 2022-05-05 Qualcomm Incorporated Triggering migration to enable inter-donor topology adaptation in a wireless network

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210315043A1 (en) * 2018-08-09 2021-10-07 Zte Corporation Information Transmission Method and Apparatus, Storage Medium, and Electronic Apparatus
US20210044958A1 (en) * 2019-08-08 2021-02-11 Qualcomm Incorporated Signaling to support mobile integrated access and backhaul
WO2022030770A1 (fr) * 2020-08-04 2022-02-10 Samsung Electronics Co., Ltd. Nœuds dans un réseau de communication et procédés associés
CN114390601A (zh) * 2020-10-16 2022-04-22 大唐移动通信设备有限公司 控制信令传输方法、装置、iab节点、源宿主和目标宿主
US20220141894A1 (en) * 2020-11-02 2022-05-05 Qualcomm Incorporated Triggering migration to enable inter-donor topology adaptation in a wireless network

Similar Documents

Publication Publication Date Title
US20250016643A1 (en) Systems and methods for inter-donor migration and apparatus
US20240187880A1 (en) Systems and methods for configuration information transfer
WO2023141795A1 (fr) Migration inter-donneur pour nœuds d'accès et de liaison terrestre intégrés (iab)
US12301357B2 (en) Uplink packet duplication transmissions
US20250008385A1 (en) Systems and methods for inter-donor migration and apparatus
US20240188157A1 (en) Systems and methods for establishing shared n3 tunnel
WO2025065621A1 (fr) Systèmes et procédés de migration inter-donneurs
WO2024065245A1 (fr) Systèmes et procédés de transfert d'informations dans un système iab et appareil
WO2025137827A1 (fr) Systèmes et procédés de transfert d'informations pour systèmes de relais
WO2025145441A1 (fr) Systèmes et procédés de prise en charge de qualité d'expérience
US20240340632A1 (en) Systems and methods for identifying subscription-based unmanned aerial vehicle (uav)
WO2025145587A1 (fr) Systèmes et procédés de transfert d'informations pour systèmes de relais
US20250338182A1 (en) Method of inter-donor migration and apparatus thereof
US20240323723A1 (en) Systems and methods for non-public network (npn) measurement
WO2024026875A1 (fr) Systèmes et procédés de configuration de multi-rat à double connectivité (mrdc) de véhicule aérien sans pilote (uav)
WO2024216773A1 (fr) Systèmes et procédés de détermination d'un accès
WO2024230187A1 (fr) Systèmes et procédés de détection et de gestion de mobilité assistée
WO2025156340A1 (fr) Systèmes et procédés de rétroaction de performance d'équipement utilisateur
WO2023245647A1 (fr) Systèmes et procédés pour nœud intelligent commandé par ue
WO2023010374A1 (fr) Systèmes et procédés de transfert d'informations

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

Country of ref document: EP

Kind code of ref document: A1