Rewriting BAP header in integrated access backhaul

Abstract

A method and apparatus for rewriting a BAP header in an IAB network. The apparatus receives a routing configuration from a second base station indicating a mapping between a first routing ID and a second routing ID. The apparatus receives a packet having a packet header indicating the first routing ID. The apparatus determines the second routing ID based on the routing configuration for mapping the first routing ID in the packet header to the second routing ID. The apparatus modifies the packet header to replace the first routing ID with the second routing ID based on the determination of the second routing ID. The apparatus sends the packet based on the second routing ID.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of and priority to U.S. Provisional Application Serial No. 63 / 104,353, filed on October 22, 2020, and entitled “Rewriting BAP Headers in IAB”; and U.S. Patent Application No. 17 / 451,770, filed on October 21, 2021, and entitled “Rewriting BAP Headers in IAB”, the entire contents of which are expressly incorporated herein by reference. Technical Field

[0003] The present disclosure generally relates to communication systems, and more particularly, to configurations for rewriting a Backhaul Adaptation Protocol (BAP) header in an Integrated Access Backhaul (IAB) network. Background Art

[0004] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies capable of supporting communications 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.

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution released 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. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable low latency communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. There is a need to further improve 5G NR technology. These improvements may also be applicable to other multiple access technologies and telecommunication standards using these technologies. Summary of the invention

[0006] A brief summary of one or more aspects is given below to provide a basic understanding of such aspects. This summary is not a general summary of all expected aspects and is not intended to identify key or important elements of all aspects or describe the scope of any or all aspects. Its purpose is only to serve as a prelude to the more detailed description given later, giving some concepts of one or more aspects in a simplified form.

[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a device at a first base station. The apparatus may be a processor and / or a modem at the first base station or the first base station itself. The apparatus receives a routing configuration from a second base station indicating a mapping between a first routing identifier (ID) and a second routing ID. The apparatus receives a packet having a packet header indicating a first routing ID. The apparatus determines a second routing ID based on a routing configuration that maps a first routing ID in a packet header to a second routing ID. The apparatus modifies a packet header based on a determination of the second routing ID to replace the first routing ID with the second routing ID. The apparatus sends a packet based on the second routing ID.

[0008] In one aspect of the present disclosure, a method, a computer readable medium, and an apparatus are provided. The apparatus may be a device at a second base station. The apparatus may be a processor and / or a modem at the second base station or the second base station itself. The apparatus configures a first base station to modify a packet header of a packet, wherein the packet header indicates a first routing identifier (ID). The apparatus sends a routing configuration to the first base station indicating a mapping between a first routing ID and a second routing ID.

[0009] To achieve the foregoing and related ends, 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 one or more aspects. However, these features are merely indicative of some of the various ways in which the principles of the various aspects may be employed, and this description is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0011] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0012] Figure 2B is a diagram illustrating an example of DL channels within a subframe according to various aspects of the present disclosure.

[0013] Figure 2Cis a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0014] Figure 2D is a diagram illustrating an example of UL channels within a subframe according to various aspects of the present disclosure.

[0015] Figure 3 is a schematic diagram showing an example of a base station and a UE in an access network.

[0016] Figure 4 is a first diagram showing an IAB network.

[0017] Figure 5 is a second diagram illustrating an IAB network.

[0018] Figure 6 is a diagram illustrating a Radio Link Control (RLC) channel in an IAB network.

[0019] Figure 7 is a diagram showing quality of service (QoS) mapping information within an IAB network.

[0020] Figure 8 is a diagram showing an IP / BAP configuration.

[0021] Fig. 9 Example topology redundancy for an IAB donor is shown.

[0022] Fig.10 is a call flow diagram of signaling between a first base station and a second base station.

[0023] Fig.11 is a flow chart of a method of wireless communication.

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

[0025] Fig.13 is a diagram illustrating an example of a hardware implementation for an example apparatus.

[0026] Fig.14 is a flow chart of a method of wireless communication.

[0027] Fig.15 is a diagram illustrating an example of a hardware implementation for an example apparatus. DETAILED DESCRIPTION

[0028] 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 configuration in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in the form of block diagrams in order to avoid obscuring such concepts.

[0029] 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 detailed description below 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.

[0030] For example, an element, or any part of an element, or any combination of elements, can 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, gated logic, discrete hardware circuits, and other suitable hardware configured to perform various functions described throughout the present disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, 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, executable files, execution threads, processes, functions, etc.

[0031] Accordingly, in one or more example embodiments, the described functions may be implemented in hardware, software, or any combination thereof. If implemented in software, the 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. By way of 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 the aforementioned computer-readable media types, or any other medium that may be used to store computer executable code that can be accessed by a computer in the form of instructions or data structures.

[0032] Although various aspects and implementations are described in this application by the description of some examples, it will be understood by those skilled in the art that additional implementations and use cases may be generated in many different arrangements and scenarios. The innovation described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, implementation and / or use can be generated via integrated chip implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, equipment enabling artificial intelligence (AI), etc.). Although some examples may or may not be specifically for use cases or applications, there may be a variety of applicable scopes for the described innovations. Implementations may have a range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more aspects of the described innovations. In some actual settings, the equipment incorporating the described aspects and features may also include additional components and features for the implementation and implementation of the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily include several components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The innovations described herein are intended to be implemented in a variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc., having different sizes, shapes, and configurations.

[0033] Figure 11 is a diagram showing 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.

[0034] 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 be connected to 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 be connected to the core network 190 via a second backhaul link 184. Among other functions, the base station 102 can perform one or more of the following functions: transfer of user data, wireless 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), user and device tracking, RAN information management (RIM), paging, positioning, and transmission of warning 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 first backhaul link 132, the second backhaul link 184, and the third backhaul link 134 may be wired or wireless.

[0035] The base station 102 can communicate wirelessly with the UE 104. Each of the base stations 102 can provide communication coverage for a respective geographic coverage area 110. There can be overlapping geographic coverage areas 110. For example, a small cell 102' can have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network including small cells and macro cells can be referred to as a heterogeneous network. A heterogeneous network can also include a home evolved Node B (eNB) (HeNB), which can provide services for a restricted group called a closed subscriber group (CSG). The communication link 120 between the base station 102 and the UE 104 can 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 can use multiple input multiple output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link can be through one or more carriers. Base station 102 / UE 104 may use spectrum of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier allocated in carrier aggregation for a total of up to Yx MHz (x component carriers) for transmission in each direction. The carriers may be adjacent to each other or may not be adjacent. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​than for 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).

[0036] 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 various wireless D2D communication systems, such as, for example, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE 802.11) standard, LTE, or NR.

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

[0038] The small cell 102' may operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, the small cell 102' may adopt NR and use the same unlicensed spectrum (e.g., 5 GHz, etc.) as used by the Wi-Fi AP 150. The small cell 102' adopting NR in the unlicensed spectrum may improve the coverage of the access network and / or increase the capacity of the access network.

[0039] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified with the frequency range names FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the "sub-6 GHz" band in various documents and articles. Similar naming issues sometimes arise with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz-300 GHz) which is identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0040] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as the frequency range name FR3 (7.125GHz–24.25GHz). The frequency bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and thus can effectively extend the characteristics of FR1 and / or FR2 to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to above 52.6GHz. For example, three higher operating bands have been identified as the frequency range names FR4a or FR4-1 (52.6GHz–71GHz), FR4 (52.6GHz–114.25GHz), and FR5 (114.25GHz–300GHz). Each of these higher frequency bands falls within the EHF band.

[0041] In view of the above, unless otherwise specifically stated, it should be understood that if the term "sub-6 GHz" or the like is used herein, it can be broadly referred to as a frequency that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, it can be broadly referred to as a frequency that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or can be within the EHF band.

[0042] The base station 102, whether a small cell 102' or a large cell (e.g., a macro base station), may include and / or be referred to as an eNB, a gNodeB (gNB), or another type of base station. Some base stations, such as gNB 180, may operate in traditional sub-6 GHz spectrum, in millimeter wave frequencies, and / or near millimeter wave frequencies to communicate with UE 104. When the gNB 180 operates in millimeter wave or near millimeter wave frequencies, the gNB 180 may be referred to as a millimeter wave base station. The millimeter wave base station 180 may utilize beamforming 182 with the UE 104 to compensate for the extremely high path loss and short distance. 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.

[0043] Base station 180 may send beamformed signals to the UE 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 send 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 for base station 180 may or may not be the same. The transmit direction and receive direction for UE 104 may or may not be the same.

[0044] 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 communicate 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. Generally speaking, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides IP address allocation and other functions for the UE. 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 setup 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 allocate MBMS services 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 charging information related to eMBMS.

[0045] The core network 190 may include an access and mobility management function unit (AMF) 192, other AMFs 193, a session management function unit (SMF) 194, and a user plane function unit (UPF) 195. The AMF 192 may communicate with a unified data management unit (UDM) 196. The AMF 192 is a control node for processing signaling between the UE 104 and the core network 190. Typically, the AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are transmitted through the UPF 195. The UPF 195 provides IP address allocation and other functions to the UE. The UPF 195 is connected to an IP service 197. The IP service 197 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a packet switching (PS) stream (PSS) service, and / or other IP services.

[0046] A base station may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver, a wireless base station, a wireless transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), or some other appropriate term. Base station 102 provides an access point to EPC 160 or core network 190 for 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 computer, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, or any other similarly functional device. Some of UE 104 may be referred to as IoT devices (e.g., a parking meter, a gas pump, a toaster, a heart monitor, etc.). UE 104 may also be referred to by those skilled in the art as a station, mobile station, user station, mobile unit, user unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile user station, access terminal, mobile terminal, wireless terminal, remote terminal, handheld device, user agent, mobile client, client or some other appropriate term. In some scenarios, the term UE may also be applied to one or more companion devices, such as in a device constellation arrangement. One or more of these devices may access a network together and / or individually.

[0047] Refer again Figure 1 , in some aspects, the first base station 180 may be configured to modify a mapping configuration between BAP routing IDs. For example, the first base station 180 may include a modification component 198 configured to modify a mapping configuration between BAP routing IDs. The first base station 180 may receive a routing configuration indicating a mapping between a first routing ID and a second routing ID from a second base station 180. The first base station 180 may receive a packet 180 having a packet header indicating a first routing ID. The first base station 180 may determine the second routing ID based on the routing configuration for mapping the first routing ID in the packet header to the second routing ID. The first base station 180 may modify the packet header based on the determination of the second routing ID to replace the first routing ID with the second routing ID. The first base station may send a packet based on the second routing ID.

[0048] Refer again Figure 1In some aspects, the second base station 180 may be configured to configure the base station to modify a mapping configuration between BAP routing IDs. For example, the second base station 180 may include a modification component 199 configured to configure the base station to modify a mapping configuration between BAP routing IDs. The second base station 180 may configure the first base station 180 to modify a packet header of a packet, wherein the packet header indicates the first routing ID. The second base station 180 may send a routing configuration indicating a mapping between the first routing ID and the second routing ID to the first base station 180.

[0049] Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0050] Figures 2A-2D Included are diagrams of example frame structures and resources that may be utilized in communications between base stations 102, UEs 104, and / or secondary UEs (or sidelink UEs) 110 as described in the present disclosure. Figure 2A FIG200 is a diagram showing an example of a first subframe within a 5G / NR frame structure. Figure 2B FIG230 is a diagram showing an example of DL channels within a 5G / NR subframe. Figure 2C Figure 250 shows an example of a second subframe within a 5G / NR frame structure. Figure 2D FIG280 is a diagram showing an example of an UL channel within a 5G / NR subframe. The 5G / NR frame structure can be frequency division duplex (FDD) (wherein, for a particular set of subcarriers (carrier system bandwidth), the subframes within the subcarrier set are dedicated to either DL or UL), or can be time division duplex (TDD) (wherein, for a particular set of subcarriers (carrier system bandwidth), the subframes within the subcarrier set are dedicated to both DL and UL). Figure 2A , 2C In the example provided, it is assumed that the 5G / NR frame structure is TDD, subframe 4 is configured with slot format 28 (mostly DL), where D is DL, U is UL, and F is flexibly used between DL / UL, and subframe 3 is configured with slot format 1 (where all are UL). Although subframes 3 and 4 are shown using slot formats 1 and 28, respectively, any particular subframe can 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 mix of DL, UL and flexible symbols. The UE is configured with a slot format (dynamically through DL control information (DCI) or semi-statically / statically through radio resource control (RRC) signaling) through a received slot format indicator (SFI). Note that the following description also applies to the 5G / NR frame structure as TDD.

[0051] Figures 2A-2D The frame structure is shown, and various aspects of the present disclosure may be applicable to other wireless communication technologies, which may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 subframes (1ms) of equal size. Each subframe may include one or more time slots. A subframe may also include a microslot, which may include 7, 4, or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For a normal CP, each time slot may include 14 symbols, and for an extended CP, each time slot may include 12 symbols. The symbol on the DL may be a CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbol. The symbol on the UL may be a CP-OFDM symbol (for high throughput scenarios) or a discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbol (also referred to as a single carrier frequency division multiple access (SC-FDMA) symbol) (for power-limited scenarios; limited to single stream transmission). The number of slots within a subframe may be based on the CP and the numerology. The numerology defines the subcarrier spacing (SCS) and, in effect, the symbol length / duration (which may be equal to 1 / SCS).

[0052] μ <![CDATA[SCSΔf=2 μ ·15[kHz]]]> Cyclic prefix 0 15 ordinary 1 30 ordinary 2 60 Normal, Extended 3 120 ordinary 4 240 ordinary

[0053] For normal CP (14 symbols / slot), different digital schemes μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, digital scheme 2 allows 4 slots per subframe. Accordingly, for normal CP and digital scheme μ, there are 14 symbols / slot and 2 μ timeslots / subframe. The subcarrier spacing can be equal to 2 μ *15kHz, where μ is digital scheme 0 to 4. Thus, digital scheme μ=0 has a subcarrier spacing of 15kHz, and digital scheme μ=4 has a subcarrier spacing of 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figures 2A-2D Examples are provided for a normal CP (with 14 symbols per slot) and a digital scheme μ=2 (with 4 slots per subframe). The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency-division multiplexed (see Figure 2B ). Each BWP can have a specific number scheme and CP (normal or extended).

[0054] The resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) (also called a physical RB (PRB)), which extends 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0055] like Figure 2A As shown in , some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) for channel estimation at the UE (indicated as R for a specific configuration, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS). The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0056] Figure 2B Examples of various DL channels within a subframe of a frame are shown. A physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within a BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during a PDCCH monitoring opportunity on a CORESET, wherein the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at larger and / or lower frequencies across the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identity. A 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 can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The physical broadcast channel (PBCH), which carries the master information block (MIB), can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also called an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information that is not sent via the PBCH (e.g., system information block (SIB)), and paging messages.

[0057] like Figure 2CAs shown in , some of the REs carry DM-RS for channel estimation at the base station (indicated as R for one specific configuration, but other DM-RS configurations are possible). The UE may send DM-RS for a physical uplink control channel (PUCCH) and DM-RS for a physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first one or two symbols of the PUSCH. The PUCCH DM-RS may be sent in different configurations depending on whether a short PUCCH or a long PUCCH is sent and on the specific PUCCH format used. Although not shown, the UE may send a sounding reference signal (SRS). The SRS may be sent in the last symbol of the subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the combs in the comb. The SRS may be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0058] Figure 2D Examples of various UL channels within a subframe of a frame are shown. The PUCCH may be positioned as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may additionally be used to carry buffer status reports (BSRs), power headroom reports (PHRs), and / or UCI.

[0059] Figure 33 is a block diagram of a base station 310 in an access network communicating with a UE 350. 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 functions. 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 medium access control (MAC) layer. The controller / processor 375 provides: RRC layer functions 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 for UE measurement reporting; PDCP layer functions associated with header compression / decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with transmission 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 functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), and MAC Demultiplexing of SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling and logical channel prioritization.

[0060] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functions associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on the transmission channel, forward error correction (FEC) encoding / decoding of the transmission channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 processes 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-order quadrature amplitude modulation (M-QAM)). Subsequently, the coded and modulated symbols may be divided into parallel streams. Subsequently, each stream may be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time domain and / or frequency domain, and then combined using an inverse fast Fourier transform (IFFT) to generate 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. Channel estimates may be derived from reference signals and / or channel condition feedback sent by the UE 350. Each spatial stream is then provided to a different antenna 320 via a separate transmitter 318X. Each transmitter 318TX may modulate a radio frequency (RF) carrier with a respective spatial stream for transmission.

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

[0062] 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 and logical channels, packet reassembly, decryption, 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 an ACK and / or NACK protocol to support HARQ operations.

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

[0064] Channel estimates derived by the channel estimator 358 from a reference signal or feedback sent by the base station 310 may be used by the TX processor 368 to select an appropriate coding and modulation scheme, 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 respective spatial stream for transmission.

[0065] 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.

[0066] 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 and logical channels, packet reassembly, decryption, 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.

[0067] 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 All aspects related to 198 or 199.

[0068] Figure 4 4 is a first diagram 400 showing an IAB network. The IAB network provides access network functions between access nodes (ANs) 404, 406A, 406B, 408A, 408B and AN / UEs 410A, 410B, 410C, 410D, 410E, and 410F, and backhaul network functions between ANs. The AN includes an IAB donor 404 (which has a wired connection to a core network 402) and IAB nodes 406A and 406B (which operate wirelessly and relay services to / from the IAB donor through one or more AN hops 408A and 408B). The IAB AN shares resources between access and backhaul. That is, resources used for access communications between the AN and the AN / UE are also used for backhaul communications between the ANs.

[0069] Figure 55 is a second diagram illustrating an IAB network. In the IAB network, there are two types of base stations: an IAB donor (e.g., an IAB donor 502) and an IAB node (e.g., an IAB node 504). The IAB donor is an enhanced gNB having a function for controlling the IAB network. The IAB donor includes a central unit (CU) (e.g., CU 502A) that controls the entire IAB network through configuration. The CU maintains RRC and packet data convergence protocol (PDCP) layer functions. The IAB donor also includes a distributed unit (DU) (e.g., DU 502B) for scheduling child nodes (e.g., UE 506A, 506B, 506C, 506D and / or AN 508A, 508B) of the IAB donor. The DU maintains radio link control (RLC), medium access control (MAC), and physical (PHY) layer functions. The IAB node 504 is an L2 relay node that includes a mobile terminal (MT) and DU functions. MT is scheduled by its parent IAB node or IAB donor (similar to UE). DU schedules child nodes (UE and / or AN) of the IAB node.

[0070] Figure 6 600 is a diagram illustrating RLC channels in an IAB network. As discussed above, the IAB network provides both access network functions and backhaul network functions. According to the access network functions, the IAB AN can communicate with other UEs and / or MTs of other IABANs via access RLC channels. According to the backhaul network functions, the IAB AN can route services to other ANs via backhaul RLC channels. Access RLC channels include UE to DU / DU to UE (which carries PDCP for RRC or data radio bearer (DRB)) and MT to DU / DU to MT (which carries PDCP for RRC (or DRB)). Backhaul RLC channels include MT to DU / DU to MT, which carries Backhaul Adaptation Protocol (BAP) messages for backhaul access services. Different possible mappings are allowed between UE / MT DRBs and backhaul RLC channels, such as shown with 1:1 UE DRBs to backhaul RLC channels (i.e., each UE DRB is mapped to one backhaul RLC channel), 3:1 UE DRBs to backhaul RLC channels (i.e., three UE DRBs are mapped to one backhaul RLC channel), and 1:1 UE DRBs to backhaul RLC channels and 2:1 UE DRBs to backhaul RLC channels (i.e., one UE DRB is mapped to a first backhaul RLC channel and two UE DRBs are mapped to a second backhaul RLC channel). The 1:1 mapping allows certain UE DRBs to take precedence over other UE DRBs, while for 2:1 and 3:1 mappings, UE DRBs in the same backhaul RLC channel may not take precedence over each other.

[0071] Figure 7700 is a diagram illustrating QoS mapping information within an IAB network. The QoS mapping information includes a differentiated services code point (DSCP) 702 and an Internet Protocol (IP) v6 (IPv6) flow label. Differentiated services are intended to provide a framework and building blocks to enable scalable service differentiation to be deployed on the Internet. In a packet forwarding path, differentiated services (DS) are implemented by mapping the DSCP contained in a field in the IP packet header to a specific forwarding treatment or per-hop behavior (PHB) at each AN along its path. Six bits of the DS field are used as the DSCP to select the PHB that the packet experiences at each node. A two-bit CU field is currently reserved. The DSCP field is defined as an unstructured field to facilitate the definition of future per-hop behaviors. With some exceptions, the mapping of DSCP to PHB should be configurable. DS-compliant nodes should support the logical equivalent of a configurable mapping table from DSCP to PHB.

[0072] The IPv6 flow label field (referred to herein as the IP flow label) includes a 20-bit flow label field in the IPv6 header used by the AN to mark packets of the flow. From the perspective of the network layer, a flow is a sequence of packets sent from a specific source to a specific unicast, anycast, or multicast destination that the AN expects to mark as a flow. The typical definition of a flow for this purpose is any set of packets carrying the same 5-tuple of {destination address, source address, protocol, destination port, source port}. There are situations where the complete 5-tuple for all packets is not easily available to the forwarding AN, especially for segmented packets. In such a case, the flow can be defined by fewer IPv6 header fields, typically using only 2-tuples {destination address, source address}. The use of a triple of flow label, source address, and destination address fields enables efficient IPv6 flow classification, in which only fixed-position IPv6 main header fields are used. Packets can be processed in a flow-specific manner. In order to achieve classification based on flow labels, the source node can assign each unrelated transport connection and application data flow to a new flow.

[0073] like Figure 7As shown, a UE 708 may be dual connected to a master node (MN) eNB 704 and a secondary gNB (IAB donor) 708 for managing an IAB. For each requested E-UTRAN radio access bearer (E-RAB) configured as a MN-terminated split bearer / secondary cell group (SCG) bearer, if a QoS mapping information information element (IE) is included in a general packet radio service (GPRS) tunneling protocol (GTP) tunnel endpoint IE in a secondary gNB (SgNB) additional / modification request confirmation message, a master eNB (MeNB) 704 (also referred to as a MN-eNB) may (if supported) use the IE to set the DSCP and / or flow label fields for downlink IP packets sent from the MeNB 704 to a secondary node (SN) enhanced gNB 706 (SN en-gNB) (serving the IAB) via a GTP tunnel indicated by the GTP tunnel endpoint IE. The SN donor 706 configures a mapping of packets received from the MN-eNB 704 to routes transmitted via the IAB backhaul based on the IP header fields.

[0074] For each requested DRB, if the QoS Mapping Information IE is included in the DL UP Parameters IE in the Bearer Association Setup / Modify Request message, the gNB CU for User Plane (UP) (gNB-CU-UP) shall use this IE to set the DSCP and / or Flow Label fields in the downlink IP packets sent over the GTP tunnel indicated by the UP Transport Layer Information IE. The downlink mapping to BAP routing and egress backhaul RLC channels shall be configured at the IAB Donor DU based on the IP header fields.

[0075] The UE may be connected to the IAB network. The IAB donor may establish a DRB for the UE. The DRB flows between the IAB donor CU and the UE. In some aspects, the IAB donor CU may configure a downlink mapping at the donor DU, as described above. In some aspects, the IAB donor CU may configure an IP header field with a DSCP / IPv6 flow label and may send packets to the donor DU, as described above. In some aspects, the IAB donor CU may include a CU-CP 710 and one or more CU-Ups 712. In such aspects, the DRB flows between the CU-UP and the UE, as previously described, for example, in paragraph

[0067] . The CU-CP may perform bearer establishment for each DRB at the CU-UP. The CU-CP may configure QoS mapping information for each requested DRB at the CU-UP, as described above. The CU-UP may also configure the IP header field based on the QoS mapping information, as described above. The downlink mapping may be configured by the CU-CP at the donor DU, as described above.

[0076] The IAB donor CU may include an IAB donor CU (IAB donor CU-CP) for a control plane (CP) and one or more IAB donor CUs (IAB donor CU-UP) for a user plane (UP). The DRB flow may be sent to / from the UE through an IAB donor DU or an IAB-DU between the IAB donor CU-UPs. The IAB donor CU-UP 712 inserts QoS mapping information into the IP packet, and the QoS mapping information includes a DSCP and an IP flow label. Based on the QoS mapping information, the IAB donor CU-CP 710 configures a routing path for the IAB donor DU 714, so when the IAB donor DU receives an IP packet, the IAB donor DU 714 decides how to route the service.

[0077] Figure 8 800 and 850. As described above, for DL ​​packet processing in 850, the IAB donor CU[-UP] (e.g., IAB donor 1 802A or IAB donor 2 802B) inserts QoS mapping information into the IP packet, the QoS mapping information including DSCP and IP flow label. Based on the QoS mapping information, the IAB donor CU[-CP] configures a routing path for downlink mapping at the IAB donor DU. When the IAB donor DU receives the IP packet, the IAB donor DU can then decide how to route the service based on the IP header and the downlink mapping configuration. The downlink mapping configuration indicates the mapping between the IP header fields (destination IP address, DCSP and / or IPv6 flow label) and the BAP routing ID. The IAB donor DU inserts a BAP header into the packet for carrying the BAP routing ID. The IAB donor DU also determines the mapping between the BAP routing ID and the egress link based on the routing configuration, and the IAB donor DU forwards the BAP packet along the egress link. The IAP donor DU also determines the egress RLC channel based on the IP header and the downlink mapping configuration. The IAP donor DU sends a BAP packet to IAB node 1. IAB node 1 determines that the BAP address (which may be part of the BAP routing ID and carried in the BAP header) does not match its own BAP address (i.e., there is a BAP address mismatch), and determines the egress link for sending the BAP packet based on the BAP routing ID and the routing configuration. Based on the ingress RLC channel and the channel mapping configuration, IAB node 1 determines the egress RLC channel. IAB node 1 then sends the IP packet to IAB node 4 via the determined link and egress RLC channel. The same process is followed for IAB node 4 and IAB node 5, where IAB node 5 determines that the BAP address matches, removes the BAP header, and forwards the IP packet to upper layer processing for transmission to the UE.

[0078] For UL packet processing 800, based on the service type and uplink mapping configuration, the IAB node 5 determines the BAP routing ID and inserts the BAP routing ID into the BAP header. Based on the BAP routing ID and routing configuration, the IAB node 5 determines the egress link, and determines the egress RLC channel based on the service type. The IAB node 5 sends the IP packet to the IAB node 4 based on the determined egress link and egress RLC channel. The IAB node 4 determines the egress link based on the BAP routing ID and routing configuration, and determines the egress RLC channel based on the ingress RLC channel and routing configuration. The IAB node 4 sends the BAP packet to the IAB node 1 based on the determined egress link and egress RLC channel. The IAB node 1 follows the same process, and the IP packet is finally received and processed by the IAB donor where there is a BAP address match.

[0079] Fig. 9 An example topology redundancy 900 for IAB donors is shown. An IAB node may be connected to one or more IAB donors. Fig. 9 As shown, the IAB-MT1 of IAB node 1 904 can be dually connected to CU1 of IAB donor 1 902A and CU2 of IAB donor 2 902B. IAB-DU1 can be connected to CU2 of IAB donor 2 902B. A child node of IAB node 1 (such as IAB node 2) can be connected to CU1 of IAB donor 1 902A. IAB node 3 908 can be connected to CU2 of IAB donor 2 902B. CU1 of IAB donor 1 902A can route F1-U services on a secondary path via a donor DU associated with CU2 of IAB donor 2 902B to facilitate load balancing or redundancy between IAB donors. Various aspects provided herein facilitate CU1 of IAB donor 1 902A to configure QoS mapping for services routed on a topology associated with CU2, and facilitate CU2 of IAB donor 2 902B to configure a routing path with appropriate QoS for services associated with CU1. Similarly, MT1 may be singly connected to parent DU3 908 and CU2 902B, while IAB Node 1 and / or UEs are connected to first donor 902A. For example, for topology adaptation, MT1 may migrate from a first donor to a second donor, wherein at least one of the UE or child / child MT has not yet migrated to the second donor.

[0080] Fig. 9The backhaul routing path shown in carries traffic between CU1 and IAB Node 2, and includes donor DU2, IAB Node 3 908, and IAB Node 1 904 along the path. Thus, the backhaul routing path extends over topology segments that may be managed by different CUs. For example, in some aspects, CU1 may manage backhaul transmissions for a southbound topology segment to IAB Node 1 904 (e.g., between IAB Node 1 904 and IAB Node 2 906). In some aspects, CU2 may manage backhaul transmissions for a northbound topology segment to IAB Node 1 904 (e.g., between IAB Node 1 904 and IAB Node 3 908 or between IAB Node 3 908 and donor DU2).

[0081] Each of the two CUs may not be aware of the topology for the other segment managed by the other CU. If a single BAP Route ID is configured for a path that extends over both topology segments, that BAP Route ID may be selected by either CU1 or CU2. If the BAP Route ID is selected by CU1, CU1 may ensure that the selected BAP Route ID does not conflict with another BAP Route ID within the segment managed by CU1 (this may be more accurate than Fig. 9 ). However, in some aspects, the selected BAP routing ID may conflict with another BAP routing ID used in the topology segment managed by CU2 (this may also be more detailed than Fig. 9 ). Similarly, if Fig. 9 If a BAP routing ID for the inter-domain return routing path is selected by CU2, CU2 can ensure that the selected BAP routing ID does not conflict with another BAP routing ID within the segment managed by CU2, but in some aspects, it may still conflict with a BAP routing ID used in the segment managed by CU1.

[0082] Therefore, it may be advantageous to divide the backhaul routing path into two parts, one for each topology segment. The first part extends between IAB node 1 904 and IAB node 2 906, and the part can be assigned a BAP routing ID by CU1. The second part extends between IAB node 1 904 and donor DU2, and the part can be assigned a BAP routing ID by CU2. In some aspects, IAB node 1 904 can perform header rewriting so that IAB node 1 904 modifies the BAP routing ID of the packet received on the second part (e.g., BAP routing ID=2 910) to another BAP routing ID to be used on the first part (e.g., BAP routing ID=1 912). The header rewriting can be based on a configuration, which can be configured by CU1 or CU2. The configuration indicates a mapping between two BAP routing IDs. Similar examples apply to upstream packets.

[0083] A similar scenario occurs in topology adaptation, where in one example MT1 is initially connected to Fig. 91 904, and then switches the parent node to IAB node 3. Any child / child UE / MT of IAB node 1 may still not have migrated to the second donor, in which case inter-domain BAP routing may be required again. In some aspects, the traffic associated with IAB donor 1 902A that is routed via the topology associated with IAB donor 2 902B may be used for multiple destination IAB nodes associated with IAB donor 1 902A, where IAB node 2 906 may be one of the multiple destinations. Other destination IAB nodes may be child or descendant IAB nodes of IAB node 1 904. Regarding the traffic flow in the downlink direction, for different destinations, the downlink traffic may follow the same or different physical paths between IAB donor DU2 902B and IAB node 1 904. In order for the IAB node 1 904 to perform header rewriting and properly map traffic to the appropriate outgoing BAP routing IDs (e.g., ID 912) for different destinations, traffic received by the IAB node 1 904 from the IAB donor DU2 902B may carry different incoming BAP routing IDs (e.g., ID 910), which may or may not partially include the destination BAP address of the IAB node 1 904. In some aspects, for example, where traffic for different destination IAB nodes follows one physical path (e.g., the same IAB node chain) between the IAB donor DU2 902B and the IAB node 1 904, multiple BAP routing IDs may be assigned to the path. In some aspects, the multiple BAP routing IDs may or may not carry the destination BAP address of the IAB node 1 904. In aspects where the multiple BAP routing IDs carry the destination BAP address of the IAB node 1 904, the node may have one or more destination BAP addresses. In some aspects, multiple BAP route IDs may have the same path ID or different path IDs. Different path IDs may correspond to the same physical path.

[0084] Various aspects provided herein provide a configuration for rewriting a BAP header in an IAB network. For example, a first base station may be configured to modify a mapping configuration between BAP routing IDs. The first base station may be an IAB node.

[0085] In some aspects, the IAB node may receive a packet for carrying a first routing ID from a previous hop node. The IAB node may modify the header of the packet to carry a second routing ID based on a routing configuration (e.g., a header rewrite configuration) for mapping the first routing identifier to the second routing identifier. The IAB node may determine the next hop node based on the second routing ID. The IAB node may send the packet to the next hop node. The second base station may include an IAB donor node. The IAB donor node may indicate to the IAB node to modify the header of the packet carrying the first routing identifier. The IAB donor node may provide the IAB node with a routing configuration (e.g., a header rewrite configuration) for mapping the first routing identifier to the second routing identifier. In some aspects, the packet may be an upstream packet or a downstream packet. In some aspects, the routing identifier may be a BAP routing ID. In some aspects, the header of the packet may be a BAP header. In some aspects, the IAB node may receive a routing configuration from an IAB donor CU. In some aspects, the packet may be an upstream packet, and the first route identifier corresponds to a BAP route between an access IAB node and an IAB node, and the second route identifier corresponds to a BAP route between the IAB node and a donor DU. In some aspects, the packet may be a downstream packet, and the first route identifier corresponds to a BAP route between the donor DU and the IAB node, and the second route identifier corresponds to a BAP route between the IAB node and the access IAB node.

[0086] The BAP route including the next hop node may be managed by the first IAB donor CU, and the BAP route including the previous hop node may be managed by the second IAB donor CU. The first route identifier may carry the BAP address of the IAB node. Modifying the first route identifier to the second route identifier may include changing the destination BAP address of the packet. Modifying the first route identifier to the second route identifier may include changing the BAP path ID of the packet. The routing configuration (e.g., header rewrite configuration) may be based on the ingress BH RLC CH between the previous hop node and the IAB node. The routing configuration may indicate the egress BH RLC CH between the IAB node and the next hop node. The IAB node may receive a packet carrying a third route identifier from the previous hop node. The IAB node may forward a packet with a third route identifier to the next hop node based on the routing configuration. The IAB node may receive the routing configuration on RRC signaling or F1 control plane (F1-C) signaling.

[0087] Fig.101000 is a call flow diagram of signaling between a first base station 1002 and a second base station 1006. The first base station 1002 or the second base station 1004 may be configured to provide at least one cell. The UE may be configured to communicate with the first base station 1002 or the second base station 1004. For example, Figure 1 In the context of , the first base station 1002 or the second base station 1004 can correspond to the base station 102 / 180, and thus, the cell can include a geographic coverage area 110 in which communication coverage is provided and / or a small cell 102' having a coverage area 110'. In addition, the UE can correspond to at least the UE 104. In another example, in Figure 3 In the context of , the first base station 1002 or the second base station 1004 can correspond to the base station 310, and the UE can correspond to the UE 350.

[0088] As shown at 1006, the second base station 1004 can configure the first base station 1002 to modify a packet header of the packet. The second base station 1004 can configure the first base station 1002 to modify a packet header of the packet, wherein the packet header can indicate the first routing ID. The first base station 1002 can receive a configuration for modifying the packet header from the second base station 1004.

[0089] As shown at 1008, the second base station 1004 may send a routing configuration (e.g., a header rewrite configuration) for indicating a mapping between the first routing ID and the second routing ID. The second base station 1004 may send a routing configuration for indicating a mapping between the first routing ID and the second routing ID to the first base station 1002. The first base station 1002 may receive a routing configuration from the second base station 1004. In some aspects, the first base station 1002 may be an IAB node, and the second base station 1004 may be an IAB donor node. In some aspects, the first routing ID may include a BAP address of the first base station 1002. In some aspects, the routing configuration (e.g., a header rewrite configuration) may also indicate a mapping between an ingress backhaul RLC channel between a forward hop node of the first base station 1002 and the first base station 1002. A packet may be received from the forward hop node. The second routing ID may be determined based on a routing configuration that maps both the first routing ID and the ingress backhaul RLC channel to the second routing ID. For the second routing ID, the routing configuration may indicate an egress backhaul RLC channel between the first base station 1002 and the next hop node of the first base station 1002. The packet may be sent to the next hop node via the egress backhaul RLC channel. In some aspects, for the second routing ID, the routing configuration may indicate a mapping between an ingress backhaul RLC channel and an egress backhaul RLC channel, wherein the ingress backhaul RLC channel is between the first base station 1002 and the first base station 1002, and the egress backhaul RLC channel is between the first base station 1002 and the next hop node of the first base station 1002. A packet may be received from the previous hop node, and the packet may be sent to the next hop node via the egress backhaul RLC channel. In some aspects, the routing configuration may be sent via one of RRC signaling or F1 control plane (F1-C) signaling.

[0090] As shown at 1010, the first base station 1002 can receive a packet having a packet header indicating a first routing ID. In some aspects, the packet can include a BAP packet. In some aspects, the packet header of the packet can include a BAP header. In some aspects, the packet can include one of an upstream packet or a downstream packet.

[0091] As shown at 1012, the first base station 1002 may determine a second routing ID. The first base station 1002 may determine the second routing ID based on a routing configuration (e.g., a header rewrite configuration) for mapping the first routing ID in the packet header to the second routing ID. In some aspects, the packet may include an upstream packet, and the first routing ID may correspond to a first BAP route between the access IAB node and the first base station, and the first base station is an IAB node. The access IAB node may have a signaling connection with the second base station 1004, and the second routing ID may correspond to a second BAP route between the first base station 1002 and the IAB donor node. In some aspects, the IAB donor node may be different from the second base station 1004. In some aspects, the first BAP route may be managed by the second base station 1004, and the second BAP route may be managed by the IAB donor node. In some aspects, the packet may include a downstream packet, and the first routing ID may correspond to a first BAP route between the IAB donor node and the first base station 1002, and the first base station 1004 may be an IAB node. The second route ID may correspond to a second BAP route between the first base station 1002 and an access IAB node, which may have a signaling connection with the second base station 1004. In some aspects, the IAB donor node may be different from the second base station 1004. In some aspects, the first BAP route may be managed by the IAB donor node and the second BAP route may be managed by the second base station 1004.

[0092] As shown at 1014, the first base station 1002 may modify the packet header. The first base station 1002 may modify the packet header to replace the first routing ID with the second routing ID. The first base station 1002 may modify the packet header to replace the first routing ID with the second routing ID based on the determination of the second routing ID. In some aspects, modifying the packet header to replace the first routing ID with the second routing ID may also include: changing at least one of a destination BAP address of the packet or changing a BAP path ID of the packet.

[0093] First base station 1002 may send the packet based on the second routing ID, as shown at 1016. The packet may be sent to the next hop node based on the second routing ID.

[0094] In some aspects, the first base station 1002 may receive the second packet. The first base station 1002 may receive the second packet having a packet header indicating a third routing ID. The first base station 1002 may receive the second packet from a previous hop node of the first base station 1002.

[0095] In some aspects, first base station 1002 may determine that the third routing ID may be excluded from the mapping for modification to a different routing ID. First base station 1004 may determine based on the received routing configuration that the third routing ID may be excluded from the mapping for modification to a different routing ID within the routing configuration.

[0096] In some aspects, the first base station 1002 may forward the second packet to the next hop node.The first base station 1002 may forward the second packet to the next hop node based on the third routing ID.

[0097] Fig.11 1100 is a flow chart of a method of wireless communication. The method may be performed by a base station or a component of a base station (e.g., base station 102 / 180, 1002; apparatus 1302; baseband unit 1304, which may include memory 376 and may be the entire base station 310 or a component of base station 310, such as TX processor 316, RX processor 370 and / or controller / processor 375). One or more of the operations shown may be omitted, swapped, or performed simultaneously. The method may allow a base station to modify a mapping configuration between BAP routing IDs.

[0098] At 1102, the first base station may receive a routing configuration (e.g., a header rewrite configuration). For example, 1102 may be performed by the routing component 1340 of the device 1302. The first base station may receive a routing configuration for indicating a mapping between a first routing ID and a second routing ID. The first base station may receive a routing configuration from a second base station. In some aspects, the first base station may be an IAB node, and the second base station may be an IAB donor node. In some aspects, the first routing ID may include a BAP address of the first base station. In some aspects, the routing configuration may also indicate a mapping between an ingress return RLC channel between a forward hop node of the first base station and the first base station. A packet may be received from the forward hop node. The second routing ID may be determined based on a routing configuration for mapping both the first routing ID and the ingress return RLC channel to a second routing ID. For the second routing ID, the routing configuration may indicate an egress return RLC channel between the first base station and the next hop node of the first base station. The packet may be sent to the next hop node via the egress return RLC channel. In some aspects, for the second routing ID, the routing configuration may indicate a mapping between an ingress backhaul RLC channel and an egress backhaul RLC channel, the ingress backhaul RLC channel being between a previous hop node of the first base station and the first base station, and the egress backhaul RLC channel being between the first base station and a next hop node of the first base station. A packet may be received from the previous hop node, and the packet may be sent to the next hop node via the egress backhaul RLC channel. In some aspects, the routing configuration may be received via one of RRC signaling or F1-C signaling.

[0099] At 1104, the first base station may receive a packet having a packet header indicating a first routing ID. For example, 1104 may be performed by a packet component 1342 of the apparatus 1302. In some aspects, the packet may include a BAP packet. In some aspects, a packet header of the packet may include a BAP header. In some aspects, the packet may include one of an upstream packet or a downstream packet.

[0100] At 1106, the first base station may determine a second routing ID. For example, 1106 may be performed by the determination component 1344 of the device 1302. The first base station may determine the second routing ID based on a routing configuration for mapping the first routing ID in the packet header to the second routing ID. In some aspects, the packet may include an upstream packet, and the first routing ID may correspond to a first BAP route between the access IAB node and the first base station, and the first base station is an IAB node. The access IAB node may have a signaling connection with the second base station 1004, and the second routing ID may correspond to a second BAP route between the first base station and the IAB donor node. In some aspects, the IAB donor node may be different from the second base station. In some aspects, the first BAP route may be managed by the second base station, and the second BAP route may be managed by the IAB donor node. In some aspects, the packet may include a downstream packet, and the first routing ID may correspond to a first BAP route between the IAB donor node and the first base station, and the first base station may be an IAB node. The second route ID may correspond to a second BAP route between the first base station and an access IAB node, and the access IAB node may have a signaling connection with the second base station. In some aspects, the IAB donor node may be different from the second base station. In some aspects, the first BAP route may be managed by the IAB donor node and the second BAP route may be managed by the second base station.

[0101] At 1108, the first base station may modify the packet header. For example, 1108 may be performed by the modifying component 1346 of the apparatus 1302. The first base station may modify the packet header to replace the first routing ID with the second routing ID. The first base station may modify the packet header to replace the first routing ID with the second routing ID based on the determination of the second routing ID. In some aspects, modifying the packet header to replace the first routing ID with the second routing ID may also include: changing at least one of a destination BAP address of the packet or changing a BAP path ID of the packet.

[0102] At 1110, the first base station may send the packet based on the second routing ID. For example, 1110 may be performed by the sending component 1334 of the device 1302. The packet may be sent to the next hop node based on the second routing ID.

[0103] Fig.12 1200 is a flow chart of a method of wireless communication. The method may be performed by a base station or a component of a base station (e.g., base station 102 / 180, 1002; apparatus 1302; baseband unit 1304, which may include memory 376 and may be the entire base station 310 or a component of base station 310, such as TX processor 316, RX processor 370 and / or controller / processor 375). One or more of the operations shown may be omitted, swapped, or performed simultaneously. The method may allow a base station to modify a mapping configuration between BAP routing IDs.

[0104] At 1202, the first base station may receive a routing configuration (e.g., a header rewrite configuration). For example, 1202 may be performed by the routing component 1340 of the device 1302. The first base station may receive a routing configuration for indicating a mapping between a first routing ID and a second routing ID. The first base station may receive a routing configuration from a second base station. In some aspects, the first base station may be an IAB node, and the second base station may be an IAB donor node. In some aspects, the first routing ID may include a BAP address of the first base station. In some aspects, the routing configuration may also indicate a mapping between an ingress return RLC channel between a forward hop node of the first base station and the first base station. A packet may be received from the forward hop node. The second routing ID may be determined based on a routing configuration for mapping both the first routing ID and the ingress return RLC channel to a second routing ID. For the second routing ID, the routing configuration may indicate an egress return RLC channel between the first base station and the next hop node of the first base station 1002. The packet may be sent to the next hop node via the egress return RLC channel. In some aspects, for the second routing ID, the routing configuration may indicate a mapping between an ingress backhaul RLC channel and an egress backhaul RLC channel, the ingress backhaul RLC channel being between a previous hop node of the first base station and the first base station 1002, and the egress backhaul RLC channel being between the first base station and a next hop node of the first base station. A packet may be received from the previous hop node, and the packet may be sent to the next hop node via the egress backhaul RLC channel. In some aspects, the routing configuration may be received via one of RRC signaling or F1-C signaling.

[0105] At 1204, the first base station may receive a packet having a packet header indicating a first routing ID. For example, 1204 may be performed by a packet component 1342 of the apparatus 1302. In some aspects, the packet may include a BAP packet. In some aspects, a packet header of the packet may include a BAP header. In some aspects, the packet may include one of an upstream packet or a downstream packet.

[0106] At 1206, the first base station may determine a second routing ID. For example, 1206 may be performed by the determination component 1344 of the device 1302. The first base station may determine the second routing ID based on a routing configuration for mapping the first routing ID in the packet header to the second routing ID. In some aspects, the packet may include an upstream packet, and the first routing ID may correspond to a first BAP route between the access IAB node and the first base station, and the first base station is an IAB node. The access IAB node may have a signaling connection with the second base station 1004, and the second routing ID may correspond to a second BAP route between the first base station and the IAB donor node. In some aspects, the IAB donor node may be different from the second base station. In some aspects, the first BAP route may be managed by the second base station, and the second BAP route may be managed by the IAB donor node. In some aspects, the packet may include a downstream packet, and the first routing ID may correspond to a first BAP route between the IAB donor node and the first base station, and the first base station may be an IAB node. The second route ID may correspond to a second BAP route between the first base station and an access IAB node, and the access IAB node may have a signaling connection with the second base station. In some aspects, the IAB donor node may be different from the second base station. In some aspects, the first BAP route may be managed by the IAB donor node and the second BAP route may be managed by the second base station.

[0107] At 1208, the first base station may modify the packet header. For example, 1208 may be performed by the modification component 1346 of the apparatus 1302. The first base station may modify the packet header to replace the first routing ID with the second routing ID. The first base station may modify the packet header to replace the first routing ID with the second routing ID based on the determination of the second routing ID. In some aspects, modifying the packet header to replace the first routing ID with the second routing ID may also include: changing at least one of a destination BAP address of the packet or changing a BAP path ID of the packet.

[0108] At 1210, the first base station may send the packet based on the second routing ID. For example, 1210 may be performed by a sending component 1334 of the apparatus 1302. The packet may be sent to a next hop node based on the second routing ID.

[0109] At 1212, the first base station may receive the second packet. For example, 1212 may be performed by packet component 1342 of apparatus 1302. The first base station may receive the second packet having a packet header indicating a third routing ID. The first base station may receive the second packet from a previous hop node of the first base station.

[0110] At 1214, the first base station may determine that the third routing ID may be excluded from the mapping for modification to a different routing ID. For example, 1214 may be performed by a determining component 1344 of the apparatus 1302. The first base station may determine based on the received routing configuration that the third routing ID may be excluded from the mapping for modification to a different routing ID within the routing configuration.

[0111] At 1216, the first base station may forward the second packet to the next hop node. For example, 1216 may be performed by the sending component 1334 of the apparatus 1302. The first base station may forward the second packet to the next hop node based on the third routing ID.

[0112] Fig.13 1300 is a diagram illustrating an example of a hardware implementation for an apparatus 1302. The apparatus 1302 may be a base station, a component of a base station, or may implement base station functionality. In some aspects, the apparatus 1302 may include a baseband unit 1304. The baseband unit 1304 may communicate with the UE 104 via a cellular RF transceiver. The baseband unit 1304 may include a computer-readable medium / memory. The baseband unit 1304 is responsible for general processing, including executing software stored on a computer-readable medium / memory. The software, when executed by the baseband unit 1304, causes the baseband unit 1304 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the baseband unit 1304 when executing the software. The baseband unit 1304 also includes a receiving component 1330, a communication manager 1332, and a sending component 1334. The communication manager 1332 includes one or more components shown. The components within the communication manager may be stored in a computer-readable medium / memory and / or configured as hardware within the baseband unit 1304. The baseband unit 1304 may be a component of the base station 310 and may include a memory 376 and / or at least one of the TX processor 316 , the RX processor 370 , and the controller / processor 375 .

[0113] The communication manager 1332 includes a routing component 1340 that can receive a routing configuration, for example, as described in conjunction with Fig.11 1102 or Fig.12 1202 described. The communication manager 1332 also includes a packet component 1342, which can receive a packet having a packet header indicating a first routing ID, for example, as described in conjunction with Fig.11 1104 or Fig.12 1204 described. The grouping component 1342 can be configured to receive a second grouping, for example, as combined Fig.12 The communication manager 1332 also includes a determining component 1344, which can determine the second routing ID, for example, as described in conjunction with Fig.11 1106 or Fig.12 1206. The determining component 1344 can be configured to determine that the third routing ID can be excluded from the mapping for modification to a different routing ID, for example, as combined Fig.12 1214 described. The communication manager 1332 also includes a modification component 1346, which can modify the packet header, for example, as combined Fig.11 1108 or Fig.12 The sending component 1334 can be configured to forward the second packet to the next hop node, for example, as described in conjunction with Fig.12 of 1216 described.

[0114] The apparatus may include executing Fig.11 and 12 Each block in the flowchart of the algorithm has an additional component. Therefore, it can be performed by the component Fig.11 and 12 Each block in the flowchart of the process / algorithm may be included in the apparatus, and the apparatus may include one or more of those components. The components may be one or more hardware components specifically 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] As shown, the device 1302 may include various components configured for various functions. In one configuration, the device 1302 (specifically, the baseband unit 1304) includes a unit for receiving a routing configuration for indicating a mapping between a first routing ID and a second routing ID from a second base station. The device includes a unit for receiving a packet with a packet header for indicating a first routing ID. The device includes a unit for determining a second routing ID based on a routing configuration that maps a first routing ID in a packet header to a second routing ID. The device includes a unit for modifying a packet header based on a determination of a second routing ID to replace the first routing ID with a second routing ID. The device includes a unit for sending a packet based on a second routing ID. The device also includes a unit for receiving a second packet with a packet header for indicating a third routing ID. The device also includes a unit for determining based on the routing configuration that the third routing ID is excluded from the different routing IDs used to modify the routing configuration in the mapping. The device also includes a unit for forwarding the second packet to a next hop node based on the third routing ID. A means may be one or more of the components of the apparatus 1302 configured to perform the functions recited by the means. As described above, the apparatus 1302 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Thus, in one configuration, a means may be the TX processor 316, the RX processor 370, and the controller / processor 375 configured to perform the functions recited by the means.

[0116] Fig.14 1400 is a flow chart of a method of wireless communication. The method may be performed by a base station or a component of a base station (e.g., base station 102 / 180, 1004; apparatus 1502; baseband unit 1504, which may include memory 376 and may be the entire base station 310 or a component of base station 310, such as TX processor 316, RX processor 370 and / or controller / processor 375). One or more of the operations shown may be omitted, swapped, or performed simultaneously. The method may allow a base station to configure the base station to modify a mapping configuration between BAP routing IDs.

[0117] At 1402, the second base station may configure the first base station to modify a packet header of a packet. For example, 1402 may be performed by a modification component 1540 of the device 1502. The second base station may configure the first base station to modify a packet header of a packet, wherein the packet header may indicate a first routing ID. In some aspects, the packet may include a BAP packet. In some aspects, the packet header of the packet may include a BAP header. In some aspects, the first base station may include an IAB node, and the second base station may include an IAB donor node. In some aspects, the packet may be one of an upstream packet or a downstream packet. In some aspects, the packet may be an upstream packet, and the first routing ID may correspond to a first BAP route between an access IAB node and a first base station, and the first base station is an IAB node. The access IAB node may have a signaling connection with the second base station 1004. The second routing ID may correspond to a second BAP route between the first base station and the IAB donor node. In some aspects, the IAB donor node may be different from the second base station. In some aspects, the first BAP route may be managed by the second base station and the second BAP route may be managed by the IAB donor node. In some aspects, the packet may be a downstream packet, and the first route ID may correspond to the first BAP route between the IAB donor node and the first base station, the first base station being an IAB node. The second route ID may correspond to the second BAP route between the first base station and the access IAB node. The access IAB node may have a signaling connection with the second base station. The IAB donor node may be different from the second base station. In some aspects, the first BAP route may be managed by the IAB donor node, and the second BAP route may be managed by the second base station. In some aspects, the first route ID may include the BAP address of the first base station.

[0118] At 1404, the second base station may send a routing configuration (e.g., a header rewrite configuration) indicating a mapping between the first routing ID and the second routing ID. For example, 1404 may be performed by routing component 1542 of apparatus 1502. The second base station may send a routing configuration to the first base station indicating a mapping between the first routing ID and the second routing ID. In some aspects, the routing configuration may be sent via one of RRC signaling or F1-C signaling.

[0119] Fig.151500 is a diagram illustrating an example of a hardware implementation for an apparatus 1502. The apparatus 1502 may be a base station, a component of a base station, or may implement base station functionality. In some aspects, the apparatus 1502 may include a baseband unit 1504. The baseband unit 1504 may communicate with the UE 104 via a cellular RF transceiver 1522. The baseband unit 1504 may include a computer-readable medium / memory. The baseband unit 1504 is responsible for general processing, including executing software stored on a computer-readable medium / memory. The software, when executed by the baseband unit 1504, causes the baseband unit 1504 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the baseband unit 1504 when executing the software. The baseband unit 1504 also includes a receiving component 1530, a communication manager 1532, and a sending component 1534. The communication manager 1532 includes one or more components shown. The components within the communication manager may be stored in a computer-readable medium / memory and / or configured as hardware within the baseband unit 1504. The baseband unit 1504 may be a component of the base station 310 and may include the memory 376 and / or at least one of the TX processor 316 , the RX processor 370 , and the controller / processor 375 .

[0120] The communication manager 1532 includes a modification component 1540, which can configure the first base station to modify the packet header of the packet, for example, as in conjunction with Fig.14 The communication manager 1532 also includes a routing component 1542, which can send a routing configuration indicating a mapping between a first routing ID and a second routing ID, for example, as described in conjunction with Fig.14 1404 described.

[0121] The apparatus may include executing Fig.14 Each block in the flowchart of the algorithm has an additional component. Therefore, it can be performed by the component Fig.14 Each block in the flowchart of the process / algorithm may be included in the apparatus, and the apparatus may include one or more of those components. The components may be one or more hardware components specifically 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.

[0122] As shown, the device 1502 may include various components configured for various functions. In one configuration, the device 1502 (specifically, the baseband unit 1504) includes a unit for configuring the first base station to modify the packet header of the packet, wherein the packet header indicates the first routing ID. The device includes a unit for sending a routing configuration indicating the mapping between the first routing ID and the second routing ID to the first base station. The unit may be one or more components of the components of the device 1502 that are configured to perform the functions recorded by the unit. As described above, the device 1502 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Therefore, in one configuration, the unit may be a TX processor 316, an RX processor 370, and a controller / processor 375 configured to perform the functions recorded by the unit.

[0123] It should be understood that the specific order or hierarchy of blocks in the disclosed process / flowchart is an illustration of an exemplary method. It should be understood that the specific order or hierarchy of blocks in the process / flowchart can be rearranged based on design preferences. In addition, some blocks can be merged or omitted. The attached method claims provide the elements of each block in a sample order and are not meant to be limited to the specific order or hierarchy provided.

[0124] The foregoing description is provided so that any person skilled in the art can implement the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but to conform to the full range consistent with the content expressed by the claims, wherein, unless explicitly stated as such, reference to the singular element is not intended to mean "one and only one", but "one or more". Terms such as "if", "when ..." and "while ..." should be interpreted as "under the condition of ...", rather than implying an immediate time relationship or reaction. That is, these phrases (e.g., "when ...") do not mean immediate action in response to the occurrence of an action or during the occurrence of an action, but only mean that the action will occur if the condition is met, but do not require a specific or immediate time constraint for the occurrence of the action. The word "exemplary" used herein means "as an example, instance or illustration". Any aspect described as "exemplary" herein need not be interpreted as being preferred to or having advantages over other aspects. Unless otherwise explicitly stated, the term "some" 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 multiples of A, multiples of B, or multiples of 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 only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may include one or more members of A, B, or C. All structural and functional equivalents to the elements of the various aspects described throughout the disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Furthermore, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly recorded in the claims. The words "module," "mechanism," "element," "device," and the like may not be substitutes for the word "unit." Likewise, no claim element is to be interpreted as a functional unit unless the element is explicitly recorded using the phrase "unit for..."

[0125] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

[0126] Aspect 1 is an apparatus for wireless communication at a first base station, comprising at least one processor coupled to a memory and configured to: receive a routing configuration indicating a mapping between a first routing ID and a second routing ID from a second base station; receive a packet having a packet header indicating the first routing ID; determine the second routing ID based on the routing configuration mapping the first routing ID in the packet header to the second routing ID; modify the packet header to replace the first routing ID with the second routing ID based on the determination of the second routing ID; and send the packet based on the second routing ID. .

[0127] Aspect 2 is the apparatus according to aspect 1, further comprising: a transceiver coupled to the at least one processor.

[0128] Aspect 3 is an apparatus according to any one of aspects 1 and 2, further comprising: the packet is a BAP packet.

[0129] Aspect 4 is an apparatus according to any one of aspects 1-3, further comprising: the packet header of the packet is a BAP header.

[0130] Aspect 5 is an apparatus according to any one of aspects 1-4, further comprising: the packet is one of an upstream packet or a downstream packet.

[0131] Aspect 6 is an apparatus according to any one of Aspects 1-5, further comprising: the packet is the upstream packet, and the first routing ID corresponds to a first BAP route between an access IAB node and the first base station, the first base station is an IAB node, the access IAB node has a signaling connection with the second base station, and the second routing ID corresponds to a second BAP route between the first base station and an IAB donor node.

[0132] Aspect 7 is an apparatus according to any one of aspects 1-6, further comprising: the IAB donor node is different from the second base station.

[0133] Aspect 8 is an apparatus according to any one of aspects 1-7, further comprising: the first BAP route is managed by the second base station, and the second BAP route is managed by the IAB donor node.

[0134] Aspect 9 is an apparatus according to any one of Aspects 1-8, further comprising: the packet is the downstream packet, and the first routing ID corresponds to a first BAP route between the IAB donor node and the first base station, the first base station is an IAB node, and the second routing ID corresponds to a second BAP route between the first base station and an access IAB node, and the access IAB node has a signaling connection with the second base station.

[0135] Aspect 10 is an apparatus according to any one of aspects 1-9, further comprising: the IAB donor node is different from the second base station.

[0136] Aspect 11 is an apparatus according to any one of aspects 1-10, further comprising: the first BAP route is managed by the IAB donor node, and the second BAP route is managed by the second base station.

[0137] Aspect 12 is an apparatus according to any one of aspects 1-11, further comprising: the first routing ID comprises a BAP address of the first base station.

[0138] Aspect 13 is an apparatus according to any one of Aspects 1-12, further comprising: modifying the packet header to replace the first routing ID with the second routing ID also comprises: changing at least one of the destination BAP address of the packet or changing the BAP path ID of the packet.

[0139] Aspect 14 is an apparatus according to any one of Aspects 1-13, further comprising: the routing configuration also indicates a mapping between an ingress return RLC channel between a forward hop node of the first base station and the first base station, the packet is received from the forward hop node, and the second routing ID is determined based on the routing configuration for mapping both the first routing ID and the ingress return RLC channel to the second routing ID.

[0140] Aspect 15 is an apparatus according to any one of Aspects 1-14, further comprising: for the second routing ID, the routing configuration indicates an exit return RLC channel between the first base station and the next hop node of the first base station, and the packet is sent to the next hop node through the exit return RLC channel.

[0141] Aspect 16 is an apparatus according to any one of Aspects 1-15, further comprising: for the second routing ID, the routing configuration indicates a mapping between an ingress return RLC channel and an egress return RLC channel, the ingress return RLC channel is between a previous hop node of the first base station and the first base station, the egress return RLC channel is between the first base station and a next hop node of the first base station, the packet is received from the previous hop node, and the packet is sent to the next hop node through the egress return RLC channel.

[0142] Aspect 17 is an apparatus according to any one of Aspects 1-16, further comprising: the at least one processor is also configured to: receive a second packet having the packet header indicating a third routing ID; determine based on the routing configuration: the third routing ID is excluded in the mapping from different routing IDs used for modification into the routing configuration; and forward the second packet to a next hop node based on the third routing ID.

[0143] Aspect 18 is an apparatus according to any one of aspects 1-17, further comprising: the routing configuration is received through one of RRC signaling or F1-C signaling.

[0144] Aspect 19 is a method for implementing wireless communication of any one of aspects 1-18.

[0145] Aspect 20 is an apparatus for wireless communication, comprising means for implementing any one of aspects 1-18.

[0146] Aspect 21 is a computer-readable medium storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 1-18.

[0147] Aspect 22 is an apparatus for wireless communication at a second base station, comprising at least one processor coupled to a memory and configured to: configure a first base station to modify a packet header of a packet, wherein the packet header indicates a first routing ID; and send a routing configuration to the first base station indicating a mapping between the first routing ID and a second routing ID.

[0148] Aspect 23 is the apparatus of aspect 22, further comprising: a transceiver coupled to the at least one processor.

[0149] Aspect 24 is an apparatus according to any one of aspects 21 and 22, further comprising: the packet is a BAP packet, wherein the packet header of the packet is a BAP header.

[0150] Aspect 25 is an apparatus according to any one of aspects 21-23, further comprising: the packet is one of an upstream packet or a downstream packet.

[0151] Aspect 26 is an apparatus according to any one of Aspects 21-24, further comprising: the packet is the upstream packet, and the first routing ID corresponds to a first BAP route between an access IAB node and the first base station, the first base station is an IAB node, the access IAB node has a signaling connection with the second base station, and the second routing ID corresponds to a second BAP route between the first base station and an IAB donor node.

[0152] Aspect 27 is an apparatus according to any one of aspects 21-25, further comprising: the IAB donor node is different from the second base station.

[0153] Aspect 28 is an apparatus according to any one of Aspects 21-26, further comprising: the packet is the downstream packet, and the first routing ID corresponds to a first BAP route between the IAB donor node and the first base station, the first base station is an IAB node, and the second routing ID corresponds to a second BAP route between the first base station and an access IAB node, and the access IAB node has a signaling connection with the second base station.

[0154] Aspect 29 is an apparatus according to any one of aspects 21-27, further comprising: the IAB donor node is different from the second base station.

[0155] Aspect 30 is an apparatus according to any one of aspects 21-28, further comprising: the first routing ID comprises a BAP address of the first base station.

[0156] Aspect 31 is an apparatus according to any one of aspects 21-29, further comprising: the routing configuration is sent via one of RRC signaling or F1-C signaling.

[0157] Aspect 32 is a method for implementing wireless communication of any one of aspects 21-31.

[0158] Aspect 33 is an apparatus for wireless communication, comprising means for implementing any one of aspects 21-31.

[0159] Aspect 34 is a computer-readable medium storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 21-31.

Claims

1. An apparatus for wireless communication at a first base station, comprising: Memory; as well as at least one processor coupled to the memory and configured to: receiving, from a second base station, a routing configuration indicating a mapping between a first routing identifier (ID) and a second routing ID; receiving a packet having a packet header indicating the first routing ID; determining the second routing ID based on the routing configuration for mapping the first routing ID in the packet header to the second routing ID; modifying the packet header to replace the first routing ID with the second routing ID based on the determination of the second routing ID; as well as The packet is sent based on the second routing ID.

2. The apparatus according to claim 1, further comprising: A transceiver is coupled to the at least one processor.

3. The device according to claim 1, wherein: The packet is a Backhaul Adaptation Protocol (BAP) packet.

4. The device according to claim 1, wherein: The packet header of the packet is a Backhaul Adaptation Protocol (BAP) header.

5. The device according to claim 1, wherein: The packet is one of an upstream packet or a downstream packet.

6. The device according to claim 5, wherein: The packet is the upstream packet, and the first route ID corresponds to a first backhaul adaptation protocol (BAP) route between an access integrated access backhaul (IAB) node and the first base station, the first base station is an IAB node, the access IAB node has a signaling connection with the second base station, and the second route ID corresponds to a second BAP route between the first base station and an IAB donor node.

7. The device according to claim 6, wherein: The IAB donor node is different from the second base station.

8. The device according to claim 6, wherein: The first BAP route is managed by the second base station, and the second BAP route is managed by the IAB donor node.

9. The device according to claim 5, wherein: The packet is the downstream packet, and the first route ID corresponds to a first backhaul adaptation protocol (BAP) route between an integrated access backhaul (IAB) donor node and the first base station, the first base station is an IAB node, and the second route ID corresponds to a second BAP route between the first base station and an access IAB node, the access IAB node having a signaling connection with the second base station.

10. The device according to claim 9, wherein: The IAB donor node is different from the second base station.

11. The device according to claim 9, wherein: The first BAP route is managed by the IAB donor node, and the second BAP route is managed by the second base station.

12. The device according to claim 1, wherein: The first routing ID includes a Backhaul Adaptation Protocol (BAP) address of the first base station.

13. The device according to claim 1, wherein: The modifying the packet header to replace the first routing ID with the second routing ID further includes at least one of changing a destination Backhaul Adaptation Protocol (BAP) address of the packet or changing a BAP path ID of the packet.

14. The device according to claim 1, wherein: The routing configuration also indicates a mapping between an ingress backhaul radio link control (RLC) channel between a forward hop node of the first base station and the first base station, the packet is received from the forward hop node, and the second routing ID is determined based on the routing configuration for mapping both the first routing ID and the ingress backhaul RLC channel to the second routing ID.

15. The device according to claim 14, wherein: For the second route ID, the route configuration indicates an egress backhaul RLC channel between the first base station and a next hop node of the first base station, and the packet is sent to the next hop node through the egress backhaul RLC channel.

16. The device according to claim 1, wherein For the second routing ID, the routing configuration indicates a mapping between an ingress backhaul radio link control (RLC) channel and an egress backhaul RLC channel, the ingress backhaul RLC channel being between a previous hop node of the first base station and the first base station, the egress backhaul RLC channel being between the first base station and a next hop node of the first base station, the packet being received from the previous hop node, and the packet being sent to the next hop node through the egress backhaul RLC channel.

17. The device according to claim 1, wherein: The at least one processor is further configured to: receiving a second packet having the packet header indicating a third routing ID; determining, based on the routing configuration: the third routing ID is excluded from the different routing IDs used for modification into the routing configuration in the mapping; as well as The second packet is forwarded to a next hop node based on the third routing ID.

18. The device according to claim 1, wherein: The routing configuration is received via one of radio resource control (RRC) signaling or F1 control plane (F1-C) signaling.

19. A method for wireless communication of a first base station (BS), comprising: receiving, from a second base station, a routing configuration indicating a mapping between a first routing identifier (ID) and a second routing ID; receiving a packet having a packet header indicating the first routing ID; determining the second routing ID based on the routing configuration for mapping the first routing ID in the packet header to the second routing ID; modifying the packet header to replace the first routing ID with the second routing ID based on the determination of the second routing ID; as well as The packet is sent based on the second routing ID.

20. An apparatus for wireless communication at a second base station, comprising: Memory; as well as at least one processor coupled to the memory and configured to: configuring the first base station to modify a packet header of the packet, wherein the packet header indicates a first routing identifier (ID); and A routing configuration indicating a mapping between the first routing ID and a second routing ID is sent to the first base station.

21. The apparatus according to claim 20, further comprising: A transceiver is coupled to the at least one processor.

22. The device according to claim 20, wherein: The packet is a Backhaul Adaptation Protocol (BAP) packet, wherein the packet header of the packet is a BAP header.

23. The device according to claim 20, wherein: The packet is one of an upstream packet or a downstream packet.

24. The device according to claim 23, wherein: The packet is the upstream packet, and the first route ID corresponds to a first backhaul adaptation protocol (BAP) route between an access integrated access backhaul (IAB) node and the first base station, the first base station is an IAB node, the access IAB node has a signaling connection with the second base station, and the second route ID corresponds to a second BAP route between the first base station and an IAB donor node.

25. The device according to claim 24, wherein: The IAB donor node is different from the second base station.

26. The device according to claim 23, wherein The packet is the downstream packet, and the first route ID corresponds to a first backhaul adaptation protocol (BAP) route between an integrated access backhaul (IAB) donor node and the first base station, the first base station is an IAB node, and the second route ID corresponds to a second BAP route between the first base station and an access IAB node, the access IAB node having a signaling connection with the second base station.

27. The device according to claim 26, wherein: The IAB donor node is different from the second base station.

28. The device according to claim 20, wherein: The first routing ID includes a Backhaul Adaptation Protocol (BAP) address of the first base station.

29. The device according to claim 20, wherein: The routing configuration is sent via one of radio resource control (RRC) signaling or F1 control plane (F1-C) signaling.

30. A wireless communication method of a second base station, comprising: configuring the first base station to modify a packet header of the packet, wherein the packet header indicates a first routing identifier (ID); and A routing configuration indicating a mapping between the first routing ID and a second routing ID is sent to the first base station.

Images