Inter-host cell management in wireless communication networks

Abstract

Various aspects relate to techniques and methods for migrating a radio access network (RAN) node associated with a first host node in a communication network. The first host node may receive cell configuration data associated with one or more cells of the RAN node activated by the first host node via a first communication interface, such as an F1-C or resource control (RRC) interface. The first host node may process the cell configuration data and transmit the cell configuration data to a second host node using a second communication interface, such as an Xn or X2 interface, for migrating the RAN node from the first host node to the second host node.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to Non-Provisional Application No. 17 / 239,432 filed in the U.S. Patent Office on April 23, 2021 and Provisional Application No. 63 / 018,425 filed in the U.S. Patent Office on April 30, 2020, the contents of which are incorporated herein by reference as if fully set forth below and for all applicable purposes. Technical Field

[0003] The techniques discussed below relate generally to wireless communication networks, and more particularly, to techniques and methods for inter-donor cell management in wireless communication networks, such as integrated access and backhaul (IAB) networks. Background Art

[0004] In a 5G new radio wireless communication network, resources can be shared between an access network and a backhaul network. For example, a wireless spectrum can be used for an access link (e.g., a link between a base station and a user equipment (UE)) and a backhaul link (e.g., a link between a base station and a core network). In such an integrated access backhaul (IAB) network, base station functions can be logically divided into a central unit (CU) and one or more distributed units (DUs). The CU hosts the radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) layers that control the operation of one or more DUs. The DU hosts the radio link control (RLC), media access control (MAC), and physical (PHY) layers. In an example IAB network architecture, the CU can be implemented at an edge IAB node, which can be referred to as an IAB host node. The DU can be co-located with the CU and / or distributed across multiple base stations or other radio access network (RAN) nodes within the IAB network.

[0005] The CU and DU are connected via the F1 interface, which uses the F1 application protocol (F1-AP) to transfer information between the CU and DU. Neighboring nodes (e.g., gNBs) can communicate via the X2 or Xn interface. Enhancements to IAB cell management continue to be developed to support the functions and features of the IAB network. Summary of the invention

[0006] An overview of one or more aspects of the present disclosure is given below to provide a basic understanding of these aspects. This overview is not an extensive review of all expected features of the present disclosure, and is neither intended to identify key or important elements of all aspects of the present disclosure, nor is it intended to describe the scope of any or all aspects of the present disclosure. Its sole purpose is to present some concepts of one or more aspects of the present disclosure in some form as a preface to a more detailed description presented later.

[0007] In one example, a method of migrating a radio access network (RAN) node associated with a first host node in a communication network is disclosed. The method includes receiving, in the first host node via a first communication interface, cell configuration data associated with the RAN node, the cell configuration data including data associated with one or more cells of the RAN node activated by the first host node. The method may also include processing the cell configuration data to migrate the one or more cells to a second host node; and sending the processed cell configuration data to the second host node via a second communication interface for migrating the RAN node from the first host node to the second host node.

[0008] Another example provides a first host node in a wireless communication network. The first host node may include a first communication interface, a second communication interface, a memory, and a processor communicatively coupled to the transceiver and the memory. The processor and the memory may be configured to receive cell configuration data associated with a RAN node via the first communication interface in the first host node, the cell configuration data including data associated with one or more cells of the RAN node activated by the first host node. The processor and the memory may also be configured to process the cell configuration data to migrate one or more cells to a second host node; and send the processed cell configuration data to the second host node via the second communication interface for migrating the RAN node from the first host node to the second host node.

[0009] Another example provides a first host node in a wireless communication network, wherein the first host node includes a component for receiving cell configuration data associated with a RAN node via a first communication interface in the first host node, the cell configuration data including data associated with one or more cells of the RAN node activated by the first host node. The host node may also include a component for processing the cell configuration data to migrate the one or more cells to a second host node; and a component for sending the processed cell configuration data to the second host node via a second communication interface for migrating the RAN node from the first host node to the second host node.

[0010] Another example provides a computer-readable medium storing instructions executable by one or more processors of a first host node to perform the following operations: receiving cell configuration data associated with a RAN node via a first communication interface in the first host node, the cell configuration data including data associated with one or more cells of the RAN node activated by the first host node; processing the cell configuration data to migrate the one or more cells to a second host node; and sending the processed cell configuration data to the second host node via a second communication interface for use in migrating the RAN node from the first host node to the second host node.

[0011] By reading the following detailed description, these and other aspects of the present invention will be more fully understood. By reading the following description of the specific exemplary examples of the present invention in conjunction with the accompanying drawings, it will be clear to those of ordinary skill in the art that other aspects, features and examples of the present invention. Although the features of the present invention can be discussed relative to some of the following examples and the accompanying drawings, all examples of the present invention can include one or more advantageous features discussed herein. In other words, although one or more examples can be discussed as having certain advantageous features, one or more such features can also be used according to the various examples of the present invention discussed herein. In a similar manner, although the exemplary examples can be discussed below as equipment, system or method examples, it should be understood that such exemplary examples can be implemented in various equipment, systems and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1 is a schematic diagram of a wireless communication system according to some aspects;

[0013] Figure 2 is a conceptual illustration of an example of a radio access network according to some aspects;

[0014] Figure 3 is a schematic diagram illustrating the organization of radio resources in an air interface utilizing orthogonal frequency division multiplexing (OFDM) according to some aspects;

[0015] Figure 4 is a block diagram illustrating a wireless communication system supporting beamforming and / or multiple-input multiple-output (MIMO) communications according to some aspects;

[0016] Figure 5 is a diagram providing a high-level illustration of one example of a network configuration including an integrated access backhaul (IAB) network according to some aspects;

[0017] Figure 6 is a diagram illustrating an example of IAB node functionality in an IAB network according to some aspects;

[0018] Figure 7 is a diagram illustrating an example of an NR cell global identification signal according to some aspects;

[0019] Figure 8 is a diagram illustrating cell activation between two nodes on an Xn link according to some aspects;

[0020] Fig. 9 is a diagram illustrating a high-level example of inter-gNB handover according to some aspects;

[0021] Fig.10 is a diagram illustrating migration of an IAB node from one IAB host to another IAB host according to some aspects;

[0022] Fig.11 is a block diagram illustrating an example of a hardware implementation of an IAB node employing a processing system according to some aspects;

[0023] Fig.12 is a flow chart illustrating a process for migrating a RAN node from a first donor node to a second donor node according to some aspects; and

[0024] Fig.13 is a flow chart illustrating another process for migrating a RAN node from a first donor node to a second donor node according to some aspects. DETAILED DESCRIPTION

[0025] In conjunction with the accompanying drawings, the detailed description set forth below is intended as a description of various configurations and is not intended to represent the only configuration in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0026] Although aspects and examples are described in this application by way of illustration of some examples, it will be understood by those skilled in the art that additional implementations and use cases may occur in many different arrangements and scenarios. The innovations described herein may be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, examples and / or uses may be implemented by integrated chip examples and other devices based on non-module components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial devices, retail / purchasing devices, medical devices, AI-enabled devices, etc.). Although some examples may or may not be specific to use cases or applications, a variety of applicability of the described innovations may occur. The range of implementations may range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or OEM devices or systems that include one or more aspects of the innovation. In some practical settings, devices including the described aspects and features may also have to include additional components and features for implementing and practicing the claimed and described examples. For example, the transmission and reception of wireless signals must include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.) The innovations described herein can be implemented in a variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc., of various sizes, shapes, and configurations.

[0027] The various concepts presented throughout this disclosure may be implemented across a variety of telecommunication systems, network architectures and communication standards. Figure 1 , various aspects of the present disclosure are described with reference to a wireless communication system 100 as a non-limiting illustrative example. The wireless communication system 100 includes three interacting domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106. By means of the wireless communication system 100, the UE 106 may be able to perform data communications with an external data network 110 (such as, but not limited to, the Internet).

[0028] The RAN 104 may implement any suitable wireless communication technology or technologies to provide wireless access to the UE 106. As an example, the RAN 104 may operate in accordance with the 3rd Generation Partnership Project (3GPP) New Radio (NR) specification, commonly referred to as 5G. As another example, the RAN 104 may operate under a mix of 5G NR and Evolved Universal Terrestrial Radio Access Network (eUTRAN) standards, commonly referred to as Long Term Evolution (LTE). 3GPP refers to such a hybrid RAN as the Next Generation RAN, or NG-RAN. Of course, many other examples may be utilized within the scope of the present disclosure.

[0029] As shown, RAN 104 includes multiple base stations 108. In a broad sense, a base station is a network element in a radio access network that is responsible for radio transmission and reception to or from a UE in one or more cells. In different technologies, standards or contexts, those skilled in the art may refer to the base station as a base transceiver (BTS), a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), an access point (AP), a node B (NB), an eNode B (eNB), a gNode B (gNB), a transmission and reception point (TRP) or some other suitable terminology. In some examples, a base station may include two or more TRPs, which may be collocated or non-collocated. Each TRP may communicate on the same or different carrier frequencies in the same or different frequency bands. In an example where RAN 104 operates according to LTE and 5G NR standards, one of the base stations may be an LTE base station, and the other base station may be a 5G NR base station.

[0030] RAN 104 is further shown as supporting wireless communications for multiple mobile devices. In the 3GPP standards, a mobile device may be referred to as a user equipment (UE), but may also be referred to as a mobile station (MS), a user station, a mobile unit, a user unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile user station, an access terminal (AT), a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other suitable terminology by those skilled in the art. A UE may be a device (e.g., a mobile device) that provides a user with access to network services.

[0031] Within the present disclosure, a "mobile" device does not necessarily need to have the ability to move, and can be stationary. The term mobile device or mobile device refers broadly to a variety of devices and technologies. A UE may include multiple hardware structural components whose size, shape, and arrangement facilitate communication; these components may include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc. electrically coupled to each other. For example, some non-limiting examples of mobile devices include mobile phones, cellular phones, smart phones, Session Initiation Protocol (SIP) phones, laptops, personal computers (PCs), notebooks, netbooks, smartbooks, tablets, personal digital assistants (PDAs), and various embedded systems, such as corresponding to the "Internet of Things" (IoT).

[0032] The mobile device may also be a car or other vehicle, a remote sensor or actuator, a robot or robotic device, a satellite radio, a global positioning system (GPS) device, an object tracking device, a drone, a multicopter, a quadcopter, a remote control device, a consumer and / or wearable device (such as glasses), a wearable camera, a virtual reality device, a smart watch, a health or fitness tracker, a digital audio player (e.g., an MP3 player), a camera, a game console, etc. The mobile device may also be a digital home or smart home device, such as home audio, video, and / or multimedia equipment, an appliance, a vending machine, smart lighting, a home security system, a smart meter, etc. The mobile device may also be a smart energy device, a security device, a solar panel or solar array, a municipal infrastructure device that controls power (e.g., a smart grid), lighting, water, etc., an industrial automation and enterprise device, a logistics controller, and / or agricultural equipment, etc. In addition, the mobile device may provide networked medical or telemedicine support, i.e., remote health care. Remote health devices may include remote health monitoring devices and remote health management devices, whose communications may be given priority treatment or priority access over other types of information, for example, in terms of priority access to critical service data transmission and / or associated QoS for critical service data transmission.

[0033] Wireless communication between RAN 104 and UE 106 can be described as utilizing an air interface. Transmissions from a base station (e.g., base station 108) to one or more UEs (e.g., similar to UE 106) over an air interface can be referred to as downlink (DL) transmissions. According to certain aspects of the present disclosure, the term downlink can refer to a point-to-multipoint transmission initiated at a base station (e.g., base station 108). Another way to describe the scheme can be to use the term broadcast channel multiplexing. Transmissions from a UE (e.g., UE 106) to a base station (e.g., base station 108) can be referred to as uplink (UL) transmissions. According to other aspects of the present disclosure, the term uplink can refer to a point-to-point transmission initiated at a UE (e.g., UE 106).

[0034] In some examples, access to the air interface may be scheduled, wherein a scheduling entity (e.g., a base station 108) allocates resources for communications between some or all devices and equipment within its service area or cell. Within the present disclosure, as discussed further below, a scheduling entity may be responsible for scheduling, allocating, reconfiguring, and releasing resources for one or more scheduled entities (e.g., UEs 106). That is, for scheduled communications, multiple UEs 106 (which may be scheduled entities) may utilize resources allocated by the scheduling entity 108.

[0035] Base station 108 is not the only entity that can act as a scheduling entity. That is, in some examples, a UE can act as a scheduling entity to schedule resources for one or more scheduled entities (e.g., one or more other UEs). For example, a UE can communicate directly with other UEs in a peer-to-peer or device-to-device manner and / or in a relay configuration.

[0036] like Figure 1 As shown, the scheduling entity 108 can broadcast downlink traffic 112 to one or more scheduled entities (e.g., one or more UEs 106). In a broad sense, the scheduling entity 108 is a node or device responsible for scheduling traffic in the wireless communication network, including downlink traffic 112, and in some examples, uplink traffic 116 from one or more scheduled entities (e.g., one or more UEs 106) to the scheduling entity 108. On the other hand, the scheduled entity (e.g., UE 106) is a node or device that receives downlink control information 114, which includes but is not limited to scheduling information (e.g., grants), synchronization or timing information, or other control information from another entity in the wireless communication network (such as the scheduling entity 108).

[0037] In addition, uplink and / or downlink control information and / or traffic information can be sent on a waveform that can be time-divided into frames, subframes, time slots and / or symbols. As used herein, a symbol can refer to a time unit in which each subcarrier carries a resource element (RE) in an orthogonal frequency division multiplexing (OFDM) waveform. A time slot can carry 7 or 14 OFDM symbols. A subframe can refer to a duration of 1ms. Multiple subframes or time slots can be grouped together to form a single frame or radio frame. Within the present disclosure, a frame can refer to a predetermined duration (e.g., 10ms) for wireless transmission, wherein each frame includes, for example, 10 subframes, each subframe 1ms. Of course, these definitions are not required, and any suitable scheme for organizing waveforms can be utilized, and the various time divisions of waveforms can have any suitable duration.

[0038] Typically, the base stations 108 may include a backhaul interface for communicating with a backhaul portion 120 of the wireless communication system 100. The backhaul portion 120 may provide a link between the base stations 108 and the core network 102. Additionally, in some examples, the backhaul network may provide interconnections between the various base stations 108. Various types of backhaul interfaces may be used, such as a direct physical connection using any suitable transport network, a virtual network, etc.

[0039] The core network 102 may be part of the wireless communication system 100 and may be independent of the radio access technology used in the RAN 104. In some examples, the core network 102 may be configured according to a 5G standard (e.g., 5GC). In other examples, the core network 102 may be configured according to a 4G Evolved Packet Core (EPC) or any other suitable standard or configuration.

[0040] Reference now Figure 2 , as a non-limiting illustrative example, a schematic diagram of a radio access network (RAN) 200 according to some aspects of the present disclosure is provided. In some examples, the RAN 200 can be connected to the RAN described above and Figure 1 The same as the RAN 104 shown in FIG.

[0041] The geographic area covered by RAN 200 may be divided into a plurality of cellular areas (cells), which a user equipment (UE) may uniquely identify based on an identifier broadcast over the geographic area from an access point or base station. Figure 2 Cells 202, 204, 206, and 208 are shown, each of which may include one or more sectors (not shown). A sector is a sub-area of ​​a cell. All sectors within a cell are served by the same base station. A radio link within a sector may be identified by a single logical identifier belonging to the sector. In a cell divided into multiple sectors, multiple sectors within a cell may be formed by antenna groups, each antenna being responsible for communicating with a UE in a portion of the cell.

[0042] Various base station arrangements can be used. Figure 2 , two base stations, base station 210 and base station 212, are shown in cells 202 and 204. A third base station (base station 214) is shown controlling a remote radio head (RRH) 216 in cell 206. That is, the base station may have an integrated antenna or may be connected to an antenna or RRH 216 via a feeder cable. In the illustrated example, cells 202, 204, and 206 may be referred to as macro cells because base stations 210, 212, and 214 support cells with large sizes. In addition, base station 218 is shown in cell 208, which may overlap with one or more macro cells. In this example, cell 208 may be referred to as a small cell (e.g., a micro cell, a pico cell, a femto cell, a home base station, a home Node B, a home e Node B, etc.) because base station 218 supports a cell with a relatively small size. The cell size may be determined based on system design and component constraints.

[0043] It should be understood that RAN 200 may include any number of wireless base stations and cells. In addition, relay nodes may be deployed to extend the size or coverage area of ​​a given cell. Base stations 210, 212, 214, 218 provide wireless access points to the core network for any number of mobile devices. In some examples, base stations 210, 212, 214, and / or 218 may be similar to those described above and described in Figure 1 The scheduling entity 108 shown in FIG. 1 is the same as or similar to that shown in FIG.

[0044] Figure 2 Also included is an unmanned aerial vehicle (UAV) 220, which may be a drone or a quadcopter. UAV 220 may be configured to function as a base station, or more specifically as a mobile base station. That is, in some examples, the cell is not necessarily stationary, and the geographic area of ​​the cell may move depending on the location of a mobile base station (such as UAV 220).

[0045] Within the RAN 200, cells may include UEs that may communicate with one or more sectors of each cell. In addition, each base station 210, 212, 214, 218, and 220 may be configured to provide access to the core network 102 (see FIG. 1 ) for all UEs in the respective cells. Figure 1 ) access point. For example, UEs 222 and 224 may communicate with base station 210; UEs 226 and 228 may communicate with base station 212; UEs 230 and 232 may communicate with base station 214 via RRH 216; UE 234 may communicate with base station 218; and UE 236 may communicate with mobile base station 220. In some examples, UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240, and / or 242 may communicate with the base stations described above and in Figure 1 202. In some examples, UAV 220 (e.g., a quadcopter) may be a mobile network node and may be configured to function as a UE. For example, UAV 220 may operate within cell 202 by communicating with base station 210.

[0046] On the other hand of RAN 200, side link signals can be used between UEs without relying on scheduling or control information from a base station. For example, side link communications can be used in a device-to-device (D2D) network, a peer-to-peer (P2P) network, a vehicle-to-vehicle (V2V) network, a vehicle-to-everything (V2X) network, and / or other suitable side link networks. For example, two or more UEs (e.g., UE 238, 240, and 242) can use side link signals 237 to communicate with each other without relaying the communication through a base station. In some examples, UE 238, 240, and 242 can each be used as a scheduling entity or a transmitting side link device and / or a scheduled entity or a receiving side link device to schedule resources and transmit side link signals 237 between them without relying on scheduling or control information from a base station. In other examples, two or more UEs (e.g., UE 226 and 228) within the coverage area of ​​a base station (e.g., base station 212) can also transmit side link signals 227 via a direct link (side link) without transmitting the communication through base station 212. In this example, base station 212 may allocate resources to UEs 226 and 228 for sidelink communications.

[0047] In order to achieve a low block error rate (BLER) for transmission over the air interface while still achieving very high data rates, channel coding can be used. That is, wireless communications can often make use of suitable error-correcting block codes. In a typical block code, an information message or sequence is segmented into code blocks (CBs), and then an encoder (e.g., CODEC) at the transmitting device mathematically adds redundancy to the information message. Exploiting this redundancy in the encoded information message can improve the reliability of the message, thereby being able to correct any bit errors that may occur due to noise.

[0048] Data encoding can be implemented in a variety of ways. In early 5G NR specifications, user data is encoded using quasi-cyclic low-density parity check (LDPC) with two different basemaps: one basemap is used for large code blocks and / or high code rates, and the other basemap is used for other cases. Control information and the physical broadcast channel (PBCH) are encoded using polarization coding based on nested sequences. For these channels, puncture, shortening, and repetition are used for rate matching.

[0049] Aspects of the present disclosure may be implemented using any suitable channel codes. Various implementations of base stations and UEs may include suitable hardware and capabilities (eg, encoders, decoders, and / or CODECs) to utilize one or more of these channel codes for wireless communications.

[0050] In the RAN 200, the ability of a UE to communicate independently of its location while moving is called mobility. Various physical channels between the UE and the RAN 200 are usually established, maintained, and released under the control of an access and mobility management function (AMF). In some scenarios, the AMF may include a security context management function (SCMF) and a security anchor function (SEAF) that perform authentication. The SCMF may manage security contexts for both control plane and user plane functions in whole or in part.

[0051] In various aspects of the present disclosure, the RAN 200 may utilize DL-based mobility or UL-based mobility to implement mobility and switching (i.e., transferring the UE's connection from one radio channel to another). In a network configured for DL-based mobility, during a call with a scheduling entity, or at any other time, the UE may monitor various parameters of the signal from its serving cell and various parameters of neighboring cells. Depending on the quality of these parameters, the UE may maintain communication with one or more neighboring cells. During this period, if the UE moves from one cell to another, or if the signal quality from a neighboring cell exceeds the signal quality from the serving cell for a given amount of time, the UE may perform a handover or handover from the serving cell to a neighboring (target) cell. For example, a UE 224 may move from a geographic area corresponding to its serving cell 202 to a geographic area corresponding to a neighboring cell 206. When the signal strength or quality from a neighboring cell 206 exceeds the signal strength or quality of its serving cell 202 for a given amount of time, the UE 224 may send a report message to its serving base station 210 indicating this situation. In response, UE 224 may receive a handover command, and the UE may undergo a handover to cell 206 .

[0052] In a network configured for UL-based mobility, the UL reference signal from each UE can be used by the network to select a serving cell for each UE. In some examples, base stations 210, 212, and 214 / 216 can broadcast a unified synchronization signal (e.g., a unified primary synchronization signal (PSS), a unified secondary synchronization signal (SSS), and a unified physical broadcast channel (PBCH)). UE222, 224, 226, 228, 230, and 232 can receive the unified synchronization signal, derive the carrier frequency and time slot timing from the synchronization signal, and send an uplink pilot or reference signal in response to the derived timing. The uplink pilot signal sent by a UE (e.g., UE 224) can be received simultaneously by two or more cells (e.g., base stations 210 and 214 / 216) within the RAN 200. Each cell can measure the strength of the pilot signal, and the radio access network (e.g., one or more of base stations 210 and 214 / 216 and / or a central node within the core network) can determine the serving cell of UE 224. As the UE 124 moves through the RAN 200, the RAN 200 may continue to monitor the uplink pilot signal sent by the UE 224. When the signal strength or quality of the pilot signal measured by the neighboring cell exceeds the signal strength or quality measured by the serving cell, the RAN 200 may switch the UE 224 from the serving cell to the neighboring cell with or without notifying the UE 224.

[0053] Although the synchronization signals transmitted by base stations 210, 212 and 214 / 216 may be uniform, the synchronization signals may not identify a specific cell, but may identify a region of multiple cells operating on the same frequency and / or having the same timing. The use of regions in a 5G network or other next generation communication network implements an uplink-based mobility framework and improves the efficiency of both the UE and the network because the number of mobility messages that need to be exchanged between the UE and the network can be reduced.

[0054] In various implementations, the air interface in the radio access network 200 can utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum provides exclusive use of a portion of the spectrum, typically achieved by a mobile network operator purchasing a license from a government regulator. Unlicensed spectrum provides shared use of a portion of the spectrum without the need for a government-granted license. Although some technical rules generally still need to be followed to access unlicensed spectrum, access can generally be obtained by any operator or device. Shared spectrum may be between licensed spectrum and unlicensed spectrum, where technical rules or restrictions may be required to access the spectrum, but the spectrum may still be shared by multiple operators and / or multiple RATs. For example, a license holder of a portion of licensed spectrum may provide licensed shared access (LSA) to share the spectrum with other parties, for example, to obtain access under appropriate conditions determined by the license holder.

[0055] Devices communicating in the radio access network 200 may utilize one or more multiplexing techniques and multiple access algorithms to enable simultaneous communication of various devices. For example, the 5G NR specification utilizes orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) to provide multiple access for UL transmissions from UEs 222 and 224 to the base station 210, and provides multiplexing for DL ​​transmissions from the base station 210 to one or more UEs 222 and 224. In addition, for UL transmissions, the 5G NR specification provides support for discrete Fourier transform-spread spectrum-OFDM (DFT-s-OFDM) with CP (also known as single carrier FDMA (SC-FDMA)). However, within the scope of the present disclosure, multiplexing and multiple access are not limited to the above schemes, and may be provided using time division multiple access (TDMA), code division multiple access (CDMA), frequency division multiple access (FDMA), sparse code multiple access (SCMA), resource extension multiple access (RSMA), or other suitable multiple access schemes. In addition, multiplexing of DL transmissions from base station 210 to UEs 222 and 224 may be provided using time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), sparse code multiplexing (SCM), or other suitable multiplexing schemes.

[0056] The equipment in the radio access network 200 may also utilize one or more duplex algorithms. Duplex refers to a point-to-point communication link in which two endpoints can communicate with each other bidirectionally. Full-duplex means that two endpoints can communicate with each other at the same time. Half-duplex means that only one endpoint can send information to the other endpoint at a time. Half-duplex emulation is often implemented for wireless links that utilize time division duplex (TDD). In TDD, transmissions in different directions on a given channel are separated from each other using time division multiplexing. That is, in some cases, the channel is dedicated to transmission in one direction, while at other times, the channel is dedicated to transmission in another direction, where the direction can change very quickly, such as several times per time slot. In wireless links, full-duplex channels generally rely on physical isolation of the transmitter and receiver, as well as suitable interference cancellation techniques. Full-duplex emulation is often implemented for wireless links by utilizing frequency division duplex (FDD) or space division duplex (SDD). In FDD, transmissions in different directions can operate on different carrier frequencies (e.g., within paired spectrum). In SDD, transmissions in different directions on a given channel are separated from each other using space division multiplexing (SDM). In other examples, full-duplex communication can be implemented within an unpaired spectrum (e.g., within a single carrier bandwidth), where transmissions in different directions occur within different sub-bands of the carrier bandwidth. This type of full-duplex communication may be referred to herein as sub-band full-duplex (SBFD), also known as flexible duplex.

[0057] Reference Figure 3 Various aspects of the present disclosure are described with reference to the OFDM waveforms schematically shown in FIG. It will be appreciated by those skilled in the art that various aspects of the present disclosure may be applied to SC-FDMA waveforms in substantially the same manner as described below. That is, although some examples of the present disclosure may focus on OFDM links for clarity, it will be appreciated that the same principles may also be applied to SC-FDMA waveforms.

[0058] Reference now Figure 3 , shows an expanded view of an exemplary subframe 302, showing an OFDM resource grid. However, as will be readily appreciated by those skilled in the art, the PHY transmission structure for any particular application may differ from the examples described herein depending on any number of factors. Here, time is in the horizontal direction, in units of OFDM symbols; and frequency is in the vertical direction, in units of subcarriers of a carrier.

[0059] Resource grid 304 can be used to schematically represent the time-frequency resources of a given antenna port. That is, in a multiple-input multiple-output (MIMO) implementation with multiple available antenna ports, corresponding multiple resource grids 304 can be used for communication. Resource grid 304 is divided into multiple resource elements (REs) 306. RE is 1 subcarrier × 1 codeword, is the smallest discrete part of the time-frequency grid, and contains a single complex value representing data from a physical channel or signal. Depending on the modulation used in a specific implementation, each RE can represent one or more information bits. In some examples, a block of REs can be referred to as a physical resource block (PRB) or more simply a resource block (RB) 308, which contains any suitable number of consecutive subcarriers in the frequency domain. In one example, an RB can include 12 subcarriers, which number is independent of the parameter set used. In some examples, depending on the parameter set, an RB can include any suitable number of consecutive OFDM symbols in the time domain. In the present disclosure, it is assumed that a single RB such as RB 308 corresponds entirely to a single communication direction (sending or receiving for a given device).

[0060] A group of contiguous or discontinuous resource blocks may be referred to herein as a resource block group (RBG), a subband, or a bandwidth part (BWP). A group of subbands or BWPs may span the entire bandwidth. Scheduling of a scheduled entity (e.g., a UE) for downlink, uplink, or sidelink transmission typically involves scheduling one or more resource elements 306 within one or more subbands or bandwidth parts (BWPs). Thus, a UE typically utilizes only a subset of a resource grid 304. In some examples, an RB may be the smallest resource unit that may be allocated to a UE. Thus, the more RBs scheduled for a UE and the higher the modulation scheme selected for the air interface, the higher the data rate for the UE. The RBs may be scheduled by a scheduling entity such as a base station (e.g., gNB, eNB, etc.), or may be scheduled by the UE implementing the D2D sidelink communication itself.

[0061] In this illustration, RB 308 is shown as occupying less than the entire bandwidth of subframe 302, with some subcarriers shown above and below RB 308. In a given implementation, subframe 302 may have a bandwidth corresponding to any number of one or more RBs 308. Furthermore, in this illustration, RB 308 is shown as occupying less than the entire duration of subframe 302, but this is merely one possible example.

[0062] Each 1 ms subframe 302 may include one or more adjacent time slots. Figure 3In the example shown, as an illustrative example, a subframe 302 includes four time slots 310. In some examples, a time slot can be defined according to a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a time slot can include 7 or 14 OFDM symbols with a nominal CP. Additional examples may include micro-slots with a shorter duration (e.g., one to three OFDM symbols), sometimes referred to as shortened transmission time intervals (TTIs). In some cases, these micro-slots or shortened transmission time intervals (TTIs) may be sent, occupying resources scheduled for ongoing time slot transmissions of the same or different UEs. Any number of resource blocks may be used within a subframe or time slot.

[0063] An expanded view of one of the time slots 310 shows the time slot 310 including a control region 312 and a data region 314. In general, the control region 312 may carry control channels, and the data region 314 may carry data channels. Of course, a time slot may contain all DL, all UL, or at least one DL portion and at least one UL portion. Figure 3 The structure shown is merely exemplary in nature, and different slot structures may be utilized and may include one or more of each of the control region and the data region.

[0064] although Figure 3 Although not shown in the figure, each RE 306 within the RB 308 can be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, etc. Other REs 306 within the RB 308 can also carry pilot or reference signals. These pilot or reference signals can be used by the receiving device to perform channel estimation of the corresponding channel, which can achieve coherent demodulation / detection of the control and / or data channels within the RB 308.

[0065] In some examples, time slot 310 may be used for broadcast, multicast, groupcast, or unicast communications. For example, broadcast, multicast, or groupcast communications may refer to point-to-multipoint transmissions from one device (e.g., a base station, UE, or other similar device) to other devices. Here, broadcast communications are transmitted to all devices, while multicast or groupcast communications are transmitted to multiple intended receiving devices. Unicast communications may refer to point-to-point transmissions from one device to a single other device.

[0066] In an example of cellular communication on a cellular carrier via a Uu interface, for DL ​​transmission, a scheduling entity (e.g., a base station) may allocate one or more REs 306 (e.g., within a control region 312) to one or more scheduled entities (e.g., UEs) to carry DL control information including one or more DL control channels (e.g., a physical downlink control channel (PDCCH)). The PDCCH carries downlink control information (DCI), including but not limited to power control commands (e.g., one or more open-loop power control parameters and / or one or more closed-loop power control parameters), scheduling information, grants, and / or RE allocations for DL ​​and UL transmissions. The PDCCH may also carry HARQ feedback transmissions, such as an acknowledgment (ACK) or a negative acknowledgment (NACK). HARQ is a technique well known to those of ordinary skill in the art, in which the integrity of a packet transmission may be checked on the receiving side to ensure accuracy, for example, using any suitable integrity checking mechanism, such as a checksum or a cyclic redundancy check (CRC). If the integrity of the transmission is confirmed, an ACK may be sent, and if it is not confirmed, a NACK may be sent. In response to the NACK, the transmitting device may send a HARQ retransmission, which may enable pursuit combining, incremental redundancy, and the like.

[0067] The base station may also allocate one or more REs 306 (e.g., in the control region 312 or the data region 314) to carry other DL signals, such as a demodulation reference signal (DMRS); a phase tracking reference signal (PT-RS); a channel state information (CSI) reference signal (CSI-RS); and a synchronization signal block (SSB). The SSBs may be broadcast at regular intervals based on a period (e.g., 5, 10, 20, 30, 80, or 130 ms). The SSBs include a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast control channel (PBCH). The UE may utilize the PSS and SSS to achieve radio frame, subframe, time slot, and symbol synchronization in the time domain, identify the center of the channel (system) bandwidth in the frequency domain, and identify the physical cell identity (PCI) of the cell.

[0068] The PBCH in the SSB may also include a master information block (MIB), which includes various system information and parameters for decoding a system information block (SIB). The SIB may be, for example, SystemInformationType 1 (SIB1), which may include various additional system information. Together, the MIB and SIB1 provide minimum system information (SI) for initial access. Examples of system information transmitted in the MIB may include, but are not limited to, subcarrier spacing (e.g., a default downlink parameter set), system frame number, configuration of a PDCCH control resource set (CORESET) (e.g., PDCCH CORESET0), a cell barring indicator, a cell reselection indicator, a raster offset, and a search space for SIB1. Examples of remaining minimum system information (RMSI) transmitted in SIB1 may include, but are not limited to, a random access search space, a paging search space, downlink configuration information, and uplink configuration information. The base station may also send other system information (OSI).

[0069] In UL transmission, the scheduled entity (e.g., UE) may utilize one or more REs 306 to carry UL control information (UCI) including one or more UL control channels (such as, physical uplink control channel (PUCCH)) to the scheduling entity. UCI may include various packet types and categories, including pilots, reference signals, and information configured to implement or assist in decoding uplink data transmission. Examples of uplink reference signals may include sounding reference signals (SRS) and uplink DMRS. In some examples, UCI may include a scheduling request (SR), i.e., a request to the scheduling entity to schedule uplink transmission. Here, in response to the SR sent on the UCI, the scheduling entity may send downlink control information (DCI), which may schedule resources for uplink packet transmission. UCI may also include HARQ feedback, channel state feedback (CSF) (such as CSI report), or any other suitable UCI.

[0070] In addition to control information, one or more REs 306 may be allocated for data traffic (e.g., within the data region 314). Such data traffic may be carried on one or more traffic channels, such as, for DL ​​transmissions, on a physical downlink shared channel (PDSCH); or for UL transmissions, on a physical uplink shared channel (PUSCH). In some examples, one or more REs 306 within the data region 314 may be configured to carry other signals, such as one or more SIBs and DMRS.

[0071] In an example of sidelink communication on a sidelink carrier via a proximity service (ProSe) PC5 interface, a control region 312 of a time slot 310 may include a physical sidelink control channel (PSCCH) including sidelink control information (SCI) sent by an initiating (transmitting) sidelink device (e.g., a Tx V2X device or other Tx UE) to a group of one or more other receiving sidelink devices (e.g., an Rx V2X device or other Rx UE). A data region 314 of the time slot 310 may include a physical sidelink shared channel (PSSCH) including sidelink data traffic sent by an initiating (transmitting) sidelink device in resources reserved by the transmitting sidelink device via the SCI on the sidelink carrier. Other information may be further sent on each RE 306 within the time slot 310. For example, HARQ feedback information may be sent from a receiving sidelink device to a transmitting sidelink device in a physical sidelink feedback channel (PSFCH) within the time slot 310. Additionally, one or more reference signals may be sent within slot 310, such as a sidelink SSB, a sidelink CSI-RS, a sidelink SRS, and / or a sidelink positioning reference signal (PRS).

[0072] These physical channels are usually multiplexed and mapped to transport channels for processing at the medium access control (MAC) layer. Transport channels carry information blocks called transport blocks (TBs). Based on the modulation and coding scheme (MCS) and the number of RBs in a given transmission, the transport block size (TBS), which may correspond to the number of information bits, may be a controlled parameter.

[0073] Figure 3 The channels or carriers shown in are not necessarily all channels or carriers that may be used between devices, and one of ordinary skill in the art will recognize that other channels or carriers may be used in addition to those shown, such as other traffic, control, and feedback channels.

[0074] In some aspects of the present disclosure, the scheduling entity and / or the scheduled entity may be configured for beamforming and / or multiple-input multiple-output (MIMO) techniques. Figure 4 An example of a wireless communication system 400 that supports beamforming and / or MIMO is shown. In a MIMO system, a transmitter 402 includes multiple transmit antennas 404 (e.g., N transmit antennas), and a receiver 406 includes multiple receive antennas 408 (e.g., M receive antennas). Therefore, there are N×M signal paths 410 from the transmit antennas 404 to the receive antennas 408. Each of the transmitter 402 and the receiver 406 can be implemented, for example, within a scheduling entity, a scheduled entity, or any other suitable wireless communication device.

[0075] The use of this multi-antenna technology enables wireless communication systems to exploit the spatial domain to support spatial multiplexing, beamforming, and transmit diversity. Spatial multiplexing can be used to send different data streams, also called layers, simultaneously on the same time-frequency resources. Data streams can be sent to a single UE to increase the data rate, or to multiple UEs to increase the overall system capacity, the latter of which is called multi-user MIMO (MU-MIMO). This is achieved by spatially precoding each data stream (i.e., multiplying the data stream by different weights and phase shifts), and then sending each spatially precoded stream through multiple transmit antennas on the downlink. The spatially precoded data streams arrive at the UE with different spatial signatures, which enables each UE to recover one or more data streams destined for that UE. On the uplink, each UE sends a spatially precoded data stream, which enables the base station to identify the source of each spatially precoded data stream.

[0076] The number of data streams or layers corresponds to the transmission rank. In general, the rank of a MIMO system is limited to the smaller of the number of transmit or receive antennas 404 or 408. In addition, channel conditions at the UE and other considerations, such as available resources at the base station, may also affect the transmission rank. For example, the rank (and therefore the number of data streams) assigned to a particular UE on the downlink can be determined based on a rank indicator (RI) sent from the UE to the base station. The RI can be determined based on the antenna configuration (e.g., the number of transmit and receive antennas) and the signal to interference and noise ratio (SINR) measured on each receive antenna. The RI can indicate, for example, the number of layers that can be supported under current channel conditions. The base station can use the RI along with resource information (e.g., available resources and the amount of data to be scheduled for the UE) to assign a transmission rank to the UE.

[0077] In one example, if Figure 4 As shown, a rank 2 spatial multiplexing transmission on a 2x2 MIMO antenna configuration will send one data stream from each transmit antenna 404. Each data stream follows a different signal path 410 to each receive antenna 408. The receiver 406 can then use the received signal from each receive antenna 408 to reconstruct the data stream.

[0078] Beamforming is a signal processing technique that can be used at a transmitter 402 or a receiver 406 to shape or steer an antenna beam (e.g., a transmit beam or a receive beam) along a spatial path between the transmitter 402 and the receiver 406. Beamforming can be achieved by combining signals transmitted via antennas 404 or 408 (e.g., antenna elements of an antenna array module) so that some signals experience constructive interference and other signals experience destructive interference. In order to produce the desired constructive / destructive interference, the transmitter 402 or the receiver 406 can apply an amplitude and / or phase offset to the signal transmitted or received from each antenna 404 or 408 associated with the transmitter 402 or the receiver 406.

[0079] In some examples, in order to select a specific beam for communicating with the UE, the base station may send a reference signal, such as an SSB or a channel state information reference signal (CSI-RS), on each of multiple beams (SSB beams) in a beam scanning manner. The UE may measure the reference signal received power (RSRP), reference signal received quality (RSRQ), or SINR on each beam, and send a beam measurement report indicating the RSRP of each measured beam to the base station. The base station may then select a specific beam for communicating with the UE based on the beam measurement report. In other examples, if the channel is reciprocal, the base station may derive a specific beam for communicating with the UE based on uplink measurements of one or more uplink reference signals, such as a sounding reference signal (SRS).

[0080] In a 5G NR network, a base station can be an aggregated base station, in which the radio protocol stack is logically integrated within a single RAN node; or a disaggregated base station, in which the radio protocol stack is logically divided between a central unit (CU) and one or more distributed units (DUs). The CU hosts the radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) layers that control the operation of one or more DUs. The DU hosts the radio link control (RLC), media access control (MAC), and physical (PHY) layers. The CU can be implemented within an edge RAN node, which can be referred to as a host node, while one or more DUs can be collocated with the CU and / or distributed in multiple RAN nodes that are physically separated from each other. For example, a disaggregated base station can be used in an integrated access backhaul (IAB) network.

[0081] Figure 5is a diagram that provides a high-level illustration of one example of an IAB network configuration 500 according to some aspects. In this illustration, a communication network 502, such as an IAB network, is coupled to a remote network 504, such as a primary backhaul network or a mobile core network. In such an IAB network 502, wireless spectrum can be used for both access links and backhaul links. In some examples, the wireless spectrum can utilize millimeter wave (mmWave) or sub-6 GHz carrier frequencies.

[0082] IAB network 502 may be similar to Figure 2 As shown in the radio access network 200, the IAB network 502 can be divided into a plurality of cells 506, 508, 510, 512, and 514, each of which can be served by a respective IAB node 516, 518, 520, 522, and 524. Each of the IAB nodes 516-524 can be a base station (e.g., a gNB) or other node that utilizes a wireless spectrum (e.g., a radio frequency (RF) spectrum) to support access by one or more UEs located within the cell 506-514 served by the IAB node.

[0083] exist Figure 5 In the example shown, IAB node 516 communicates with UE 526 and 528 via wireless access links 530 and 532, IAB node 518 communicates with UE 534 via wireless access link 536, and IAB node 522 communicates with UE 538 via wireless access link 540. IAB nodes 516-524 are also interconnected via one or more wireless backhaul links 542, 544, 546, 548, 550, and 552. Each wireless backhaul link 542-552 can use the same wireless spectrum (e.g., radio frequency (RF) spectrum) as access links 530-540 to backhaul access to / from remote network 504. This can be referred to as wireless self-backhaul. Such wireless self-backhaul can easily and quickly implement the deployment of highly dense small cell networks. That is, rather than requiring each new gNB deployment to be equipped with its own hardwired backhaul connection, the wireless spectrum used for communications between gNBs and UEs can be used for backhaul communications between any number of IAB nodes to form the IAB network 502.

[0084] exist Figure 5In the example shown, IAB node 516 communicates with IAB node 520 via wireless backhaul link 542, IAB node 520 communicates with IAB node 522 via wireless backhaul link 544, IAB node 522 communicates with IAB node 524 via wireless backhaul link 546, IAB node 524 communicates with IAB node 518 via wireless backhaul link 548, IAB node 518 communicates with IAB node 516 via wireless backhaul link 550, and IAB node 518 communicates with IAB node 520 via wireless backhaul link 552. Figure 5 As shown, each IAB node 516-524 may be connected to two or more other IAB nodes via respective wireless backhaul links 542-552 for robustness.

[0085] Some or all of the IAB nodes 516-524 may also be connected via wired backhaul links (e.g., fiber, coaxial cable, Ethernet, copper wire, etc.) and / or microwave backhaul links. Thus, the IAB network 502 may support both wired / microwave and wireless backhaul services. At least one IAB node (e.g., IAB node 524) may be a border IAB node, also referred to herein as an IAB host node, which also provides a communication link 554 to the remote network 504. For example, the IAB host node 524 may include a wired (e.g., fiber, coaxial cable, Ethernet, copper wire), microwave, or other suitable link 554 to the remote network 504.

[0086] In order to facilitate wireless communication between IAB nodes 516-524 and between IAB nodes 516-524 and UEs served by IAB nodes 516-524, each IAB node 516-524 can be configured to act as both a scheduling entity and a scheduled entity. Therefore, an IAB node (e.g., IAB node 516) can utilize the same wireless spectrum to send access services to / from UEs and then backhaul the access services to / from remote network 504. For example, in order to backhaul access services to / from IAB node 518, IAB node 518 can communicate with IAB node 520 to send backhaul access services via wireless backhaul link 542, IAB node 520 can communicate with IAB node 522 to send backhaul access services via wireless backhaul link 544, and IAB node 522 can communicate with IAB node 524 to send backhaul access services via wireless backhaul link 546. In this example, both IAB nodes 520 and 522 may act as both a scheduling entity and a scheduled entity to backhaul access traffic to / from IAB node 516. In this way, communications between a pair of IAB nodes may be solely scheduled by one of the IAB nodes within the pair.

[0087] In other examples, the IAB node can schedule wireless backhaul communications between other IAB node pairs. For example, the IAB node 524 can operate as a scheduling entity of the IAB network 502, and the IAB nodes 516, 520, and 522 each operate as a scheduled entity to backhaul access services to / from the IAB node 516. In this example, the IAB node 524 can schedule wireless backhaul communications between each pair of IAB nodes (e.g., between the IAB node 516 and the IAB node 520, between the IAB node 520 and the IAB node 522, and between the IAB node 522 and the IAB node 524). As another example, the IAB node 522 can operate as a scheduling entity to schedule wireless backhaul communications between the IAB nodes 516 and 520 and between the IAB node 520 and the IAB node 522. The IAB node 522 can then operate as a scheduled entity to allow the IAB node 524 to schedule wireless backhaul communications between them.

[0088] Figure 6 6 is a schematic diagram showing an example of IAB node functions within the IAB network 600. Figure 6 In the example shown, the IAB node 602 is shown as being coupled to the core network 604 via a wired connection. The IAB node 602 may be referred to herein as an IAB host node, which may be, for example, an enhanced gNB including functionality for controlling the IAB network 600. In some examples, the IAB host node 602 may include a central unit (CU) 606 and a distributed unit (DU) 608. The CU 606 is configured to operate as a centralized network node (or central entity) within the IAB network 600. For example, the CU 606 may include radio resource control (RRC) layer functionality and packet data convergence protocol (PDCP) layer functionality to control / configure other nodes (e.g., IAB nodes and UEs) within the IAB network 600. Thus, the CU 606 may be configured to implement centralized mechanisms for handover decisions, topology changes, routing, bearer mapping, UE security, and other appropriate services.

[0089] The DU 608 is configured to operate as a scheduling entity to schedule scheduled entities (e.g., other IAB nodes and UEs) of the IAB host node 602. For example, the DU 608 of the IAB host node 602 may operate as a scheduling entity to schedule the IAB nodes 610 and 612 and the UEs 614 and 616. Thus, the DU 608 of the IAB host node 602 may schedule communications with the IAB nodes 610 and 612 via respective backhaul links, and schedule communications with the UEs 614 and 616 via respective access links. In some examples, the DU 608 may include radio link control (RLC), medium access control (MAC), and physical (PHY) layer functions to enable operation as a scheduling entity.

[0090] Each of the IAB nodes 610 and 612 may be configured as a layer 2 (L2) relay node, including respective DUs 620 and mobile terminal (MT) units 618, so that each L2 relay IAB node 610 and 612 can operate as a scheduling entity and a scheduled entity. For example, the MT unit 618 within each of the L2 relay IAB nodes 610 and 612 is configured to operate as a scheduled entity that can be scheduled by the IAB host node 602. Each MT unit 618 within the L2 relay IAB nodes 610 and 612 also facilitates communication with the IAB host node 602 via respective backhaul links. In addition, the DU 620 within each of the L2 relay IAB nodes 610 and 612 operates similarly to the DU 608 within the IAB host node 602 to serve as a scheduling entity to schedule one or more corresponding scheduled entities (e.g., other IAB nodes and / or UEs) of the L2 relay IAB nodes 610 and 612.

[0091] For example, the DU 620 of the L2 relay IAB node 612 serves as a scheduling entity to schedule communication with the UE 622 via the access link, while the DU 620 of the L2 relay IAB node 610 serves as a scheduling entity to schedule communication with the MT unit 618 of the L2 relay IAB nodes 624 and 626 via the corresponding backhaul links and with the UE 628 via the access link. Each of the L2 relay IAB nodes 624 and 626 also includes a respective DU 620 that serves as a scheduling entity to communicate with the corresponding UEs 630 and 632.

[0092] exist Figure 6In the network topology shown, the IAB host node 602, in conjunction with each of the L2 relay IAB nodes 610, 612, 624, and 626, can together form a decomposed base station (e.g., a decomposed gNB). The decomposed base station includes a CU 606 and each of the DUs 608 and 620 controlled by the CU 606. The CU / DU functional division in the decentralized base station can help to implement time-critical services such as scheduling, retransmission, segmentation, and other similar services in the DU 608 / 620. Even if a non-ideal backhaul is used between the CU and the DU, less time-critical functions can be concentrated in the CU 606 and resource pooled in the CU 606. Another benefit of CU / DU separation is that the external interfaces of the gNB (such as Xn) are terminated in the CU, thereby avoiding the additional complexity of terminating the external interface to each DU. The Xn interface can serve as a network interface between RAN nodes and can provide connections between gNB to gNB, gNB to eNB, and eNB to eNB. CU / DU partitioning also supports centralized termination of PDCP, which helps in end-to-end (E2E) security protection of UE communications between UE and CU, and packet processing for dual connectivity and switching between different DUs of the decomposed base station, because the traffic flows to / from different DUs are separated at the CU. It should be understood that the decomposed base station can be implemented in networks other than the IAB network, and the present disclosure is not limited to any particular type of network.

[0093] As described above, a gNB can be configured as a single logical node (e.g., an aggregated base station), or it can include a central unit (CU) and one or more distributed units (DUs) in a decentralized base station configuration. The CU and the DUs it controls are connected via the F1 interface. The F1 application protocol (F1-AP) is used to transfer low-level configuration information of radio bearers between the CU and the DU, and to establish a general tunneling protocol (GTP) tunnel between the DU and the CU for each radio bearer.

[0094] As further discussed above, the protocol stack of the IAB node may include two parts: a mobile terminal (MT) part (e.g., 618) for communicating with a parent node; and a distributed unit (DU) part (e.g., 620) for communicating with a child IAB node or a normal UE, where hop-by-hop RLC may be used between IAB nodes. Multi-hop forwarding may be performed by an IAB-specific backhaul adaptation protocol (BAP). During operation, the IAB host may assign a unique L2 address (BAP address) to each IAB node it controls. In the case of multipath, multiple routing IDs may be associated with each BAP address. The BAP of the source node (IAB host DU for DL ​​traffic, and L2 relay IAB node for UL) may add a BAP header to the packets they are sending, which will include a BAP routing ID (e.g., the BAP address of the destination / source IAB node and an optional path ID). Each IAB node may have a routing table (configured by the IAB host node CU 602) containing the next hop identifier for each BAP routing ID. Separate routing tables may be maintained for DL ​​and UL directions, with the DL table being used by the DU portion of the IAB node and the UL table being used by the MT portion of the IAB node.

[0095] Backhaul (BH) RLC channels can be used to transport packets between IAB nodes (or between an IAB host DU and an IAB node). When it comes to mapping between UE radio bearers and backhaul RLC channels, multiple mappings are supported, such as N:1 and 1:1 mapping. N:1 mapping multiplexes several UE radio bearers onto a single BH RLC channel based on specific parameters, such as the QoS profile of the bearer. N:1 is designed to optimize the use of BH RLC channels and requires less signaling overhead because a small number of BH RLC channels need to be established. On the other hand, 1:1 mapping maps each UE radio bearer to a separate BH RLC channel.

[0096] Before becoming fully operational, the IAB node may perform an IAB integration process. The IAB node may initially connect to the network by using its MT function to perform the initial access process for a regular UE. The reuse of the traditional UE initial access process complies with the principle of minimizing the impact on the core network. Next, the IAB host node may establish one or more BH RLC channels at one or more intermediate hops toward the newly joined IAB node, for example, establishing a certain number of default BH RLC channels that can be used for N:1 mapping, BHRLC channels for the F1-AP service of the DU part of the IAB node, etc. between the new IAB node and its parent node. The IAB host node may also update the routing table at the intermediate hop to enable routing toward the IAB node. In addition, the newly established BH RLC connection may be used to carry F1-AP control signaling, which is used to configure the DU function of the IAB node. Once the IAB-DU function is established, the IAB node may serve regular UEs, similar to any other DU.

[0097] Figure 7 7 is a diagram illustrating an example of an NR cell global identification signal (NCGI) 702 according to some aspects. The NCGI 702 may be configured as an identifier of an NR cell at an IAB host DU or an IAB node DU (e.g., see 1012, 1018 below) and may include a concatenation of a public land mobile network (PLMN) ID 704 and an NR cell identity (NCI) 706. In some examples, the PLMN ID 704 may be configured as a 24-bit identifier, including a mobile country code (MCC) 708, which may be 12 bits, and a mobile network code (MNC) 710, which may also be 12 bits. In some examples, the NCI 706 may be configured as a 36-bit identifier, where a gNB identifier (gNB ID) 712 may occupy the leftmost 22-32 bits and a local cell ID 714 occupies the remaining bits. In some examples, the gNB-ID can be configured to be unique within the gNB, such that the gNB-ID is common to all cells (e.g., in IAB host DUs and IAB node DUs) served by the gNB (e.g., with one IAB host CU). Similarly, the PLMN ID and the gNB-ID together can be used to identify the gNB.

[0098] In some examples, a physical cell identifier (PCI) may be used, where the PCI is used as an ID for the cell with up to 1008 supported values ​​for NR systems. The PCI can be reused by multiple geographically separated cells in the network, and cells with the same PCI can be distinguished by their unique cell global identifier (e.g., NCGI). The PCI can be carried by the PSS / SSS in the SSB block, and the PCI can be used to determine one or more scrambling sequences for different physical signals / channels. For some channel types, such as PBCH, PDCCH CoreSet 0, and / or cell-specific PDSCH transmissions, only the PCI can be used as a scrambling seed. For other channels, the configured scrambling seed may also be used alternatively or in addition to the PCI.

[0099] In some examples, cell information may be exchanged via an Xn interface, where the first gNB may provide the second gNB information about cells served by the first gNB via Xn using a Served Cell Information Element (IE). The first gNB may further update the list of serving cells provided to the second gNB via Xn by adding, modifying, and / or deleting cells on the list. For modification or deletion, the cells may be indicated by their existing NCGI. The first gNB may request information about cells served by the second gNB from the second gNB via Xn using the Cell Assistance Information IE, after which the second gNB will send the serving cell information of the requested cells. Here, two options may be available when requesting cell information. In the first option, the first gNB may request a complete list of cells served by the second gNB using, for example, a complete information request indicator. Under the second option, the first gNB may request a limited list of serving cells by providing their NCGI.

[0100] Figure 8 800 is a diagram illustrating cell activation between two nodes on an Xn link according to some aspects. During operation, a gNB (RAN node) may shut down cells served by an associated IAB node to save power. Figure 8In an example of , a first gNB 802 (NG-RAN node 1) may initiate a cell activation procedure toward a second gNB 804 (NG-RAN node 2), wherein the first gNB 802 sends a cell activation request 806 to the second gNB 804 to activate one or more cells that were previously reported as inactive. The gNB 802 may be configured as an IAB host node (which includes a CU and one or more DUs that may be co-located and / or distributed), and the gNB 804 may be configured as an aggregated base station or another IAB host node (e.g., another decomposed base station). In some examples, the first gNB may indicate which served cells are to be activated by using the NCGI of the requested cells. The second gNB 804 responds to the cell activation request 806 by sending a cell activation response 808 indicating the activation status of the requested cells. Deactivation may be performed in a similar manner, and may be indicated to other gNBs by the gNB 802 using a deactivation indication signal along with the served cell information.

[0101] Fig. 9 900 is a diagram illustrating a high-level example of an inter-gNB handover of an IAB host node in accordance with some aspects. The example illustrates a source gNB 904 requesting a handover of a UE 902 to a target gNB 906, wherein a handover request signal 908 is sent to the target gNB 906 over an Xn interface. The target gNB 906 performs admission control in block 910 and provides a new RRC configuration as part of a handover request confirmation signal 912. The source gNB 904 provides the RRC configuration to the UE by forwarding an RRC reconfiguration signal 914 received in the handover request confirmation signal 912. As shown, after receiving the RRC reconfiguration signal 914, the UE 902 switches to the new cell in block 916, moves the RRC connection to the target gNB 906, and replies with an RRC reconfiguration complete signal 918. The target gNB 906 then sends a UE context release signal 920 to the source gNB 904 to notify the source gNB 904 of the successful handover.

[0102] Fig.10 1000 is a diagram illustrating migration of an IAB node from a first IAB host node 1014 to a second IAB host node 1016 according to some aspects. Diagram 1000 may be part of an IAB network, such as described above in conjunction with Figure 5-6and 8-9 described. In this example, an IAB node 1002 (e.g., an L2 relay IAB node) is migrating from a first gNB 1020 represented by an IAB host CU1 1014 and an associated IAB host DU1 1012 to a second gNB 1022 represented by an IAB host CU2 1016 and an associated IAB host DU2 1018. The IAB node 1002 is configured with a mobile terminal function through an IAB-MT 1004 and a distributed unit function through an IAB-DUa 1006 and an IAB-DUb 1008. Those skilled in the art should understand that for the purpose of logical description, the IAB-DUa 1006 and IAB-DUb 1008 are shown as separate entities in the figure, and the IAB-DUa 1006 and IAB-DUb 1008 may also be configured as a single entity during operation. The IAB node 1002 can be connected to one or more child nodes or devices, depicted as UE 1030 in the figure.

[0103] The IAB host CU1 1014 may communicate with the IAB host CU2 1016 via an Xn interface. The IAB host CU1 1014 may be coupled to the IAB host DU1 1012 via an IP connection interface. Similarly, as shown, the IAB host CU2 1016 may be coupled to the IAB host DU2 1018 via a separate IP connection interface. The IAB host CU1 1014 may also be coupled to the IAB-DUa 1006 via an F1 control (F1-C) interface, and to the IAB-DUb 1008 via a separate F1-C interface.

[0104] During operation, the migration of the IAB node MT 1004 from the IAB host CU1 1014 to the IAB host CU2 1016 also requires the migration of the IAB-DUa 1006 and the IAB-DUb 1008. Migrating the IAB-DUa 1006 and the IAB-DUb 1008 to the IAB host CU2 1016 requires changing the NCGI of the cell (e.g., 1020) served by the IAB-DUa 1006 and the cell served by the IAB-DUb 1008, and may require changing the physical cell identifier (PCI). In addition, both the IAB host CU1 1014 and the IAB host CU2 1016 should know the new NCGI (e.g., 702) to transfer the child UE / MT of the migrated IAB node 1002 from the IAB host CU1 1014 to the IAB host CU2 1016. In some examples, the PCI of the migrated IAB-DUa 1006 can be broadcast over the air interface (NR) before the child UE / MT (e.g., 1030) can be migrated. Similarly, the PCI of the migrated IAB-DUb 1008 can be broadcast before the child UE / MT of the IAB-DUb 1008 can be migrated. As shown, the change of NCGI / PCI from the IAB host CU1 1014 to the IAB host CU2 1016 can be transmitted via the Xn interface. In some examples, when the IAB host CU1 1014 does not yet know the NCGI of these cells, the IAB host CU1 1014 can use the identifier of the IAB node 1002 to indicate to the IAB host CU2 1016 the cells on the migrated IAB-DUa 1006 (and IAB-DUb 1008).

[0105] In some examples, the IAB host CU1 1014 can establish a first signaling connection to the IAB node 1002, and can be configured to cause the IAB host DU1 1012 to provide a first cell configuration associated with the first IAB host CU1 1014 to the second IAB host CU2 1016 on the base station interface Xn (which can alternatively be an X2 interface), indicating one or more cells served by the IAB-DUa 1006. The first signaling connection can be implemented using F1-C or RRC, and the base station interface can be an Xn or X2 interface. The first cell configuration represents one or more cells activated by the first IAB host CU1 1014 on the IAB-DUa 1006 of the IAB node 1002. The cell configuration may include, but is not limited to, NCGI data carrying an identifier (gNB-ID) of the first IAB host, PCI data, activation status, and / or cell information. The cell information may include, but is not limited to, PLMN ID, area code, frequency or bandwidth, cell direction, cell size, cell mode (e.g., TDD, FDD), TDD configuration, measurement timing configuration, cell access information (e.g., prohibited cells) and / or connection support information (e.g., EN-DC).

[0106] The IAB host CU1 1014 may also provide the second IAB host CU2 1016 with a second cell configuration (to be migrated configuration) of another DU (IAB-DUb 1008) of the IAB node 1002, wherein the second cell configuration is used for one or more cells of the IAB-DUb 1008 associated with the first IAB host CU1 1014. The first IAB host CU1 1014 may derive the second cell configuration from the first cell configuration, for example, by mapping the NCGI. In some examples, the first IAB host CU1 1014 may receive the second cell configuration from the IAB node 1002 on a first signaling connection (e.g., via F1-C or RRC). In some examples, the second IAB host CU2 1016 may receive the second cell configuration from the IAB node 1002 on a second signaling connection (e.g., F1-C or RRC) established with the IAB node.

[0107] In some examples, the second IAB host CU2 1016 can derive the second cell configuration from the first cell configuration received from the first IAB host CU1 1014 on the base station interface (e.g., Xn or X2 interface) or from the IAB node 1002 on the second signaling connection (e.g., F1-C or RRC). For example, the second cell configuration can be derived using cell mapping, PCI changes (to avoid PCI conflicts), or existing PCIs (i.e., no PCI changes to minimize service interruptions at the child UE / MT). In some examples, the second IAB host CU2 1016 can provide the first IAB host CU1 1014 with a mapping between the first cell configuration and the second cell configuration using, for example, NCGI, PCI. In some examples, once the second cell configuration is received or derived, the second IAB host CU2 1016 can send the second cell configuration to the IAB node 1002 on the second signaling connection (e.g., F1-C or RRC). The second IAB host CU2 1016 may also indicate the mapping between the first and second cell configurations to the IAB node 1002 .

[0108] The first IAB host CU1 1014 may request the IAB host DU1 1012 to send the second cell configuration to the IAB node 1002 over the first signaling connection. In some examples, the first IAB host CU1 1014 may also provide a mapping between the first cell configuration and the second cell configuration to the second IAB host CU2 1016, for example, by NCGI.

[0109] The first IAB host CU1 1014 can indicate that the first or second cell configuration is for one or more cells served by the DU (e.g., IAB-DUa 1006, IAB-DUb 1008) by sending a configuration in a handover preparation, a secondary node (SN) addition preparation, an SN modification, or an SN change (which may include a third master node) of the IAB-MT 1004, wherein the first IAB host CU1 1014 is configured as a source host, a master node, or a source SN. By including an identifier of the IAB-MT 1004 on a base station interface (e.g., an Xn or X2 interface), the first IAB host CU1 1014 can indicate to the second IAB-host CU2 1016 that the first cell configuration is associated with one or more cells served by the IAB-DUa 1006, and the second cell configuration is associated with one or more cells served by the IAB-DUb 1008. The identifier may be configured as a NG-RAN node UE application protocol ID reference for IAB node 1002 MT related information transmission and reception between the first IAB host CU1 1014 and the second IAB host CU2 1016 on a base station interface (e.g., an Xn or X2 interface). In some examples, the identifier of the IAB-MT 1004 may be configured as IP address information or BAP address information assigned to the IAB node MT 1004 by the IAB host CU2 1016. These identifiers of the IAB-MT 1004 may be sent by the IAB node 1002 to the first IAB host CU1 1014, or requested by the first IAB host CU1 1014 on a first signaling connection (e.g., F1-C or RRC).

[0110] In some examples, the second IAB host CU2 1016 may provide the first IAB host CU1 1014 with a second cell configuration of the DU (e.g., IAB-DUb1008) of the IAB node 1002 associated with the second IAB host CU2 1016. For example, the second cell configuration information may be provided within a handover preparation message, an SN addition preparation message, an SN modification message, or an SN change message of the IAB-MT 1004. Here, the second IAB host CU2 1016 is configured as a target host, SN, or target SN. In some examples, the second IAB host CU2 1016 may send the first and / or second cell configurations and include an identifier of the IAB-MT1004 as described above to indicate that the configuration is for one or more cells served by the IAB node DU associated with the IAB-MT 1004.

[0111] In some examples, the first IAB host CU1 1014 may request the second IAB host CU2 1016 to send the second cell configuration by providing an identifier of the IAB-MT 1004. The first IAB host CU1 1014 may also request the second IAB host CU2 1016 to activate the cell on the IAB node DU (e.g., 1006, 1008) by providing an identifier of the collocated IAB-MT 1004. In some examples, the first IAB host CU1 1014 may use the second cell configuration in a subsequent handover request (or SN addition, SN change) to the second IAB host CU2 1016 of the child / descendant UE / MT of the IAB-DUb 1008. For example, the first IAB host CU1 1014 may indicate to the second IAB host CU2 1016 the target NCGI on the IAB-DUb 1008 of the IAB node 1002 received in the second cell configuration.

[0112] Fig.11 1 is a block diagram illustrating an example of a hardware implementation of a host node 1100 employing a processing system 1114. For example, the host node 1100 may be an IAB host node (e.g., 1014, 1016), or other RAN node (e.g., a base station such as a gNB) forming at least part of a decomposed base station, such as Figure 9-13 Any one or more of the following.

[0113] The host node 1100 may be implemented with a processing system 1114 including one or more processors 1104. Examples of processors 1104 include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform various functions described throughout this disclosure. In various examples, the RAN node 1100 may be configured to perform any one or more of the functions described herein. That is, the processor 1104 used in the host node 1100 may be used to implement any one or more of the processes and procedures described herein.

[0114] In some cases, the processor 1104 may be implemented via a baseband or modem chip, and in other implementations, the processor 1104 may include multiple devices distinct from the baseband or modem chip (e.g., in cases where they may work together to implement the examples discussed herein). As described above, various hardware arrangements and components other than a baseband modem processor may be used in implementations, including RF chains, power amplifiers, modulators, buffers, interleavers, adders / summers, etc.

[0115] In this example, the processing system 1114 may be implemented with a bus architecture, generally represented by bus 1102. Bus 1102 may include any number of interconnecting buses and bridges, depending on the specific application and overall design constraints of the processing system 1114. Bus 1102 communicatively couples various circuits together, including one or more processors (generally represented by processor 1104), memory 1105, and computer readable media (generally represented by computer readable media 1106). Bus 1102 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore are not further described.

[0116] The bus interface 1108 provides an interface between the bus 1102 and the communication interface 1110. The communication interface 1110 provides one or more communication interfaces or components for communicating with various other devices on a transmission medium (e.g., air, wire) through multiple communication interfaces (e.g., Xn, F1-C). Depending on the nature of the device, a user interface 1112 (e.g., keyboard, display, speaker, microphone, joystick, touch screen) may also be provided. Of course, such a user interface 1112 is optional and may be omitted in some examples.

[0117] The processor 1104 is responsible for managing the bus 1102 and general processing, including executing software stored on the computer-readable medium 1106. When executed by the processor 1104, the software causes the processing system 1114 to perform the various functions described herein for any particular device. The computer-readable medium 1106 and the memory 1105 may also be used to store data that is manipulated by the processor 1104 when executing the software.

[0118] One or more processors 1104 in the processing system can execute software. Software should be broadly interpreted to mean instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable programs, execution threads, processes, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. The software may reside on a computer-readable medium 1106.

[0119] Computer readable medium 1106 may be a non-transitory computer readable medium. As an example, non-transitory computer readable media include magnetic storage devices (e.g., hard disks, floppy disks, magnetic strips), optical disks (e.g., compact disks (CDs) or digital versatile disks (DVDs)), smart cards, flash memory devices (e.g., cards, sticks, or key drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. Computer readable medium 1106 may reside in processing system 1114, outside processing system 1114, or distributed across multiple entities including processing system 1114. Computer readable medium 1106 may be included in a computer program product. As an example, a computer program product may include a computer readable medium in a packaging material. Those skilled in the art will recognize how to best implement the described functions presented throughout this disclosure depending on the specific application and the overall design constraints imposed on the entire system.

[0120] In some aspects of the present disclosure, the processor 1104 may include circuits configured for various functions. In an example where the RAN node 1100 is an IAB host node, the processor 1104 may include a central unit (CU) circuit 1142 and a distributed unit (DU) circuit 1144. In an example where the RAN node 1100 is an L2 relay IAB node, the processor 1104 may include only a DU circuit 1144 (e.g., the CU circuit 1142 is omitted in this example). The CU circuit 1142 may also be configured to execute the CU software 1152 included on the computer-readable medium 1106 to implement one or more functions described herein. In addition, the DU circuit 1144 may also be configured to execute the DU software 1154 included on the computer-readable medium 1106 to implement one or more functions described herein.

[0121] CU circuitry 1142 may also include migration circuitry 1146, which may be configured to execute migration software 1156 contained in CU software 1152 of computer-readable medium 1152. DU circuitry 1144 may include migration circuitry 1148, which may be associated with migration circuitry 1146 of CU circuitry 1142 and configured to execute migration software 1158 contained in DU software 1154 of computer-readable medium 1106. In some examples, migration circuitry 1146 is configured to receive and process cell configuration data and cell information data associated with an IAB node (e.g., 1002), as described above in conjunction with Fig.10For migration purposes. The cell configuration may include, but is not limited to, NCGI data carrying an identifier (gNB-ID) of the IAB host (e.g., 1014), PCI data, activation status, and / or cell information. The cell information may include, but is not limited to, PLMN ID, area code, frequency or bandwidth, cell direction, cell size, cell mode (e.g., TDD, FDD), TDD configuration, measurement timing configuration, cell access information (e.g., prohibited cells), and / or connection support information (e.g., Evolved Universal Terrestrial Radio Access New Radio Dual Connectivity (EN-DC)). The migration circuit 1146 may also be configured to derive the cell configuration and perform the mapping functions (e.g., mapping of NCGI) as described above, and may provide connection data for migrating an IAB node (e.g., 1002) from one IAB host node (e.g., gNB) in the IAB network to another IAM host node.

[0122] Fig.12 1 is a flow chart illustrating a process 1200 for migrating a RAN node from a first host node to a second host node in a wireless communication network according to some aspects. In some examples, the communication network may include an IAB network. As described below, in certain implementations within the scope of the present disclosure, some or all of the illustrated features may be omitted, and some of the illustrated features may not be necessary for implementation of all examples. In some examples, the method may be performed by a host node 1100 (described above and as Fig.11 as shown), a processor or processing system, or any suitable component for performing the functions described.

[0123] In block 1202, a host node (e.g., a first host node) may receive cell configuration data associated with a RAN node (e.g., 1002) via a first communication interface (e.g., F1-C or RRC interface), the cell configuration data including data associated with one or more cells of the RAN node activated by the first host node. The cell configuration data may include, but is not limited to, one or more of an NR cell global identity (NCGI) (including an identifier (gNB-ID) of the first host node), PCI data, activation status, and / or cell information. The cell information may include one or more of a public land mobile network (PLMN) ID, an area code, a frequency or bandwidth, a cell direction, a cell size, a cell mode, a time division duplex (TDD) configuration, a measurement timing configuration, cell access information, and / or connection support information. In some examples, the first communication interface is one of an F1 control (F1-C) interface or a radio resource control (RRC) interface. In some examples, the first host node includes a source integrated access and backhaul (IAB) host node. In some examples, the first host node includes a first IAB host node, and the second host node includes a second IAB host node. For example, the above combination Fig.11 The processing circuitry 1104 in conjunction with the communication interface 1110 shown and described may provide means for receiving cell configuration data.

[0124] In block 1204, the first host node processes the cell configuration data to migrate one or more cells to the second host node. Fig.11 The CU circuitry 1142 and DU circuitry 1144 shown and described may provide components for processing cell configuration data.

[0125] In block 1206, the first host node sends the processed cell configuration data to the second host node via the second communication interface for migrating the RAN node from the first host node to the second host node. In some examples, the second communication interface can be configured as an Xn or X2 interface. The processed cell configuration data can be sent as a handover preparation message, a secondary node addition preparation message, a secondary node modification message, or a secondary node change message. In some examples, the above is combined with Fig.11 The depicted CU circuitry 1142 and DU circuitry 1144 along with the communication interface 1110 may provide means for sending processed cell configuration data to a second donor node for use in migrating the RAN node from the first donor node to the second donor node.

[0126] Fig.131 is a flow chart illustrating another process 1300 for migrating a RAN node from a first host node to a second host node according to some aspects. As described below, in certain implementations within the scope of the present disclosure, some or all of the illustrated features may be omitted, and some of the illustrated features may not be necessary for implementation of all examples. In some examples, the method may be performed by a host node 1100 (described above and as Fig.11 as shown), a processor or processing system, or any suitable component for performing the functions described.

[0127] In block 1302, a first host node (eg, 1020) receives first cell configuration data, which may be in combination with the above. Fig.10 For example, the first donor node may receive, via a first communication interface (e.g., F1-C or RRC interface), first cell configuration data associated with a RAN node (e.g., 1002), the cell configuration data including data associated with one or more cells of the RAN node activated by the first donor node. For example, the above combined Fig.11 The processing circuitry 1104 in conjunction with the communication interface 1110 shown and described may provide means for receiving first cell configuration data.

[0128] In block 1304, the first host node may obtain second cell configuration data associated with the RAN node (e.g., 1002). The second cell configuration data includes data associated with one or more cells of the RAN node activated by the first host node. With respect to obtaining the second cell configuration data, process 1300 illustrates three alternative processes, as indicated by the dotted lines in the figure. In block 1306, as described above, the second cell configuration data associated with the RAN node may be derived from the first cell configuration data in the first host node via a mapping between the first cell configuration data and the second cell configuration data. Alternatively, in block 1308, the second cell configuration associated with the RAN node data may be obtained via a first communication interface (e.g., (e.g., F1-C or RRC)). In another alternative, as shown in block 1310, the second cell configuration data associated with the RAN node may be received via a second communication interface (e.g., Xn, X2). For example, in combination with the above Fig.11 The processing circuitry 1104 in conjunction with the communication interface 1110 shown and described may provide means for receiving second cell configuration data.

[0129] In block 1312, the first host node sends the first and / or second cell configuration with or without mapping data to the second host node. For example, the first host node may send the second cell configuration data to the second host node via the second communication interface for migrating the RAN node from the first host node to the second host node. In some examples, the above Fig.11 The depicted CU circuitry 1142 , DU circuitry 1144 , together with the communication interface 1110 , may provide components for receiving and processing cell configuration data, and mapping and / or sending the processed cell configuration data to a second donor node for migration.

[0130] In one configuration, the host node (e.g., the DU and / or CU of the IAB base station) includes various components as described in the present disclosure. In one aspect, the aforementioned components may be Fig.11 The processor 1104 shown in is configured to perform the functions described by the aforementioned components. On the other hand, the aforementioned components may be a circuit or any device configured to perform the functions described by the aforementioned components.

[0131] Of course, in the above examples, the circuits included in the processor 1104 are provided only as examples, and other components for performing the described functions may be included in various aspects of the present disclosure, including but not limited to instructions stored in the computer-readable medium 1106, or in Figure 1-2 , 4-6 and 8-11 and using, for example, Fig.12 and 13 Any other suitable means or components of the described processes and / or algorithms.

[0132] Figure 12-13 The illustrated processes may include additional aspects, such as any single aspect or any combination of aspects described below and / or in combination with one or more other processes described elsewhere herein.

[0133] Aspect 1: A method for migrating a radio access network (RAN) node associated with a first host node in a communication network, comprising: receiving cell configuration data associated with the RAN node via a first communication interface in the first host node, the cell configuration data including data associated with one or more cells of the RAN node activated by the first host node; processing the cell configuration data to migrate the one or more cells to a second host node; and sending the processed cell configuration data to the second host node via a second communication interface for migrating the RAN node from the first host node to the second host node.

[0134] Aspect 2: The method according to aspect 1, wherein the first communication interface is one of an F1 control (F1-C) interface or a radio resource control (RRC) interface; and the second communication interface is one of an Xn interface or an X2 interface.

[0135] Aspect 3: The method according to aspect 1 or 2, wherein the first host node comprises a source integrated access and backhaul (IAB) host node.

[0136] Aspect 4: A method according to any one of Aspects 1 to 3, wherein the cell configuration data includes one or more of NR cell global identity (NCGI), physical cell identifier (PCI) data, activation status or cell information, wherein the NCGI includes an identifier of the first host node.

[0137] Aspect 5: A method according to any one of Aspects 1 to 4, wherein the cell information includes one or more of a public land mobile network (PLMN) identifier (ID), an area code, a frequency or bandwidth, a cell direction, a cell size, a cell mode, a time division duplex (TDD) configuration, a measurement timing configuration, a cell access information, or a connection support information.

[0138] Aspect 6: The method according to any one of Aspects 1 to 5 further includes: obtaining second cell configuration data associated with the RAN node, the second cell configuration data including data associated with one or more cells of the RAN node activated by the first host node; and sending the second cell configuration data to the second host node via the second communication interface for migrating the RAN node from the first host node to the second host node.

[0139] Aspect 7: The method according to any one of aspects 1 to 6, wherein obtaining the second cell configuration data associated with the RAN node comprises deriving the second cell information from the first cell configuration via mapping.

[0140] Aspect 8: The method according to any one of aspects 1 to 7, wherein obtaining the second cell configuration data associated with the RAN node comprises receiving the second cell configuration data from the RAN node via the first communication interface.

[0141] Aspect 9: The method according to any one of aspects 1 to 8, wherein obtaining the second cell configuration data associated with the RAN node comprises receiving the second cell configuration data from the second donor node via the second communication interface.

[0142] Aspect 10: The method according to any one of aspects 1 to 9, wherein the second cell configuration comprises mapping data for mapping between the first cell configuration data and the second cell configuration data.

[0143] Aspect 11: A method according to any one of Aspects 1 to 10, wherein sending the processed cell configuration data comprises sending the processed cell configuration data in one of a handover preparation message, a secondary node addition preparation message, a secondary node modification message or a secondary node change message.

[0144] Aspect 12: The method according to any one of aspects 1 to 11, wherein the communication network comprises an integrated access and backhaul (IAB) network.

[0145] Aspect 13: The method according to any one of aspects 1 to 12, wherein the first host node comprises a first IAB host node, and the second host node comprises a second IAB host node.

[0146] Aspect 14: A device in a wireless communication network, comprising a first communication interface, a second communication interface, a memory, and a processor coupled to the first communication interface, the second communication interface, and the memory, wherein the processor and the memory are configured to execute the method described in any one of Aspects 1 to 13.

[0147] Aspect 15: An apparatus in a wireless communication network, comprising components for performing the method of any one of Aspects 1 to 13.

[0148] Aspect 16: A non-transitory computer-readable medium storing therein instructions executable by one or more processors of a device to implement the method of any one of aspects 1 to 13.

[0149] Several aspects of wireless communication networks have been presented with reference to exemplary implementations. As those skilled in the art will readily appreciate, various aspects described throughout this disclosure may be extended to other telecommunication systems, network architectures, and communication standards.

[0150] For example, various aspects may be implemented in other systems defined by 3GPP, such as Long Term Evolution (LTE), Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile (GSM). Various aspects may also be extended to systems defined by the Third Generation Partnership Project 2 (3GPP2), such as CDMA2000 and / or Evolution Data Optimized (EV-DO). Other examples may be implemented in systems employing IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra Wideband (UWB), Bluetooth, and / or other suitable systems. The actual telecommunication standard, network architecture, and / or communication standard employed will depend on the specific application and the overall design constraints imposed on the system.

[0151] Within the present disclosure, the word "exemplary" is used to mean "serving as an example, instance, or illustration". Any implementation or aspect described herein as "exemplary" is not necessarily to be construed as being preferred or advantageous over other aspects of the present disclosure. Likewise, the term "aspect" does not require that all aspects of the present disclosure include the features, advantages, or modes of operation discussed. The term "coupled" as used herein refers to a direct or indirect coupling between two objects. For example, if object A physically contacts object B, and object B contacts object C, then objects A and C can still be considered to be coupled to each other - even if they are not in direct physical contact with each other. For example, a first object can be coupled to a second object even if the first object has never been in direct physical contact with the second object. The terms "circuit" and "circuitry" are used broadly and are intended to include both hardware implementations of electrical devices and conductors and software implementations of information and instructions, where these electrical devices and conductors, when connected and configured, implement the performance of the functions described in the present disclosure, without limitation to the type of electronic circuits, which, when executed by a processor, implement the performance of the functions described in the present disclosure.

[0152] Figure 1-13 One or more of the components, steps, features and / or functions shown in the drawings may be rearranged and / or combined into a single component, step, feature or function, or may be embodied in several components, steps or functions. Additional elements, components, steps and / or functions may also be added without departing from the novel features disclosed herein. Figure 1-2 , 4-6 and 8-11 shown in the apparatus, device and / or components can be configured to perform the method described herein, features or steps in one or more. The novel algorithm described here can also be effectively implemented in software and / or embedded in hardware.

[0153] It should be understood that the specific order or hierarchy of steps in the disclosed methods is an illustration of an exemplary process. Based on design preferences, it should be understood that the specific order or hierarchy of steps in the methods can be rearranged. The accompanying method claims present elements of the various steps in an example order, and are not meant to be limited to the specific order or hierarchy presented unless specifically stated therein.

[0154] The foregoing description is provided to enable those skilled in the art to practice the various aspects described herein. It will be readily apparent to those skilled in the art that various modifications to these aspects are to be made, and the general principles defined herein may be applicable to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but to conform to the full scope consistent with the language of the claims, wherein, unless otherwise specifically stated, reference to an element in the singular form is not intended to mean "one and only one", but rather "one or more". Unless otherwise specifically stated, the term "some" refers to one or more. A phrase referring to "at least one" in a list of items refers to any combination of these items, including a single member. As an example, "at least one of a, b, or c" is intended to cover a; b; c; a and b; a and c; b and c; and a, b, and c. All structural and functional equivalents of elements throughout the various aspects described in this disclosure that are known or will be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims.

Claims

1. A method for migrating a radio access network RAN ​​node associated with a first IAB host node in an integrated access and backhaul IAB network, comprising: receiving, in the first IAB donor node via a first communication interface, first cell configuration data associated with the RAN node, the first cell configuration data comprising data associated with one or more cells of the RAN node activated by the first IAB donor node, wherein the RAN node is configured with at least one IAB mobile terminal function IAB-MT and at least one IAB distributed unit function IAB-DU, and wherein the first cell configuration data comprises one or more New Radio NR Cell Global Identifiers NCGI; processing the first cell configuration data to migrate the one or more cells to a second IAB host node; as well as The processed first cell configuration data is sent to the second IAB host node via a second communication interface, for migrating the RAN node from the first IAB host node to the second IAB host node.

2. The method according to claim 1, wherein The first communication interface is one of an F1 control F1-C interface or a radio resource control RRC interface; The second communication interface is one of an Xn interface and an X2 interface. 3 . The method of claim 1 , wherein the first IAB host node comprises a source IAB host node. 4 . The method of claim 1 , wherein the one or more NCGIs include an identifier of the first IAB host node, physical cell identifier (PCI) data, an activation status, or cell information.

5. The method according to claim 4, wherein the cell information comprises one or more of a public land mobile network PLMN identifier ID, an area code, a frequency or bandwidth, a cell direction, a cell size, a cell mode, a time division duplex TDD configuration, a measurement timing configuration, a cell access information, or a connection support information.

6. The method according to claim 1, further comprising: obtaining second cell configuration data associated with the RAN node, the second cell configuration data comprising data associated with one or more cells of the RAN node activated by the first IAB donor node; as well as The second cell configuration data is sent to the second IAB host node via the second communication interface, so as to migrate the RAN node from the first IAB host node to the second IAB host node.

7. The method of claim 6, wherein obtaining the second cell configuration data associated with the RAN node comprises deriving second cell information from a first cell configuration via a mapping.

8. The method of claim 6, wherein obtaining the second cell configuration data associated with the RAN node comprises receiving the second cell configuration data from the RAN node via the first communication interface.

9. The method of claim 6, wherein obtaining the second cell configuration data associated with the RAN node comprises receiving the second cell configuration data from the second IAB donor node via the second communication interface. 10 . The method according to claim 9 , wherein the second cell configuration comprises mapping data for mapping between the first cell configuration data and the second cell configuration data.

11. The method of claim 1, wherein sending the processed first cell configuration data comprises sending the processed first cell configuration data in one of a handover preparation message, a secondary node addition preparation message, a secondary node modification message, or a secondary node change message.

12. A first IAB host node in an integrated access and backhaul IAB network, comprising: a first communication interface; A second communication interface; Memory; and a processor communicatively coupled to the transceiver and the memory, wherein the processor is configured to: receiving, in the first IAB donor node via a first communication interface, first cell configuration data associated with a radio access network RAN ​​node, the first cell configuration data comprising data associated with one or more cells of the RAN node activated by the first IAB donor node, wherein the RAN node is configured with at least one IAB mobile terminal function IAB-MT and at least one IAB distributed unit function IAB-DU, and wherein the first cell configuration data comprises one or more New Radio NR Cell Global Identifiers NCGI; processing the first cell configuration data to migrate the one or more cells to a second IAB host node; as well as The processed first cell configuration data is sent to the second IAB host node via a second communication interface, for migrating the RAN node from the first IAB host node to the second IAB host node.

13. The first IAB host node according to claim 12, wherein The first communication interface is one of an F1 control F1-C interface or a radio resource control RRC interface; The second communication interface is one of an Xn interface and an X2 interface.

14. The first IAB host node of claim 12, wherein the first IAB host node comprises a source IAB host node. 15 . The first IAB host node of claim 14 , wherein the one or more NCGIs include an identifier of the first IAB host node, physical cell identifier (PCI) data, an activation status, or cell information.

16. The first IAB host node according to claim 15, wherein the cell information comprises one or more of a public land mobile network PLMN identifier ID, an area code, a frequency or bandwidth, a cell direction, a cell size, a cell mode, a time division duplex TDD configuration, a measurement timing configuration, a cell access information, or a connection support information.

17. The first IAB host node according to claim 12, further comprising: obtaining second cell configuration data associated with the RAN node, the second cell configuration data comprising data associated with one or more cells of the RAN node activated by the first IAB donor node; as well as The second cell configuration data is sent to the second IAB host node via the second communication interface, so as to migrate the RAN node from the first IAB host node to the second IAB host node.

18. The first IAB host node of claim 17, wherein obtaining the second cell configuration data associated with the RAN node comprises deriving second cell information from first cell configuration via mapping.

19. The first IAB host node of claim 17, wherein obtaining the second cell configuration data associated with the RAN node comprises receiving the second cell configuration data from the RAN node via the first communication interface.

20. The first IAB donor node of claim 17, wherein obtaining the second cell configuration data associated with the RAN node comprises receiving the second cell configuration data from the second IAB donor node via the second communication interface.

21. The first IAB host node according to claim 20, wherein the second cell configuration comprises mapping data for mapping between the first cell configuration data and the second cell configuration data.

22. The first IAB host node of claim 12, wherein sending the processed first cell configuration data comprises sending the processed first cell configuration data in one of a handover preparation message, a secondary node addition preparation message, a secondary node modification message, or a secondary node change message.

23. A first IAB host node in an integrated access and backhaul IAB network, comprising: means for receiving, in the first IAB donor node via a first communication interface, first cell configuration data associated with a radio access network RAN ​​node, the first cell configuration data comprising data associated with one or more cells of the RAN node activated by the first IAB donor node, wherein the RAN node is configured with at least one IAB mobile terminal function IAB-MT and at least one IAB distributed unit function IAB-DU, and wherein the first cell configuration data comprises one or more New Radio NR Cell Global Identity NCGI; means for processing the first cell configuration data to migrate the one or more cells to a second IAB host node; as well as means for sending the processed first cell configuration data to the second IAB host node via a second communication interface for migrating the RAN node from the first IAB host node to the second IAB host node.

24. The first IAB host node according to claim 23, wherein The first communication interface is one of an F1-C or a radio resource control, RRC, interface; and The second communication interface is one of an Xn or X2 interface.

25. The first IAB host node according to claim 23, further comprising: means for obtaining second cell configuration data associated with the RAN node, the second cell configuration data comprising data associated with one or more cells of the RAN node activated by the second IAB donor node; as well as means for sending the second cell configuration data to the second IAB host node via the second communication interface for migrating the RAN node from the first IAB host node to the second IAB host node.

26. A non-transitory computer-readable medium having stored therein instructions executable by one or more processors of a first integrated access and backhaul (IAB) host node to: receiving, in the first IAB donor node via a first communication interface, first cell configuration data associated with a radio access network RAN ​​node, the first cell configuration data comprising data associated with one or more cells of the RAN node activated by the first IAB donor node, wherein the RAN node is configured with at least one IAB mobile terminal function IAB-MT and at least one IAB distributed unit function IAB-DU, and wherein the first cell configuration data comprises one or more New Radio NR Cell Global Identifiers NCGI; processing the first cell configuration data to migrate the one or more cells to a second IAB host node; as well as The processed first cell configuration data is sent to the second IAB host node via a second communication interface, for migrating the RAN node from the first IAB host node to the second IAB host node.

Images