Support scheduling instructions

Abstract

A base station central unit (CU) may receive measurement reports from one or more user equipments (UEs). The CU may identify a scheduling plan indication (SPI) for one or more scheduling nodes in the network based at least in part on the received measurement reports. The SPI may specify a scheduling state mode within a time period, which is used by the scheduling node to schedule communication resources for one or more UEs in the network. The scheduling state may specify a UE or other communication resource for a transmission scheduling decision made by a scheduling node (e.g., based on an interference profile determined according to the received measurement reports), or may specify a beam pattern for a beamforming procedure performed by a scheduling node. In some cases, a scheduling node may identify a tentative SPI, which the CU may pass between other scheduling nodes to implement a distributed scheduling coordination scheme.

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. patent application No. 16 / 418,824, entitled “SUPPORTING SCHEDULING PLAN INDICATIONS,” filed by LUO et al. on May 21, 2019, and U.S. provisional patent application No. 62 / 677,533, entitled “SUPPORTING SCHEDULING PLAN INDICATIONS,” filed by LUO et al. on May 29, 2018, each of which is assigned to the assignee of this application and is expressly incorporated herein. Background Art

[0003] The following relates generally to wireless communications and, more particularly, to supporting Scheduling Plan Indication (SPI).

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasting, etc. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems), and fifth generation (5G) systems, which may be referred to as new radio (NR) systems. These systems may use various technologies, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), or discrete Fourier transform spread OFDM (DFT-S-OFDM). A wireless multiple access communication system may include several base stations or network access nodes, each of which simultaneously supports the communication of multiple communication devices, which may be referred to as user equipment (UE).

[0005] In some wireless communication systems (e.g., 5G New Radio (NR) systems), a base station may include a central unit (CU) and a distributed unit (DU), wherein one or more DUs associated with a base station may be partially controlled by the CU associated with the base station. The base station CU may be a component of a database, a data center, a core network, or a network cloud. In some cases (e.g., in an integrated access backhaul (IAB) network), a network node may communicate with a base station CU (e.g., a donor base station) via a backhaul link (e.g., a wired backhaul or a wireless backhaul). The donor base station (e.g., an IAB donor) may be in communication with one or more IAB nodes that operate as a base station DU relative to the IAB donor. These relay mechanisms may forward received traffic to other devices, extend the wireless access range of one or more base stations, and the like. However, in some cases, resource scheduling within an access network that implements such relay technology may be associated with increased complexity, such as due to interference between adjacent beams of adjacent cells and UEs.

[0006] Overview

[0007] The described technology relates to improved methods, systems, devices or apparatuses (equipment) that support scheduling plan indication (SPI). In general, the described technology provides signaling of SPI information to coordinate scheduling in a wireless communication system that implements distributed unit (DU) technology. A core network may be associated with one or more access networks (ANs). In a network that employs distributed node technology, each AN may include a central unit (CU) (e.g., associated with a base station) and one or more scheduling nodes (e.g., DUs also associated with the base station, for example) for scheduling communications with user equipment (UE) within the network.

[0008] In some examples, the network may employ centralized intra-AN scheduling coordination via SPI. The CU may receive measurement reports from one or more UEs. The CU may identify an SPI for one or more scheduling nodes (e.g., DUs) in the network based at least in part on the received measurement reports. The SPI may specify a scheduling state mode within a time period, which is to be used by one or more scheduling nodes to schedule communication resources for one or more UEs in the network (e.g., the SPI mode may be set by the CU based on an interference profile determined based on the received measurement reports). The scheduling state (e.g., for a given time unit) may specify a UE, beam index, or other communication resource to be used by the scheduling node to make a transmission scheduling decision. Additionally or alternatively, the scheduling state may coordinate a beam index or beam pattern for a beamforming procedure performed by a scheduling node.

[0009] In some examples, the network may employ distributed intra-AN scheduling coordination via SPI. The scheduling node may identify experimental SPIs, and the CU may take these experimental SPIs into consideration when determining the SPI. The scheduling state associated with the experimental SPI transmitted by the scheduling node may depend on the capability or functional division between the CU and the scheduling nodes within the network (e.g., the experimental SPI may depend on the role or responsibility assumed by the scheduling node in making scheduling decisions). The CU may receive the experimental SPI from one or more scheduling nodes, and may update the experimental SPI (e.g., based on an interference profile) or may pass or forward the experimental SPI to other scheduling nodes (e.g., the CU may pass the experimental SPI between the scheduling nodes, and each scheduling node may take each other's experimental SPI into consideration when making scheduling decisions). For example, the scheduling node may prepare an updated SPI based on the experimental SPIs of other scheduling nodes, and in some cases may then distribute the updated SPI. Such techniques may provide a distributed scheduling coordination solution for scheduling nodes.

[0010] In some examples, the network may employ inter-AN scheduling coordination via SPI (e.g., inter-AN scheduling coordination may be employed in addition to intra-AN scheduling coordination). For example, in a distributed inter-AN scheduling coordination scheme, two or more CUs may exchange tentative SPIs with each other, and each CU may modify the SPI based on the tentative SPIs associated with the other CUs, which may then signal the SPI to their respective scheduling nodes. In a centralized inter-AN scheduling coordination scheme, each CU may signal the tentative SPI to a network node, and the network node may modify the SPI based on all received tentative SPIs, and may signal the updated SPI to each CU (e.g., each CU may then indicate the updated SPI to their respective scheduling nodes).

[0011] A wireless communication method is described. The method may include: receiving a measurement report of a UE, wherein the measurement report includes measured values ​​of at least one beam of a cell measured by the UE. The method may further include: identifying an indication of a scheduling plan for a scheduling node, the indication of the scheduling plan specifying a scheduling state mode within a time period, wherein the indication of the scheduling plan is based on the measurement report and is to be used by the scheduling node to schedule communication resources for the UE.

[0012] An apparatus for wireless communication is described. The apparatus may include a processor, a memory in electronic communication with the processor, and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to: receive a measurement report of a UE, wherein the measurement report includes a measured value of at least one beam of a cellular cell measured by the UE. The instructions are executable by the processor to further cause the apparatus to: identify an indication of a scheduling plan for a scheduling node, the indication of the scheduling plan specifying a scheduling state mode within a time period, wherein the indication of the scheduling plan is based on the measurement report and is to be used by the scheduling node to schedule communication resources for the UE.

[0013] Another apparatus for wireless communication is described. The apparatus may include: means for receiving a measurement report of a UE, wherein the measurement report includes a measured value of at least one beam of a cell measured by the UE. The apparatus may further include: means for identifying an indication of a scheduling plan for a scheduling node, the indication of the scheduling plan specifying a scheduling state mode within a time period, wherein the indication of the scheduling plan is based on the measurement report and is to be used by the scheduling node to schedule communication resources for the UE.

[0014] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor for the following operations: receiving a measurement report of a UE, wherein the measurement report includes a measured value of at least one beam of a cellular cell measured by the UE. The code may further include instructions executable by the processor for the following operations: identifying an indication of a scheduling plan for a scheduling node, the indication of the scheduling plan specifying a scheduling state mode within a time period, wherein the indication of the scheduling plan is based on the measurement report and is to be used by the scheduling node to schedule communication resources for the UE.

[0015] In some examples of the methods, devices (equipment) and non-transient computer-readable media described herein, the scheduling state mode includes a scheduling information state, or a flexible state, or an invalid state, or a combination thereof. In some examples of the methods, devices (equipment) and non-transient computer-readable media described herein, for the flexible state, the scheduling node may be allowed to schedule any UE, or any beam direction, or a combination thereof. In some examples of the methods, devices (equipment) and non-transient computer-readable media described herein, for the invalid state, the scheduling node may be prevented from scheduling all UEs, or all beam directions, or a combination thereof.

[0016] In some examples of the methods, devices (equipment), and non-transient computer-readable media described herein, the time period includes one or more time slots or mini-time slots. In some examples of the methods, devices (equipment), and non-transient computer-readable media described herein, the indication of the scheduling plan identifies values ​​for scheduling for a scheduling state, and these values ​​include a set of UE indexes, or a set of beam indexes, or a set of angle values, or a set of position values, or a combination thereof. In some examples of the methods, devices (equipment), and non-transient computer-readable media described herein, the indication of the scheduling plan schedules data transmission for different UEs, or different beam modes, or a combination thereof for a scheduling state.

[0017] In some examples of the methods, devices (equipment) and non-transitory computer-readable media described herein, the indication of the scheduling plan identifies, for a scheduling state, an allocated resource block, or a buffer status, or a priority, or a communication type, or a modulation and coding scheme (MCS), or a target signal-to-interference and noise ratio (SINR), or a target transmit power, or a target receive power, or a combination thereof.

[0018] Some examples of the methods, devices (equipment), and non-transitory computer-readable media described herein may further include operations, features, devices, or instructions for the following actions: transmitting a measurement report by the scheduling node to the CU, and receiving an indication of a scheduling plan from the CU based on transmitting the measurement report.

[0019] Some examples of the methods, devices (equipment), and non-transitory computer-readable media described herein may further include operations, features, devices, or instructions for the following actions: determining a tentative scheduling plan by a scheduling node, transmitting an indication of the tentative scheduling plan to a CU, and receiving an indication of an updated scheduling plan based on the tentative scheduling plan from the CU, wherein the updated scheduling plan is a scheduling plan for the scheduling node.

[0020] Some examples of the methods, devices (equipment), and non-transitory computer-readable media described herein may further include operations, features, devices, or instructions for the following actions: the first CU transmits an indication of the scheduling plan to the scheduling node, wherein the first CU identifies the indication of the scheduling plan. In some examples of the methods, devices (equipment), and non-transitory computer-readable media described herein, the indication identifying the scheduling plan may include operations, features, devices, or instructions for the following actions: the first CU determines the indication of the scheduling plan based on a received measurement report, and the measurement report is received from the scheduling node.

[0021] In some examples of the methods, apparatus (equipment), and non-transitory computer-readable media described herein, an indication identifying the scheduling plan may include operations, features, apparatus, or instructions for the following actions: receiving an indication of a tentative scheduling plan from the scheduling node, and determining an updated scheduling plan for the scheduling node based on the received indication of the tentative scheduling plan and the received measurement report, wherein the updated scheduling plan may be a scheduling plan for the scheduling node.

[0022] In some examples of the methods, apparatuses (equipment), and non-transitory computer-readable media described herein, the updated scheduling plan for the scheduling node may be further based on at least one additional tentative scheduling plan received from at least one additional scheduling node, and may be further based on at least one additional measurement report from at least one additional UE. Some examples of the methods, apparatuses (equipment), and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for the following actions: receiving an indication of the scheduling plan from a second CU, the received indication being transmitted by the CU to the scheduling node.

[0023] Some examples of the methods, apparatuses (equipment), and non-transitory computer-readable media described herein may further include operations, features, devices, or instructions for the following actions: transmitting the measurement report to a core network node, and receiving an indication of a scheduling plan from the core network node. Some examples of the methods, apparatuses (equipment), and non-transitory computer-readable media described herein may further include operations, features, devices, or instructions for the following actions: transmitting the indication of the scheduling plan by the first CU to the second CU, or the core network node, or a combination thereof, wherein the first CU identifies the indication of the scheduling plan based on the received measurement report.

[0024] Some examples of the methods, devices (equipment), and non-transitory computer-readable media described herein may further include operations, features, devices, or instructions for the following actions: receiving an indication of a tentative scheduling plan from a second scheduling node via a CU at the scheduling node, and determining, by the scheduling node, an updated scheduling plan for the scheduling node based on the received indication of the tentative scheduling plan.

[0025] Some examples of the methods, devices (equipment), and non-transitory computer-readable media described herein may further include operations, features, devices, or instructions for the following actions: identifying, by the scheduling node, at least one priority rule applicable to a scheduling plan for the scheduling node, wherein the updated scheduling plan for the scheduling node may be determined based on an indication of a received tentative scheduling plan and the at least one priority rule.

[0026] Some examples of the methods, devices (equipment), and non-transitory computer-readable media described herein may further include operations, features, devices, or instructions for the following actions: receiving indications of one or more experimental scheduling plans at the CU, each of the one or more experimental scheduling plans for an additional scheduling node, and forwarding the indications of the one or more experimental scheduling plans to the scheduling node.

[0027] Some examples of the methods, devices (equipment), and non-transitory computer-readable media described herein may further include operations, features, devices, or instructions for the following actions: the indication identifying the scheduling plan includes an indication that the scheduling plan is determined by the core network node based on a received measurement report, and the method further includes transmitting the indication of the scheduling plan determined by the core network node to the CU.

[0028] Some examples of the methods, devices (equipment), and non-transitory computer-readable media described herein may further include operations, features, devices, or instructions for the following actions: receiving at least one additional measurement report of at least one additional UE from the scheduling node or at least one second scheduling node at the CU, and determining, by the CU, an interference profile based on the received measurement report and the at least one additional measurement report, wherein the indication of the scheduling plan may be identified based on the determined interference profile. In some examples of the methods, devices (equipment), and non-transitory computer-readable media described herein, the interference profile includes a profile of an interfering UE, or an interfering beam, or a combination thereof.

[0029] Some examples of the methods, devices (equipment), and non-transitory computer-readable media described herein may further include operations, features, devices, or instructions for the following actions: receiving an interference profile from a central unit at the scheduling node, identifying at least one UE, or at least one beam direction, or a combination thereof as interfering based on the received interference profile, and assigning, by the scheduling node, the at least one UE, or the at least one beam direction, or a combination thereof to different time units, or different non-overlapping resource block allocations, or a combination thereof.

[0030] Some examples of the methods, apparatuses (equipment), and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for the following actions: transmitting configuration information for the UE to use to perform measurements on the cell, or at least one additional cell, or a combination thereof. Some examples of the methods, apparatuses (equipment), and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for the following actions: receiving at least one additional measurement report from the UE based on the transmitted configuration information.

[0031] Some examples of the methods, devices (equipment), and non-transitory computer-readable media described herein may further include operations, features, devices, or instructions for the following actions: transmitting an indication of the scheduling plan by a parent node of an integrated access and backhaul network (IAB) to a child node of the IAB.

[0032] Some examples of the methods, apparatus (equipment), and non-transitory computer-readable media described herein may further include operations, features, devices, or instructions for transmitting an indication of the scheduling plan on a group common physical downlink control channel (GC-PDCCH), or a radio resource control (RRC) message, or a combination thereof.

[0033] In some examples of the methods, devices (equipment), and non-volatile computer-readable media described herein, the indication identifying the scheduling plan may include operations, features, devices, or instructions for the following actions: identifying a conflict between a first indication of a first scheduling plan for the scheduling node and a second indication of a scheduling plan for the scheduling node, and selecting the first scheduling plan or the second scheduling plan to become the scheduling plan based on rules for scheduling plan selection.

[0034] Some examples of the methods, devices (equipment), and non-transitory computer-readable media described herein may further include operations, features, devices, or instructions for the following actions: identifying a first time duration associated with a first scheduling plan and a second time duration associated with a second scheduling plan, wherein the rule indicates that the first scheduling plan can be selected based on the second time duration being longer than the first time duration.

[0035] Some examples of the methods, devices (equipment), and non-transitory computer-readable media described herein may further include operations, features, devices, or instructions for the following actions: receiving a first indication of a first scheduling plan through a first type of interface, receiving a second indication of a second scheduling plan through a second type of interface, and selecting the first scheduling plan to become the scheduling plan based on the rule indicating that the first type of interface overrides the second type of interface.

[0036] In some examples of the methods, devices (equipment), and non-transient computer-readable media described herein, the scheduling node includes a DU of an IAB network. In some examples of the methods, devices (equipment), and non-transient computer-readable media described herein, the IAB network includes a CU that controls a group of DUs including the DU. In some examples of the methods, devices (equipment), and non-transient computer-readable media described herein, the SPI may be used for inter-DU coordination via the CU of the IAB network. In some examples of the methods, devices (equipment), and non-transient computer-readable media described herein, the SPI may be used for inter-CU coordination via one or more Xn_C interfaces, or via a core network, or a combination thereof. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Figure 1 An example of a wireless communication system supporting scheduling plan indication (SPI) in accordance with aspects of the present disclosure is illustrated.

[0039] Figure 2A and 2B An example of a wireless communication system supporting SPI according to aspects of the present disclosure is illustrated.

[0040] Figure 3 An example of a centralized coordination scheme supporting SPI according to aspects of the present disclosure is illustrated.

[0041] Figure 4 An example of a scheduling graph supporting SPI according to aspects of the present disclosure is illustrated.

[0042] Figure 5 An example of a process flow supporting SPI according to aspects of the present disclosure is illustrated.

[0043] Figure 6 An example of a process flow supporting SPI according to aspects of the present disclosure is illustrated.

[0044] Figure 7 An example of a process flow supporting SPI according to aspects of the present disclosure is illustrated.

[0045] Figure 8 An example of a process flow supporting SPI according to aspects of the present disclosure is illustrated.

[0046] Fig. 9 and 10 A block diagram of an SPI-enabled device according to aspects of the present disclosure is shown.

[0047] Fig.11 A block diagram of a SPI-enabled communications manager is shown in accordance with aspects of the present disclosure.

[0048] Fig.12 A diagram of a system including an SPI-enabled device according to aspects of the present disclosure is shown.

[0049] Figures 13 to 23 A flow chart illustrating a method of supporting SPI according to aspects of the present disclosure is shown.

[0050] Detailed Description

[0051] In some wireless communication systems (e.g., 5G New Radio (NR) systems), a base station may be split into a base station central unit (CU) and a base station distributed unit (DU), wherein one or more DUs associated with a base station may be partially controlled by a CU associated with the base station. The base station CU may be a component of a database, a data center, a core network, or a network cloud. In some cases (e.g., in an integrated access backhaul (IAB) network), a network node may communicate with a base station CU (e.g., a donor base station) via a backhaul link (e.g., a wired backhaul or a wireless backhaul). The donor base station (e.g., an IAB donor) may be in communication with one or more IAB nodes that operate as a base station DU relative to the IAB donor. For example, an IAB network may include a chain of wireless devices (e.g., starting with a donor base station and ending with a user equipment (UE), with any number of IAB nodes between them) to extend the range of the base station CU.

[0052] However, these relay techniques (e.g., CU-DU architectures) may be associated with increased scheduling complexity (e.g., because several DUs or IAB nodes may each be in communication with one or more UEs). For example, two different cells may each be controlled by a DU, where each DU is controlled by a CU. In some cases, UE communications associated with a first cell may interfere with UE communications associated with a second cell. In addition, a wireless communication system may include multiple base stations (e.g., multiple different base station CUs), each of which may be associated with its own set of DUs. As the number of relay systems (e.g., independent base station CUs that each implement a DU) within the network increases, more complex scheduling coordination techniques may be desirable.

[0053] The technology described herein provides a scheduling plan indication (SPI) that can reduce interference and enable flexible and efficient scheduling in a network that adopts a CU-DU (e.g., relay) architecture. In general, the described technology provides signaling of SPI information to coordinate scheduling in a wireless communication system that implements DU technology. The core network can be associated with one or more access networks (ANs). In a network that adopts distributed node technology, each AN may include a CU (e.g., associated with a base station) and one or more scheduling nodes for scheduling communications with UEs within the network (e.g., DUs that are also associated with the base station, for example).

[0054] In some examples, the network may employ centralized intra-AN scheduling coordination via SPI. The CU may receive measurement reports from one or more UEs. The CU may identify an SPI for one or more scheduling nodes (e.g., DUs) in the network based at least in part on the received measurement reports. The SPI may specify a scheduling state mode within a time period that is to be used by one or more scheduling nodes to schedule communication resources for one or more UEs in the network (e.g., the SPI mode may be set by the CU based on an interference profile determined based on the received measurement reports). The scheduling state (e.g., for a given time unit) may specify a UE, beam index, or other communication resource to be used by the scheduling node to make a transmission scheduling decision. Additionally or alternatively, the scheduling state may coordinate a beam index or beam pattern for a beamforming procedure performed by a scheduling node.

[0055] In some examples, the network may employ distributed intra-AN scheduling coordination via SPI. The scheduling node may identify experimental SPIs, and the CU may take these experimental SPIs into consideration when determining the SPI. The scheduling state associated with the experimental SPI transmitted by the scheduling node may depend on the capability or functional division between the CU and the scheduling nodes within the network (for example, the experimental SPI may depend on the role or responsibility assumed by the scheduling node in making scheduling decisions). The CU may receive the experimental SPI from one or more scheduling nodes, and may update the experimental SPI (for example, based on an interference profile) or may pass or forward the experimental SPI to other scheduling nodes (for example, the CU may pass the experimental SPI between the scheduling nodes, and the scheduling nodes may take each other's experimental SPIs into consideration when making scheduling decisions, such as by preparing an updated SPI based on the experimental SPIs of other parties in the case of a distributed scheduling coordination scheme of scheduling nodes).

[0056] In some examples, the network may employ inter-AN scheduling coordination via SPI (e.g., inter-AN scheduling coordination may be employed in addition to intra-AN scheduling coordination). For example, in a distributed inter-AN scheduling coordination scheme, two or more CUs may exchange tentative SPIs with each other, and each CU may modify the SPI based on the tentative SPIs associated with the other CUs, which may then signal the SPI to their respective scheduling nodes. In a centralized inter-AN scheduling coordination scheme, each CU may signal the tentative SPI to a network node, and the network node may modify the SPI based on all received tentative SPIs, and may signal the updated SPI to each CU (e.g., each CU may then indicate the updated SPI to their respective scheduling nodes).

[0057] Beneficially, these techniques may provide reduced inter-AN and intra-AN interference (eg, due to improved scheduling coordination) and flexible scheduling coordination in networks (eg, ANs) associated with a variety of CU / DU functional partitions.

[0058] Various aspects of the present disclosure are initially described in the context of a wireless communication system. Example coordination schemes, scheduling diagrams, and process flows that implement the discussed techniques are then described. Various aspects of the present disclosure are further illustrated and described by and with reference to apparatus diagrams, system diagrams, and flow diagrams related to supporting SPI.

[0059] Figure 1 An example of a wireless communication system 100 according to various aspects of the present disclosure is illustrated. The wireless communication system 100 includes a base station 105, a UE 115, and a core network 130. In some examples, the wireless communication system 100 can be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, or an NR network. In some cases, the wireless communication system 100 can support enhanced broadband communications, ultra-reliable (e.g., mission-critical) communications, low latency communications, or communications with low-cost and low-complexity devices.

[0060] The base station 105 may communicate wirelessly with the UE 115 via one or more base station antennas. The base station 105 described herein may include or may be referred to by those skilled in the art as a base transceiver station, a radio base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next generation Node B, or a Gigabit Node B (any of which may be referred to as a gNB), a Home Node B, a Home Evolved Node B, or some other suitable terminology. The wireless communication system 100 may include different types of base stations 105 (e.g., macro cell base stations or small cell base stations). The UE 115 described herein may be able to communicate with various types of base stations 105 and network equipment (including macro eNBs, small cell eNBs, gNBs, relay base stations, etc.).

[0061] Each base station 105 may be associated with a particular geographic coverage area 110 in which it supports communications with various UEs 115. Each base station 105 may provide communications coverage for the respective geographic coverage area 110 via a communications link 125, and the communications link 125 between the base station 105 and the UE 115 may utilize one or more carriers. The communications link 125 shown in the wireless communication system 100 may include an uplink transmission from the UE 115 to the base station 105, or a downlink transmission from the base station 105 to the UE 115. Downlink transmissions may also be referred to as forward link transmissions, and uplink transmissions may also be referred to as reverse link transmissions.

[0062] The geographic coverage area 110 of the base station 105 may be divided into sectors that constitute only a portion of the geographic coverage area 110, and each sector may be associated with a cell. For example, each base station 105 may provide communication coverage for a macro cell, a small cell, a hotspot, or other types of cells, or various combinations thereof. In some examples, the base station 105 may be mobile and therefore provide communication coverage for a mobile geographic coverage area 110. In some examples, different geographic coverage areas 110 associated with different technologies may overlap, and the overlapping geographic coverage areas 110 associated with different technologies may be supported by the same base station 105 or different base stations 105. The wireless communication system 100 may include, for example, a heterogeneous LTE / LTE-A / LTE-A Pro or NR network, in which different types of base stations 105 provide coverage for various geographic coverage areas 110.

[0063] The term "cell" refers to a logical communication entity for communicating with base station 105 (e.g., on a carrier), and may be associated with an identifier to distinguish adjacent cells operating via the same or different carriers (e.g., physical cell identifier (PCID), virtual cell identifier (VCID)). In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types that may provide access to different types of devices (e.g., machine type communication (MTC), narrowband Internet of Things (NB-IoT), enhanced mobile broadband (eMBB), or others). In some cases, the term "cell" may refer to a portion of a geographic coverage area 110 (e.g., a sector) on which the logical entity operates.

[0064] Each UE 115 can be dispersed throughout the wireless communication system 100, and each UE 115 can be stationary or mobile. UE 115 can also be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, wherein "device" can also be referred to as a unit, a station, a terminal, or a client. UE 115 can also be a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 can also refer to a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or an MTC device, etc., which can be implemented in various items (such as electrical appliances, vehicles, meters, etc.).

[0065] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or with a base station 105 without human intervention. In some examples, M2M communication or MTC may include communications from devices that integrate sensors or meters to measure or capture information and relay the information to a central server or application, which may utilize the information or present the information to a person interacting with the program or application. Some UEs 115 may be designed to collect information or implement automated behavior of machines. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, health care monitoring, field survival monitoring, weather and geographic event monitoring, queue management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

[0066] Some UEs 115 may be configured to employ a reduced power consumption mode of operation, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but not simultaneous transmission and reception). In some examples, half-duplex communication may be performed at a reduced peak rate. Other power saving techniques for UE 115 include entering a power saving "deep sleep" mode when not engaged in active communications, or operating over a limited bandwidth (e.g., in accordance with narrowband communications). In some cases, UE 115 may be designed to support critical functions (e.g., mission critical functions), and the wireless communication system 100 may be configured to provide ultra-reliable communications for these functions.

[0067] In some cases, UE 115 may also be able to communicate directly with other UE 115 (e.g., using a peer-to-peer (P2P) or device-to-device (D2D) protocol). One or more UEs in a group of UEs 115 utilizing D2D communication may be within the geographic coverage area 110 of the base station 105. Other UEs 115 in this group may be outside the geographic coverage area 110 of the base station 105, or may not be able to receive transmissions from the base station 105 for other reasons. In some cases, each group of UEs 115 communicating via D2D communication may utilize a one-to-many (1:M) system, in which each UE 115 transmits to each other UE 115 in the group. In some cases, the base station 105 facilitates the scheduling of resources for D2D communication. In other cases, D2D communication is performed between UEs 115 without involving the base station 105.

[0068] The base stations 105 may communicate with the core network 130 and with each other. For example, the base stations 105 may interface with the core network 130 via a backhaul link 132 (e.g., via S1 or other interface). The base stations 105 may communicate with each other directly (e.g., directly between the base stations 105) or indirectly (e.g., via the core network 130) on a backhaul link 134 (e.g., via X2, Xn, F1, or other interface).

[0069] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) or Ethernet connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a next generation core (NGC), which may include at least one mobility management entity (MME), an authentication and mobility management function (AMF), or a session management function (SM), at least one serving gateway (S-GW), and at least one packet data network (PDN) gateway (P-GW) or user plane function (UPF). The MME may manage non-access layer (e.g., control plane) functions such as mobility, authentication, and bearer management of UE 115 served by a base station 105 associated with the EPC. User IP packets may be delivered through the S-GW, which itself may be connected to the P-GW. The P-GW or UPF may provide IP address allocation and other functions. The P-GW may be connected to a network operator IP service. Operator IP services may include access to the Internet, intranets, IP multimedia subsystems (IMS), or packet switched (PS) streaming services.

[0070] At least some network devices (such as base stations 105) may include subcomponents, such as entities, which may be examples of access node controllers (ANCs). Each AN entity may communicate with each UE 115 through a number of other AN transmission entities, which may be referred to as radio heads, smart radio heads, or transmit / receive points. In some configurations, the various functions of each AN entity or base station 105 may be distributed across various network devices (e.g., radio heads and AN controllers) or merged into a single network device (e.g., base station 105).

[0071] The wireless communication system 100 may operate using one or more frequency bands, typically in the range of 300 MHz to 300 GHz. In general, the 300 MHz to 3 GHz region is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelengths are in the range of from about 1 decimeter to 1 meter long. UHF waves may be blocked or redirected by buildings and environmental features. However, these waves may penetrate various structures sufficiently for macro cells to provide services to UEs 115 located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 km) compared to transmission using lower frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.

[0072] The wireless communication system 100 may also operate in the very high frequency (SHF) region using a frequency band from 3 GHz to 30 GHz, also known as the centimeter frequency band. The SHF region includes frequency bands that may be opportunistically used by devices that can tolerate interference from other users, such as the 5 GHz Industrial, Scientific, and Medical (ISM) band.

[0073] The wireless communication system 100 may also operate in the extremely high frequency (EHF) division of the spectrum (e.g., from 30 GHz to 300 GHz), which is also referred to as the millimeter band. In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between the UE 115 and the base station 105, and the EHF antenna of the corresponding device may be even smaller and more closely spaced than the UHF antenna. In some cases, this may facilitate the use of antenna arrays within the UE 115. However, the propagation of EHF transmissions may be subject to even greater atmospheric attenuation and shorter range than SHF or UHF transmissions. The technology disclosed herein may be adopted across transmissions using one or more different frequency divisions, and the use of frequency bands specified across these frequency divisions may vary by country or regulatory agency.

[0074] In some cases, the wireless communication system 100 may utilize both licensed and unlicensed radio frequency spectrum bands. For example, the wireless communication system 100 may adopt license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed band (such as a 5GHz ISM band). When operating in an unlicensed radio frequency spectrum band, wireless devices (such as base stations 105 and UE 115) may adopt a listen-before-talk (LBT) procedure to ensure that the frequency channel is clear before transmitting data. In some cases, operations in unlicensed bands may be based on CA configurations (e.g., LAA) in coordination with CCs operating in licensed bands. Operations in unlicensed spectrum may include downlink transmissions, uplink transmissions, peer-to-peer transmissions, or a combination of these. Duplexing in unlicensed spectrum may be based on frequency division duplexing (FDD), time division duplexing (TDD), or a combination of the two.

[0075] In some examples, the base station 105 or the UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. For example, the wireless communication system 100 may use a transmission scheme between a transmitting device (e.g., the base station 105) and a receiving device (e.g., the UE 115), wherein the transmitting device is equipped with multiple antennas and the receiving device is equipped with one or more antennas. MIMO communication may employ multipath signal propagation to increase spectral efficiency by transmitting or receiving multiple signals via different spatial layers, which may be referred to as spatial multiplexing. For example, the transmitting device may transmit multiple signals via different antennas or different antenna combinations. Similarly, the receiving device may receive multiple signals via different antennas or different antenna combinations. Each of these multiple signals may be referred to as a separate spatial stream and may carry bits associated with the same data stream (e.g., the same codeword) or different data streams. Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO technology includes single-user MIMO (SU-MIMO), in which multiple spatial layers are transmitted to the same receiving device, and multi-user MIMO (MU-MIMO), in which multiple spatial layers are transmitted to multiple devices.

[0076] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a base station 105 or a UE 115) to shape or direct an antenna beam (e.g., a transmit beam or a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals communicated via antenna elements of an antenna array so that signals propagating at a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals communicated via antenna elements may include the transmitting device or the receiving device applying a particular amplitude and phase shift to the signal carried via each antenna element associated with the device. Adjustments associated with each antenna element may be defined by a set of beamforming weights associated with a particular orientation (e.g., relative to the antenna array of the transmitting device or the receiving device, or relative to some other orientation).

[0077] In one example, the base station 105 may use multiple antennas or antenna arrays to perform beamforming operations for directional communication with the UE 115. For example, some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by the base station 105 in different directions, which may include a signal being transmitted according to different beamforming weight sets associated with different transmission directions. Transmissions in different beam directions may be used to identify (e.g., by the base station 105 or a receiving device, such as the UE 115) a beam direction for subsequent transmission and / or reception by the base station 105. Some signals (such as data signals associated with a particular receiving device) may be transmitted by the base station 105 in a single beam direction (e.g., a direction associated with a receiving device (such as the UE 115)). In some examples, the beam direction associated with transmissions along a single beam direction may be determined based at least in part on signals transmitted in different beam directions. For example, UE 115 may receive one or more signals transmitted by base station 105 in different directions, and UE 115 may report indications of the signals it received with the highest signal quality or other acceptable signal quality to base station 105. Although these techniques are described with reference to signals transmitted by base station 105 in one or more directions, UE 115 may use similar techniques for transmitting signals multiple times in different directions (e.g., for identifying a beam direction for subsequent transmission or reception by UE 115) or for transmitting signals in a single direction (e.g., for transmitting data to a recipient device).

[0078] A receiving device (e.g., UE 115, which may be an example of a mmW receiving device) may try multiple receive beams when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from base station 105. For example, the receiving device may try multiple receive directions by receiving via different antenna subarrays, processing received signals according to different antenna subarrays, receiving according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, or processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different receive beams or receive directions. In some examples, the receiving device may use a single receive beam to receive along a single beam direction (e.g., when receiving a data signal). A single receive beam may be aligned in a beam direction determined based at least in part on listening according to different receive beam directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio, or other acceptable signal quality based at least in part on listening according to multiple beam directions).

[0079] In some cases, the antennas of a base station 105 or a UE 115 may be located within one or more antenna arrays that may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some cases, the antennas or antenna arrays associated with a base station 105 may be located at different geographic locations. A base station 105 may have an antenna array having several rows and columns of antenna ports that the base station 105 may use to support beamforming for communications with a UE 115. Likewise, a UE 115 may have one or more antenna arrays that may support various MIMO or beamforming operations.

[0080] In some cases, the wireless communication system 100 can be a packet-based network that operates according to a layered protocol stack. In the user plane, the communication of the bearer or packet data convergence protocol (PDCP) layer can be based on IP. In some cases, the radio link control (RLC) layer can perform packet segmentation and reorganization to communicate on the logical channel. The media access control (MAC) layer can perform priority handling and multiplex the logical channel into the transport channel. The MAC layer can also use hybrid automatic repeat request (HARQ) to provide retransmission of the MAC layer, thereby improving link efficiency. In the control plane, the radio resource control (RRC) protocol layer can provide the establishment, configuration and maintenance of the RRC connection of the radio bearer supporting user plane data between the UE 115 and the base station 105 or the core network 130. At the physical (PHY) layer, the transport channel can be mapped to the physical channel.

[0081] In some cases, UE 115 and base station 105 may support retransmission of data to increase the likelihood that the data is successfully received. HARQ feedback is a technique that increases the likelihood of correctly receiving data on communication link 125. HARQ may include a combination of error detection (e.g., using cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ can improve the throughput of the MAC layer in poor radio conditions (e.g., signal-to-noise ratio conditions). In some cases, a wireless device may support simultaneous slot HARQ feedback, where the device may provide HARQ feedback in a specific time slot for data received in a previous symbol in the time slot. In other cases, the device may provide HARQ feedback in a subsequent time slot or according to some other time interval.

[0082] The time interval in LTE or NR can be represented by a basic time unit (which may refer to a sampling period T for example). s =1 / 30,720,000 seconds). The time intervals of the communication resources may be organized according to radio frames each having a duration of 10 milliseconds (ms), where the frame period may be expressed as T f =307,200Ts . A radio frame may be identified by a system frame number (SFN) ranging from 0 to 1023. Each frame may include 10 subframes numbered from 0 to 9, and each subframe may have a duration of 1 ms. A subframe may be further divided into 2 time slots, each having a duration of 0.5 ms, and each time slot may contain 6 or 7 modulation codeword periods (e.g., depending on the length of the cyclic prefix added before each codeword period). Excluding the cyclic prefix, each codeword period may contain 2048 sampling periods. In some cases, a subframe may be the minimum scheduling unit of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In other cases, the minimum scheduling unit of the wireless communication system 100 may be shorter than a subframe or may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI) or in a selected component carrier using sTTI).

[0083] In some wireless communication systems, a time slot may be further divided into a plurality of mini-slots containing one or more symbols. In some instances, a symbol of a mini-slot or a mini-slot may be the minimum scheduling unit. For example, each symbol may vary in duration depending on the subcarrier spacing or the operating frequency band. Further, some wireless communication systems may implement time slot aggregation, wherein a plurality of time slots or mini-slots are aggregated together and used for communication between UE 115 and base station 105.

[0084] The term "carrier" refers to a set of radio frequency spectrum resources having a defined physical layer structure for supporting communications on the communication link 125. For example, a carrier of the communication link 125 may include a portion of a radio frequency spectrum band that operates according to a physical layer channel for a given radio access technology. Each physical layer channel may carry user data, control information, or other signaling. A carrier may be associated with a predefined frequency channel (e.g., an E-UTRA Absolute Radio Frequency Channel Number (EARFCN)) and may be located according to a channel grid for discovery by a UE 115. A carrier may be downlink or uplink (e.g., in FDD mode), or may be configured to carry downlink communications and uplink communications (e.g., in TDD mode). In some examples, a signal waveform transmitted on a carrier may include multiple subcarriers (e.g., using a multi-carrier modulation (MCM) technique such as OFDM or DFT-s-OFDM).

[0085] The organization structure of the carrier may be different for different radio access technologies (e.g., LTE, LTE-A, LTE-A Pro, NR, etc.). For example, communications on a carrier may be organized according to TTIs or time slots, each of which may include user data and control information or signaling to support decoding of the user data. A carrier may also include dedicated acquisition signaling (e.g., synchronization signals or system information, etc.) and control signaling to coordinate carrier operations. In some examples (e.g., in a carrier aggregation configuration), a carrier may also have acquisition signaling or control signaling to coordinate the operations of other carriers.

[0086] Physical channels may be multiplexed on a carrier according to various techniques. Physical control channels and physical data channels may be multiplexed on a downlink carrier, for example, using a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. In some examples, control information transmitted in a physical control channel may be distributed in a cascaded manner between different control regions (e.g., between a common control region or a common search space and one or more UE-specific control regions or UE-specific search spaces).

[0087] A carrier may be associated with a particular bandwidth of the radio frequency spectrum, and in some examples, the carrier bandwidth may be referred to as the "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of several predetermined bandwidths of a carrier for a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 MHz). In some examples, each served UE 115 may be configured to operate on part or all of the carrier bandwidth. In other examples, some UEs 115 may be configured to operate using a narrowband protocol type associated with a predefined portion or range (e.g., a set of subcarriers or RBs) within a carrier (e.g., an "in-band" deployment of a narrowband protocol type).

[0088] In a system using MCM technology, a resource element may include a symbol period (e.g., the duration of a modulation symbol) and a subcarrier, where the symbol period and the subcarrier spacing are inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme). Thus, the more resource elements received by UE 115 and the higher the order of the modulation scheme, the higher the data rate of UE 115 can be. In a MIMO system, wireless communication resources may refer to a combination of radio frequency spectrum resources, time resources, and space resources (e.g., space layers), and the use of multiple space layers may further increase the data rate of communication with UE 115.

[0089] A device (e.g., base station 105 or UE 115) of wireless communication system 100 may have a hardware configuration that supports communication on a particular carrier bandwidth, or may be configurable to support communication on one of a set of carrier bandwidths. In some examples, wireless communication system 100 may include base stations 105 and / or UEs that may support simultaneous communication via carriers associated with more than one different carrier bandwidths.

[0090] The wireless communication system 100 may support communication with a UE 115 on multiple cells or carriers, a feature that may be referred to as carrier aggregation (CA) or multi-carrier operation. The UE 115 may be configured with multiple downlink CCs and one or more uplink CCs according to a carrier aggregation configuration. Carrier aggregation may be used with both FDD and TDD component carriers.

[0091] In some cases, the wireless communication system 100 may utilize an enhanced component carrier (eCC). An eCC may be characterized by one or more features including a wider carrier or frequency channel bandwidth, a shorter symbol duration, a shorter TTI duration, or a modified control channel configuration. In some cases, an eCC may be associated with a carrier aggregation configuration or a dual connectivity configuration (e.g., when multiple serving cells have suboptimal or non-ideal backhaul links). An eCC may also be configured for use in an unlicensed spectrum or a shared spectrum (e.g., where more than one operator is allowed to use the spectrum). An eCC characterized by a wide carrier bandwidth may include one or more segments that may be utilized by a UE 115 that is not capable of monitoring the entire carrier bandwidth or is otherwise configured to use a limited carrier bandwidth (e.g., to save power).

[0092] In some cases, an eCC may utilize a different symbol duration than other CCs, which may include using a reduced symbol duration compared to the symbol duration of other CCs. A shorter symbol duration may be associated with an increased spacing between adjacent subcarriers. A device utilizing an eCC (such as a UE 115 or a base station 105) may transmit a wideband signal (e.g., according to a frequency channel or carrier bandwidth of 20, 40, 60, 80 MHz, etc.) with a reduced symbol duration (e.g., 16.67 microseconds). A TTI in an eCC may include one or more symbol periods. In some cases, the TTI duration (i.e., the number of symbol periods in a TTI) may be variable.

[0093] Wireless communication systems such as NR systems may utilize any combination of licensed, shared, and unlicensed spectrum bands, etc. The flexibility of eCC symbol duration and subcarrier spacing may allow eCC to be used across multiple spectrums. In some examples, NR shared spectrum may increase spectrum utilization and spectrum efficiency, particularly through dynamic vertical (e.g., across frequency) and horizontal (e.g., across time) sharing of resources.

[0094] In some wireless communication systems 100, one or more base stations 105 may be split into a base station CU and a base station DU, wherein one or more DUs associated with a base station may be partially controlled by the CU associated with the base station. The base station CU may be a component of a database, a data center, or a core network 130 (e.g., a 5G NR core network (5GC)). The base station CU may communicate with the donor base station 105 via a backhaul link 132 (e.g., a wired backhaul or a wireless backhaul). As another example, in an IAB network, a base station CU (e.g., a donor base station 105-a) may communicate with a core network 130 (e.g., an NGC) via a backhaul link 132 (e.g., a wired backhaul or a wireless backhaul). The donor base station 105-a (e.g., an IAB donor) may be in communication with one or more IAB nodes (e.g., base stations 105-b and base stations 105-c) operating as base station DUs relative to the IAB donor. For example, an IAB network may include a chain of wireless devices (e.g., starting with donor base station 105-a and ending with UE 115, with any number of IAB nodes in between) to extend the range of a base station CU. In some cases, the CU-DU architecture may result in increased scheduling complexity between cells associated with different DUs and / or IAB nodes.

[0095] Aspects of base station 105 (e.g., IAB node, DU, etc.) and served UE 115 may implement SPI signaling in wireless communication system 100 to achieve improved inter-cell coordination and scheduling. Wireless communication system 100 may adopt a relay chain for communication within CU-DU architecture. Donor base station 105 may include or be connected to base station CU, and may transmit signals to relay base station 105 (e.g., DU) on downlink. Relay base station 105 may relay these signals to other relay base stations 105, or to UE 115 on downlink, or to both. Donor base station 105 or relay base station 105 may adjust the scheduling of these transmissions according to SPI signaling described below. Relay base station 105 may act as a relay between donor base station 105 and UE115 in two transmission directions. Donor base station 105 may refer to a base station including a base station DU connected to base station CU. As will be discussed, the donor base station 105 and the relay base station 105 may implement different aspects and perform different functions related to SPI signaling.The described SPI-based scheduling techniques may mitigate interference and utilize wireless resources within the wireless communication system 100 more efficiently.

[0096] A CU (e.g., associated with a base station 105) may receive measurement reports from one or more UEs 115. The CU may identify an SPI for one or more scheduling nodes (e.g., DUs) in the network based at least in part on the received measurement reports. The SPI may specify a scheduling state mode over a period of time that is to be used by one or more scheduling nodes to schedule communication resources for one or more UEs 115 in the network. The scheduling state may specify a UE 115 or other communication resource to be used by the scheduling node to make a transmission scheduling decision, or may specify a beam pattern for a beamforming procedure performed by the scheduling node (e.g., based on an interference profile determined based on the received measurement reports). In some cases, the scheduling node may identify tentative SPIs that the CU may take into account when determining the SPI, or may communicate these tentative SPIs between other scheduling nodes to implement a distributed scheduling coordination scheme.

[0097] Figure 2A and 2B An example of a wireless communication system that can adopt a CU-DU split architecture and implement SPI according to various aspects of the present disclosure is illustrated. For example, Figure 2A A wireless communication system 200 (e.g., an NR system, an LTE system, etc.) supporting SPI according to various aspects of the present disclosure is illustrated. The wireless communication system 200 may include a core network 205 (e.g., a 5GC) and a base station 210 split into a base station CU 215 and a base station DU 220, wherein one or more DUs 220 associated with the base station 210 may be partially controlled by the CU 215 associated with the base station 210. The base stations 210-a and 210-b may be examples of various aspects of the base station 105, and the core network 205 may be examples of various aspects of the core network 130, as described with reference to FIG. Figure 1 as described.

[0098] For example, the base station 210-b may be split into a CU 215 and DUs 220-a and 220-b. The CU 215 may host layer 3 (L3) (e.g., RRC, service data adaptation protocol (SDAP), packet data convergence protocol (PDCP), etc.) functionality and signaling. The DUs 220-a and 220-b may host lower layers, such as layer 1 (L1) and layer 2 (L2) (e.g., radio link control (RLC), media access control (MAC), physical (PHY), etc.) functionality and signaling, and may each be at least partially controlled by the CU 215. The DUs 220-a and 220-b may each support one of a plurality of cells (e.g., each DU 220 may be associated with one or more different cells). The CU 215 and the DUs 220-a and 220-b may communicate via an F1 interface according to a protocol (e.g., an F1 application protocol (AP) protocol) that defines signaling messages between the CU 215 and the DUs 220. In addition, the CU 215 may communicate with the core network 205 via an NG interface (which may be an example of a portion of the backhaul link 132) and may communicate with other CUs 215 (e.g., a CU associated with the base station 210-a) via an Xn-C interface (which may be an example of a portion of the backhaul link 134).

[0099] Figure 2B A wireless communication system 201 (e.g., including a portion of an IAB network) supporting SPI according to various aspects of the present disclosure is illustrated. The wireless communication system 201 may include a core network 225 (e.g., NGC), an IAB donor 230, an IAB node 235, and a UE 115, wherein each IAB node may be partially controlled by each other and / or the IAB donor 203. The IAB donor 230 and the IAB node 235 may be as described in reference Figure 1 Examples of various aspects of the base station 105 described herein and the core network 225 may be as described with reference to Figure 1 Examples of aspects of the described core network 130. The IAB donor 230 and one or more IAB nodes 235 can be configured as (eg, or be in communication according to) a relay chain.

[0100] For example, AN may refer to the communication between the access node (e.g., IAB donor 230 and IAB nodes 235-a and 235-b) and the UE 115. The IAB donor 230 may facilitate the connection between the core network 225 and the AN (e.g., via a wired or wireless connection to the core network 225). That is, the IAB donor 230 may refer to a radio access network (RAN) node having a wired or wireless connection to the core network 225. The IAB donor 230 may include a CU 240 and at least one DU 245, wherein the CU 240 communicates with the core network 225 through an NG interface (e.g., a certain backhaul link 132). The IAB node 235 may refer to a RAN node that provides IAB functionality (e.g., access to the UE 115, wireless self-backhaul capability, etc.). The IAB node 235 may include a DU 245 and a mobile terminal (MT) 250. DU 245 can act as a distributed scheduling node for child nodes associated with IAB node 235, and MT 250 can act as a scheduled node for parent nodes associated with IAB node 235. That is, IAB donor 230 can be referred to as a parent node in communication with one or more child nodes (e.g., IAB donor can relay transmission for UE through one or more other IAB nodes 235.) In addition, IAB node 235 can also be referred to as a parent node or child node of other IAB nodes 235, depending on the relay chain or configuration of AN. Therefore, the MT interface of the IAB node (e.g., MT 250) can provide a Uu interface for receiving signaling from the parent IAB node for the child node, and the DU interface (e.g., DU 245) can provide a Uu interface for signaling to the child IAB node or UE 115 for the parent node. As discussed in greater detail herein, the CU 240 of the IAB donor 230 may schedule one or more IAB nodes 235 via SPI signaling to the DUs 245 of the IAB nodes 235 (eg, over an F1 interface).

[0101] For example, the IAB node 235-a may be referred to as a parent node associated with the IAB node 235-b, and a child node associated with the IAB donor 230. The IAB donor may include a CU 240 having a wired (e.g., optical fiber) or wireless connection to the core network 225, and may act as a parent node for the IAB nodes 235-a and 235-b. For example, the DU 245 of the IAB donor 230 may relay a transmission to the UE 115 via the IAB node 235. The CU 240 of the IAB donor 230 may signal the SPI to the IAB nodes 235-a and 235-b via the F1 interface, and the IAB nodes 235-a and 235-b may schedule a transmission (e.g., a transmission relayed from the IAB donor 230 to the UE 115) through the DU 245 based on the received SPI. That is, data may be relayed to and from the IAB nodes 235-a and 235-b via signaling on the NR Uu interface (e.g., a communication link 125) of the MT 250 to the IAB nodes 235-a and 235-b. Communication with the IAB node 235-a may be scheduled by the DU 245 of the IAB node 230 based on SPI signaling, and communication with the IAB node 235-b may be scheduled by the DU 245 of the IAB node 235-a based on SPI signaling.

[0102] In general, wireless communication system 200 and wireless communication system 201 can illustrate an example wireless communication system that communicates within an AN using a relay chain (e.g., CU-DU architecture). Donor base station 105 may include or be connected to base station CU, and may transmit signals to relay base station 105 (e.g., DU, IAB node, etc.) on a downlink. Relay base station 105 may relay these signals to UE 115 on a downlink. Donor base station 105 or relay base station 105 may adjust the scheduling of these transmissions according to the SPI signaling described below. Relay base station 105 may act as a relay between donor base station 105 and UE 115 in two transmission directions. Donor base station 105 may refer to a base station including a base station DU connected to base station CU. As discussed herein, donor base station 105 and relay base station 105 may implement different aspects related to SPI signaling and perform different functions related to SPI signaling. The described SPI-based scheduling techniques may mitigate interference and more efficiently utilize wireless resources within a wireless communication system.

[0103] In the following description, the SPI-based scheduling technology may be described in actions and processes performed by CU, DU, and UE, but may be implemented by donor base station 105, relay base station 105, UE 115, base station 210, CU 215, DU 220, IAB donor 230, IAB node 235, CU 240, DU 245, MT 250, etc. (and so on) without departing from the scope of the present disclosure. That is, CU may refer to any central entity that controls multiple scheduling nodes in a network. CU may be associated with L3 signaling and functionality within the network. In the context of wireless communication system 201, CU may refer to CU functionality at IAB donor 230, which controls DU 245 of IAB nodes 235-a and 235-b and its own DU. DU may refer to any node that performs scheduling functions in a network and may be associated with L1 and L2 signaling and functionality within the network. In the context of the wireless communication system 201, DU may refer to the DU 245 functionality at the IAB node 235 or IAB donor 230, which schedules the UE 115 and MT 250 within its coverage. UE may refer to a node that is scheduled in a network. In the context of the wireless communication system 201, UE may refer to the UE 115 and / or MT 250 functionality at the IAB node 235 for an access link.

[0104] The SPI may specify a mode or configuration of a scheduling state within a time period of N time units. The scheduling state may refer to the state of any scheduling associated with a network, or a resource within a network, for a given time unit. For example, possible scheduling states may include a scheduling information state (e.g., a scheduled state), a flexible state, and / or an invalid (NULL) state. The scheduling information state may adopt various formats depending on the scheduling information indicated by the scheduling information state (e.g., the scheduling information state may indicate what is scheduled during a given time unit, such as one or more UEs, beams, positions, etc.). For example, the scheduling information state may indicate a set of UE indexes used for scheduling (e.g., for scheduling data transmission for different UEs), a set or a range of beam indexes, a set or a range of relative or absolute angle values, a set or a range of relative or absolute position values, etc. The scheduling information status may further indicate or include additional information associated with the scheduling, such as allocated resource blocks (RBs), buffer status (e.g., buffer status report (BSR)), priority of communication or traffic type, modulation and coding scheme (MCS), signal-to-noise ratio (SNR), target signal-to-interference and noise ratio (SINR), target transmit or receive power (e.g., target total radiated power (TRP)), etc.

[0105] A flexible state may indicate that any UE or beam direction may be scheduled for a given time unit (e.g., a flexible state may indicate that a scheduling node (e.g., a DU) is allowed to schedule any UE or beam direction during a time unit associated with the flexible state). In some cases, a flexible state may be defined (e.g., by a central node via an SPI) as a hard state or a soft state. A hard state may indicate that a communication may be scheduled by a scheduling node and may be fully controlled by the scheduling node. A soft state may indicate that a link from a scheduling node to a child node may be dynamically controlled by a scheduling node (e.g., a parent node may permit a child node to use a soft state, but the communication may be unavailable by default unless the parent node permits otherwise). An invalid state (e.g., an unavailable state) may indicate that no communication is scheduled during the time unit, or that no communication is to be scheduled (e.g., a DU is restricted from scheduling all communications). For example, an invalid state may indicate that a scheduling node (e.g., a DU) is prevented from scheduling all or any UEs, beam directions, etc. (e.g., an invalid state may indicate that no resources are available for use by a scheduling node).

[0106] For example, for the scheduling of DU sublinks (e.g., links between a scheduling node and its child nodes), there may be three types (e.g., three different types of availability or usage criteria). For example, the communication or resources of the DU sublink may be configured as hard (e.g., controlled by a child node), soft (e.g., controlled by a parent node), or unavailable (e.g., SPI information may be coordinated for scheduling via the distribution of scheduling states, such as scheduling information states, flexible states, hard states, soft states, invalid or unavailable states, etc.). Hard resource configuration may result in the corresponding time resources being always available for the DU sublink. Soft resource configuration may result in the availability of the corresponding time resources for the DU sublink being explicitly and / or implicitly controlled by the parent node. Thus, a DU may be configured with, for example, the following resource types: hard downlink, hard uplink, hard flexible, unavailable (NA), soft downlink, soft uplink, and soft flexible. In some cases, soft resources (e.g., soft downlink, soft uplink, or soft flexible resources) may be initially unavailable for a sublink of a DU and may be converted to hard resources (e.g., hard downlink, hard uplink, or hard flexible resources) by a parent node (e.g., explicitly or implicitly).

[0107] A time unit in the SPI (e.g., a time unit in an SPI mode or configuration) may refer to one or more time slots or mini-time slots. In addition, the scheduling plan indicated by the SPI may be applicable to different types of scheduling. For example, the SPI may indicate scheduling of data transmission for different DUs, different UEs, and the like. In another example, the SPI may indicate scheduling of a beam pattern for a procedure such as a synchronization procedure, a beam management procedure, an inter-relay discovery procedure, a random access channel procedure (RACH), and the like. That is, the SPI may be additionally used in some cases to indicate scheduling or coordination of a beam pattern (e.g., in a system supporting mmW communication), as described in reference to Figure 3 Described in more detail.

[0108] SPI can be associated with an override rule (e.g., an SPI priority criterion) for conflict resolution in a scenario where multiple SPIs for the same node or resource are received. Multiple different SPI types can be defined and can be associated with different priorities, and the way in which the SPI is received can establish a priority relative to other received SPIs, and so on. For example, for an SPI defined on a Uu air interface, an SPI type can be defined for a semi-static configuration within a relatively large time range, and another SPI type can be defined for a dynamic configuration within a relatively small time range. An override rule (e.g., or a priority criterion) can establish an SPI override for a dynamic configuration or take precedence over an SPI for a semi-static configuration. In other examples, there is an inherent priority in the way in which the SPI is received. For example, in an IAB network (e.g., a wireless communication system 201), an IAB node 235 can receive an SPI from its parent node on a Uu interface (e.g., an IAB node 235-b can receive an SPI from an IAB node 235-a), and can also receive an SPI from a CU 240 on an F1-AP interface. In such a case, an override rule (eg, or priority criteria) may establish that the SPI received on the Uu interface overrides the SPI received on the F1-AP interface (eg, or vice versa).

[0109] SPI can be defined and signaled on different interfaces. For example, SPI can be signaled on the interface between CU and DU (e.g., SPI signaling messages can be defined for SPI on F1-AP). Such F1-AP signaling of SPI can be used during centralized scheduling coordination of DU by CU (e.g., applicable to AN, IAB network with architecture group 1) and during distributed scheduling coordination between DUs (e.g., as described in reference to FIG. Figure 5-8SPI may also be signaled on an interface between CUs (e.g., an Xn-C interface) or an interface between a CU and a core network (e.g., an NG interface). Such Xn-C and / or NG signaling of SPI may be used during inter-CU scheduling coordination (e.g., as described in reference to Figure 7-8 described in more detail). Additionally, the SPI may be signaled over an air interface (e.g., a Uu interface) between a base station and a UE or between a base station and a MT. Such Uu signaling of the SPI may be used for direct scheduling coordination between parent-child nodes in an IAB network, for UE power saving, and the like. In some examples, the SPI may be included in RRC signaling, F1-AP communication, group common PDCCH (GC-PDCCH) signaling, or some combination thereof. As described above, the base station 105 may be an example of a full gNB, an access node, an eNB, or some combination thereof, and the base station CU may be an example of a gNB-CU, a gNB, or a control function.

[0110] Figure 3 An example of a centralized coordination scheme 300 supporting SPI according to aspects of the present disclosure is illustrated. In some examples, the centralized coordination scheme 300 can be referred to as Figure 1 The centralized coordination scheme 300 may include a CU 305 (e.g., a donor base station), DUs 310-a and 310-b (e.g., relay base stations), and at least UEs 115-a, 115-b, 115-c, and 115-d, which may be reference UEs 115-a, 115-b, 115-c, and 115-d. Figure 1 , 2A and corresponding devices described in 2B. The centralized coordination scheme 300 may utilize F1 or F1-AP signaling (eg, signaling on an F1 or F1-AP interface) to communicate SPIs (eg, a trial SPI 320 and an updated SPI 325) between the CU 305 and the DUs 310-a and 310-b.

[0111] As discussed above, the SPI may be used to coordinate or configure a beam sweeping pattern for a neighboring cell controlled by the DU 310. In a wireless communication system (e.g., mmW system) utilizing beamforming technology, a base station (e.g., DU 310) may transmit information (e.g., reference signals, synchronization signals, etc.) for cell acquisition and synchronization in a beam sweeping pattern in order to provide sufficient information to all UEs within the coverage area of ​​the base station. For example, the DU 310 may beam sweep a set of synchronization signal blocks (SSBs) (e.g., which may include a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a physical broadcast channel (PBCH), etc.). Each cell (e.g., DU 310) may broadcast the SSBs in a beam sweeping manner. UEs (e.g., UEs 115-a, 115-b, 115-c, and 115-d) may monitor SSBs transmitted via beam 315 to obtain RRM measurements (e.g., UE 115-a may identify neighbor cells based on beam 315-d transmitted by DU 310-b).

[0112] In some cases, associated transmissions from adjacent cells may interfere with each other (e.g., beam sweeping patterns utilized during cell synchronization procedures may interfere, beamformed transmissions to UEs may interfere, etc.), resulting in reduced system performance. For example, two cells may be controlled by different DUs 310 (e.g., cell 1 may be controlled by DU 310-a, while cell 2 may be controlled by DU 310-b). DU 310-a may transmit to UE 115-a using beam 315-a, which in some cases (e.g., in the absence of SPI coordination) may cause interference to transmissions from DU 310-b to UE 115-d using beam 315-d. Similarly, DU 310-a may transmit to UE 115-b using beam 315-b, which in some cases (e.g., in the absence of SPI coordination) may cause interference to transmissions from DU 310-b to UE 115-c using beam 315-c. Additionally or alternatively, transmissions from UEs 115-a, 115-b, 115-c, and 115-d may interfere with each other (e.g., due to their proximity, due to time-frequency resources used by the UEs, etc.).

[0113] As discussed herein, the CU 305 may control both DUs 310-a and 310-b and may use the SPI to coordinate UE 115 scheduling, beam patterns, beamformed transmissions between neighboring cells, etc. The SPI may be used to coordinate beam sweep patterns, schedule communications for UEs 115, etc. For example, the DU 310-a may signal a tentative SPI 320-a to the CU 305, and the DU 310-b may signal a tentative SPI 320-b to the CU 305. The CU 305 may receive the tentative SPIs 320-a and 320-b and transmit updated SPIs 325-a and 325-b to the DUs 310-a and 310-b. For example, in some cases, CU 305 may determine an interference profile (e.g., based on analysis of received experimental SPIs 320-a and 320-b, analysis of measurement reports received from any of UEs 115-a, 115-b, 115-c, and 115-d, etc.), and add or adjust information associated with the received experimental SPIs 320-a and 320-b (e.g., update the received experimental SPIs 320-a and 320-b). The updated SPIs 325-a and 325-b may thereby coordinate any beamformed transmissions within the network to UE 115. Additionally, the updated SPIs 325-a and 325-b may coordinate any beam sweeping patterns used for beam sweeping procedures associated with Cell 1 and Cell 2.

[0114] Figure 4 An example of an SPI scheduling diagram 400 supporting SPI according to aspects of the present disclosure is illustrated. Aspects of the SPI scheduling diagram 400 may be referred to by reference Figure 1-3 The wireless communication system 100, the wireless communication system 200, the wireless communication system 201, and / or the centralized coordination scheme 300 described herein can be implemented. The SPI scheduling diagram 400 may include an IAB node 405, which may be a reference Figure 2B An example of a corresponding device is described. The SPI scheduling diagram 400 may illustrate how resources 410 (eg, UE 115 index, beam index, beam sweep pattern, angle value set, position value set, etc.) may be scheduled by the IAB node 405 .

[0115] As discussed above, the SPI may be transmitted in the IAB network via the Uu air interface with a signal for scheduling coordination (e.g., the SPI scheduling diagram 400 may implement Uu signaling between the IAB nodes 405 to convey the SPI for resource scheduling). Each IAB node 405 may be both a scheduling node (e.g., DU) of its child node and a scheduled node (e.g., MT) of its parent node. The parent node of the IAB node 405 may include another IAB node 405 or an IAB donor. The child node of the IAB node 405 may include another IAB node 405 or a UE 115. The IAB node may use the Uu air interface to send its SPI to its child node so that the child IAB node can avoid scheduling conflicts (e.g., interference) from half-duplex constraints. For example, for a given time unit (e.g., a time unit associated with the SPI mode), if the IAB node 405 is not scheduled by its parent IAB node, the IAB node may use the time unit to communicate with its own child node. The child IAB node may determine the resources 410 used on its own child node based on the received SPI. That is, based on the SPI received from the parent node, the IAB node 405 can know which resources 410 are to be used for the child nodes of the IAB node 405. For example, the IAB node 405-b can receive the SPI associated with the resource 410-a from the IAB node 405-a (e.g., the parent node), and can use the resource 410-b for the SPI sent to the IAB nodes 405-d and 405-e (e.g., the child nodes). In some examples, based on the received SPI, the parent node (e.g., DU) can identify the UE, beam direction, or other resources as interfering. The parent node can therefore assign the interfering UE, beam direction, etc. to different time units or different non-overlapping resource block allocations (e.g., different resources 410).

[0116] Figure 5 An example of a process flow 500 for supporting SPI according to aspects of the present disclosure is illustrated. In some examples, the process flow 500 can implement aspects of the wireless communication system 100, the wireless communication system 200, and / or the wireless communication system 201. The process flow 500 can include a UE 115-e, a CU 505, and a DU 510, which can be referenced Figures 1 to 4Examples of corresponding devices described. In some cases, CU 505 and DU 510 may be located in the same device (e.g., a donor base station or a donor IAB may include CU 505 and DU 510). In other cases, CU 505 and DU 510 may be located in separate locations (e.g., CU 505 may be located in an IAB donor and DU 510 may be located in an IAB node, such as a subnode associated with the IAB donor including CU 505), and an F1 association (e.g., an L3 signaling channel) may be formed. In some examples, CU 505 may be a component of a database, a data center, or a cloud network. Process flow 500 may illustrate centralized intra-AN scheduling coordination using SPI signaling on an F1-AP interface. In the following description of process flow 500, operations between UE 115-e, CU 505, and DU 510 may be transmitted in an order different from the exemplary order shown, or operations performed by UE 115-e, CU 505, and DU 510 may be performed in a different order or at a different time. In some cases, certain operations may also be excluded from process flow 500, or other operations may be added to process flow 500.

[0117] At 515, the CU 505 may configure the UE 115-e to transmit a radio resource management (RRM) measurement report. The RRM procedure may provide a mechanism that enables a UE (e.g., UE 115-e) to report reference signal beam indices and measurement parameters (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), signal to interference plus noise ratio (SINR), etc.) from its serving cell and from neighbor cells that the UE can detect. In some cases, the reference signal beam index may include an SSB index or a channel state information reference signal (CSI-RS) index, which may be indicated in the RRM configuration and / or the RRM measurement report.

[0118] At 520, the UE 115-e may transmit an RRM measurement report to the CU 505. For example, the UE 115-e may receive downlink reference signals from the serving cell and from the neighbor cells. The UE 115-e may measure (e.g., detect) the quality of the beam and report the measurement information to the CU (e.g., the RRC layer of the base station). The RRM measurement report may include beam indices and measurement parameters for the serving cell and the neighbor cells. For example, the RRM measurement report may include results of SSB measurements, CSI-RS measurements, beam indices, physical cell IDs, etc. associated with the serving cell and the neighbor cells (e.g., according to the configuration received at 515). In some cases, the RRM measurement report may be transmitted to the DU 510 and relayed from the DU 510 to the CU 505 (e.g., the UE 115-e may transmit the RRM measurement report to the DU 510 using Uu signaling, and the DU 510 may pass or relay the RRM measurement report to the CU 505 using F1-AP signaling).

[0119] At 525, CU 505 may determine an interference profile based at least in part on the RRM measurement report received at 520. For example, CU 505 may identify UEs and / or beam pairs that interfere between neighboring cells. If a serving beam associated with a second UE (e.g., a UE other than UE 115-e) is one of the interfering beams or neighbor beams of UE 115-e, the second UE may be identified as interfering with UE 115-e. The identification of the interfering beam may be based on a history of RRM reports provided by a group of UEs (e.g., a group of UEs within a network). The interference profile may include profiles of interfering UEs, interfering beams, etc.

[0120] For example, in some cases, CU 505 may receive at least one measurement report in addition to the measurement report received at 520 (e.g., at least one additional measurement report of at least one additional UE). The additional measurement report may be received from DU 510, or may be received from some other DU controlled by CU 505. CU 505 may determine an interference profile based at least in part on the measurement report received at 520 and the at least one additional measurement report (e.g., CU 505 may use multiple measurement reports to identify interfering UEs, interfering beams, etc.). In some cases, CU 505 may signal the interference profile to DU 510. In such cases, DU 510 may identify UEs, beam directions, etc. as interfering based on the received interference profile. DU 510 may therefore assign interfering UEs, beam directions, etc. to different time units or different non-overlapping resource block allocations (e.g., as described with reference to resources 410-a and 410-b, as described in reference to resources 410-a and 410-b). Figure 4 discussed in ).

[0121] In some cases, at 530, the CU 505 may configure additional measurements to obtain a more accurate interference estimate. For example, the CU 505 may transmit configuration information to the UE 115-e for use by the UE 115-e to perform additional measurements on one or more cells. The UE 115-e may transmit at least one additional measurement report based on the received configuration information. In some cases, the CU 505 may modify or adjust the interference profile determined at 525 based on the additional configured RRM measurements.

[0122] At 535, the DU 510 may signal the experimental SPI to the CU 505 (e.g., via F1-AP signaling). In some cases, the DU 510 may determine the experimental SPI based on L1 / L2 reports (e.g., channel state information (CSI) reports, buffer status reports, etc.) from UEs within the corresponding cell of the DU 510. The scope of the experimental SPI may depend on the functional division between the CU 505 and the DU 510 (e.g., the DU 510 may assume more or less responsibility for scheduling decisions for its own cell). For example, in some implementations, the DU 510 may assume a relatively larger role (e.g., more responsibility) in scheduling decisions for its own cell by including more scheduling information (e.g., scheduling information status) in the experimental SPI signaled to the CU 505. The CU 505 may then adjust the scheduling information indicated in the received experimental SPI to control inter-cell interference. In other examples, the DU 510 may take a relatively smaller role (e.g., less responsibility) in scheduling decisions for its own cell by including more flexible states in the tentative SPI (e.g., marking some or all time units in the SPI pattern as flexible) so that the CU 505 may take some or all scheduling decisions. That is, the DU 510 may have more or less control over scheduling decisions based on what the DU 510 includes in the tentative SPI transmitted to the CU 505 (e.g., what states the DU sets for a certain set of time units). In still other examples, the DU 510 may not transmit the tentative SPI. In such cases, the CU 505 may completely determine the SPI without DU input and have complete control and authority over the scheduling of each DU 510.

[0123] At 540, CU 505 may modify the received scheduling plan (e.g., the received tentative SPI) based on the interference profile (e.g., determined at 525) to reduce or control interference. For example, interfering UEs or beam directions from neighboring DUs may be placed into different time units or have non-overlapping RB allocations when scheduled in the same time unit (e.g., the SPI pattern may be modified or updated so that the interfering UEs / beam directions may be separated in time and / or frequency). The SPI for a scheduling node (e.g., DU 510) may be determined based on a measurement report received from the scheduling node.

[0124] For example, at 540, CU 505 may identify an SPI for a scheduling node (e.g., DU 510). The SPI may specify a scheduling state mode within a time period. The SPI may be based on the measurement report received at 520. In some cases, the scheduling state mode may include a scheduling information state, a flexible state, or an invalid state. The flexible state may allow the scheduling node to schedule any UE, any beam direction, etc. In some cases, the flexible state may be defined (e.g., by a central node via the SPI) as a hard state or a soft state. The hard state may indicate that the communication may be scheduled by the scheduling node and may be fully controlled by the scheduling node. The soft state may indicate that the link from the scheduling node to the child node may be dynamically controlled by the scheduling node (e.g., the parent node may permit the child node to use the soft state, but the communication may be defaulted to unavailable unless the parent node permits otherwise). An invalid state (e.g., an unavailable state) may prevent the scheduling node from scheduling all UEs, all beam directions, etc. (e.g., an invalid state may indicate that there are no resources available for the scheduling node).

[0125] In some cases, the time period associated with the SPI mode may refer to one or more time slots or mini-time slots. In some cases, the SPI may identify a value used for scheduling (e.g., a set of UE indexes, a set of beam indexes, a set of angle values, a set of position values, etc.) for a scheduling state. The SPI may schedule data transmission for different UEs, different beam modes (e.g., for procedures related to cellular cell beamforming), etc. for a scheduling state. Additionally or alternatively, the SPI may identify the allocated RBs, buffer status, scheduling priority, communication type, MCS, target SINR, target transmit power, target receive power, etc. for a scheduling state.

[0126] At 545, CU 505 may signal the updated SPI to DU 510 (eg, via F1-AP signaling). In some cases, the updated SPI may be transmitted on GC-PDCCH, RRC message, etc.

[0127] At 550, the DU 510 may schedule the UE 115-e (eg, along with communication resources) according to the updated SPI received at 545 (eg, the DU 510 may schedule the UE 115-e in compliance with the received SPI, or may coordinate a certain beamforming procedure in some cases).

[0128] In some cases, DU 510 may refer to a DU of an IAB network (e.g., wireless communication system 201). In some cases, the IAB network may include a CU 505 that may control multiple DUs (e.g., and the multiple DUs may include at least DU 510). The SPI (e.g., the updated SPI at 545) may be used for inter-DU coordination via the CU 505 of the IAB network.

[0129] Figure 6 An example of a process flow 600 supporting SPI according to aspects of the present disclosure is illustrated. In some examples, the process flow 600 can implement aspects of the wireless communication system 100, the wireless communication system 200, and / or the wireless communication system 201. The process flow 600 can include UE 115-f, UE 115-g, CU 605, DU 610-a, and DU 610-b, which can be referenced Figures 1 to 4 Examples of corresponding devices described. In some cases, CU 605 and DU 610-a and 610-b can be located in the same device (e.g., a donor base station or a donor IAB can include CU 605 and DU 610-a and 610-b). In other cases, CU 605 and DU 610-a and 610-b can be located in separate locations (e.g., CU 605 can be located in an IAB donor and DU 610-a and 610-b can be located in separate IAB nodes, such as certain sub-nodes associated with the IAB donor including CU 605), and an F1 association (e.g., an L3 signaling channel) can be formed. In some examples, CU 605 can be a component of a database, a data center, or a cloud network. Process flow 600 can illustrate a distributed intra-AN coordination scheme between DU 610-a and 610-b using SPI signaling on a Uu interface. In the following description of process flow 600, operations between UE 115-f, UE 115-g, CU 605, DU 610-a, and DU 610-b may be transmitted in an order different from the exemplary order shown, or operations performed by UE 115-f, UE 115-g, CU 605, DU 610-a, and DU 610-b may be performed in a different order or at a different time. In some cases, certain operations may also be excluded from process flow 600, or other operations may be added to process flow 600.

[0130] At 615, DUs 610-a and 610-b may determine a tentative SPI (e.g., DU 610-a may determine tentative SPI 1 and DU 610-b may determine tentative SPI 2). For example, DUs 610-a and 610-b may determine the tentative SPI based on their respective cells (e.g., based on L1 / L2 reports from UEs within their respective cells, such as CSI reports, BSRs, etc.). In some cases, the tentative SPI may include scheduling information that further depends on DU-related functionality (e.g., whether the tentative SPI includes a scheduling information state, a flexible state, a hard state, a soft state, or an invalid state may depend on the functionality or priority of the DU in some cases). For example, in some cases, DU 610-a may be associated with a high priority and may be associated with increased scheduling functionality / priority relative to DU 610-b. In such cases, the experimental SPI associated with DU 610-a may include a scheduling information state, while the experimental SPI associated with DU 610-b may include a flexible state or soft state (e.g., so that DU 610-b can routinely defer to or rely on DU 610-a for SPI / scheduling coordination). In some cases, 615-a and 615-b may be executed in parallel (e.g., at least partially overlapping in time), and in other cases, 615-a and 615-b may be executed independently and at different times.

[0131] At 620 , the DU 610 - a may signal the tentative SPI 1 (eg, determined at 615 - a ) to the CU 605 .

[0132] At 625, the CU 605 may add information to the tentative SPI in some cases. For example, in some cases, the CU 605 may determine an interference profile (e.g., as discussed above with reference to 525). In such cases, the CU 605 may receive the tentative SPI 1 at 620 and may modify the SPI or add information to the SPI based on the interference profile. In other examples, the CU 605 may not change the tentative SPI 1 and may simply pass or forward the tentative SPI 1 to the DU 610-b.

[0133] At 630 , the CU 605 may communicate or forward the tentative SPI 1 (eg, updated or unchanged) to the DU 610 - b .

[0134] At 635, DU 610-b may update the SPI based on the tentative SPI 2 determined at 615-b and the tentative SPI 1 received at 630. For example, the SPI may be updated based on considering the scheduling status included in both the tentative SPI 1 and the tentative SPI 2 (e.g., the updated SPI may be determined based on considering and coordinating the scheduling information status, flexible status, and invalid status in the tentative SPI 1 and tentative SPI 2 modes for each time unit).

[0135] At 640, DU 610-b may communicate or forward the updated SPI to CU 605. At 645, CU 605 may communicate or forward the updated SPI to DU 610-a. At 650-a and 650-b, DUs 610-a and 610-b may schedule one or more UEs in their respective cells based at least in part on the updated SPI. As mentioned above, in some cases, 650-a and 650-b may be performed in parallel (e.g., at least partially overlapping in time), and in other cases, 650-a and 650-b may be performed independently and at different times.

[0136] Figure 7 An example of a process flow 700 supporting SPI according to aspects of the present disclosure is illustrated. In some examples, the process flow 700 can implement aspects of the wireless communication system 100, the wireless communication system 200, and / or the wireless communication system 201. The process flow 700 can include UE 115-h, UE 115-i, CU 702-a, CU 702-b, DU 705-a, and DU 705-b, which can be referenced Figures 1 to 4Examples of corresponding devices described. In some cases, the CU and DU (e.g., CU 702-a and DU 705-a) may be located in the same device (e.g., a donor base station or a donor IAB may include CU 702-a and DU 705-a). In other cases, the CU and DU may be located in separate locations (e.g., CU 702-a may be located in an IAB donor and DU 705-a may be located in an IAB node, such as a subnode associated with the IAB donor including CU 702-a), and an F1 association (e.g., an L3 signaling channel) may be formed. In some examples, CU 702-a and 702-b may be components of a database, a data center, or a cloud network. Process flow 700 may illustrate distributed inter-AN scheduling coordination using SPI signaling on an Xn-C interface. In the following description of process flow 700, operations between UE 115-h, UE 115-i, CU 702-a, CU 702-b, DU 705-a, and DU 705-b may be transmitted in an order different from the exemplary order shown, or operations performed by UE 115-h, UE 115-i, CU 702-a, CU 702-b, DU 705-a, and DU 705-b may be performed in a different order or at a different time. In some cases, certain operations may also be excluded from process flow 700, or other operations may be added to process flow 700.

[0137] At 710-a and 710-b, CUs 702-a and 702-b may configure UEs 115-h and 115-i to transmit RRM measurement reports. In some cases, 710-a and 710-b may be performed in parallel (e.g., at least partially overlapping in time), and in other cases, 710-a and 710-b may be performed independently and at different times.

[0138] At 715-a and 715-b, UEs 115-h and 115-i may transmit RRM measurement reports to CUs 702-a and 702-b. For example, UEs 115-h and 115-i may receive downlink reference signals from a serving cell and from a neighboring cell. UEs 115-h and 115-i may measure (e.g., detect) the quality of a beam and report the measurement information to the CU (e.g., the RRC layer of a base station). The RRM measurement report may include beam indices and measurement parameters for the serving cell and the neighboring cell. For example, the RRM measurement report may include results of SSB measurements, CSI-RS measurements, beam indices, physical cell IDs, etc. associated with the serving cell and the neighboring cell (e.g., according to the corresponding configurations received by 115-h and 115-i at 710-a and 710-b). In some cases, RRM measurement reports may be transmitted to DUs 705-a and 705-b and may be relayed from DUs 705-a and 705-b to CUs 702-a and 702-b, respectively (e.g., UE 115-h may transmit RRM measurement reports to DU 705-a using Uu signaling, and DU 705-a may pass or relay RRM measurement reports to CU 702-a using F1-AP signaling). In some cases, 715-a and 715-b may be performed in parallel (e.g., at least partially overlapping in time), and in other cases, 715-a and 715-b may be performed independently and at different times.

[0139] At 720-a and 720-b, CUs 702-a and 702-b may create or determine an interference profile based at least in part on the RRM measurement reports received at 715-a and 715-b. For example, CUs 702-a and 702-b may each identify UEs and / or beam pairs that interfere between neighbor cells associated with their respective ANs. The interference profile may include profiles of interfering UEs, interfering beams, etc. In some cases, 720-a and 720-b may be performed in parallel (e.g., at least partially overlapping in time), and in other cases, 720-a and 720-b may be performed independently and at different times.

[0140] At 725, CUs 702-a and 702-b may exchange tentative SPIs. For example, each of CU 702-a and CU 702-b may determine a tentative SPI based on one or more received measurement reports. CUs 702-a and 702-b may exchange such tentative SPIs for distributed inter-AN scheduling coordination. In some examples, inter-AN scheduling coordination may be similar to distributed intra-AN scheduling coordination techniques performed by DUs, as described in reference to Figure 6As discussed in 615 of (e.g., in some cases, each CU may be associated with a different priority, which may affect the determination and content of the experimental SPI exchanged at 725). For example, the experimental SPI may include scheduling information that is further dependent on the AN or CU priority (e.g., whether the experimental SPI includes a scheduling information state, a flexible state, a hard state, a soft state, or an invalid state may depend on the priority associated with the CU in some cases). For example, in some cases, CU 702-a may be associated with a high priority relative to CU 702-b. In such cases, the experimental SPI associated with CU 702-a may include a scheduling information state, while the experimental SPI associated with CU 702-b may include a flexible state.

[0141] At 730-a and 730-b, CU 702-a and 702-b may modify or update the SPI based on the experimental SPI exchanged at 725. For example, the SPI may be updated based on consideration of the scheduling state included in the exchanged experimental SPI (e.g., the updated SPI may be determined by each of CU 702-a and CU 702-b based on consideration and coordination of the scheduling information state, flexible state (e.g., hard state, soft state), and invalid state in the exchanged experimental SPI mode for each time unit). In some cases, 730-a and 730-b may be executed in parallel (e.g., at least partially overlapping in time), and in other cases, 730-a and 730-b may be executed independently and at different times.

[0142] At 735-a and 735-b, CUs 702-a and 702-b may signal the updated SPI to DUs 705-a and 705-b (e.g., via F1-AP signaling). In some cases, 735-a and 735-b may be performed in parallel (e.g., at least partially overlapping in time), and in other cases, 735-a and 735-b may be performed independently and at different times.

[0143] At 740-a and 740-b, DUs 705-a and 705-b may schedule one or more UEs (e.g., including UE 115-h and UE 115-i) in their respective cells based at least in part on the updated SPI. In some cases, 740-a and 740-b may be performed in parallel (e.g., at least partially overlapping in time), and in other cases, 740-a and 740-b may be performed independently and at different times.

[0144] In some cases, DU 705-a and 705-b may refer to DUs of different IAB networks (e.g., different wireless communication systems 201). In some cases, the IAB networks may each include a CU 702 that controls multiple DUs (e.g., CU 702-a may control multiple DUs including at least DU 705-a, and CU 702-b may control multiple DUs including at least DU 705-b). SPI (e.g., the updated SPI at 735-a and 735-b) may be used for inter-CU coordination.

[0145] Figure 8 An example of a process flow 800 for supporting SPI according to aspects of the present disclosure is illustrated. In some examples, the process flow 800 can implement aspects of the wireless communication system 100, the wireless communication system 200, and / or the wireless communication system 201. The process flow 800 can include UE 115-j, UE 115-k, core network 805, CU 807-a, CU 807-b, DU 810-a, and DU 810-b, which can be referenced Figures 1 to 4 An example of a corresponding device described. Process flow 800 may illustrate a coordinated inter-AN coordination scheme between CU 807-a and 807-b using SPI signaling on the NG interface. In the following description of process flow 800, operations between UE 115-j, UE 115-k, core network 805, CU 807-a, CU 807-b, DU 810-a and DU 810-b may be transmitted in an order different from the exemplary order shown, or operations performed by UE 115-j, UE 115-k, core network 805, CU 807-a, CU 807-b, DU 810-a and DU 810-b may be performed in a different order or at different times. In some cases, certain operations may also be excluded from process flow 800, or other operations may be added to process flow 800.

[0146] At 815-a and 815-b, CUs 807-a and 807-b may configure UEs 115-j and 115-k to transmit RRM measurement reports. In some cases, 815-a and 815-b may be performed in parallel (e.g., at least partially overlapping in time), and in other cases, 815-a and 815-b may be performed independently and at different times.

[0147] At 820-a and 820-b, UEs 115-j and 115-k may transmit RRM measurement reports to CUs 807-a and 807-b. For example, UEs 115-j and 115-k may receive downlink reference signals from a serving cell and from a neighbor cell. UEs 115-j and 115-k may measure (e.g., detect) the quality of a beam and report the measurement information to the CU (e.g., the RRC layer of a base station). The RRM measurement report may include beam indices and measurement parameters for the serving cell and the neighbor cell. For example, the RRM measurement report may include results of SSB measurements, CSI-RS measurements, beam indices, physical cell IDs, etc. associated with the serving cell and the neighbor cell (e.g., according to the corresponding configurations received by UEs 115-j and 115-k at 815-a and 815-b). In some cases, RRM measurement reports may be transmitted to DUs 810-a and 810-b, and may be relayed from DUs 810-a and 810-b to CUs 807-a and 807-b, respectively (e.g., UE 115-j may transmit RRM measurement reports to DU 810-a using Uu signaling, and DU 810-a may pass or relay RRM measurement reports to CU 807-a using F1-AP signaling). In some cases, 820-a and 820-b may be performed in parallel (e.g., at least partially overlapping in time), and in other cases, 820-a and 820-b may be performed independently and at different times.

[0148] At 825-a and 825-b, CUs 807-a and 807-b may create or determine an interference profile based at least in part on the RRM measurement reports received at 820-a and 820-b. For example, CUs 807-a and 807-b may each identify UEs and / or beam pairs that interfere between neighboring cells associated with their respective ANs. The interference profile may include profiles of interfering UEs, interfering beams, and the like. In some cases, 825-a and 825-b may be executed in parallel (e.g., at least partially overlapping in time), and in other cases, 825-a and 825-b may be executed independently and at different times. At 830-a and 830-b, CUs 807-a and 807-b may transmit experimental SPIs to the core network 805. CU 807-a and 807-b may each determine a tentative SPI (e.g., CU 807-a may determine tentative SPI 1 and CU 807-b may determine tentative SPI 2). For example, CU 807-a and 807-b may determine the tentative SPI based on their respective ANs (e.g., based on measurement reports from UEs within their respective cells). In some cases, 830-a and 830-b may be performed in parallel (e.g., at least partially overlapping in time), and in other cases, 830-a and 830-b may be performed independently and at different times.

[0149] At 835, the core network 805 may modify or update the SPI based on the tentative SPI received at 830-a and 830-b.

[0150] At 840, the core network 805 may signal the updated SPI to CUs 807-a and 807-b (e.g., via NG signaling). At 845-a and 845-b, CUs 807-a and 807-b may forward or pass (e.g., and in some cases adjust or update before forwarding or passing) the updated SPI to DUs 810-a and 810-b. At 850-a and 850-b, DUs 810-a and 810-b may schedule one or more UEs (e.g., including UE 115-j and UE 115-k) in their respective cells based at least in part on the updated SPI.

[0151] Fig. 9 A block diagram 900 of a device 905 supporting SPI according to aspects of the present disclosure is shown. The device 905 may be an example of aspects of a base station 105 as described herein. The device 905 may include a receiver 910, a communication manager 915, and a transmitter 920. The device 905 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0152] The receiver 910 may receive information, such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to supporting SPI, etc.). The information may be passed to other components of the device 905. The receiver 910 may be a reference Fig.12 Examples of aspects of the described transceiver 1220. The receiver 910 may utilize a single antenna or a collection of antennas.

[0153] The communication manager 915 may: receive a measurement report of a UE, the measurement report including a measured value of at least one beam of a cellular cell measured by the UE; and an indication of a scheduling plan for a scheduling state mode within a time period for a scheduling node identifier, the indication of the scheduling plan being based on the measurement report and to be used by the scheduling node to schedule communication resources for the UE. The communication manager 915 may be an example of various aspects of the communication manager 1210 described herein. The actions performed by the communication manager 915 described herein may be implemented to achieve one or more potential advantages described herein. An implementation may allow a network (e.g., a device, such as a base station, CU, DU, etc.) to mitigate interference and more efficiently utilize wireless resources within a wireless communication system via identification of a scheduling plan indication (e.g., SPI), which is used to specify a scheduling state mode within a time period (e.g., based on a received measurement report of a UE). For example, in some cases, the SPI may be used to indicate scheduling or coordination of data transmission scheduling, beam patterns, etc., which may provide improved quality and service reliability at the UE 115, because data transmission scheduling, scheduled beam patterns, etc. performed by base stations, CUs, DUs, etc. may be coordinated. Such coordination can result in reduced network latency (e.g., reduced latency for retransmissions due to interference, etc.), reduced power consumption by UE 115 and / or base station 105 (e.g., reduced power consumption associated with delivering any retransmissions), etc.

[0154] The communication manager 915 or its subcomponents may be implemented in hardware, in code (e.g., software or firmware) executed by a processor, or any combination thereof. If implemented in code executed by a processor, the functions of the communication manager 915 or its subcomponents may be performed by a general purpose processor, a DSP, an application specific integrated circuit (ASIC), an FPGA or other programmable logic device designed to perform the functions described in the present disclosure, discrete gate or transistor logic, discrete hardware components, or any combination thereof.

[0155] The communication manager 915 or its subcomponents may be physically located at various locations, including being distributed such that portions of functionality are implemented by one or more physical components at different physical locations. In some examples, according to various aspects of the present disclosure, the communication manager 915 or its subcomponents may be separate and distinct components. In some examples, according to various aspects of the present disclosure, the communication manager 915 or its subcomponents may be combined with one or more other hardware components (including, but not limited to, input / output (I / O) components, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof).

[0156] The transmitter 920 may transmit signals generated by other components of the device 905. In some examples, the transmitter 920 may be co-located with the receiver 910 in a transceiver module. For example, the transmitter 920 may be a reference Fig.12 Examples of various aspects of the described transceiver 1220. The transmitter 920 may utilize a single antenna or a collection of antennas.

[0157] Fig.10 A block diagram 1000 of a device 1005 supporting SPI according to aspects of the present disclosure is shown. The device 1005 may be an example of aspects of the device 905 or base station 105 as described herein. The device 1005 may include a receiver 1010, a communication manager 1015, and a transmitter 1030. The device 1005 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0158] The receiver 1010 may receive information, such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to supporting SPI, etc.). The information may be passed to other components of the device 1005. The receiver 1010 may be a reference Fig.12 Examples of various aspects of the described transceiver 1220. The receiver 1010 may utilize a single antenna or a collection of antennas.

[0159] The communication manager 1015 may be an example of aspects of the communication manager 915 as described herein. The communication manager 1015 may include a measurement report manager 1020 and an SPI manager 1025. The communication manager 1015 may be an example of aspects of the communication manager 1210 as described herein.

[0160] The measurement report manager 1020 may receive a measurement report of a UE, the measurement report including a measured value of at least one beam of a cell measured by the UE.

[0161] The SPI manager 1025 may identify, for the scheduling node, an indication of a scheduling plan that specifies a scheduling state mode within a time period, the indication of the scheduling plan being based on the measurement report and to be used by the scheduling node to schedule communication resources for the UE.

[0162] Transmitter 1030 can transmit signals generated by other components of device 1005. In some examples, transmitter 1030 can be co-located with receiver 1010 in a transceiver module. For example, transmitter 1030 can be a reference Fig.12 Examples of various aspects of the described transceiver 1220. The transmitter 1030 may utilize a single antenna or a collection of antennas.

[0163] Fig.11 A block diagram 1100 of a communication manager 1105 supporting SPI according to aspects of the present disclosure is shown. The communication manager 1105 may be an example of aspects of the communication manager 915, the communication manager 1015, or the communication manager 1210 described herein. The communication manager 1105 may include a measurement report manager 1110, an SPI manager 1115, a tentative SPI manager 1120, an SPI update manager 1125, an SPI priority manager 1130, and an interference profile manager 1135. Each of these modules may communicate directly or indirectly with each other (e.g., via one or more buses). In some cases, the communication manager 1105 may be included in a scheduling node (such as a DU).

[0164] The measurement report manager 1110 may receive a measurement report from a UE, the measurement report including a measured value of at least one beam of a cell measured by the UE. In some examples, the measurement report manager 1110 may transmit the measurement report to the CU by a scheduling node. In some examples, the measurement report manager 1110 may receive an indication of a scheduling plan from the CU based on transmitting the measurement report. In some examples, the measurement report manager 1110 may transmit configuration information for the UE to use to perform measurements on the cell, or at least one additional cell, or a combination thereof. In some examples, the measurement report manager 1110 may receive at least one additional measurement report from the UE based on the transmitted configuration information. The actions performed by the measurement report manager 1110 as described herein may be implemented to determine an interference profile, identify an interfering UE, an interfering beam, etc. For example, the actions performed by the measurement report manager 1110 as described herein may be implemented so that the interfering UE 115, the interfering beam direction, etc. may be assigned to different time units or different non-overlapping resource block allocations, which may provide interference mitigation and more efficient use of wireless resources.

[0165] The SPI manager 1115 may identify an indication of a scheduling plan for a scheduling node, the indication of the scheduling plan specifying a scheduling state mode within a time period, the indication of the scheduling plan being based on the measurement report and to be used by the scheduling node to schedule communication resources for the UE. Such indications of scheduling plans (e.g., SPI) may be used to coordinate beam sweeping patterns, schedule communications for UE 115, coordinate UE 115 scheduling between neighboring cells, beam patterns, beamformed transmissions, and the like. Such coordination via SPI signaling may provide improved inter-cell coordination and scheduling, intra-cell coordination and scheduling, and the like. In addition, such coordination and scheduling techniques described herein may mitigate interference and utilize wireless resources more efficiently, which may provide improved quality of service for UE 115, base station 105, and the like.

[0166] In some examples, when the indicated scheduling state is a flexible state, the scheduling node is allowed to schedule any UE, or any beam direction, or a combination thereof. In some examples, when the indicated scheduling state is an invalid state, the scheduling node is blocked from scheduling all UEs, or all beam directions, or a combination thereof. In some examples, the SPI manager 1115 may transmit an indication of a scheduling plan on a GC-PDCCH, or an RRC message, or a combination thereof. In some examples, the SPI manager 1115 may receive a first indication of a first scheduling plan through a first type of interface. In some examples, the SPI manager 1115 may receive a second indication of a second scheduling plan through a second type of interface.

[0167] In some cases, the scheduling state mode includes a scheduling information state, or a flexible state, or an invalid state, or a combination thereof. In some cases, the time period includes one or more time slots or mini time slots. In some cases, the indication of the scheduling plan identifies the values ​​used for scheduling for a scheduling state, and these values ​​include a set of UE indexes, or a set of beam indexes, or a set of angle values, or a set of position values, or a combination thereof. In some cases, the indication of the scheduling plan schedules data transmission for different UEs, or different beam modes, or a combination thereof for a scheduling state. In some cases, the indication of the scheduling plan identifies the allocated resource blocks, or buffer status, or priority, or communication type, or MCS, or target SINR, or target transmit power, or target receive power, or a combination thereof for a scheduling state. In some cases, the scheduling node includes a DU of an IAB network. In some cases, the IAB network includes a CU that controls a group of DUs including the DU. In some cases, the SPI is used for inter-DU coordination via the CU of the IAB network. In some cases, the SPI is used for inter-CU coordination via one or more Xn_C interfaces, or via the core network, or a combination thereof.

[0168] The experimental SPI manager 1120 may determine the experimental scheduling plan by the scheduling node (e.g., based on L1 / L2 signaling from one or more UEs, such as CSI reports, BSRs, etc.). In some examples, the experimental SPI manager 1120 may transmit an indication of the experimental scheduling plan to the CU. In some examples, the experimental SPI manager 1120 may receive an indication of the experimental scheduling plan from a second scheduling node via the CU at the scheduling node.

[0169] The SPI update manager 1125 may receive an indication of an updated schedule based on the tentative schedule from the CU, wherein the updated schedule is a schedule for the scheduling node. In some examples, the SPI update manager 1125 may determine an updated schedule for the scheduling node based on the indication of the received tentative schedule by the scheduling node.

[0170] The SPI priority manager 1130 may identify at least one priority rule of a scheduling plan applicable to the scheduling node by the scheduling node, wherein the updated scheduling plan for the scheduling node is determined based on the indication of the received tentative scheduling plan and the at least one priority rule. In some examples, the SPI priority manager 1130 may identify a conflict between a first indication of a first scheduling plan for the scheduling node and a second indication of a scheduling plan for the scheduling node. In some examples, the SPI priority manager 1130 may select the first scheduling plan or the second scheduling plan to become the scheduling plan based on a rule for scheduling plan selection. In some examples, the SPI priority manager 1130 may identify a first time duration associated with the first scheduling plan and a second time duration associated with the second scheduling plan, wherein the rule indicates that the first scheduling plan is selected based on the second time duration being longer than the first time duration. In some examples, the SPI priority manager 1130 may select the first scheduling plan to become the scheduling plan based on the rule indicating that the interface of the first type overrides the interface of the second type.

[0171] The interference profile manager 1135 may receive an interference profile from the central unit at the scheduling node. In some examples, the interference profile manager 1135 may identify at least one UE, or at least one beam direction, or a combination thereof as interfering based on the received interference profile. In some examples, the interference profile manager 1135 may assign the at least one UE, or the at least one beam direction, or a combination thereof to different time units, or different non-overlapping resource block allocations, or a combination thereof by the scheduling node.

[0172] Fig.12A diagram of a system 1200 including a device 1205 supporting SPI according to aspects of the present disclosure is shown. The device 1205 may be an example of a device 905, a device 1005, or a DU as described herein or include components thereof. The device 1205 may include components for two-way voice and data communications, including components for transmitting and receiving communications, including a communication manager 1210, a network communication manager 1215, a transceiver 1220, an antenna 1225, a memory 1230, and a processor 1240. These components may be in electronic communication via one or more buses (e.g., a bus 1245).

[0173] The communication manager 1210 can: receive a measurement report from a UE, the measurement report including measured values ​​of at least one beam of a cellular cell measured by the UE; and an indication of a scheduling plan that specifies a scheduling state mode within a time period for a scheduling node identifier, the indication of the scheduling plan being based on the measurement report and to be used by the scheduling node to schedule communication resources for the UE.

[0174] The network communication manager 1215 can manage communications with other CUs 240 (e.g., or CU 215), as described in reference Figure 1-8 For example, the network communication manager 1215 may include a controller or scheduler for controlling communication with the CU through the F1-AP interface. For example, the network communication manager 1215 may provide an F1-AP interface for SPI signaling for the coordinated scheduling technology described herein.

[0175] The transceiver 1220 can communicate bidirectionally via one or more antennas, wired or wireless links, as described above. For example, the transceiver 1220 may represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. The transceiver 1220 may also include a modem to modulate packets and provide the modulated packets to an antenna for transmission, and demodulate packets received from an antenna.

[0176] In some cases, a wireless device may include a single antenna 1225. However, in some cases, the device may have more than one antenna 1225, which may be capable of transmitting or receiving multiple wireless transmissions concurrently.

[0177] Memory 1230 may include RAM and ROM. Memory 1230 may store computer-readable, computer-executable code or software 1235 including instructions that, when executed, cause the processor to perform the various functions described herein. In some cases, memory 1230 may include, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0178] Processor 1240 may include an intelligent hardware device (e.g., a general purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor 1240 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into processor 1240. Processor 1240 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1230) to cause device 1205 to perform various functions (e.g., functions or tasks supporting SPI).

[0179] The software 1235 may include code or instructions for implementing various aspects of the present disclosure, including instructions for supporting wireless communications. The software 1235 may be stored in a non-transitory computer-readable medium, such as a system memory or other type of memory. In some cases, the software 1235 may not be directly executed by the processor 1240, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein.

[0180] Fig.13 A block diagram 1300 of a communication manager 1305 supporting SPI according to aspects of the present disclosure is shown. The communication manager 1305 may be an example of aspects of the communication manager 1610 described herein. The communication manager 1305 may include a measurement report manager 1310 and a SPI manager 1315. Each of these modules may communicate with each other directly or indirectly (e.g., via one or more buses).

[0181] The measurement report manager 1310 may receive a measurement report from a UE, the measurement report including a measured value of at least one beam of a cell measured by the UE. In some examples, the measurement report manager 1310 may transmit configuration information for the UE to use to perform measurements on the cell, or at least one additional cell, or a combination thereof. In some examples, the measurement report manager 1310 may receive at least one additional measurement report from the UE based on the transmitted configuration information. The actions performed by the measurement report manager 1310 as described herein may be implemented to determine an interference profile, identify an interfering UE, an interfering beam, etc. For example, the actions performed by the measurement report manager 1310 as described herein may be implemented so that an interfering UE 115, an interfering beam direction, etc. may be assigned to different time units or different non-overlapping resource block allocations, which may provide interference mitigation and more efficient use of wireless resources.

[0182] The SPI manager 1315 may identify an indication of a scheduling plan for a scheduling node, the indication of the scheduling plan specifying a scheduling state mode within a time period, the indication of the scheduling plan being based on the measurement report and to be used by the scheduling node to schedule communication resources for the UE. In some examples, when the indicated scheduling state is a flexible state, the scheduling node is allowed to schedule any UE, or any beam direction, or a combination thereof. In some examples, when the indicated scheduling state is an invalid state, the scheduling node is prevented from scheduling all UEs, or all beam directions, or a combination thereof. In some examples, the indication identifying the scheduling plan includes an indication that the scheduling plan is determined by the core network node based on the received measurement report. In some examples, the SPI manager 1315 may transmit the indication of the scheduling plan on a GC-PDCCH, an RRC message, an F1 interface, an Xn-C interface, an NG interface, or a combination thereof.

[0183] The actions performed by the SPI manager 1315 as described herein may be implemented to achieve one or more potential advantages described herein. An implementation may allow a network (e.g., a network device such as a base station, CU, DU, etc.) to mitigate interference and more efficiently utilize radio resources within a wireless communication system via identification of a scheduling plan indication (e.g., SPI), which is used to specify a scheduling state mode within a time period (e.g., based on a received UE measurement report). For example, in some cases, the SPI may be used to indicate scheduling or coordination of data transmission scheduling, beam patterns, etc., which may provide improved quality and service reliability at the UE 115 because data transmission scheduling, scheduled beam patterns, etc. performed by the base station, CU, DU, etc. may be coordinated. Such coordination may result in reduced network latency (e.g., reduced latency for retransmissions due to interference, etc.), reduced power consumption of the UE 115 and / or the base station 105 (e.g., reduced power consumption associated with delivering any retransmissions), etc.

[0184] In some cases, the scheduling state mode includes a scheduling information state, or a flexible state, or an invalid state, or a combination thereof. In some cases, the time period includes one or more time slots or mini time slots. In some cases, the indication of the scheduling plan identifies the values ​​used for scheduling for a scheduling state, and these values ​​include a set of UE indexes, or a set of beam indexes, or a set of angle values, or a set of position values, or a combination thereof. In some cases, the indication of the scheduling plan schedules data transmission for different UEs, or different beam modes, or a combination thereof for a scheduling state. In some cases, the indication of the scheduling plan identifies the allocated resource blocks, or the buffer status, or the priority, or the communication type, or the MCS, or the target SINR, or the target transmit power, or the target receive power, or a combination thereof for a scheduling state.

[0185] In some cases, the method further includes transmitting an indication of the scheduling plan determined by the core network node to the CU. In some cases, the scheduling node includes a DU of an IAB network. In some cases, the IAB network includes a CU that controls a group of DUs including the DU. In some cases, the SPI is used for inter-DU coordination via the CU of the IAB network. In some cases, the SPI is used for inter-CU coordination via one or more Xn_C interfaces, or via the core network, or a combination thereof.

[0186] Fig.14 A diagram of a system 1400 including a device 1405 supporting SPI according to aspects of the present disclosure is shown. The device 1405 may be an example of a network or network core as described herein or include components thereof. The device 1405 may include components for bidirectional data communication, including components for transmitting and receiving communications, including a communication manager 1410, a network communication manager 1415, a memory 1430, a processor 1440, and an AN communication manager 1445. These components may be in electronic communication via one or more buses (e.g., bus 1450).

[0187] The communication manager 1410 may be an example of the communication manager 1305 as described herein. For example, the communication manager 1410 may perform any of the methods or processes described above. In some cases, the communication manager 1410 may be implemented in hardware, software executed by a processor, firmware, or any combination thereof.

[0188] The network communication manager 1415 can manage communications with other base stations 105 (eg, or base station 210, IAB donor 230, etc.), for example, via an NG interface, as described in reference to Figure 1-8 In some examples, the network communication manager 1415 may provide an X2 interface within the LTE / LTE-A wireless communication network technology to provide communication between base stations 105. That is, the network communication manager 1415 may provide an NG interface for SPI signaling for the coordinated scheduling technology described herein.

[0189] The access network communication manager 1445 can manage communication with one or more components of the same core network (intra-core network communication), or communication with network nodes of other networks (inter-network communication), for example, communication with network components of core network 130 or core network 225.

[0190] A database controller can manage data storage and processing in a database. In some cases, a user can interact with the database controller. In other cases, the database controller can operate automatically without user interaction. The database can be an example of a single database, a distributed database, multiple distributed databases, a data store, a data lake, or an emergency backup database.

[0191] Memory 1430 may include random access memory (RAM) and read-only memory (ROM). Memory 1430 may store computer-readable, computer-executable code or software 1435 including instructions that, when executed, cause the processor to perform the various functions described herein. In some cases, memory 1430 may include, among other things, a basic input / output system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0192] Processor 1440 may include an intelligent hardware device (e.g., a general purpose processor, a DSP, a central processing unit (CPU), a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor 1430 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into processor 1440. Processor 1440 may be configured to execute computer-readable instructions stored in memory 1430 to perform various functions (e.g., functions or tasks supporting SPI).

[0193] The software 1435 may include instructions for implementing various aspects of the present disclosure, including instructions for supporting wireless communications. The software 1435 may be stored in a non-transitory computer-readable medium, such as a system memory or other type of memory. In some cases, the software 1645 may not be directly executed by the processor 1440, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein.

[0194] Fig.15 A block diagram 1500 of a communication manager 1505 supporting SPI according to aspects of the present disclosure is shown. The communication manager 1505 may be an example of aspects of the communication manager 2010 described herein. The communication manager 1505 may include a measurement report manager 1510, a SPI manager 1515, a tentative SPI manager 1520, a SPI update manager 1525, and an interference profile manager 1530. Each of these modules may communicate with each other directly or indirectly (e.g., via one or more buses).

[0195] The measurement report manager 1510 may receive a measurement report of a UE, the measurement report including a measured value of at least one beam of a cell measured by the UE. In some examples, the measurement report manager 1510 may transmit the measurement report to a core network node. In some examples, the measurement report manager 1510 may receive at least one additional measurement report of at least one additional UE from the scheduling node or at least one second scheduling node at the CU. In some examples, the measurement report manager 1510 may transmit configuration information for the UE to perform measurements on the cell, or at least one additional cell, or a combination thereof. In some examples, the measurement report manager 1510 may receive at least one additional measurement report from the UE based on the transmitted configuration information. The actions performed by the measurement report manager 1510 as described herein may be implemented to determine an interference profile, identify an interfering UE, an interfering beam, etc. For example, the actions performed by the measurement report manager 1510 as described herein may be implemented so that the interfering UE 115, the interfering beam direction, etc. may be assigned to different time units or different non-overlapping resource block allocations, which may provide interference mitigation and more efficient use of radio resources.

[0196] The SPI manager 1515 may identify an indication of a scheduling plan for a scheduling node, the indication of the scheduling plan specifying a scheduling state mode within a time period, the indication of the scheduling plan being based on the measurement report and to be used by the scheduling node to schedule communication resources for the UE. In some examples, when the indicated scheduling state is a flexible state, the scheduling node is allowed to schedule any UE, or any beam direction, or a combination thereof. In some examples, when the indicated scheduling state is an invalid state, the scheduling node is prevented from scheduling all UEs, or all beam directions, or a combination thereof. In some examples, the SPI manager 1515 may transmit the indication of the scheduling plan to the scheduling node by the first CU, wherein the first CU identifies the indication of the scheduling plan. In some examples, the SPI manager 1515 may determine the indication of the scheduling plan by the first CU based on the received measurement report, which is received from the scheduling node.

[0197] In some examples, the SPI manager 1515 may receive an indication of a scheduling plan from a second CU, and the received indication is transmitted by the CU to the scheduling node. In some examples, the SPI manager 1515 may receive an indication of a scheduling plan from a core network node. In some examples, the SPI manager 1515 may transmit the indication of the scheduling plan to the second CU or the core network node or a combination thereof by the first CU, wherein the first CU identifies the indication of the scheduling plan based on the received measurement report. In some examples, the SPI manager 1515 may transmit the indication of the scheduling plan to the child node of the IAB by the parent node of the IAB. In some examples, the SPI manager 1515 may transmit the indication of the scheduling plan on the GC-PDCCH, or the RRC message, or a combination thereof.

[0198] In some cases, the scheduling state mode includes a scheduling information state, or a flexible state, or an invalid state, or a combination thereof. In some cases, the time period includes one or more time slots or mini time slots. In some cases, the indication of the scheduling plan identifies the values ​​used for scheduling for a scheduling state, and these values ​​include a set of UE indexes, or a set of beam indexes, or a set of angle values, or a set of position values, or a combination thereof. In some cases, the indication of the scheduling plan schedules data transmission for different UEs, or different beam modes, or a combination thereof for a scheduling state. In some cases, the indication of the scheduling plan identifies the allocated resource blocks, or buffer status, or priority, or communication type, or MCS, or target SINR, or target transmit power, or target receive power, or a combination thereof for a scheduling state. In some cases, the scheduling node includes a DU of an IAB network. In some cases, the IAB network includes a CU that controls a group of DUs including the DU. In some cases, the SPI is used for inter-DU coordination via the CU of the IAB network. In some cases, the SPI is used for inter-CU coordination via one or more Xn_C interfaces, or via the core network, or a combination thereof.

[0199] The actions performed by the SPI manager 1515 (e.g., and / or the experimental SPI manager 1520, the SPI update manager 1525, etc.) as described herein may be implemented to achieve one or more potential advantages described herein. An implementation may allow a network (e.g., a device, such as a base station, CU, DU, etc.) to mitigate interference and more efficiently utilize radio resources within a wireless communication system via identification of a scheduling plan indication (e.g., SPI) that specifies a scheduling state mode within a time period (e.g., based on a received UE measurement report). For example, in some cases, the SPI may be used to indicate scheduling or coordination of data transmission scheduling, beam patterns, etc., which may provide improved quality and service reliability at the UE 115 because data transmission scheduling, scheduled beam patterns, etc. performed by the base station, CU, DU, etc. may be coordinated. Such coordination may result in reduced network latency (e.g., reduced latency for retransmissions due to interference, etc.), reduced power consumption of the UE 115 and / or the base station 105 (e.g., reduced power consumption associated with delivering any retransmissions), etc.

[0200] The experimental SPI manager 1520 may receive an indication of an experimental schedule from the scheduling node. In some examples, the experimental SPI manager 1520 may receive an indication of one or more experimental schedules at the CU, each of the one or more experimental schedules for an additional scheduling node. In some examples, the experimental SPI manager 1520 may forward the indication of the one or more experimental schedules to the scheduling node.

[0201] The SPI update manager 1525 may determine an updated scheduling plan for the scheduling node based on the received indication of the tentative scheduling plan and the received measurement report, wherein the updated scheduling plan is a scheduling plan for the scheduling node. In some cases, the updated scheduling plan for the scheduling node is further based on at least one additional tentative scheduling plan received from at least one additional scheduling node and further based on at least one additional measurement report from at least one additional UE.

[0202] The interference profile manager 1530 may determine an interference profile by the CU based on the received measurement report and the at least one additional measurement report, wherein the indication of the scheduling plan is identified based on the determined interference profile. In some cases, the interference profile includes a profile of the UE that causes interference, or the beam that causes interference, or a combination thereof.

[0203] Fig.16A diagram of a system 1600 including a device 1605 supporting SPI according to various aspects of the present disclosure is shown. The device 1605 may be an example of a base station 105 or DU as described herein or include components thereof. The device 1605 may include components for two-way voice and data communications, including components for transmitting and receiving communications, including a communication manager 1610, a network communication manager 1615, a transceiver 1620, an antenna 1625, a memory 1630, a processor 1640, and an inter-station communication manager 1645. These components may be in electronic communication via one or more buses (e.g., a bus 1655).

[0204] The communication manager 1610 may: receive a measurement report from a UE, the measurement report including measured values ​​of at least one beam of a cellular cell measured by the UE; and an indication of a scheduling plan for a scheduling state mode specified within a time period for a scheduling node identifier, the indication of the scheduling plan being based on the measurement report and to be used by the scheduling node to schedule communication resources for the UE.

[0205] The network communications manager 1615 may manage communications with the core network (e.g., via one or more wired backhaul links), such as communications to the core network 130 (e.g., to the core network 225 (e.g., NGC) via an NG interface (e.g., a backhaul link 132). For example, the network communications manager 1615 may provide an NG interface for SPI signaling (transmission and / or reception) for the coordinated scheduling techniques described herein.

[0206] In some cases, the device 1605 may include a transceiver that can communicate bidirectionally via one or more antennas, wired or wireless links, as described above. For example, a transceiver may represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. The transceiver may also include a modem to modulate packets and provide the modulated packets to an antenna for transmission, and demodulate packets received from the antenna. In some cases, the device 1605 may include a single antenna. However, in some cases, the device may have more than one antenna, which may be able to transmit or receive multiple wireless transmissions concurrently.

[0207] Memory 1630 may include RAM, ROM, or a combination thereof. Memory 1630 may store computer readable code or software 1635 including instructions that, when executed by a processor (e.g., processor 1640), cause the device to perform various functions described herein. In some cases, memory 1630 may include, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0208] Processor 1640 may include an intelligent hardware device (e.g., a general purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor 1640 may be configured to operate a memory array using a memory controller. In some cases, the memory controller may be integrated into processor 1640. Processor 1640 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1630) so that the device performs various functions (e.g., functions or tasks supporting SPI).

[0209] The inter-station communication manager 1645 may manage communications with the base station 105, the base station 210, the CU 215, the IAB donor 230, the IAB node 235, and / or the CU 240, as described with reference to Figure 1-8 As described, and may include a controller or scheduler for controlling communications with these nodes. For example, the inter-station communication manager 1645 may coordinate the scheduling of transmissions to the UE 115 for various interference mitigation techniques (such as beamforming or joint transmission). In some examples, the inter-station communication manager 1645 may provide an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between base stations 105, or may provide an Xn-C interface of a 5G / NR wireless communication network technology to provide communications between base stations 210, CU 215, IAB donor 230, IAB node 235, and / or CU 240.

[0210] The DU communication manager 1650 may manage communications with one or more DUs 220 and / or one or more DUs 245, as described in reference to Figure 1-8 As described herein. For example, the network communication manager 1650 may include a controller or scheduler for controlling communication with a DU (e.g., a gNB-DU) via an F1-AP interface. For example, the DU communication manager 1650 may provide an F1-AP interface for signaling (e.g., transmitting or receiving) of SPI and / or measurement reports for the coordinated scheduling techniques described herein.

[0211] The software 1635 may include instructions for implementing various aspects of the present disclosure, including instructions for supporting wireless communications. The software 1635 may be stored in a non-transitory computer-readable medium, such as a system memory or other type of memory. In some cases, the software 1635 may not be directly executed by the processor 1640, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein.

[0212] It should be noted that the above methods describe possible implementations, and that the operations and steps may be rearranged or otherwise modified and other implementations are possible. Furthermore, aspects from two or more methods may be combined.

[0213] Fig.17 1 is a flowchart illustrating a method 1700 for supporting SPI according to aspects of the present disclosure. The operations of the method 1700 may be implemented by the base station 105 or its components as described herein. For example, the operations of the method 1700 may be implemented by the base station 105 or its components as described herein. Figures 9 to 16 In some examples, the base station may execute an instruction set to control the functional elements of the base station to perform the functions described below. Additionally or alternatively, the base station may use dedicated hardware to perform various aspects of the functions described below.

[0214] At 1705, the base station may receive a measurement report from a UE, the measurement report including a measured value of at least one beam of a cell measured by the UE. The operations of 1705 may be performed according to the methods described herein. In some examples, aspects of the operations of 1705 may be performed as described with reference to Figures 9 to 16 The measurement report manager described herein is used to perform the above operations.

[0215] At 1710, the base station may identify an indication of a scheduling plan for a scheduling node, the indication of the scheduling plan specifying a scheduling state mode within a time period, the indication of the scheduling plan being based on the measurement report and to be used by the scheduling node to schedule communication resources for the UE. The operations of 1710 may be performed according to the methods described herein. In some examples, aspects of the operations of 1710 may be performed as described with reference to Figures 9 to 16 The SPI manager described here is executed.

[0216] Fig.18 1 is a flowchart illustrating a method 1800 for supporting SPI according to aspects of the present disclosure. The operations of the method 1800 may be implemented by the base station 105 or its components as described herein. For example, the operations of the method 1800 may be implemented by the base station 105 or its components as described herein. Figures 9 to 16 In some examples, the base station may execute an instruction set to control the functional elements of the base station to perform the functions described below. Additionally or alternatively, the base station may use dedicated hardware to perform various aspects of the functions described below.

[0217] At 1805, the base station may receive a measurement report from a UE, the measurement report including a measured value of at least one beam of a cell measured by the UE. The operations of 1805 may be performed according to the methods described herein. In some examples, aspects of the operations of 1805 may be performed as described with reference to Figures 9 to 16 The measurement report manager described herein is used to perform the above operations.

[0218] At 1810, the base station may transmit the measurement report to the CU by the scheduling node. The operation of 1810 may be performed according to the methods described herein. In some examples, various aspects of the operation of 1810 may be performed as described with reference to Figures 9 to 16 The measurement report manager described herein is used to perform the above operations.

[0219] At 1815, the base station may receive an indication of a scheduling plan from the CU based on transmitting the measurement report. The operations of 1815 may be performed according to the methods described herein. In some examples, aspects of the operations of 1815 may be performed as described with reference to Figures 9 to 16 The SPI manager described here is executed.

[0220] At 1820, the base station may identify an indication of a scheduling plan for the scheduling node, the indication of the scheduling plan specifying a scheduling state mode within a time period, the indication of the scheduling plan being based on the measurement report and to be used by the scheduling node to schedule communication resources for the UE. The operations of 1820 may be performed according to the methods described herein. In some examples, aspects of the operations of 1820 may be performed as described with reference to Figures 9 to 16 The SPI manager described here is executed.

[0221] Fig.19 1 is a flowchart illustrating a method 1900 for supporting SPI according to aspects of the present disclosure. The operations of the method 1900 may be implemented by the base station 105 or its components as described herein. For example, the operations of the method 1900 may be implemented by the base station 105 or its components as described herein. Figures 9 to 16 In some examples, the base station may execute an instruction set to control the functional elements of the base station to perform the functions described below. Additionally or alternatively, the base station may use dedicated hardware to perform various aspects of the functions described below.

[0222] At 1905, the base station may receive a measurement report from a UE, the measurement report including a measured value of at least one beam of a cell measured by the UE. The operations of 1905 may be performed according to the methods described herein. In some examples, aspects of the operations of 1905 may be performed as described with reference to Figures 9 to 16 The measurement report manager described herein is used to perform the above operations.

[0223] At 1910, the base station may determine a tentative scheduling plan by a scheduling node. The operations of 1910 may be performed according to the methods described herein. In some examples, various aspects of the operations of 1910 may be performed as described with reference to Figures 9 to 16 The experimental SPI manager described is implemented.

[0224] At 1915, the base station may transmit an indication of the tentative scheduling plan to the CU. The operations of 1915 may be performed according to the methods described herein. In some examples, aspects of the operations of 1915 may be performed as described with reference to Figures 9 to 16 The experimental SPI manager described is implemented.

[0225] At 1920, the base station may receive an indication of an updated scheduling plan based on the tentative scheduling plan from the CU, wherein the updated scheduling plan is a scheduling plan for the scheduling node. The operations of 1920 may be performed according to the methods described herein. In some examples, aspects of the operations of 1920 may be performed as described with reference to Figures 9 to 16 The SPI update manager described above is used to perform the

[0226] At 1925, the base station may identify an indication of a scheduling plan for the scheduling node, the indication of the scheduling plan specifying a scheduling state mode within a time period, the indication of the scheduling plan being based on the measurement report and to be used by the scheduling node to schedule communication resources for the UE. The operations of 1925 may be performed according to the methods described herein. In some examples, aspects of the operations of 1925 may be performed as described with reference to Figures 9 to 16 The SPI manager described here is executed.

[0227] Fig. 20 2000 is shown to illustrate a flow chart of a method 2000 for supporting SPI according to aspects of the present disclosure. The operations of the method 2000 may be implemented by the base station 105 or its components as described herein. For example, the operations of the method 2000 may be implemented by the base station 105 or its components as described herein. Figures 9 to 16 In some examples, the base station may execute an instruction set to control the functional elements of the base station to perform the functions described below. Additionally or alternatively, the base station may use dedicated hardware to perform various aspects of the functions described below.

[0228] At 2005, the base station may receive a measurement report from a UE, the measurement report including a measured value of at least one beam of a cellular cell measured by the UE. The operation of 2005 may be performed according to the methods described herein. In some examples, aspects of the operation of 2005 may be performed as described with reference to Figures 9 to 16 The measurement report manager described herein is used to perform the above operations.

[0229] At 2010, the base station may identify an indication of a scheduling plan for the scheduling node, the indication of the scheduling plan specifying a scheduling state mode within a time period, the indication of the scheduling plan being based on the measurement report and to be used by the scheduling node to schedule communication resources for the UE. The operations of 2010 may be performed according to the methods described herein. In some examples, aspects of the operations of 2010 may be performed as described with reference to Figures 9 to 16The SPI manager described here is executed.

[0230] At 2015, the base station may transmit an indication of the scheduling plan to the scheduling node by the first CU, wherein the first CU identifies the indication of the scheduling plan. The operation of 2015 may be performed according to the method described herein. In some examples, various aspects of the operation of 2015 may be performed as described with reference to Figures 9 to 16 The SPI manager described here is executed.

[0231] Fig.21 2100 for supporting SPI according to aspects of the present disclosure. The operations of the method 2100 may be implemented by the base station 105 or its components as described herein. For example, the operations of the method 2100 may be implemented by the base station 105 or its components as described herein. Figures 9 to 16 In some examples, the base station may execute an instruction set to control the functional elements of the base station to perform the functions described below. Additionally or alternatively, the base station may use dedicated hardware to perform various aspects of the functions described below.

[0232] At 2105, the base station may receive a measurement report from a UE, the measurement report including a measured value of at least one beam of a cell measured by the UE. The operations of 2105 may be performed according to the methods described herein. In some examples, aspects of the operations of 2105 may be performed as described with reference to Figures 9 to 16 The measurement report manager described herein is used to perform the above operations.

[0233] At 2110, the base station may identify an indication of a scheduling plan for the scheduling node, the indication of the scheduling plan specifying a scheduling state mode within a time period, the indication of the scheduling plan being based on the measurement report and to be used by the scheduling node to schedule communication resources for the UE. The operations of 2110 may be performed according to the methods described herein. In some examples, aspects of the operations of 2110 may be performed as described with reference to Figures 9 to 16 The SPI manager described here is executed.

[0234] At 2115, the base station may receive an indication of a tentative scheduling plan from the scheduling node. The operations of 2115 may be performed according to the methods described herein. In some examples, aspects of the operations of 2115 may be performed as described with reference to Figures 9 to 16 The experimental SPI manager described is implemented.

[0235] At 2120, the base station may determine an updated scheduling plan for the scheduling node based on the received indication of the tentative scheduling plan and the received measurement report, wherein the updated scheduling plan is a scheduling plan for the scheduling node. The operations of 2120 may be performed according to the methods described herein. In some examples, aspects of the operations of 2120 may be performed as described with reference to Figures 9 to 16 The SPI update manager described above is used to perform the

[0236] At 2125, the base station may transmit an indication of the scheduling plan to the scheduling node by the first CU, wherein the first CU identifies the indication of the scheduling plan. The operation of 2125 may be performed according to the methods described herein. In some examples, various aspects of the operation of 2125 may be performed as described with reference to Figures 9 to 16 The SPI manager described here is executed.

[0237] Fig. 22 2200 according to various aspects of the present disclosure. The operations of the method 2200 may be implemented by the base station 105 or its components as described herein. For example, the operations of the method 2200 may be implemented by the base station 105 or its components as described herein. Figures 9 to 16 In some examples, the base station may execute an instruction set to control the functional elements of the base station to perform the functions described below. Additionally or alternatively, the base station may use dedicated hardware to perform various aspects of the functions described below.

[0238] At 2205, the base station may receive a measurement report from a UE, the measurement report including a measured value of at least one beam of a cell measured by the UE. The operations of 2205 may be performed according to the methods described herein. In some examples, aspects of the operations of 2205 may be performed as described with reference to Figures 9 to 16 The measurement report manager described herein is used to perform the above operations.

[0239] At 2210, the base station may identify an indication of a scheduling plan for the scheduling node, the indication of the scheduling plan specifying a scheduling state mode within a time period, the indication of the scheduling plan being based on the measurement report and to be used by the scheduling node to schedule communication resources for the UE. The operations of 2210 may be performed according to the methods described herein. In some examples, aspects of the operations of 2210 may be performed as described with reference to Figures 9 to 16 The SPI manager described here is executed.

[0240] At 2215, the base station may receive an indication of one or more tentative scheduling plans at the CU, each of the one or more tentative scheduling plans for an additional scheduling node. The operations of 2215 may be performed according to the methods described herein. In some examples, aspects of the operations of 2215 may be performed as described with reference to Figures 9 to 16 The experimental SPI manager described is implemented.

[0241] At 2220, the base station may forward an indication of the one or more tentative scheduling plans to the scheduling node. The operations of 2220 may be performed according to the methods described herein. In some examples, aspects of the operations of 2220 may be performed as described with reference to Figures 9 to 16 The experimental SPI manager described is implemented.

[0242] Fig.23 2300 for supporting SPI according to aspects of the present disclosure. The operations of the method 2300 may be implemented by the base station 105 or its components as described herein. For example, the operations of the method 2300 may be implemented by the base station 105 or its components as described herein. Figures 9 to 16 In some examples, the base station may execute an instruction set to control the functional elements of the base station to perform the functions described below. Additionally or alternatively, the base station may use dedicated hardware to perform various aspects of the functions described below.

[0243] At 2305, the base station may receive a measurement report from a UE, the measurement report including a measured value of at least one beam of a cell measured by the UE. The operations of 2305 may be performed according to the methods described herein. In some examples, aspects of the operations of 2305 may be performed as described with reference to Figures 9 to 16 The measurement report manager described herein is used to perform the above operations.

[0244] At 2310, the base station may receive at least one additional measurement report of at least one additional UE from the scheduling node or at least one second scheduling node at the CU. The operations of 2310 may be performed according to the methods described herein. In some examples, aspects of the operations of 2310 may be performed as described with reference to Figures 9 to 16 The measurement report manager described herein is used to perform the above operations.

[0245] At 2315, the base station may determine, by the CU, an interference profile based on the received measurement report and the at least one additional measurement report, wherein the indication of the scheduling plan is identified based on the determined interference profile. The operations of 2315 may be performed according to the methods described herein. In some examples, aspects of the operations of 2315 may be performed as described with reference to Figures 9 to 16 The interference profile manager described is executed.

[0246] At 2320, the base station may identify an indication of a scheduling plan for the scheduling node, the indication of the scheduling plan specifying a scheduling state mode within a time period, the indication of the scheduling plan being based on the measurement report and to be used by the scheduling node to schedule communication resources for the UE. The operations of 2320 may be performed according to the methods described herein. In some examples, aspects of the operations of 2320 may be performed as described with reference to Figures 9 to 16 The SPI manager described here is executed.

[0247] It should be noted that the above methods describe possible implementations, and that the operations and steps may be rearranged or otherwise modified and other implementations are possible. Furthermore, aspects from two or more methods may be combined.

[0248] The technology described herein can be used in various wireless communication systems, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA) and other systems. CDMA systems can implement radio technologies such as CDMA2000, Universal Terrestrial Radio Access (UTRA). CDMA2000 covers IS-2000, IS-95 and IS-856 standards. IS-2000 versions are generally referred to as CDMA2000 1X, 1X, etc. IS-856 (TIA-856) is generally referred to as CDMA2000 1xEV-DO, High Rate Packet Data (HRPD), etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. TDMA systems can implement radio technologies such as Global System for Mobile Communications (GSM).

[0249] OFDMA systems can implement radio technologies such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE802.20, Flash-OFDM, etc. UTRA and E-UTRA are part of Universal Mobile Telecommunications System (UMTS). LTE, LTE-A, and LTE-A Pro are versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, LTE-A Pro, NR, and GSM are described in documents from an organization called the "3rd Generation Partnership Project" (3GPP). CDMA2000 and UMB are described in documents from an organization called the "3rd Generation Partnership Project 2" (3GPP2). The technology described herein can be used for the systems and radio technologies mentioned above as well as for other systems and radio technologies. Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to applications other than LTE, LTE-A, LTE-A Pro, or NR applications.

[0250] A macro cell generally covers a relatively large geographic area (e.g., an area of ​​several kilometers in radius) and may allow unrestricted access by UEs 115 that have service subscriptions with a network provider. A small cell may be associated with a lower power base station 105 (compared to a macro cell), and the small cell may operate in the same or different (e.g., licensed, unlicensed, etc.) frequency band as the macro cell. According to various examples, a small cell may include a pico cell, a femto cell, and a micro cell. A pico cell, for example, may cover a smaller geographic area and may allow unrestricted access by UEs 115 that have service subscriptions with a network provider. A femto cell may also cover a smaller geographic area (e.g., a residence) and may provide restricted access by UEs 115 associated with the femto cell (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 of users in a residence, etc.). An eNB for a macro cell may be referred to as a macro eNB. An eNB for a small cell may be referred to as a small cell eNB, a pico eNB, a femto eNB, or a home eNB. An eNB may support one or more (eg, two, three, four, etc.) cells and may also support communication using one or more component carriers.

[0251] One or more wireless communication systems 100 described herein may support synchronous or asynchronous operation. For synchronous operation, the base stations 105 may have similar frame timing, and transmissions from different base stations 105 may be approximately aligned in time. For asynchronous operation, the base stations 105 may have different frame timing, and transmissions from different base stations 105 may not be aligned in time. The techniques described herein may be used for synchronous or asynchronous operation.

[0252] The information and signals described herein may be represented using any of a variety of different techniques and technologies. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0253] The various illustrative blocks and modules described in conjunction with the disclosure herein may be implemented or executed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0254] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted by a computer-readable medium as one or more instructions or codes. Other examples and implementations fall within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described above may be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. Features that implement the functions may also be physically located in various locations, including being distributed so that parts of the functions are implemented at different physical locations.

[0255] Computer readable medium includes both non-transient computer storage medium and communication medium, and it includes any medium that facilitates computer program to transfer from one place to another place.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.As an example and not limitation, non-transient computer readable medium can include random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, disk storage or other magnetic storage device, or can be used to carry or store instruction or data structure form of desired program code means and can be accessed by general or special-purpose computer or general or special-purpose processor any other non-transient medium.Any connection is also properly referred to as computer readable medium.For example, if software is transmitted from website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are just included in the definition of medium. Disk and disc as used herein include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0256] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items with a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Similarly, as used herein, the phrase "based on" should not be interpreted as referring to a closed set of conditions. For example, an exemplary step described as "based on condition A" may be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."

[0257] In the accompanying drawings, similar components or features may have the same reference number. In addition, various components of the same type may be distinguished by following the reference number with a dash and a second reference number that distinguishes between similar components. If only the first reference number is used in the specification, the description may apply to any of the similar components having the same first reference number regardless of the second reference number, or other subsequent reference numbers.

[0258] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or that fall within the scope of the claims. The term "exemplary" as used herein means "used as an example, instance, or illustration" and does not mean "better than" or "better than other examples." This detailed description includes specific details to provide an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0259] The description herein is provided to enable those skilled in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to those skilled in the art, and the universal principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication, comprising: receiving a measurement report of a user equipment UE, the measurement report comprising a measured value of at least one beam of a cell measured by the UE; as well as identifying, for a scheduling node, an indication of a scheduling plan, the indication of the scheduling plan specifying a scheduling state pattern within a time period, the indication of the scheduling plan being based at least in part on the measurement report and being used by the scheduling node to schedule communication resources for the UE, The scheduling state mode includes a scheduling information state, a flexible state, an invalid state, or a combination thereof. For the flexible state, the scheduling node is allowed to schedule any UE, or any beam direction, or a combination thereof; as well as For the inactive state, the scheduling node is blocked from scheduling all UEs, or all beam directions, or a combination thereof.

2. The method of claim 1, wherein the time period comprises one or more time slots or mini-time slots.

3. The method as claimed in claim 1, wherein the indication of the scheduling plan identifies a value used for scheduling for a scheduling state, and the value used for scheduling includes a set of UE indexes, or a set of beam indexes, or a set of angle values, or a set of position values, or a combination thereof.

4. The method of claim 1, wherein the indication of the scheduling plan is for a scheduling state, scheduling data transmission for different UEs, or different beam modes, or a combination thereof.

5. The method of claim 1, wherein the indication of the scheduling plan identifies, for a scheduling state, an allocated resource block, or a buffer status, or a priority, or a communication type, or a modulation and coding scheme MCS, or a target signal-to-interference-and-noise ratio SINR, or a target transmit power, or a target receive power, or a combination thereof.

6. The method of claim 1, further comprising: The scheduling node transmits the measurement report to a central unit CU; as well as Based at least in part on transmitting the measurement report, an indication of the scheduling plan is received from the CU.

7. The method of claim 1, further comprising: The scheduling node determines a trial scheduling plan; transmitting an indication of the tentative scheduling plan to the CU; as well as An indication of an updated scheduling plan based at least in part on the tentative scheduling plan is received from the CU, wherein the updated scheduling plan is a scheduling plan for the scheduling node.

8. The method of claim 1, further comprising: The indication of the scheduling plan is transmitted to the scheduling node by a first central unit CU, wherein the indication of the scheduling plan is identified by the first CU.

9. The method of claim 8, wherein the indication identifying the scheduling plan comprises: An indication of the scheduling plan is determined by the first CU based at least in part on the received measurement report, the measurement report received from the scheduling node.

10. The method of claim 8, wherein the indication identifying the scheduling plan comprises: receiving an indication of a tentative scheduling plan from the scheduling node; as well as An updated scheduling plan for the scheduling node is determined based at least in part on the received indication of the tentative scheduling plan and the received measurement report, wherein the updated scheduling plan is a scheduling plan for the scheduling node.

11. The method of claim 10, wherein the updated scheduling plan for the scheduling node is further based at least in part on at least one additional tentative scheduling plan received from at least one additional scheduling node, and further based at least in part on at least one additional measurement report from at least one additional UE.

12. The method of claim 8, further comprising: An indication of the scheduling plan is received from a second CU, the received indication being transmitted by the CU to the scheduling node.

13. The method of claim 8, further comprising: Transmitting the measurement report to a core network node; as well as An indication of the scheduling plan is received from the core network node.

14. The method of claim 1, further comprising: The indication of the scheduling plan is transmitted by the first CU to the second CU, or a core network node, or a combination thereof, wherein the first CU identifies the indication of the scheduling plan based at least in part on the received measurement report.

15. The method of claim 1, further comprising: receiving, at the scheduling node, an indication of a tentative scheduling plan from a second scheduling node via the CU; as well as An updated scheduling plan for the scheduling node is determined, by the scheduling node, based at least in part on the received indication of the tentative scheduling plan.

16. The method of claim 15, further comprising: At least one priority rule applicable to a scheduling plan of the scheduling node is identified by the scheduling node, wherein the updated scheduling plan for the scheduling node is determined based at least in part on the received indication of the tentative scheduling plan and the at least one priority rule.

17. The method of claim 1, further comprising: receiving, at a central unit CU, an indication of one or more tentative scheduling plans, each of the one or more tentative scheduling plans being for an additional scheduling node; as well as An indication of the one or more tentative scheduling plans is forwarded to the scheduling node.

18. The method of claim 1, wherein: Identifying the indication of the scheduling plan comprises determining, by a core network node, the indication of the scheduling plan based at least in part on the received measurement report; and The method further comprises transmitting an indication of the scheduling plan determined by the core network node to a central unit CU.

19. The method of claim 1, further comprising: receiving, at a central unit CU, at least one additional measurement report of at least one additional UE from the scheduling node or at least one second scheduling node; as well as An interference profile is determined by the CU based at least in part on the received measurement report and the at least one additional measurement report, wherein the indication of the scheduling plan is identified based at least in part on the determined interference profile.

20. The method of claim 19, wherein the interference profile comprises a profile of an interfering UE, or an interfering beam, or a combination thereof.

21. The method of claim 1, further comprising: receiving, at the scheduling node, an interference profile from a central unit; identifying at least one UE, or at least one beam direction, or a combination thereof as interfering based at least in part on the received interference profile; as well as The at least one UE, or the at least one beam direction, or a combination thereof is assigned by the scheduling node to different time units, or different non-overlapping resource block allocations, or a combination thereof.

22. The method of claim 1, further comprising: Configuration information is transmitted for use by the UE to perform measurements on the cell, or at least one additional cell, or a combination thereof.

23. The method of claim 22, further comprising: At least one additional measurement report is received from the UE based at least in part on the transmitted configuration information.

24. The method of claim 1, further comprising: The indication of the scheduling plan is transmitted by a parent node of an integrated access and backhaul network IAB to a child node of the IAB.

25. The method of claim 1, further comprising: The indication of the scheduling plan is transmitted on a group common physical downlink control channel GC-PDCCH, or a radio resource control RRC message, or a combination thereof.

26. The method of claim 1, wherein the indication identifying the scheduling plan comprises: identifying a conflict between a first indication of a first scheduling plan for the scheduling node and a second indication of a second scheduling plan for the scheduling node; as well as The first schedule or the second schedule is selected to be the schedule based at least in part on a rule for schedule selection.

27. The method of claim 26, further comprising: A first duration of time associated with the first schedule and a second duration of time associated with the second schedule are identified, wherein the rule indicates that the first schedule is selected based at least in part on the second duration of time being longer than the first duration of time.

28. The method of claim 26, further comprising: receiving, via an interface of a first type, a first indication of a first scheduling plan; receiving, via an interface of a second type, a second indication of a second scheduling plan; as well as The first schedule is selected to become the schedule based at least in part on the rule indicating that interfaces of the first type override interfaces of the second type.

29. The method of claim 1, wherein the scheduling node comprises a distributed unit DU of an integrated access and backhaul IAB network.

30. The method of claim 29, wherein the IAB network includes a central unit (CU) controlling a plurality of DUs including the DU.

31. The method of claim 29, wherein the indication of the scheduling plan is used for inter-DU coordination via a central unit CU of the IAB network.

32. The method of claim 29, wherein the indication of the scheduling plan is used for inter-CU coordination via one or more Xn_C interfaces, or via a core network, or a combination thereof.

33. An apparatus for wireless communication, comprising: processor, a memory coupled to the processor; as well as instructions stored in the memory, the instructions being executable by the processor to cause the apparatus to: receiving a measurement report of a user equipment UE, the measurement report comprising a measured value of at least one beam of a cell measured by the UE; as well as identifying, for a scheduling node, an indication of a scheduling plan, the indication of the scheduling plan specifying a scheduling state pattern within a time period, the indication of the scheduling plan being based at least in part on the measurement report and being used by the scheduling node to schedule communication resources for the UE, The scheduling state mode includes a scheduling information state, a flexible state, an invalid state, or a combination thereof. For the flexible state, the scheduling node is allowed to schedule any UE, or any beam direction, or a combination thereof; as well as For the inactive state, the scheduling node is blocked from scheduling all UEs, or all beam directions, or a combination thereof.

34. The apparatus of claim 33, wherein the instructions are further executable by the processor to cause the apparatus to: The scheduling node transmits the measurement report to a central unit CU; and Based at least in part on transmitting the measurement report, an indication of the scheduling plan is received from the CU.

35. The apparatus of claim 33, wherein the instructions are further executable by the processor to cause the apparatus to: The scheduling node determines a trial scheduling plan; transmitting an indication of the tentative scheduling plan to the CU; and An indication of an updated scheduling plan based at least in part on the tentative scheduling plan is received from the CU, wherein the updated scheduling plan is a scheduling plan for the scheduling node.

36. The apparatus of claim 33, wherein the instructions are further executable by the processor to cause the apparatus to: The indication of the scheduling plan is transmitted to the scheduling node by a first central unit CU, wherein the indication of the scheduling plan is identified by the first CU.

37. The apparatus of claim 33, wherein the instructions are further executable by the processor to cause the apparatus to: The indication of the scheduling plan is transmitted by the first CU to the second CU, or a core network node, or a combination thereof, wherein the first CU identifies the indication of the scheduling plan based at least in part on the received measurement report.

38. The apparatus of claim 33, wherein the instructions are further executable by the processor to cause the apparatus to: receiving, at the scheduling node, an indication of a tentative scheduling plan from a second scheduling node via the CU; and An updated scheduling plan for the scheduling node is determined, by the scheduling node, based at least in part on the received indication of the tentative scheduling plan.

39. The apparatus of claim 33, wherein the instructions are further executable by the processor to cause the apparatus to: receiving at a central unit CU an indication of one or more tentative scheduling plans, each of the one or more tentative scheduling plans being for an additional scheduling node; and An indication of the one or more tentative scheduling plans is forwarded to the scheduling node.

40. The apparatus of claim 33, wherein: Identifying the indication of the scheduling plan comprises determining, by a core network node, the indication of the scheduling plan based at least in part on the received measurement report; and The instructions are further executable by the processor to cause the apparatus to: transmit an indication of the scheduling plan determined by the core network node to a central unit CU.

41. The apparatus of claim 33, wherein the instructions are further executable by the processor to cause the apparatus to: receiving at a central unit CU at least one additional measurement report of at least one additional UE from the scheduling node or at least one second scheduling node; and An interference profile is determined by the CU based at least in part on the received measurement report and the at least one additional measurement report, wherein the indication of the scheduling plan is identified based at least in part on the determined interference profile.

42. The apparatus of claim 33, wherein the instructions are further executable by the processor to cause the apparatus to: receiving, at the scheduling node, an interference profile from a central unit; identifying at least one UE, or at least one beam direction, or a combination thereof as interfering based at least in part on the received interference profile; as well as The at least one UE, or the at least one beam direction, or a combination thereof is assigned by the scheduling node to different time units, or different non-overlapping resource block allocations, or a combination thereof.

43. The apparatus of claim 33, wherein the instructions are further executable by the processor to cause the apparatus to: Configuration information is transmitted for use by the UE to perform measurements on the cell, or at least one additional cell, or a combination thereof.

44. The apparatus of claim 33, wherein the instructions are further executable by the processor to cause the apparatus to: The indication of the scheduling plan is transmitted by a parent node of an integrated access and backhaul network IAB to a child node of the IAB.

45. The apparatus of claim 33, wherein the instructions are further executable by the processor to cause the apparatus to: The indication of the scheduling plan is transmitted on a group common physical downlink control channel GC-PDCCH, or a radio resource control RRC message, or a combination thereof.

46. ​​The apparatus of claim 33, wherein instructions for identifying an indication of the schedule are executable by the processor to cause the apparatus to: identifying a conflict between a first indication of a first scheduling plan for the scheduling node and a second indication of a second scheduling plan for the scheduling node; and The first schedule or the second schedule is selected to be the schedule based at least in part on a rule for schedule selection.

47. An apparatus for wireless communication, comprising: means for receiving a measurement report of a user equipment UE, the measurement report comprising a measured value of at least one beam of a cell measured by the UE; as well as means for identifying, for a scheduling node, an indication of a scheduling plan, the indication of the scheduling plan specifying a scheduling state pattern over a time period, the indication of the scheduling plan being based at least in part on the measurement report and to be used by the scheduling node to schedule communication resources for the UE, The scheduling state mode includes a scheduling information state, a flexible state, an invalid state, or a combination thereof. For the flexible state, the scheduling node is allowed to schedule any UE, or any beam direction, or a combination thereof; as well as For the inactive state, the scheduling node is blocked from scheduling all UEs, or all beam directions, or a combination thereof.

48. The apparatus of claim 47, wherein the time period comprises one or more time slots or mini-slots.

49. An apparatus as described in claim 47, wherein the indication of the scheduling plan identifies, for a scheduling state, a value used for scheduling, and the value used for scheduling includes a set of UE indices, or a set of beam indices, or a set of angle values, or a set of position values, or a combination thereof.

50. The apparatus of claim 47, wherein the indication of the scheduling plan is for a scheduling state, scheduling data transmission for different UEs, or different beam modes, or a combination thereof.

51. An apparatus as described in claim 47, wherein the indication of the scheduling plan identifies, for a scheduling state, an allocated resource block, or a buffer status, or a priority, or a communication type, or a modulation and coding scheme MCS, or a target signal-to-interference and noise ratio SINR, or a target transmit power, or a target receive power, or a combination thereof.

52. The apparatus of claim 47, further comprising: means for transmitting, by the scheduling node, the measurement report to a central unit CU; as well as Means for receiving an indication of the scheduling plan from the CU based at least in part on transmitting the measurement report.

53. The apparatus of claim 47, further comprising: means for determining, by the scheduling node, a tentative scheduling plan; means for transmitting an indication of said tentative scheduling plan to the CU; as well as Means for receiving, from the CU, an indication of an updated scheduling plan based at least in part on the tentative scheduling plan, wherein the updated scheduling plan is a scheduling plan for the scheduling node.

54. The apparatus of claim 47, further comprising: Means for transmitting, by a first central unit CU, an indication of the scheduling plan to the scheduling node, wherein the indication of the scheduling plan is identified by the first CU.

55. The apparatus of claim 47, further comprising: Means for transmitting, by the first CU, an indication of the scheduling plan to a second CU, or a core network node, or a combination thereof, wherein the first CU identifies the indication of the scheduling plan based at least in part on the received measurement report.

56. The apparatus of claim 47, further comprising: means for receiving, at the scheduling node, via the CU from a second scheduling node, an indication of a tentative scheduling plan; as well as Means for determining, by the scheduling node, an updated scheduling plan for the scheduling node based at least in part on the received indication of the tentative scheduling plan.

57. The apparatus of claim 47, further comprising: means for receiving, at a central unit CU, an indication of one or more tentative scheduling plans, each of the one or more tentative scheduling plans being for an additional scheduling node; as well as Means for forwarding an indication of the one or more tentative scheduling plans to the scheduling node.

58. The apparatus of claim 47, wherein: The means for identifying the indication of the scheduling plan comprises determining, by a core network node, the indication of the scheduling plan based at least in part on the received measurement report; and The apparatus further comprises means for transmitting an indication of the scheduling plan determined by the core network node to a central unit CU.

59. The apparatus of claim 47, further comprising: means for receiving, at a central unit CU, at least one additional measurement report of at least one additional UE from said scheduling node or at least one second scheduling node; as well as Means for determining, by the CU, an interference profile based at least in part on the received measurement report and the at least one additional measurement report, wherein the indication of the scheduling plan is identified based at least in part on the determined interference profile.

60. The apparatus of claim 47, further comprising: means for receiving, at said scheduling node, an interference profile from a central unit; means for identifying at least one UE, or at least one beam direction, or a combination thereof as interfering based at least in part on the received interference profile; as well as Means for assigning, by the scheduling node, the at least one UE, or the at least one beam direction, or a combination thereof, to different time units, or different non-overlapping resource block allocations, or a combination thereof.

61. The apparatus of claim 47, further comprising: Means for transmitting configuration information for use by the UE to perform measurements on the cell, or at least one additional cell, or a combination thereof.

62. The apparatus of claim 47, further comprising: Means for transmitting, by a parent node of an integrated access and backhaul network, IAB, an indication of said scheduling plan to a child node of said IAB.

63. The apparatus of claim 47, further comprising: Means for transmitting an indication of the scheduling plan on a group common physical downlink control channel GC-PDCCH, or a radio resource control RRC message, or a combination thereof.

64. The apparatus of claim 47, wherein the means for identifying an indication of the schedule comprises: means for identifying a conflict between a first indication of a first scheduling plan for the scheduling node and a second indication of a second scheduling plan for the scheduling node; as well as Means for selecting the first schedule or the second schedule to be the schedule based at least in part on rules for schedule selection.

65. A non-transitory computer readable medium storing code for wireless communication, the code comprising instructions executable by a processor to: receiving a measurement report of a user equipment UE, the measurement report comprising a measured value of at least one beam of a cell measured by the UE; and identifying, for a scheduling node, an indication of a scheduling plan, the indication of the scheduling plan specifying a scheduling state pattern within a time period, the indication of the scheduling plan being based at least in part on the measurement report and being used by the scheduling node to schedule communication resources for the UE, The scheduling state mode includes a scheduling information state, a flexible state, an invalid state, or a combination thereof. For the flexible state, the scheduling node is allowed to schedule any UE, or any beam direction, or a combination thereof; and For the inactive state, the scheduling node is blocked from scheduling all UEs, or all beam directions, or a combination thereof.

Images