Multi-link network coordination

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a central entity may determine a set of schedulable resources for a plurality of links associated with a plurality of nodes of a multi-link network; and may provide scheduling information to the plurality of nodes to schedule communications on the plurality of links based at least in part on determining the schedulable set of resources. In some aspects, a node of a network may determine an extended slot format indicator for the node based at least in part on a received extended slot format indicator for a parent node of the node and a null adjustment request received from a child node of the node; the determined extended slot format indicator may be provided to the child node; and may provide the received null adjustment request to the parent node. Numerous other aspects are provided.

Description

[0001] This application is a divisional application of a patent application with an international application date of August 8, 2019, an international application number of PCT / US2019 / 045763, a Chinese national application date of August 8, 2019, an application number of 201980051615.8, and an invention name of “Multi-link Network Coordination”.

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS PURSUANT TO 35 USC §119

[0003] This application claims priority to U.S. Provisional Patent Application No. 62 / 716,875, entitled “MULTI-LINK NETWORK COORDINATION,” filed on August 9, 2018, and U.S. Non-Provisional Patent Application No. 16 / 534,432, entitled “MULTI-LINK NETWORK COORDINATION,” filed on August 7, 2019, which are hereby expressly incorporated herein by reference.

[0004] Disclosed technical field

[0005] Various aspects of the technology described below generally relate to wireless communications, and more particularly to techniques and apparatuses for multi-link network coordination. Some techniques and apparatuses described herein enable and provide wireless communication devices and systems configured for multi-link or multi-hop scenarios and efficient communications therein. Background Art

[0006] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). 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, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0007] A wireless communication network may include several base stations (BS) that can support communication of several user equipments (UEs). User equipments (UEs) may communicate with base stations (BSs) via downlinks and uplinks. Downlinks (or forward links) refer to the communication link from a BS to a UE, while uplinks (or reverse links) refer to the communication link from a UE to a BS. As will be described in more detail herein, a BS may be referred to as a Node B, a gNB, an Access Point (AP), a Radio Head, a Transmit Receive Point (TRP), a New Radio (NR) BS, a 5G Node B, and the like.

[0008] The above multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different user equipment to communicate at the city, country, region, and even global level. New Radio (NR) (which may also be referred to as 5G) is an enhancement set to the LTE mobile standard promulgated by the Third Generation Partnership Project (3GPP). NR is designed to better support mobile broadband Internet access by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink (DL), using CP-OFDM and / or SC-FDM (e.g., also known as discrete Fourier transform spread OFDM (DFT-s-OFDM) on the uplink (UL), and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation. Other open standards are better integrated to better support mobile broadband Internet access. However, as the demand for mobile broadband access continues to grow, there is a need for further improvements in LTE and NR technologies. Preferably, these improvements should be applicable to other multiple access technologies and telecommunication standards that adopt these technologies.

[0009] A brief overview of some examples

[0010] The following summarizes some aspects of the present disclosure to provide a basic understanding of the technology discussed. This summary is not an exhaustive overview of all conceived features of the present disclosure, and is neither intended to identify the key or decisive elements of all aspects of the present disclosure nor to attempt to define the scope of any or all aspects of the present disclosure. The sole purpose of this summary is to give some concepts of one or more aspects of the present disclosure in an overview form as a prelude to a more detailed description given later.

[0011] In some aspects, a wireless communication method performed by a central entity may include determining a set of schedulable resources for a plurality of links associated with a plurality of nodes of a multi-link network, wherein at least one of the plurality of nodes is not a parent node or a child node of the central entity. The method may include providing scheduling information to the plurality of nodes to schedule communications on the plurality of links based at least in part on determining the set of schedulable resources.

[0012] In some aspects, a central entity for wireless communication may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to: determine a set of schedulable resources for a plurality of links associated with a plurality of nodes of a multi-link network, wherein at least one of the plurality of nodes is not a parent node or a child node of the central entity. The memory and the one or more processors may be configured to: provide scheduling information to the plurality of nodes to schedule communications on the plurality of links based at least in part on determining the set of schedulable resources.

[0013] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of a central entity, may cause the one or more processors to: determine a set of schedulable resources for a plurality of links associated with a plurality of nodes of a multi-link network, wherein at least one of the plurality of nodes is not a parent node or a child node of the central entity. The one or more instructions, when executed by the one or more processors of the central entity, may cause the one or more processors to: provide scheduling information to the plurality of nodes to schedule communications on the plurality of links based at least in part on determining the set of schedulable resources.

[0014] In some aspects, an apparatus for wireless communication may include: means for determining a set of schedulable resources for a plurality of links associated with a plurality of nodes of a multi-link network, wherein at least one of the plurality of nodes is not a parent node or a child node of the apparatus. The apparatus may include: means for providing scheduling information to the plurality of nodes to schedule communications on the plurality of links based at least in part on determining the set of schedulable resources.

[0015] In some aspects, a wireless communication method performed by a node may include: determining an extended slot format indicator of the node based at least in part on an extended slot format indicator received by a parent node of the node and a blanking adjustment request received from a child node of the node, wherein the extended slot format indicator of the node includes a blanking field that identifies a non-schedulable resource of the node. The method may include: providing the determined extended slot format indicator to the child node of the node. The method may include: providing the received blanking adjustment request to the parent node of the node.

[0016] In some aspects, a node for wireless communication may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to determine an extended slot format indicator of the node based at least in part on an extended slot format indicator of a parent node of the node and a blanking adjustment request received from a child node of the node, wherein the extended slot format indicator of the node includes a blanking field identifying an unschedulable resource of the node. The memory and the one or more processors may be configured to provide the determined extended slot format indicator to the child node of the node. The memory and the one or more processors may be configured to provide the received blanking adjustment request to the parent node of the node.

[0017] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of a node, may cause the one or more processors to: determine the extended slot format indicator of the node based at least in part on the received extended slot format indicator of the parent node of the node and the blanking adjustment request received from the child node of the node, wherein the extended slot format indicator of the node includes a blanking field identifying the unschedulable resources of the node. The one or more instructions, when executed by one or more processors of the node, may cause the one or more processors to: provide the determined extended slot format indicator to the child node of the node. The one or more instructions, when executed by one or more processors of the node, may cause the one or more processors to: provide the received blanking adjustment request to the parent node of the node.

[0018] In some aspects, an apparatus for wireless communication may include: means for determining an extended slot format indicator of the apparatus based at least in part on a received extended slot format indicator of a parent node of the apparatus and a blanking adjustment request received from a child node of the apparatus, wherein the extended slot format indicator of the apparatus includes a blanking field identifying a non-schedulable resource of the apparatus. The apparatus may include: means for providing the determined extended slot format indicator to the child node of the apparatus. The apparatus may include: means for providing the received blanking adjustment request to the parent node of the apparatus.

[0019] Aspects generally include methods, devices, apparatus, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices, nodes, central entities, and processing systems as substantially described herein with reference to and as illustrated in the drawings and specification.

[0020] The foregoing has broadly outlined the features and technical advantages of examples according to the present disclosure in an effort to make the following detailed description better understood. Additional features and advantages will be described hereinafter. The disclosed concepts and specific examples can be easily used as a basis for modifying or designing other structures for implementing the same purpose as the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the accompanying drawings is provided for illustration and description purposes and does not define limitations on the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] In order to understand the above-stated features of the present disclosure in detail, the above briefly summarized content may be described in more detail with reference to various aspects, some of which are illustrated in the accompanying drawings. However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and should not be considered to limit its scope, as the description may allow for other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0023] Figure 1 is a block diagram conceptually illustrating an example of a wireless communication network in accordance with various aspects of the present disclosure.

[0024] Figure 2 is a block diagram conceptually illustrating an example of a base station in communication with a user equipment (UE) in a wireless communication network according to various aspects of the present disclosure.

[0025] Figure 3A is a block diagram conceptually illustrating an example of a frame structure in a wireless communication network in accordance with various aspects of the present disclosure.

[0026] Figure 3B is a block diagram conceptually illustrating an example synchronous communication hierarchy in a wireless communication network in accordance with various aspects of the present disclosure.

[0027] Figures 4A-4C is a diagram illustrating an example of a network topology for a network in accordance with various aspects of the present disclosure.

[0028] Figure 5 is a diagram illustrating an example of centralized resource partitioning according to various aspects of the present disclosure.

[0029] Figure 6 is a diagram illustrating an example of dynamic resource coordination according to various aspects of the present disclosure.

[0030] Figure 7 is a diagram illustrating an example process, such as performed by a central entity, in accordance with various aspects of the present disclosure.

[0031] Figure 8 is a diagram illustrating an example process, for example, performed by a node, according to various aspects of the present disclosure. Detailed Description

[0033] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be implemented in many different forms and should not be interpreted as being limited to any specific structure or function given throughout the present disclosure. On the contrary, these aspects are provided to make the present disclosure thorough and complete, and it will fully convey the scope of the present disclosure to those skilled in the art. At least partially based on the teachings herein, those skilled in the art will appreciate that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is independently implemented or implemented in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein can be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods practiced using supplements or other other structures, functionality, or structures and functionality as the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the present disclosure disclosed herein can be implemented by one or more elements of the claims.

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

[0035] It should be noted that although various aspects may be described herein using terminology typically associated with 3G and / or 4G wireless technologies, various aspects of the present disclosure may be applied in communication systems based on other generations, such as 5G and later generations, including NR technology.

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

[0037] Figure 1 1 is a diagram illustrating a network 100 in which various aspects of the present disclosure may be practiced. The network 100 may be an LTE network or some other wireless network, such as a 5G or NR network. The wireless network 100 may include several BSs 110 (shown as BSs 110a, BSs 110b, BSs 110c, and BSs 110d) and other network entities. A BS is an entity that communicates with a user equipment (UE) and may also be referred to as a base station, NR BS, B node, gNB, 5G B node (NB), access point, transmit receive point (TRP), etc. Each BS may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" may refer to a coverage area of ​​a BS and / or a BS subsystem serving the coverage area, depending on the context in which the term is used.

[0038] A BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a residence) and may allow restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG)). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In Figure 1 In the example shown in , BS110a may be a macro BS for macro cell 102a, BS110b may be a pico BS for pico cell 102b, and BS110c may be a femto BS for femto cell 102c. The BS may support one or more (e.g., three) cells. The terms "eNB", "base station", "NR BS", "gNB", "TRP", "AP", "Node B", "5GNB", and "cell" may be used interchangeably herein.

[0039] In some aspects, the cell may not necessarily be stationary, and the geographic area of ​​the cell may move depending on the location of the mobile BS. In some aspects, the BSs may be interconnected to each other and / or to one or more other BSs or network nodes (not shown) in the access network 100 via various types of backhaul interfaces, such as direct physical connections, virtual networks, and / or the like using any suitable transport network.

[0040] The wireless network 100 may also include a relay station. A relay station is an entity that can receive transmissions of data from an upstream station (e.g., a BS or a UE) and send transmissions of the data to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that can relay transmissions for other UEs. Figure 1 In the example shown in , a relay station 110d may communicate with a macro BS 110a and a UE 120d to facilitate communication between the BS 110a and the UE 120d. A relay station may also be referred to as a relay BS, a relay base station, a relay, or the like.

[0041] The wireless network 100 may be a heterogeneous network including different types of BSs (e.g., macro BSs, pico BSs, femto BSs, relay BSs, etc.). These different types of BSs may have different transmit power levels, different coverage areas, and different effects on interference in the wireless network 100. For example, a macro BS may have a high transmit power level (e.g., 5 to 40 watts), while a pico BS, a femto BS, and a relay BS may have a lower transmit power level (e.g., 0.1 to 2 watts).

[0042] A network controller 130 may be coupled to a set of BSs and may provide coordination and control of these BSs. The network controller 130 may communicate with each BS via a backhaul. The BSs may also communicate with each other directly or indirectly, for example, via a wireless or wired backhaul.

[0043] UE 120 (e.g., 120a, 120b, 120c) may be dispersed throughout the wireless network 100, and each UE may be stationary or mobile. UE may also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, etc. UE may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet device, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, a biometric sensor / device, a wearable device (smart watch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., a music or video device, or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, or any other suitable device configured to communicate via a wireless or wired medium.

[0044] Some UEs may be considered as machine type communication (MTC) UEs, or evolved or enhanced machine type communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., which may communicate with a base station, another device (e.g., a remote device), or some other entity. A wireless node may provide connectivity to or to a network (e.g., a wide area network, such as the Internet or a cellular network), for example, via a wired or wireless communication link. Some UEs may be considered as Internet of Things (IoT) devices, and / or may be implemented as NB-IoT (narrowband Internet of Things) devices. Some UEs may be considered as client equipment (CPE). UE 120 may be included inside a housing that houses components of UE 120, such as a processor component, a memory component, etc.

[0045] In general, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support a specific radio access technology (RAT) and may operate on one or more frequencies. RAT may also be referred to as radio technology, air interface, etc. Frequency may also be referred to as carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0046] In some aspects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using base station 110 as an intermediary to communicate with each other) using one or more sidelink channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, etc.), mesh networks, etc. In this case, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by base station 110.

[0047] As indicated above, Figure 1 These are provided as examples only. Other examples may differ from those described herein. Figure 1 Examples described.

[0048] Figure 2 A block diagram of a design 200 of a base station 110 and a UE 120 is shown, which may be Figure 1 One for each base station and one for each UE in the base station 110. Base station 110 may be equipped with T antennas 234a through 234t, and UE 120 may be equipped with R antennas 252a through 252r, where in general T≧1 and R≧1.

[0049] At the base station 110, the transmit processor 220 may receive data for one or more UEs from the data source 212, select one or more modulation and coding schemes (MCS) for each UE based at least in part on a channel quality indicator (CQI) received from the UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MCS selected for the UE, and provide data symbols for all UEs. The transmit processor 220 may also process system information (e.g., for semi-static resource partitioning information (SRPI), etc.) and control information (e.g., CQI requests, grants, upper layer signaling, etc.), and provide overhead symbols and control symbols. The transmit processor 220 may also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS)) and synchronization signals (e.g., primary synchronization signals (PSS) and secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide T output symbol streams to T modulators (MOD) 232a to 232t. Each modulator 232 may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator 232 may further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The T downlink signals from modulators 232a to 232t may be transmitted via T antennas 234a to 234t, respectively. According to various aspects described in more detail below, position coding may be used to generate synchronization signals to convey additional information.

[0050] At UE 120, antennas 252a to 252r may receive downlink signals from base station 110 and / or other base stations and may provide received signals to demodulators (DEMODs) 254a to 254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) the received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 256 may obtain received symbols from all R demodulators 254a to 254r, perform MIMO detection on the received symbols where applicable, and provide detected symbols. A receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data for UE 120 to a data sink 260, and provide decoded control information and system information to a controller / processor 280. The channel processor may determine reference signal received power (RSRP), received signal strength indicator (RSSI), reference signal received quality (RSRQ), channel quality indicator (CQI), etc. In some aspects, one or more components of UE 120 may be included in a housing.

[0051] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, CQI, etc.). The transmit processor 264 may also generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266, if applicable, further processed by modulators 254a through 254r (e.g., for DFT-s-OFDM, CP-OFDM, etc.), and transmitted to the base station 110. At the base station 110, uplink signals from the UE 120 as well as other UEs may be received by the antenna 234, processed by the demodulator 232, detected by the MIMO detector 236, if applicable, and further processed by the receive processor 238 to obtain decoded data and control information sent by the UE 120. The receive processor 238 may provide decoded data to a data sink 239 and decoded control information to a controller / processor 240. The base station 110 may include a communication unit 244 and communicate with the network controller 130 via the communication unit 244. The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292.

[0052] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2Any other components of the may perform one or more techniques associated with multi-link network coordination, as described in more detail elsewhere herein. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the Figure 7 The process 700 Figure 8 The operations of process 800, and / or other processes as described herein. Memories 242 and 282 may store data and program codes for base station 110 and UE 120, respectively. Scheduler 246 may schedule UEs for data transmission on the downlink and / or uplink.

[0053] In some aspects, the central entity (e.g., base station 110, UE 120, etc.) may include: means for determining (e.g., using controller / processor 240, controller processor 280, etc.) a set of schedulable resources for multiple links associated with multiple nodes of the multi-link network; means for providing scheduling information to the multiple nodes to schedule communications on the multiple links based at least in part on determining the set of schedulable resources (e.g., using controller / processor 240, transmit processor 220, TX MIMO processor 230, modulator 232, antenna 234, controller / processor 280, transmit processor 264, TX MIMO processor 266, modulator 254, antenna 252, etc.); etc. In some aspects, such means may include means for combining Figure 2 One or more components of a base station 110, a UE 120, etc. are described.

[0054] In some aspects, a node (e.g., base station 110, UE 120, etc.) may include: means for determining (e.g., using controller / processor 240, controller processor 280, etc.) an extended slot format indicator for the node based at least in part on a received extended slot format indicator for a parent node of the node and a blanking adjustment request received from a child node of the node; means for providing (e.g., using controller / processor 240, transmit processor 220, TX MIMO processor 230, modulator 232, antenna 234, controller / processor 280, transmit processor 264, TX MIMO processor 266, modulator 254, antenna 252, etc.) the determined extended slot format indicator to a child node of the node; means for (e.g., using controller / processor 240, transmit processor 220, TX MIMO processor 230, modulator 232, antenna 234, controller / processor 280, transmit processor 264, TX MIMO processor 266, modulator 254, antenna 252, etc.) MIMO processor 266, modulator 254, antenna 252, etc.) to provide the received blanking adjustment request to the parent node of the node; etc. In some aspects, such means may include a device in conjunction with Figure 2 One or more components of a base station 110, a UE 120, etc. are described.

[0055] As indicated above, Figure 2 These are provided as examples only. Other examples may differ from those described herein. Figure 2 Examples described.

[0056] Figure 3A An example frame structure 300 for frequency division duplex (FDD) in a telecommunication system (e.g., NR) is shown. The transmission timeline for each of the downlink and uplink may be divided into units of radio frames (sometimes referred to as frames). Each radio frame may have a predetermined duration (e.g., 10 milliseconds (ms)) and may be divided into a set of Z (Z ≥ 1) subframes (e.g., with indices 0 to Z-1). Each subframe may have a predetermined duration (e.g., 1 ms) and may include a set of time slots (e.g., in Figure 3A Each subframe 2 is shown m time slots, where m is a parameter design for transmission, such as 0, 1, 2, 3, 4, etc.). Each time slot may include a set of L symbol periods. For example, each time slot may include fourteen symbol periods (e.g., Figure 3A ), seven symbol periods, or another number of symbol periods. In the case where a subframe includes two slots (e.g., when m=1), the subframe may include 2L symbol periods, where the 2L symbol periods in each subframe may be assigned indices 0 to 2L-1. In some aspects, the scheduling unit for FDD may be frame-based, subframe-based, slot-based, symbol-based, etc.

[0057] Although some techniques are described herein in conjunction with frames, subframes, time slots, etc., these techniques may be equally applicable to other types of wireless communication structures, which may be referred to in 5G NR using terms other than "frames," "subframes," "time slots," etc. In some aspects, a wireless communication structure may refer to a periodic, time-bounded communication unit defined by a wireless communication standard and / or protocol. Additionally or alternatively, a wireless communication structure may be used in conjunction with Figure 3A The wireless communication structure configurations are different from those shown in FIG.

[0058] In certain telecommunications (e.g., NR), a base station may transmit synchronization signals. For example, a base station may transmit a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and the like on the downlink for each cell supported by the base station. The PSS and SSS may be used by the UE for cell search and acquisition. For example, the PSS may be used by the UE to determine symbol timing, and the SSS may be used by the UE to determine a physical cell identifier associated with the base station and frame timing. The base station may also transmit a physical broadcast channel (PBCH). The PBCH may carry some system information, such as system information that supports initial access of the UE.

[0059] In some aspects, a base station may transmit a PSS, SSS, and / or PBCH according to a synchronization communication level (e.g., a synchronization signal (SS) level) including multiple synchronization communications (e.g., SS blocks), as described below in conjunction with Figure 3B as described.

[0060] Figure 3B is a block diagram conceptually illustrating an example SS hierarchy, which is an example of a synchronous (SYNC) communication hierarchy. Figure 3B As shown in FIG. 1 , the SS hierarchy may include an SS burst set, which may include a plurality of SS bursts (identified as SS burst 0 to SS burst B-1, where B is the maximum number of repetitions of the SS burst that may be transmitted by the base station). As further shown, each SS burst may include one or more SS blocks (identified as SS block 0 to SS block (b max_SS-1 ), where b max_SS-1 is the maximum number of SS blocks that can be carried by an SS burst. In some aspects, different SS blocks may be beamformed differently. A set of SS bursts may be transmitted by a wireless node periodically, such as every X milliseconds, e.g. Figure 3B In some aspects, SS burst sets may have fixed or dynamic lengths, such as in Figure 3B is shown as Y milliseconds.

[0061] Figure 3BThe SS burst set shown in is an example of a synchronous communication set, and other synchronous communication sets may be used in conjunction with the techniques described herein. Figure 3B The SS blocks shown in are examples of synchronous communications, and other synchronous communications may be used in conjunction with the techniques described herein.

[0062] In some aspects, an SS block includes resources that carry PSS, SSS, PBCH, and / or other synchronization signals (e.g., a third synchronization signal (TSS)) and / or synchronization channels. In some aspects, multiple SS blocks are included in an SS burst, and the PSS, SSS, and / or PBCH may be identical for each SS block across an SS burst. In some aspects, a single SS block may be included in an SS burst. In some aspects, an SS block may be at least four symbol periods in length, with each symbol carrying one or more of a PSS (e.g., occupying one symbol), an SSS (e.g., occupying one symbol), and / or a PBCH (e.g., occupying two symbols).

[0063] In some aspects, the symbols of the SS block are consecutive, such as Figure 3B In some aspects, the symbols of the SS block are non-contiguous. Similarly, in some aspects, one or more SS blocks of an SS burst may be transmitted in contiguous radio resources (e.g., contiguous symbol periods) during one or more time slots. Additionally or alternatively, one or more SS blocks of an SS burst may be transmitted in non-contiguous radio resources.

[0064] In some aspects, an SS burst may have a burst periodicity, whereby each SS block of the SS burst is transmitted by the base station according to the burst periodicity. In other words, the SS blocks may be repeated during each SS burst. In some aspects, an SS burst set may have a burst set periodicity, whereby each SS burst of the SS burst set is transmitted by the base station according to a fixed burst set periodicity. In other words, the SS burst may be repeated during each SS burst set.

[0065] The base station may transmit system information, such as system information blocks (SIBs), on a physical downlink shared channel (PDSCH) in certain time slots. The base station may transmit control information / data on a physical downlink control channel (PDCCH) in C symbol periods of a time slot, where B may be configurable for each time slot. The base station may transmit traffic data and / or other data on the PDSCH in the remaining symbol periods of each time slot.

[0066] As indicated above, Figure 3A and 3B are provided as examples. Other examples may differ from those described in Figure 3A and 3B Examples described.

[0067] Figures 4A-4C 4 is a diagram illustrating an example 400 of a network topology for a multi-link network according to various aspects of the present disclosure. Self-backhaul or integrated access / backhaul (IAB) may be deployed to use a common set of resources for access traffic and backhaul traffic. For example, a first node (e.g., BS110, UE 120, etc.) may communicate backhaul traffic with a second node via a first millimeter wave resource, and may communicate access traffic with a third node via a second millimeter wave resource. In some aspects, the second node and the third node may be the same node. For example, the first node may communicate traffic via a first millimeter wave resource and a second millimeter wave resource. Although some aspects described herein are described in terms of an IAB deployment, some aspects described herein may be used in conjunction with other types of multi-hop networks.

[0068] like Figure 4A As shown in , example 400 may include multiple nodes 402 (e.g., BSs) and multiple nodes 404 (e.g., UEs). At least one node (e.g., node 402-1) may communicate with a core network via a backhaul link 406 (such as an optical fiber connection, a wireless backhaul connection, etc.). Nodes 402 and 404 may communicate with each other using: a link set 408 (such as a millimeter wave link set); an air interface such as 3G, 4G, 5G, etc.; etc. In some aspects, node 402 may correspond to Figure 1 Similarly, the node 404 may correspond to the BS 110 or UE 120 shown in FIG. Figure 1 BS 110 or UE 120 is shown in FIG.

[0069] like Figure 4A As further shown in FIG. 4 , one or more nodes 402 or 404 may communicate indirectly via one or more other nodes 402 or 404. For example, data may be passed from the core network to node 404-6 via backhaul link 406, link 408 between node 402-1 and node 402-5, link 408 between node 402-5 and node 402-4, link 408 between node 402-4 and node 404-5, and link 408 between node 404-5 and node 404-6. In some aspects, multiple different paths may be used to communicate data between nodes 402 or 404. For example, node 402-5 may communicate with node 402-4 via a single link 408 (e.g., a direct link) between node 402-5 and node 402-4, and / or via a first link 408 between node 402-5 and node 402-3 and a second link (e.g., an indirect link) between node 402-3 and node 402-4.

[0070] like Figure 4BAs shown in, node 402 and node 404 can be arranged in hierarchical topology to realize the management to network resources.Each link 408 can be associated with the main link endpoint (main LEP) and from the link endpoint (from LEP), which can define the level between node 402 or 404.For example, node 402-6 can communicate with node 402-7 via link 408-1.In this case, node 402-6 is associated with the main link endpoint of link 408-1, and node 402-7 is associated with the from the link endpoint of link 408-1, which can be defined as node 402-6 being higher than node 402-7 and node 402-7 being defined as being lower than node 402-6 in level with respect to link 408-1.In this case, node 402-6 can be referred to as master node or parent node, and node 402-7 can be referred to as slave node or child node. Furthermore, node 402 - 6 may be defined as upstream relative to node 402 - 7 (and node 402 - 7 may be defined as downstream relative to node 402 - 6 ).

[0071] Similarly, node 402-7 includes the master link endpoint of link 408-2, and node 402-8 includes the slave link endpoint of link 408-2. In this case, with respect to link 408-2, node 402-7 is hierarchically higher than node 402-8 and is located upstream of node 402-8, while node 402-8 is hierarchically lower than node 402-7 and is located downstream of node 402-7. In this case, node 402-7 may be referred to as a master node or a parent node, and node 402-8 may be referred to as a slave node or a child node.

[0072] like Figure 4C As shown in , a set of interfaces can be illustrated in a hierarchical topology for a set of nodes 402. In this case, node 402-10 (e.g., a first IAB node) can be hierarchically lower than node 402-11 (e.g., a second IAB node), and can be hierarchically lower than node 402-12 (e.g., an IAB donor). Similarly, node 402-11 can be hierarchically lower than node 402-12.

[0073] In some aspects, an IAB node may be a node that relays traffic to or from an anchor through one or more hops (e.g., one or more other nodes). In some aspects, an IAB donor may be a node associated with a wired connection to a core network. For example, node 402-12 may include a central unit (CU) that includes an NG interface that connects the CU to a core unit 410 (e.g., a next generation core (NGC) unit), which may be a node of a core network.

[0074] In some aspects, node 402-12 may communicate with nodes 402-10 and 402-11 via another interface. For example, the CU of node 402-12 may include an F1 interface to the corresponding distributed units (DUs) of nodes 402-10 and 402-11. Additionally or alternatively, the DU of node 402-12 (e.g., which may be a master link endpoint) may include an NR Uu interface to the MT of node 402-11 (e.g., the MT of node 402-11 may be a slave link endpoint of the NR Uu interface) and a radio link control adaptation channel (RLC / adaptation) interface to the MT of node 402-11. Additionally or alternatively, the DU of node 402-12 may include one or more other interfaces, such as an NR Uu interface to UE 120 (e.g., node 404), etc.

[0075] In some aspects, node 402-11 may communicate using one or more other interfaces. For example, the DU of node 402-11 may include an NR Uu interface to the MT of node 402-10, an RLC / adaptation interface to the MT of node 402-11, an NR Uu interface to UE 120, etc. In some aspects, node 402-10 may include one or more other interfaces, such as an NR Uu interface to UE 120.

[0076] In some aspects, the CU, DU, and MT may be associated with a functional subset of the node 402. For example, the CU of the node 402-12 may be associated with communicating with the core network and may operate in conjunction with a radio resource control (RRC) layer, a packet data control protocol (PDCP) layer, and the like. Additionally or alternatively, the DU may be a scheduling node for a corresponding MT (which may be a child node). In other words, the DU may represent a master link endpoint for a corresponding MT (which may represent a slave link endpoint). In some aspects, the DU and MT may be associated with communicating scheduling information in conjunction with a radio link control (RLC) layer, a media access control (MAC) layer, a physical (PHY) layer, and the like.

[0077] As indicated above, Figures 4A-4C are provided as examples. Other examples may differ from those described in Figures 4A-4C Examples described.

[0078] In some communication systems (such as 5G or NR), a multi-link network or a multi-hop network may be deployed to enable communication between wireless nodes of the network. Strategies (such as half-duplex constraints) may be implemented for nodes of the network (such as hierarchically arranged parent nodes, nodes, and child nodes). However, the MT of the node may receive a scheduling indicating transmission via a link from the parent node, and the DU of the node may provide a scheduling indicating reception on another link to the child node, which may violate the half-duplex constraint. In addition, the lack of scheduling flexibility in a multi-link network may lead to inefficient use of network resources. Some aspects described herein implement multi-link resource coordination. For example, a central entity may be deployed to implement centralized resource partitioning by providing scheduling information, which identifies a set of schedulable resources determined at least in part based on feedback information (e.g., a resource utilization report). Similarly, a node may be configured to provide an extended SFI based at least in part on a received extended slot format indicator (SFI) and received uplink feedback to achieve dynamic resource coordination. In this way, multi-link networks may achieve improved latency, improved reliability, improved scheduling flexibility, etc. relative to other techniques for resource coordination.

[0079] Figure 5 is a diagram illustrating an example 500 of centralized resource partitioning according to various aspects of the present disclosure. Figure 5 As shown in , example 500 includes a central entity 502 (e.g., an IAB donor), a node 504, a node 506, a UE 508, and a UE 510 in a hierarchical topology multi-link network. The central entity 502 and the node 504 can communicate via a link 522; the node 506 and the node 504 can communicate via a link 524; the UE 508 and the node 506 can communicate via a link 526; and the UE 510 and the node 506 can communicate via a link 528.

[0080] like Figure 55 and further indicated by reference numeral 540, the central entity 502 may receive resource utilization reports. For example, the central entity 502 may receive one or more resource utilization reports from one or more child nodes of the central entity 502, such as node 504, node 506, UE 508, UE 510, etc. In some aspects, the nodes, such as node 504, node 506, UE 508, UE 510, etc., may determine resource utilization and may provide resource utilization reports to enable the central entity 502 to determine a schedulable resource bitmap. For example, the node 504 may receive a first schedulable resource bitmap from the central entity 502, may use one or more schedulable resources in the multi-link network, and may provide a resource utilization report indicating utilization of the schedulable resources identified by the first schedulable resource bitmap. In this case, the central entity 502 may determine a second schedulable resource bitmap for node 504 based at least in part on the resource utilization report (e.g., and one or more other resource utilization reports from one or more other child nodes of the central entity 502), thereby enabling centralized dynamic reconfiguration of scheduling of the multi-link network.

[0081] like Figure 5 542, the central entity 502 may determine a schedulable resource bitmap. For example, the central entity 502 may determine one or more schedulable resource bitmaps for the nodes 504, 506, UEs 508, 510, etc. In some aspects, the central entity 502 may determine the schedulable resource bitmap based at least in part on resource utilization reports received from the nodes 504, 506, UEs 508, 510, etc. and propagated upstream by the nodes 504, 506, UEs 508, 510, etc.

[0082] In some aspects, the central entity 502 may determine the schedulable resource bitmap based at least in part on the policy in the multi-link network. For example, for nodes with direct connections (e.g., nodes 504 and 506 via link 524), the central entity 502 may determine a first schedulable resource bitmap for node 504 and a second schedulable resource bitmap for node 506. In this case, the first schedulable resource bitmap and the second schedulable resource bitmap may be determined so that the schedulable resources indicated to nodes 504 and 506 do not overlap in time. In other words, the first schedulable resource set indicated to node 504 via the corresponding schedulable resource bitmap does not overlap in time with the second schedulable resource set indicated to node 506. In this way, a half-duplex policy may be implemented for a multi-link network.

[0083] Additionally or alternatively, as indicated by reference numeral 544, the central entity 502 may determine a first schedulable resource bitmap and a second schedulable resource bitmap for the node 504 and the node 506, respectively, such that the schedulable resources indicated to the nodes 504 and 506 overlap in time but are associated with a coordinated semi-static time slot format configuration. In this case, the corresponding schedulable resource bitmap causes the node 504 to receive from both the central entity 502 and the node 506 in the third time slot and transmit to both the central entity 502 and the node 506 in the fourth time slot. In this way, the central entity 502 can implement a half-duplex strategy for the multi-link network.

[0084] In some aspects, the central entity 502 may determine the schedulable resource bitmap based at least in part on a particular scheduling granularity. For example, the central entity 502 may determine the schedulable resource bitmap to indicate scheduling for one or more time slots (e.g., a single time slot or a group of time slots), which may reduce signaling overhead relative to scheduling on a per-symbol or per-symbol group basis, thereby improving network utilization. Additionally or alternatively, the central entity 502 may determine the schedulable resource bitmap to indicate scheduling for one or more symbols (e.g., a single symbol or a group of symbols), which may enable greater flexibility in scheduling modes relative to scheduling on a per-slot or per-slot group basis, thereby improving latency. In some aspects, the central entity 502 may determine parameters (e.g., a particular bit indicator) of the schedulable resource bitmap based at least in part on a channel type. For example, the central entity 502 may determine a first schedulable resource bitmap parameter for resources of a physical downlink control channel (PDCCH), a second schedulable resource bitmap parameter for resources of a physical uplink control channel (PUCCH), and so on.

[0085] In some aspects, the central entity 502 may determine the schedulable resource bitmap and / or one or more parameters of the schedulable resource bitmap based at least in part on a radio resource control (RRC) configuration of one or more other nodes (such as the node 504, the node 506, the UE 508, the UE 510, etc.). In some aspects, the central entity 502 may determine the schedulable resource bitmap based at least in part on the resource allocation. For example, the central entity 502 may determine the schedulable resource bitmap to apply to all allocated resources. In this case, one or more allocated resources corresponding to the non-schedulable resources associated with the schedulable resource bitmap are invalid.

[0086] Additionally or alternatively, the central entity 502 may determine the schedulable resource bitmap based at least in part on the channel type or resource allocation type. For example, the central entity 502 may determine that some allocated resources (such as synchronization signal block (SSB) resources, type 0 PDCCH resources, PRACH resources, etc.) are classified as always schedulable resources, and may determine the schedulable resource bitmap to indicate the allocated resources that are not classified as always schedulable resources. In this case, the node 504 may apply the schedulable resource bitmap to the portion of the resource allocation that is not classified as always schedulable resources. In some aspects, the central entity 502 may dynamically indicate a strategy for resolving conflicts between the schedulable resource bitmap and resource allocations associated with, for example, a particular type of channel.

[0087] In some aspects, the central entity 502 may determine attribute parameters of the schedulable resource bitmap. For example, the central entity 502 may determine attribute parameters of a first schedulable resource bitmap indicating that the first schedulable resource bitmap is applicable to an access link of the node 506, and may determine attribute parameters of a second schedulable resource bitmap indicating that the second schedulable resource bitmap is applicable to a backhaul link of the node 506. In this way, the central entity 502 may determine a schedulable resource bitmap for a node associated with multiple links.

[0088] Similarly, the central entity 502 may configure attribute parameters indicating that a particular schedulable resource bitmap is applicable to all links of the node 506, all access links of the node 506, a subset of access links of the node 506, all backhaul links of the node 506, a subset of backhaul links of the node 506, etc. Additionally or alternatively, the central entity 502 may determine attribute parameters identifying allocation granularity (e.g., whether the schedulable resource bitmap is applied on a per-slot basis, on a per-symbol basis, etc.), time parameters (e.g., whether the schedulable resource bitmap is applicable to a specific time segment, a specific scheduling type (such as FDM), etc.), channel type parameters (e.g., whether the schedulable resource bitmap is applicable to SSB, PDCCH, PDSCH, physical uplink shared channel (PUSCH), PRACH, etc.), traffic type parameters (e.g., whether the schedulable resource bitmap is applicable to enhanced mobile broadband (eMBB) traffic, ultra-reliable low latency communication (URLLC) traffic, etc.), etc.

[0089] like Figure 5546, the central entity 502 may provide a schedulable resource bitmap. For example, the central entity 502 may provide the schedulable resource bitmap to the node 504. In some aspects, the central entity 502 may provide multiple schedulable resource bitmaps. For example, the central entity 502 may provide a first schedulable resource bitmap to the node 504, a second schedulable resource bitmap to the node 506, and so on. In this way, the central entity 502 may schedule communications on the multi-link network so that policies (such as half-duplex constraints) are satisfied.

[0090] In some aspects, the central entity 502 may provide a schedulable resource bitmap via a specific interface. For example, the central entity 502 may provide a first schedulable resource bitmap to the node 504 via an F1 application protocol (F1-AP) interface, and may provide a second schedulable resource bitmap to the node 506 via the F1-AP interface. Similarly, the central entity 502 may receive a resource utilization report from the node 504 and / or the node 506, for example, via a corresponding F1-AP interface. In some aspects, a set of interaction rules for schedulable resource bitmaps and resource allocation may be stored in a data structure (e.g., a data structure of the central entity 502, the node 504, the node 506, etc.), and may be signaled using the F1-AP interface. Additionally or alternatively, the set of interaction rules for interpreting the schedulable resource bitmap may be dynamically indicated based at least in part on the selection of one or more interaction rules in a set of candidate interaction rules.

[0091] In some aspects, the set of interaction rules may specify that the schedulable resource bitmap applies to all resource allocations and any allocated resources associated with non-schedulable resources are invalid. Additionally or alternatively, the set of interaction rules may establish that resource allocations associated with synchronization signal blocks (SSBs), type 0 physical downlink control channels (PDCCHs), physical random access channels (PRACHs), etc. are to be considered schedulable resources and the schedulable resource bitmap applies only to the remaining resource allocations. Additionally or alternatively, the set of interaction rules may establish that a mobile terminal (MT) of a node (e.g., node 504, node 506, etc.) is to cancel operations that conflict with operations of a co-located distributed unit (DU) of the node on the schedulable resources of the DU.

[0092] In some aspects, the interaction rules may define that time resources and channel allocations (e.g., SSB, type 0PDCCH, PRACH, etc.) with threshold performance impacts are always schedulable. In some aspects, the interaction rules may define that resources will be interpreted as schedulable resources for a specific type of link. For example, in a synchronous network, resources allocated by SSB or type 0PDCCH may be schedulable for links of access types. In some aspects, the schedulable mode of the schedulable resource bitmap may be constrained at least in part based on potential conflicts with resource allocations. In some aspects, a central unit (CU) (e.g., central entity 502) and a node (e.g., node 504, node 506, etc.) may allocate resources at least in part based on a schedulable mode.

[0093] In some aspects, a CU (e.g., central entity 502), MT (e.g., node 504, node 506, etc.), DU (e.g., node 504, node 506, etc.) may resolve specific conflicts between schedulable resource bitmaps and resource allocations. For example, when a radio resource control (RRC) configured allocation (e.g., a periodic or semi-persistent allocation) with allocated resources overlapping with non-schedulable resources is signaled, the DU may cancel transmission or reception on non-schedulable resources based at least in part on the schedulable resource bitmap. Similarly, in the case where the schedulable resource bitmap has not been signaled at the NR Uu interface, a child node of the DU may suppress transmission or reception on non-schedulable resources.

[0094] In some aspects, based at least in part on receiving the schedulable resource bitmap, a node (such as the node 504 or the node 506) can configure layer 2 (L2) scheduling. For example, the node 506 can determine the L2 scheduling of the link 526 with the UE 508 based at least in part on the schedulable resource bitmap to meet the policy of the multi-link network (such as a half-duplex policy). In this way, the central entity 502 can perform centralized resource partitioning of the multi-link network.

[0095] As indicated above, Figure 5 are provided as examples. Other examples may differ from those described in Figure 5 Examples described.

[0096] Figure 6 6 is a diagram illustrating an example 600 of dynamic resource coordination according to various aspects of the present disclosure. Figure 6 As shown in , example 600 includes a parent node 602, a node 604, and a child node 606 communicating in a multi-link network. In some aspects, parent node 602 and node 604 may communicate via link 612, and node 604 and child node 606 may communicate via link 614.

[0097] like Figure 6 622, node 604 may receive an extended SFI from parent node 602. For example, node 604 may receive the extended SFI from parent node 602 via link 612. In some aspects, the extended SFI may include a null field. For example, parent node 602 may set a null (N) value for the field to dynamically indicate to node 604 (e.g., a child of parent node 602) that the resource is not schedulable. In some aspects, the null value may be applicable to a particular type of resource. For example, for resources allocated for synchronization signal blocks (SSBs), physical random access channels (PRACHs), physical downlink control channels (PDCCH) type 0, etc., parent node 602 may not set the null value.

[0098] In some aspects, the extended SFI may include one or more other values, such as a downlink (↓) value, an uplink value (↑), a flexible (x) value (e.g., which may be flexibly used for downlink or uplink), etc. In this way, the parent node 602 may indicate the scheduling to the node 604. In some aspects, the node 604 may receive the extended SFI based at least in part on the dynamic coordination being configured for the network. For example, a first node (e.g., node 604) may transmit a dynamic coordination flag to a second node (e.g., parent node 602) to indicate that dynamic coordination is to be enabled based at least in part on the capabilities of the first node and / or the second node.

[0099] like Figure 6 6 and further shown by reference numeral 624, node 604 may receive a blanking adjustment request from child node 606. For example, node 604 may receive a blanking adjustment request from child node 606 via link 614. In some aspects, the blanking adjustment request may include a value indicating a change to the blanking field of the extended SFI message. For example, child node 606 may indicate an increase in the number of blanking fields or a decrease in the number of blanking fields. Additionally or alternatively, child node 606 may indicate that no change is to be applied to the blanking field. In some aspects, node 604 may receive the blanking adjustment request via a physical uplink control channel (PUCCH) message, a media access control (MAC) control element (CE) message, or the like.

[0100] like Figure 6626, the node 604 may determine the extended SFI based at least in part on the received SFI and the received blanking adjustment request. For example, the node 604 may determine the extended SFI based at least in part on the value of the extended SFI received from the parent node 602 and the value of the blanking adjustment request received from the child node 606. In this way, the node 604 uses the extended SFI and the blanking adjustment request to dynamically coordinate communications in the multi-link network. In some aspects, the node 604 may determine the extended SFI to implement one or more policies for the multi-link network. For example, the node 604 may determine the extended SFI to cause the scheduling of the link 614 and the link 612 to meet the half-duplex policy.

[0101] like Figure 6 6 and further indicated by reference numeral 628, the node 604 may provide the determined extended SFI to the child node 606. For example, the node 604 may provide the determined extended SFI to the child node 606 (and / or to one or more other child nodes). In some aspects, the node 604 may provide the determined SFI to the child node 606 to indicate to the child node 606 a schedule for monitoring opportunities (e.g., a set of 20 time slots of a channel associated with the link 614).

[0102] In some aspects, the determined extended SFI may be associated with a specific delay corresponding to, for example, the PDCCH decoding capability of the node 604. For example, the node 604 may be associated with a specific delay in decoding the PDCCH conveying the received extended SFI. In this case, the communication schedule may account for the specific delay by including one or more repeated time slots. For example, for a one-slot delay per hop in a multi-link network having a set of 4 hierarchical nodes, a first monitoring opportunity at a first node may be associated with 4 repeated time slots, a second monitoring opportunity at a second node may be associated with 3 repeated time slots, a third monitoring opportunity at a third node may be associated with 2 repeated time slots, and a fourth monitoring opportunity at a fourth node may be associated with 1 repeated time slot. In this way, each node (e.g., parent node 602, node 604, child node 606, etc.) may determine a time slot format for monitoring opportunities based at least in part on the extended SFI.

[0103] like Figure 6 6 and further indicated by reference numeral 630, the node 604 may provide the received blanking adjustment request to the parent node 602. For example, the node 604 may propagate the received blanking adjustment request to the parent node 602 to enable the parent node 602 to adjust the scheduling of the next extended SFI to be provided to the node 604 to schedule the link 612 of the parent node 602 and the node 604. In this way, the node 604 implements uplink feedback for dynamic coordination in a multi-link network.

[0104] As indicated above, Figure 6 are provided as examples. Other examples may differ from those described in Figure 6 Examples described.

[0105] Figure 7 is a diagram illustrating an example process 700, performed, for example, by a central entity, in accordance with various aspects of the present disclosure. Example process 700 is an example of a central entity (eg, BS 110, UE 120, central entity 502, etc.) performing centralized resource partitioning.

[0106] like Figure 7 As shown in , in some aspects, process 700 may include: determining a set of schedulable resources for a plurality of links associated with a plurality of nodes of a multi-link network, wherein at least one of the plurality of nodes is not a parent node or a child node of the central entity (block 710). For example, a central entity (e.g., using controller / processor 240, controller / processor 280, etc.) may determine a set of schedulable resources for a plurality of links associated with a plurality of nodes of a multi-link network, wherein at least one of the plurality of nodes is not a parent node or a child node of the central entity, as described above with reference to Figure 4A , 4B , 4C, 5 and / or 6 are described in more detail.

[0107] like Figure 7 As shown in , in some aspects, process 700 may include: providing scheduling information to the plurality of nodes to schedule communications on the plurality of links based at least in part on determining the set of schedulable resources (block 720). For example, a central entity (e.g., using controller / processor 240, transmit processor 220, TX MIMO processor 230, MOD 232, antenna 234, controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, etc.) may provide scheduling information to the plurality of nodes to schedule communications on the plurality of links based at least in part on determining the set of schedulable resources, as described above with reference to Figure 4A , 4B , 4C, 5 and / or 6 are described in more detail.

[0108] Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0109] In a first aspect, the central entity is configured to determine a schedulable resource set based at least in part on a resource utilization report received from another node in the plurality of nodes. In a second aspect, either alone or in combination with the first aspect, the scheduling information is a schedulable resource bit map, wherein the bits of the schedulable resource bit map indicate whether the corresponding resource unit can be scheduled by a specific node in the plurality of nodes. In a third aspect, either alone or in combination with any one of the first and second aspects, a message for identifying a schedulable resource set or a message for conveying scheduling information received by the central entity is an F1 application protocol (F1-AP) message. In a fourth aspect, either alone or in combination with any one of the first to third aspects, a first subset of schedulable resource sets is associated with a first direction in the network, and a second subset of schedulable resource sets is associated with a second direction in the network. In a fifth aspect, either alone or in combination with any one of the first to fourth aspects, the first subset and the second subset do not overlap in the time domain.

[0110] In a sixth aspect, alone or in combination with any one of the first to fifth aspects, the first subset and the second subset overlap in time and are associated with a coordinated semi-static timeslot format configuration. In a seventh aspect, alone or in combination with any one of the first to sixth aspects, the central entity is configured to at least one of: schedule communications on a per-time slot basis, schedule communications on a per-time slot group basis, schedule communications on a per-code symbol basis, or schedule communications on a per-code symbol group basis. In an eighth aspect, alone or in combination with any one of the first to seventh aspects, the central entity is configured to: determine scheduling information based at least in part on at least one radio resource configuration of the plurality of nodes.

[0111] In a ninth aspect, either alone or in combination with any one of the first to eighth aspects, the central entity is configured to: receive a resource utilization report identifying utilization of one or more schedulable resources, and the resource utilization report is determined at least in part based on layer 2 (L2) scheduling. In a tenth aspect, either alone or in combination with any one of the first to ninth aspects, the set of schedulable resources is determined at least in part based on at least one of: time resources, channel allocation, link type, scheduling mode capability parameters, resource availability, allocation type, or aggregation parameters. In an eleventh aspect, either alone or in combination with any one of the first to tenth aspects, the scheduling information is associated with an attribute parameter, and the attribute parameter identifies at least one of: allocation granularity, link association, time segment, channel type, or traffic type.

[0112] In the twelfth aspect, alone or in combination with any one of the first to eleventh aspects, the scheduling information is associated with one or more links of the multiple links, and the one or more links include at least one of the following: the multiple links, a subset of the multiple links, an access link set of the multiple links, and a return link set of the multiple links. In the thirteenth aspect, alone or in combination with any one of the first to twelfth aspects, the scheduling information is associated with a channel type, and the channel type includes at least one of the following: a synchronization signal block channel, a physical downlink control channel, a physical downlink shared channel, or a physical uplink shared channel. In the fourteenth aspect, alone or in combination with any one of the first to thirteenth aspects, the scheduling information is configured for a specific channel type at least in part based on explicit configuration information included in the scheduling information or implicit configuration information associated with a radio resource configuration message.

[0113] In a fifteenth aspect, either alone or in combination with any one of the first to fourteenth aspects, the central entity is configured to: follow one or more interaction rules for schedulable resource sets. In a sixteenth aspect, either alone or in combination with any one of the first to fifteenth aspects, the one or more interaction rules define schedulable resource sets as applicable to the entire resource allocation. In a seventeenth aspect, either alone or in combination with any one of the first to sixteenth aspects, the one or more interaction rules define a specific type of channel as a schedulable resource, and the specific type of channel includes at least one of the following: a synchronization signal block, a type 0 physical downlink control channel, or a physical random access channel.

[0114] In an eighteenth aspect, either alone or in combination with any one of the first to seventeenth aspects, the one or more interaction rules define a specific type of link. In a nineteenth aspect, either alone or in combination with any one of the first to eighteenth aspects, providing scheduling information includes: prompting a first node among the plurality of nodes to cancel an operation that conflicts with an operation of a second node among the plurality of nodes according to the one or more interaction rules. In a twentieth aspect, either alone or in combination with any one of the first to nineteenth aspects, a first subset of a schedulable resource set is associated with a first scheduling node among the plurality of nodes, and a second subset of a schedulable resource set is associated with a second scheduling node among the plurality of nodes, and the first scheduling node is directly connected to the second scheduling node.

[0115] although Figure 7 An example block diagram of process 700 is shown, but in some aspects, process 700 may include Figure 7 Additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in the process 700. Additionally or alternatively, two or more blocks of the process 700 may be executed in parallel.

[0116] Figure 8 is a diagram illustrating an example process 800, performed, for example, by a node, in accordance with various aspects of the present disclosure. The example process 800 is an example of a node of a network (eg, BS 110, UE 120, node 604, etc.) performing dynamic resource coordination.

[0117] like Figure 8 As shown in , in some aspects, process 800 may include: determining an extended slot format indicator of the node based at least in part on an extended slot format indicator received from a parent node of the node and a blanking adjustment request received from a child node of the node, wherein the extended slot format indicator of the node includes a blanking field that identifies non-schedulable resources of the node (block 810). For example, a node (e.g., using controller / processor 240, controller / processor 280, etc.) may determine an extended slot format indicator of the node based at least in part on an extended slot format indicator received from a parent node of the node and a blanking adjustment request received from a child node of the node, wherein the extended slot format indicator of the node includes a blanking field that identifies non-schedulable resources of the node, as described above with reference to Figure 4A , 4B , 4C, 5 and / or 6 are described in more detail.

[0118] like Figure 8 As shown in , in some aspects, process 800 may include: providing the determined extended slot format indicator to the child nodes of the node (block 820). For example, the node (e.g., using controller / processor 240, transmit processor 220, TX MIMO processor 230, MOD 232, antenna 234, controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, etc.) may provide the determined extended slot format indicator to the child nodes of the node, as described above with reference to Figure 4A , 4B , 4C, 5 and / or 6 are described in more detail.

[0119] like Figure 8 As shown in , in some aspects, process 800 may include providing the received blanking adjustment request to a parent node of the node (block 830). For example, the node (e.g., using controller / processor 240, transmit processor 220, TX MIMO processor 230, MOD 232, antenna 234, controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, etc.) may provide the received blanking adjustment request to the parent node of the node, as described above with reference to Figure 4A , 4B , 4C, 5 and / or 6 are described in more detail.

[0120] Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0121] In a first aspect, the node is configured to: receive the received blanking adjustment request message in a physical uplink control channel or a medium access control (MAC) control element (CE). In a second aspect, alone or in combination with the first aspect, the number of repeated time slots in the extended time slot format indicator of the node relative to the received extended time slot format indicator of the parent node corresponds to the physical downlink control channel decoding capability and the physical downlink channel monitoring opportunity scheduling.

[0122] In a third aspect, either alone or in combination with any one or more of the first and second aspects, the node is configured to use an extended slot format indicator based at least in part on a value of a dynamic coordination flag. In a fourth aspect, either alone or in combination with any one or more of the first to third aspects, the node is configured to define one or more slots as blanked slots and one or more symbols as blanked symbols. In a fifth aspect, either alone or in combination with any one or more of the first to fourth aspects, the blanked slot is not a resource allocated for at least one of: a synchronization signal block, a physical random access channel, or a type 0 physical downlink control channel.

[0123] although Figure 8 An example block diagram of process 800 is shown, but in some aspects, process 800 may include Figure 8 Additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in the process 800. Additionally or alternatively, two or more blocks of process 800 may be executed in parallel.

[0124] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired by practice of the various aspects.

[0125] As used herein, the term component is intended to be broadly interpreted as hardware, firmware, or a combination of hardware and software. As used herein, a processor is implemented with hardware, firmware, or a combination of hardware and software.

[0126] Some aspects are described herein in conjunction with a threshold value. As used herein, satisfying a threshold value may refer to a value being greater than a threshold value, greater than or equal to a threshold value, less than a threshold value, less than or equal to a threshold value, equal to a threshold value, not equal to a threshold value, and the like.

[0127] It will be apparent that the systems and / or methods described herein can be implemented in different forms of hardware, firmware, or a combination of hardware and software. Actual dedicated control hardware or software code for implementing these systems and / or methods does not limit the various aspects. Thus, the operation and behavior of these systems and / or methods are described herein without reference to specific software code - it is understood that software and hardware can be designed to implement these systems and / or methods based at least in part on the description herein.

[0128] Although specific feature combinations are described in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. In fact, many of these features can be combined in a manner not specifically described in the claims and / or undisclosed in the specification. Although each dependent claim listed below can be directly subordinate to only one claim, the disclosure of various aspects includes that each dependent claim is combined with each other claim in this group of claims. The phrase quoting "at least one of" a column of items refers to any combination of these items, including single members. As an example, "at least one of a, b or c" is intended to cover: a, b, c, ab, ac, bc and abc, and any combination with multiple identical elements (for example, aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc and cCc, or any other sorting of a, b and c).

[0129] Elements, actions or instructions used herein should not be interpreted as critical or necessary unless explicitly described as such. Moreover, as used herein, the articles "one" and "a" are intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the terms "set (set)" and "group" are intended to include one or more items (e.g., related items, non-related items, combinations of related and non-related items, etc.), and can be used interchangeably with "one or more". In the case of being intended for only one project, the term "only one" or similar language is used. Moreover, as used herein, the terms "having", "containing", "including" etc. are intended to be open terms. In addition, the phrase "based on" is intended to mean "based at least in part on", unless otherwise explicitly stated.

Claims

1. A wireless communication method performed by a node of a network, comprising: receiving an extended slot format indicator (SFI) from a parent node of the node, the extended SFI providing a dynamic indication of whether a resource set is schedulable or non-schedulable; as well as One or more resources in the set of resources are scheduled for a link between the node and a child node of the node based at least in part on the dynamic indication.

2. The method of claim 1, wherein: The extended SFI is based at least in part on a radio resource control, RRC, configuration.

3. The method of claim 1, wherein: The scheduled one or more resources are on at least one of: a per-slot basis, a per-slot group basis, a per-symbol basis, or a per-symbol group basis.

4. The method of claim 1, wherein: Scheduling the one or more resources includes: The one or more resources in the set of resources are scheduled according to a set of time slots of a channel associated with the link between the node and the subnode.

5. The method of claim 1, further comprising: The scheduled one or more resources are provided to the child node.

6. The method of claim 5, further comprising: defining one or more time slots as blanked time slots and defining one or more codewords as blanked codewords, wherein the extended time slot format indicator includes the one or more time slots and the one or more codewords, and Wherein providing the scheduled one or more resources to the child node is based at least in part on defining the one or more time slots and the one or more symbols.

7. The method of claim 6, wherein: The blanked time slot is not a resource allocated for at least one of: a synchronization signal block, a physical random access channel, or a type-0 physical downlink control channel.

8. The method of claim 1, further comprising: The scheduled one or more resources are provided to another node that is another child node of the parent node.

9. The method of claim 8, wherein: Receiving the extended SFI comprises: receiving the extended SFI via a first interface; and Wherein, providing the scheduled one or more resources includes: The scheduled one or more resources are provided to the node via a second interface different from the first interface.

10. The method of claim 1, wherein: Scheduling the one or more resources includes: The one or more resources in the set of resources are scheduled for the link between the node and the child node of the node based at least in part on a value of a dynamic coordination flag associated with the dynamic indication.

11. The method of claim 1, wherein: The child node is a user equipment.

12. A node for wireless communication, comprising: Memory; as well as one or more processors coupled to the memory, the one or more processors configured to: receiving an extended slot format indicator (SFI) from a parent node of the node, the extended SFI providing a dynamic indication of whether a resource set is schedulable or non-schedulable; as well as One or more resources in the set of resources are scheduled for a link between the node and a child node of the node based at least in part on the dynamic indication.

13. The node of claim 12, wherein: The extended SFI is based at least in part on a radio resource control, RRC, configuration.

14. The node of claim 12, wherein: The scheduled one or more resources are on at least one of: a per-slot basis, a per-slot group basis, a per-symbol basis, or a per-symbol group basis.

15. The node of claim 12, wherein: To schedule the one or more resources, the one or more processors are configured to: The one or more resources in the set of resources are scheduled according to a set of time slots of a channel associated with the link between the node and the subnode.

16. The node of claim 12, wherein: The one or more processors are further configured to: The scheduled one or more resources are provided to the child node.

17. The node of claim 16, wherein: The one or more processors are further configured to: defining one or more time slots as blanked time slots and defining one or more codewords as blanked codewords, wherein the extended time slot format indicator includes the one or more time slots and the one or more codewords, and Wherein providing the scheduled one or more resources to the child node is based at least in part on defining the one or more time slots and the one or more symbols.

18. The node of claim 17, wherein: The blanked time slot is not a resource allocated for at least one of: a synchronization signal block, a physical random access channel, or a type-0 physical downlink control channel.

19. The node of claim 12, wherein: The one or more processors are further configured to: The scheduled one or more resources are provided to another node that is another child node of the parent node.

20. The node of claim 19, wherein: To receive the extended SFI, the one or more processors are configured to: The extended SFI is received via a first interface, and wherein, to provide the scheduled one or more resources, the one or more processors are configured to: The scheduled one or more resources are provided to the node via a second interface different from the first interface.

21. The node of claim 12, wherein: To schedule the one or more resources, the one or more processors are configured to: The one or more resources in the set of resources are scheduled for the link between the node and the child node of the node based at least in part on a value of a dynamic coordination flag associated with the dynamic indication.

22. The node of claim 12, wherein: The child node is a user equipment.

23. A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising: One or more instructions that, when executed by one or more processors of a node, cause the node to: receiving an extended slot format indicator (SFI) from a parent node of the node, the extended SFI providing a dynamic indication of whether a resource set is schedulable or non-schedulable; as well as One or more resources in the set of resources are scheduled for a link between the node and a child node of the node based at least in part on the dynamic indication.

24. The non-transitory computer readable medium of claim 23, wherein: The extended SFI is based at least in part on a radio resource control, RRC, configuration.

25. A device for wireless communication, comprising: means for receiving an extended slot format indicator (SFI) from a parent node of the node, the extended SFI providing a dynamic indication of whether a set of resources is schedulable or non-schedulable; as well as Means for scheduling one or more resources in the set of resources for a link between the node and a child node of the node based at least in part on the dynamic indication.

26. The apparatus of claim 25, wherein: The extended SFI is based at least in part on a radio resource control, RRC, configuration.

27. The apparatus of claim 25, wherein: The scheduled one or more resources are on at least one of: a per-slot basis, a per-slot group basis, a per-symbol basis, or a per-symbol group basis.

28. The apparatus of claim 25, wherein: The means for scheduling the one or more resources comprises: means for scheduling the one or more resources in the set of resources according to a set of time slots of a channel associated with the link between the node and the subnode.

29. The apparatus of claim 25, further comprising: Means for providing the scheduled one or more resources to the child node.

Images