Integrated access and backhaul network random access parameter optimization

Abstract

The apparatus obtains random access information for at least one of a donor node serving a node or a neighbor cell of the node, and determines one or more random access parameters for the device to use in performing a random procedure with the node. The one or more random access parameters are based on the obtained random access information. The apparatus may be an IAB node.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Application No. 62 / 903,456, filed on September 20, 2019, entitled “INTEGRATED ACCESS AND BACKHAUL NETWORK RANDOMACCESS PARAMETER OPTIMIZATION,” and U.S. Patent Application No. 17 / 021,252, filed on September 15, 2020, entitled “INTEGRATED ACCESS AND BACKHAUL NETWORK RANDOMACCESS PARAMETER OPTIMIZATION,” which are expressly incorporated herein by reference in their entirety. background Technical Field

[0004] The present disclosure relates generally to communication systems and, more particularly, to an Integrated Access and Backhaul (IAB) network.

[0005] introduction

[0006] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0007] These multiple access technologies have been adopted in various telecommunication standards to provide common protocols that enable different wireless devices to communicate at city, country, region, and even global levels. An example telecommunication standard is 5G New Radio (NR). 5G NR is a part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5GNR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Some aspects of 5G NR can be based on 4G Long Term Evolution (LTE) standards. There is a need for further improvements to 5G NR technology. These improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies.

[0008] Overview

[0009] A brief summary of one or more aspects is given below to provide a basic understanding of such aspects. This summary is not an exhaustive overview of all conceived aspects, and is neither intended to identify the key or critical elements of all aspects nor to define the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description that will be presented later.

[0010] An integrated access and backhaul (IAB) network may include multiple cellular cells that communicate with each other to provide an access network and a backhaul network to a core network. Each node in an IAB network may have a random access configuration that includes random access parameters for use by a user equipment (UE) during a random access procedure with an IAB node. The nodes of an IAB network may be numerous and may be close together, making network planning for random access configurations and / or random access parameters difficult or impractical.

[0011] The IAB node obtains random access information for at least one of the donor node serving the node or the neighbor cell of the node, and determines one or more random access parameters for the device to use to perform a random procedure with the node. The random access information for the service node or the neighbor cell may be a random access configuration of the service node or the neighbor cell. The one or more random access parameters are based on the acquired random access information. The IAB node may reconfigure its random access configuration to include the determined random access parameters. The IAB node may determine the random access parameters by checking the random access configuration received from the service node or the neighbor cell. Additionally or alternatively, the IAB node may send the random access configuration received from the neighbor cell to the service node and determine the random access parameters based on the random access parameters received from the service node in response.

[0012] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus obtains random access information for at least one of a donor node serving the node or a neighbor cell of the node at a mobile terminal (MT) of a node. The apparatus determines one or more random access parameters for a device to use to perform a random procedure with the node, wherein the one or more random access parameters are based on the obtained random access information.

[0013] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus receives a report from a node served by a central unit (CU), the report including random access information of at least one of a donor node serving the node or a neighbor cell of the node acquired by the node. The apparatus determines one or more random access parameters for a device to use to perform a random procedure with the node, wherein the one or more random access parameters are determined based on the acquired random access information. The apparatus sends the one or more random access parameters to the node.

[0014] To achieve the foregoing and related ends, the one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and drawings set forth in detail certain illustrative features of the one or more aspects. However, these features are merely indicative of several of the various ways in which the principles of the various aspects may be employed, and this description is intended to cover all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.

[0017] Figure 2A , 2B, 2C, and 2D are diagrams illustrating examples of a first 5G / NR frame, a DL channel within a 5G / NR subframe, a second 5G / NR frame, and a UL channel within a 5G / NR subframe, respectively.

[0018] Figure 3 is a diagram illustrating an example of a base station and a user equipment (UE) in an access network.

[0019] Figure 4 is a diagram illustrating the IAB network.

[0020] Figure 5 is a diagram illustrating the IAB network and its components.

[0021] Figure 6 Examples of interactions between an IAB donor, an IAB node, and child IAB nodes are illustrated.

[0022] Figure 7 is a communication diagram illustrating RACH optimized communication between a UE, a base station, and another base station.

[0023] Figure 8 is a communication diagram illustrating random access procedure communication in an IAB network.

[0024] Fig. 9 is a flow chart of a wireless communication method.

[0025] Fig.10 is a conceptual data flow diagram illustrating the flow of data between different devices / components in an example arrangement.

[0026] Fig.11 is a diagram illustrating an example of a hardware implementation for an apparatus employing a processing system.

[0027] Fig.12 is a flow chart of a wireless communication method.

[0028] Fig.13 is a conceptual data flow diagram illustrating the flow of data between different devices / components in an example arrangement.

[0029] Fig.14 is a diagram illustrating an example of a hardware implementation for an apparatus employing a processing system.

[0030] Detailed Description

[0031] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. This detailed description includes specific details to provide 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 instances, well-known structures and components are shown in block diagram form in order to avoid diluting such concepts.

[0032] Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0033] As an example, an element, or any part of an element, or any combination of elements may be implemented as a "processing system" including one or more processors. Examples of processors include: microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gating logic, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout this disclosure. One or more processors in a processing system may execute software. Software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether it is described in software, firmware, middleware, microcode, hardware description languages, or other terms.

[0034] Accordingly, in one or more example embodiments, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, these functions may be stored or encoded on a computer-readable medium as one or more instructions or codes. Computer-readable media include computer storage media. Storage media may be any available medium that can be accessed by a computer. As an example and not limitation, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, a combination of computer-readable media of the above types, or any other medium that may be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0035] Figure 1 1 is a diagram illustrating an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a UE 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). A macro cell includes a base station. A small cell includes a femto cell, a pico cell, and a micro cell.

[0036] The base station 102 configured for 4G LTE (collectively referred to as the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with the EPC 160 via a first backhaul link 132 (e.g., an S1 interface). The base station 102 configured for 5G NR (collectively referred to as the Next Generation RAN (NG-RAN)) can interface with the core network 190 via a second backhaul link 184. Among other functions, the base station 102 can also perform one or more of the following functions: delivery of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, positioning, and delivery of alert messages. The base stations 102 may communicate with each other directly or indirectly (eg, through the EPC 160 or the core network 190) over a third backhaul link 134 (eg, an X2 interface). The third backhaul link 134 may be wired or wireless.

[0037] Base stations 102 may communicate wirelessly with UEs 104. Each base station 102 may provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network that includes both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). A communication link 120 between a base station 102 and a UE 104 may include an uplink (UL) (also referred to as a reverse link) transmission from the UE 104 to the base station 102 and / or a downlink (DL) (also referred to as a forward link) transmission from the base station 102 to the UE 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. These communication links may be over one or more carriers. For each carrier allocated in a carrier aggregation of up to Yx MHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use a spectrum of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.) bandwidth. These carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). The component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell), and the secondary component carrier may be referred to as a secondary cell (SCell).

[0038] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). The D2D communication may be through a variety of wireless D2D communication systems, such as, for example, FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0039] The wireless communication system may further include a Wi-Fi access point (AP) 150 communicating with a Wi-Fi station (STA) 152 in the 5 GHz unlicensed spectrum via a communication link 154. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform a clear channel assessment (CCA) to determine whether the channel is available prior to communication.

[0040] The small cell 102' may operate in a licensed and / or unlicensed spectrum. When operating in an unlicensed spectrum, the small cell 102' may employ NR and use the same 5 GHz unlicensed spectrum as used by the Wi-Fi AP 150. The small cell 102' employing NR in the unlicensed spectrum may boost the coverage of the access network and / or increase the capacity of the access network.

[0041] Whether a small cell 102' or a large cell (e.g., a macro base station), the base station 102 may include and / or be referred to as an eNB, a gB node (gNB), or another type of base station. Some base stations (such as gNB 180) may operate in traditional sub-6 GHz spectrum, millimeter wave (mmW) frequencies, and / or near mmW frequencies to communicate with UE 104. When gNB 180 operates in mmW or near mmW frequencies, gNB 180 may be referred to as a mmW base station. Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 mm and 10 mm. The radio waves in this band may be referred to as millimeter waves. Near mmW can be extended down to 3 GHz frequencies with a wavelength of 100 mm. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, which is also referred to as centimeter waves. Communications using mmW / near mmW radio frequency bands (e.g., 3 GHz–300 GHz) have extremely high path loss and short range. The mmW base station 180 may utilize beamforming 182 with the UE 104 to compensate for the extremely high path loss and short range. The base station 180 and the UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays to facilitate beamforming.

[0042] Base station 180 may transmit beamformed signals to UE 104 in one or more transmit directions 182'. UE 104 may receive beamformed signals from base station 180 in one or more receive directions 182". UE 104 may also transmit beamformed signals to base station 180 in one or more transmit directions. Base station 180 may receive beamformed signals from UE 104 in one or more receive directions. Base station 180 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each of base station 180 / UE 104. The transmit direction and receive direction of base station 180 may be the same or may be different. The transmit direction and receive direction of UE 104 may be the same or may be different.

[0043] The EPC 160 may include a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and a packet data network (PDN) gateway 172. The MME 162 may be in communication with a home subscriber server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. In general, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are delivered through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation and other functions. The PDN gateway 172 and the BM-SC 170 are connected to IP services 176. The IP services 176 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and / or other IP services. The BM-SC 170 may provide functionality for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS transmissions, may be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and may be used to schedule MBMS transmissions. The MBMS gateway 168 may be used to distribute MBMS traffic to base stations 102 belonging to a multicast broadcast single frequency network (MBSFN) area that broadcasts a specific service, and may be responsible for session management (start / stop) and for collecting eMBMS-related charging information.

[0044] The core network 190 may include an access and mobility management function (AMF) 192, other AMFs 193, a session management function (SMF) 194, and a user plane function (UPF) 195. AMF 192 may be in communication with a unified data management (UDM) 196. AMF 192 is a control node that handles signaling between UE 104 and the core network 190. In general, AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are delivered through UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 is connected to IP services 197. IP services 197 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and / or other IP services.

[0045] A base station may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmission reception point (TRP), or some other suitable term. The base station 102 provides an access point to the EPC 160 or the core network 190 for the UE 104. Examples of UE 104 include a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a tablet device, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a health care device, an implant, a sensor / actuator, a display, or any other similar functional device. Some UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, ovens, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.

[0046] Reference again Figure 1In some aspects, the wireless communication system and access network 100 may include an IAB network, for example, including an IAB node 103. The base station 102 / 180 in communication with the IAB node 103 may be or include a control node or an IAB donor node 180a. In some aspects, the IAB node 103 may be configured to determine a parameter for the UE 104 to use to perform a random access procedure with the IAB node 103. The IAB node 103 may include a parameter determination component 198 configured to determine the parameter based on system information received from a neighboring node or a message received from the IAB donor 180a. The IAB donor 180a may include a centralized determination component 198 configured to determine the value of the parameter, for example, based on system information received by the IAB node 103. Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar fields, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0047] Figure 2A 200 is a diagram illustrating an example of a first subframe within a 5G / NR frame structure. Figure 2B FIG230 is a diagram illustrating an example of DL channels within a 5G / NR subframe. Figure 2C 250 is a diagram illustrating an example of a second subframe within a 5G / NR frame structure. Figure 2D 280 is a diagram illustrating an example of an UL channel within a 5G / NR subframe. The 5G / NR frame structure may be FDD, where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL, or TDD, where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL. Figure 2A , 2C In the example provided, the 5G / NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (mostly DL) and subframe 3 is configured with slot format 34 (mostly UL), where D is DL, U is UL, and X is for flexible use between DL / UL. Although subframes 3 and 4 are shown as having slot formats 34 and 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are full DL and full UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The UE is configured with a slot format (dynamically configured by DL control information (DCI) or semi-statically / statically configured by radio resource control (RRC) signaling) through the received slot format indicator (SFI). Note that the following description also applies to the 5G / NR frame structure for TDD.

[0048] Other wireless communication technologies may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 equally sized subframes (1ms). Each subframe may include one or more time slots. A subframe may also include mini-slots, which may include 7, 4, or 2 symbols. Each time slot may include 7 or 14 symbols, depending on the time slot configuration. For time slot configuration 0, each time slot may include 14 symbols, and for time slot configuration 1, each time slot may include 7 symbols. The symbols on the DL may be cyclic prefix (CP) OFDM (CP-OFDM) symbols. The symbols on the UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also known as single carrier frequency division multiple access (SC-FDMA) symbols) (for power-limited scenarios; limited to single stream transmission). The number of time slots within a subframe is based on the time slot configuration and parameter design. For slot configuration 0, different parameter designs μ of 0 to 5 allow 1, 2, 4, 8, 16, and 32 slots per subframe, respectively. For slot configuration 1, different parameter designs 0 to 2 allow 2, 4, and 8 slots per subframe, respectively. Accordingly, for slot configuration 0 and parameter design μ, there are 14 symbols per slot and 2 per subframe. μ time slots. The subcarrier spacing and symbol length / duration vary depending on parameter design. The subcarrier spacing can be equal to 2 μ *15kHz, where μ is parameter design 0 to 5. Thus, parameter design μ=0 has a subcarrier spacing of 15kHz, while parameter design μ=5 has a subcarrier spacing of 480kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figures 2A-2D An example of slot configuration 0 with 14 symbols per slot and parameter design μ=0 is provided, with 1 slot per subframe. The subcarrier spacing is 15 kHz and the symbol duration is about 66.7 μs.

[0049] Other wireless communication technologies may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 equally sized subframes (1ms). Each subframe may include one or more time slots. A subframe may also include mini-slots, which may include 7, 4, or 2 symbols. Each time slot may include 7 or 14 symbols, depending on the time slot configuration. For time slot configuration 0, each time slot may include 14 symbols, and for time slot configuration 1, each time slot may include 7 symbols. The symbols on the DL may be cyclic prefix (CP) OFDM (CP-OFDM) symbols. The symbols on the UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also known as single carrier frequency division multiple access (SC-FDMA) symbols) (for power-limited scenarios; limited to single stream transmission). The number of time slots within a subframe is based on the time slot configuration and parameter design. For slot configuration 0, different parameter designs μ of 0 to 5 allow 1, 2, 4, 8, 16, and 32 slots per subframe, respectively. For slot configuration 1, different parameter designs 0 to 2 allow 2, 4, and 8 slots per subframe, respectively. Accordingly, for slot configuration 0 and parameter design μ, there are 14 symbols per slot and 2 per subframe. μ time slots. The subcarrier spacing and symbol length / duration vary depending on parameter design. The subcarrier spacing can be equal to 2 μ *15kHz, where μ is parameter design 0 to 5. Thus, parameter design μ=0 has a subcarrier spacing of 15kHz, while parameter design μ=5 has a subcarrier spacing of 480kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figures 2A-2D An example of slot configuration 0 with 14 symbols per slot and parameter design μ=0 is provided, with 1 slot per subframe. The subcarrier spacing is 15 kHz and the symbol duration is about 66.7 μs.

[0050] like Figure 2A As illustrated in FIG, some REs carry reference (pilot) signals (RS) for UEs. RSs may include demodulation RSs (DM-RSs) for channel estimation at the UE (indicated as Rx for one specific configuration, where 100x is the port number, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RSs). RSs may also include beam measurement RSs (BRSs), beam refinement RSs (BRRSs), and phase tracking RSs (PT-RSs).

[0051] Figure 2BAn example of various DL channels within a subframe of an explanation frame. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs), each CCE includes 9 RE groups (REGs), and each REG includes 4 consecutive REs in an OFDM symbol. The primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by the UE 104 to determine the subframe / symbol timing and the physical layer identity. The secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE may determine the physical cell identifier (PCI). Based on the PCI, the UE may determine the location of the aforementioned DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) may be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block. The MIB provides the number of RBs in the system bandwidth, as well as the system frame number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH (such as System Information Blocks (SIBs)), and paging messages.

[0052] As in Figure 2C As illustrated in FIG, some REs carry DM-RSs for channel estimation at the base station (indicated as R for one particular configuration, but other DM-RS configurations are possible). The UE may transmit DM-RSs for the physical uplink control channel (PUCCH) and DM-RSs for the physical uplink shared channel (PUSCH). The PUSCH DM-RS may be transmitted in the first or first two symbols of the PUSCH. The PUCCH DM-RS may be transmitted in different configurations depending on whether a short PUCCH or a long PUCCH is transmitted and on the specific PUCCH format used. Although not shown, the UE may transmit a sounding reference signal (SRS). The SRS may be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0053] Figure 2D An example of various UL channels within a subframe of an illustration frame. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), and HARQ ACK / NACK feedback. The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0054] Figure 33 is a block diagram of a base station 310 in communication with a UE 350 in an access network. In the DL, IP packets from the EPC 160 may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a media access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration of UE measurement reports; PDCP layer functionality associated with header compression / decompression, security (ciphering, cipher decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0055] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time domain and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine coding and modulation schemes and for spatial processing. The channel estimates may be derived from reference signals and / or channel condition feedback transmitted by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX may modulate an RF carrier with a corresponding spatial stream for transmission.

[0056] At the UE 350, each receiver 354RX receives a signal through its corresponding antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for the UE 350. If there are multiple spatial streams destined for the UE 350, they can be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then transforms the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, as well as the reference signal, are recovered and demodulated by determining the signal constellation point most likely transmitted by the base station 310. These soft decisions can be based on the channel estimates calculated by the channel estimator 358. These soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted on the physical channel by the base station 310. These data and control signals are then provided to the controller / processor 359 which implements layer 3 and layer 2 functionality.

[0057] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport channels and logical channels, packet reassembly, cipher interpretation, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0058] Similar to the functionality described in conjunction with DL transmissions performed by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression, and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing MAC SDUs onto TBs, demultiplexing MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0059] Channel estimates derived by a channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by a TX processor 368 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with a corresponding spatial stream for transmission.

[0060] UL transmissions are processed at the base station 310 in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318RX receives a signal through its respective antenna 320. Each receiver 318RX recovers information modulated onto an RF carrier and provides the information to a RX processor 370.

[0061] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, cipher decoding, header decompression, control signal processing to recover IP packets from the UE 350. The IP packets from the controller / processor 375 may be provided to the EPC 160. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0062] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform operations related to Figure 1 The 198 combined aspects.

[0063] Figure 4 4 is a diagram illustrating an IAB network 400. The IAB network 400 may include an anchor node or control node (which may be referred to herein as an "IAB donor") 410 and an access node (which may be referred to herein as an "IAB node") 420. The IAB donor 410 may be a base station, such as a gNB or an eNB, and may perform a function for controlling the IAB network 400. The IAB node 420 may include an L2 relay node, etc. The IAB donor 410 and the IAB node 420 share resources together to provide an access network and a backhaul network to the core network 490. For example, resources may be shared between an access link and a backhaul link in the IAB network.

[0064] UE 430 interfaces with IAB node 420 or IAB donor 410 via access link 470. IAB nodes 420 communicate with each other and with IAB donor 410 via backhaul link 460. IAB donor is connected to core network 490 via wired backhaul link 450. UE 430 communicates with core network by relaying messages to IAB network 400 via their respective access link 470, which can then relay the message to IAB donor 410 via backhaul link 460 to communicate with core network via wired backhaul link 450. Similarly, core network can communicate with UE 430 by sending messages to IAB donor 410 via wired backhaul link 450. The IAB donor 410 transmits the message to the IAB node 420 connected to the UE 430 via the backhaul link 460 through the IAB network 400 , and the IAB node 420 transmits the message to the UE 430 via the access link 470 .

[0065] Figure 55 is a diagram illustrating an IAB network 500 and its components. The IAB network 500 includes an IAB donor 510 and an IAB node 520. The IAB node and the IAB donor can provide a wireless access link to a UE 530.

[0066] The IAB donor 510 may be considered as the root node of the tree structure of the IAB network 500. The IAB donor node 510 may be connected to the core network 590 via a wired connection 591. The wired connection may include, for example, a wired optical fiber. The IAB donor node 510 may provide a connection to one or more IAB nodes 520a. The IAB nodes 520a may each be referred to as a child node of the IAB donor node 510. The IAB donor node 510 may also provide a connection to one or more UEs 530a, which may be referred to as child UEs of the IAB donor 510. The IAB donor 510 may be connected to its child IAB node 520a via a backhaul link 560, and may be connected to the child UE 530a via an access link 570. The IAB node 520a, which is a child node of the IAB node 510, may also have (all) IAB nodes 520b and / or (all) UE 530b as child nodes. For example, the IAB node 520b may be further connected to a sub-node and / or a sub-UE. Figure 5 IAB nodes 520b are illustrated providing access links to UEs 530c, respectively.

[0067] The IAB donor 510 may include a central unit (CU) and a distributed unit (DU). The central unit CU may provide control of the IAB nodes 520a, 520b in the IAB network 500. For example, the CU may be responsible for the configuration of the IAB network 500. The CU may perform RRC / PDCP layer functions. The DU may perform scheduling. For example, the DU may schedule resources for communication by the child IAB node 520a and / or the UE 530a of the IAB donor 510.

[0068] The IAB nodes 520a, 520b may include a mobile terminal (MT) and a DU. The MT of the IAB node 520a may operate as a scheduled node, similar to being scheduled by the DU of the parent node (e.g., IAB donor 510) to the UE 530a. The MT of the IAB node 520b may operate as a scheduled node of the parent IAB node 520a. The DU of the IAB node 520a may schedule the child IAB node 520b and the UE 530b of the IAB node 520a. Since the IAB node may provide a connection to an IAB node, which in turn provides a connection for another IAB node, the pattern of the parent IAB node including the DU of the scheduling child IAB node / child UE may continue.

[0069] Figure 6 An example of interaction between an IAB donor 610, an IAB node 620, and a child IAB node 630 is illustrated. The CU 612 of the IAB donor 610 can provide centralized management of resources available for IAB node communication. The CU 612 of the IAB donor 610 can allocate these resources semi-statically. Additionally or alternatively, the soft resources of the child node can be controlled in a distributed dynamic manner by the parent node of the child node (e.g., the DU 624 or 614 of the parent node). For example, the DU 624 of the IAB node 620 can allocate the soft resources of the child IAB node 630 through dynamic control signaling.

[0070] MTs 622 and 632 may have resources as downlink (DL) resources, uplink (UL) resources, or flexible (F) resources. DUs 614, 624, and 634 may have hard DL resources, hard UL resources, and / or hard F resources. DUs 614, 624, and 634 may have soft DL resources, soft UL resources, and / or soft flexible resources. In addition to hard or soft resource types, DUs 614, 624, and 634 may have resources as unavailable (NA) type resources.

[0071] The CU 612 of the IAB donor 610 may communicate with the DU 624 of the IAB node 620 and the DU 634 of the child IAB node 630 over the FL-AP interface 640. The F1-AP interface 640 may support exchanging information (e.g., TDD-UL-DL configuration) and delivering encapsulated RRC messages for MTs of child nodes of the recipient IAB node (e.g., delivering encapsulated RRC messages for the child IAB node 630 to the DU 624 of the IAB node 620). In some aspects, the CU 612 may configure a resource mode of the DU 624 of the IAB node 620 over the FI-AP interface 640.

[0072] The DU 624 of the IAB node 620 may communicate with the MT 632 of the child IAB node 630 over the Uu air interface 650. The Uu air interface 650 may support delivery of an RRC message received from the CU 612 of the IAB donor 610 to the MT 632 of the child IAB node 630, and may support the DU 624 of the IAB node 620 to dynamically schedule the MT 632 of the child IAB node 630. In some aspects, the IAB node 620 may dynamically control soft resources of the DU 634 of the child IAB node 630 over the Uu air interface 650.

[0073] Figure 7 is a communication diagram illustrating RACH optimized communication between a UE 702 , a base station 704 , and another base station 706 .

[0074] When UE 702 initially attempts to connect to a mobile network, the UE may perform a random access procedure 708 to establish communication with a node of the network. The random access procedure 708 may be referred to as a random access channel (RACH) procedure. For example, the UE may use the random access procedure 708 to request an RRC connection, reestablish an RRC connection, restore an RRC connection, etc. UE 702 may initiate a random access message exchange by sending a first random access message 703 (e.g., Msg 1) including a preamble to a base station 704. UE 702 may obtain random access parameters, for example, including preamble format parameters, time and frequency resources, parameters for determining a root sequence and / or cyclic shift of a random access preamble, etc. in system information 701 from the base station 704. The preamble in the first random access message 703 may be transmitted together with an identifier such as a random access RNTI (RA-RNTI). UE 702 may, for example, randomly select a random access preamble sequence from a preamble sequence set. If the UE 702 randomly selects the preamble sequence, the base station 704 can simultaneously receive another preamble from a different UE. In some examples, the preamble sequence can be assigned to the UE 702.

[0075] The base station 704 may respond to the first random access message 703 by sending a second random access message 705 (e.g., Msg 2) using the PDSCH and including a random access response (RAR). The RAR may include, for example, an identifier of the random access preamble sent by the UE 702, a time advance (TA), an uplink grant for the UE 702 to transmit data, a cell radio network temporary identifier (C-RNTI) or other identifier, and / or a backoff indicator. Upon receiving the second random access message 705 including the RAR, the UE 702 may, for example, use the PUSCH to transmit a third random access message 707 (e.g., Msg 3) to the base station 704, which may include an RRC connection request, an RRC connection reestablishment request, or an RRC connection recovery request, depending on the trigger for initiating the random access procedure 708. Then, the base station 704 can complete the random access procedure 708 by sending a fourth random access message 709 (e.g., Msg 4) to the UE 702 (e.g., using the PDCCH for scheduling and the PDSCH for messages). The fourth random access message 709 may include a random access response message, which includes timing advance information, contention resolution information, and / or RRC connection establishment information. The UE 702 may monitor the PDCCH, for example, using the C-RNTI. If the PDCCH is successfully decoded, the UE 702 may also decode the PDSCH. The UE 702 may send HARQ feedback for any data carried in the fourth random access message. If two UEs send the same preamble in their respective first random access messages 703, both UEs can receive the RAR, resulting in both UEs sending the third random access message 707. The base station 704 can resolve such conflicts by being able to decode the third random access message 702 from only one of the UEs and responding to the UE with the fourth random access message 709. Another UE that has not received the fourth random access message 709 may determine that the random access is not successful and may retry the random access. Therefore, the fourth message 709 may be referred to as a contention resolution message. The fourth random access message 709 may complete the random access procedure 708. Therefore, the UE 702 may then transmit uplink communications with the base station 704 and / or receive downlink communications with the base station 704 based on the RAR of the fourth random access message 709.

[0076] In some aspects, the random access parameters for the cell can be adjusted to improve the access probability or reduce the waiting time associated with the random access. The base station can configure the random access parameters for the random access process, or can adjust these random access parameters based on the changing conditions when the communication within the network changes. For example, these random access parameters can be configured or reconfigured to optimize the random access with the base station. The optimized random access configuration can achieve improved communication with the UE and network performance gain through reduced connection time, higher throughput or better cell coverage. The random access parameters may include the number and position of random access resources, such as time and frequency resources and / or preamble resources for random access. For example, the random access configuration of the base station may indicate the number of random access opportunities (RO) and / or the position of the RO in time and frequency. These random access parameters may include backoff parameters that can be used to avoid congestion. The backoff parameter may be a timer value, and the base station may resolve contention between UEs attempting to connect to the base station by instructing one or two UEs to back off after the timer value expires. These random access parameters may also include power-related parameters. These power-related parameters may include an initial transmission power, an initial target received power, and / or a power ramp step size for transmitting a random access message. The random access message may include an identifier, such as a preamble. To avoid conflicts between different base stations using the same identifier (e.g., between a macro cell and a small cell), a base station may be assigned, or may use, a subset of available identifiers. These random access parameters may include a subset of available identifiers for the base station.

[0077] The base station 704 may send a report 710 (such as RACH-reportReq-r9) to the UE 702. The UE 702 may receive the report 710 and may send a report 712 (e.g., a RACH report) to the base station 704. The report 712 from the UE may provide data about the random access procedure 708 performed between the UE 702 and the base station 704. For example, the report 712 may indicate the number of attempts made by the UE 702 before the random access procedure 708 was successfully performed and a connection with the base station 704 was established. The report 712 may indicate whether the UE 702 experienced contention with another UE while attempting to establish a connection with the base station 704.

[0078] At 714, the base station 704 may receive information about the random access configuration of the other base station 706 from the other base station 706, including values ​​of some or all random access parameters of the other base station 706. The base station 704 may also send information about its random access configuration to the other base station 706, including values ​​of some or all random access parameters of the base station 704. The base station 704 and the other base station 706 may exchange information about their random access configurations over an X2 interface.

[0079] As illustrated at 716, the base station 704 may optimize its random access parameters, e.g., adjust its random access parameters to improve the probability and latency of the UE accessing the network. The base station 704 may optimize its random access parameters based on information received in the report including the report 712 received from the UE 702. The base station 704 may additionally or alternatively optimize its random access parameters based on information about the random access configuration of another base station 706. For example, the base station 704 may change the subset of available identifiers for the random access preamble (e.g., may request a new subset from the control entity) based on determining that its current identifier overlaps with an identifier used by another base station 706.

[0080] Figure 8 8 is a communication diagram illustrating random access process communications in an IAB network. The IAB network may include an IAB donor 802 and IAB nodes 804, 806, and 808. The IAB network may include multiple nodes that are overlapping and / or relatively close together, and in some aspects may include mobile IAB nodes. Accordingly, manual and / or static network planning for avoiding interference, conflicts, etc. may be impractical or impossible.

[0081] In some aspects, the DU of the IAB node may determine its initial configuration / resources for random access. The IAB node may be preconfigured with a certain random access configuration and / or random access resources. Therefore, the DU may use the preconfigured random access configuration and / or random access resources for the initial random access configuration and / or random access resources. Such baseline random access configuration parameters or resources may be preconfigured by the CU, preconfigured by the manufacturer, or based on predefined parameters that are typically applied by the DU. An initial configuration may be provided for a mobile IAB node. As presented herein, the DU of the IAB node may obtain information about the IAB network it is joining, and may determine the initial random access configuration parameters or resources based on the information obtained. This may enable the IAB node to optimize the initial random access configuration or resources for the IAB network of which it will become a part.

[0082] For example, the IAB node 804 may obtain system information 810 from the IAB donor 802. The IAB node 804 may additionally or alternatively obtain system information 812 from another IAB node 806. The IAB node 806 may be a neighbor IAB node (e.g., may be within a set distance from the IAB node 804, or may be a parent node or child node of the IAB node 804). Specifically, the MT of the IAB node 804 may obtain system information 810 and / or 812. In some aspects, the system information may indicate a random access configuration of a corresponding IAB node (e.g., the IAB donor 802 or the IAB node 806). In some aspects, the system information may indicate a random access resource of a corresponding IAB node. In some aspects, the system information may indicate a resource configuration (e.g., a time division duplex configuration or a bandwidth fraction configuration) of a corresponding IAB node.

[0083] As illustrated at 814, the IAB node 804 can determine the initial random access configuration and / or initial resource assigned for the random access process. In some aspects, the IAB node 804 may be preconfigured with a certain random access configuration and / or random access resource, and the IAB node 804 may determine that the preconfigured random access configuration and / or random access resource will be the initial random access configuration and / or random access resource. In some aspects, the IAB node 804 may be preconfigured with multiple random access configurations and random access resources, and the IAB node 804 may determine which of the preconfigured random access configurations and / or random access resources is to be used as the initial random access configuration and / or random access resource. For example, the IAB node 804 may be preconfigured with a conventional random access configuration and random access resource and preconfigured with a mobile random access configuration and a mobile random access resource. The IAB node 804 may determine whether the IAB node 804 is mobile or stationary. If the IAB node 804 determines that it is mobile, it may determine the mobile random access configuration as the initial random access configuration and the mobile random access resources as the initial random access resources. If the IAB node 804 determines that it is not mobile, it may determine the regular random access configuration as the initial random access configuration and the regular random access resources as the initial random access resources. In some aspects, the IAB node 804 may determine its initial random access configuration and random access resources to optimize the random access process, as described above with respect to Figure 7 of 716 discussed.

[0084] In some aspects, the IAB node 804 may determine its initial random access configuration and / or its initial random access resources based on system information 810 received from the IAB donor 802. In some aspects, the IAB node 804 may determine its initial random access configuration and / or its initial random access resources based on system information 812 received from the IAB node 806. For example, the IAB node 804 may determine its initial random access configuration and / or its initial random access resources based on a random access configuration, random access resources, and / or resource configuration (e.g., a time division duplex configuration or a bandwidth fraction configuration) of the IAB donor 802 or the IAB node 806.

[0085] In some aspects, the IAB node 804 may receive a random access identifier (e.g., a random access message preamble) used by the IAB donor 802 and the IAB node 806 as part of random access configuration information included in the IAB donor 802 system information 810 and the IAB node 806 system information 812. The IAB node 804 may determine its random access identifier based on the received random access identifier. For example, the IAB node 804 may select a random access identifier that is different from the received random access identifiers of the IAB donor 802 and the IAB node 806; or may have a preconfigured random access identifier, may determine that the preconfigured random access identifier conflicts with one of the received random access identifiers, and may select a new random access identifier that is different from the received random access identifier.

[0086] In some aspects, the IAB node 804 may receive a subset of qualified random access identifiers as part of random access configuration information included in the IAB donor 802 system information 810 and / or the IAB node 806 system information 812. The random access identifier values ​​may be divided into a first value subset and a second value subset. For example, the first value subset may be used for a macro cell and the second value subset may be used for a small cell, or the first value subset may be used for a stationary cell and the second value subset may be used for a mobile cell. The IAB node 804 may determine a subset of its available random access identifiers based on the subset of qualified random access identifiers. In some aspects, the IAB node 804 may select a first or second random access identifier value subset based on the characteristics of the IAB node 804 (e.g., if the IAB node 804 is a small cell or a stationary cell, the first subset may be selected, and if the IAB node 804 is a macro cell or a mobile cell, the second subset may be selected). In some aspects, the IAB node 804 may determine that a preconfigured subset of random access identifier values ​​is within the received subset of random access identifier values, and if they are within the received subset of random access identifier values, may determine that the preconfigured subset of random access identifier values ​​is to be used; and if they are not within the received subset of random access identifier values, may select a new subset of random access identifier values.

[0087] In some aspects, the IAB node 804 may receive random access resources being used at the IAB donor 802 in the system information 810 received from the IAB donor 802. The IAB node 804 may determine that the random access resources for the IAB node 804 are different from the random access resources of the IAB donor 802 (eg, do not overlap in the time domain).

[0088] In some aspects, the IAB node 804 may receive the transmit power or receive power of the IAB donor 802 and the IAB node 806 as part of the random access configuration information contained in the IAB donor 802 system information 810 and / or the IAB node 806 system information 812. The IAB node 804 may determine that interference with signals from the IAB donor 802 or the IAB node 806 may be possible (e.g., based on the transmit or receive power and the location of the IAB donor 802 or the IAB node 806), and may determine its transmit power or receive power to avoid interference with signals from the IAB donor 802 and / or the IAB node 806.

[0089] Once the IAB node 804 determines the initial configuration and / or random access resources, the IAB node 804 may transmit its initial configuration 816 to the IAB donor 802. The DU of the IAB node 804 may transmit the initial configuration 816 to the CU of the IAB donor 802 over the F1-AP interface during the initial setup procedure for the DU to establish its connection with the CU.

[0090] In some aspects, the IAB donor 802 may send a configuration update message 820 to the IAB node 804. The IAB node 804 may receive the configuration update message 820 and may change some or all random access configurations of the IAB node 804 based on the configuration update message 820. In some aspects, the IAB donor 802 may send the configuration update message 820 during an initial setup of the FL-AP interface.

[0091] As illustrated at 830, after the IAB node 804 has determined its initial random access configuration and initial random access resources at 814, the IAB node 804 may determine to reconfigure its random access configuration and / or random access resources. In some aspects, the IAB node 804 may determine to reconfigure its random access configuration and / or random access resources to optimize the load on the IAB node 804 or optimize the resource utilization of the IAB node 804. In some aspects, the IAB node 804 may determine to reconfigure its random access configuration and / or random access resources based on preconfigured parameters. For example, the preconfigured parameters may indicate whether the IAB node 804 is mobile or stationary. The IAB node 804 may reconfigure its random access configuration based on determining that the IAB node 804 has changed its mobility state from mobile to stationary.

[0092] In some aspects, the IAB donor 802 may send a new random access configuration 832 to the IAB node 804, the IAB node 804 may receive the new random access configuration 832, and the IAB node 804 may determine at 830 to reconfigure its random access configuration and / or resources assigned to the random access process based on receiving the new random access configuration 832, and may reconfigure its random access configuration to the new random access configuration 832. In some aspects, the new random access configuration 832 may be a recommended or optional random access configuration, and the IAB node 804 may determine whether to use the new random access configuration 832, or how to use the new random access configuration 832. For example, the new random access configuration 832 may include a subset of random access identifier values, and the IAB node 804 may determine to reconfigure its random access identifier value to be within the subset of random access identifier values.

[0093] In some aspects, the IAB node 804 may determine at 830 to reconfigure its random access configuration and / or resources assigned for the random access procedure in response to receiving the new or updated system information. In some aspects, the IAB node 806 may transmit the updated system information 834 to the IAB node 804, the IAB node 804 may receive the new system information 834, and the IAB node may reconfigure its random access configuration based on the new system information 834.

[0094] In some aspects, the new IAB node 808 may send system information 836 to the IAB node 804. The new IAB node 808 may be a mobile IAB node. The IAB node 808 may not send system information before the IAB node 804 determines the initial random access configuration and the initial random access resource. For example, the IAB node 804 may have received system information from a neighboring cell, and the IAB node 808 may be too far away geographically or too far away in the IAB network tree to be considered as a neighboring cell. The IAB node 808 may send system information 836 to the IAB node 804 in response to determining that the IAB node 808 is within a set geographical range of the IAB node 804, determining that the IAB node 808 is a parent node or child node of the IAB node 804, or determining that the IAB node 808 and the IAB node 804 have a common parent node or child node. The IAB node 804 may determine to reconfigure its random access configuration based on receiving the new system information 836 from the IAB node 808.

[0095] In some aspects, the IAB node 804 may determine at 830 to reconfigure its random access configuration and / or resources assigned for a random access procedure based on evaluating the new system information 834 or 836 itself. In some aspects, the IAB node 804 may determine at 830 to reconfigure its random access configuration and / or resources assigned for a random access procedure based on transmitting the new system information 834 or 836 to the IAB donor 802 and receiving a new random access configuration 832 from the IAB donor 802 in response to the new system information 834 or 836.

[0096] Various aspects of the new or updated system information 834 or 836 that may be considered when the IAB node 804 determines at 830 to reconfigure its random access configuration and how to reconfigure its random access configuration are discussed above with respect to determining an initial random configuration of the IAB node 804 based on the system information 810 and / or 812. For example, the IAB node 804 may determine to reconfigure its random access identifier based on a received random access identifier, may determine to reconfigure its subset of available random access identifiers based on a received subset of eligible random access identifiers (e.g., to avoid overlapping random access identifiers), may determine to reconfigure its random access resources to be different from the received random access resources (e.g., not overlapping in the time domain), or may determine to reconfigure its transmit and / or receive power levels based on received transmit and / or receive power levels of neighbor IAB nodes and / or locations of neighbor IAB nodes (e.g., to reduce or avoid collisions with neighbor IAB nodes).

[0097] Once the IAB node 804 determines the reconfigured random access configuration, the IAB node 804 may transmit a configuration update message 842 to the IAB donor 802 , the configuration update message 842 indicating the reconfigured random access configuration of the IAB node 804 .

[0098] The IAB node 804 may receive new or updated acquired system information 844 from a neighboring cell. In some aspects, the acquired system information 844 may be from a neighboring cell in a different IAB network (hereinafter referred to as an "out-of-network neighboring cell"). In some aspects, the IAB node 804 may determine to reconfigure its random access configuration based on receiving the acquired system information 844 from the out-of-network neighboring cell, as illustrated at 830. In some aspects, the IAB node 804 may transmit the acquired system information 844 of the out-of-network neighboring cell to the IAB donor 802. Based on the acquired system information 844, the CU of the IAB donor 802 may send a new random access configuration 832 to the IAB node 804, and as illustrated at 830, the IAB node 804 may determine to reconfigure its random access configuration based on receiving the new random access configuration 832, as previously discussed.

[0099] Fig. 9900 is a flowchart of a wireless communication method. The method may be performed by an IAB node (e.g., IAB node 103; IAB node 804; IAB node 1450; equipment 1002 / 1002'; processing system 1114, which may include memory 376 and may be an IAB node 103, 804 or 1350 or a component of an IAB node 103, 804 or 1350 (such as TX processor 316, RX processor 370, and / or controller / processor 375)). The method may enable an IAB node to improve or optimize random access parameters based on other IAB nodes in the network. In some examples, the method may enable an IAB node to optimize or select an improved initial random access configuration and / or random access resources.

[0100] At 902, at a mobile terminal (MT) of a node, the node may obtain random access information for at least one of a donor node serving the node or a neighbor cell of the node. For example, 902 may be performed by an acquisition component 1012. In some aspects, the node may be an integrated access and backhaul node. In some aspects, the node may obtain random access information in system information from the donor node or the neighbor cell. In some aspects, the acquired random access information may include at least one of a random access configuration for a donor node or a neighbor cell, a random access resource for a donor node or a neighbor cell, a TDD resource configuration for a donor node or a neighbor cell, or a bandwidth portion configuration for a donor node or a neighbor cell.

[0101] In some aspects, at 904, the node may report the acquired random access information from the DU of the node to the CU. For example, 904 may be performed by a reporting component 1014. In some aspects, the node may report the acquired random access information to the CU in an initial report. In some aspects, the node may report the acquired random access information to the CU in an update report.

[0102] In some aspects, at 906, the node may receive a random access configuration from the CU, wherein the node determines the one or more random access parameters based on the random access configuration received from the CU. For example, 906 may be performed by a configuration receiving component 1008. In some aspects, the random access configuration from the CU may include a range of random access preamble identifiers. In some aspects, the random access information reported by the node to the CU may include information about neighbor cells belonging to different CUs.

[0103] Finally, at 908, the node may determine one or more random access parameters for use by the device in performing a random procedure with the node, wherein the one or more random access parameters are based on the acquired random access information. For example, 908 may be performed by parameter determination component 1006. In some aspects, the node may determine the one or more random access parameters using the acquired random access information. In some aspects, determining the one or more random access parameters may include selecting a first random access preamble identifier set that is different from a second random access preamble identifier set for the donor node or the neighbor cell. In some aspects, determining the one or more random access parameters may include selecting a first random access resource that does not overlap in time with a second random access resource for the donor node or the neighbor cell. In some aspects, determining the one or more random access parameters may include selecting a power control parameter for random access based on potential interference to the donor node or the neighbor cell. In some aspects, the one or more random access parameters determined by the node may include at least one of: a random access preamble identifier, a time and frequency resource, a power-related parameter, a number of retransmissions, or a backoff timer for contention resolution. In some aspects, the node may determine the one or more random access parameters based on at least one of: avoiding overlap with other random access parameters of the donor node or the neighbor cell, increasing random access probability, reducing random access wait time, reducing contention between the node and the donor node or the neighbor cell, or improving random access involving mobility.

[0104] Fig.101000 is a conceptual data flow diagram illustrating data flows between different devices / components in an example apparatus 1002. The apparatus may be a node, e.g., an IAB node. The apparatus includes a receiving component 1004 that receives random access information and a random access configuration from a donor node 1060, and that receives random access information from a node 1050 (e.g., a neighboring node). The apparatus includes an acquisition component 1012 that receives the random access information from the receiving component 1004, e.g., as described in conjunction with 902. The apparatus includes a reporting component 1014 that receives the random access information from the acquisition component 1012 and sends the random access information to a transmission component 1010 to report to a CU of the donor node 1060, e.g., as described in conjunction with 904. The apparatus includes a configuration receiving component 1008 that receives the random access configuration from the receiving component 1004 and sends the random access configuration to a parameter determining component 1006, e.g., as described in conjunction with 906. The apparatus includes a parameter determination component 1006 that determines random access parameters for the node, e.g., as described in conjunction with 908, and sends the determined parameters to a transmission component 1010 to send to a donor node 1060. Finally, the apparatus includes a transmission component 1010 that sends the determined parameters and random access information to the donor node 1060.

[0105] The equipment may include performing Fig.10 The additional components of each box of the algorithm in the preceding flowchart. Thus, Fig.10 Each block in the aforementioned flow chart of can be performed by a component and the equipment may include one or more of those components. These components can be one or more hardware components specially configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0106] Fig.11 1 is a diagram 1100 illustrating an example of a hardware implementation of an apparatus 1002' employing a processing system 1114. The processing system 1114 may be implemented with a bus architecture generally represented by a bus 1124. Depending on the specific application of the processing system 1114 and the overall design constraints, the bus 1124 may include any number of interconnecting buses and bridges. The bus 1124 links together various circuits, including one or more processors and / or hardware components (represented by the processor 1104, components 1004, 1006, 1008, 1010, 1012, 1014, and computer readable medium / memory 1106). The bus 1124 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 will not be described further.

[0107] The processing system 1114 may be coupled to the transceiver 1110. The transceiver 1110 is coupled to one or more antennas 1120. The transceiver 1110 provides a means for communicating with various other equipment over a transmission medium. The transceiver 1110 receives signals from the one or more antennas 1120, extracts information from the received signals, and provides the extracted information to the processing system 1114 (specifically, the receiving component 1004). In addition, the transceiver 1110 receives information from the processing system 1114 (specifically, the transmitting component 1010) and generates signals to be applied to the one or more antennas 1120 based on the received information. The processing system 1114 includes a processor 1104 coupled to a computer-readable medium / memory 1106. The processor 1104 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory 1106. The software, when executed by the processor 1104, causes the processing system 1114 to perform the various functions described above for any particular equipment. The computer-readable medium / memory 1106 may also be used to store data that is manipulated by the processor 1104 when executing software. The processing system 1114 further includes at least one of the components 1004, 1006, 1008, 1010, 1012, and 1014. These components may be software components that run in the processor 1104, software components that reside / stored in the computer-readable medium / memory 1106, one or more hardware components coupled to the processor 1104, or some combination thereof. The processing system 1114 may be a component of the base station 310 and may include the memory 376 and / or at least one of the following: the TX processor 316, the RX processor 370, and the controller / processor 375. Alternatively, the processing system 1114 may be the entire base station (e.g., see Figure 3 310).

[0108] In one configuration, an apparatus 1002 / 1002' for wireless communication includes: a device for acquiring random access information of at least one of a donor node serving the node or a neighboring cellular cell of the node at a mobile terminal (MT) of the node; and a device for determining one or more random access parameters for the device to use for performing a random procedure with the node, wherein the one or more random access parameters are based on the acquired random access information. The equipment may include a device for reporting the acquired random access information from the DU of the node to the CU. The equipment may include a device for receiving a random access configuration from the CU, and the device for determining may determine the one or more random access parameters based on the random access configuration received from the CU. The aforementioned device may be one or more of the aforementioned components of the equipment 1002 and / or the processing system 1114 of the equipment 1002' configured to perform the functions described by the aforementioned device. As described above, the processing system 1114 may include a TX processor 316, an RX processor 370, and a controller / processor 375. As such, in one configuration, the aforementioned means may be the TX processor 316, the RX processor 370, and the controller / processor 375 configured to perform the functions recited by the aforementioned means.

[0109] Fig.12 1200 is a flowchart of a wireless communication method. The method may be performed by a control node. In some aspects, the method may be performed by a CU (e.g., a CU of an IAB donor 180a; a CU of an IAB donor 802; a CU of an IAB donor 1060; equipment 1302 / 1302'; a processing system 1414, which may include a memory 376 and which may be the entire IAB donor 180a, 802 or 1060, the entire CU of an IAB donor 180a, 802 or 1060, or a component of the CU or IAB donor 180a, 802 or 1060, such as a TX processor 316, an RX processor 370, and / or a controller / processor 375) and / or a processor of the control node or CU. The method may enable a CU to improve or optimize random access parameters of an IAB node connected to the CU based on other IAB nodes adjacent to the IAB node. In some examples, these neighboring IAB nodes may be in the same network or may be in different networks.

[0110] At 1202, a CU may receive a report from a node served by the CU, the report including random access information of at least one of a donor node or a neighbor cell of the node obtained by the node for serving the node. For example, 1202 may be performed by a reporting component 1312. In some aspects, the node may include an integrated access and backhaul node. In some aspects, the report may include an initial report from the node. In some aspects, the report may include an update report from the node. In some aspects, the report from the node may include information about neighbor cells belonging to different CUs. In some aspects, the random access information may include a random access configuration for a donor node or a neighbor cell, a random access resource for a donor node or a neighbor cell, a time division duplex (TDD) resource configuration for a donor node or a neighbor cell, or a bandwidth portion configuration for a donor node or a neighbor cell.

[0111] At 1204, the CU may determine one or more random access parameters for the device to perform a random access process with at least one of the node, the donor node, and the neighbor cell, wherein the one or more random access parameters are determined based on the acquired random access information. For example, 1204 may be performed by a determination component 1314. In some aspects, the one or more random access parameters may include a range of random access preamble identifiers for the node. In some aspects, determining the one or more random access parameters may include selecting a first set of random access preamble identifiers that is different from a second set of random access preamble identifiers for the donor node or the neighbor cell. In some aspects, determining the one or more random access parameters may include selecting a first random access resource that does not overlap in time with a second random access resource for the donor node or the neighbor cell. In some aspects, determining the one or more random access parameters may include selecting a power control parameter for random access based on potential interference to the donor node or the neighbor cell. In some aspects, the one or more random access parameters determined by the CU may include at least one of: a random access preamble identifier, time and frequency resources, power-related parameters, a number of retransmissions, or a backoff timer for contention resolution. In some aspects, the CU may determine the one or more random access parameters based on at least one of: avoiding overlap with other random access parameters of the donor node or the neighbor cell, increasing random access probability, reducing random access waiting time, reducing contention between the node and the donor node or the neighbor cell, or improving random access involving mobility.

[0112] Finally, at 1206, the CU can send the one or more random access parameters to the node. For example, 1206 can be performed by the transmission component 1310.

[0113] Fig.13 1300 is a conceptual data flow diagram illustrating data flow between different devices / components in an example apparatus 1302. The apparatus may be a CU of an IAB donor. The apparatus includes a receiving component 1304 that receives a report including random access information from a node 1350. The apparatus includes a reporting component 1312 that receives the report from the receiving component 1304 and sends the random access information to a determining component 1314, e.g., as described in conjunction with 1202. The apparatus includes a determining component 1314 that receives the random access information from the reporting component 1312 and determines random access parameters for use by the device to perform a random access procedure with at least one of the node 1350, the donor node 1370, and the neighbor cell 1360, e.g., as described in conjunction with 1204. The apparatus includes a transmitting component 1310 that receives the random access parameters from the determining component 1314 and transmits the random access parameters to the node 1350, the donor node 1370, or the neighbor cell 1360.

[0114] The equipment may include performing Fig.12 The additional components of each box of the algorithm in the preceding flowchart. Thus, Fig.12 Each block in the aforementioned flow chart of can be performed by a component and the equipment may include one or more of those components. These components can be one or more hardware components specially configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0115] Fig.14 1400 is a diagram illustrating an example of a hardware implementation of an apparatus 1302' employing a processing system 1414. The processing system 1414 may be implemented with a bus architecture generally represented by a bus 1424. Depending on the specific application of the processing system 1424 and the overall design constraints, the bus 1414 may include any number of interconnecting buses and bridges. The bus 1424 links together various circuits including one or more processors and / or hardware components (represented by the processor 1404, components 1304, 1310, 1312, 1314, and computer readable medium / memory 1406). The bus 1424 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 will not be described further.

[0116] The processing system 1414 may be coupled to the transceiver 1410. The transceiver 1410 is coupled to one or more antennas 1420. The transceiver 1410 provides a means for communicating with various other equipment over a transmission medium. The transceiver 1410 receives signals from the one or more antennas 1420, extracts information from the received signals, and provides the extracted information to the processing system 1414 (specifically, the receiving component 1304). In addition, the transceiver 1410 receives information from the processing system 1414 (specifically, the transmitting component 1310) and generates signals to be applied to the one or more antennas 1420 based on the received information. The processing system 1414 includes a processor 1404 coupled to a computer-readable medium / memory 1406. The processor 1404 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory 1406. The software, when executed by the processor 1404, causes the processing system 1414 to perform the various functions described above for any particular device. The computer-readable medium / memory 1406 may also be used to store data manipulated by the processor 1404 when executing software. The processing system 1414 further includes at least one of the components 1304, 1310, 1312, and 1314. These components may be software components running in the processor 1404, software components resident / stored in the computer-readable medium / memory 1406, one or more hardware components coupled to the processor 1404, or some combination thereof. The processing system 1414 may be a component of the base station 310 and may include the memory 376 and / or at least one of the following: the TX processor 316, the RX processor 370, and the controller / processor 375. Alternatively, the processing system 1414 may be the entire base station (e.g., see Figure 3 310).

[0117] In one configuration, the equipment 1302 / 1302' for wireless communication includes a device for receiving a report from a node served by a CU, the report including random access information of at least one of a donor node or a neighboring cell of the node for serving the node obtained by the node. The equipment may include a device for determining one or more random access parameters for the device to use to perform a random procedure with the node, wherein the one or more random access parameters are determined based on the acquired random access information. The equipment may include a device for sending the one or more random access parameters to the node. The aforementioned device may be one or more of the aforementioned components of the equipment 1302 and / or the processing system 1414 of the equipment 1302' configured to perform the functions described by the aforementioned device. As described above, the processing system 1414 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Thus, in one configuration, the aforementioned device may be a TX processor 316, an RX processor 370, and a controller / processor 375 configured to perform the functions described by the aforementioned device.

[0118] It should be understood that the specific order or hierarchy of each box in the disclosed process / flowchart is an illustration of an example approach. It should be understood that the specific order or hierarchy of each box in these process / flowcharts can be rearranged based on design preferences. In addition, some boxes can be combined or omitted. The attached method claims present the elements of various boxes in an exemplary order and are not meant to be limited to the specific order or hierarchy presented.

[0119] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be easily understood by those skilled in the art, and the universal principles defined in this article can be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown in this article, but should be granted the full scope consistent with the claims in language, wherein the singular reference of the elements is not intended to represent "there is and only one", but "one or more", unless otherwise stated. The wording "exemplary" is used herein to mean "used as an example, instance or explanation". Any aspect described as "exemplary" herein does not have to be interpreted as being superior to or superior to other aspects. Unless otherwise stated, the term "some / certain" refers to one or more. Combinations such as "at least one of A, B or C", "one or more of A, B or C", "at least one of A, B and C", "one or more of A, B and C" and "A, B, C or any combination thereof" include any combination of A, B and / or C, and may include multiple A, multiple B or multiple C. Specifically, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members of A, B, or C. All structural and functional equivalents of the elements of the various aspects described throughout this disclosure that are currently or hereafter known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims. The terms "module," "mechanism," "element," "device," and the like may not be a substitute for the term "means." Thus, no claim element should be interpreted as a means-plus-function unless the element is explicitly stated using the phrase "means for..."

Claims

1. A method for wireless communication at a node, comprising: Obtaining random access information of a donor node serving the node and a neighbor cell of the node, wherein the random access information for the donor node is obtained from the donor node, and the random access information for the neighbor cell is obtained from the neighbor cell; and One or more random access parameters are determined for use by a device in performing a random access procedure with the node, wherein the one or more random access parameters are based on the acquired random access information.

2. The method of claim 1, further comprising: reporting the acquired random access information from the distributed unit DU of the node to the first central unit CU; as well as A random access configuration is received from the first CU, wherein the node determines the one or more random access parameters based on the random access configuration received from the first CU. 3 . The method of claim 2 , wherein the acquired random access information reported by the node to the first CU includes information about a neighbor cell belonging to a second CU different from the first CU.

4. The method according to claim 1 , wherein the acquired random access information comprises at least one of the following: a random access configuration for the donor node or the neighbor cell, random access resources for the donor node or the neighbor cell, Time Division Duplex (TDD) resource configuration for the donor node or the neighbor cell, or A bandwidth portion is configured for the donor node or the neighbor cell.

5. An apparatus for wireless communication at a node, comprising: Memory; as well as at least one processor coupled to the memory and configured to: Obtaining random access information of a donor node serving the node and a neighboring cell of the node, wherein the random access information for the donor node is obtained from the donor node, and the random access information for the neighboring cell is obtained from the neighboring cell; as well as One or more random access parameters are determined for use by a device in performing a random access procedure with the node, wherein the one or more random access parameters are based on the acquired random access information.

6. The apparatus of claim 5, wherein the node comprises an integrated access and backhaul node.

7. The apparatus of claim 5, wherein the processor uses the acquired random access information to determine the one or more random access parameters.

8. The apparatus of claim 5, wherein the processor is further configured to: reporting the acquired random access information from the distributed unit DU of the node to the first central unit CU; and A random access configuration is received from the first CU, wherein the processor determines the one or more random access parameters based on the random access configuration received from the first CU. 9 . The apparatus of claim 8 , wherein the processor reports the acquired random access information to the first CU in an initial report. 10 . The apparatus of claim 8 , wherein the processor reports the acquired random access information to the first CU in an update report.

11. The apparatus of claim 8, wherein the random access configuration from the first CU comprises a range of random access preamble identifiers. 12 . The apparatus of claim 8 , wherein the acquired random access information reported by the processor to the first CU includes information about a neighbor cell belonging to a second CU different from the first CU.

13. The apparatus of claim 5, wherein the acquired random access information comprises at least one of the following: a random access configuration for the donor node or the neighbor cell, random access resources for the donor node or the neighbor cell, Time Division Duplex (TDD) resource configuration for the donor node or the neighbor cell, or A bandwidth portion is configured for the donor node or the neighbor cell.

14. The apparatus of claim 5, wherein determining the one or more random access parameters comprises: A first set of random access preamble identifiers is selected that is different from a second set of random access preamble identifiers used for the donor node or the neighbor cell.

15. The apparatus of claim 5, wherein determining the one or more random access parameters comprises: A first random access resource is selected that does not temporally overlap with a second random access resource for the donor node or the neighbor cell.

16. The apparatus of claim 5, wherein determining the one or more random access parameters comprises: A power control parameter for random access is selected based on potential interference to the donor node or the neighbor cell.

17. The apparatus of claim 5, wherein the one or more random access parameters determined by the processor include at least one of: Random access preamble identifier, Time and frequency resources, Power related parameters, Number of retransmissions, or Backoff timer for contention resolution.

18. The apparatus of claim 17, wherein the processor determines the one or more random access parameters based on at least one of: Avoid overlapping with other random access parameters of the donor node or the neighbor cell, Increase the random access probability, Reduce random access waiting time, reducing contention between the node and the donor node or the neighbor cell, or Improvements to random access involving mobility.

19. The apparatus according to claim 5, wherein the random access information is obtained at a mobile terminal MT of the node.

20. An apparatus for wireless communication at a node, comprising: means for obtaining random access information of a donor node serving the node and a neighbor cell of the node, wherein the random access information for the donor node is obtained from the donor node, and the random access information for the neighbor cell is obtained from the neighbor cell; and Means for determining one or more random access parameters for a device to perform a random procedure with the node, wherein the one or more random access parameters are based on the obtained random access information.

21. The apparatus of claim 20, further comprising: means for reporting the acquired random access information from the distributed unit DU of said node to the first central unit CU; as well as means for receiving a random access configuration from the first CU, wherein the node determines the one or more random access parameters based on the random access configuration received from the first CU.

22. The apparatus of claim 21, wherein the acquired random access information reported by the reporting means to the first CU includes information about a neighbor cell belonging to a second CU different from the first CU.

23. The apparatus of claim 20, wherein the acquired random access information comprises at least one of: a random access configuration for the donor node or the neighbor cell, random access resources for the donor node or the neighbor cell, Time Division Duplex (TDD) resource configuration for the donor node or the neighbor cell, or A bandwidth portion is configured for the donor node or the neighbor cell.

24. A non-transitory computer-readable medium storing computer-executable code for wireless communication at a node, the code, when executed by a processor, causing the processor to: Obtain random access information of a donor node serving the node and neighboring cells of the node, wherein: The random access information for the donor node is obtained from the donor node, and the random access information for the neighbor cell is obtained from the neighbor cell; as well as One or more random access parameters are determined for use by a device in performing a random access procedure with the node, wherein the one or more random access parameters are based on the acquired random access information.

25. The computer-readable medium of claim 24, wherein the code further causes the processor to: reporting the acquired random access information from the distributed unit DU of the node to the first central unit CU; and A random access configuration is received from the first CU, wherein the processor determines the one or more random access parameters based on the random access configuration received from the first CU.

26. The computer-readable medium of claim 25, wherein the code causes the processor to report the acquired random access information to the first CU to include information about neighbor cells belonging to a second CU different from the first CU.

27. The computer-readable medium of claim 24, wherein the code causes the processor to obtain the random access information in system information from the donor node or the neighbor cell.

28. The computer-readable medium of claim 27, wherein the acquired random access information comprises at least one of: a random access configuration for the donor node or the neighbor cell, random access resources for the donor node or the neighbor cell, Time Division Duplex (TDD) resource configuration for the donor node or the neighbor cell, or A bandwidth portion is configured for the donor node or the neighbor cell.

29. A method for wireless communication at a control node, comprising: receiving a report from a node served by the control node, the report comprising random access information of a donor node serving the node and neighbor cells of the node acquired by the node; determining one or more random access parameters for use by a device in performing a random access procedure with at least one of the node, the donor node, or the neighbor cell, wherein the one or more random access parameters are determined based on the obtained random access information; and The one or more random access parameters are sent to the node, the donor node, or the neighbor cell.

30. The method of claim 29, wherein the control node is a first control node, and wherein the report from the node includes information about neighbor cells belonging to a second control node different from the first control node.

31. The method of claim 29, wherein the random access information comprises at least one of: a random access configuration for the donor node or the neighbor cell, random access resources for the donor node or the neighbor cell, Time Division Duplex (TDD) resource configuration for the donor node or the neighbor cell, or A bandwidth portion is configured for the donor node or the neighbor cell.

32. The method of claim 29, wherein the one or more random access parameters determined by the control node include at least one of: Random access preamble identifier, Time and frequency resources, Power related parameters, Number of retransmissions, or Backoff timer for contention resolution.

33. The method of claim 32, wherein the control node determines the one or more random access parameters based on at least one of: avoiding overlap with other random access parameters of the node, the donor node, or the neighboring cell, Increase the random access probability, Reduce random access waiting time, reducing contention between the node and the donor node or the neighbor cell, or Improvements to random access involving mobility.

34. An apparatus for wireless communication at a control node, comprising: Memory; as well as at least one processor coupled to the memory and configured to: receiving a report from a node served by the control node, the report comprising random access information of a donor node serving the node and neighbor cells of the node acquired by the node; determining one or more random access parameters for use by a device in performing a random access procedure with at least one of the node, the donor node, or the neighbor cell, wherein the one or more random access parameters are determined based on the obtained random access information; and The one or more random access parameters are sent to the node, the donor node, or the neighbor cell.

35. The apparatus of claim 34, wherein the node comprises an integrated access and backhaul node.

36. The apparatus of claim 34, wherein the report comprises an initial report from the node.

37. The apparatus of claim 34, wherein the report comprises an update report from the node.

38. The apparatus of claim 34, wherein the one or more random access parameters comprise a range of random access preamble identifiers for the node, the donor node, or the neighbor cell.

39. The apparatus of claim 34, wherein the control node is a first control node, and wherein the report from the node includes information about neighbor cells belonging to a second control node different from the first control node.

40. The apparatus of claim 34, wherein the random access information comprises at least one of: a random access configuration for the donor node or the neighbor cell, random access resources for the donor node or the neighbor cell, Time Division Duplex (TDD) resource configuration for the donor node or the neighbor cell, or A bandwidth portion is configured for the donor node or the neighbor cell.

41. The apparatus of claim 34, wherein the processor determining the one or more random access parameters comprises: A first set of random access preamble identifiers for the node is selected that is different from a second set of random access preamble identifiers for the donor node or the neighbor cell.

42. The apparatus of claim 34, wherein the processor determining the one or more random access parameters comprises: A first random access resource for the node is selected that does not temporally overlap with a second random access resource for the donor node or the neighbor cell.

43. The apparatus of claim 34, wherein the processor determining the one or more random access parameters comprises: A power control parameter for random access is selected based on potential interference between the node and the donor node or the neighbor cell.

44. The apparatus of claim 34, wherein the one or more random access parameters determined by the processor include at least one of: Random access preamble identifier, Time and frequency resources, Power related parameters, Number of retransmissions, or Backoff timer for contention resolution.

45. The apparatus of claim 44, wherein the processor determines the one or more random access parameters based on at least one of: avoiding overlap with other random access parameters of the node, the donor node, or the neighboring cell, Increase the random access probability, Reduce random access waiting time, reducing contention between the node and the donor node or the neighbor cell, or Improvements to random access involving mobility.

46. ​​The apparatus of claim 34, wherein the control node comprises a Central Unit (CU) of an IAB donor.

47. An apparatus for wireless communication at a control node, comprising: means for receiving a report from a node served by the control node, the report comprising random access information of a donor node serving the node and neighbor cells of the node acquired by the node; means for determining one or more random access parameters for use by a device in performing a random access procedure with at least one of the node, the donor node, or the neighbor cell, wherein the one or more random access parameters are determined based on the obtained random access information; as well as means for sending the one or more random access parameters to the node, the donor node, or the neighbor cell.

48. The apparatus of claim 47, wherein the control node is a first control node, and wherein the report from the node includes information about neighbor cells belonging to a second control node different from the first control node.

49. The apparatus of claim 47, wherein the random access information comprises at least one of: a random access configuration for the donor node or the neighbor cell, random access resources for the donor node or the neighbor cell, Time Division Duplex (TDD) resource configuration for the donor node or the neighbor cell, or A bandwidth portion is configured for the donor node or the neighbor cell.

50. The apparatus of claim 47, wherein the one or more random access parameters determined by the means for determining include at least one of: Random access preamble identifier, Time and frequency resources, Power related parameters, Number of retransmissions, or Backoff timer for contention resolution.

51. The apparatus of claim 50, wherein the means for determining determines the one or more random access parameters based on at least one of: avoiding overlap with other random access parameters of the node, the donor node, or the neighboring cell, Increase the random access probability, Reduce random access waiting time, reducing contention between the node and the donor node or the neighbor cell, or Improvements to random access involving mobility.

52. A non-transitory computer-readable medium storing computer-executable code for wireless communication at a control node, the code, when executed by a processor, causing the processor to: receiving a report from a node served by the control node, the report comprising random access information of a donor node serving the node and neighbor cells of the node acquired by the node; determining one or more random access parameters for use by a device in performing a random access procedure with at least one of the node, the donor node, or the neighbor cell, wherein the one or more random access parameters are determined based on the obtained random access information; and The one or more random access parameters are sent to the node, the donor node, or the neighbor cell.

53. The computer-readable medium of claim 52, wherein the control node is a first control node, and wherein the report from the node includes information about neighbor cells belonging to a second control node different from the first control node.

54. The computer-readable medium of claim 52, wherein the random access information comprises at least one of: a random access configuration for the donor node or the neighbor cell, random access resources for the donor node or the neighbor cell, Time Division Duplex (TDD) resource configuration for the donor node or the neighbor cell, or A bandwidth portion is configured for the donor node or the neighbor cell.

55. The computer-readable medium of claim 52, wherein the one or more random access parameters determined by the processor include at least one of: Random access preamble identifier, Time and frequency resources, Power related parameters, Number of retransmissions, or Backoff timer for contention resolution.

56. The computer-readable medium of claim 55, wherein the code causes the processor to determine the one or more random access parameters based on at least one of: avoiding overlap with other random access parameters of the node, the donor node, or the neighboring cell, Increase the random access probability, Reduce random access waiting time, reducing contention between the node and the donor node or the neighbor cell, or Improvements to random access involving mobility.

Images