BAP configuration associated with the topology identifier

Abstract

The second network node determines a backhaul adaptation protocol (BAP) configuration associated with backhaul traffic transmission and includes a topology identifier corresponding to a topology in a plurality of topologies, for which traffic associated with the topology is transmitted based on the BAP configuration. The second network node sends the BAP configuration associated with backhaul traffic transmission to the first network node. The first network node receives a first BAP configuration associated with a first topology identifier (ID) corresponding to the first topology and a second BAP configuration associated with a second topology ID corresponding to a second topology that at least partially overlaps with the first topology. The first network node determines to route traffic associated with the first topology ID based on the first BAP configuration, and to route traffic associated with the second topology ID based on the second BAP configuration.

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,477, filed on October 22, 2020, and entitled “BAP Configuration Including Associated with a Topology Identifier”; and U.S. Patent Application No. 17 / 451,797, filed on October 21, 2021, and entitled “BAP Configuration Associated with a Topology Identifier”, the entire contents of which are expressly incorporated herein by reference. Technical Field

[0003] The present disclosure relates generally to communication systems and, more particularly, to wireless communications in an Integrated Access and Backhaul (IAB) network. Background Art

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

[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 (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., together 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 for further improvements in 5G NR technology. These improvements may also be applicable to other multiple access technologies and telecommunication standards that employ 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 an extensive overview of all expected aspects, and is neither intended to identify the key or important elements of all aspects, nor to delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description that will be given later.

[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may include a first network node. The apparatus receives a first backhaul adaptation protocol (BAP) configuration associated with a first topology and a second BAP configuration associated with a second topology that at least partially overlaps with the first topology. The apparatus routes traffic associated with the first topology based on the first BAP configuration and routes traffic associated with the second topology based on the second BAP configuration.

[0008] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may include a first network node. The apparatus receives a first BAP configuration associated with a first topology identifier (ID) corresponding to a first topology and a second BAP configuration associated with a second topology ID corresponding to a second topology that at least partially overlaps with the first topology. The apparatus determines whether a service is associated with the first topology ID or the second topology ID, and routes the service associated with the first topology ID based on the first BAP configuration, and routes the service associated with the second topology ID based on the second BAP configuration.

[0009] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may include a second network node. The apparatus determines a BAP configuration associated with backhaul traffic transmission, the BAP configuration including a topology identifier corresponding to a topology in a plurality of topologies, for which a service associated with the topology is transmitted based on the BAP configuration. The apparatus sends the BAP configuration associated with backhaul traffic transmission to a first network node.

[0010] To accomplish the foregoing and related purposes, one or more aspects include 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 indicative of only 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

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

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

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

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

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

[0016] Figure 3 is a schematic diagram illustrating an example of a first wireless device and a second wireless device in an access network.

[0017] Figure 4 is a schematic diagram illustrating an example IAB network.

[0018] Figure 5 is a schematic diagram illustrating an example IAB network and its components.

[0019] Figure 6 is a schematic diagram showing example connections for an IAB network.

[0020] Fig. 7A An example of header information used for differentiated services is shown.

[0021] Figure 7B An example of a UE having connections with a primary node and a secondary node is shown.

[0022] Figure 7C Example components and an IAB donor node are shown.

[0023] Figure 8 An example of downlink packet processing in an IAB network is shown.

[0024] Fig. 9 An example of uplink packet processing in an IAB network is shown.

[0025] Fig. 10A An example IAB network is shown in which an IAB node has dual connectivity to multiple IAB donor nodes.

[0026] Fig. 10B Shown for combining Fig. 10A An example communication flow of dual connectivity is described.

[0027] Fig.11A An example of an IAB network with a redundant topology is shown.

[0028] Fig. 11B An example communication flow including a BAP configuration associated with a topology identifier is shown.

[0029] Fig.12 is a schematic diagram showing traffic associated with a topology identifier transmitted over an IAB network having a redundant topology.

[0030] Fig.13 is a flow chart of a method of wireless communication.

[0031] Fig.14 is a diagram illustrating an example of a hardware implementation for an example apparatus.

[0032] Fig.15A and 15B is a flow chart of a method of wireless communication.

[0033] Fig.16 is a schematic diagram illustrating an example of a hardware implementation for an example apparatus. DETAILED DESCRIPTION

[0034] The specific embodiments described below in conjunction with the accompanying drawings are intended to be descriptions of various configurations and are not intended to represent the only configurations in which the concepts described herein can be practiced. For the purpose of providing a comprehensive understanding of each concept, the specific embodiments include specific details. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in the form of block diagrams to avoid obscuring such concepts.

[0035] Several aspects of telecommunication systems will now be presented with reference to various devices and methods. These devices 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.

[0036] 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, threads of execution, processes, functions, etc.

[0037] 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 computer-readable media of the above types, or any other medium that can be used to store computer executable code that can be accessed by a computer in the form of instructions or data structures.

[0038] 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 various aspects described in this article 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 various scopes of application of the various aspects described. Implementation can 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) equipment or systems incorporating one or more aspects of the various aspects described. 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 multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The aspects described herein are intended to be implemented in various devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc., having different sizes, shapes, and configurations.

[0039] Figure 1 1 is a schematic 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.

[0040] 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 also perform one or more of the following functions: transmission 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 delivery of warning messages. Base stations 102 may communicate with each other directly or indirectly (eg, through EPC 160 or core network 190) over a third backhaul link 134 (eg, an X2 interface). First backhaul link 132, second backhaul link 184, and third backhaul link 134 may be wired or wireless.

[0041] The base station 102 can communicate wirelessly with the UE 104. Each of the base stations 102 can provide communication coverage for a corresponding 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 both 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 to 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, which includes spatial multiplexing, beamforming and / or transmit diversity. The communication link may be through one or more carriers. The base station 102 / UE 104 may use a spectrum of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier allocated in a carrier aggregation 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 to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated 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).

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

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

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

[0045] 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). The frequencies between FR1 and FR2 are typically referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is typically (interchangeably) referred to as the "sub-6 GHz" band in various documents and articles. Similar naming issues sometimes arise regarding FR2, which is typically (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), and the EHF band is identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0046] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands of 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 can therefore 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 above 52.6GHz. For example, three higher operating bands have been identified as the frequency range names FR2-2 (52.6GHz–71GHz), FR4 (71GHz–114.25GHz), and FR5 (114.25GHz–300GHz). Each of these higher frequency bands falls within the EHF band.

[0047] 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 broadly represent frequencies 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 broadly represent frequencies that can include mid-band frequencies, can be within FR2, or can be within the EHF band.

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

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

[0050] 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 to 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 distribute MBMS services to base stations 102 belonging to a multicast broadcast single frequency network (MBSFN) area broadcasting a particular service, and may be responsible for session management (start / stop) and for collecting eMBMS-related billing information.

[0051] The core network 190 may include an access and mobility management function (AMF) 192, other AMFs 193, a session management function (SMF) 194, and a user plane function (UPF) 195. The AMF 192 may communicate with a unified data management unit (UDM) 196. The AMF 192 is a control node that handles 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 UE IP address allocation and other functions. 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.

[0052] A base station may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver station, a 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. The base station 102 provides an access point to the EPC 160 or the core network 190 for the UE 104. Examples of UE 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio unit, 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 the UEs 104 may be referred to as IoT devices (e.g., a parking meter, a gas pump, an oven, a vehicle, a heart monitor, etc.). UE 104 may also be referred to 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.

[0053] In some examples, the IAB node 103 may include a topology identifier component 198 configured to receive a first BAP configuration associated with a first topology corresponding to a first topology and a second BAP configuration associated with a second topology corresponding to a second topology that at least partially overlaps with the first topology. The topology identifier component 198 of the IAB node 103 may be configured to determine whether the traffic is associated with the first topology or the second topology, and to route the traffic associated with the first topology based on the first BAP configuration, and to route the traffic associated with the second topology based on the second BAP configuration. The IAB donor CU (e.g., base station 102 or 180 or other IAB node) may include a topology identifier component 199 configured to determine a BAP configuration associated with backhaul traffic transmission, the BAP configuration including a topology identifier corresponding to a topology in a plurality of topologies, for which traffic associated with the topology is transmitted based on the BAP configuration. The topology identifier component 199 may also be configured to send the BAP configuration associated with backhaul traffic transmission to the first network node.

[0054] Although aspects described below 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.

[0055] Figure 2A is a diagram 200 showing an example of a first subframe within a 5G NR frame structure. Figure 2B is a schematic diagram 230 showing an example of DL channels within a 5G NR subframe. Figure 2C is a diagram 250 showing an example of a second subframe within a 5G NR frame structure. Figure 2D 280 is a diagram showing an example of UL channels 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), a subframe within a subcarrier set is dedicated to either DL or UL), or can be time division duplex (TDD) (wherein, for a particular set of subcarriers (carrier system bandwidth), a subframe within a subcarrier set is dedicated to both DL and UL). Figure 2A , 2C In the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having 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 configured by DL control information (DCI) or semi-statically / statically configured by radio resource control (RRC) signaling) through the received slot format indicator (SFI). It should be noted that the following description also applies to the 5G NR frame structure as TDD.

[0056] Figures 2A-2DThe 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).

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

[0058] 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).

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

[0060] As in 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).

[0061] 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 identification. 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) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as 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 (such as a system information block (SIB)), and paging messages.

[0062] As in Figure 2CAs shown in , some of the REs carry DM-RS for channel estimation at the base station (indicated as R for a 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 depending on the specific PUCCH format used. 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. The SRS may be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

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

[0064] Figure 3 310 is a block diagram of a first wireless device communicating with a second wireless device. For example, the first wireless device 310 may be a base station in an access network that communicates with a UE (e.g., wireless device 350). In some examples, the first wireless device 310 may be an IAB node that communicates with the UE (e.g., wireless device 350). In other examples, the first device may be a parent IAB node (e.g., IAB node DU), and the second wireless device may be a child IAB node (e.g., IAB node MT). In some examples, the first wireless device may be an IAB donor, and the second wireless device may be an IAB node. In some examples, the first wireless device may be an IAB donor, and the second wireless device may be an IAB donor.

[0065] although Figure 3The various aspects are described in conjunction with a base station and a UE, but these concepts can be applied to communications between other wireless devices. In the DL, IP packets from the EPC 160 can be provided to the 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), MAC Demultiplexing of SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0066] 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 of 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)). The coded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time domain and / or frequency domain, and then combined 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 channel estimator 374 can be used to determine coding and modulation schemes and for spatial processing. Channel estimates can be derived based on reference signals and / or channel condition feedback sent by device 350. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX can modulate a radio frequency (RF) carrier with a corresponding spatial stream for transmission.

[0067] At the device 350, each receiver 354RX receives a signal through its corresponding antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functions associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for the device 350. If multiple spatial streams are destined for the device 350, they can be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then uses a fast Fourier transform (FFT) to convert 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 wireless device 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 the wireless device 310. The data and control signals are then provided to the controller / processor 359, which implements layer 3 and layer 2 functionality.

[0068] 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, packet reassembly, decryption, header decompression, and control signal processing between transport channels and logical channels 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.

[0069] Similar to the functions described in conjunction with DL transmissions performed by the wireless device 310, the controller / processor 359 provides: RRC layer functions associated with the following: system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functions associated with the following: header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions 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 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.

[0070] Channel estimates derived by the channel estimator 358 based on a reference signal or feedback transmitted by the wireless device 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 corresponding spatial stream for transmission.

[0071] UL transmissions are processed at the wireless device 310 in a manner similar to that described in conjunction with the receiver functionality at the device 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 the RX processor 370.

[0072] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets from the device 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.

[0073] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform operations related to Figure 1 Various aspects related to the topology identifier component 198.

[0074] 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 Various aspects related to the topology identifier component 199.

[0075] Figure 4 is a schematic diagram showing an IAB network 400. The IAB network provides access network functions between an access node (AN) 420 and other ANs / UEs and backhaul network functions between ANs 420. AN 420 includes an IAB donor and an IAB node, the IAB donor may have a wired connection to a core network, the IAB node operates wirelessly and relays services to / from the IAB donor through one or more AN hops. The IAB AN 420 shares resources between access links and backhaul links. That is, resources (e.g., in time and frequency) used for access communications between AN 420 and other ANs 420 and / or between AN 420 and UE 430 may also be used for backhaul communications between ANs.

[0076] The IAB network 400 may include an anchor node (which may be referred to herein as an "IAB donor") 410 and an access node (which may be referred to herein as an "IAB node") 420. The IAB donor 410 may be a base station (e.g., Figure 1 102 or 180 in the core network 490), and can perform functions for controlling the IAB network 400. In some aspects, the IAB donor 410 can be an eNB or a gNB. The IAB node 420 can include an L2 relay node, etc. The IAB donor 410 and the IAB node 420 share resources together to provide an access network and a backhaul network to the core network 490. For example, resources can be shared between access links and backhaul links in the IAB network.

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

[0078] Each IAB node (e.g., including the IAB donor 410 and each IAB node 420) may use a PCI value. The PCI value may be used as an identifier of the IAB donor 410 or the IAB node 420. The PCI value may be used to determine a scrambling sequence applied to a physical signal and / or channel sent by a particular IAB node. For example, a PSS and / or SSS sent by a corresponding IAB donor 410 or an IAB node 420 may be scrambled using a scrambling sequence based on the PCI used by the corresponding IAB node.

[0079] Figure 5 A second schematic diagram of an IAB network 500 and its components is shown. The IAB network 500 includes an IAB donor 510 and IAB nodes 520a and 520b. The IAB nodes and the IAB donor can provide wireless access links to UEs 530a, 530b, 530c.

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

[0081] The IAB donor 510 may include a central unit (CU) and a distributed unit (DU). The central unit CU may provide control for the IAB nodes 520a, 520b in the IAB network 500. For example, the CU may control the IAB network 500 by configuration. The CU may perform RRC / PDCP layer functions. The IAB donor 510 also includes a DU that performs scheduling. For example, the DU may schedule resources for communication by the child IAB node 520a and / or the UE 530a of the IAB donor 510. The DU maintains radio link control (RLC), medium access control (MAC), and physical (PHY) layer functions.

[0082] The IAB nodes 520a, 520b may include a mobile terminal (MT) and a DU. The IAB node is an L2 relay node. The MT of the IAB node 520a may operate as a scheduled node scheduled by the DU of the parent node (e.g., the IAB donor 510) similarly to the UE 530a. The MT of the IAB node 520b may operate as a scheduled node of the parent node 520a. The DU may schedule a child IAB node 520b and a UE 530b of the IAB node 520a. The IAB node may provide a connection to an IAB node, which in turn provides a connection to another IAB node. The pattern of the parent IAB node including the DU scheduling the child IAB node / child UE may continue to have the same Figure 5 There are many more connections than shown.

[0083] Figure 6 6 is a schematic diagram showing RLC channels in an IAB network. Figure 4 and 5 As discussed, the IAB network provides both access network functions and backhaul network functions. The IAB network includes an IAB donor having a CU 602 and a DU 604. For access network functions, IAB ANs 606a, 606b, and 606c can communicate with other UEs 608a and 608b and / or MTs of other IAB ANs via access RLC channels. For backhaul network functions, IAB ANs 606a, 606b, and 606c can route services to other ANs (e.g., 606a, 606b, and 606c) via backhaul RLC channels. Access RLC channels may 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 may include MT to DU / DU to MT, which carries a backhaul adaptation protocol (BAP) message for backhaul access services.

[0084] Differentiated services can provide a framework and building blocks to enable scalable service differentiation to be deployed on the Internet. In the packet forwarding path, differentiated services (DS) can be implemented by including fields in the Internet Protocol (IP) packet header (e.g., Fig. 7A This is achieved by mapping the Differentiated Services Code Point (DSCP) in the DS field (field shown in the example header information 700 in the DS field) to a specific forwarding treatment or per-hop behavior (PHB) at each AN along its path. The six bits of the DS field are used as the DSCP to select the PHB that the packet experiences at each node. The two-bit CU field can be reserved. The DSCP field can be defined as an unstructured field to facilitate the definition of future per-hop behaviors. The mapping of DSCP to PHB can be configurable. DS-compliant nodes can support the logical equivalent of a configurable mapping table from DSCP to PHB.

[0085] The IP flow label field (referred to herein as the IP flow label) may include a 20-bit flow label field in an IP header (e.g., an IPv6 header) used by the AN to mark packets of a 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 intends to mark as a flow. An example definition of a flow for this purpose may be any set of packets carrying the same 5-tuple of {destination address, source address, protocol, destination port, source port}. There are situations where a complete 5-tuple for all packets is not easily available to the forwarding AN, particularly for segmented packets. In such a case, the flow may be defined by fewer IP header fields, typically using only a 2-tuple {destination address, source address}. The use of a triple of flow label, source address, and destination address fields enables efficient IP flow classification, in which only fixed-position IPv6 main header fields are used. Packets may be processed in a flow-specific manner. In order to implement flow label-based classification, the source node may assign each unrelated transport connection and application data stream to a new flow.

[0086] like Figure 7B As shown in example 725 in FIG. 1 , a UE 708 may be dual connected to a master node (MN) eNB 704 and a secondary gNB (IAB donor) 708 that manages 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 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, the master eNB (MeNB) 704 (also referred to as the MN-eNB) shall (if supported) use the IE to set the DSCP and / or flow label fields of downlink IP packets sent from the MeNB to a secondary node (SN) enhanced gNB (SN-en-gNB) 706 (serving the IAB) via a GTP tunnel indicated by the GTP tunnel endpoint IE for each requested E-UTRAN radio access bearer (E-RAB) configured as a MN-terminated split bearer / secondary cell group (SCG) bearer. 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.

[0087] For each requested DRB, if the QoS Mapping Information IE is included in the DL User Plane (UP) Parameters IE in the Bearer Association Setup / Modify Request message, the gNB CU for 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.

[0088] UE 708 may connect to the IAB network. Figure 7C An example 750 of a UE 708 connected in an IAB network is shown. An 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 downlink mappings at the donor DU, as described above. In some aspects, the IAB donor CU may configure IP header fields with DSCP / IPv6 flow labels 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, as described above. Figure 7C As shown. In such an aspect, the DRB flow between the CU-UP and the UE can be configured as described above. The CU-CP can perform bearer establishment for each DRB at the CU-UP. The CU-CP can configure QoS mapping information for each requested DRB at the CU-UP, as described above. The CU-UP can also configure IP header fields based on the QoS mapping information, as described above. The downlink mapping can be configured by the CU-CP at the donor DU, as described above.

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

[0090] Figure 8800 is a schematic diagram illustrating an IP / BAP configuration for downlink packet processing. As described above, an IAB donor CU (e.g., an IAB donor CU-UP) (e.g., an IAB donor 1 802a or an IAB donor 2 802b) inserts QoS mapping information within an IP packet, the QoS mapping information including a DSCP and an IP flow label. Based on the QoS mapping information, the IAB donor CU (e.g., an IAB donor CU-CP) configures a routing path for downlink mapping at the IAB donor DU. When the IAB donor DU receives an 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 a mapping between an IP header field (destination IP address, DCSP and / or IPv6 flow label) and a BAP route ID. The IAB donor DU inserts a BAP header into the packet carrying the BAP route identifier. The IAP donor DU also determines the egress link to which the IP packet is forwarded. For example, the IAP donor DU also determines a mapping between a BAP routing ID and an egress link based on the routing configuration, along which the IAB donor DU forwards the BAP packet. The IAB donor DU sends the BAP packet to the IAB node 1 804. The IAB node 1 804 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, the IAB node 1 804 determines the egress RLC channel. The IAB node 1 804 then sends the IP packet to the IAB node 4 806 via the determined link and egress RLC channel. The same process is followed for the IAB node 4 806 and the IAB node 5 808, where the IAB node 5 808 determines that the BAP address matches, removes the BAP header, and forwards the IP packet to upper layer processing for transmission to the UE 810.

[0091] Fig. 9900 is a schematic diagram showing an IP / BAP configuration for uplink packet processing. For UL services, based on the service type and the uplink mapping configuration, the IAB node 5 908 determines the BAP routing ID of the uplink packet from the UE 910 and inserts the BAP routing ID into the BAP header for the UL packet. Based on the BAP routing ID and the routing configuration, the IAB node 5 908 determines the egress link and determines the egress RLC channel based on the service type. The IAB node 5 908 sends the IP packet to the IAB node 4 906 based on the determined egress link and the egress RLC channel. The IAB node 4 906 determines the egress link based on the BAP routing ID and the routing configuration. The IAB node 4 906 determines the egress RLC channel based on the ingress RLC channel and the channel mapping configuration. The IAB node 4 906 sends the BAP packet to the IAB node 1 904 based on the determined egress link and the egress RLC channel. IAB Node 1 904 follows the same process and the IP packet is eventually received and processed by IAB Donor 902 where there is a BAP address match.

[0092] Fig. 10A A network diagram 1000 is shown showing an IAB donor CU 1 1006a and an IAB donor CU 2 1006, each having a connection to a parent IAB-DU or donor DU 1004 and connected to a child IAB node MT 1002. Thus, a parent IAB node 1004 (whether an IAB node or an IAB donor DU) and a child IAB node (e.g., node MT 1002) may have dual connections to both IAB donor CU 1 1006a and IAB donor CU 2 1006b. Fig. 10B An example communication flow 1050 is shown for providing BAP configuration between IAB donor CUs 1 and 2 (e.g., 1006a and 1006b) and IAB-DU 1 1004a and IAB-DU 2 1004b for directing communications to IAB-MT 1 1002a and IAB-MT 1002b, respectively. IAB donor CU1 1006a may send a request to IAB-DU1 1004a to configure a backhaul (BH) RLC channel between IAB-DU 1 1004a and IAB-MT1 1002a. IAB donor CU1 1006a may indicate a BH RLC CH ID 1010 for the BH RLC CH. IAB-DU1 1004a may configure the BH RLC CH at 1012 and select a corresponding unique LCID. The IAB-DU1 1004a may send a response at 1014 to CU1 1006a indicating the BH RLC CH ID and LCID of the configured channel.

[0093] The IAB donor CU1 1006a may also send an RRC message 1016 to configure the other end of the BH RLC CH at the IAB-MT 1002a. The IAB donor CU1 1006a may include both the BH RLC CH ID and the LCID of the CH to be configured in the RRC message.

[0094] At 1018, the IAB-MT 1002a responds to the IAB donor CU 1 1006a to indicate that the RRC reconfiguration is complete. The IAB donor CU 1 1006a then provides the BAP configuration 1020 to the IAB-DU 1 1004a to route and perform channel mapping for traffic transmitted on the configured BH RLC CH. Fig. 10B Not shown in the figure, the IAB donor CU 1 1006a can provide the IAB node 1002a with a second BAP configuration mapped to the traffic transmitted on the configured BH RLC CH. Since the IAB donor CU 1 1006a and the IAB donor CU 2 1006b are each connected to a corresponding logical parent IAB DU or donor DU 1004 and a child IAB MT 1002, the IAB donor CU2 1006b can follow a similar process to configure the second BH RLC CH between the IAB-DU2 1004b and the IAB-MT2 1002b, and then provide a separate BAP configuration to handle the traffic transmitted on the second BH RLC CH. The IAB donor CUs (e.g., 1006a and 1006b) each provide their own messages (e.g., 1010, 1016, 1020) to the IAB-DU. The parent IAB-DU 1004 selects a unique LCID across all BH RLC CHs configured (whether configured by IAB donor CU1 1006a or IAB donor CU2 1006b). This allows the IAB-DU 1004 and the IAB-MT 1002 to perform namespace differentiation based on the LCID, wherein the IAB-DU 1004 and the IAB-MT 1002 can resolve the BH RLC CH ID from the LCID even when the BH RLC CH IDs selected by the two CUs 1006a and 1006b conflict.

[0095] Fig.11AA network diagram 1100 is shown, which shows topological redundancy, wherein an IAB donor CU 11206a can be connected to an IAB donor CU2 1206, which has a connection to a parent IAB-DU or donor DU 1104 and is connected to a child IAB node MT 1102. The connection between IAB donor CU 1 1206a and IAB donor CU2 1206b provides topological redundancy for the IAB network. In some examples, the parent IAB node 1104 can have dual connections to IAB donor CU 1 1106a and IAB donor CU 2 1106b. The parent DU 1104 and the child MT 1102 can route the business associated with CU1 1106a (which can be F1-C, F1-U or non-F1 business). The parent DU 1104 and the child MT 1102 can also route the business associated with CU2 1106b. In contrast to FIG. 10 , the parent DU 1104 and child MT 1102 may receive configuration only from CU2 1106 b , whether to process and route traffic associated with CU1 1106 a or CU2 1106 b . Fig. 11B An example communication flow 1150 is shown for providing BAP configuration between an IAB donor CU 2 1006b and an IAB-DU2 1104 for directing communications to an IAB-MT 2 1102, respectively. As an example, the IAB donor CU 2 1106b may route F1-U traffic (for itself or for the IAB donor CU1 1106a) via the IAB-DU 2 1104. The IAB donor CU 2 1106b may configure a BH RLC CH between the parent IAB-DU2 1104 and the child IAB-MT2 1102, and indicate, for example, at 1110, a backhaul RLC channel ID and a topology identifier (ID) for communication. The BH RLC CH may be configured to carry traffic associated with CU1 1106a or CU2 1106b. The parent IAB-DU2 1104 may be able to determine which CU the traffic transmitted on the BH RLC CH is associated with. Although in FIG. 10 , the parent IAB-DU 1004 may determine this implicitly, where it associates the BH RLC channel with the CU from which it received the configuration message, e.g., if it receives the configuration message from CU1 1006a, it associates the BH RLC CH with CU1 1006b, and if it receives the configuration message from CU2 1006b, it associates the BH RLC CH with CU2 1006b. Fig. 10B On the contrary, Fig. 11BIn the embodiment, the parent IAB-DU 1004 receives a configuration message for a BH RLC CH from CU2 1006b, regardless of whether the CH carries traffic associated with CU1 1006a or CU2 1006a. For this reason, CU2 includes a topology identifier in the message 1010 along with the BH RLC CHID to indicate the association of the configured BH RLC CH with a specific CU, which may be different from the CU providing the message to the IAB DU.

[0096] IAB-DU 2 1104 selects a unique LCID at 1112 similar to Fig. 10B . The IAB-DU 2 1104 sends a response indicating the backhaul RLC channel ID and LCID to the IAB donor CU 2 1106b at 1114. Although not shown in the figure, the IAB-DU2 1104 may also include a corresponding topology identifier. The IAB donor CU 2 1106b then sends an RRC message 1116 indicating the backhaul RLC channel ID, LCID, and topology identifier to the IAB-MT 1102b. CU2 1106b may include a topology identifier to enable the child node 1102 to create an association between the configured BH RLC CH and the topology associated with the service transmitted on the BH RLC CH. At 1118, the IAB-MT 1102b responds to the IAB donor CU 2 1106b to indicate that the RRC reconfiguration is complete. By including the topology identifier in messages 1110 and 1116, the two BH RLC CHs of CU1 and CU2 that carry the associated traffic can carry the same CH ID, but the parent IAB-DU 1104 and the child IAB-MT2 1102 will still be able to resolve the traffic transmitted on the two channels based on their association with different topology IDs. The IAB donor CU 2 1106b then provides the BAP configuration 1120 to the IAB-DU 2 104 or IAB-MT2 1102 (not shown in the figure). The IAB donor CU2 1106b can include the topology identifier in the BAP configuration. The parent IAB-DU 1104 and the child IAB-MT2 1102 can use the corresponding BAP configuration associated with the first topology ID to process and route the traffic transmitted on the BH RLC CH associated with the first topology ID. The parent IAB-DU 1104 and the child IAB-MT2 1102 may also process and route traffic transmitted on the BH RLC CH associated with the second topology ID using the corresponding BAP configuration associated with the second topology ID. The IAB donor CU 2 1106b may provide its own message to the IAB-DU or may provide a message for the IAB donor CU 1 1106a.

[0097] Fig.12 An example topology redundancy 1200 for IAB donors (eg, IAB donors 1202 and 1204) is shown, similar to the combination of Fig.11A and 11B The topology described is redundant. An IAB node can be connected to one or more IAB donors. Fig.12 As shown in FIG. 1 , the IAB-MT1 of the IAB node 1 1208 may be dually connected to the CU1 of the IAB donor 1 1202 and the CU2 of the IAB donor 2 1204. The IAB-DU1 of the IAB node 1 1208 may be connected to the CU2 of the IAB donor 2 1204. The child nodes of the IAB node 1 (such as the IAB node 2 1212) may be connected to the CU1 of the IAB donor 1 1202. The IAB node 3 1206 may be connected to the CU2 of the IAB donor 2 1204. The CU1 of the IAB donor 1 1202 may route the F1-U traffic on the secondary path via the donor DU associated with the CU2 of the IAB donor 2 1204 to facilitate load balancing or redundancy between the IAB donors. As shown in FIG. Fig.11A and 11B As described, the BAP configuration may include an associated topology identifier. The IAB node may use the topology identifier associated with the service to process the service based on the corresponding BAP configuration. Fig.12 It shows that there may be overlapping topologies.

[0098] Fig.12 An example of a first routing path is shown that carries traffic between CU1 1202 and IAB Node 2 1212 and extends along the path over donor DU 2 of donor 1204 , IAB Node 3 1206 , and IAB Node 1 1208 . Fig.12 An example of a second routing path is shown that carries traffic between CU2 1204 and IAB Node 4 1210 and extends along the path over donor DU2 of donor 1204 and IAB Node 3 1206 .

[0099] exist Fig.12 In the example of FIG. 1 , the first routing path and the second routing path may have the same BAP routing ID ( Fig.12 Thus, for example, traffic received by IAB Node 3 1206 from donor DU2 may carry the same routing ID = Y, whether the traffic corresponds to a first path and is to be routed left to IAB Node 1, or corresponds to a second path and is to be routed right to IAB Node 2.

[0100] Additionally, both traffic blocks may indicate (as part of the BAP routing ID) the same destination BAP address (eg, BAP address = 2 for IAB Node 2 1212, and BAP address = 2 for IAB Node 4 1210).

[0101] In addition, IAB Node 3 1206 may receive traffic associated with the first routing path from donor DU2 on the first BH RLC CH, and receive traffic associated with the second routing path from donor DU2 on the second BH RLC CH. Fig.12 As shown, two BH RLC channels may carry the same CH ID (eg, ID=3).

[0102] However, as described in FIG11 , when two CHs are configured, these CHs may be associated with different topology identifiers. Fig.12 In the example of , the first BH RLC CH is associated with topology identifier = 1, and the second BH RLC CH is associated with topology identifier = 2. For the traffic transmitted between IAB Node 3 1206 and donor DU2, the traffic can be differentiated based on BAP routing ID (wherein the topology identifier can be a part of the BAP routing ID) or BH RLC CH ID or LCID. Fig.12 In the example and similar to Figure 11, each LCID can be selected so that it is associated with a topology identifier. For example, one BH RLC CH between the IAB node 3 1206 and the donor DU2 has LCID=1 and can be associated with the topology ID=1, while the other BH RLC CH has LCID=2 and can be associated with the topology ID=2. In this way, when the IAB node 3 receives a packet carrying LCID=1 from the donor DU2, the IAB node 3 associates the packet with the topology ID=1, and thus the packet can be routed based on the BAP configuration associated with the topology ID=1. Similarly, when the IAB node 3 receives a packet carrying LCID=2 from the donor DU2, the IAB node 3 associates the packet with the topology ID=2, and the packet is routed using the BAP configuration associated with the topology ID=2. Therefore, services associated with two routing paths can be correctly transmitted across overlapping topologies. Similar examples are applied at other IAB nodes. When the IAB node 1 is connected to the IAB node 3 alone, and the traffic flows across different topological parts to the UE and MT under the IAB node 3 associated with CU1, a similar scenario also holds true.

[0103] As combined Fig.11A and 11BAs described, the various aspects provided herein facilitate the donor CU to improve communication by providing a BAP configuration, the BAP configuration including a topology identifier corresponding to a topology, for which a service associated with the topology is transmitted based on the configuration. The IAB donor CU sends a BAP configuration associated with IAB backhaul service transmission to an IAB node or an IAB donor DU. The IAB node 1104 may ACK the BAP configuration and include a topology identifier in the ACK message. The IAB node 1104 may receive the BAP configuration 1120 on F1-C or RRC.

[0104] When sending a service, the IAB donor CU may indicate the topology identifier of this type to the IAB node. Fig. 11B , the IAB donor CU 2 1106b sends traffic 1122 along with an indication of the corresponding topology ID. At 1124, the IAB-DU 1104 determines the BAP configuration corresponding to the topology ID. The IAB-DU 1104 processes the traffic 1126 using the corresponding BAP configuration associated with the topology ID.

[0105] The BAP configuration 1120 may include a BAP address configuration for an IAB node or an IAB donor DU. The BAP configuration 1120 may include establishing a BH RLC CH at an IAB node MT. The BAP configuration 1120 may include establishing a BH RLC CH at an IAB node DU or an IAB donor DU. The BAP configuration 1120 may include a modification to the BH RLC CH. The BAP configuration 1120 may include an uplink mapping configuration between an upper layer service type or IP header field and a BAP routing ID at an IAB node, an egress link (next hop BAP address), or an egress BH RLCCH. The BAP configuration 1120 may include a downlink mapping configuration between an IP header field and a BAP routing ID at an IAB donor DU or an IAB node, an egress link (next hop BAP address), or an egress BH RLC CH. The BAP configuration 1120 may include a BH RLC CH mapping configuration between an ingress BH RLC CH and an egress BH RLC CH. The IAB donor CU may provide a topology identifier included as part of the BAP routing ID. The IAB donor CU may provide a topology identifier as part of the BH RLC CH.

[0106] The IAB donor CU (eg, 1106b) may indicate to the IAB node 1104 a topology identifier of a traffic type (eg, F1-C signaling, F1-U tunnel, non-F1, etc.) at the IAB node.

[0107] The IAB node 1104 (e.g., whether an IAB donor DU or an IAB-DU) can receive multiple BAP configurations, each BAP configuration carrying a topology identifier. For example, the IAB node 1104 can receive a first BAP configuration carrying a first topology identifier corresponding to a first topology, and can receive a second BAP configuration carrying a second topology identifier corresponding to a second topology. The IAB node 1104 processes the service according to the corresponding BAP configuration 1120 associated with the topology identifier. For example, the IAB node 1104 uses the first BAP configuration to process the service associated with the first topology, and uses the second BAP configuration to process the service associated with the second topology. The topology identifier can be part of the BAP routing ID. For example, the IAB node or IAB donor DU (e.g., 1104) can also transmit a packet carrying a BAP routing ID with a first topology identifier. The IAB node or IAB donor DU 1104 processes the packet as a service associated with the first topology corresponding to the first topology identifier.

[0108] The IAB node 1104 may receive a first topology identifier of a service type (e.g., F1-C signaling, F1-U tunnel, non-F1) at the IAB node. The IAB node 1104 processes the service as a service associated with the first topology. In some examples, a specific service type (e.g., F1-C signaling, F1-U tunnel, non-F1) at the IAB node may default to a specific topology identifier, e.g., a first topology identifier. As a non-limiting example, a service type associated with a first IAB donor CU (e.g., IAB donor CU11106a) may default to a first topology identifier. Other service types may similarly default to specific topology identifiers. As another example, a service that communicates with a first IAB donor CU (e.g., IAB donor CU1006a) via an IAB donor DU 1104 may default to a first topology identifier.

[0109] The IAB node DU or IAB donor DU (e.g., 1104) may configure a first BH RLC CH based on a BAP configuration with a first topology identifier. The IAB node DU or IAB donor DU may allocate a first LCID corresponding to the first BH RLC CH, as shown at 1112. The IAB node DU or IAB donor DU 1104 may also transmit a packet (e.g., service 1122 / 1126) carrying a first LCID (e.g., an LCID associated with a first topology and a first BAP configuration). The IAB node DU or IAB donor DU 1104 processes the packet as a service associated with a first topology corresponding to the first topology identifier. The IAB node DU or IAB donor DU 1104 may set a portion of the first LCID (e.g., the LCID selected at 1112) to the first topology identifier.

[0110] although Fig. 11B The aspects in the present invention illustrate a downlink example, but the downlink example is only used to illustrate the concept. The aspects presented herein can be applied to uplink communications.

[0111] The IAB node MT 1102 may configure a first BH RLC CH based on the BAP configuration (e.g., 1120) with the first topology identifier. The IAB node MT 1102 may receive, for example, at 1116, a first LCID allocated for the first BH RLC CH. The IAB node MT 1102 may also transmit a packet carrying the first LCID. The IAB node MT 1102 processes the packet as a service associated with the first topology corresponding to the first topology identifier.

[0112] The IAB node 1104 may receive a downstream packet associated with the first topology (e.g., included in service 1122) and, if the packet carries a destination BAP address that matches a BAP address assigned to the IAB node via a BAP address configuration in a BAP configuration having a first topology identifier, pass the packet to upper layer processing.

[0113] The IAB node 1104 may receive a downstream packet associated with the first topology (e.g., included in the traffic 1122), and may forward the packet on an egress link based on a BAP routing ID carried by the packet and a routing configuration received in a BAP configuration with the first topology identifier (e.g., if a destination BAP address carried by the packet does not match a BAP address assigned to the IAB node via a BAP address configuration in the BAP configuration with the first topology identifier). The IAB node 1104 may map the packet associated with the first topology to an egress BHRLC CH on an egress link based on an ingress BH RLC CH on which the IAB node receives the packet and a BH RLC CH mapping configuration received in a BAP configuration with the first topology identifier.

[0114] IAB node 1104 may receive an upstream packet associated with the first topology (eg, from IAB-MT 1102) and forward the packet on an egress link based on the BAP routing ID carried by the packet and the routing configuration received in the BAP configuration with the first topology identifier.

[0115] The IAB node 1104 may map packets associated with the first topology to an egress BH RLC CH on an egress link based on the ingress BH RLC CH on which the IAB node receives the packet and a BH RLC CH mapping configuration received in a BAP configuration with the first topology identifier.

[0116] The IAB node 1104 may receive a BAP SDU from an upper layer associated with the first topology and send a corresponding packet carrying a BAP routing ID based on the upper layer traffic type of the BAP SDU or IP header field and the uplink mapping configuration received in the BAP configuration with the first topology identifier.

[0117] The IAB node 1104 may send the packet on the egress link based on the selected BAP routing ID and the routing configuration received in the BAP configuration with the first topology identifier.

[0118] The IAB node 1104 may map the packet to the egress BH RLC CH on the egress link based on the upper layer traffic type or IP header field and the uplink mapping configuration received in the BAP configuration with the first topology identifier.

[0119] The IAB donor DU may receive a BAP SDU from an upper layer associated with the first topology and send a corresponding packet carrying a BAP routing ID based on the IP header field and the downlink mapping configuration received in the BAP configuration with the first topology identifier.

[0120] The IAB donor DU may send the packet on the egress link based on the selected BAP routing ID and the routing configuration received in the BAP configuration with the first topology identifier.

[0121] The IAB donor DU may map the packet to the egress BH RLC CH on the egress link based on the IP header fields and the downlink mapping configuration received in the BAP configuration with the first topology identifier.

[0122] The IAB donor DU may receive an upstream packet associated with the first topology and pass the packet to upper layer processing if the packet carries a destination BAP address matching a BAP address assigned to the IAB donor DU via a BAP address configuration in a BAP configuration having a first topology identifier.

[0123] Fig.13 1300 is a flow chart of a method of wireless communication. The method may be performed by a network node (e.g., base station 102 / 180, 350; IAB node 103; IAB donor CU 1 1106a or IAB donor CU2 1106b; device 1402). In some aspects, the network node may be referred to as a RAN node or a relay node. Fig.13 In the description of , the network node may be referred to as a second network node.

[0124] At 1302, the second network node determines a BAP configuration associated with backhaul traffic transmission, the BAP configuration including a topology identifier corresponding to a topology in a plurality of topologies, for which traffic associated with the topology is transmitted based on the BAP configuration. The determination of the BAP configuration may be performed, for example, by a BAP component 1440 of the apparatus 1402. The topology identifier may be a network node CU identifier of the second network node. The topology identifier may be at least one of a portion of a BAP route ID, a portion of a backhaul RLC channel ID, or a portion of a BAP address. The plurality of topologies may include a first topology and a second topology at least partially overlapping the first topology, wherein the first topology carries traffic associated with the second network node and the second topology carries traffic associated with a third network node. Fig.11A , 11B 12 show examples of different topologies associated with traffic in an IAB network.

[0125] At 1304, the second network node sends a BAP configuration associated with backhaul traffic transmission to the first network node. The transmission can be performed, for example, by the configuration component 1442 of the apparatus 1402. For example, Fig. 11BAn example is shown in which the IAB donor CU 21106b sends a BAP configuration 1120 including a topology identifier to the IAB node 1104. For the topology, the BAP configuration may include at least one of the following: a BAP address configuration for the first network node; establishing a backhaul RLC channel at the first network node; modifying the backhaul RLC channel at the first network node; an uplink mapping configuration between at least one of the service type or IP header field and the BAP route ID, the egress link at the first network node, or the egress backhaul RLC channel at the first network node; a downlink mapping configuration between the IP header field and the BAP route ID, the egress link at the first network node, or the egress backhaul RLC channel at the first network node; a routing configuration along the BAP route between the BAP route ID and the egress link at the first network node; or a backhaul RLC channel mapping configuration between the ingress backhaul RLC channel at the first network node and the egress backhaul RLC channel. The network node may also send information indicating the topology identifier of the service type to the first network node.

[0126] Fig.14 1400 is a schematic diagram illustrating an example of a hardware implementation for an apparatus 1402. The apparatus 1402 is a network node and includes a baseband unit 1404. The apparatus may be a base station, a component of a base station, or may implement base station functionality. The apparatus may be an IAB node, a component of an IAB node, or may implement IAB node functionality. In some aspects, the apparatus may be referred to as a RAN node or a relay node. In some aspects, the apparatus may be an IAB node, for example, an IAB donor CU, such as in conjunction with Fig.11A , 11B or 12. The baseband unit 1404 can communicate with the UE 104 via the cellular RF transceiver 1422. The baseband unit 1404 may include a computer-readable medium / memory. The baseband unit 1404 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When the software is executed by the baseband unit 1404, the baseband unit 1404 performs the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the baseband unit 1404 when executing the software. The baseband unit 1404 also includes a receiving component 1430, a communication manager 1432, and a sending component 1434. The communication manager 1432 includes one or more components shown. The components within the communication manager 1432 may be stored in a computer-readable medium / memory and / or configured as hardware within the baseband unit 1404. The baseband unit 1404 may be a component of the wireless device 310 and may include at least one of the TX processor 316 , the RX processor 370 , and the controller / processor 375 , and / or the memory 376 .

[0127] The communication manager 1432 includes a BAP component 1440 that determines a BAP configuration associated with backhaul traffic transmission, the BAP configuration including a topology identifier corresponding to a topology in a plurality of topologies, for which traffic associated with the topology is transmitted based on the BAP configuration, e.g., as described in conjunction with 1302. The communication manager 1432 also includes a configuration component 1442 that sends the BAP configuration associated with backhaul traffic transmission to the first network node, e.g., as described in conjunction with 1304. The communication manager 1432 may also include a topology identifier component 1444 that indicates a topology identifier associated with the BAP configuration, e.g., as described in conjunction with Figure 11A-13 any diagram described in FIG.

[0128] The apparatus may include executing Fig.13 Flowchart or Fig. 10B and / or additional components of each block in the algorithm of the communication flow of 11B. Thus, the components may be executed Fig.13 Flowchart or Fig. 10B Each block in the communication flow of 11B and / or 11B, and the device may include one or more of those components. The component may be one or more hardware components specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0129] As shown, the device 1402 may include various components configured for various functions. In one configuration, the device 1402 (specifically, the baseband unit 1404) includes: a unit for determining a BAP configuration associated with backhaul service transmission, the BAP configuration including a topology identifier corresponding to a topology in a plurality of topologies, for which a service associated with the topology is transmitted based on the BAP configuration; and a unit for sending the BAP configuration associated with backhaul service transmission to the first network node. The unit may be one or more components of the components of the device 1402 configured to perform the functions recorded by the unit. As described above, the device 1402 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.

[0130] Fig.15A 1500 is a flow chart of a method of wireless communication. The method may be performed by a network node (eg, base station 102 / 180, 350; IAB node 103; IAB node 1104; apparatus 1402). In some aspects, the network node may be referred to as a RAN node or a relay node.

[0131] At 1502, a first network node receives a first BAP configuration associated with a first topology identifier corresponding to a first topology and a second BAP configuration associated with a second topology ID corresponding to a second topology that at least partially overlaps with the first topology. In some aspects, the first BAP configuration can be associated with the first topology ID for the first topology, and the second BAP configuration can be associated with the second topology ID for the second topology. Receiving the BAP configuration can be performed, for example, by a BAP configuration component 1640 of the apparatus 1602. For the corresponding first topology and second topology, each of the first BAP configuration and the second BAP configuration may respectively include at least one of the following: BAP address configuration for the first network node; establishing a backhaul RLC channel at the first network node; modifying the backhaul RLC channel at the first network node; uplink mapping configuration between at least one of the service type or IP header fields and the BAP route ID, the egress link at the first network node, or the egress backhaul RLC channel at the first network node; downlink mapping configuration between the IP header field and the BAP route ID, the egress link at the first network node, or the egress backhaul RLC channel at the first network node; routing configuration along the BAP route between the BAP route ID and the egress link at the first network node; or a backhaul RLC channel mapping configuration between the ingress backhaul RLC channel at the first network node and the egress backhaul RLC channel. At least one of the first BAP configuration or the second BAP configuration may be received via at least one of an RRC signal or F1-C signaling. Fig. 11B An example is shown where the IAB node 1104 receives a BAP configuration 1120 that includes a topology identifier.

[0132] A service that can be associated with a first topology can be associated with a second network node, and a service associated with a second topology can be associated with a third network node. The service can be associated with the first topology or the second topology based on a default value of a service type of the service. In some aspects, the service can be associated with a first topology ID or a second topology ID based on a default value of a service type of the service. The service type can be at least one of F1-C signaling, F1-U tunnel, or non-F1 service. When the service is transmitted with the second network node, the service can be associated with the first topology by default, and when the service is transmitted with the third network node, the service can be associated with the second topology by default. In some aspects, when the service is transmitted with the second network node, the service can be associated with the first topology ID by default, and when the service is transmitted with the third network node, the service can be determined to be associated with the second topology ID by default. The first topology ID can be a network node CU identifier of the second network node, and the second topology ID is a network node CU identifier of the third network node. Each of the first topology ID and the second topology ID can be at least one of the following: a portion of a BAP routing ID, a portion of a backhaul RLC channel ID, or a portion of a BAP address.

[0133] At 1506, the first network node routes traffic associated with the first topology based on the first BAP configuration and routes traffic associated with the second topology based on the second BAP configuration. The routing may be performed, for example, by a routing component 1642 of the apparatus 1602. In some aspects, the network node may route traffic associated with the first topology ID based on the first BAP configuration and route traffic associated with the second topology ID based on the second BAP configuration. Fig. 11B An example of an IAB node processing a service based on a BAP configuration is shown, and Fig.12 An example of an IAB node routing traffic based on different topologies is shown. For example, routing traffic associated with a first topology based on a first BAP configuration and routing traffic associated with a second topology based on a second BAP configuration may include sending a packet within information indicating whether the packet is associated with the first topology (e.g., a first topology ID) or the second topology (e.g., a second topology ID).

[0134] In some aspects, routing services at 1506 may include: receiving a downstream packet associated with a first topology ID; and passing the packet to upper layer processing when the packet carries a destination BAP address that matches a BAP address assigned to the first network node via a BAP address configuration in a first BAP configuration having the first topology ID.

[0135] As another example, at 1506, routing traffic may include: receiving a downstream packet associated with a first topology ID; and forwarding the packet to an egress link based on the BAP routing ID carried by the packet and the routing configuration received in the first BAP configuration with the first topology ID when the destination BAP address carried by the packet does not match the BAP address assigned to the first network node via the BAP address configuration in the third BAP configuration with the first topology ID. The routing traffic may include: mapping the packet associated with the first topology ID to an egress backhaul RLC channel on the egress link based on the ingress backhaul RLC channel on which the first network node receives the packet and based on the backhaul RLC channel mapping received in the fourth BAP configuration with the first topology ID.

[0136] As another example, routing traffic at 1506 may include: receiving an upstream packet associated with a first topology ID; and forwarding the packet to an egress link based on a BAP routing ID carried by the packet and a routing configuration received in a first BAP configuration having the first topology ID. Routing traffic at 1506 may include: mapping the packet associated with the first topology ID to an egress backhaul RLC channel on the egress link based on an ingress backhaul RLC channel on which the first network node receives the packet and based on a backhaul RLC channel mapping received in a third BAP configuration having the first topology ID.

[0137] As another example, routing the traffic at 1506 may include: receiving a BAPSDU associated with a first topology ID; and sending a corresponding packet carrying the BAP routing ID based on a traffic type or IP header field of the BAP SDU and based on an uplink mapping configuration received in a first BAP configuration with the first topology ID. The packet may be sent on an egress link based on the BAP routing ID and a routing configuration received in a third BAP configuration with the first topology ID. The packet may be mapped to an egress backhaul radio link control (RLC) channel on the egress link based on a traffic type or IP header field and based on an uplink mapping configuration received in a fourth BAP configuration with the first topology ID.

[0138] As another example, routing traffic at 1506 may include: receiving a BAPSDU associated with a first topology ID; and sending a corresponding packet carrying the BAP routing ID based on an IP header field and a downlink mapping configuration received in a first BAP configuration with the first topology ID. The packet may be sent on an egress link based on the BAP routing ID and a routing configuration received in a third BAP configuration with the first topology ID. The packet may be mapped to an egress backhaul radio link control (RLC) channel on the egress link based on an IP header field and based on a downlink mapping configuration received in a fourth BAP configuration with the first topology ID.

[0139] As another example, routing services at 1506 may include: receiving an upstream packet associated with a first topology ID; and passing the packet to upper layer processing when the packet carries a destination BAP address that matches a BAP address assigned to the first network node via a BAP address configuration in a first BAP configuration having the first topology ID.

[0140] Fig. 15B It is shown that it can include such as combining Fig.15A 1502 and 1506 of the method of wireless communication described in the flowchart 1550. In some aspects, at 1504, the first network node can also determine whether the traffic is associated with the first topology or the second topology. In some aspects, the network node can determine whether the traffic is associated with the first topology ID or the second topology ID. The determination can be performed, for example, by the topology identifier component 1644 of the device 1602. Fig. 11BIt is shown that the IAB node 1104 determines, for example, a BAP configuration based on a topology identifier associated with a service. A service associated with a first topology may be associated with a second network node, and a service associated with a second topology may be associated with a third network node. The first topology ID may be a network node CU identifier of the second network node, and the second topology ID may be a network node CU identifier of the third network node. Each of the first topology ID and the second topology ID may be at least one of the following: a portion of a BAP routing ID, a portion of a backhaul RLC channel ID, or a portion of a BAP address. The service may be determined to be associated with the first topology or the second topology based on a default value of a service type of the service. In some aspects, the service may be determined to be associated with the first topology ID or the second topology ID based on a default value of a service type of the service. The service type may be at least one of F1-C signaling, F1-U tunnel, or non-F1 service. When transmitting a service with the second network node, the service may be determined to be associated with the first topology by default, and when transmitting a service with the third network node, the service may be determined to be associated with the second topology by default. In some aspects, when communicating traffic with the second network node, the traffic may be determined to be associated with the first topology ID by default, and when communicating traffic with the third network node, the traffic may be determined to be associated with the second topology ID by default.

[0141] As shown at 1503, the first network node may receive information indicating that at least one of the first topology ID or the second topology ID is associated with a particular traffic type, wherein the traffic is routed based on the received information at 1506. The receiving may be performed, for example, by a topology identifier component 1644 of the apparatus 1602. For example, the traffic type may be at least one of F1-C signaling, F1-U tunneling, or non-F1 traffic.

[0142] As shown at 1508, the first network node can configure a first backhaul RLC channel based on the first BAP configuration with the first topology ID. The configuration can be performed, for example, by the BH RLC CH component 1646 of the apparatus 1602.

[0143] As shown at 1510, the first network node may allocate a first LCID corresponding to the first backhaul RLC channel. The allocation may be performed, for example, by an allocation component 1648 of the apparatus 1602. Routing the traffic at 1506 may include transmitting a packet including the first LCID corresponding to the first backhaul RLC channel, transmitting the packet including processing the packet as traffic associated with the first topology corresponding to the first topology ID. For example, at least a portion of the first LCID may be allocated to include the first topology ID.

[0144] As shown at 1510, the first network node may receive a first LCID assigned for a first backhaul RLC channel. The receiving may be performed, for example, by an LCID component 1650 of the apparatus 1602. Routing the traffic at 1506 may include transmitting a packet including the first LCID corresponding to the first backhaul RLC channel, transmitting the packet including processing the packet as traffic associated with a first topology corresponding to the first topology ID.

[0145] As shown at 1512, the first network node can send an acknowledgement to acknowledge receipt of at least one of the first BAP configuration or the second BAP configuration, the acknowledgement including at least one of the first topology ID or the second topology ID. The transmission can be performed, for example, by feedback component 1652 of apparatus 1602.

[0146] Fig.16 1600 is a diagram illustrating an example of a hardware implementation for an apparatus 1602. The apparatus 1602 is a network node and includes a baseband unit 1604. The apparatus may be a base station, a component of a base station, or may implement base station functionality. The apparatus may be an IAB node, a component of an IAB node, or may implement IAB node functionality. In some aspects, the apparatus may be referred to as a RAN node or a relay node. In some aspects, the apparatus may be an IAB node, such as in conjunction with a Fig.11A , 11B or 12. The baseband unit 1604 can communicate with the UE 104 via a cellular RF transceiver. The baseband unit 1604 may include a computer-readable medium / memory. The baseband unit 1604 is responsible for general processing, including executing software stored on a computer-readable medium / memory. When the software is executed by the baseband unit 1604, the baseband unit 1604 performs the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the baseband unit 1604 when executing the software. The baseband unit 1604 also includes a receiving component 1630, a communication manager 1632, and a sending component 1634. The communication manager 1632 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 1604. The baseband unit 1604 may be a component of the wireless device 310 and may include at least one of the TX processor 316, the RX processor 370, and the controller / processor 375 and / or the memory 376.

[0147] The communication manager 1632 includes a BAP configuration component 1640 configured to receive a first BAP configuration associated with a first topology and a second BAP configuration associated with a second topology that at least partially overlaps with the first topology, e.g., as described in conjunction with 1502. The communication manager 1632 also includes a routing component 1642 that routes traffic associated with the first topology based on the first BAP configuration and routes traffic associated with the second topology based on the second BAP configuration, e.g., as described in conjunction with 1506. The communication manager 1632 also includes a BH RLC CH component 1646 that configures a first backhaul RLC channel based on the first BAP configuration with the first topology, e.g., as described in conjunction with 1508. The communication manager 1632 also includes a topology identifier component 1644 that determines whether traffic is associated with the first topology or the second topology, e.g., as described in conjunction with 1504. The communication manager 1632 also includes an allocation component 1648 that is configured to allocate a first LCID corresponding to the first backhaul RLC channel, e.g., as described in conjunction with 1510 or 1512. The communication manager 1632 also includes an LCID component 1650 configured to receive a first LCID assigned for a first backhaul RLC channel, e.g., as described in conjunction with 1514. The communication manager 1632 also includes a feedback component 1652 configured to send an acknowledgment to acknowledge receipt of at least one of the first BAP configuration or the second BAP configuration, e.g., as described in conjunction with 1514.

[0148] The apparatus may include executing the flowchart of FIG. 15 and combining Figure 11A-12 Each of the blocks in the algorithm described in the various aspects may be an additional component. Thus, the flowchart of FIG. 15 and the combination of FIG. Figure 11A-12 Each block in the various aspects described, and the apparatus may include one or more of those components. The component 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.

[0149] As shown, the device 1602 may include various components configured for various functions. In one configuration, the device 1602 (specifically, the baseband unit 1604) includes: a unit for receiving a first BAP configuration associated with a first topology corresponding to a first topology and a second BAP configuration associated with a second topology corresponding to a second topology that at least partially overlaps with the first topology; and a unit for routing services associated with the first topology based on the first BAP configuration and routing services associated with the second topology based on the second BAP configuration. The device 1602 may also include: a unit for determining whether the service is associated with the first topology or the second topology. The device 1602 may also include: a unit for receiving information indicating that at least one of the first topology or the second topology is associated with a specific service type, wherein the service is routed based on the received information. The apparatus 1602 may also include: a unit for configuring a first backhaul RLC channel based on a first BAP configuration having a first topology; and a unit for assigning a first LCID corresponding to the first backhaul RLC channel, wherein routing the service includes: transmitting a packet including the first LCID corresponding to the first backhaul RLC channel, and transmitting the packet includes: processing the packet as a service associated with the first topology corresponding to the first topology ID. The apparatus 1602 may also include: a unit for configuring the first backhaul RLC channel based on a first BAP configuration having a first topology ID; and a unit for receiving the first LCID assigned to the first backhaul RLC channel, wherein the routing service includes: transmitting a packet including the first LCID corresponding to the first backhaul RLC channel, and transmitting the packet includes: processing the packet as a service associated with the first topology corresponding to the first topology ID. The apparatus 1602 may also include: a unit for receiving a downstream packet associated with the first topology ID; and a unit for passing the packet to an upper layer for processing when the packet carries a destination BAP address that matches a BAP address assigned to the first network node via a BAP address configuration in a BAP configuration having a first topology ID. The apparatus 1602 may also include: a unit for receiving a downstream packet associated with the first topology ID; and a unit for forwarding the packet to an egress link based on the BAP routing ID carried by the packet and the routing configuration received in the first BAP configuration with the first topology ID when the destination BAP address carried by the packet does not match the BAP address assigned to the first network node via the BAP address configuration in the third BAP configuration with the first topology ID. The apparatus 1602 may also include: a unit for receiving an upstream packet associated with the first topology ID; and a unit for forwarding the packet to an egress link based on the BAP routing ID carried by the packet and the routing configuration received in the first BAP configuration with the first topology ID.The apparatus 1602 may also include: a unit for receiving a BAP SDU associated with a first topology ID; and a unit for sending a corresponding packet carrying a BAP routing ID based on a service type or an IP header field of the BAP SDU and based on an uplink mapping configuration received in a first BAP configuration with the first topology ID. The apparatus 1602 may also include: a unit for receiving a BAP SDU associated with a first topology ID; and a unit for sending a corresponding packet carrying a BAP routing ID based on an IP header field and a downlink mapping configuration received in a first BAP configuration with the first topology ID. The apparatus 1602 may also include: a unit for receiving an upstream packet associated with the first topology ID; and a unit for passing the packet to an upper layer for processing when the packet carries a destination BAP address that matches a BAP address assigned to a first network node via a BAP address configuration in a first BAP configuration with the first topology ID. The apparatus 1602 may also include: a unit for sending a confirmation to confirm the receipt of at least one of the first BAP configuration or the second BAP configuration, the confirmation including at least one of the first topology ID or the second topology ID. A means may be one or more of the components of the apparatus 1602 configured to perform the functions recited by the means. As described above, the apparatus 1602 may include the TX processor 316, the RX processor 370, and the 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.

[0150] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is an illustration of an exemplary method. It should be understood that the specific order or hierarchy of the 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 an exemplary order and are not meant to be limited to the specific order or hierarchy provided.

[0151] 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 various aspects shown herein, but are given the full scope consistent with the textual 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 meaning a direct temporal relationship or reaction. That is, these phrases (e.g., "when ...") do not mean an immediate action in response to the occurrence of an action or during the occurrence of the action, but only mean that if the condition is met, the action will occur, but no specific or immediate time constraint is required for the occurrence of the action. The word "exemplary" is used herein to mean "used as an example, instance or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred to or having advantages over other aspects. Unless otherwise expressly 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, wherein any such combination may include one or more members or several 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 become 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, no disclosure herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly recited in the claims. The words "module," "mechanism," "element," "device," etc. may not be substitutes for the word "unit." Thus, no claim element is to be interpreted as a unit-plus-function unless the element is explicitly recited using the phrase "unit for..."

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

[0153] Aspect 1 is a method for wireless communication of a first BS, comprising: receiving a first BAP configuration associated with a first topology ID corresponding to a first topology and a second BAP configuration associated with a second topology ID corresponding to a second topology that at least partially overlaps with the first topology; determining whether a service is associated with the first topology ID or the second topology ID; and routing the service associated with the first topology ID based on the first BAP configuration, and routing the service associated with the second topology ID based on the second BAP configuration.

[0154] In aspect 2, the method according to aspect 1 also includes: for the corresponding first topology and second topology, each of the first BAP configuration and the second BAP configuration respectively includes at least one of the following items: BAP address configuration for the first BS; establishing a return RLC channel at the first BS; modifying the return RLC channel at the first BS; uplink mapping configuration between at least one of the service type or IP header fields and the BAP routing ID, the exit link at the first BS, or the exit return RLC channel at the first BS; downlink mapping configuration between the IP header field and the BAP routing ID, the exit link at the first BS, or the exit return RLC channel at the first BS; routing configuration along the BAP route between the BAP routing ID and the exit link at the first BS; or return RLC channel mapping configuration between the ingress return RLC channel at the first BS and the egress return RLC channel.

[0155] In aspect 3, the method according to aspect 1 or aspect 2 further includes: the traffic associated with the first topology is associated with a second BS, and the traffic associated with the second topology is associated with a third BS.

[0156] In aspect 4, the method according to any one of aspects 1-3 further includes: the first topology ID is a BS CU identifier of the second BS, and the second topology ID is a BS CU identifier of the third BS.

[0157] In aspect 5, the method according to any one of aspects 1-3 further includes: each of the first topology ID and the second topology ID is at least one of the following: a part of a BAP routing ID, a part of a backhaul RLC channel ID, or a part of a BAP address.

[0158] In aspect 6, the method according to any one of aspects 1-5 further includes: routing the service associated with the first topology ID based on the first BAP configuration and routing the service associated with the second topology ID based on the second BAP configuration includes: sending a packet within information indicating whether the packet is associated with the first topology ID or the second topology ID.

[0159] In aspect 7, the method according to any one of aspects 1-6 further includes: receiving information indicating that at least one of the first topology ID or the second topology ID is associated with a specific service type, wherein the service is routed based on the received information.

[0160] In aspect 8, the method according to any one of aspects 1 to 7 further includes: the service type is at least one of F1-C signaling, F1-U tunnel or non-F1 service.

[0161] In aspect 9, the method according to any one of aspects 1-6 further includes: the service is determined to be associated with the first topology ID or the second topology ID based on a default value of a service type of the service.

[0162] In aspect 10, the method according to any one of aspects 1-6 or 9 further includes: the service type is at least one of F1-C signaling, F1-U tunnel or non-F1 service.

[0163] In aspect 11, the method according to any one of aspects 1-6 or 9 further includes: when the service is transmitted to the second BS, the service is determined to be associated with the first topology ID by default, and when the service is transmitted to the third BS, the service is determined to be associated with the second topology ID by default.

[0164] In aspect 12, the method according to any one of aspects 1-11 further includes: configuring a first return RLC channel based on the first BAP configuration having the first topology ID; and allocating a first LCID corresponding to the first return RLC channel, wherein the routing of the service includes: transmitting a packet including the first LCID corresponding to the first return RLC channel, and the transmitting of the packet includes: processing the packet as a service associated with the first topology corresponding to the first topology ID.

[0165] In aspect 13, the method according to any one of aspects 1-12 further includes: at least a portion of the first LCID is allocated to include the first topology ID.

[0166] In aspect 14, the method according to any one of aspects 1-11 further includes: configuring a first return RLC channel based on the first BAP configuration having the first topology ID; and receiving a first LCID assigned to the first return RLC channel, wherein the routing of the service includes: transmitting a packet including the first LCID corresponding to the first return RLC channel, and the transmitting of the packet includes: processing the packet as a service associated with the first topology corresponding to the first topology ID.

[0167] In aspect 15, the method according to any one of aspects 1-14 further includes: routing the service includes: receiving a downstream packet associated with the first topology ID; and passing the packet to upper layer processing when the packet carries a destination BAP address that matches the BAP address assigned to the first BS via the BAP address configuration in the first BAP configuration with the first topology ID.

[0168] In aspect 16, the method according to any one of aspects 1-14 further includes: routing the service includes: receiving a downstream packet associated with the first topology ID; and when the destination BAP address carried by the packet does not match the BAP address assigned to the first BS via the BAP address configuration in the third BAP configuration with the first topology ID, forwarding the packet to the exit link based on the BAP routing ID carried by the packet and the routing configuration received in the first BAP configuration with the first topology ID.

[0169] In aspect 17, the method according to any one of aspects 1-14 or 16 further includes: the routing of the service includes: mapping the packet associated with the first topology ID to the egress return RLC channel on the egress link based on the ingress return RLC channel on which the first BS receives the packet and based on the return RLC channel mapping received in the fourth BAP configuration with the first topology ID.

[0170] In aspect 18, the method according to any one of aspects 1-14 further includes: routing the service includes: receiving an upstream packet associated with the first topology ID; and forwarding the packet to an egress link based on the BAP routing ID carried by the packet and the routing configuration received in the first BAP configuration with the first topology ID.

[0171] In aspect 19, the method according to any one of aspects 1-14 or 18 further includes: the routing of the service includes: mapping the packet associated with the first topology ID to the egress return RLC channel on the egress link based on the ingress return RLC channel on which the first BS receives the packet and based on the return RLC channel mapping received in the third BAP configuration with the first topology ID.

[0172] In aspect 20, the method according to any one of aspects 1-19 further includes: receiving a BAP SDU associated with the first topology ID; and sending a corresponding packet carrying a BAP routing ID based on the service type or IP header field of the BAP SDU and based on the uplink mapping configuration received in the first BAP configuration with the first topology ID.

[0173] In aspect 21, the method according to any one of aspects 1-20 further includes: the packet is sent on an egress link based on the BAP routing ID and a routing configuration received in a third BAP configuration with the first topology ID.

[0174] In aspect 22, the method according to any one of aspects 1-21 further includes: the packet is mapped to the export return RLC channel on the export link based on the service type or the IP header field and based on the uplink mapping configuration received in the fourth BAP configuration with the first topology ID.

[0175] In aspect 23, the method according to any one of aspects 1-19 further includes: routing the service includes: receiving a BAP SDU associated with the first topology ID; and sending a corresponding packet carrying the BAP routing ID based on the IP header field and the downlink mapping configuration received in the first BAP configuration with the first topology ID.

[0176] In aspect 24, the method according to any one of aspects 1-19 or 23 further includes: the packet is sent on an egress link based on the BAP routing ID and a routing configuration received in a third BAP configuration with the first topology ID.

[0177] In aspect 25, the method according to any one of aspects 1-19, 23 or 24 further includes: the packet is mapped to the export return RLC channel on the export link based on the IP header field and based on the downlink mapping configuration received in the fourth BAP configuration with the first topology ID.

[0178] In aspect 26, the method according to any one of aspects 1-25 further includes: routing the service includes: receiving an upstream packet associated with the first topology ID; and passing the packet to upper layer processing when the packet carries a destination BAP address that matches the BAP address assigned to the first BS via the BAP address configuration in the first BAP configuration with the first topology ID.

[0179] In aspect 27, the method according to any one of aspects 1-26 further includes: sending a confirmation to confirm the receipt of at least one of the first BAP configuration or the second BAP configuration, the confirmation including at least one of the first topology ID or the second topology ID.

[0180] In aspect 28, the method according to any one of aspects 1-27 further includes: at least one of the first BAP configuration or the second BAP configuration is received through at least one of RRC signaling or F1-C signaling.

[0181] Aspect 29 includes an apparatus for wireless communication of a first BS, comprising: a unit for receiving a first BAP configuration associated with a first topology ID corresponding to a first topology and a second BAP configuration associated with a second topology ID corresponding to a second topology that at least partially overlaps with the first topology; a unit for determining whether a service is associated with the first topology ID or the second topology ID; and a unit for routing the service associated with the first topology ID based on the first BAP configuration, and routing the service associated with the second topology ID based on the second BAP configuration.

[0182] In aspect 30, the apparatus according to aspect 29 further comprises means for performing the method according to any one of aspects 2-28.

[0183] Aspect 31 is a device for wireless communication of a first BS, comprising: a memory; and at least one processor coupled to the memory and configured to: receive a first BAP configuration associated with a first topology ID corresponding to a first topology and a second BAP configuration associated with a second topology ID corresponding to a second topology that at least partially overlaps with the first topology; determine whether a service is associated with the first topology ID or the second topology ID; and route the service associated with the first topology ID based on the first BAP configuration, and route the service associated with the second topology ID based on the second BAP configuration.

[0184] In aspect 32, the apparatus according to aspect 31 further comprises: at least one processor, wherein the at least one processor is further configured to perform the method according to any one of claims 2-28.

[0185] Aspect 33 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer executable code for wireless communication for a first BS, wherein the code, when executed by a processor, causes the processor to perform the following operations: receiving a first BAP configuration associated with a first topology ID corresponding to a first topology and a second BAP configuration associated with a second topology ID corresponding to a second topology that at least partially overlaps with the first topology; determining whether a service is associated with the first topology ID or the second topology ID; and routing the service associated with the first topology ID based on the first BAP configuration, and routing the service associated with the second topology ID based on the second BAP configuration.

[0186] In aspect 34, the computer-readable medium according to aspect 33 further comprises: code for executing the method according to any one of claims 2-28.

[0187] Aspect 35 is a method for wireless communication of a second BS, comprising: determining a BAP configuration associated with backhaul service transmission, the BAP configuration comprising a topology identifier corresponding to a topology among multiple topologies, and for the topology, transmitting a service associated with the topology based on the BAP configuration; and sending the BAP configuration associated with the backhaul service transmission to the first BS.

[0188] In aspect 36, the method according to aspect 35 further includes: for the topology, the BAP configuration includes at least one of the following items: BAP address configuration for the first BS; establishing a return RLC channel at the first BS; modifying the return RLC channel at the first BS; uplink mapping configuration between at least one of the service type or IP header fields and the BAP routing ID, the exit link at the first BS, or the exit return RLC channel at the first BS; downlink mapping configuration between the IP header field and the BAP routing ID, the exit link at the first BS, or the exit return RLC channel at the first BS; routing configuration along the BAP routing between the BAP routing ID and the exit link at the first BS; or a return RLC channel mapping configuration between the ingress return RLC channel at the first BS and the egress return RLC channel.

[0189] In aspect 37, the method according to aspect 35 or 36 further includes: the topology identifier is a BS CU identifier of the second BS.

[0190] In aspect 38, the method according to any one of aspects 35 or 36 further includes: the topology identifier is at least one of the following: a part of a BAP route ID, a part of a backhaul RLC channel ID, or a part of a BAP address.

[0191] In aspect 39, the method according to any one of aspects 35-38 further includes: sending information of the topology identifier indicating a service type to the first BS.

[0192] In aspect 39, the method according to any one of aspects 35-38 further includes: the multiple topologies include a first topology and a second topology that at least partially overlaps with the first topology, wherein the first topology carries services associated with the second BS and the second topology carries services associated with a third BS.

[0193] Aspect 41 is a device for wireless communication of a second BS, comprising: a unit for determining a BAP configuration associated with backhaul service transmission, the BAP configuration comprising a topology identifier corresponding to a topology among multiple topologies, and for the topology, transmitting a service associated with the topology based on the BAP configuration; and a unit for sending the BAP configuration associated with the backhaul service transmission to the first BS.

[0194] In aspect 42, the apparatus according to aspect 41 further comprises means for performing the method according to any one of claims 36-40.

[0195] Aspect 43 is a device for wireless communication of a second BS, comprising: a memory; and at least one processor, which is coupled to the memory and configured to: determine a BAP configuration associated with backhaul service transmission, the BAP configuration comprising a topology identifier corresponding to a topology among multiple topologies, and for the topology, transmit a service associated with the topology based on the BAP configuration; and send the BAP configuration associated with the backhaul service transmission to the first BS.

[0196] In aspect 44, the apparatus according to aspect 43 further comprises: at least one processor, wherein the at least one processor is further configured to perform the method according to any one of claims 36-40.

[0197] Aspect 45 is a computer-readable medium storing computer executable code for wireless communication for a second BS, wherein the code, when executed by a processor, causes the processor to perform the following operations: determine a BAP configuration associated with backhaul service transmission, the BAP configuration comprising a topology identifier corresponding to a topology among a plurality of topologies, and for the topology, transmit a service associated with the topology based on the BAP configuration; and send the BAP configuration associated with the backhaul service transmission to the first BS.

[0198] In aspect 46, the computer-readable medium of aspect 45 further comprises code for executing the method of any one of claims 36-40.

[0199] Aspect 47 is a method of wireless communication at a first network node, comprising: receiving a first BAP configuration associated with a first topology and a second BAP configuration associated with a second topology that at least partially overlaps with the first topology; and routing services associated with the first topology based on the first BAP configuration, and routing services associated with the second topology based on the second BAP configuration.

[0200] In aspect 48, the method according to aspect 47 further comprises associating the first BAP configuration with a first topology ID of the first topology and associating the second BAP configuration with a second topology ID of the second topology.

[0201] In aspect 49, the method according to aspect 48 further comprises: determining whether traffic is associated with the first topology ID or the second topology ID in order to route the traffic.

[0202] In aspect 50, the method according to any one of aspects 47-49 further includes: for the corresponding first topology and the second topology, each of the first BAP configuration and the second BAP configuration respectively includes at least one of the following items: BAP address configuration for the first network node; establishing a return RLC channel at the first network node; uplink mapping configuration between at least one item in the service type or IP header field and the BAP routing ID, the exit link at the first network node, or the exit return RLC channel at the first network node; routing configuration along the BAP route between the BAP routing ID and the exit link at the first network node; or a return RLC channel mapping configuration between the ingress return RLC channel at the first network node and the egress return RLC channel.

[0203] In aspect 51, the method according to any one of aspects 47-50 further comprises: the first service associated with the first topology is associated with a second network node, and the second service associated with the second topology is associated with a third network node.

[0204] In aspect 52, the method according to any one of aspects 47-51 further includes: receiving information indicating that at least one of the first topology or the second topology is associated with a specific service type, wherein the service is routed based on the received information, and the service type is at least one of F1-C signaling, F1-U tunnel, or non-F1 service.

[0205] In aspect 53, the method according to any one of aspects 47-51 further includes: the service is associated with the first topology or the second topology based on a default value of the service type of the service, and the service type is at least one of F1-C signaling, F1-U tunnel or non-F1 service.

[0206] In aspect 54, the method according to aspect 53 further comprises: if the traffic is communicated with a second network node, the traffic is associated with the first topology by default, and if the traffic is communicated with a third network node, the traffic is associated with the second topology by default.

[0207] In aspect 55, the method according to any one of aspects 47-54 further includes: receiving a downstream packet associated with the first topology, and routing the service also includes: passing the downstream packet to an upper layer processing when the downstream packet carries a destination BAP address that matches the BAP address assigned to the first network node via the BAP address configuration in the first BAP configuration having the first topology.

[0208] In aspect 56, the method according to any one of aspects 47-54 further includes: receiving a downstream packet associated with the first topology; and routing the service also includes: when the destination BAP address carried by the downstream packet does not match the BAP address assigned to the first network node via the BAP address configuration in the third BAP configuration having the first topology, forwarding the downstream packet to an egress link based on the BAP routing ID carried by the downstream packet and the routing configuration received in the first BAP configuration having the first topology.

[0209] In aspect 57, the method according to aspect 56 further includes: routing the service includes: mapping the downstream packets associated with the first topology ID to the egress return RLC channel on the egress link based on the ingress return RLC channel on which the first network node receives the downstream packets and based on the return RLC channel mapping received in the fourth BAP configuration having the first topology.

[0210] In aspect 58, the method according to any one of aspects 47-57 further includes: receiving an upstream packet associated with the first topology; and routing the service also includes: forwarding the upstream packet to an egress link based on a BAP routing ID carried by the upstream packet and a routing configuration received in the first BAP configuration associated with the first topology.

[0211] In aspect 59, the method according to aspect 58 further includes: routing the service includes: mapping the upstream packets associated with the first topology to the egress return RLC channel on the egress link based on the ingress return RLC channel on which the first network node receives the upstream packets and based on the return RLC channel mapping received in the third BAP configuration having the first topology.

[0212] In aspect 60, according to the method of any one of aspects 47-59, at least one of the first BAP configuration or the second BAP configuration is included in at least one of an RRC signal or F1-C signaling.

[0213] In aspect 61, the method according to any one of aspects 47-54 or 60 further includes: receiving a BAP SDU associated with the first topology; and routing the service includes: sending a corresponding packet carrying a BAP routing ID based on the service type or IP header field of the BAP SDU and based on the uplink mapping configuration received in the first BAP configuration having the first topology, wherein the corresponding packet is used to transmit on the export link based on the BAP routing ID and the routing configuration in the third BAP configuration having the first topology, and wherein the corresponding packet is mapped to the export return RLC channel on the export link based on the service type or the IP header field and based on the uplink mapping configuration received in the fourth BAP configuration having the first topology.

[0214] In aspect 62, the method according to any one of aspects 47-54 or 60 further includes: receiving a BAP SDU associated with the first topology; and routing the service includes: sending a corresponding packet carrying a BAP routing ID based on an IP header field and a downlink mapping configuration received in the first BAP configuration having the first topology, wherein the corresponding packet is used to transmit on an export link based on the BAP routing ID and the routing configuration in a third BAP configuration having the first topology, and wherein the corresponding packet is mapped to an export return RLC channel on the export link based on the IP header field and based on the downlink mapping configuration in a fourth BAP configuration having the first topology.

[0215] In aspect 63, the method according to any one of aspects 47-54 or 60 further includes: receiving an upstream packet associated with the first topology; and routing the service includes: passing the upstream packet to upper layer processing when the packet carries a destination BAP address that matches the BAP address assigned to the first network node via the BAP address configuration in the first BAP configuration having the first topology.

[0216] In aspect 64, the method according to any one of aspects 47-51 or 56-63 further includes: the first topology is based on a network node CU identifier of a second network node, and the second topology is based on a network node CU identifier of a third network node.

[0217] In aspect 65, the method according to any one of aspects 47-50, 51-55 or 64 further includes: for the corresponding first topology and the second topology, each of the first BAP configuration and the second BAP configuration respectively includes at least one of the following items: modifying the return RLC channel at the first network node; or a downlink mapping configuration between the IP header field and the BAP routing ID, the exit link at the first network node, or the exit return RLC channel at the first network node.

[0218] In aspect 66, the method according to any one of aspects 47-51, 56-63 or 65 further includes: each of the first topology ID and the second topology ID is based on at least a portion of at least one of a BAP routing ID, a backhaul RLC channel ID or a BAP address.

[0219] In aspect 67, the method according to any one of aspects 1-66 further includes: routing the traffic includes: sending a packet within information indicating whether the packet is associated with the first topology ID or the second topology ID.

[0220] In aspect 68, the method according to any one of aspects 1-67 further includes: configuring a first return RLC channel based on the first BAP configuration having a first topology ID; allocating a first LCID corresponding to the first return RLC channel; and transmitting a packet including the first LCID corresponding to the first return RLC channel, wherein transmitting the packet includes: processing the packet as a service associated with a first topology corresponding to the first topology ID, wherein at least a portion of the first LCID is allocated to include the first topology ID.

[0221] In aspect 69, the method according to any one of aspects 1-67 further includes: configuring a first return RLC channel based on the first BAP configuration having a first topology ID; receiving a first LCID assigned to the first return RLC channel; and transmitting a packet including the first LCID corresponding to the first return RLC channel, wherein transmitting the packet includes: processing the packet as a service associated with the first topology corresponding to the first topology ID.

[0222] Aspect 70 is an apparatus for wireless communication, comprising means for performing the method according to any one of aspects 47-60.

[0223] In aspect 71, the apparatus according to aspect 70 further comprises a transceiver.

[0224] In aspect 72, the apparatus according to aspect 70 further comprises at least one antenna.

[0225] Aspect 73 is an apparatus for wireless communication, comprising: a memory; and at least one processor coupled to the memory, the at least one processor configured to perform the method according to any one of aspects 47-60.

[0226] In aspect 74, the apparatus according to aspect 73 further comprises a transceiver.

[0227] In aspect 75, the apparatus according to aspect 73 further comprises at least one antenna.

[0228] Aspect 76 is a computer-readable medium (eg, a non-transitory computer-readable medium) storing computer-executable code for wireless communication of a first BS, which, when executed by a processor, causes the processor to perform a method according to any one of aspects 47-60.

Claims

1. An apparatus for wireless communication at a first network node, comprising: Memory; as well as at least one processor coupled to the memory, the memory and the at least one processor being configured to: receiving a first backhaul adaptation protocol (BAP) configuration associated with a first topology and a second BAP configuration associated with a second topology that at least partially overlaps with the first topology, wherein the first BAP configuration is associated with a first topology identifier (ID) for the first topology and the second BAP configuration is associated with a second topology ID for the second topology; as well as Traffic associated with the first topology is routed based on the first BAP configuration, and traffic associated with the second topology is routed based on the second BAP configuration.

2. The device according to claim 1, wherein: The memory and the at least one processor are further configured to: It is determined whether the traffic is associated with the first topology ID or the second topology ID in order to route the traffic.

3. The device according to claim 1, wherein: For the first topology and the second topology, each of the first BAP configuration and the second BAP configuration includes at least one of the following: a BAP address configuration for the first network node; establishing a backhaul radio link control (RLC) channel at the first network node; an uplink mapping configuration between at least one of a traffic type or an Internet Protocol (IP) header field and a BAP routing identifier (ID), an egress link at the first network node, or an egress backhaul RLC channel at the first network node; a routing configuration along a BAP route between a BAP route ID and the egress link at the first network node; or A backhaul RLC channel mapping configuration between an ingress backhaul RLC channel at the first network node and the egress backhaul RLC channel.

4. The device according to claim 1, wherein: The first traffic associated with the first topology is associated with a second network node, and the second traffic associated with the second topology is associated with a third network node.

5. The device according to claim 1, wherein: The memory and the at least one processor are further configured to: Receive information indicating that at least one of the first topology or the second topology is associated with a specific service type, wherein the service is routed based on the information and the service type is at least one of F1 control plane (F1-C) signaling, F1 user plane (F1-U) tunnel, or non-F1 service.

6. The device according to claim 1, wherein: The service is associated with the first topology or the second topology based on a default value of a service type of the service, wherein the service type is at least one of F1 control plane (F1-C) signaling, F1 user plane (F1-U) tunnel, or non-F1 service.

7. The device according to claim 6, wherein: If the traffic is communicated with the second network node, the traffic is associated with the first topology by default, and if the traffic is communicated with the third network node, the traffic is associated with the second topology by default.

8. The device according to claim 1, wherein: In order to route the traffic, the memory and the at least one processor are further configured to: receiving a downstream packet associated with the first topology; and The downstream packet is passed to upper layer processing when the downstream packet carries a destination BAP address that matches a BAP address assigned to the first network node via a BAP address configuration in the first BAP configuration having the first topology.

9. The device according to claim 1, wherein: In order to route the traffic, the memory and the at least one processor are further configured to: receiving a downstream packet associated with the first topology; and When the destination BAP address carried by the downstream packet does not match the BAP address assigned to the first network node via the BAP address configuration in the third BAP configuration having the first topology, the downstream packet is forwarded to an egress link based on the BAP routing ID carried by the downstream packet and the routing configuration received in the first BAP configuration having the first topology.

10. The device according to claim 9, wherein: In order to route the traffic, the memory and the at least one processor are further configured to: The downstream packets associated with the first topology are mapped to an egress backhaul radio link control (RLC) channel on the egress link based on an ingress backhaul RLC channel on which the first network node receives the downstream packets and based on a backhaul RLC channel mapping received in a fourth BAP configuration having the first topology.

11. The device according to claim 1, wherein: In order to route the traffic, the memory and the at least one processor are further configured to: receiving an upstream packet associated with the first topology; and The upstream packet is forwarded to an egress link based on a BAP routing identifier (ID) carried by the upstream packet and a routing configuration received in the first BAP configuration associated with the first topology.

12. The device according to claim 11, wherein In order to route the traffic, the memory and the at least one processor are further configured to: The upstream packets associated with the first topology are mapped to an egress backhaul radio link control (RLC) channel on the egress link based on an ingress backhaul RLC channel on which the first network node receives the upstream packets and based on a backhaul RLC channel mapping received in a third BAP configuration having the first topology.

13. The device according to claim 1, wherein: At least one of the first BAP configuration or the second BAP configuration is included in at least one of a radio resource control (RRC) signal or F1 control plane (F1-C) signaling.

14. The device according to claim 1, wherein: In order to route the traffic, the memory and the at least one processor are further configured to: receiving a BAP service data unit (SDU) associated with the first topology; as well as A corresponding packet carrying a BAP routing ID is sent based on a service type or an Internet Protocol (IP) header field of the BAP SDU and based on an uplink mapping configuration received in the first BAP configuration having the first topology, wherein the corresponding packet is used for transmission on an egress link based on the BAP routing ID and the routing configuration in a third BAP configuration having the first topology, and wherein the corresponding packet is mapped to an egress backhaul radio link control (RLC) channel on the egress link based on the service type or the IP header field and based on the uplink mapping configuration received in a fourth BAP configuration having the first topology.

15. The device according to claim 1, wherein: In order to route the traffic, the memory and the at least one processor are further configured to: receiving a BAP service data unit (SDU) associated with the first topology; as well as A corresponding packet carrying a BAP routing ID is sent based on an Internet Protocol (IP) header field and a downlink mapping configuration received in the first BAP configuration having the first topology, wherein the corresponding packet is used for transmission on an egress link based on the BAP routing ID and the routing configuration in a third BAP configuration having the first topology, and wherein the corresponding packet is mapped to an egress backhaul radio link control (RLC) channel on the egress link based on the IP header field and based on the downlink mapping configuration in a fourth BAP configuration having the first topology.

16. The device according to claim 1, wherein In order to route the traffic, the memory and the at least one processor are further configured to: receiving an upstream packet associated with the first topology; and The upstream packet is delivered to an upper layer process when the upstream packet carries a destination BAP address matching a BAP address assigned to the first network node via a BAP address configuration in the first BAP configuration having the first topology.

17. The device according to claim 1, wherein: The first topology is based on a network node central unit (CU) identifier of a second network node, and the second topology is based on a network node CU identifier of a third network node.

18. The device according to claim 1, wherein: For the first topology and the second topology, each of the first BAP configuration and the second BAP configuration includes at least one of the following: modifying a backhaul radio link control (RLC) channel at the first network node; or A downlink mapping configuration between an Internet Protocol (IP) header field and a BAP routing identifier (ID), an egress link at the first network node, or an egress backhaul RLC channel at the first network node.

19. The device according to claim 1, wherein: Each of the first topology ID and the second topology ID is based on at least a portion of at least one of a BAP route ID, a backhaul radio link control (RLC) channel ID, or a BAP address.

20. The device according to claim 1, wherein In order to route traffic associated with the first topology based on the first BAP configuration and to route traffic associated with the second topology based on the second BAP configuration, the memory and the at least one processor are configured to send the packet within information indicating whether the packet is associated with the first topology ID or the second topology ID.

21. The device according to claim 1, wherein The memory and the at least one processor are further configured to: configuring a first backhaul radio link control (RLC) channel based on the first BAP configuration having the first topology ID; Allocating a first logical channel ID (LCID) corresponding to the first backhaul RLC channel; as well as Transmitting a packet including the first LCID corresponding to the first return RLC channel, the transmitting the packet comprising: processing the packet as a service associated with the first topology corresponding to the first topology ID, wherein at least a portion of the first LCID is allocated to include the first topology ID.

22. The device according to claim 1, wherein: The memory and the at least one processor are further configured to: configuring a first backhaul radio link control (RLC) channel based on the first BAP configuration having the first topology ID; receiving a first logical channel ID (LCID) allocated for the first backhaul RLC channel; as well as Transmitting a packet including the first LCID corresponding to the first backhaul RLC channel, the transmitting the packet including processing the packet as the traffic associated with the first topology corresponding to the first topology ID.

23. A method for wireless communication of a first network node, comprising: receiving a first backhaul adaptation protocol (BAP) configuration associated with a first topology and a second BAP configuration associated with a second topology that at least partially overlaps with the first topology, wherein the first BAP configuration is associated with a first topology identifier (ID) for the first topology and the second BAP configuration is associated with a second topology ID for the second topology; and Traffic associated with the first topology is routed based on the first BAP configuration, and traffic associated with the second topology is routed based on the second BAP configuration.

24. The method according to claim 23, wherein: For the first topology and the second topology, each of the first BAP configuration and the second BAP configuration includes at least one of the following: a BAP address configuration for the first network node; establishing a backhaul radio link control (RLC) channel at the first network node; an uplink mapping configuration between at least one of a traffic type or an Internet Protocol (IP) header field and a BAP routing identifier (ID), an egress link at the first network node, or an egress backhaul RLC channel at the first network node; a routing configuration along a BAP route between a BAP route ID and the egress link at the first network node; or A backhaul RLC channel mapping configuration between an ingress backhaul RLC channel at the first network node and the egress backhaul RLC channel.

25. The method of claim 23, further comprising: Receive information indicating that at least one of the first topology or the second topology is associated with a specific service type, wherein the service is routed based on the information and the service type is at least one of F1 control plane (F1-C) signaling, F1 user plane (F1-U) tunnel, or non-F1 service.

26. The method of claim 23, further comprising: receiving a downstream packet associated with the first topology; as well as The downstream packet is passed to upper layer processing when the downstream packet carries a destination BAP address that matches a BAP address assigned to the first network node via a BAP address configuration in the first BAP configuration having the first topology.

27. The method of claim 23, further comprising: receiving a downstream packet associated with the first topology; as well as When the destination BAP address carried by the downstream packet does not match the BAP address assigned to the first network node via the BAP address configuration in the third BAP configuration having the first topology, the downstream packet is forwarded to an egress link based on the BAP routing ID carried by the downstream packet and the routing configuration received in the first BAP configuration having the first topology.

28. The method according to claim 27, further comprising: The downstream packets associated with the first topology are mapped to an egress backhaul radio link control (RLC) channel on the egress link based on an ingress backhaul RLC channel on which the first network node receives the downstream packets and based on a backhaul RLC channel mapping received in a fourth BAP configuration having the first topology.

29. The method of claim 23, further comprising: receiving an upstream packet associated with the first topology; as well as The upstream packet is forwarded to an egress link based on a BAP routing identifier (ID) carried by the upstream packet and a routing configuration received in the first BAP configuration associated with the first topology.

30. The method of claim 29, further comprising: The upstream packets associated with the first topology are mapped to an egress backhaul radio link control (RLC) channel on the egress link based on an ingress backhaul RLC channel on which the first network node receives the upstream packets and based on a backhaul RLC channel mapping received in a third BAP configuration having the first topology.

31. The method of claim 23, further comprising: receiving a BAP service data unit (SDU) associated with the first topology; as well as A corresponding packet carrying a BAP routing ID is sent based on a service type or an Internet Protocol (IP) header field of the BAP SDU and based on an uplink mapping configuration received in the first BAP configuration having the first topology, wherein the corresponding packet is used for transmission on an egress link based on the BAP routing ID and the routing configuration in a third BAP configuration having the first topology, and wherein the corresponding packet is mapped to an egress backhaul radio link control (RLC) channel on the egress link based on the service type or the IP header field and based on the uplink mapping configuration received in a fourth BAP configuration having the first topology.

32. The method of claim 23, further comprising: receiving a BAP service data unit (SDU) associated with the first topology; as well as A corresponding packet carrying a BAP routing ID is sent based on an Internet Protocol (IP) header field and a downlink mapping configuration received in the first BAP configuration having the first topology, wherein the corresponding packet is used for transmission on an egress link based on the BAP routing ID and the routing configuration in a third BAP configuration having the first topology, and wherein the corresponding packet is mapped to an egress backhaul radio link control (RLC) channel on the egress link based on the IP header field and based on the downlink mapping configuration in a fourth BAP configuration having the first topology.

33. The method of claim 23, further comprising: receiving an upstream packet associated with the first topology; as well as The upstream packet is delivered to an upper layer process when the upstream packet carries a destination BAP address matching a BAP address assigned to the first network node via a BAP address configuration in the first BAP configuration having the first topology.

34. The method of claim 23, further comprising: configuring a first backhaul radio link control (RLC) channel based on the first BAP configuration having the first topology ID; Allocating a first logical channel ID (LCID) corresponding to the first backhaul RLC channel; as well as Transmitting a packet including the first LCID corresponding to the first return RLC channel, the transmitting the packet comprising: processing the packet as a service associated with the first topology corresponding to the first topology ID, wherein at least a portion of the first LCID is allocated to include the first topology ID.

35. The method of claim 23, further comprising: configuring a first backhaul radio link control (RLC) channel based on the first BAP configuration having the first topology ID; receiving a first logical channel ID (LCID) allocated for the first backhaul RLC channel; as well as Transmitting a packet including the first LCID corresponding to the first backhaul RLC channel, the transmitting the packet including processing the packet as the traffic associated with the first topology corresponding to the first topology ID.

36. An apparatus for wireless communication at a second network node, comprising: Memory; as well as at least one processor coupled to the memory, the memory and the at least one processor being configured to: determining a backhaul adaptation protocol (BAP) configuration associated with transmission of backhaul traffic, the BAP configuration comprising a topology identifier corresponding to a topology in a plurality of topologies, for which traffic associated with the topology is transmitted based on the BAP configuration, wherein the plurality of topologies comprises a first topology and a second topology at least partially overlapping with the first topology, wherein the first topology carries first traffic associated with the second network node, and the second topology carries second traffic associated with a third network node; and The BAP configuration associated with the backhaul traffic transmission is sent to a first network node.

37. The device according to claim 36, wherein For the topology, the BAP configuration includes at least one of the following: a BAP address configuration for the first network node; establishing a backhaul radio link control (RLC) channel at the first network node; modifying the backhaul RLC channel at the first network node; an uplink mapping configuration between at least one of a traffic type or an Internet Protocol (IP) header field and a BAP routing identifier (ID), an egress link at the first network node, or an egress backhaul RLC channel at the first network node; a downlink mapping configuration between the IP header field and the BAP routing ID, the egress link at the first network node, or the egress backhaul RLC channel at the first network node; a routing configuration along a BAP route between a BAP route ID and the egress link at the first network node; or A backhaul RLC channel mapping configuration between an ingress backhaul RLC channel at the first network node and the egress backhaul RLC channel.

38. The device according to claim 36, wherein The topology identifier is a network node central unit (CU) identifier of the second network node.

39. The device according to claim 36, wherein: The topology identifier is based on a portion of at least one of a BAP routing identifier (ID), a backhaul radio link control (RLC) channel ID, or a BAP address.

40. The apparatus of claim 36, wherein: The memory and the at least one processor are further configured to: Information indicating the topology identifier for a traffic type is sent to the first network node.

41. A method for wireless communication of a second network node, comprising: determining a backhaul adaptation protocol (BAP) configuration associated with transmission of backhaul traffic, the BAP configuration comprising a topology identifier corresponding to a topology in a plurality of topologies, for which traffic associated with the topology is transmitted based on the BAP configuration, wherein the plurality of topologies comprises a first topology and a second topology at least partially overlapping with the first topology, wherein the first topology carries first traffic associated with the second network node, and the second topology carries second traffic associated with a third network node; and The BAP configuration associated with the backhaul traffic transmission is sent to a first network node.

42. The method according to claim 41, wherein: For the topology, the BAP configuration includes at least one of the following: a BAP address configuration for the first network node; establishing a backhaul radio link control (RLC) channel at the first network node; modifying the backhaul RLC channel at the first network node; an uplink mapping configuration between at least one of a traffic type or an Internet Protocol (IP) header field and a BAP routing identifier (ID), an egress link at the first network node, or an egress backhaul RLC channel at the first network node; a downlink mapping configuration between the IP header field and the BAP routing ID, the egress link at the first network node, or the egress backhaul RLC channel at the first network node; a routing configuration along a BAP route between a BAP route ID and the egress link at the first network node; or A backhaul RLC channel mapping configuration between an ingress backhaul RLC channel at the first network node and the egress backhaul RLC channel.

43. The method of claim 41, wherein: The topology identifier is a network node central unit (CU) identifier of the second network node.

44. The method of claim 41, wherein: The topology identifier is based on a portion of at least one of a BAP routing identifier (ID), a backhaul radio link control (RLC) channel ID, or a BAP address.

45. The method of claim 41, further comprising: Information indicating the topology identifier for a traffic type is sent to the first network node.

Images