Delay bounds for scheduling priority and packet dropping in integrated access and backhaul networks

Abstract

A method, a computer-readable medium, and an apparatus for wireless communication at an integrated access and backhaul (IAB) node are provided. The IAB node receives a first delay parameter and a second delay parameter associated with a packet, the first delay parameter associated with a discard determination for the packet and the second delay parameter associated with scheduling the packet for transmission. The IAB node performs a discard decision for the packet based on the associated first delay parameter or schedules the packet for transmission to a second IAB node or a user equipment (UE) using the second delay parameter associated with the packet. A central unit (CU) of the IAB network can indicate to the IAB node the second delay parameter for scheduling the packet and the first delay parameter for determining whether to discard the packet.

Description

[0001] Cross-reference to related applications

[0002] This application claims the benefit and priority of U.S. Provisional Application Serial No. 63 / 072,731, filed August 31, 2020, entitled “Delay Bounds for Scheduling Priority and Packet Discard in an Integrated Access and Backhaul Network”, and U.S. Patent Application No. 17 / 394,331, filed August 4, 2021, entitled “DELAY BOUNDS FORSCHEDULING PRIORITY AND PACKET DISCARD IN AN INTEGRATED ACCESS AND BACKHAULNETWORK”, which are expressly incorporated herein by reference in their entirety. Technical Field

[0003] This disclosure generally relates to communication systems, and more specifically to wireless communications including integrated access and backhaul (IAB) networks. Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that enable 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 telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the city, national, regional, and even global levels. An example telecommunications standard is 5G New Radio (NR). 5G NR is part of the Continuous Mobile Broadband Evolution (CMB) initiative released by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., scalability 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 can be based on the 4G Long Term Evolution (LTE) standard. There is a need for further improvements to 5G NR technology. These improvements can also be applied to other multiple access technologies and telecommunications standards that adopt them. Summary of the Invention

[0006] The following provides a brief overview of one or more aspects to offer a basic understanding of them. This overview is not a comprehensive summary of all anticipated aspects, nor is it intended to identify key or important elements of all aspects, nor to describe 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 the more detailed descriptions that follow.

[0007] In one aspect of this disclosure, a method, computer-readable medium, and apparatus for wireless communication at an IAB node are provided. The IAB node apparatus receives a first delay parameter and a second delay parameter associated with a packet, the first delay parameter being associated with determining whether the packet should be discarded, and the second delay parameter being associated with scheduling the packet for transmission. Transmission of the packet may involve a time period, for example, with one or more retransmissions (such as Hybrid Automatic Repeat Request (HARQ) retransmissions or Radio Link Control (RLC) layer retransmissions). The IAB node may discard the packet based on the first delay parameter associated with it, or schedule the packet for transmission to a second IAB node or a User Equipment (UE) using the second delay parameter associated with it. For example, if the delay exceeds the first delay parameter, the IAB node may discard the packet and stop transmission midway through the transmission process. If the delay is less than the first delay parameter, the IAB node may schedule the packet for transmission based on the second delay parameter.

[0008] In another aspect of this disclosure, a method, computer-readable medium, and apparatus for wireless communication for an IAB node are provided. The apparatus receives a first delay parameter and a second delay parameter associated with a packet, the first delay parameter being associated with determining whether the packet should be dropped and the second delay parameter being associated with scheduling the packet for transmission. The apparatus performs a drop decision based on the first delay parameter associated with the packet and schedules the packet for transmission to a second IAB node or a UE using the second delay parameter associated with the packet.

[0009] In another aspect of this disclosure, a method, computer-readable medium, and apparatus for wireless communication of a central unit (CU) in an IAB network are provided. The apparatus indicates to an IAB node a first delay parameter for determining whether to discard a packet and a second delay parameter for scheduling the packet. The apparatus transmits the packet via one or more IAB nodes including the IAB node for transmission to a UE.

[0010] To achieve the foregoing and related objectives, the one or more aspects include the features fully described below and specifically pointed out in the claims. Certain illustrative features of the one or more aspects are set forth in detail in the following description and drawings. However, these features indicate only a few of the various ways in which the principles of the aspects can be employed, and the description is intended to include all such aspects and their equivalents. Attached Figure Description

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

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

[0013] Figure 2B This is a schematic diagram illustrating an example of a DL channel within a subframe according to various aspects of this disclosure.

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

[0015] Figure 2D This is a schematic diagram illustrating an example of a UL channel within a subframe according to various aspects of this disclosure.

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

[0017] Figure 4 An example IAB network is shown.

[0018] Figure 5An example aspect of an IAB network is shown, including the distributed unit (DU) function and mobile terminal (MT) function of IAB nodes in the IAB network.

[0019] Figure 6 The L2 structure of the IAB network is shown.

[0020] Figure 7 An example architecture for IAB donors is shown.

[0021] Figure 8 The stack architecture of the IAB network is shown.

[0022] Figure 9 An example aspect of packet delay budget (PDB) for access networks is shown.

[0023] Figure 10 An example aspect of PDB for IAB networks is shown.

[0024] Figure 11 An example aspect is shown that provides multiple PDB boundaries to intermediate IAB nodes in an IAB network.

[0025] Figure 12 This is a flowchart of a wireless communication method.

[0026] Figure 13 This is a flowchart of a wireless communication method.

[0027] Figure 14 This is a schematic diagram illustrating an example of a hardware implementation for an example device.

[0028] Figure 15 This is a flowchart of a wireless communication method.

[0029] Figure 16 This is a schematic diagram illustrating an example of a hardware implementation for an example device. Detailed Implementation

[0030] Packet Delay Budget (PDB) defines the upper limit of the time packets can be delayed between the UE and the User Plane Function (UPF) terminating the N6 interface. PDB can be a Quality of Service (QoS) feature. In an IAB network, one or more intermediate IAB nodes can provide connectivity between the IAB node serving the UE and the IAB donor. PDB for each backhaul radio link control (RLC) channel can be provided to intermediate IAB-DUs. The PDB for each backhaul RLC channel provides a delay cap between the IAB Distributed Unit (DU) and the child mobile terminal (MT) (e.g., between the DU of the parent IAB node and the MT of the child IAB node served by the parent IAB node). Therefore, the PDB for each backhaul RLC channel provides a delay limit for a single hop between IAB nodes. PDB and core network (CN) PDB can be provided to the serving IAB node of the UE per DRB and per QoS flow, but not to intermediate nodes. Intermediate IAB nodes may not be aware of the end-to-end PDB of QoS flows aggregated to the backhaul RLC.

[0031] The aspects presented in this paper support QoS latency requirements by providing multiple functionalities that can be applied at scheduling nodes (e.g., base stations, gNB-DUs, or IAB-DUs). Scheduling nodes can apply latency-aware scheduling to prioritize resource allocation and scheduling decisions among RLC channels. RLC channels can be used for different UEs / sub-MTs or for the same UE / sub-MT. For example, an RLC channel with a lower PDB can be given a higher scheduling priority than another RLC channel with a larger PDB value. Additionally, scheduling nodes can use drop criteria to discard packets whose delays have expired.

[0032] As presented herein, an IAB node can receive a first delay parameter and a second delay parameter associated with a packet. The first delay parameter is associated with determining whether the packet should be dropped, and the second delay parameter is associated with scheduling the packet for transmission. Transmission of the packet may involve a time period, for example, with one or more retransmissions (such as Hybrid Automatic Repeat Request (HARQ) retransmissions or Radio Link Control (RLC) layer retransmissions). The IAB node may drop the packet based on the first delay parameter associated with it, or schedule the packet for transmission to a second IAB node or User Equipment (UE) using the second delay parameter associated with it. For example, if the delay exceeds the first delay parameter, the IAB node may drop the packet and stop transmission midway. If the delay is less than the first delay parameter, the IAB node may schedule the packet for transmission based on the second delay parameter. Aspects of this application can improve topology-wide fairness, multi-hop latency, and congestion in IAB networks.

[0033] The detailed descriptions below, taken with reference to the accompanying drawings, are intended as descriptions of various configurations and not as representations of the only configuration in which the concepts described herein can be practiced. Specific details are included in the detailed descriptions for the purpose of providing a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0034] Several aspects of a telecommunications system will now be described with reference to various apparatuses and methods. These apparatuses and methods will be described in detail below and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively, “elements”). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the entire system.

[0035] As an 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, system-on-a-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 the various functions described throughout this 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 terms, software should be interpreted broadly as meaning instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc.

[0036] Therefore, in one or more example embodiments, the described functionality can be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality can be stored or encoded as one or more instructions or code on a computer-readable medium. A computer-readable medium includes a computer storage medium. The storage medium can be any available medium accessible to a computer. By way of example, and not limitation, such a computer-readable medium can include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures accessible to a computer.

[0037] While aspects and implementations have been described herein with reference to illustrations of some examples, those skilled in the art will understand that additional implementations and use cases can be implemented in many different arrangements and scenarios. The aspects described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, implementations and / or uses can be implemented through integrated chip implementations and other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, artificial intelligence (AI) enabled devices, etc.). While some examples may or may not be specific to a particular use case or application, a wide variety of applicability to the described aspects is possible. Implementations can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the described aspects. In some practical settings, devices incorporating the described aspects and features may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily involve 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 a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or non-aggregated components, end-user equipment, etc., of different sizes, shapes, and constructions.

[0038] Figure 1This is a schematic diagram illustrating an example of a wireless communication system and access network 100. The wireless communication system (also known as a wireless wide area network (WWAN)) includes a base station 102, a user interface unit (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 macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macro cells include base stations. Small cells include femtocells, picocells, and microcells.

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

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

[0041] Some UEs 104 can communicate with each other using device-to-device (D2D) communication link 158. D2D communication link 158 can use DL / UL WWAN spectrum. D2D communication link 158 can use one or more sideline channels, such as the Physical Sideline Broadcast Channel (PSBCH), Physical Sideline Discovery Channel (PSDCH), Physical Sideline Shared Channel (PSSCH), and Physical Sideline Control Channel (PSCCH). D2D communication can be conducted through various wireless D2D communication systems, such as WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0042] 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, for example, in an unlicensed spectrum such as 5 GHz. When communicating in an unlicensed spectrum, the STA 152 / AP 150 may perform a free channel assessment (CCA) before communication to determine whether the channel is available.

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

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

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

[0046] In light of the foregoing, unless otherwise specifically stated, it should be understood that the term "sub-6GHz" or similar terms (if used herein) can broadly refer to: frequencies less than 6GHz, frequencies within FR1, or frequencies that may include intermediate frequency bands. Furthermore, unless otherwise specifically stated, it should be understood that the term "millimeter wave" or similar terms (if used herein) can broadly refer to: frequencies that may include intermediate frequency bands, frequencies within FR2, FR4, FR4-a, or FR4-1 and / or FR5, or frequencies within the EHF band.

[0047] 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, gNodeB (gNB), or another type of base station. Some base stations (such as gNB 180) may operate in conventional sub-6 GHz spectrum, millimeter wave frequencies, and / or near-millimeter wave frequencies in communication with UE 104. When gNB 180 operates in millimeter wave or near-millimeter wave frequencies, gNB 180 may be referred to as a millimeter wave base station. Millimeter wave base station 180 may utilize beamforming 182 with UE 104 to compensate for path loss and short range. Base station 180 and UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming.

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

[0049] EPC 160 may include Mobility Management Entity (MME) 162, other MMEs 164, Serving Gateway 166, Multimedia Broadcast Multicast Service (MBMS) Gateway 168, Broadcast Multicast Service Center (BM-SC) 170, and Packet Data Network (PDN) Gateway 172. MME 162 can communicate with Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC 160. Typically, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are delivered through Serving Gateway 166, which is itself connected to PDN Gateway 172. PDN Gateway 172 provides UE IP address allocation and other functions. PDN Gateway 172 and BM-SC 170 are connected to IP Service 176. IP Service 176 may include the Internet, intranet, IP Multimedia Subsystem (IMS), PS streaming service, and / or other IP services. The BM-SC 170 provides functionality for MBMS user service provisioning and delivery. It can serve as an entry point for content provider MBMS transmissions, authorize and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and schedule MBMS transmissions. The MBMS gateway 168 can distribute MBMS services to base stations 102 belonging to Multicast-Broadcast Single Frequency Network (MBSFN) areas belonging to broadcast-specific services, and can be responsible for session management (start / stop) and collecting billing information related to eMBMS.

[0050] The core network 190 may include Access and Mobility Management Functions (AMF) 192, other AMFs 193, Session Management Functions (SMF) 194, and User Plane Functions (UPF) 195. AMF 192 may communicate with Unified Data Management (UDM) 196. AMF 192 is the control node that handles signaling between UE 104 and the core network 190. Typically, AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are transmitted through UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 connects to IP services 197. IP services 197 may include the Internet, intranets, IP Multimedia Subsystem (IMS), Packet Switched (PS) Streaming (PSS) services, and / or other IP services.

[0051] Base stations may include and / or be referred to as gNB, Node B, eNB, access point, base transceiver station, radio base station, radio transceiver, transceiver function, Basic Services Set (BSS), Extended Services Set (ESS), Transmitter Receiver Point (TRP), or some other suitable term. Base station 102 provides UE 104 with access to EPC 160 or core network 190. Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, GPS devices, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional devices. Some UE 104 may be referred to as IoT devices (e.g., parking timers, air pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, user station, mobile unit, user unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile user station, access terminal, mobile terminal, radio terminal, remote terminal, mobile phone, user agent, mobile client, client, or any other suitable term.

[0052] Refer again Figure 1 In some aspects, IAB node 103 may include a scheduling / dropping component 198 configured to: receive a first delay parameter and a second delay parameter associated with a packet, the first delay parameter being associated with determining whether to drop the packet and the second delay parameter being associated with scheduling the packet for transmission; and to drop the packet using the first delay parameter associated with the packet, or to schedule the packet for transmission to a second IAB node or UE 104 using the second delay parameter associated with the packet. The central unit (CU) 107 of the IAB network may include a delay parameter component 199 configured to: indicate to IAB node 103 the second delay parameter for scheduling packets and the first delay parameter for determining whether to drop packets. The CU may send packets for transmission to UE 104 via one or more IAB nodes 103 including the IAB node.

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

[0054] Figure 2A This is a schematic diagram 200 showing an example of the first subframe within a 5G NR frame structure. Figure 2BThis is a schematic diagram 230 illustrating an example of a DL channel within a 5G NR subframe. Figure 2C This is a schematic diagram 250 showing an example of a second subframe within a 5G NR frame structure. Figure 2D This is a schematic diagram 280 illustrating an example of a UL channel within a 5G NR subframe. The 5G NR frame structure can be Frequency Division Duplex (FDD) or Time Division Duplex (TDD). In FDD, for a given set of subcarriers (carrier system bandwidth), subframes within that set are dedicated to either DL or UL. In TDD, for a given set of subcarriers (carrier system bandwidth), subframes within that set are dedicated to both DL and UL. Figure 2A , 2C In the provided example, it is assumed that the 5G NR frame structure is TDD, where subframe 4 is configured with slot format 28 (primarily DL), where D is DL, U is UL, and F is flexibly used between DL / UL, and subframe 3 is configured with slot format 1 (with all 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 all DL and UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The UE is configured with a slot format by receiving a Slot Format Indicator (SFI) (dynamically configured via DL Control Information (DCI) or semi-statically / statically configured via Radio Resource Control (RRC) signaling). This description also applies to the TDD 5G NR frame structure.

[0055] Figures 2A-2D The frame structure is illustrated, and aspects of this disclosure are applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10 ms) may be divided into 10 equal-sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include micro-time slots, 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 ordinary or extended. For ordinary CP, each time slot may include 14 symbols, and for extended CP, each time slot may include 12 symbols. Symbols on the DL may be CP Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. Symbols on the UL may be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Extended OFDM (DFT-s-OFDM) symbols (also known as Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols) (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the time slot configuration and CP. The digital scheme defines the subcarrier spacing (SCS) and actually defines the symbol length / duration, which is equal to 1 / SCS.

[0056]

[0057] For a standard CP (e.g., 14 symbols per slot), different digital schemes μ0 through 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For an extended CP, digital scheme 2 allows 4 slots per subframe. Therefore, for slot configuration 0 and digital scheme μ, there are 14 symbols / slot and 2... μ Each time slot / subframe. Subcarrier spacing and symbol length / duration are functions of the digital scheme. Subcarrier spacing can be equal to 2. μ *15kHz, where μ is the digital scheme from 0 to 4. Therefore, 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 proportional to the subcarrier spacing. Figures 2A-2D Examples are provided for a standard CP with 14 symbols per time slot and a digital scheme μ=2 with 4 time slots per subframe. The time 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, one or more different bandwidth portions (BWPs) can exist via frequency division multiplexing (see [link to example]). Figure 2B Each BWP can have a specific digital scheme and CP (normal or extended).

[0058] A resource grid can be used to represent the frame structure. Each time slot consists of a resource block (RB) extending for 12 consecutive subcarriers (also known as a physical RB (PRB)). The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

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

[0060] Figure 2BExamples of various DL channels within a subframe of a frame are shown. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE comprising six RE groups (REGs), each REG comprising 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 PDCCH monitoring timing on the CORESET, where these PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may reside at higher and / or lower frequencies on the channel bandwidth. The Primary Synchronization Signal (PSS) may be located within symbol 2 of a specific subframe of the frame. UE 104 uses the PSS to determine subframe / symbol timing and physical layer identification. The Secondary Synchronization Signal (SSS) may be located within symbol 4 of a specific subframe of the frame. The UE uses the SSS to determine the Physical Layer Cell Identifier Group Number and radio frame timing. Based on the Physical Layer Identifier and the Physical Layer Cell Identifier 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 known 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 not transmitted via the PBCH (e.g., System Information Block (SIB)), and paging messages.

[0061] like Figure 2C As shown, some 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 can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and DM-RS for the Physical Uplink Shared Channel (PUSCH). PUSCH DM-RS can be transmitted in the first or first two symbols of the PUSCH. PUCCH DM-RS can be transmitted in different configurations depending on whether a short or long PUCCH is transmitted, and depending on the specific PUCCH format used. The UE can transmit a Sounding Reference Signal (SRS). SRS can be transmitted in the last symbol of a subframe. SRS can have a comb structure, and the UE can transmit SRS on a comb. SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0062] Figure 2DExamples of various UL channels within a subframe of a frame are shown. The PUCCH can 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) ACK / NACK feedback. The PUCCH carries data and can additionally be used to carry buffer status reports (BSR), power clearance reports (PHR), and / or UCI.

[0063] Figure 3 This is a block diagram illustrating communication between wireless device 310 and wireless device 350 in the access network. In some examples, device 310 may be an IAB donor, and device 350 may be an IAB node. In some examples, device 310 may be a parent IAB node, and device 350 may be a child IAB node. Device 310 may be a parent IAB node, and device 350 may be a UE. In the DL, IP packets from EPC 160 or core network 190 may be provided to controller / processor 375. Controller / processor 375 implements Layer 3 and Layer 2 functions. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Serving Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The controller / processor 375 provides: RRC layer functions associated with broadcasting 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 (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with the delivery of upper-layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation 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), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority ordering.

[0064] Transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functions associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. 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), and M-quadrature amplitude modulation (M-QAM)). The encoded and modulated symbols can then be segmented into parallel streams. Each stream can then be mapped to OFDM subcarriers, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and subsequently combined using inverse fast Fourier transform (IFFT) to generate a physical channel carrying a stream of time-domain OFDM symbols. The OFDM streams are spatially precoded to generate multiple spatial streams. The channel estimate from channel estimator 374 can be used to determine coding and modulation schemes and for spatial processing. The channel estimate can be derived based on a reference signal transmitted by device 350 and / or channel condition feedback. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX can use the corresponding spatial stream to modulate an RF carrier for transmission.

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

[0066] The controller / processor 359 may be associated with a memory 360 that stores program code 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 and logical channels to recover IP packets from the EPC 160. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0067] Similar to the functions described in conjunction with DL transmissions performed by device 310, controller / processor 359 provides: RRC layer functions associated with system information (e.g., MIB, SIB) capture, RRC connection, and measurement reporting; PDCP layer functions associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with the transmission of upper-layer PDUs, error correction via ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation 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 to TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority processing, and logical channel priority ordering.

[0068] The TX processor 368 can use the channel estimate derived by the channel estimator 358 from the reference signal transmitted by the device 310 or from feedback to select an appropriate coding and modulation scheme, and to facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via individual transmitters 354TX. Each transmitter 354TX can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0069] UL transmissions are processed at device 310 in a manner similar to that described for the receiver function at device 350. Each receiver 318RX receives signals via its respective antenna 320. Each receiver 318RX recovers the information modulated onto the RF carrier and provides that information to the RX processor 370.

[0070] Controller / processor 375 may be associated with memory 376, which stores program code and data. Memory 376 may be referred to as computer-readable medium. In UL, controller / processor 375 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transport and logical channels to recover IP packets from device 350. IP packets from controller / processor 375 can be provided to EPC 160 or core network 190. Controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0071] At least one of the TX processor 368, RX processor 356, and controller / processor 359 can be configured to perform operations related to... Figure 1 The scheduling / dropping component is related to various aspects of 198.

[0072] At least one of the TX processor 316, RX processor 370, and controller / processor 375 can be configured to perform operations related to... Figure 1 The delay parameter component 199 is related to various aspects.

[0073] Figure 4 This is a schematic diagram illustrating an IAB network 400. 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, such as a gNB or eNB (e.g., Figure 1 The IAB node 420 can include base stations 102 or 180 in the IAB network 400 and can perform functions for controlling the IAB network 400. The IAB donor 410 and the IAB node 420 share resources to provide access and backhaul networks to the core network 490. For example, resources can be shared between access links and backhaul links in the IAB network.

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

[0075] Each IAB node (e.g., including IAB donor 410 and each IAB node 420) can use a PCI value. The PCI value can be used as an identifier for that IAB donor 410 or IAB node 420. The PCI value can be used to determine the scrambling sequence applied to physical signals and / or channels transmitted by a particular IAB node. For example, a PSS and / or SSS transmitted by the corresponding IAB donor 410 or IAB node 420 can be scrambled using a scrambling sequence based on the PCI used by the respective IAB node. The network can have a limited number of available PCI values. For example, a 5G NR system can support 1008 PCI values. Therefore, a given PCI value can be reused within the same network.

[0076] Figure 5 This is a schematic diagram illustrating the IAB network 500 and its components. The IAB network 500 includes an IAB donor 510 and IAB nodes 520a and 520b. The IAB nodes and the IAB donor can provide radio access links to UEs 530a-c.

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

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

[0079] IAB nodes 520a and 520b may include mobile terminals (MTs) and users (DUs). The MT of IAB node 520a can operate as a scheduled node, similar to UE 530a, and be scheduled by the DU of its parent node (e.g., IAB donor 510). The MT of IAB node 520b can operate as a scheduled node of its parent node 520a. The DU can schedule child IAB nodes 520b and UE 530b of IAB node 520a. This is because IAB nodes can provide connectivity to other IAB nodes, which in turn provide connectivity to other IAB nodes. The pattern of including a parent IAB node for scheduling child IAB nodes / child UEs can continue. Figure 5 More links are shown.

[0080] Figure 6 An IAB network (e.g.) is shown Figure 5Example L2 architecture 600 (Example IAB network in the example). IAB donor CU 602 may have an IP connection to IAB donor DU 604. Donor DU 604 may provide multiple RLC backhaul channels to one or more parent IAB nodes 606. The backhaul RLC channel between DU and MT carries a Backhaul Adaptation Protocol (BAP) for backhauling access services. IAB node 606 may operate as a parent node to one or more child nodes (e.g., IAB node 616) or UE 610. IAB node 606's DU 608 may provide access RLC channels to one or more UEs 610 and / or IAB node 616's MT 612. The access RLC channel between DU 608 and UE 610 may carry PDCP for RRC or DRB. The access RLC channel between DU 608 and MT 612 may carry PDCP for RRC or DRB. DU 608 of IAB node 606 can provide a backhaul RLC channel to MT 612 of IAB node 616. An access RLC channel protocol stack 630 is shown, illustrating an RLC layer with PDCP, MAC, and PHY layers for the access link. A backhaul RLC channel protocol stack 640 is shown, illustrating an RLC layer with BAP, MAC, and PHY layers for the backhaul link. Similar to IAB node 606, IAB node 616 can operate as a parent node to one or more child nodes (e.g., IAB node 618) or UE 610. IAB node 616 may include DU 614, which provides an access RLC channel to one or more UEs 620 and / or MT 612 of IAB node 618, and / or provides a backhaul RLC channel to MT 612 of IAB node 618. This mode can continue, and IAB node 618 can serve additional child IAB nodes and / or UEs. IAB node 606 may be referred to as an “intermediate node” or “intermediate IAB node” between IAB donor DU 604 and IAB node 616 serving UE 602. IAB node 616 may be referred to as a “serving IAB node” or “serving node” of UE 620.

[0081] Figure 7The overall architecture of IAB donor 700 (i.e., IAB donor 510) is shown. Here, IAB donor 700 can be a 5G / NR gNB (i.e., gNB 180). IAB donor 700 can include IAB donor-CU 702 and one or more IAB donor-DU 708. IAB donor-CU 702 can include IAB donor-CU control plane (CP) (IAB donor-CU-CP) 704 and one or more IAB donor-CU user plane (UP) (IAB donor-CU-UP) 706. IAB donor-CU-CP 704 can provide configuration control messages for all or more IAB donor-DU 708. IAB donor-CU-UP 706 can send data packets to and from the IAB network (i.e., IAB network 500) via IAB donor-DU 708. IAB-donor-CU-CP 704 and one or more IAB-donor-CU-UP 706 can communicate with each other via the E1 interface. IAB-donor-CU-CP 704 and one or more IAB-donor-DU 708 can communicate with each other via the F1 control plane interface (F1-C). IAB-donor-CU-UP 706 and one or more IAB-donor-DU 708 can communicate with each other via the F1 user plane interface (F1-U).

[0082] Figure 8 The stack architecture of the IAB network from UE 802 (i.e., one or more UEs 530a / 530b) to IAB donor 811 (i.e., IAB donor 510 / 700) is shown. The stack architecture of the IAB network shows the stack architecture of the user plane 800 of the IAB network and the stack architecture of the control plane 820 of the IAB network. The stack architecture of the user plane 800 of the IAB network includes the stack structure of the user plane of UE 802, IAB-Node 2 804, IAB-Node 1 806, IAB-Donor-DU 808, IAB-Donor-CU-UP 810, and the user plane function (UPF) 812 of the core network. The stack architecture of the control plane 820 of the IAB network includes the control plane of UE 802, IAB node-2 804, IAB node-1 806, IAB donor-DU 808, IAB donor-CU-UP 810, and the stack structure of the access and mobility management functions (AMF) 814 of the core network. Here, IAB node-2 804 connected to UE 802 can be referred to as serving IAB node 804. IAB node-1 806 provided along the path between serving IAB node 804 and IAB donor 811 can be referred to as intermediate IAB node 806.

[0083] In some examples, the connection between UE 802 and serving IAB node 804 can be referred to as an NR link (NR Uu interface), and the RLC channel between UE 802 and serving IAB node 804 can be referred to as an access RLC channel.

[0084] The UPF 812 and IAB donor 811 in the core network can be connected to each other via the NG user plane interface (NG-U), and the AMF 814 and IAB donor 811 in the core network can be connected to each other via the NG control plane interface (NG-C).

[0085] Intermediate IAB node 806 can provide a backhaul connection between serving IAB node 804 and IAB donor 811. The RLC channel between serving IAB node 804 and IAB donor 811 via intermediate IAB node 806 can be referred to as the backhaul RLC channel.

[0086] Intermediate IAB node 806 may have a backhaul layer configured to route data packets between IAB donor 811 and serving IAB node 804. Data packets on the backhaul layer may have a routing ID embedded in the backhaul adaptation protocol (BAP) header of the data packet, enabling the data packet to be routed through intermediate IAB node 806 between IAB donor 811 and target serving IAB node 804. Serving IAB 804 can receive data packets from UE 802 and send data packets to UE 802.

[0087] although Figure 8 The illustration shows an IAB network including an intermediate IAB node 806, but aspects of this disclosure are not necessarily limited thereto, and an IAB network may include multiple intermediate IAB nodes. Thus, an IAB network may have more than one (1) path established via multiple intermediate IAB nodes between the serving IAB node 804 and the IAB donor 811.

[0088] Quality of Service (QoS) flows can provide the finest level of QoS differentiation within a Protocol Data Unit (PDU) session. One or more QoS flows can be mapped to a Data Radio Bearer (DRB), for example, at the SDAP layer. Examples of QoS parameters include: 5G QoS Indicator (5QI), flow bit rate (e.g., for Guaranteed Bit Rate (GBR)), aggregate bit rate (e.g., per PDU session, per UE), Allocation and Retention Policy (ARP), and others. Examples of 5QI characteristics can include any of the following: type, QoS priority, Packet Delay Budget (PDB), dynamically assigned 5QI, Packet Error Rate (PER), Delay Criterion Indicator, average window, maximum data burst size, extended packet delay budget, Core Network (CN) PDB downlink, CNPDB uplink, etc. QoS information can be provided to the UE's Service DU by the CU. For example, in Figure 5 In the process, the CU of donor IAB node 510 connects to the DU of IAB node 520b, which is serving UE 530c. Similarly, Figure 6 CU 602 can provide QoS information to DU 608 serving UE 610, or it can provide QoS information to DU 614 serving IAB node 616 serving UE 620. CU can provide QoS information to the UE's serving DU per DRB and per QoS flow (e.g., via F1-AP messages).

[0089] For example, a UE context setup message on an F1-AP can indicate the DRB to be set up using a setup item information element (IE) that includes a DRB identifier (ID), selected QoS information, and E-UTRAN QoS. The setup IE can also include DRB information, which may include one or more of DRB QoS, Single Network Slice Selection Assistance Information (N-SSAI), or notification control. The setup IE can also include flows mapped to a DRB item, which may include one or more of QoS flow identifiers, QoS flow level QoS parameters, QoS flow mapping indications, or Time-Sensitive Communications (TSC) service characteristics. A UE context setup message can indicate one or more backhaul RLC channels to be set up. The IE for the backhaul RLC channel to be set up may include one or more of the following: backhaul RLC channel ID, selected backhaul QoS information, E-UTRAN backhaul RLC channel QoS, control plane service type and RLC mode, BAP control PDU channel, service mapping information, or configured BAP address. Selecting QoS characteristics can indicate one or more of the following: non-dynamic 5QI (e.g., with a non-dynamic 5QI descriptor), dynamic 5QI (e.g., with a dynamic 5QI descriptor), RAN ARP, GBR QoS flow information, reflected QoS attributes, PDU session ID, uplink PDU session aggregation maximum bit rate, or QoS monitoring request. QoS parameters can define the QoS to be applied to a QoS flow, DRB, or backhaul RLC channel. For backhaul RLC channels, IE and GBR QoS flow information (IE) can be applicable, where GBR QoS flow information may be present if the backhaul RLC channel carries traffic belonging to a GBR QoS flow. Dynamic 5QI can indicate the QoS characteristics of non-standardized or unconfigured 5QIs used for downlink and uplink communications. Non-dynamic 5QI can indicate the QoS characteristics of standardized or pre-configured 5QIs used for downlink and uplink.

[0090] PDB defines the upper limit of the time a packet can be delayed between the UE and the UPF terminating the N6 interface. In some examples, PDB can be indicated in units of 0.5 ms. Extended PDB, CN PDB downlink, or CN PDB uplink can be indicated in units of 0.01 ms. For backhaul RLC channels, PDB defines the upper limit of the time a packet can be delayed between the IAB-DU and its sub-IAB-MT. PDB can be a QoS feature.

[0091] Figure 9 An example schematic diagram 900 is shown illustrating a PDB used to deliver packets between UPF 906 and UE 904, which terminates at N6 interface 916. Figure 9The CN PDB between UPF 906 and access network 902 is also shown. As illustrated, access network 902 includes DU 908, CU control plane (CU_CP) 910, and CU user plane (UP) 912. The CN PDB can be a static value (e.g., non-dynamic) or can be dynamically configured by the CU via F1-AP. Figure 9 As shown by dashed line 918, PDB and CN PDB can be provided to DU 908 per DRB and per QoS flow. For example, PDB and CN PDB can be provided to DU by CU via F1-AP.

[0092] The delay budget applied to the radio interface can be determined by subtracting the static value of the CN PDB, which represents the delay between any UPF 906 terminating N6 916 (which may be selected for a PDU session) and the access network 902. For GBR QoS flows using the delay-critical resource type, to obtain a more accurate delay budget PDB for the RAN, the dynamic value of the CN PDB, representing the delay between the UPF 906 terminating N6 for that QoS flow and the access network 902, can be used. If used for a QoS flow, the RAN can apply the dynamic value for the CN PDB instead of the static value for the CN PDB, for example, it may only be related to 5QI. As an example, the packet delay budget applied to the radio interface can be derived by subtracting the static values ​​of the CN PDB for 1ms, 2ms, 5ms, etc., of the delay between the UPF terminating N6 and the access network from a given PDB.

[0093] Figure 10 An example of an IAB network 1000 including UE 1004 is shown. UE 1004 exchanges communication with UPF 1006 via IAB donor 1007 having CU CP 1010, CUUP 1012, and DU 1008. One or more intermediate IAB nodes can provide connectivity between IAB node 1020 serving UE 1004 and IAB donor 1007. Each IAB node may include DU 1016 and MT 1014, for example, as combined... Figure 5 and 6 As described. The PDB of each backhaul RLC channel can be provided to the intermediate IAB-DU. The PDB of each backhaul RLC channel can provide an upper limit on the delay between the IAB DU and the child MT (e.g., between DU1016 of the parent IAB node and MT 1014 of the child IAB node served by the parent IAB node). Therefore, the PDB of each backhaul RLC channel (in Figure 10(As shown in "BHRLC_PDB"), only single-hop latency limits are provided between IAB nodes. PDBs and CN PDBs can be provided to the serving IAB node 1020 of UE 1004 per DRB and per QoS flow, for example, but not to intermediate nodes. Similar to... Figure 9 The example described herein allows PDB and CN PDB to be provided to serving IAB node 1020, for example, from CU (e.g., CU_CP 1010) of IAB donor 1007 to DU 1016 of serving IAB node 1020. CU may only indicate one-hop PDB (e.g., backhaul RLC PDB) to intermediate IAB node DU. Intermediate IAB nodes may not be aware of the end-to-end PDB of the QoS flows aggregated to the backhaul RLC.

[0094] As described herein, to support QoS latency requirements, several functions can be applied at the scheduling node (e.g., base station, gNB-DU, or IAB-DU). As a first aspect, the scheduling node can apply latency-aware scheduling to prioritize scheduling decisions and resource allocation among RLC channels. RLC channels can be used for different UEs / sub-MTs or for the same UE / sub-MT. For example, an RLC channel with a lower PDB can be given a higher scheduling priority than another RLC channel with a larger PDB value.

[0095] Additionally, scheduling nodes can use criteria to determine whether to drop packets to apply the dropping of packets whose delay has expired. As an example, for a GBR QoS flow with a delay-critical GBR resource type, packets with delays exceeding the PDB are counted as lost and included in the PER unless the data burst exceeds the Maximum Data Burst Value (MDBV) within the PDB's time period or the QoS flow exceeds GBR. For instance, the maximum number of transmissions for MAC HARQ entities and / or AM-RLC entities can be determined based on the PDB or (PDB-CN PDB), allowing TX nodes to abandon HARQ and / or RLC retransmissions when packet delays exceed a limit or threshold (e.g., PDB or PDB-CNPDB).

[0096] For access networks with a single hop, such as Figure 9 As shown, these two functions can be determined based on the same end-to-end delay limit (e.g., (PDB-CN PDB)).

[0097] However, for multi-hop networks, such as Figure 4 , 5 The IAB networks shown in any of 6, 8, or 10 can determine these two functions based on different types of delay limits. For example, they can be based on the target delay budget assigned to a hop (e.g., a hop PDB, such as...). Figure 10The BHRLC_PDB shown is used to determine the scheduling priority among different RLC channels at that hop. However, packets exceeding one hop PDB may not be dropped at intermediate hops, as the packet can still satisfy the end-to-end PDB by using less delay than the target one-hop PDB at a later hop. The aspects presented in this paper provide a way to drop packets at intermediate hops, for example, if the packet has exceeded the end-to-end delay budget.

[0098] Such as combination Figure 10 As described, a single delay limit, such as a backhaul RLC PDB or a one-hop delay limit, can be indicated to intermediate IAB nodes in an IAB network for backhaul RLC. The end-to-end delay budget (e.g., PDB and CN PDB) of the QoS flow can be known only to the donor CU_CP and serving IAB node accessing the RLC, and not to the intermediate IAB nodes of the backhaul RLC. Scheduling and packet dropping using the one-hop backhaul RLC PDB known to the intermediate IAB nodes of the backhaul RLC may result in packet dropping still achieving the end-to-end PDB. In some examples, intermediate IAB nodes can use a one-hop delay limit (e.g., backhaul RLC PDB) to schedule packet priority and may not perform packet dropping. Using the PDB information used for accessing the RLC channel, packet dropping can be restricted to being performed at the end node (e.g., donor CU_UP or serving IAB node). This restriction on packet dropping at intermediate IAB nodes of the backhaul RLC channel may result in resource waste due to delivering expired packets exceeding the end-to-end PDB at intermediate nodes.

[0099] To enable IAB nodes to perform scheduling and dropping of packets for the backhaul RLC channel, the IAB donor CU can provide IAB nodes with a separate delay cap for scheduling and dropping. Figure 11 An example IAB network 1100 is shown, in which multiple delay thresholds 1150 are provided to IAB nodes 1114 and 1116. Thus, an IAB donor CU (e.g., CU CP1110 of IAB donor 1107) can provide multiple delay thresholds to the IAB nodes for the backhaul RLC channel. Figure 11 Also shown is DU 1108 of IAB donor 1107. IAB nodes (e.g., IAB nodes 1114 or 1116) may use a first delay limit (which may be referred to herein as a first delay parameter or a first delay threshold) for packet dropping and may use a second delay limit (which may be referred to herein as a second delay parameter or a second delay threshold) for packet scheduling decisions.

[0100] When making scheduling decisions, IAB node DU can use a second delay limit to prioritize packets across multiple RLC channels (e.g., including both backhaul RLC channels and access RLC channels).

[0101] An IAB node (e.g., IAB node 1114 or 1116) can use a first delay threshold to determine whether to discard a packet being transmitted between UPF 1106 and UE 1104. If the packet's delay exceeds the first threshold, the IAB node (e.g., IAB node 1114 or 1116) can discard the packet.

[0102] In some respects, the delay of the packet used by the IAB node to make a drop decision can be the delay experienced at the current hop between the current IAB node DU and the child MT or UE1104 (e.g., the single-hop delay between the IAB node DU that makes the drop decision and the child MT / UE). Figure 11 The diagram shows that the current hop delay for IAB node 1114 is 1125a, and the current hop delay for IAB node 1116 is 1125b. IAB node 1114 can assume that the total transmission time (e.g., delay) at the current hop includes all HARQ retransmissions and RLC retransmissions up to the decision time at the current hop. Once the delay exceeds a second threshold, IAB node 1114 can discard the packet and stop its transmission or retransmission.

[0103] In some aspects, the delay used by the IAB node for packet discarding decisions can be a more comprehensive delay, including delays from previous hops (e.g., all previous hops). The IAB node can derive the delay experienced from previous hops via a timestamp carried in the packet header (e.g., in the BAP header). The IAB node can compare the current time with this timestamp to determine the delay. The CU can create a timestamp and / or include it in the header, for example, based on the reception of the packet at CU UP 1112. In some examples, the IAB node can determine the delay experienced by the packet at the IAB node's reception time, for example, by IAB-MT for DL ​​packets or by IAB-DU for UL packets. In this example, the delay may not include the transmission time at the current hop. Figure 11 The previous hop delay for the downlink to IAB node 1114 up to reception at MT is shown as 1127a, and the previous hop delay for IAB node 1116 is shown as 1127b. In some examples, the IAB node can determine the delay experienced by the packet up to the IAB node's drop decision time (e.g., including the transmission time of the current hop). Figure 11The previous hop delay for the downlink to IAB node 1114, including the delay at the current hop, is shown as 1129a, and the previous hop delay for IAB node 1116 is shown as 1129b.

[0104] The determination of the delay for packet dropping, based on the current hop delay or the delay of the previous hop combined with the current hop delay, may affect the IAB node's decision on the maximum number of HARQ and RLC transmissions at the current hop.

[0105] The first delay limit used by the IAB node for packet dropping can have a larger value than the second delay limit used for scheduling decisions. For the backhaul RLC channel, the CU CP 1110 can have complete information about the QoS flows aggregated into the backhaul RLC channel, and it can determine the first limit for packet dropping as max(PDB-CN PDB) over all QoS flows aggregated into the backhaul RLC channel.

[0106] Donor CUs (e.g., CU CP 1110) can indicate delay limits (e.g., delay limits for scheduling and dropping) to IAB nodes via F1-AP messages and / or RRC messages.

[0107] In one example, the second delay limit could refer to the BHRLC_PDB indicated for the backhaul RLC via the F1-AP message, for example, as... Figure 10 As shown, the first delay limit can be carried by new signaling in an F1-AP or RRC message.

[0108] The donor CU may or may not indicate a first delay limit for packet dropping on the backhaul RLC channel. If the first delay limit is not indicated, the packet dropping functionality may not apply to backhaul RLC. Therefore, if the IAB node does not receive a second delay limit, the IAB node can determine that packet dropping should not be performed. In some examples, the delay limit for packet dropping may be indicated for a backhaul RLC channel dedicated to Delay-Critical GBR, rather than for other types of packets.

[0109] Figure 12 This is a flowchart 1200 of a wireless communication method. The method can be performed by an IAB node or a component of an IAB node (e.g., IAB nodes 103, 420, 520a, 520b, 606, 616, 618, 804, 806, 1114, or 1116; wireless device 310 or 350; apparatus 1402). This method enables the IAB node to perform scheduling and dropping functions in a manner that efficiently utilizes radio resources without discarding packets that can be received by the UE within the PDB.

[0110] At 1202, the IAB node receives a first delay parameter and a second delay parameter associated with the packet. The first delay parameter is associated with determining whether the packet will be dropped, and the second delay parameter is associated with scheduling the packet for transmission. For example, this reception can be performed by, for example, a first delay parameter component 1448 and a second delay parameter component 1450 via a receive component 1430 and an RF transceiver 1422 of device 1402. Figure 11 An example is shown where IAB node 1114 or 1116 receives first and second delay parameters from donor node 1107. The first delay parameter may be greater than the second delay parameter. For example, the first delay parameter may be based on the PDB between the user plane function and the UE minus the core network packet delay budget, such as PDB-CN PDB. The first delay parameter may be indicated for the RLC channel of the aggregated delay-critical GBR flow. For example, the second delay parameter may include the backhaul RLCPDB. The second delay parameter may be received in an F1-AP message. In some aspects, the first and second delay parameters may be received from the donor CU.

[0111] At 1206, the IAB node performs a drop decision based on a first delay parameter associated with the packet. The IAB node either drops the packet based on the first delay parameter or schedules the packet for transmission to a second IAB node or the UE using a second delay parameter associated with the packet. The drop decision can, for example, be determined by... Figure 14 The discard component 1440 of the device 1402 is used to perform this.

[0112] For example, at 1210, the UE can discard a packet based on the packet's delay exceeding a first delay parameter. In some examples, the delay can correspond to the delay between the DU at the IAB node and the child node scheduled by the IAB node for a single hop. The child node can be a child UE or a MT of the child IAB node. Figure 11 Examples are shown where the current hop delay of IAB node 1114 is 1125a and the current hop delay of IAB node 1116 is 1125b. In some examples, the delay may include the delay of one or more hops preceding the IAB node. The packet delay may be based on the timestamp in the packet header.

[0113] At 1208, the IAB node uses a second delay parameter associated with the packet to schedule the packet for transmission to a second IAB node or the UE. For example, if the IAB node does not drop the packet based on the first delay parameter, the IAB node can schedule the packet for transmission. This scheduling can, for example, be determined by... Figure 14 The scheduling component 1444 of the communication manager 1432 is used to execute this.

[0114] In some aspects, the method may include combining Figure 13 Additional aspects of the description.

[0115] Figure 13 This is a flowchart 1300 of a wireless communication method. The method can be performed by an IAB node or a component of an IAB node (e.g., IAB nodes 103, 420, 520a, 520b, 606, 616, 618, 804, 806, 1114 or 1116; wireless device 310 or 350; apparatus 1402).

[0116] At 1302, the IAB node can receive a first delay parameter and a second delay parameter. In some aspects, the first and second delay parameters can be received from the donor CU. For example, this reception can be performed by, for example, a first delay parameter component 1448 and a second delay parameter component 1450 via the receiving component 1430 and the RF transceiver 1422 of device 1402. Figure 11 An example is shown where IAB node 1114 or 1116 receives first and second delay parameters from donor node 1107.

[0117] At 1306, the IAB node uses a first delay parameter associated with the packet to determine whether to drop the packet. For example, this determination could be made by... Figure 14 The first delay parameter can be executed by the drop-off component 1440 of the communication manager 1432. The first delay parameter can be greater than the second delay parameter. For example, the first delay parameter can be based on the PDB between the user plane function and the UE minus the core network packet delay budget, such as PDB-CN PDB. The first delay parameter can be indicated for the RLC channel of the aggregated delay-critical GBR flow. For example, the second delay parameter can include the backhaul RLC PDB. The second delay parameter can be received in an F1-AP message.

[0118] When the packet delay exceeds a first delay parameter, the IAB node can decide to discard the packet. In some examples, the delay may correspond to the delay between the DU at the IAB node and the child node scheduled by the IAB node for a single hop. The child node can be a child UE or a MT of the child IAB node. Figure 11 Examples are shown where the current hop delay of IAB node 1114 is 1125a and the current hop delay of IAB node 1116 is 1125b. In some examples, the delay may include the delay of one or more hops preceding the IAB node. For example, at 1304, the IAB node can determine the packet delay based on the timestamp in the packet header. This determination may, for example, be made by... Figure 14 The delay component 1446 of the device 1402 performs this function. For example, a timestamp can be included in the BAP layer header. In some examples, the delay can be determined when a packet is received at the IAB node. Figure 11The previous hop delay of the downlink at IAB node 1114 up to reception at MT is shown as 1127a, and the previous hop delay of IAB node 1116 up to reception is shown as 1127b. In some examples, the delay may include the delay of the current hop provided by the IAB node. Figure 11 The diagram shows the previous hop delay of the downlink for IAB node 1114 as 1129a and the previous hop delay for IAB node 1116 as 1129b, including the delay at the current hop. In some examples, if no indication for the first delay parameter is received for a packet, the IAB node may determine not to drop the packet.

[0119] For example, at 1310, the UE discards a packet based on the packet's delay exceeding a first delay parameter. In some examples, the delay may correspond to the delay between the DU at the IAB node and the child node scheduled by the IAB node for a single hop. The child node may be a child UE or a MT of the child IAB node. Figure 11 Examples are shown where the current hop delay of IAB node 1114 is 1125a and the current hop delay of IAB node 1116 is 1125b. In some examples, the delay may include the delay of one or more hops preceding the IAB node. The packet delay may be based on the timestamp in the packet header.

[0120] At 1308, the IAB node uses a second delay parameter associated with the packet to schedule the packet for transmission to a second IAB node or the UE. For example, if the IAB node determines, based on the first delay parameter, not to discard the packet, it can schedule the packet for transmission. The transmission of the packet can involve a period of time, for example, with one or more retransmissions (e.g., HARQ retransmissions or RLC layer retransmissions). The IAB node can discard the packet and stop transmission midway through the transmission process, for example, if the delay exceeds the first delay parameter. Therefore, the determination of whether to discard the packet can occur during the transmission process, for example, as shown at 1312.

[0121] The scheduling can be, for example, by Figure 14 The scheduling component 1444 of the communication manager 1432 performs this function. In some examples, scheduling packet transmissions using a second delay parameter includes prioritizing packet transmissions in relation to multiple RLC channels. The multiple RLC channels may include one or more backhaul RLC channels and one or more access RLC channels.

[0122] Figure 14This is a schematic diagram 1400 illustrating an example of a hardware implementation of device 1402. Device 1402 may be an IAB node, a component of an IAB node, or may implement IAB node functionality. In some aspects, device 1402 may include a baseband unit 1404. Baseband unit 1404 may communicate via cellular RF transceiver 1422 with: UE 104; another IAB node 103, whether a parent or child node; and CU 107 of a donor IAB node. Baseband unit 1404 may include computer-readable medium / memory. Baseband unit 1404 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by baseband unit 1404, the software causes baseband unit 1404 to perform the various functions described herein. The computer-readable medium / memory may also be used to store data manipulated by baseband unit 1404 when executing the software. Baseband unit 1404 also includes a receiving component 1430, a communication manager 1432, and a transmitting component 1434. The communication manager 1432 includes one or more of the 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 device 310 and may include at least one of a memory 376 and / or a TX processor 316, an RX processor 370, and a controller / processor 375.

[0123] Communication manager 1432 includes a first delay parameter component 1448 configured to receive a first delay parameter associated with a packet via receiving component 1430, for example, as described in conjunction with 1202 and 1302. Communication manager 1432 includes a second delay parameter component 1450 configured to receive a second delay parameter associated with a packet via receiving component 1430, for example, as described in conjunction with 1202 and 1302. Communication manager 1432 includes a discard component 1440 that uses the first delay parameter associated with the packet to determine whether to discard the packet (e.g., as described in conjunction with 1306), and / or discards the packet based on the first delay parameter (e.g., as described in conjunction with 1210). Communication manager 1432 also includes a scheduling component 1444 that, if the IAB node determines based on the first delay parameter not to discard the packet, schedules the packet for transmission to a second IAB node or UE using the second delay parameter associated with the packet, for example, as described in conjunction with 1208 and / or 1308. The communication manager 1432 may also include a delay component 1446, which determines the delay of a packet based on a timestamp in the packet header, for example, as described in conjunction with 1304.

[0124] The device may include execution Figure 12 And / or additional components for each box of the algorithm in the flowchart of 13. Therefore,Figure 12 Each block in the flowchart of 13 and / or 13 may be executed by a component, and the apparatus 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 processor implementation, or some combination thereof.

[0125] As shown in the figure, device 1402 may include various components configured for various functions. In one configuration, device 1402 (specifically, baseband unit 1404) includes: units for receiving a first delay parameter and a second delay parameter associated with a packet, the first delay parameter being associated with determining whether to discard the packet and the second delay parameter being associated with scheduling the packet for transmission; units for discarding the packet based on the first delay parameter associated with the packet; and units for scheduling the packet for transmission to a second IAB node or UE using the second delay parameter associated with the packet. Device 1402 may also include: units for determining whether to discard a packet using the first delay parameter associated with the packet, and units for scheduling the packet for transmission to a second IAB node or UE using the second delay parameter associated with the packet when the IAB node determines not to discard the packet based on the first delay parameter. Device 1402 may also include: units for determining the delay of a packet based on a timestamp in the packet header. The units may be one or more components of device 1402 configured to perform the functions described by the units. As described above, device 1402 may include TX processor 316, RX processor 370, and controller / processor 375. Therefore, in one configuration, the units may be TX processor 316, RX processor 370, and controller / processor 375 configured to perform the functions described by the units.

[0126] Figure 15 This is a flowchart 1500 of a wireless communication method. The method can be performed by an IAB node CU (e.g., CU 107, 602, 702; IAB donor nodes 410, 510, 810, 1107; wireless device 310 or 350; apparatus 1602). The method enables the CU to provide parameters that allow the IAB node to perform scheduling and dropping functions in a manner that efficiently utilizes radio resources without discarding packets that can be received by the UE within the PDB.

[0127] At position 1502, the CU indicates to the IAB node a first delay parameter for determining whether to drop the packet and a second delay parameter for scheduling the packet. If the packet's delay exceeds the first delay parameter, the first delay parameter can instruct the IAB node to drop the packet. For example, this indication can be... Figure 16The delay budget component 1640 of the communication manager 1632 performs this function. The first delay parameter can be greater than the second delay parameter. For example, the first delay parameter can be based on the PDB between the user plane function and the UE minus the core network packet delay budget, such as PDB-CN PDB. The first delay parameter can be indicated for the RLC channel of the aggregated delay-critical GBR flow. For example, the second delay parameter can include the backhaul RLC PDB. The second delay parameter can be indicated in the F1-AP message.

[0128] In some examples, the latency may correspond to the latency between the DU at the IAB node and the child node scheduled by the IAB node for a single hop. The child node can be a child UE or a MT of the child IAB node. Figure 11 Examples are shown where the current hop latency of IAB node 1114 is 1125a and the current hop latency of IAB node 1116 is 1125b. In some examples, the latency may include the latency of one or more hops preceding the IAB node.

[0129] In some respects, the CU can include a timestamp in the packet header. The inclusion of a timestamp can, for example, be achieved by... Figure 16 The timestamp component 1644 of the device 1602 is used to perform this operation. For example, the timestamp can be included in the BAP layer header. In some examples, the delay can be determined when a packet is received at the IAB node. Figure 11 The previous hop delay of the downlink at IAB node 1114 up to reception at MT is shown as 1127a, and the previous hop delay of IAB node 1116 up to reception is shown as 1127b. In some examples, the delay may include the delay of the current hop provided by the IAB node. Figure 11 The diagram shows the previous hop delay of the downlink for IAB node 1114 as 1129a and the previous hop delay for IAB node 1116 as 1129b, including the delay at the current hop. In some examples, if the CU does not provide an indication of the first delay parameter used for the packet, the IAB node may determine not to drop the packet.

[0130] At point 1504, the CU sends packets via one or more IAB nodes, including this IAB node, for transmission to the UE. For example, the packets may be sent by... Figure 16 The transmission component 1634 of the device 1602 in the middle transmits.

[0131] Figure 16This is a schematic diagram 1600 illustrating an example of a hardware implementation of device 1602. Device 1602 may be a CU or donor IAB node, a component of a CU or donor IAB node, or may perform the functions of a CU or donor IAB node. In some aspects, device 1602 may include a baseband unit 1604. Baseband unit 1604 may communicate with one or more IAB nodes 103 via cellular RF transceiver 1622. Baseband unit 1604 may include computer-readable medium / memory. Baseband unit 1604 is responsible for general processing, including executing software stored on computer-readable medium / memory. When executed by baseband unit 1604, the software causes baseband unit 1604 to perform the various functions described herein. Computer-readable medium / memory may also be used to store data manipulated by baseband unit 1604 when executing the software. Baseband unit 1604 also includes a receiving component 1630, a communication manager 1632, and a transmitting component 1634. Communication manager 1632 includes one or more of the illustrated components. The components within the communication manager 1632 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 device 310 and may include at least one of the memory 376 and / or the TX processor 316, the RX processor 370, and the controller / processor 375.

[0132] The communication manager 1632 includes a delay budget component 1640, wherein the CU indicates to the IAB node a second delay parameter for scheduling packets and a first delay parameter for determining whether to discard packets, for example, as described in conjunction with 1502. The communication manager 1632 also includes a timestamp component 1644, which includes a timestamp in the packet header, for example, as described in conjunction with 1506. The transmission component 1634 transmits packets via one or more IAB nodes including the IAB node for transmission to the UE, for example, as described in conjunction with 1504.

[0133] The apparatus may include the ability to perform Figure 15 The flowchart shows the algorithm as an additional component for each box. Therefore, Figure 15 Each box in the flowchart can be executed by a component, and the apparatus can include one or more of those components. The components can 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 processor implementation, or some combination thereof.

[0134] As shown in the figure, apparatus 1602 may include various components configured for various functions. In one configuration, apparatus 1602 (specifically baseband unit 1604) includes: a unit for indicating to an IAB node a first delay parameter for determining whether to discard a packet and a second delay parameter for scheduling the packet. Apparatus 1602 may also include: a unit for transmitting packets via one or more IAB nodes including the IAB node for transmission to a UE. Apparatus 1602 may also include: a unit for including a timestamp in the header of the packet. The unit may be one or more components of apparatus 1602 configured to perform the functions described by the unit. As described above, apparatus 1602 may include TX processor 316, RX processor 370, and controller / processor 375. Therefore, in one configuration, the unit may be TX processor 316, RX processor 370, and controller / processor 375 configured to perform the functions described by the unit.

[0135] It should be understood that the specific order or hierarchy of boxes in the disclosed process / flowchart is an illustration of exemplary methods. It should be understood that the specific order or hierarchy of boxes in the process / flowchart may be rearranged based on design preferences. Furthermore, some boxes may be combined or omitted. The appended method claims present the elements of the individual boxes in a sample order and are not intended to limit one to the specific order or hierarchy presented.

[0136] The preceding description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but should be given the full scope consistent with the language of the claims, wherein, unless specifically stated otherwise, references to singular elements are not intended to mean “one and only one,” but rather “one or more.” Terms such as “if,” “when,” and “at the time of,” should be interpreted as indicating “under the condition of,” rather than implying an immediate temporal relationship or reaction. That is, these phrases, such as “when,” do not imply an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply imply that an action will occur if the condition is met, without requiring a specific or immediate temporal constraint on the occurrence of the action. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects. Unless specifically stated otherwise, the term “some” means one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be 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 of A, B, or C. All structural and functional equivalents of elements throughout the various aspects described in this disclosure that are known or will be known hereafter by those skilled in the art are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is expressly recited in the claims. The terms “module,” “mechanism,” “element,” and “device” are not necessarily substitutes for the term “means.” Therefore, no element of a claim should be interpreted as a unit plus a function unless the element is explicitly stated using the phrase “means for.”

[0137] The following aspects are illustrative only and may be combined with, and are not limited to, other aspects of the examples or teachings described herein.

[0138] Aspect 1 is a method for wireless communication at an IAB node, comprising: using a first delay parameter to determine whether to discard a packet; and using a second delay parameter associated with the packet to schedule the packet for transmission to a second IAB node or a UE.

[0139] In aspect 2, the method according to aspect 1 further includes: scheduling the transmission of the packet using the second delay parameter, including prioritizing the transmission of the packet in relation to a plurality of RLC channels.

[0140] In aspect 3, the method according to aspect 1 or aspect 2 further includes: the plurality of RLC channels comprising one or more backhaul RLC channels and one or more access RLC channels.

[0141] In aspect 4, the method according to any one of aspects 1-3 further includes: when the delay of the packet exceeds a first delay parameter, the IAB node determines to discard the packet.

[0142] In aspect 5, the method according to any one of aspects 1-4 further includes: the delay corresponding to the delay between the DU at the IAB node and the child node scheduled by the IAB node for a single hop.

[0143] In aspect 6, the method according to any one of aspects 1-5 further includes: the delay includes a delay of one or more hops prior to the IAB node.

[0144] In aspect 7, the method according to any one of aspects 1-6 further includes: determining the delay of the packet based on the timestamp in the header of the packet.

[0145] In aspect 8, the method according to any one of aspects 1-7 further includes: the timestamp being included in the BAP layer header.

[0146] In aspect 9, the method according to any one of aspects 1-8 further includes: determining the delay when the packet is received at the IAB node.

[0147] In aspect 10, the method according to any one of aspects 1-9 further includes: the delay includes the delay of the current hop provided by the IAB node.

[0148] In aspect 11, the method according to any one of aspects 1-10 further includes: the first delay parameter being greater than the second delay parameter.

[0149] In aspect 12, the method according to any one of aspects 1-11 further includes: the first delay parameter is based on the PDB between the user plane function and the UE minus the core network packet delay budget.

[0150] In aspect 13, the method according to any one of aspects 1-12 further includes: receiving the first delay parameter and the second delay parameter from the donor CU.

[0151] In aspect 14, the method according to any one of aspects 1-13 further includes: the second delay parameter includes the backhaul RLC PDB and is received in an F1-AP message.

[0152] In aspect 15, the method according to any one of aspects 1-14 further includes: if no indication of a first delay parameter for the packet is received, the IAB node determines not to discard the packet.

[0153] In aspect 16, the method according to any one of aspects 1-15 further includes: a first delay parameter being indicated for the RLC channel of the aggregated delay critical GB stream.

[0154] Aspect 17 is an apparatus comprising one or more processors and one or more memories in electronic communication with the one or more processors, the one or more memories storing instructions executable by the one or more processors to cause the apparatus to perform the method according to any one of aspects 1-16.

[0155] Aspect 18 is a system or apparatus comprising units for implementing the method according to any one of aspects 1-16 or implementing the apparatus according to any one of aspects 1-16.

[0156] Aspect 19 is a non-transitory computer-readable medium storing instructions that can be executed by one or more processors to cause the one or more processors to perform the method according to any one of aspects 1-16.

[0157] Aspect 20 is a method for wireless communication at a CU in an IAB network, comprising: indicating to an IAB node a first delay parameter for determining whether to discard a packet and a second delay parameter for scheduling the packet; and transmitting the packet via one or more IAB nodes including the IAB node for transmission to a UE.

[0158] In aspect 21, the method according to aspect 20 further includes: a first delay parameter indicating that if the delay of the packet exceeds the first delay parameter, the IAB node discards the packet.

[0159] In aspect 22, the method according to aspect 20 or aspect 21 further includes: the delay corresponds to the delay between the DU at the IAB node and the child node scheduled by the IAB node for a single hop.

[0160] In aspect 23, the method according to any one of aspects 20-22 further includes: the delay includes a delay of one or more hops prior to the IAB node.

[0161] In aspect 24, the method according to any one of aspects 20-23 further includes: including a timestamp in the header of the packet.

[0162] In aspect 25, the method according to any one of aspects 20-24 further includes: the timestamp being included in the BAP layer header.

[0163] In aspect 26, the method according to any one of aspects 20-25 further includes: the second delay parameter being greater than the first delay parameter.

[0164] In aspect 27, the method according to any one of aspects 20-26 further includes: a first delay parameter based on the PDB between the user plane function and the UE minus the core network packet delay budget.

[0165] In aspect 28, the method according to any one of aspects 20-27 further includes: a first delay parameter comprising the return RLC PDB and indicated in an F1-AP message.

[0166] In aspect 29, the method according to any one of aspects 20-28 further includes: a first delay parameter being indicated for the RLC channel of the aggregated delay critical GBR stream.

[0167] Aspect 30 is a device or apparatus comprising one or more processors and one or more memories in electronic communication with the one or more processors, the one or more memories storing instructions executable by the one or more processors to cause the device to perform the method according to any one of aspects 20-29.

[0168] In aspect 31, the device or apparatus according to aspect 30 further includes: at least one antenna and a transceiver coupled to the at least one antenna and the one or more processors.

[0169] Aspect 32 is a system or apparatus comprising units for implementing the method according to any one of aspects 20-29 or implementing the apparatus according to any one of aspects 20-29.

[0170] In aspect 33, the system or apparatus according to aspect 32 further includes at least one antenna and a transceiver coupled to said at least one antenna.

[0171] Aspect 34 is a non-transitory computer-readable medium storing instructions that can be executed by one or more processors to cause the one or more processors to perform the method according to any one of aspects 20-29.

[0172] Aspect 35 is a method for wireless communication at a first IAB node, comprising: receiving a first delay parameter and a second delay parameter associated with a packet, the first delay parameter being associated with a discard determination for the packet and the second delay parameter being associated with scheduling the packet for transmission; performing a discard determination based on the first delay parameter associated with the packet; and scheduling the packet for transmission to a second IAB node or a UE using the second delay parameter associated with the packet.

[0173] In aspect 36, the method according to aspect 35 further includes: scheduling the packet to the second IAB node using a second delay parameter associated with the packet, including prioritizing the transmission of the packet in relation to a plurality of RLC channels.

[0174] In aspect 37, the method according to aspect 36 further includes: the plurality of RLC channels comprising one or more backhaul RLC channels and one or more access RLC channels.

[0175] In aspect 38, the method according to any one of aspects 35-37 further includes: the discard decision is based on whether the delay of the packet exceeds a first delay parameter.

[0176] In aspect 39, the method according to aspect 38 further includes: the delay corresponds to the delay between the DU at the first IAB node and the child node scheduled by the first IAB node for a single hop.

[0177] In aspect 40, the method according to aspect 38 further includes: the delay includes a delay of one or more hops prior to the first IAB node.

[0178] In aspect 41, the method according to aspect 40 further includes: the delay of the packet is based on a timestamp in the header of the packet.

[0179] In aspect 42, the method according to aspect 41 further includes: the timestamp being included in the BAP layer header.

[0180] In aspect 43, the method according to any one of aspects 40-41 further includes: the delay being based on the reception of the packet at the first IAB node.

[0181] In aspect 44, the method according to aspect 38 further includes: the delay includes the delay of the current hop provided by the first IAB node.

[0182] In aspect 45, the method according to any one of aspects 35-44 further includes: a first delay parameter being greater than a second delay parameter.

[0183] In aspect 46, the method according to any one of aspects 35-44 further includes: a first delay parameter based on the PDB between the user plane function and the UE minus the core network packet delay budget.

[0184] In aspect 47, the method according to any one of aspects 35-46 further includes: the first delay parameter and the second delay parameter are derived from the donor CU.

[0185] In aspect 48, the method according to any one of aspects 35-47 further includes: a second delay parameter including the return RLC PDB indicated in the F1-AP message.

[0186] In aspect 49, the method according to any one of aspects 35-48 further includes: skipping the dropping of the second packet based on the fact that no indication for the first delay parameter has been received for the second packet.

[0187] In aspect 50, the method according to any one of aspects 35-49 further includes: a first delay parameter being indicated for the RLC channel of the aggregated delay-critical GBR stream.

[0188] Aspect 51 is an apparatus including a memory and at least one processor, the memory and the at least one processor being configured to perform the method according to any one of aspects 35-50.

[0189] In aspect 52, the apparatus according to aspect 51 further includes at least one antenna and a transceiver coupled to the at least one antenna and the at least one processor.

[0190] Aspect 53 is an apparatus comprising units for implementing the method according to any one of aspects 35-50 or implementing the apparatus according to any one of aspects 35-50.

[0191] In aspect 54, the system or apparatus according to aspect 53 further includes: at least one antenna and a transceiver coupled to said at least one antenna.

[0192] Aspect 55 is a non-transitory computer-readable medium storing instructions that can be executed by one or more processors to cause the one or more processors to perform the method according to any one of aspects 35-50.

Claims

1. An apparatus for wireless communication at a first integrated access and backhaul (IAB) node, the first IAB node serving as an intermediate node in a multi-hop path between a donor central unit (CU) and a serving IAB node providing an access radio link channel (RLC) to a user equipment (UE), comprising: Memory; as well as At least one processor is coupled to the memory and configured to cause the device to perform the following operations: The donor CU receives a first PDB parameter corresponding to the end-to-end packet delay budget (PDB) for a packet destined for the UE and a second PDB parameter corresponding to the one-hop PDB for the packet destined for the UE. The first PDB parameter for the packet is based on the end-to-end PDB between the user plane function and the UE, and the second PDB parameter indicates the single-hop backhaul radio link control (RLC) PDB for the packet. The first PDB parameter is associated with the packet drop determination, and the second PDB parameter is associated with scheduling the packet for transmission. At the first IAB node, a decision on whether to discard the packet is made based on the first PDB parameter corresponding to the end-to-end PDB associated with the packet; as well as At the first IAB node, the packet is scheduled to be transmitted to the second IAB node using the second PDB parameter corresponding to the one-hop PDB associated with the packet.

2. The apparatus according to claim 1, wherein, The at least one processor is configured to cause the device to perform the following operation: scheduling the packet for transmission to the second IAB node using the second PDB parameter corresponding to the one-hop PDB associated with the packet, including: prioritizing the transmission of the packet in relation to a plurality of radio link control (RLC) channels when the drop decision indicates that the packet should not be dropped based on the first PDB parameter corresponding to the end-to-end PDB.

3. The apparatus according to claim 2, wherein, The plurality of RLC channels includes one or more backhaul RLC channels and one or more access RLC channels.

4. The apparatus according to claim 1, wherein, The discard decision is based on whether the delay of the packet exceeds the first PDB parameter corresponding to the end-to-end PDB.

5. The apparatus according to claim 4, wherein, The latency corresponds to the latency between the distributed unit (DU) at the first IAB node and the child node scheduled by the first IAB node for the single hop.

6. The apparatus according to claim 4, wherein, The delay includes the delay of one or more hops before the first IAB node.

7. The apparatus according to claim 6, wherein, The delay of the packet is based on the timestamp in the packet header.

8. The apparatus according to claim 7, wherein, The timestamp is included in the Backhaul Adaptation Protocol (BAP) layer header.

9. The apparatus according to claim 7, wherein, The latency is based on the reception of the packet at the first IAB node.

10. The apparatus according to claim 6, wherein, The delay includes the delay of the current hop provided by the first IAB node.

11. The apparatus according to claim 1, wherein, The first PDB parameter is greater than the second PDB parameter.

12. The apparatus according to claim 1, wherein, The first PDB parameter is based on the end-to-end PDB between the user plane function and the UE minus the core network PDB.

13. The apparatus according to claim 1, wherein, The second PDB parameter is indicated in the F1-AP message.

14. The apparatus according to claim 1, wherein, The at least one processor is configured to cause the device to skip discarding the second packet based on the fact that no indication for the first PDB parameter has been received for the second packet.

15. The apparatus according to claim 1, wherein, The first PDB parameter is indicated for the radio link control (RLC) channel of the aggregated delay critical guaranteed bit rate (GBR) stream.

16. The apparatus according to claim 1, further comprising: antenna; as well as A transceiver coupled to the antenna and the at least one processor.

17. The apparatus according to claim 1, wherein, The first PDB parameter is a multi-hop connection between the CU and the UE of the group, including multiple intermediate IAB nodes.

18. The apparatus according to claim 1, wherein, The first PDB parameter and the second PDB parameter are used for different determinations for the same group, and the different determinations include the discard decision and the scheduling decision.

19. A method for wireless communication at a first integrated access and backhaul (IAB) node, the first IAB node serving as an intermediate node in a multi-hop path between a donor central unit (CU) and a serving IAB node providing an access radio link channel (RLC) to a user equipment (UE), the method comprising: The donor CU receives a first PDB parameter corresponding to the end-to-end packet delay budget (PDB) for a packet destined for the UE and a second PDB parameter corresponding to the one-hop PDB for the packet destined for the UE. The first PDB parameter for the packet is based on the end-to-end PDB between the user plane function and the UE, and the second PDB parameter indicates the single-hop backhaul radio link control (RLC) PDB for the packet. The first PDB parameter is associated with the packet drop determination, and the second PDB parameter is associated with scheduling the packet for transmission. At the first IAB node, a decision on whether to discard the packet is made based on the first PDB parameter corresponding to the end-to-end PDB associated with the packet; as well as At the first IAB node, the packet is scheduled to be transmitted to the second IAB node using the second PDB parameter corresponding to the one-hop PDB associated with the packet.

20. An apparatus for wireless communication at a central unit (CU) of an integrated access and backhaul (IAB) network, comprising: Memory; as well as At least one processor is coupled to the memory and configured to cause the device to perform the following operations: The CU indicates to the IAB node a first PDB parameter corresponding to the end-to-end packet delay budget (PDB) for the packet and a second PDB parameter corresponding to the one-hop PDB for the packet, wherein the first PDB parameter for the packet is based on the end-to-end PDB between the user plane function and the user equipment (UE), and the second PDB parameter indicates the single-hop backhaul radio link control (RLC) PDB for the packet; the first PDB parameter is used by the IAB node to determine whether to drop the packet, and the second PDB parameter is used by the IAB node to schedule the packet. as well as The packet is sent via one or more IAB nodes, including the IAB node, for transmission to the UE.

21. The apparatus of claim 20, further comprising: antenna; as well as A transceiver coupled to the antenna and the at least one processor.

22. The apparatus according to claim 20, wherein, The first PDB parameter indicates that if the delay of the packet exceeds the first PDB parameter corresponding to the end-to-end PDB, the IAB node discards the packet.

23. The apparatus according to claim 22, wherein, The delay corresponds to the delay for the single hop between the distributed unit (DU) of the IAB node and the child node scheduled by the IAB node.

24. The apparatus according to claim 22, wherein, The delay includes the delay of one or more hops prior to the IAB node.

25. The apparatus according to claim 20, wherein, The at least one processor is further configured to cause the device to perform the following operations: Include the timestamp in the header of the packet.

26. The apparatus according to claim 25, wherein, The timestamp is included in the Backhaul Adaptation Protocol (BAP) layer header.

27. The apparatus according to claim 21, wherein, The first PDB parameter is greater than the second PDB parameter.

28. The apparatus according to claim 21, wherein, The first PDB parameter is based on the end-to-end PDB between the user plane function and the UE minus the core network PDB.

29. The apparatus according to claim 28, wherein, The at least one processor is configured to indicate the second PDB parameter in an F1-AP message.

30. The apparatus according to claim 21, wherein, The at least one processor is configured to indicate the first PDB parameters to the radio link control (RLC) channel for the aggregated delay critical guaranteed bit rate (GBR) stream.

31. A method for wireless communication at the central unit (CU) of an integrated access and backhaul (IAB) network, comprising: The CU indicates to the IAB node a first PDB parameter corresponding to the end-to-end packet delay budget (PDB) for the packet and a second PDB parameter corresponding to the one-hop PDB for the packet, wherein the first PDB parameter for the packet is based on the end-to-end PDB between the user plane function and the user equipment (UE), and the second PDB parameter indicates the single-hop backhaul radio link control (RLC) PDB for the packet; the first PDB parameter is used by the IAB node to determine whether to drop the packet, and the second PDB parameter is used by the IAB node to schedule the packet. as well as The packet is sent via one or more IAB nodes, including the IAB node, for transmission to the UE.

Images