Systems and methods for donor transfer and device

Abstract

A system, method, device, or computer-readable medium for inter-donor movement and device is presented. A first network node may transmit information associated with an integrated access and backhaul (IAB) related movement to a second network node. At least one aspect relates to a system, method, device, or computer-readable medium for inter-donor movement and device. The first network node may transmit / transmit / provide / signal / communicate information associated with an integrated access and backhaul (IAB) related movement to a second network node.

Description

[Technical field]

[0001] Technical Field The present disclosure relates generally to wireless communications, including but not limited to systems and methods for inter-donor transfer and devices. [Background technology]

[0002] background The standards body, the 3rd Generation Partnership Project (3GPP®), is currently specifying a new air interface called 5G New Radio (5G NR) as well as the Next Generation Packet Core Network (NG-CN, or NGC). 5G NR has three main components: 5G Access Network (5G-AN), 5G Core Network (5GC), and User Equipment (UE). To facilitate the enablement of different data services and requirements, the elements of 5GC, also called Network Functions (NFs), have been simplified and some of them are software-based so they can be adapted as needed. Summary of the Invention [Means for solving the problem]

[0003] overview The exemplary embodiments disclosed herein are directed to solving 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 accompanying drawings. In accordance with various embodiments, exemplary systems, methods, devices, and computer program products are disclosed herein. However, it is understood that these embodiments are presented by way of example and not limitation, and various modifications to the disclosed embodiments can be made while remaining within the scope of the present disclosure, as will be apparent to those skilled in the art upon reading this disclosure.

[0004] At least one aspect relates to a system, method, apparatus, or computer-readable medium for inter-donor transfer and an apparatus, wherein a first network node may transmit / transmit / provide / signal / communicate information associated with an integrated access and backhaul (IAB) related transfer to a second network node.

[0005] In some embodiments, a first network node comprising a source donor can transmit information to a second network node comprising a target donor. The information can include at least one of an indication of a distributed unit (DU) movement, a counter value of a mobile terminated (MT) movement procedure, or an identification of a third network node having an F1 connection with the IAB-DU. In some embodiments, the method can include determining (e.g., by the source donor or the target donor) whether to perform a DU or user equipment (UE) movement according to the information. The method can include transmitting an indication of whether to perform a DU or UE movement to the third network node.

[0006] In some embodiments, the method may include determining whether to perform a DU or user equipment (UE) movement by comparing the counter value to a threshold number of MT movement procedures (e.g., MT movement operations / procedures). In some embodiments, the threshold number of MT movement procedures may be transmitted to at least one of the source donor or the target donor, or the IAB node.

[0007] In some embodiments, a first network node comprising an IAB node or a source donor of an IAB-MT or a source donor of a user equipment (UE) can transmit information to a second network node comprising a target donor. The information can include IP address request information or an indication of a mobility type. In some embodiments, the method / apparatus / computer-readable medium can include at least one of: the IP address request information can include at least one of a number of IP addresses for the IAB node, or an indicator of two sets of IP addresses, or the indication of a mobility type can include at least one of partial mobility, full mobility, distributed unit (DU) mobility, user equipment (UE) mobility, or F1 transport mobility.

[0008] In some embodiments, the first network node may transmit information to the second network node via a Radio Resource Control (RRC) message, an F1 Application Protocol (F1AP) message, or an Xn Application Protocol (XnAP) message. In some embodiments, the first network node comprising a donor centralization unit (CU) may transmit information to the second network node comprising an IAB node. The information may include an F1 setup indication instructing the IAB node to initiate an F1 setup procedure, a source logical DU indication indicating that the associated information is for a source logical DU, a target logical DU indication indicating that the associated information is for a target logical DU, a target donor IP address indicating an IP address of the target donor, a new IAB donor indication indicating that the associated information is for a new IAB donor, a type of movement type including at least one of partial movement, full movement, distributed unit (DU) movement, user equipment (UE) movement, or F1 transport movement, or at least one of one or more backhaul adaptation protocol (BAP) addresses.

[0009] In some embodiments, the first network node can transmit the information to the second network node via a Radio Resource Control (RRC) message or an F1 Application Protocol (F1AP) message. In some embodiments, the first network node comprising the first IAB donor can transmit the information to the second network node comprising the second IAB donor, or the first network node comprising the IAB node can transmit the information to the second network node comprising the second IAB donor.

[0010] In some embodiments, the information may include at least one of an IAB node identification, a target donor identification, a target cell identification, an indication of an IAB mobile terminated (IAB-MT) movement, an indication of an IAB distributed unit (IAB-DU) movement, or an indication of a user equipment (UE) movement. In some embodiments, at least one of: a first network node comprising an IAB node can transmit the information to a second network node comprising a second IAB donor, or a first network node comprising a first IAB donor can transmit the information to a second network node comprising a second IAB donor, or a first network node comprising a target donor can transmit the information to a second network node comprising a source donor. The source donor may transmit the information to the initial donor. In some embodiments, the information may include an old or source cell identifier (ID) of a distributed unit (DU) of the IAB node, and a new or target cell ID of the DU.

[0011] At least one embodiment relates to a system, method, apparatus, or computer-readable medium for inter-donor transfers and an apparatus, wherein a second network node can receive / obtain / search / collect information associated with an integrated access and backhaul (IAB) related transfer from a first network node. [Brief description of the drawings]

[0012] BRIEF DESCRIPTION OF THE DRAWINGS Various exemplary embodiments of the present solution are described in detail below in conjunction with the following figures or drawings. The drawings are provided for illustrative purposes only and merely illustrate exemplary embodiments of the present solution to facilitate the reader's understanding of the present solution. Thus, the drawings should not be considered as limiting the breadth, scope, or applicability of the present solution. It should be noted that for clarity and ease of illustration, the drawings are not necessarily drawn to scale.

[0013] [Figure 1] FIG. 1 illustrates an example of a cellular communication network in which the techniques disclosed herein may be implemented, according to one embodiment of the present disclosure.

[0014] [Diagram 2] FIG. 2 illustrates a block diagram of an example base station and a user equipment device according to some embodiments of the disclosure.

[0015] [Diagram 3] FIG. 3 illustrates a block diagram of an environment for mobile integrated access and backhaul (IAB), according to an exemplary embodiment.

[0016] [Figure 4A] FIG. 4A illustrates a block diagram of an integrated access and backhaul (IAB) architecture using a standalone (SA) mode with a next generation core (NGC), according to an example embodiment.

[0017] [Figure 4B] FIG. 4B illustrates a block diagram of an integrated access and backhaul (IAB) architecture using Evolved Universal Mobile Telecommunications System New Radio (EN-DC), according to an exemplary embodiment.

[0018] [Diagram 5]FIG. 5 illustrates a block diagram of integrated access and backhaul (IAB) nodes in a parent-child relationship according to an exemplary embodiment.

[0019] [Figure 6A] FIG. 6A illustrates a block diagram of an integrated access and backhaul (IAB) mobile termination (MT) moving from a first donor distribution unit (DU1) of a first centralization unit (CU1) to a second donor distribution unit (DU2) of a second donor centralization unit (CU2) according to an exemplary embodiment.

[0020] [Figure 6B] FIG. 6B illustrates a block diagram of an integrated access and backhaul (IAB) mobile termination (MT) moving from a second donor distribution unit (DU2) of a second donor concentration unit (CU2) to a third donor distribution unit (DU3) of a third donor concentration unit (CU3) according to an exemplary embodiment.

[0021] [Figure 6C] FIG. 6C illustrates a block diagram of an integrated access and backhaul (IAB) distribution unit (DU) moving from a first donor centralization unit (CU1) to a third donor centralization unit (CU3) according to an exemplary embodiment.

[0022] [Figure 7] FIG. 7 illustrates a flow diagram of a method for inter-donor transfer and apparatus, according to an exemplary embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0023] Detailed Description Various exemplary embodiments of the present solution will be described below with reference to the accompanying drawings to enable those skilled in the art to make and use the present solution. As will be apparent to those skilled in the art, after reading this disclosure, various changes or modifications can be made to the examples described herein without departing from the scope of the present solution. Thus, the present 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 approach. The specific order or hierarchy of steps of the disclosed methods or processes can be rearranged based on design preferences while remaining within the scope of the present solution. Thus, those skilled in the art will appreciate that the methods and techniques disclosed herein present various steps or operations in a sample order, and the present solution is not limited to the specific order or hierarchy presented unless otherwise specified.

[0024] 1. Mobile communications technology and environment FIG. 1 illustrates an example wireless communication network and / or system 100 in which the techniques disclosed herein may be implemented, according to an embodiment of the present disclosure. In the following description, 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 referred to herein as "network 100." Such an example network 100 includes a base station 102 (hereinafter BS 102, also referred to as a wireless communication node) and a user equipment device 104 (hereinafter UE 104, also referred to as a wireless communication device), which can communicate with each other via a communication link 110 (e.g., a wireless communication channel), as well as a cluster of cells 126, 130, 132, 134, 136, 138, and 140 overlapping a geographic region 101. In FIG. 1, the BS 102 and the UE 104 are included within the corresponding geographic boundaries of the cell 126. Each of the other cells 130, 132, 134, 136, 138 and 140 may include at least one base station operating in its assigned bandwidth to provide adequate wireless coverage to its intended users.

[0025] For example, the BS 102 may operate in an assigned channel transmission bandwidth to provide adequate coverage to the UE 104. The BS 102 and the UE 104 may communicate via downlink radio frames 118 and uplink radio frames 124, respectively. Each radio frame 118 / 124 may be further divided into subframes 120 / 127, which may include data symbols 122 / 128. In this disclosure, the BS 102 and the UE 104 are generally described herein as non-limiting examples of "communication nodes" capable of practicing the methods disclosed herein. Such communication nodes may be capable of wireless and / or wired communication in accordance with various embodiments of the present solution.

[0026] 2 illustrates a block diagram of an exemplary 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. System 200 may include components and elements configured to support known or conventional operational functions that need not be described in detail herein. In one exemplary embodiment, system 200 may be used to communicate (e.g., transmit and receive) data symbols in a wireless communication environment, such as wireless communication environment 100 of FIG. 1, as previously described.

[0027] 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 of which is coupled and interconnected with each other as needed 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 of which is coupled and interconnected with each other as needed via a data communication bus 240. The BS 202 communicates with the UE 204 over a communication channel 250, which may be any wireless channel or other medium suitable for the transmission of data as described herein.

[0028] As will be appreciated by those skilled in the art, system 200 may further include any number of modules other than those shown in FIG. 2. As will be appreciated by those skilled in the art, the various example 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. To clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, the various example components, blocks, modules, circuits, and steps are generally described in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software may depend on the particular application and design constraints imposed on the overall system. Those familiar with the concepts described herein may implement such functionality in an aspect suitable for each particular application, but such implementation decisions should not be construed as limiting the scope of the present disclosure.

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

[0030] The UE transceiver 230 and the base station transceiver 210 are configured to communicate over a wireless data communication link 250 and cooperate with a suitably configured RF antenna array 212 / 232 capable of supporting a particular wireless communication protocol and modulation scheme. In an exemplary embodiment, the UE transceiver 210 and the base station transceiver 210 are configured to support industry standards, such as the Long Term Evolution (LTE) standard and the emerging 5G standard. However, it is understood that the present disclosure is not necessarily limited to any particular standard and associated protocol. Rather, the UE transceiver 230 and the base station transceiver 210 may be configured to support alternative or additional wireless data communication protocols, including future standards or variants thereof.

[0031] According to various embodiments, the BS 202 may be, for example, an evolved Node B (eNB), a serving eNB, a target eNB, a femto station, or a pico station. In some embodiments, the UE 204 may be embodied in various types of user devices, such as a mobile phone, a smartphone, a personal digital assistant (PDA), a tablet, a laptop computer, a wearable computing device, etc. 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. Thus, the processor may be realized 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 combination of a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors in combination with a digital signal processor core, or any other such configuration.

[0032] Furthermore, the steps of the method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, firmware, software modules executed by the processor modules 214 and 236, respectively, or 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, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. In this regard, the memory modules 216 and 234 may be coupled to the processor modules 210 and 230, respectively, such that the processor modules 210 and 230 can read information from and write information to the memory modules 216 and 234, respectively. The memory modules 216 and 234 may be incorporated into their respective processor modules 210 and 230. In some embodiments, 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 the processor modules 210 and 230. Additionally, memory modules 216 and 234 may each include non-volatile memory for storing instructions to be executed by processor modules 210 and 230, respectively.

[0033] The network communication module 218 generally represents hardware, software, firmware, processing logic, and / or other components of the base station 202 that enable bidirectional communication between the base station transceiver 210 and other network components and communication nodes configured to communicate with the base station 202. For example, the network communication module 218 may be configured to support Internet or WiMAX traffic. In a typical deployment, without limitation, the network communication module 218 provides an 802.3 Ethernet interface to enable the base station transceiver 210 to communicate with a conventional Ethernet-based computer network. In this manner, the 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 conjugations thereof, as used herein with respect to a specified operation or function, refer to a device, component, circuit, structure, machine, signal, etc. that is physically configured, programmed, formatted, and / or arranged to perform the specified operation or function.

[0034] The Open Systems Interconnection (OSI) model (referred to herein as the "Open Systems Interconnection Model") is a conceptual and logical layout that defines the network communications used by systems (e.g., wireless communication devices, wireless communication nodes) that are open to interconnection and communication with other systems. The model is divided into seven subcomponents or layers, each of which represents a conceptual collection of services provided to its upper and lower layers. The OSI model also defines logical networks, which effectively describe computer packet forwarding by using protocols at different layers. The OSI model may be referred to as the seven-layer OSI model or 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 a non-access stratum (NAS) layer or an Internet Protocol (IP) layer, and the seventh layer is some other layer.

[0035] 2. Systems and methods for donor transfer and device Referring now to FIG. 3, a block diagram of an environment for mobile integrated access and backhaul (IAB) is shown. Integrated access and backhaul (IAB) may support wireless backhaul over new radio (NR) that allows flexible and very dense deployment of NR cells while reducing the need for wired transport infrastructure. Intra-donor centralized unit (CU) movement procedures may be provided in which both source parent node and target parent node are served by the same IAB donor-CU. However, inter-donor CU movement in a moving (mobile) IAB node may be static. As shown, it may be difficult to perform inter-donor movement in a mobile IAB usage scenario. In a mobile IAB use case, an IAB node may be mounted in a vehicle and provide coverage and capacity expansion to on-board or surrounding user equipment (UE).

[0036] Referring now to FIG. 4A, a block diagram of an integrated access and backhaul (IAB) architecture using a standalone (SA) mode with a next-generation core (NGC) is shown. Integrated access and backhaul (IAB) may enable wireless relaying in NG-RAN. Relay nodes, referred to as IAB nodes, may support access and backhaul over NR. The NR backhaul termination node on the network side may be referred to as an IAB donor, which may represent a gNB with additional functionality to support IAB. Backhauling may be via a single hop or multiple hops.

[0037] An IAB node, on an IAB donor, may 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 functionality. The gNB-DU functionality on an IAB node may also be referred to as an IAB Distributed Unit (DU) (IAB-DU). In addition to the gNB-DU functionality, an IAB node may also support a subset of UE functionality referred to as IAB Mobile Termination (MT), including, for example, physical layer, Layer 2, Radio Resource Control (RRC), and Non-Access Stratum (NAS) functionality for connecting to gNB-DUs of other IAB nodes or IAB donors, connecting to a gNB-CU on the IAB donor, and connecting to the core network, among others.

[0038] Referring now to FIG. 4B, a block diagram of an Integrated Access and Backhaul (IAB) architecture with Evolved Universal Mobile Telecommunications System New Radio (EN-DC) is shown. IAB nodes can access the network using either SA mode or EN-DC. In EN-DC, IAB nodes also connect to the MeNB via E-UTRA, and the IAB donor terminates X2-C as an SgNB (e.g., as defined in TS 37.340).

[0039] Now referring to FIG. 5, a block diagram of an integrated access and backhaul (IAB) node in a parent-child relationship is shown. All IAB nodes connected to an IAB donor through one or more hops can form a directed acyclic graph (DAG) topology with the IAB donor at its root. In this DAG topology, the adjacent node on the IAB-DU interface may be referred to as a child node, and the adjacent node on the IAB-MT interface is referred to as a parent node. The direction toward the child node may further be referred to as downstream, and 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.

[0040] Referring to FIG. 6A, a block diagram of an integrated access and backhaul (IAB) mobile termination (MT) moving from a first donor distribution unit (DU1) of a first centralized unit (CU1) to a second donor distribution unit (DU2) of a second donor centralized unit (CU2) is shown. As shown, the mobile IAB-MT may move from donor DU1 (belonging to donor CU1) to donor DU2 (belonging to donor CU2). However, the mobile IAB-DU may maintain its F1 connection with donor CU1, and the UE context can remain in / with donor CU1. F1-C / U traffic between donor CU1 and the mobile IAB-DU may be transmitted via donor DU2.

[0041] Referring to FIG. 6B, a block diagram of an integrated access and backhaul (IAB) mobile termination (MT) moving from a second donor distribution unit (DU2) of a second donor centralized unit (CU2) to a third donor distribution unit (DU3) of a third donor centralized unit (CU3) is shown. As shown, the mobile IAB-MT may move from donor DU2 (belonging to donor CU2) to donor DU3 (belonging to donor CU3). However, the mobile IAB-DU may maintain its F1 connection with donor CU1, and the UE context can remain in / with donor CU1. F1-C / U traffic between donor CU1 and the mobile IAB-DU may be transmitted via donor DU3.

[0042] Referring to Figure 6C, a block diagram of an integrated access and backhaul (IAB) distributed unit (DU) moving from a first donor centralized unit (CU1) to a third donor centralized unit (CU3) is shown. As shown, a mobile IAB-DU may move from donor CU1 to donor CU3. A UE may be handed over (or handed over / moved / switched) from donor CU1 to donor CU3. F1-C / U traffic between donor CU3 and the mobile IAB-DU may be transmitted via donor DU3.

[0043] As shown in FIG. 6A-6C, each donor CU may be associated with or correspond to at least one of a source IAB donor, a target IAB donor, or an initial IAB donor. For example, a source IAB donor may represent a donor that includes a donor DU already connected to or in communication with a mobile IAB-MT or UE 104. A target IAB donor may represent a donor CU to which a mobile IAB-MT or UE has moved. An initial IAB donor may represent at least one IAB donor that has an F1-C connection with a mobile IAB node, or one IAB donor that is a source IAB donor for the UE, or one IAB donor that is serving the UE 104 (e.g., a gNB, a BS 102, or a donor CU serving the UE 104). Hereinafter, a mobile IAB node and / or a mobile IAB-DU may be generally referred to as an IAB node and / or an IAB-DU, respectively.

[0044] I. Embodiment 1: Determining whether to perform DU / UE mobility In various embodiments, a DU (e.g., IAB-DU) movement and / or a UE 104 movement may be performed following or after an IAB-MT movement, or before an IAB-MT movement. The IAB-MT and IAB-DU may be part of an IAB entity (e.g., a donor or node) (e.g., a BS 102, a gNB, or a network node). Because a DU / UE movement may be performed before or after an IAB-MT movement, it may be difficult to determine who (e.g., which network node) and how (e.g., an operation, method, or procedure) performs a DU movement and / or a UE movement (e.g., a DU / UE movement). A DU movement may refer to an IAB-DU movement. A UE movement may refer to a UE 104 movement. The systems and methods described herein may determine at least one IAB entity (e.g., a network node) to determine whether a DU / UE movement should be performed and / or how the IAB entity triggers a DU / UE movement. The decision of who and how to trigger a DU / UE movement can be based on or follow the number of IAB-MT movement procedures / operations (e.g., how many MT movements have been performed by the IAB node and / or IAB-DU) performed after a previous movement of a co-located IAB-DU (e.g., the IAB-DU is co-located with the IAB-MT in the IAB node). Thus, based on the number of IAB-MT movements, the IAB-DU can decide / decide whether to perform a DU / UE movement. In various embodiments, based on the examples / contexts detailed herein, the first, second, or third network node, among other network nodes, can be described as or correspond to an IAB node or an IAB donor.

[0045] For example, a source donor (e.g., a source CU or a first network node, such as shown in connection with at least one of FIGS. 6A-6C) may transmit / send / provide / signal MT mobility related information (e.g., contained / contained in the history information of the UE 102) to a target donor (e.g., a target CU of a second network node). The MT mobility related information may include at least one of the following: 1) DU Move Indication / Flag. The DU Move Indication may indicate that a DU / UE move is performed when (e.g., occurrence or time frame) a co-located IAB-MT of an IAB node moves from or to a corresponding cell (e.g., a cell associated with a source donor). 2) A counter (e.g., a counter value) of an IAB-MT transfer procedure. The counter value may be incremented by 1 (e.g., among other preconfigured increment values) before / during / after an IAB-MT transfer performed by the source donor and / or target donor of the IAB-MT. The counter value may be reset to 0 before / during / after a transfer of a co-located IAB-DU; and / or 3) Identification of an initial IAB donor (e.g., a third network node). The initial IAB donor may, for example, include an F1 connection with an IAB-DU. The identification of the initial donor may include or correspond to a gNB-ID, among other identities.

[0046] In response to transmitting and / or receiving information (e.g., MT movement related information) from the source donor, the source donor and / or target donor associated with the IAB-MT may determine whether to perform a DU / UE movement. For example, the source donor and / or target donor may compare the counter value to a threshold (e.g., a threshold number of MT movement procedures to be performed). The threshold may be determined / configured based on the implementation, such as set to 2, 3, 4, or other threshold. The threshold may be configured, for example, via operations, administration, and maintenance (OAM) signaling to one or more IAB nodes or IAB donors. If the counter value is equal to or greater than the threshold, the source donor and / or target donor may transmit / send / provide / signal a DU / UE movement indication to the initial donor.

[0047] In a further example, referring to Figures 6A-6C, the threshold number may be configured as 2. The counter value may be incremented in response to an MT move (e.g., by at least one of the IAB entities). When an IAB-MT moves to a donor DU3, the counter value may be incremented to 2, which is equal to the threshold. Thus, the source donor and / or target donor receiving the information may decide to perform a DU / UE move according to the counter value being equal to or greater than the threshold.

[0048] In some cases, the threshold number of MT mobility procedures may be coordinated / communicated between donor CUs (e.g., between the first, second, and / or third donor CUs, etc.) via XnAP signaling. For example, at least one donor CU may transmit an indication of the threshold to one or more other donor CUs via a handover request or retrieve a UE context response message. This message may be sent together with or as part of the UE's historical information. The threshold number of MT mobility procedures may be configured / updated / provided to the IAB node via RRC and / or F1AP signaling.

[0049] II. Embodiment 2: Determining the Move Type to be Performed for IAB Node Movement In various implementations, there may be different types of mobility procedures / operations such as partial mobility, full mobility, DU mobility, UE mobility, F1 transport mobility, among others. Thus, in these implementations, the IAB donor (e.g., target donor or target CU) needs to be informed / informed or aware of the mobility type of the IAB node mobility to be performed.

[0050] For example, a target donor (e.g., a target donor of a second network node) may receive / obtain IAB mobility-related information from at least one of the IAB nodes or other IAB-CUs (e.g., source CU or initial CU) (e.g., the first network node). The IAB mobility-related information may include at least one of the following information: 1) IP address request information (e.g., acting as an implicit indication). The IP address request information may include at least one of a number of IP addresses for the IAB node and / or an indicator of two sets of IP addresses. The indicator of two sets of IP addresses may indicate that two sets of IP addresses are required (or not required). For example, the request for two sets of IP addresses may be an indication to perform at least one of a full mobility procedure, a DU mobility procedure, and / or a UE mobility procedure, among other mobility types. 2) An indication of a mobility type (e.g., acting as an explicit indication). This indication may include or be used to indicate a type of mobility, such as at least one of partial mobility, full mobility, DU mobility, UE mobility, and / or F1 transport mobility, among others. A partial mobility may include a mobility / handover / switch of an IAB-MT to a parent node under a different IAB donor-CU or a parent node associated with a different IAB donor-CU, and the co-located IAB-DU and / or descendant IAB nodes (e.g., if any) may terminate at the initial IAB donor-CU. A full mobility may include a mobility of a border IAB node and / or descendant IAB node (e.g., both RRC and F1 connections) from a first IAB donor CU to a second IAB donor CU. A DU mobility may include a mobility of an IAB-DU from one IAB donor to another IAB donor. A UE mobility may include a mobility of a UE 104 from one Radio Access Network (RAN) node to another RAN node. F1 transport migration may include migration of the transport path of F1 traffic from one path to another.

[0051] In some cases, the IAB node (e.g., the first network node) may transmit / send the IAB mobility related information to the target donor via a Radio Resource Control (RRC) message and / or an F1 Application Protocol (F1AP) message. In some cases, the other IAB-CU (e.g., the first network node) may transmit the IAB mobility related information to the target donor via an XnAP message (e.g., an XnAP Handover Request or an IAB Transport Mobility Management Request message).

[0052] III. Embodiment 3: Informing IAB Node of DU / UE Mobility In various embodiments, various types of mobility procedures may be presented, such as partial mobility, full mobility, DU mobility, UE mobility, F1 transport mobility, among others. Therefore, the IAB node needs to be informed / informed / instructed / triggered (e.g., via specific signaling) to perform / initiate / continue the mobility of the DU / UE.

[0053] For example, an IAB node (e.g., a second network node) may receive IAB-related configuration information from a donor CU (e.g., a source donor, a target donor, an initial donor, and / or another IAB donor) via RRC and / or F1AP signaling. The IAB-related configuration information may include at least one of the following: 1) F1 Setup Indication: This indication may instruct an IAB node to initiate F1 setup procedures / actions. 2) F1 switch indication: This indication may instruct the IAB node to initiate an F1 switch procedure / action. 3) Source logical DU indication: This indication may indicate that the associated information (e.g., IAB-related configuration information) is related to the source logical DU (e.g., there may be multiple logical DUs in an IAB node, such as source logical DU, target logical DU, etc.). 4) Target logical DU indication: This indication may indicate that the associated information is related to, applicable to, or belongs to the target logical DU. 5) Target donor (e.g., target CU) IP address. This IP address may indicate or represent the IP address of the target donor. 6) A new IAB donor indication. This indication may indicate that the associated information is for a new IAB donor (e.g., a third network node or another network node). 7) A move type indication, which may indicate the type of move (e.g., move type) to be performed, such as at least one of a partial move, a full move, a DU move, a UE move, and / or an F1 transport move; and / or 8) One or more Backhaul Adaptation Protocol (BAP) addresses. One or more BAP addresses may be assigned to the IAB node by the donor CU, such as one BAP address for each logical DU.

[0054] IV. Embodiment 4: Triggering DU / UE Movement in the Initial Donor CU In various embodiments, various types of mobility procedures may be proposed / introduced, such as partial mobility, full mobility, DU mobility, UE mobility, F1 transport mobility, etc. Thus, for example, at the initial donor (e.g., an initial CU connected to or in communication with the IAB-DU), there may be different procedures / actions / alternatives for triggering a DU / UE mobility. One or more of the following actions or procedures may be performed:

[0055] A) Triggered by the source donor (e.g., source CU) of the IAB-MT In some cases, the movement of the DU / UE may be triggered by a source donor associated with or in communication with the IAB-MT. For example, the source donor (e.g., a first network node or a first IAB donor) may transmit / send / provide IAB-related information to an initial IAB donor (e.g., a second network node or a second IAB donor). In this case, the IAB-related information may include at least one of the following: 1) Identifying IAB nodes; 2) identification of the targeted IAB donor (e.g., targeted donor or targeted CU); 3) identification of target cells (e.g., cells associated with the target donor); 4) indication of IAB-MT movement (sometimes referred to as MT movement); 5) Indication of IAB-DU movement; and / or 6) Indication of UE movement.

[0056] B) Triggered by a targeted donor (e.g., targeted CU) in the IAB-MT Additionally or alternatively, the DU / UE movement may be triggered by a target donor of the IAB-MT. For example, the target donor (e.g., a first network node or a target CU of a first IAB donor) may send / transmit IAB-related information to an initial IAB donor (e.g., a second network node or a second IAB donor). The IAB-related information may include at least one of the following: 1) Identifying IAB nodes; 2) target cell identification; 3) indication of IAB-MT movement; 4) Indication of IAB-DU movement; and / or 5) Display of UE movement.

[0057] C) Triggered by IAB nodes Additionally or alternatively, the movement of the DU / UE may be triggered by an IAB node. For example, the IAB node (e.g., a first network node) may send IAB-related information to an initial IAB donor (e.g., a second network node). In this case, the IAB-related information may include at least one of the following: 1) Identification of targeted IAB donors; 2) target cell identification; 3) indication of IAB-MT movement; 4) Indication of IAB-DU movement; and / or 5) Display of UE movement.

[0058] V. Embodiment 5: Determining New / Target Cell ID of IAB-DU Cell Serving UE In various embodiments, an initial donor (e.g., initial CU) may send / transmit / signal an Xn handover request message to a target donor (e.g., target CU) to initiate a mobility procedure for one or more UEs 104. A target cell identification / identifier (ID) may be included in the Xn handover request message. However, the initial donor may not be aware of the new / target cell ID of the IAB-DU cell serving the UE 104. Thus, one or more IAB entities (e.g., IAB nodes and / or other IAB donors) may inform / indicate / signal the initial donor of the new / target cell ID.

[0059] For example, an IAB node (e.g., a first network node comprising an IAB node) may send / transmit information including an old / source cell ID and / or a corresponding new / target cell ID of an IAB-DU (e.g., a DU of the IAB node) to an initial donor (e.g., a second network node comprising a second IAB donor). The IAB node may transmit the information via RRC and / or F1AP. Additionally or alternatively, a target donor (e.g., a first network node comprising a target CU or a first IAB donor) may transmit the information (e.g., an old and / or a corresponding new / target cell ID of an IAB-DU) to an initial donor CU.

[0060] Additionally or alternatively, the target donor (e.g., the target CU or the first network node comprising the target donor) may transmit information (e.g., the old corresponding new / target cell ID of the IAB-DU) to the source donor (e.g., the source CU or the second network node comprising the source donor). In this case, the source donor may transmit / forward the information to the initial donor (e.g., the third network node comprising the initial donor). Based on the information transmitted, received or communicated between one or more IAB entities (e.g., the IAB node and / or the IAB donor), the DU / UE mobility procedure may be performed accordingly.

[0061] Referring now to FIG. 7, a flow diagram of a method 700 of inter-donor mobility and apparatus is shown. The method 700 may be implemented using or performed by any of the components detailed above, such as the UE 104 or 204 and the BS 102 or 202, among others. In overview, a first network node (e.g., a network entity such as an IAB node or an IAB donor) may transmit information (702). A second network node (e.g., another network entity such as another / different IAB donor or an IAB node) may receive information (704). The second network node may determine whether to perform a mobility (e.g., a DU / UE mobility procedure) (706). The second network node may transmit an indication (708). A third network node may receive the indication (710).

[0062] In more detail, a first network node (e.g., a network entity, a communication node, a BS, or a gNB) may transmit / provide / transmit / signal information to a second network node (702). The first network node, the second network node, and / or the third network node may include / comprise one of an IAB node or an IAB donor, which may be used interchangeably to describe other IAB entities described herein. The information may be associated with an IAB related movement. The second network node may receive the information from the first network node (704).

[0063] In some embodiments, the first network node may include a source donor. The first network node may transmit / transmit / provide information to a second network node that includes a target donor. The information may include at least one of an indication of DU movement, a counter value (e.g., indicating the number / occurrences or count of occurrences) of the MT movement procedure, and / or an identification (ID) of a third network node that has an F1 connection with the IAB-DU.

[0064] In various embodiments, the first network node may include an IAB node or a source donor of an IAB-MT or a source donor of a UE (e.g., a communication device). The first network node may transmit information to a second network node. The second network node may include a target donor (e.g., a target donor CU). The information may include at least one of IP address request information and / or an indication of a mobility type. The IP address request information may include at least one of a number of IP addresses of the IAB node and / or an indicator of the two sets of IP addresses. The mobility type indication may include at least one of partial mobility, full mobility, distributed unit (DU) mobility, user equipment (UE) mobility, and / or F1 transport mobility. In some embodiments, the first network node may transmit information to the second network node via a radio resource control (RRC) message, an F1 application protocol (F1AP) message, and / or an Xn application protocol (XnAP) message.

[0065] In some implementations, the first network node may include or correspond to a donor CU. The second network node may include or correspond to an IAB node. The first network node may transmit / send information to a second network node comprising an IAB node. In this case, the information may include at least one of a F1 setup indication instructing the IAB node to initiate an F1 setup procedure, a source logical DU indication indicating that the associated information is for a source logical DU, a target logical DU indication indicating that the associated information is for a target logical DU, a target donor IP address indicating an IP address of the target donor, a new IAB donor indication indicating that the associated information is for a new IAB donor, a type of mobility type that may include at least one of partial mobility, full mobility, distributed unit (DU) mobility, user equipment (UE) mobility, or F1 transport mobility, and / or one or more backhaul adaptation protocol (BAP) addresses. In some aspects, the first network node may transmit information to the second network node via an RRC message and / or an F1AP message.

[0066] In some cases, the first network node may include a first IAB donor. The first node may transmit the information to a second network node, which may include a second IAB donor. In some cases, the first network node may include an IAB node. The first network node may transmit the information to a second network node, which may include a second IAB donor. In one or more of these cases, the information may include at least one of an IAB node identification, a target donor identification, a target cell identification, an indication of IAB-MT movement, an indication of IAB-DU movement, and / or an indication of UE movement.

[0067] In some aspects, the first network node may include an IAB node. The first network node may transmit the information to a second network node, which may include a second IAB donor. In some other aspects, the first network node may include a first IAB donor. The first network node may transmit the information to a second network node, which may include a second IAB donor. In still other aspects, the first network node may include a target donor. The first network node may transmit the information to a second network node, which may include a source donor. In this case, the source donor may transmit the information to an initial donor (e.g., the second IAB donor, or another (e.g., third) network node that includes the initial donor). In one or more of these cases, the information may include an old or source cell identifier (ID) of the DU of the IAB node, and / or a new or target cell ID of the DU.

[0068] After receiving the information, the second network node (e.g., including one of the source donor or the target donor) can determine whether to perform a DU or UE (e.g., DU / UE) movement according to the information (706). For example, the information may include a counter value indicating the number of MT movement procedures to be performed. The second network node (and / or other network node) can compare the counter value with a threshold number (or a predetermined number) of MT movement procedures (e.g., MT movement occurrences). By comparing the counter value with the threshold number, the second network node can determine whether to perform a DU / UE movement.

[0069] For example, the second network node may decide to perform a DU / UE move based on the counter value being equal to or greater than the threshold number. According to certain embodiments, the second network node may decide not to perform a DU / UE move based on the counter value being less than the threshold number, or vice versa. In some embodiments, the threshold number of MT move procedures may be transmitted / transmitted / provided to at least one of the source donor, the target donor, and / or the IAB node.

[0070] Based on the determination, the second network node (e.g., source donor or target donor) may send an indication / message to a third network node regarding whether to perform a movement of the DU or UE (708). The third network node (e.g., an initial donor or other donor having an F1 connection with the IAB-DU of the IAB node) may receive the indication from the second network node (710). Thus, the third network node (and / or one or more other network nodes) may perform a movement of the DU or UE based on information communicated to, from, or between the one or more network nodes.

[0071] Although various embodiments of the present solution have been described above, it should be understood that the embodiments are presented only as examples and not as limitations. Similarly, various diagrams may depict exemplary architectures or configurations, which are provided to enable those skilled in the art to understand exemplary features and functionality of the present solution. However, such skilled in the art will 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 will be understood by those skilled in the art, one or more features of one or more embodiments / implementations can be combined with one or more features of other embodiments / implementations described herein. Thus, the scope and scope of the present disclosure should not be limited by any of the exemplary embodiments described above.

[0072] It is also understood that any reference to an element herein using a designation such as "first," "second," etc., does not generally limit the quantity or order of those elements. Rather, these designations may be used herein as a convenient means of distinguishing between two or more elements or instances of an element. Thus, a reference to a first element and a second element does not imply that only two elements can be used or that the first element must precede the second element in some manner.

[0073] Additionally, those skilled in the art will understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, the data, instructions, commands, information, signals, bits and symbols that may be referred to in the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0074] Moreover, as will be appreciated by those skilled in the art, any of the various exemplary 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 implementations, analog implementations, or a combination of the two), firmware, various forms of programs or design codes incorporating instructions (which may be conveniently referred to herein as "software" or "software modules"), or any combination of these technologies. To clearly illustrate this interchangeability of hardware, firmware, and software, various exemplary components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software, or a combination of these technologies, depends on the particular application and design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in various ways for each particular application, but such implementation decisions do not cause a departure from the scope of the present disclosure.

[0075] Further, those skilled in the art will appreciate that the various exemplary logic blocks, modules, devices, components, and circuits described herein can be implemented in or performed by an integrated circuit (IC), which can 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 device, or any combination thereof. The logic blocks, modules, and circuits can further include an antenna and / or a transceiver for communicating with various components in a network or device. The general purpose processor can be a microprocessor, but alternatively, the processor can be any conventional processor, controller, or state machine. The processor can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other suitable configuration for performing the functions described herein.

[0076] If implemented in software, the functions can be stored as one or more instructions or codes on a computer-readable medium. Thus, the steps of a method or algorithm disclosed herein can be implemented as software stored on a computer-readable medium. Computer-readable media includes both computer storage media and communication media, including any medium that can enable a computer program or code to be transferred from one place to another. A storage medium can be any available medium that can be accessed by a computer. By way of example and not limitation, 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.

[0077] As used herein, the term "module" refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. Additionally, for purposes of explanation, various modules are described as individual modules; however, as will be apparent to one of ordinary skill in the art, two or more modules may be combined to form a single module that performs associated functions according to embodiments of the present solution.

[0078] Furthermore, memory or other storage devices, as well as communication components, may be used in embodiments of the solution. For clarity, it will be appreciated that the above description describes embodiments of the solution with reference to various functional units and processors. However, it will be apparent that any suitable distribution of functionality between different functional units, processing logic elements, or domains may be used without detracting from the solution. For example, functionality illustrated as being performed by separate processing logic elements or controllers may be performed by the same processing logic element or controller. Thus, references to specific functional units do not indicate a strict logical or physical structure or organization, but merely to suitable means for providing the described functionality.

[0079] Various modifications to the embodiments described in this disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the scope of the present disclosure. Thus, the present disclosure is not intended to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the novel features and principles disclosed herein, as recited in the following claims.

Claims

1. transmitting, by a first network node, information associated with an integrated access and backhaul (IAB) associated mobility to a second network node; A method comprising:

2. transmitting said information by said first network node comprising a source donor to said second network node comprising a target donor; The information is Distributed Unit (DU) Movement Indication, the counter value of the mobile terminated (MT) mobility procedure, or Identification of a third network node having an F1 connection with the IAB-DU The method of claim 1 , comprising at least one of:

3. determining whether to perform a DU or user equipment (UE) movement according to the information; sending to the third network node an indication of whether the DU or UE mobility should be performed; The method of claim 2 , comprising:

4. determining whether to perform a DU or user equipment (UE) movement by comparing the counter value with a threshold number of MT movement procedures; The method of claim 2 , comprising:

5. The threshold number of MT movement procedures is At least one of the source donor or the target donor, or IAB Node The method of claim 4 , wherein the first and second signals are transmitted to the second and third parties.

6. transmitting the information by the first network node comprising an IAB node or an IAB-MT source donor or a user equipment (UE) source donor to the second network node comprising a target donor; The information includes IP address requirement information or an indication of a mobility type. The method of claim 1.

7. the IP address request information includes at least one of a number of IP addresses for the IAB node, or an indicator of two sets of IP addresses; or The indication of the mobility type includes at least one of partial mobility, full mobility, distributed unit (DU) mobility, user equipment (UE) mobility, or F1 transport mobility. The method of claim 6, wherein the at least one of

8. transmitting, by the first network node, the information to the second network node via a Radio Resource Control (RRC) message, an F1 Application Protocol (F1AP) message, or an Xn Application Protocol (XnAP) message; The method of claim 6, comprising:

9. transmitting, by the first network node comprising a donor centralization unit (CU), the information to the second network node comprising an IAB node; The information is an F1 setup indication instructing the IAB node to initiate an F1 setup procedure; a source logical DU indication indicating that the associated information relates to a source logical DU; a target logical DU indication indicating that the associated information relates to a target logical DU; a target donor IP address indicating the IP address of the target donor; a new IAB donor indication indicating that the associated information is for a new IAB donor; A type of mobility type including at least one of partial mobility, full mobility, distributed unit (DU) mobility, user equipment (UE) mobility, or F1 transport mobility; or One or more Backhaul Adaptation Protocol (BAP) addresses The method of claim 1 , comprising at least one of:

10. transmitting, by the first network node, the information to the second network node via a Radio Resource Control (RRC) message or an F1 Application Protocol (F1AP) message; 10. The method of claim 9, comprising:

11. transmitting said information by said first network node comprising a first IAB donor to said second network node comprising a second IAB donor; or transmitting, by the first network node comprising an IAB node, the information to the second network node comprising the second IAB donor; The method of claim 1 , comprising one of:

12. The information is An identity of the IAB node; Identification of the targeted donor; Identification of the target cell; IAB Mobile Terminated (IAB-MT) Movement Indication; Indication of an IAB Distributed Unit (IAB-DU) movement, or Indication of User Equipment (UE) Movement The method of claim 11 , comprising at least one of:

13. transmitting said information by said first network node comprising an IAB node to said second network node comprising a second IAB donor; or transmitting said information by the first network node comprising a first IAB donor to the second network node comprising the second IAB donor; or transmitting said information by said first network node comprising a target donor to said second network node comprising a source donor. one of The method of claim 1 , wherein the source donor transmits the information to an initial donor.

14. The method of claim 13 , wherein the information includes an old or source cell identifier (ID) of a distribution unit (DU) of the IAB node and a new or target cell ID of the DU.

15. receiving, by a second network node, information associated with an integrated access and backhaul (IAB) associated mobility from the first network node; A method comprising:

16. 16. A non-transitory computer-readable storage medium having instructions stored thereon that, when executed by one or more processors, cause the one or more processors to perform the method of any one of claims 1 to 15.

17. A device comprising at least one processor configured to perform the method of any one of claims 1 to 15.

Images