System and method for migration between donor devices

Abstract

Systems, methods, apparatuses, or computer-readable media and apparatuses for inter-donor device migration are provided. A network node may send information related to the network node migration to a donor device. The donor device may receive information from the network node related to the network node migration.

Description

Technical Field

[0001] This disclosure generally relates to wireless communications, including but not limited to systems, methods, and apparatus for migration between donor devices. Background Technology

[0002] The standards organization Third Generation Partnership Project (3GPP) is currently developing a new radio interface called 5G New Radio (5G NR) and the Next Generation Packet Core Network (NG-CN or NGC). 5G NR will consist of three main components: the 5G Access Network (5G-AN), the 5G Core Network (5GC), and User Equipment (UE). To facilitate the implementation of different data services and needs, the elements of the 5GC (also known as Network Functions) have been simplified, with some of these elements being software-based, allowing them to be adapted as needed. Summary of the Invention

[0003] The exemplary embodiments disclosed herein relate to solving one or more problems presented in the prior art, and provide additional features that will readily become apparent from the following detailed description taken in conjunction with the accompanying drawings. According to various embodiments, exemplary systems, methods, apparatuses, and computer program products are disclosed herein. However, it should be understood that these embodiments are presented by way of example and are not restrictive, and that various modifications can be made to the disclosed embodiments while remaining within the scope of this disclosure, as will be apparent to those skilled in the art who have read this disclosure.

[0004] At least one aspect relates to a system, method, apparatus, or computer-readable medium for migrating an Integrated Access and Backhaul (IAB) node. A network node (e.g., an IAB node) may send / transmit / provide / issue information related to the network node's migration to a donor device. In some implementations, the donor device may include the donor device of the network node's Distributed Unit (DU). The migration may include the migration of the network node's Mobile Termination (MT). In some implementations, the information may be sent via an F1 interface in a signaling manner. In some implementations, the information may include indications of at least one of the following: the start of the migration, the triggering of the migration, the completion of the migration, the success of the migration, the failure of the migration, the cancellation of the migration, the start of a random access procedure, the completion of the random access procedure, the success of the random access procedure, the suspension of data transmission, or the resumption of data transmission.

[0005] In some implementations, the donor device may include the donor device of the mobile terminal (MT) of the network node. The migration may include the migration of the distributed cell (DU) of the network node. In some implementations, this information may be sent via Radio Resource Control (RRC) signaling. In some implementations, this information may include indications of at least one of the following: the start of the migration, the triggering of the migration, the completion of the migration, the success of the migration, the failure of the migration, the cancellation of the migration, or information belonging to at least one cell of the network node. In some implementations, the information belonging to at least one cell of the network node may include at least one of the following: cell identifier (ID), physical cell ID (PCI), public land mobile network (PLMN) ID, tracking area code (TAC), the ID of the DU, or the donor device ID of the DU of the network node.

[0006] In some implementations, when a wireless communication device (e.g., a UE) served by a network node switches from a source cell to a target cell, the beam information used by the wireless communication device in the source cell can be transmitted from the source Centralized Unit (CU) to the target CU, and the beam information can be transmitted from the target CU to the target Distributed Unit (DU). In some implementations, the beam information may include at least one of the following: Transmission Configuration Indicator (TCI) state identifier (ID), Synchronization Signal Block (SSB) ID, Channel State Information Reference Signal (CSI-RS) index, SignalResource Indicator (SRI), cell identifier, Bandwidth Part (BWP) ID, Control Resource Set ID, Physical Uplink Control Channel (PUCCH) resource ID, or PUCCH spatial relation ID.

[0007] In some implementations, when a wireless communication device served by a network node switches from a source cell to a target cell, the network node can send / transmit beam mapping information between the source distributed cell (DU) and the target distributed cell (DU) to the source centralized cell (CU) of the wireless communication device. In some implementations, the 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 beam information or the second beam information may include at least one of the following: Transmission Configuration Indicator (TCI) status identifier (ID), Synchronization Signal Block (SSB) ID, Channel State Information Reference Signal (CSI-RS) index, Probe Reference Signal Resource Indicator (SRI), Cell Identifier, Bandwidth Part (BWP) ID, Control Resource Set ID, Physical Uplink Control Channel (PUCCH) Resource ID, or PUCCH Spatial Relationship ID.

[0008] In some implementations, the Distributed Unit (DU) of a network node may send / transmit an F1 configuration request message to the donor device. This F1 configuration request message may include at least one of the following: Quality of Service (QoS) information of the services of the wireless communication devices served by the network node, the number of wireless communication devices served by the network node, the mobility status of the network node, the speed or rate of the network node, or the location of the network node. In some implementations, the DU of the network node may receive an F1 configuration response message from the donor device. This F1 configuration response message may include at least one of the following: QoS information of the services of the wireless communication devices that the donor device can accept or serve, or the number of wireless communication devices that the donor device can accept or serve.

[0009] At least one aspect relates to a system, method, apparatus, or computer-readable medium for migrating Integrated Access and Backhaul (IAB) nodes. The donor device can receive / obtain / collect / acquire information related to the migration of network nodes from / to the network nodes. Attached Figure Description

[0010] Various exemplary embodiments of this solution are described in detail below with reference to the following figures or drawings. These figures are provided for illustrative purposes only and depict only exemplary embodiments of this solution to aid the reader's understanding. Therefore, the figures should not be considered as limitations on the breadth, scope, or applicability of this solution. It should be noted that these figures are not necessarily drawn to scale for clarity and ease of explanation.

[0011] Figure 1 An example cellular communication network that implements the techniques disclosed herein is shown according to embodiments of the present disclosure; Figure 2 Block diagrams of example base stations and user equipment according to some embodiments of the present disclosure are shown; Figure 3 A block diagram of an environment for mobile integrated access and backhaul (IAB) according to an exemplary embodiment is shown; Figure 4A A block diagram of an integrated access and backhaul (IAB) architecture employing a standalone (SA) mode with a next-generation core network (NGC) is shown according to an exemplary embodiment. Figure 4BA block diagram of an integrated access and backhaul (IAB) architecture employing Evolved Universal Mobile Telecommunications System New Radio (EN-DC) is shown according to an exemplary embodiment. Figure 5 A block diagram of Integrated Access and Backhaul (IAB) nodes in a parent-child relationship according to an exemplary embodiment is shown; and Figure 6 A flowchart of a method and apparatus for migration between donor devices according to an exemplary embodiment is shown. Detailed Implementation

[0012] Various exemplary embodiments of this solution are described below with reference to the accompanying drawings to enable those skilled in the art to make and use this solution. As will be apparent to those skilled in the art, various changes or modifications can be made to the examples described herein without departing from the scope of this solution after reading this disclosure. Therefore, this solution is not limited to the exemplary embodiments and applications described and illustrated herein. Furthermore, the specific order or hierarchy of steps in the methods disclosed herein is merely an example method. Based on design preferences, the specific order or hierarchy of steps in the disclosed methods or processes can be redeployed while remaining within the scope of this solution. Therefore, those skilled in the art will understand that the methods and techniques disclosed herein present various steps or actions in an exemplary order, and unless otherwise expressly stated, this solution is not limited to the specific order or hierarchy presented.

[0013] 1. Mobile Communication Technology and Environment Figure 1 An example wireless communication network and / or system 100 that can implement the techniques disclosed herein is illustrated according to embodiments of this disclosure. In the following discussion, wireless communication network 100 can be any wireless network, such as a cellular network or a narrowband Internet of Things (NB-IoT) network, and is referred to herein as "network 100". Such an example network 100 includes base stations 102 (hereinafter referred to as "BS 102", also called wireless communication nodes) and user equipment 104 (hereinafter referred to as "UE 104", also called wireless communication devices) that can communicate with each other via communication links 110 (e.g., wireless communication channels), and a cluster of cells 126, 130, 132, 134, 136, 138, and 140 covering a geographic area 101. Figure 1In this context, BS 102 and UE 104 are contained within their respective geographical boundaries in cell 126. Each of the other cells 130, 132, 134, 136, 138, and 140 may include at least one base station that operates on its allocated bandwidth to provide sufficient radio coverage to its intended users.

[0014] For example, BS 102 can operate on the allocated channel transmission bandwidth to provide sufficient coverage to UE 104. BS 102 and UE 104 can communicate via downlink radio frame 118 and uplink radio frame 124, respectively. Each radio frame 118 / 124 can also be divided into subframes 120 / 127, which can include data symbols 122 / 128. In this disclosure, BS 102 and UE 104 are described herein as non-limiting examples of "communication nodes," and generally, such non-limiting examples of "communication nodes" can practice the methods disclosed herein. According to various embodiments of this scheme, such a communication node can be capable of wireless and / or wired communication.

[0015] Figure 2 A block diagram of an example wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., OFDM (Orthogonal Frequency Division Multiplexing) / OFDMA (Orthogonal Frequency Division Multiplexing Access) signals) according to some embodiments of the present disclosure is shown. System 200 may include components and elements configured to support known or conventional operating characteristics that do not need to be described in detail herein. In one illustrative embodiment, system 200 may be used in wireless communication environments (such as those described above) Figure 1 In a wireless communication environment 100, communication (e.g., sending and receiving) data symbols.

[0016] The system 200 typically includes a base station 202 (hereinafter referred to as "BS 202") and a user equipment 204 (hereinafter referred to as "UE 204"). The BS 202 includes a BS (Base Station) transceiver module 210 (hereinafter also referred to as: BS transceiver 210, transceiver 210), a BS antenna 212 (hereinafter also referred to as: antenna 212 or downlink antenna 212), a BS processor module 214 (hereinafter also referred to as: processor module 214), a BS memory module 216 (hereinafter also referred to as: memory module 216), and a network communication module 218, each module being coupled and interconnected with each other as needed via a data communication bus 220. UE 204 includes a UE (User Equipment) transceiver module 230 (also referred to as UE transceiver 230, transceiver 230), a UE antenna 232 (hereinafter also referred to as antenna 232 or uplink antenna 232), a UE memory module 234 (hereinafter also referred to as memory module 234), and a UE processor module 236 (hereinafter also referred to as processor module 236). Each module is coupled to and interconnected with each other as needed via a data communication bus 240. BS 202 communicates with UE 204 via communication channel 250 (hereinafter also referred to as wireless transmission link 250, wireless data communication link 250), which can be any wireless channel or other medium suitable for the data transmission described herein.

[0017] As those skilled in the art will understand, system 200 may also include, in addition to Figure 2 Any number of modules other than those shown herein. Those skilled in the art will understand that the various illustrative blocks, modules, circuits, and processing logic described in conjunction with the embodiments disclosed herein can be implemented in hardware, computer-readable software, firmware, or any practical combination thereof. To clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are generally described according to their functionality. Whether this functionality is implemented as hardware, firmware, or software may depend on the specific application and design constraints imposed on the system as a whole. Those skilled in the art described herein can implement such functionality in a suitable manner for each specific application; however, such implementation decisions should not be construed as limiting the scope of this disclosure.

[0018] According to some embodiments, UE transceiver 230 may be referred to herein as an "uplink" transceiver 230 including a radio frequency (RF) transmitter and an RF receiver, each RF transmitter and RF receiver including circuitry coupled to antenna 232. A duplex switch (not shown) may alternately couple the uplink transmitter or receiver to the uplink antenna in a time-duplex manner. Similarly, according to some embodiments, BS transceiver 210 may be referred to herein as a "downlink" transceiver 210 including an RF transmitter and an RF receiver, each RF transmitter and RF receiver including circuitry coupled to antenna 212. A downlink duplex switch may alternatively couple the downlink transmitter or receiver to downlink antenna 212 in a time-division duplex manner. The operation of the two transceiver modules 210 and 230 may be time-coordinated such that while the downlink transmitter is coupled to downlink antenna 212, the uplink receiver circuitry is coupled to uplink antenna 232 to receive transmissions via wireless transmission link 250. Conversely, the operation of the two transceivers 210 and 230 can be coordinated in time, such that while the uplink transmitter is coupled to the uplink antenna 232, the downlink receiver is coupled to the downlink antenna 212 to receive transmissions via the wireless transmission link 250. In some embodiments, there is tight time synchronization with a minimum guard time between changes in the duplex direction.

[0019] UE transceiver 230 and base transceiver 210 are configured to communicate via wireless data communication link 250 and cooperate with RF antennas 212 / 232 arranged in a suitable configuration to support specific wireless communication protocols and modulation schemes. In some illustrative embodiments, UE transceiver 210 and base transceiver 210 are configured to support industry standards, such as Long Term Evolution (LTE) and emerging 5G standards. However, it should be understood that this disclosure is not necessarily limited to application to specific standards and related protocols. Rather, UE transceiver 230 and base transceiver 210 may be configured to support alternative or additional wireless data communication protocols (including future standards or variations thereof).

[0020] According to various embodiments, BS 202 may be, for example, an evolved Node B (eNB), a serving eNB, a target eNB, a femtocell, or a picocell. In some embodiments, UE 204 may be embodied in various types of user equipment, such as mobile phones, smartphones, personal digital assistants (PDAs), tablets, laptops, wearable computing devices, etc. Processor modules 214 and 236 may be implemented or realized using a general-purpose processor, content-addressable memory, digital signal processor, application-specific integrated circuit, 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. In this way, the processor may be implemented as a microprocessor, a controller, a microcontroller, a state machine, etc. The processor may also be implemented as a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors combined with a digital signal processor core, or any other combination of such configurations.

[0021] Furthermore, the steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be directly implemented in hardware, firmware, software modules executed by processor modules 214 and 236 respectively, or any actual combination thereof. Memory modules 216 and 234 can be implemented as random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disks, removable disks, compact disc read-only memory (CD-ROM), or any other form of storage medium known in the art. In this respect, memory modules 216 and 234 can be coupled to processor modules 210 and 230, respectively, enabling processor modules 210 and 230 to read information from and write information to memory modules 216 and 234, respectively. Memory modules 216 and 234 can also be integrated into their respective processor modules 210 and 230. In some embodiments, memory modules 216 and 234 may each include cache memory for storing temporary variables or other intermediate information during the 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 processor modules 210 and 230, respectively.

[0022] Network communication module 218 broadly represents the hardware, software, firmware, processing logic, and / or other components of base station 202 that enable bidirectional communication between base station transceiver 210 and other network components and communication nodes configured to communicate with base station 202. For example, network communication module 218 may be configured to support Internet or WiMAX (World Interoperability for Microwave Access) services. In a typical deployment, but without limitation, network communication module 218 provides an 802.3 Ethernet interface, allowing base station transceiver 210 to communicate with traditional Ethernet-based computer networks. In this way, network communication module 218 may include a physical interface for connecting to a computer network (e.g., a Mobile Switching Center (MSC)). The terms “configured for,” “configured to,” and their variations, used in this document in relation to a specified operation or function, refer to a device, component, circuit, structure, machine, signal, etc., which is physically constructed, programmed, formatted, and / or arranged to perform a specified operation or function.

[0023] The Open Systems Interconnection (OSI) model (referred to herein as the "OSI model") is a conceptual and logical layout that defines network communications used by systems (e.g., wireless communication devices, wireless communication nodes) for interconnecting and communicating with other systems. The model is divided into seven sub-components or layers, each representing a conceptual set of services provided to its upper and lower layers. The OSI model also defines logical networks and efficiently describes computer packet transmission using different layer protocols. The OSI model may also be referred to as the seven-layer OSI model or the seven-layer model. In some embodiments, the first layer may be the physical layer. In some embodiments, the second layer may be the Medium Access Control (MAC) layer. In some embodiments, the third layer may be the Radio Link Control (RLC) layer. In some embodiments, the fourth layer may be the Packet Data Convergence Protocol (PDCP) layer. In some embodiments, the fifth layer may be the Radio Resource Control (RRC) layer. In some embodiments, the sixth layer may be the Non-Access Stratum (NAS) layer or the Internet Protocol (IP) layer, and the seventh layer is another layer.

[0024] 2. Systems, methods, and apparatus for relocation between donor facilities. Now for reference Figure 3 This diagram depicts a block diagram of an environment for Mobile Integrated Access and Backhaul (IAB). IAB supports wireless backhaul via New Radio (NR), enabling flexible and very dense deployment of NR cells while reducing the need for wired transmission infrastructure. A centralized unit (CU) migration procedure within the donor device can be provided, where both the source and target parent nodes are served by the same IAB donor CU. However, inter-donor CU migration within a migrating (mobile) IAB node can be static. As shown in the diagram, performing inter-donor migration in mobile IAB use cases can be challenging. In mobile IAB use cases, IAB nodes are installed in vehicles, providing coverage and capacity enhancements for in-vehicle or surrounding user equipment (UEs).

[0025] Now for reference Figure 4AThis paper describes a block diagram of an Integrated Access and Backhaul (IAB) architecture employing a Standalone (SA) mode with a Next Generation Core (NGC). Integrated Access and Backhaul (IAB) enables radio relay in the NG-RAN. Relay nodes (called IAB nodes) can support access and backhaul via NR. The terminal node of the NR backhaul on the network side is called the IAB donor device, which can represent a gNB with additional IAB-supporting functionality. Backhaul can occur via single hops or multiple hops.

[0026] IAB nodes can support gNB-DU functionality to terminate the NR access interface to the UE and the next-hop IAB node, and / or terminate the F1 protocol to the gNB-CU function on the IAB donor device. The gNB-DU function on the IAB node can also be called an IAB Distributed Unit (IAB-DU). In addition to gNB-DU functionality, IAB nodes can also support a subset of UE functions (called IAB-MT (Mobile Termination)). This subset of UE functions can include, for example, physical layer, layer 2, radio resource control (RRC), and non-access stratum (NAS) functions to connect to the gNB-DU of another IAB node or IAB donor device, thereby connecting to the gNB-CU on the IAB donor device and connecting to the core network, etc.

[0027] Now for reference Figure 4B This paper describes a block diagram of an Integrated Access and Backhaul (IAB) architecture using the Evolved Universal Mobile Telecommunications System New Radio (EN-DC). IAB nodes can access the network using either SA (Standalone) mode or EN-DC. In EN-DC, IAB nodes are also connected to the MeNB (Master eNodeB) via E-UTRA (Evolved Universal Terrestrial Radio Access), and the IAB donor device terminates as an SgNB (Secondary eNodeB, e.g., as defined in TS 37.340) via X2-C.

[0028] Now for reference Figure 5This diagram depicts the integrated access and backhaul (IAB) nodes in a parent-child relationship. All IAB nodes connected to the IAB donor device via one or more hops can form a directed acyclic graph (DAG) topology rooted at the IAB donor device. In this DAG topology, neighboring nodes on the interfaces of an IAB-DU can be called child nodes, and neighboring nodes on the interfaces of an IAB-MT can be called parent nodes. The direction towards a child node can also be called the downstream direction, while the direction towards the parent node is called the upstream direction. The IAB donor device can perform centralized resource, topology, and routing management for the IAB topology.

[0029] In some embodiments, when a mobile IAB node (e.g., on / in a vehicle) switches from one parent IAB node to another, a group of UEs served by that mobile IAB node (e.g., on / in / in-vehicle) may also perform a handover. When a group of onboard UEs perform a handover (HO) simultaneously, RACH (Random Access Channel) conflicts may occur between the UEs (e.g., between RACH process transmissions / messages). To avoid this, a RACH-free handover can be used for onboard UEs (e.g., the UE can skip the RACH process during the handover). In some implementations, when a UE performs a RACH-free handover, the UE and the target logical DU (e.g., the DU of the target parent IAB node or the target gNB-DU) cannot rely on the RACH process to determine the initial beam of the target cell. In some systems, which beam is used for the UE in the target cell is undefined. Therefore, the methods implemented by the systems, methods, apparatuses, and / or computer-readable media discussed herein can be used to determine the beam used by the UE when performing a handover in the target cell.

[0030] To implement the above scheme, the UE's source centralized unit (CU) (e.g., the CU of the source parent IAB node or the source gNB-CU) can send source beam information to the UE's target CU (e.g., the CU of the target parent IAB node or the target gNB-CU). The source beam information may include beam information used by the UE in the source cell and / or beam information used by the source CU. The source beam information (e.g., beam information of the source CU) may include at least one of the following: TCI state ID, beam state ID, SSB ID, CSI-RS index, SRI, cell identifier, BWP ID, Control Resource Set ID, PUCCH resource ID, or PUCCH spatial relationship ID. In another step, the source beam information can be sent from the UE's target CU to the UE's target distributed unit (DU) (e.g., the DU of the target parent IAB node or the target gNB-DU). In another step, the UE's target DU can determine the beam used by the UE in 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). As another step, the UE's target DU can send target beam information (e.g., beam information used by the UE in the target cell, and / or beam information used by the target CU) to the UE's target CU. The beam information may include at least one of the following: TCI state ID, SSBID, CSI-RS index, SRI, cell identifier, BWP ID, Control Resource Set ID, PUCCH resource ID, or PUCCH spatial relationship ID. As a next step, the UE's target CU can send the target beam information to the UE. For example, the UE's target CU can send the target beam information to the UE's source CU, and the source CU can send the target beam information to the UE's source DU. Then, the UE's source DU can send the target beam information to the UE.

[0031] In some implementations, the IAB node (e.g., a node serving the UE) can send beam mapping information to the UE's source CU. This beam mapping information may include beam mapping information between the source logical DU and the target logical DU. In some implementations, the beam mapping information may include beam information in the source logical DU / cell and beam information in the target logical DU / cell. Each beam information may include at least one of the following: TCI state ID, SSB ID, CSI-RS index, SRI, cell identifier, BWP ID, Control Resource Set ID, PUCCH resource ID, or PUCCH spatial relationship ID. As another step, optionally, for example, the UE's source CU can determine / identify the beam used by the UE in the target cell and send the target beam information to the UE's target CU. In some implementations, the UE's source CU can send the beam mapping information to the UE's target CU, and then the target CU can determine the beam used by the UE in the target cell. As a next step, the UE's target CU can send the target beam information beam to the UE's target DU. As another step, the UE's target DU can send target beam information (e.g., beam information used by the UE in the target cell, and / or beam information used by the target CU) to the UE's target CU. The beam information may include at least one of the following: TCI state ID, SSB ID, CSI-RS index, SRI, cell identifier, BWP ID, Control Resource Set ID, PUCCH resource ID, or PUCCH spatial relationship ID. As a next step, the UE's target CU can send the target beam information to the UE. For example, the UE's target CU can send the target beam information to the UE's source CU, and the source CU can send the target beam information to the UE's source DU. Then, the UE's source DU can send the target beam information to the UE.

[0032] In some embodiments, when a mobile IAB node switches from one parent IAB node to another, the MT portion of the mobile IAB node is migrated from the source IAB donor device to the target IAB donor device (e.g., an MT migration is performed), and the DU portion of the mobile IAB node is also migrated (e.g., a DU migration is performed). The source and target donor devices of the MT (e.g., the MT portion) may differ from the source and target donor devices of the DU (e.g., the DU portion). In some implementations, the donor device of the MT may not be aware of the DU migration, and / or the donor device of the DU may not be aware of the MT migration. In some systems, the MT migration can be initiated while the DU migration is in progress, and vice versa. Therefore, the methods implemented by the systems, methods, apparatuses, and / or computer-readable media discussed herein allow IAB donor devices to know / determine the status of the MT migration and / or DU migration, for example, to avoid simultaneous MT and / or DU migrations.

[0033] To implement the above scheme, the IAB node can, for example, send MT migration-related information to the IAB-DU donor device via F1 signaling. This MT migration-related information can provide / indicate the status / stage / condition of the MT migration. The MT migration-related information may include indications of at least one of the following: start of MT migration, triggering 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. As another step, the IAB-DU donor device can take appropriate actions based on the MT migration-related information, such as determining when to initiate DU migration, or determining whether to suspend or resume data transmission to the IAB node.

[0034] In some implementations, the IAB node can send DU migration-related information to the IAB-MT donor device, for example, via RRC signaling. This DU migration-related information can provide / indicate the status / stage / condition of the DU migration. The DU migration-related information may include indications of at least one of the following: start of DU migration, triggering of DU migration, completion of DU migration, success of DU migration, failure of DU migration, cancellation of DU migration, or cell information belonging to the mobile IAB node. In some implementations, the cell information 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 device co-located with the IAB-MT and connected to the IAB-DU. As a second step, the IAB-MT donor device can take appropriate actions based on the DU migration-related information, for example, determining when to initiate MT migration.

[0035] In some embodiments, when a mobile IAB node switches from one parent IAB node to another, the MT portion of the mobile IAB node is migrated from the source IAB donor device to the target IAB donor device, and the DU portion of the mobile IAB node is also migrated. The source and target donor devices of the MT may differ from the source and target donor devices of the DU. In some implementations, the DU migration may be triggered by Operations, Administration and Maintenance (OAM) or the source CU of the DU. After the mobile IAB node triggers the DU migration, the mobile IAB node can initiate the DU migration to the target CU of the DU, and the UEs served by the mobile IAB node will also be transferred to the target CU of the DU. In some systems, if the target CU of the DU does not have sufficient resources to serve all UEs, the UE handover may be rejected, or the target CU of the DU may only be able to accept some UE services. Therefore, the systems, methods, apparatuses, and / or computer-readable media implemented herein can allow the target CU of the DU to access / receive / understand / determine UE service information during the DU migration process prior to the UE handover process.

[0036] To implement the above scheme, the IAB-DU can send an F1 configuration request message to the IAB donor device (e.g., the target CU of the DU). This F1 configuration request message may include UE service information. It may include at least one of the following: QoS information of the UE services served by the mobile IAB node, the number of UEs served by the mobile IAB node, the mobility status of the mobile IAB node, the speed / rate of the mobile IAB node, or the location of the mobile IAB node. As another step, the IAB donor device can send an F1 configuration response or an F1 configuration failure message to the IAB-DU. This F1 configuration response or failure message may include at least one of the following: QoS information of UE services that the IAB donor device can accept / serve, or the number of UEs that the IAB donor device can accept / serve. The F1 configuration failure message may include a reason value for the F1 configuration failure, which may indicate / explain / reflect, for example, that the IAB donor device cannot (or may not) accept all UE services served by the IAB-DU, or an admission control situation.

[0037] In some embodiments, a parent node supporting a mobile IAB node can broadcast mobile IAB support information to indicate that the cell supports the mobile IAB node. If a cell broadcasts mobile IAB support information, the mobile IAB node can consider that cell as a candidate cell (e.g., the mobile IAB node / MT can attempt to connect to that cell). In some systems, the IAB donor device connected to the parent node can detect / determine that the load in the cell where the parent node resides is high. In this case, the parent node's cell may be unable (or unable) to provide service to any other mobile IAB node. Therefore, the systems, methods, apparatuses, and / or computer-readable media implemented herein discussed can be used to determine whether a parent node can broadcast mobile IAB support information.

[0038] To implement the above scheme, the IAB donor CU can, for example, send / transmit a mobile IAB prohibition message to the gNB-DU (e.g., the IAB node) via F1 signaling. This mobile IAB prohibition message indicates whether the corresponding cell prohibits access for the mobile IAB node. In another step, the gNB-DU can use the mobile IAB prohibition message to determine whether the cell allows access for the mobile IAB node. Alternatively, as another step, the gNB-DU can determine whether to broadcast mobile IAB support information based on the mobile IAB prohibition message. For example, if the mobile IAB prohibition message is set to "prohibited," the gNB-DU may not broadcast mobile IAB support information. If the mobile IAB prohibition message is set to "not prohibited," the gNB-DU can broadcast mobile IAB support information.

[0039] Now for reference Figure 6 This document describes a flowchart of donor device migration or IAB node switching in method 600. This can be used in conjunction with... Figures 1 to 5 Method 600 is implemented by any of the detailed components and devices. In general, the network node is able to send / transmit / provide / issue information related to the migration of that network node to the donor device (602). The donor device can receive / obtain / collect / acquire information related to the migration of that network node (e.g., MT migration, DU migration) from the network node (604).

[0040] More specifically, a network node (e.g., an IAB node) may send / transmit / provide / issue information related to the migration of that network node to a donor device. In some configurations, the donor device may include the donor device of a distributed unit (DU) of the network node. Migration may include the migration of a mobile terminal (MT) of the network node. In some implementations, the information can be sent via signaling through the F1 interface. In some configurations, the information may include indications of at least one of the following (e.g., indications of the status / stage of the migration): start of migration (e.g., MT or DU migration), triggering of migration, completion of migration, success of migration, failure of migration, cancellation of migration, start of random access procedure, completion of random access procedure, success of random access procedure, suspension of data transmission, or resumption of data transmission.

[0041] In some configurations, the donor device may include the donor device of a mobile terminal (MT) of a network node. Migration may include the migration of a distributed unit (DU) of a network node. In some implementations, the information may be sent via Radio Resource Control (RRC) signaling. In some configurations, the information may include indications of at least one of the following: start of migration, triggering of migration, completion of migration, success of migration, failure of migration, cancellation of migration, or information belonging to at least one cell of the network node. In some configurations, the information belonging to at least one cell of the network node may include at least one of the following: cell identifier (ID), physical cell ID (PCI), public land mobile network (PLMN) ID, tracking area code (TAC), DU ID, or the donor device ID of the DU of the network node.

[0042] In some configurations, when a wireless communication device (e.g., a UE) served by a network node switches from a source cell to a target cell, the beam information used by the wireless communication device in the source cell can be sent from the source centralized unit (CU) to the target CU, or the beam information can be sent from the target CU to the target distributed unit (DU). In some configurations, the beam information may include at least one of the following: Transmission Configuration Indicator (TCI) State Identifier (ID), Synchronization Signal Block (SSB) ID, Channel State Information Reference Signal (CSI-RS) Index, Probe Reference Signal Resource Indicator (SRI), Cell Identifier, Bandwidth Part (BWP) ID, Control Resource Set ID, Physical Uplink Control Channel (PUCCH) Resource ID, or PUCCH Spatial Relationship ID.

[0043] In some configurations, when a wireless communication device served by a network node switches from a source cell to a target cell, the network node can send / transmit beam mapping information between the source distributed cell (DU) and the target distributed cell (DU) to the source centralized cell (CU) of the wireless communication device. In some configurations, the 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: Transmission Configuration Indicator (TCI) Status Identifier (ID), Synchronization Signal Block (SSB) ID, Channel State Information Reference Signal (CSI-RS) Index, Probe Reference Signal Resource Indicator (SRI), Cell Identifier, Bandwidth Part (BWP) ID, Control Resource Set ID, Physical Uplink Control Channel (PUCCH) Resource ID, or PUCCH Spatial Relationship ID.

[0044] In some configurations, the Distributed Unit (DU) of a network node can send / transmit an F1 setup request message to a donor device. This F1 setup request message may include information related to UE services. The F1 setup request message may include at least one of the following: Quality of Service (QoS) information of the services of the wireless communication devices served by the network node, the number of wireless communication devices served by the network node, the mobility status of the network node, the speed or rate of the network node, or the location of the network node. In some configurations, the DU of the network node can receive an F1 setup response message from the donor device. This F1 setup response message may include at least one of the following: QoS information of the services of the wireless communication devices that the donor device can accept or serve, or the number of wireless communication devices that the donor device can accept or serve.

[0045] At least one aspect relates to a system, method, apparatus, or computer-readable medium-based method for migrating an Integrated Access and Backhaul (IAB) node. The donor device can receive / obtain / collect / acquire information related to the migration of a network node from that network node.

[0046] Although various embodiments of the present solution have been described above, it should be understood that these embodiments are presented as examples only and not as limitations. Similarly, the various figures may depict exemplary architectures or configurations, and these figures are provided to enable those skilled in the art to understand the exemplary features and functionality of the present solution. However, those skilled in the art should understand that the present solution is not limited to the exemplary architectures or configurations shown, but can be implemented using various alternative architectures and configurations. Furthermore, as those skilled in the art will understand, one or more features of one embodiment may be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of this disclosure should not be limited to any of the illustrative embodiments described above.

[0047] It should also be understood that any reference to elements using names such as "first," "second," etc., in this document generally does not restrict the number or order of these elements. Rather, these names may be used herein as a convenient means of distinguishing between two or more elements or instances of elements. Therefore, references to the first and second elements do not imply that only two elements can be used or that the first element must precede the second element in some way.

[0048] Furthermore, those skilled in the art will understand that information and signals can be represented using any of a variety of technologies and techniques. For example, data, instructions, commands, information, signals, bits, and symbols, as may be referenced in the above description, can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or light particles, or any combination thereof.

[0049] Those skilled in the art will further understand that any of the various illustrative logic blocks, modules, processors, means, circuits, methods, and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of both), firmware, various forms of program or design code in conjunction with instructions (which may be referred to herein as "software" or "software module" for convenience), or any combination of these technologies. To clearly illustrate the interchangeability between hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are generally described above according to their function. Whether such function is implemented as hardware, firmware, or software, or a combination of these technical means, depends on the specific application and the design constraints imposed on the system as a whole. Those skilled in the art can implement the described functions in various ways for each specific application, but these implementation decisions will not depart from the scope of this disclosure.

[0050] Furthermore, those skilled in the art will understand that the various illustrative logic blocks, modules, devices, components, and circuits described herein can be implemented within or executed by an integrated circuit (IC), which may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, or any combination thereof. Logic blocks, modules, and circuits may also include antennas and / or transceivers for communicating with various components within a network or device. A general-purpose processor may be a microprocessor, but alternatively, it may be any conventional processor, controller, or state machine. A processor may also be implemented as a combination of multiple computing devices, such as a combination of a DSP and a microprocessor, a combination of multiple microprocessors, one or more microprocessors combined with a DSP core, or any other suitable configuration performing the functions described herein.

[0051] If these functions are implemented in software, they can be stored as one or more instructions or code on a computer-readable medium. Therefore, the steps of the methods or algorithms disclosed herein can be implemented as software stored on a computer-readable medium. A computer-readable medium includes both computer storage media and communication media, encompassing any medium capable of transferring a computer program or code from one place to another. A storage medium can be any available medium accessible to a computer. For example, but not limited to, such a computer-readable medium can include RAM, ROM, EEPROM, CD-ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other medium that can be used to store the required program code in the form of instructions or data structures and is accessible to a computer.

[0052] In this document, the term "module" as used herein refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. Furthermore, for purposes of discussion, various modules are described as separate modules; however, as will be apparent to those skilled in the art, two or more modules may be combined to form a single module that performs the associated functions according to embodiments of this solution.

[0053] Furthermore, memory or other storage devices and communication components may be used in embodiments of this solution. It should be understood that, for clarity, the above description refers to embodiments of this solution with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functionality among different functional units, processing logic elements, or domains can be used without diminishing the effectiveness of this solution. For example, functions shown to be performed by a separate processing logic element or controller may be performed by the same processing logic element or controller. Therefore, references to specific functional units are merely references to suitable means for providing the described functionality and do not indicate a strict logical or physical structure or organization.

[0054] Various modifications to the embodiments described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein can be applied to other embodiments without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the embodiments shown herein, but is to be given the broadest scope consistent with the novel features and principles disclosed herein as set forth in the appended claims.

Claims

1. A method comprising: The network node sends information related to the migration of the network node to the donor device.

2. The method according to claim 1, wherein, There is at least one of the following situations: The donor device includes the donor device of the distributed unit (DU) of the network node; The migration includes the migration of the mobile terminals (MTs) of the network nodes; or The information is sent via signaling through the F1 interface.

3. The method according to claim 2, wherein, The information includes instructions for at least one of the following: The migration begins, the migration is triggered, the migration is completed, the migration is successful, the migration fails, the migration is canceled, the random access procedure begins, the random access procedure is completed, the random access procedure is successful, and the data transmission is paused or resumed.

4. The method according to claim 1, wherein: The donor device includes the donor device of the mobile terminal (MT) of the network node; The migration includes the migration of the distributed unit (DU) of the network node; or The information is transmitted via Radio Resource Control (RRC) signaling.

5. The method according to claim 4, wherein, The information includes instructions for at least one of the following: The migration start, the migration trigger, the migration completion, the migration success, the migration failure, the migration cancellation, or information belonging to at least one cell of the network node.

6. The method according to claim 5, wherein, The information belonging to at least one cell of the network node includes at least one of the following: Cell Identifier (ID), Physical Cell ID (PCI), Public Land Mobile Network (PLMN) ID, Tracking Area Code (TAC), ID of the DU, and ID of the donor device of the DU of the network node.

7. A method, wherein: When a wireless communication device served by a network node switches from a source cell to a target cell... The beam information used by the wireless communication device in the source cell is transmitted from the source centralized unit (CU) to the target CU; and The beam information is transmitted from the target CU to the target distributed unit (DU).

8. The method according to claim 7, wherein, The beam information includes at least one of the following: Transmission Configuration Indicator (TCI) Status Identifier (ID), Synchronization Signal Block (SSB) ID, Channel State Information Reference Signal (CSI-RS) Index, Probe Reference Signal Resource Indicator (SRI), Cell Identifier, Bandwidth Part (BWP) ID, Control Resource Set ID, Physical Uplink Control Channel (PUCCH) Resource ID, or PUCCH Spatial Relationship ID.

9. A method, wherein: When a wireless communication device served by a network node switches from a source cell to a target cell, the method includes: The network node sends beam mapping information between the source distributed unit (DU) and the target distributed unit (DU) to the source centralized unit (CU) of the wireless communication device.

10. The method according to claim 9, wherein, The beam mapping information includes at least one of the following: the first beam information of the source DU, or the second beam information of the target DU; The first beam information or the second beam information includes at least one of the following: Transmission Configuration Indicator (TCI) Status Identifier (ID), Synchronization Signal Block (SSB) ID, Channel State Information Reference Signal (CSI-RS) Index, Probe Reference Signal Resource Indicator (SRI), Cell Identifier, Bandwidth Part (BWP) ID, Control Resource Set ID, Physical Uplink Control Channel (PUCCH) Resource ID, or PUCCH Spatial Relationship ID.

11. A method comprising: The distributed unit (DU) of the network node sends an F1 configuration request message to the donor device. The F1 setup request message includes at least one of the following: Quality of Service (QoS) information of the wireless communication devices served by the network node, the number of wireless communication devices served by the network node, the mobility status of the network node, the speed or rate of the network node, or the location of the network node.

12. The method of claim 11, comprising: The DU of the network node receives the F1 setup response message from the donor device. The F1 setting response message includes at least one of the following: QoS information of the services of the wireless communication devices that the donor device can accept or serve, or the number of wireless communication devices that the donor device can accept or serve.

13. A method comprising: The donor device receives information from the network node related to the migration of the network node.

14. A non-transitory computer-readable storage medium storing instructions that, when executed by one or more processors, cause the one or more processors to perform the method according to any one of claims 1 to 13.

15. An apparatus comprising: At least one processor, the at least one processor being configured to implement the method according to any one of claims 1 to 13.

Images