Beam reporting enhancements for simultaneous IAB reception

Abstract

According to example aspects of the present disclosure, a method is provided that includes performing, with a first node, beam measurements on downlink beams received by the first node from at least one second node, scheduling, with the first node, at least one third node for uplink transmissions to the first node, determining, with the first node, one or more of the downlink beams that are capable of being simultaneously received with beams of the at least one third node based at least in part on the scheduling of the at least one third node and the performing of the beam measurements, and transmitting, with the first node, results of the performed beam measurements, wherein the results include an indication of the one or more determined downlink beams that are capable of being simultaneously received with beams of the at least one third node.

Description

Technical Field

[0001] The exemplary and non-limiting embodiments generally relate to communications, and more specifically to facilitating the use of backhaul links in NR / 5G networks. Background Technology

[0002] For gNBs in NR / 5G that include centralized and distributed units, it is known to use backhaul between gNB / gNB portions to relay information between user equipment and the network. Attached Figure Description

[0003] The foregoing aspects and other features are explained in the following description in conjunction with the accompanying drawings, in which:

[0004] Figure 1 This is a block diagram of a possible, non-limiting, exemplary system in which exemplary embodiments can be practiced;

[0005] Figure 2 This is a schematic diagram illustrating examples of various devices in a network;

[0006] Figure 3 This is a diagram illustrating the features described in this article;

[0007] Figure 4 This is a diagram illustrating the features described in this article;

[0008] Figure 5 This is a diagram illustrating the features described in this article;

[0009] Figure 6 This is a diagram illustrating the features described in this article;

[0010] Figure 7 This is a diagram illustrating the features described in this article;

[0011] Figure 8 This is a flowchart illustrating the steps described herein; and

[0012] Figure 9 This is a flowchart illustrating the steps described in this document. Detailed Implementation

[0013] The following abbreviations may appear in the instruction manual and / or drawings and are defined as follows:

[0014] 3GPP: Third Generation Partnership Project

[0015] 5G: Fifth Generation

[0016] 5GC: 5G Core Network

[0017] AMF: Access and Mobility Management Functions

[0018] BH: Return Trip

[0019] CLI: Cross-link interference

[0020] CRI: CSI-RS (Channel State Information Reference Signal) Resource Indicator

[0021] CSI: Channel State Information

[0022] CSI-RS: Channel State Information Reference Signal

[0023] CU: Centralized Unit

[0024] DC: Dual Connection

[0025] DU: Distributed Unit

[0026] eNB (or eNodeB): Evolved Node B (e.g., LTE base station) EN-DC: E-UTRA-NR Dual Connectivity

[0027] en-gNB or En-gNB: A node that provides NR user plane and control plane protocol termination to the UE and acts as a secondary node in the EN-DC.

[0028] E-UTRA: Evolved Universal Terrestrial Radio Access, i.e., LTE radio access technology.

[0029] FDM: Frequency Division Multiplexing

[0030] feMIMO: Further Enhanced Multiple-Input Multiple-Output

[0031] FFS: For Future Research

[0032] gNB (or gNodeB): A base station used for 5G / NR, i.e., a node that provides NR user plane and control plane protocol termination to the UE and connects to the 5GC via the NG interface.

[0033] I / F: Interface

[0034] IAB: Integrated Access and Backhaul, or Integrated Access and Backhaul

[0035] L1: Level 1

[0036] LTE: Long Term Evolution

[0037] MAC: Media Access Control

[0038] MIMO: Multiple Input Multiple Output

[0039] MME: Mobility Management Entity

[0040] MT: Mobile terminal

[0041] multi-TRP: Multiple transmit and receive points

[0042] ng or NG: the new generation

[0043] ng-eNB or NG-eNB: Next-generation eNB

[0044] NR: New Radio

[0045] N / W or NW: Network

[0046] NZP: Non-zero power

[0047] PBCH: Physical Broadcast Channel

[0048] PDCP: Packet Data Convergence Protocol

[0049] PHY: Physical Layer

[0050] RAN: Radio Access Network

[0051] RF: Radio Frequency

[0052] RLC: Radio Link Control

[0053] RS: Reference signal

[0054] RSRP: Reference Signal Received Power

[0055] RRH: Remote Radio Header Terminal

[0056] RRC: Radio Resource Control

[0057] RU: Radio Unit

[0058] Rx: Receiver

[0059] SDAP: Service Data Adaptation Protocol

[0060] SDM: Space Division Multiplexing

[0061] SGW: Service Gateway

[0062] SMF: Session Management Function

[0063] SS: Auxiliary Synchronization Signal

[0064] SSBRI: SS / PBCH (Secondary Synchronization Signal / Physical Broadcast Channel) Resource Block Indicator

[0065] TCI: Transport Configuration Indicator

[0066] TDM: Time Division Multiplexing

[0067] TRP: Transmit and receive point, such as a relay node.

[0068] Tx: Transmitter

[0069] UE: User Equipment (e.g., wireless, typically mobile device)

[0070] UPF: User Plane Functionality

[0071] WI: Work Item

[0072] Turn Figure 1 The figure illustrates a block diagram of one possible, non-limiting example in which examples can be practiced. It shows a user equipment (UE) 110, a radio access network (RAN) node 170, and (multiple) network elements 190. Figure 1 In the example, User Equipment (UE) 110 wirelessly communicates with Wireless Network 100. The UE is a wireless device that can access Wireless Network 100. UE 110 includes one or more processors 120, one or more memories 125, and one or more transceivers 130 interconnected via one or more buses 127. Each of the one or more transceivers 130 includes a receiver Rx 132 and a transmitter Tx 133. The one or more buses 127 may be address, data, or control buses and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, fiber optic cable, or other optical communication device. The one or more transceivers 130 are connected to one or more antennas 128. The one or more memories 125 include computer program code 123. UE 110 includes a module 140, which includes one or both of portions 140-1 and / or 140-2, and module 140 may be implemented in various ways. Module 140 may be implemented in hardware as module 140-1, such as as part of one or more processors 120. Module 140-1 can also be implemented as an integrated circuit or via other hardware such as a programmable gate array. In another example, module 140 can be implemented as module 140-2, which is implemented as computer program code 123 and executed by one or more processors 120. For example, one or more memories 125 and computer program code 123 can be configured, together with one or more processors 120, to cause user equipment 110 to perform one or more of the operations described herein. UE 110 communicates with RAN node 170 via radio link 111.

[0073] In this example, RAN node 170 is a base station that provides access to wireless network 100 for wireless devices (such as UE 110). RAN node 170 can be, for example, a base station for 5G, also known as New Radio (NR). In 5G, RAN node 170 can be an NG-RAN node, which is defined as a gNB or ng-eNB. A gNB is a node that provides NR user plane and control plane protocol termination to the UE and is connected to the 5GC (e.g., multiple network elements 190) via an NG interface. An ng-eNB is a node that provides E-UTRA user plane and control plane protocol termination to the UE and is connected to the 5GC via an NG interface. An NG-RAN node can include multiple gNBs, which can also include centralized unit (CU) (gNB-CU) 196 and multiple distributed unit (DU) (gNB-DU), where DU 195 is shown. Note that a DU can include or be coupled to and control a radio unit (RU). A gNB-CU is a logical node that hosts the RRC, SDAP, and PDCP protocols of a gNB, or controls the RRC and PDCP protocols of an en-gNB that controls the operation of one or more gNB-DUs. The gNB-CU terminates the F1 interface connected to the gNB-DU. The F1 interface is shown as reference numeral 198, although reference numeral 198 also shows links between remote elements of RAN node 170 and centralized elements of RAN node 170, such as the link between gNB-CU 196 and gNB-DU 195. A gNB-DU is a logical node that hosts the RLC, MAC, and PHY layers of a gNB or en-gNB, and its operation is partially controlled by the gNB-CU. A gNB-CU supports one or more cells. A cell is supported by only one gNB-DU. The gNB-DU terminates the F1 interface 198 connected to the gNB-CU. Note that DU195 is considered to include transceiver 160, for example, as part of an RU; however, some examples in this regard could allow transceiver 160 to be part of a separate RU, for example, under the control of and connected to DU 195. RAN node 170 could also be an eNB (evolved NodeB) base station for LTE (Long Term Evolution), or any other suitable base station or node.

[0074] RAN node 170 includes one or more processors 152, one or more memories 155, one or more network interfaces (N / WI / F) 161 interconnected via one or more buses 157, and one or more transceivers 160. Each of the one or more transceivers 160 includes a receiver Rx 162 and a transmitter Tx 163. The one or more transceivers 160 are connected to one or more antennas 158. The one or more memories 155 include computer program code 153. CU 196 may include one or more processors 152, memories 155, and network interfaces 161. Note that DU 195 may also include its own memory / multiple memories and processors, and / or other hardware, but these are not shown.

[0075] RAN node 170 includes module 150, which includes one or both of portions 150-1 and / or 150-2. Module 150 can be implemented in various ways. Module 150 can be implemented in hardware as module 150-1, such as as part of one or more processors 152. Module 150-1 can also be implemented as an integrated circuit or via other hardware such as a programmable gate array. In another example, module 150 can be implemented as module 150-2, which is implemented as computer program code 153 and executed by one or more processors 152. For example, one or more memories 155 and computer program code 153 are configured, together with one or more processors 152, to cause RAN node 170 to perform one or more of the operations described herein. Note that the functionality of module 150 can be distributed, such as distributed between DU 195 and CU 196, or implemented solely in DU 195.

[0076] One or more network interfaces 161 communicate over a network, such as via links 176 and 131. Two or more gNBs 170 may communicate using, for example, link 176. Link 176 may be wired, wireless, or both, and may implement, for example, an Xn interface for 5G, an X2 interface for LTE, or other suitable interfaces for other standards.

[0077] One or more buses 157 may be address, data, or control buses and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, optical fiber or other optical communication equipment, wireless channels, etc. For example, one or more transceivers 160 may be implemented as a Remote Radio Header (RRH) 195 for LTE or a Distributed Unit (DU) 195 for a gNB implementation of 5G, wherein other elements of the RAN node 170 may be physically located in a different location from the RRH / DU, and one or more buses 157 may be partially implemented as, for example, fiber optic cables or other suitable network connections for connecting other elements of the RAN node 170 (e.g., Centralized Unit (CU), gNB-CU) to the RRH / DU 195. Reference numeral 198 also indicates these suitable network links(s).

[0078] Note that the description in this document indicates that a "cell" performs a function; however, it should be clear that the equipment forming the cell can perform this function. A cell constitutes part of a base station. That is, each base station can have multiple cells. For example, there can be three cells for a single carrier frequency and associated bandwidth, each cell covering one-third of a 360-degree area, thus the coverage area of ​​a single base station is approximately elliptical or circular. Furthermore, each cell can correspond to a single carrier, and a base station can use multiple carriers. So if there are three 120-degree cells per carrier and two carriers, the base station has a total of six cells.

[0079] Wireless network 100 may include one or more network elements 190, which may include core network functions and provide connectivity to other networks (e.g., the Internet) such as telephone networks and / or data communication networks via one or more links 181. Such core network functions for 5G may include access and mobility management functions (AMFs) and / or user plane functions (UPFs) and / or session management functions (SMFs). Such core network functions for LTE may include MME (Mobility Management Entity) / SGW (Serving Gateway) functions. These are merely exemplary functions that may be supported by the network elements 190, and it should be noted that both 5G and LTE functions may be supported. RAN node 170 is coupled to network element 190 via link 131. Link 131 may be implemented as, for example, an NG interface for 5G, or an S1 interface for LTE, or other suitable interfaces for other standards. Network element 190 includes one or more processors 175, one or more memories 171, and one or more network interfaces (N / WI / F) 180 interconnected via one or more buses 185. The one or more memories 171 include computer program code 173. The one or more memories 171 and the computer program code 173 are configured, together with the one or more processors 175, to cause network element 190 to perform one or more operations.

[0080] Wireless network 100 can implement network virtualization, a process that combines hardware and software network resources and functions into a single software-based managed entity (virtual network). Network virtualization involves platform virtualization, which is often used in conjunction with resource virtualization. Network virtualization is divided into external network virtualization and internal network virtualization. External network virtualization combines many networks or network components into virtual units, while internal network virtualization provides network-like functionality to software containers on a single system. Note that the virtualized entities created by network virtualization are still implemented to some extent using hardware such as processors 152 or 175 and memories 155 and 171, and these virtualized entities also produce technical effects.

[0081] Computer-readable storage devices 125, 155, and 171 can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, flash memory, magnetic storage devices and systems, optical storage devices and systems, fixed storage, and removable storage. Computer-readable storage devices 125, 155, and 171 can be components for performing storage functions. Processors 120, 152, and 175 can be of any type suitable for the local technical environment and, as non-limiting examples, can include one or more of general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), and processors based on multi-core processor architectures. Processors 120, 152, and 175 can be components for performing functions such as controlling UE 110, RAN node 170, and other functions described herein.

[0082] Typically, various embodiments of user equipment 110 may include, but are not limited to, cellular phones with wireless communication capabilities (such as smartphones, tablets, personal digital assistants (PDAs)), portable computers with wireless communication capabilities, image capture devices with wireless communication capabilities (such as digital cameras), gaming devices with wireless communication capabilities, music storage and playback devices with wireless communication capabilities, internet devices that allow wireless internet access and browsing, tablets with wireless communication capabilities, and portable units or terminals that combine such functions.

[0083] refer to Figure 2 A schematic diagram of various devices in network 100 is shown. In this example, network 100 supports multi-hop self-backhaul, whereby 5G can be used to transmit packets between integrated access and backhaul (IAB) nodes (12) and donors (20), such as utilizing fiber connections to a next-generation core (NG core or NGC) or evolved packet core (EPC). In this example, three (3) IAB nodes 12 are shown: IAB node 1 14; IAB node 2 16; and IAB node 3 18. However, more or fewer nodes 12 can be provided, and their topology can vary. Figure 2 Donor 20 and various user equipment (UE) 110 are also shown. Each IAB node logically consists of a mobile terminal (MT) (e.g., IAB MT) that communicates with upstream nodes and RAN components (such as distributed units (DU) (e.g., IAB DU)) that communicate with downstream IAB nodes or subscriber UEs 110. In other words, the MT portion of an IAB node can be used to communicate with the parent node, and the DU portion of an IAB node can be used to communicate with child nodes or UEs.

[0084] The features described in this article typically involve the scheduling of Integrated Access and Backhaul (IAB) nodes for simultaneous reception using both sublinks and parent links. In NR / 5G, the gNB may include a split architecture, where a Centralized Unit (CU) and a Distributed Unit (DU) each perform a subset of the gNB's functions. The mobile terminal (MT) of the IAB node can interact with a parent node such as an IAB donor (e.g., Figure 2 (As shown in Figure 20) communication. IAB donors may include centralized units of the gNB and may also include distributed units. Distributed units (DUs) of an IAB node can communicate with child nodes or user equipment. For example, in Figure 2 In the example, the DU of IAB node 1 14 can be configured to communicate with IAB node 3 18. Therefore, in Figure 2 In the example, IAB donor 20 can send packets to IAB node 114 via backhaul, IAB node 114 can forward the packets to IAB node 318 via backhaul, and IAB node 318 can send packets to UE 110. This process can be considered a form of relay. However, when an IAB node is configured to perform simultaneous reception with both the MT and DU, some packets may not be received due to frequency overlap between MT and DU reception; that is, the same carrier frequency can be used by both the MT and DU. Example embodiments of this disclosure may relate to uplink reporting by the IAB MT, which can facilitate simultaneous reception with both the MT and DU. Example embodiments of this disclosure may relate to scenarios where the IAB MT has a backhaul link with a single parent or has backhaul links with multiple parents.

[0085] In unpaired spectrum FR2 / frequency-based dual connectivity (DC) scenarios, the Integrated Access Backhaul Mobile Terminal (IAB MT) can be scheduled to perform reception using multiple beams, each from a different parent, i.e., an IAB node or an IAB donor. Since IAB MT receive (RX) beamforming can be implemented using hybrid beamforming, it is possible that only one beam can be used for reception at any given time for each panel (IAB MT panel). However, if a single panel receives two beams from spatially separated parents, it can be understood that only one beam's transmission can be successfully received. Without a clear understanding of the IAB-MT's ability to receive two different beams (each from a different parent) using different panels, transmission from one parent may fail.

[0086] In an example embodiment of this disclosure, the in-frequency DC scenario may rely on enhanced beam reporting, so that beam pairs that can be received simultaneously at the IAB MT can be reported to the network / parent.

[0087] RAN1 agrees to Space Division Multiplexing / Frequency Division Multiplexing (SDM / FDM) operations (Scenario #A and Scenario #B), anticipating further consideration of these multiplexing modes in the future, potentially involving: timing modes in Scenario #6 and #7; extensions for downlink / uplink (DL / UL) power control; cross-link interference (CLI); and / or interference measurements on the backhaul (BH) link as needed to support simultaneous operation (transmit and / or receive). Scenarios #A and #B are mentioned in the following agreement [Session description of 8.10 (Enhancements to Integrated Access and Backhaul), 3GPP TSG RAN WG1 Meeting #102-e]:

[0088] "……protocol

[0089] Based on WID, Rel-17 supports the following reuse scenarios:

[0090] Multiplexing scenario A: Simultaneous use of MT-Tx / DU-Tx

[0091] Multiplexing scenario B: Simultaneous use of MT-Rx / DU-Rx

[0092] Multiplexing scenario C: Simultaneous use of MT-Rx / DU-Tx

[0093] Multiplexing scenario D: Simultaneous use of MT-Tx / DU-Rx

[0094] For both scenario A and scenario B, at least the following scenarios should be further investigated:

[0095] Single-panel or multi-panel IAB nodes operating in unpaired spectrum (FR1 and FR2 bands)

[0096] For cases C and D, at least the following scenarios should be further investigated:

[0097] Multi-panel IAB nodes operating in unpaired spectrum (FR1 and FR2 bands)

[0098] FFS: Supports the required level of specification impact for different scenarios. Any additional specification support in Rel-17 should be conditional on the feasibility from an interference and reliability perspective on a per-link and per-network basis…

[0099] In this protocol, it can be noted that simultaneous reception at Integrated Access and Backhaul (IAB) nodes may require specifications for the following scenarios: IAB Mobile Terminal (MT) and IAB Distributed Unit (DU) supporting scenario #B (i.e., simultaneous MT and DU reception), where the IAB MT is connected to only a single parent; IAB MT and IAB DU supporting scenario #B, where the IAB MT is connected to multiple parents (when supported in an in-frequency DC scenario); and IAB MT and IAB DU supporting Time Division Multiplexing (TDM), where the IAB MT is connected to multiple parents (when supported by an in-frequency DC scenario). The last scenario may also relate to UEs connected to multiple parents (e.g., Multi-TRP beam reporting).

[0100] In Rel-15, beam reporting is supported, and TS 38.214 [“NR; Physical Layer Procedures for Data”, 3GPP] documents the following:

[0101] "...If the UE is configured with CSI-ReportConfig, and the higher-level parameter reportQuantity is set to 'cri-RSRP' or 'ssb-Index-RSRP',

[0102] - If the UE is configured with the higher-level parameter groupBasedBeamReporting set to "Disabled", the UE does not need to update measurements for more than 64 CSI-RS and / or SSB resources, and the UE should report different CRIs or SSBRIs in a single report nrRreportedRS (configured higher-level parameter) for each report.

[0103] - If the UE is configured with the high-level parameter groupBasedBeamReporting set to "Enabled", the UE does not need to update measurements for more than 64 CSI-RS and / or SSB resources, and the UE should report two different CRIs or SSBRIs in a single reporting instance for each report, where the CSI-RS and / or SSB resources can be received simultaneously by the UE using a single spatial domain receive filter or using multiple simultaneous spatial domain receive filters..."

[0104] TS 38.331 [“Radio Resource Control (RRC); Protocol Specification”, 3GPP] presents... Figure 4 The CSI-ReportConfig information element shown.

[0105] The discussion on beam reporting enhancement for RAN1 feMIMO is documented in the FL summary of R1-2007294, "Summary of email discussion on beam management for simultaneous multi-TRP transmission using multiple Rx panels," in Moderator (CATT). The following items are recorded:

[0106] "...For L1-RSRP, consider measurement / reporting enhancement to facilitate inter-TRP beamforming."

[0107] pair

[0108] Option 1: Group-based reporting

[0109] For example, beam confinement to facilitate pairing between TRPs.

[0110] Option 2: Non-group-based reporting...

[0111] ...to evaluate and study at least, but not limited to, the following multibeam enhancement problems

[0112] Question 1: Considering inter-beam interference

[0113] Question 2: For group-based reporting, the number of groups and / or beams per group has been increased. Question 3: UE Rx panel-related beam measurements / reporting.

[0114] Note: The "UE panel" is for discussion purposes only...

[0115] ...Example proposals for options 1 / 2 of proposal 1-1. Note that these examples are not exhaustive or exclusive.

[0116] Option 1:

[0117] Example 1: Introducing a higher-level configuration index (labeled SSI, for discussion purposes only) into CMR resources, where the UE is requested to report beams with the same or different SSIs within the reported group.

[0118] Example 2: A CSI resource setting can be configured with multiple CSI-RS resource sets (each resource set transparently corresponds to a TRP), with restrictions / requirements on group-based reporting. Example 1: The maximum number of CSI-RSs to be reported in the sets within a group, such as 1, 2, or 4. Example 2: If multiple CSI-RS resources are reported in a group, each set should have at least one CSI-RS source to report.

[0119] Option 2

[0120] Example 1: Configure two non-group-based reporting settings for the UE to report L1-RSRP measurement results, where reporting setting 1 includes resources from TRP1 and another reporting setting 2 includes resources from a second TRP2. The two reporting settings are configured so that the UE knows it can simultaneously receive the beams reported in both reports.

[0121] Example 2: Configure two non-group-based reporting settings for the UE to report L1-RSRP measurement results, where reporting setting 1 contains resources from TRP1 and another reporting setting 2 contains resources from a second TRP2. An explicit ID is associated with each reported resource. Reported resources associated with different IDs can be received by the UE simultaneously. Reported resources associated with the same ID cannot be received by the UE simultaneously…

[0122] UEs can choose to report beam pairs they can receive simultaneously. In group-based beam reporting, beam pairs can be selected from a single Transmit and Receive Point (TRP) or multiple TRPs, but discussions for Rel-17feMIMO (Further Enhanced MIMO) are ongoing to consider beam pairs from different TRPs. Assuming the MT will support Rel-16 / 17 UE MIMO capabilities, these beam reporting features can help address the issue of IAB nodes where simultaneous transmissions may cause one or more transmissions to fail to be received. However, this IAB issue may require a different solution than that implied by either UE group-based or non-group-based beam reporting, as supporting multiplexing case #B (i.e., simultaneous MT-Rx / DU-Rx) along with in-frequency DC may additionally require alignment for simultaneous reception of the MT and DU beams. MT beam availability can vary depending on which subnode or UE the IABDU is scheduled to receive at a given time. Solutions to this problem can also extend beyond the in-frequency DC scenario and are generally applicable to case #B operation, as simultaneous reception of the MT and DU beams may be supported in the future.

[0123] The exemplary embodiments disclosed herein can be applied to both single-parent and multi-parent scenarios.

[0124] Now for reference Figure 3 This illustrates an example scenario of IAB operation in both spatial division multiplexing (SDM) case #B (i.e., simultaneous MT-Rx / DU-Rx) and intra-frequency dual-connection DC. Figure 3 In the example, the IAB node consists of four panels (panel #1, panel #2, panel #3, and panel #4), each pointing in a different direction. However, it should be understood that an IAB node can include more or fewer panels arranged in similar or different configurations. Figure 3In the example, an IAB node can use a fixed panel (covering only one direction) or several panels (covering more directions) to provide services to its nearby child nodes / UEs (e.g., child node #1, child node #2), and can also use the same set of panels to maintain connectivity toward / to the parent (e.g., parent #1, parent #2).

[0125] exist Figure 3 In this embodiment, assuming that group-based beam reporting is enhanced according to an example embodiment of this disclosure, intra-frequency DC support can use one or more of the following beam pairs: (x1, y1), (x2, y1), (x3, y1), (x3, y2), (x3, y3). These beam pairs are feasible because they enable parent #1 and parent #2 beams to be received using different panels. Figure 3 In the example, parent #1 sends beams x1 and x2 to panel #1, and beam x3 to panel #4. Figure 3 In the example, parent #2 sends beam y1 to panel #2 and beams y2 and y3 to panel #1. Therefore, beam x1 of parent #1 and beam y1 of parent #2 can be received simultaneously using different panels; beam x2 of parent #1 and beam y1 of parent #2 can be received simultaneously using different panels; beam x3 of parent #1 and beam y1 of parent #2 can be received simultaneously using different panels; beam x3 of parent #1 and beam y2 of parent #2 can be received simultaneously using different panels; and beam x3 of parent #1 and beam y3 of parent #2 can be received simultaneously using different panels. Conversely, beam x1 of parent #1 and beam y2 of parent #2 may not be received simultaneously because they both point to the same panel of the IAB node, i.e., panel #1. It should be noted that there can be more or fewer parents, each parent can send more or fewer beams to the IAB node, and different combinations of beams pointing to each panel are possible. Figure 3 This is intended to illustrate an example, not to limit the scope of this disclosure.

[0126] It should be noted that Figure 3An IAB node can be understood as including both MT and DU. If we assume Case #B operation (i.e., simultaneously MT-Rx / DU-Rx) is performed at both the IAB MT and IAB DU of the IAB node, then in-frequency DC support may not be able to use all the beam pairs reported above because the panel used to serve the child node may not be simultaneously available for in-frequency DC support. Furthermore, the combination of beam pairs available for in-frequency DC support can change as the child node being scheduled by the IAB DU in the UL changes. For example, when the IAB node serves child node #2, panel #2 may not be used for beam y1, which is transmitted / received by parent #1. However, when child node #1 is scheduled by the IAB DU and child node #2 is not scheduled by the IAB DU, beam y1 can be used for in-frequency DC support because... Figure 3 In the example, child node #1 transmits towards panel #3 of the IAB node, and the parent node transmitting the beam to panel #3 is not shown.

[0127] It should also be noted that beam usage may be limited in a single-parent scenario. For example, if from... Figure 3 Deleting parent node #1, so that the IAB node is only served by parent node #2, may result in a situation where the #B operation does not allow IAB node MT to receive simultaneously through beam y1 and IAB node DU to receive from child node #2.

[0128] The exemplary embodiments of this disclosure can provide a more efficient framework for beam reporting, which can address the aforementioned problem that simultaneous reception during DC and / or Case #B operations within the frequency range can often result in IAB nodes being unable to receive the beam.

[0129] In the example implementation, beam reporting can be enhanced for IAB deployments, enabling the network to obtain more accurate feedback information to select beams at (multiple) parent nodes for transmission, thereby allowing multiplexing case #B (i.e., MT-Rx / DU-Rx simultaneously) to be enabled at IAB nodes.

[0130] In an example embodiment, when the IAB MT is supported by in-frequency dual connectivity (or a single-parent scenario) and the IAB DU schedules UL transmissions in the same resource (i.e., the IAB DU expects to receive transmissions from the user equipment or child node in the same resource), the beam report from the IAB node to the parent / network may carry additional information indicating the multiplexing mode, the restrictions applied when the multiplexing mode is supported, and / or any other details that may allow the network / parent to understand / determine changes to the beam pairs (beams in a single-parent scenario) that can be received simultaneously at the IAB MT, while the IAB DU is scheduled to receive transmissions from the user equipment or child node.

[0131] In an example embodiment, the network can use additional information included in the beam reports from the IAB nodes to determine / limit the beams used for DL ​​transmissions to the IAB MT, while enabling the IAB DU to provide the possibility of scheduling UL transmissions for (multiple) child nodes.

[0132] In an example embodiment, when the IAB node operates in Time Division Multiplexing (TDM) mode, where the IAB MT and DU use different time-domain allocations, beam reporting may consider / include indications of: multiplexing mode; indication of lack of beam / panel restrictions; indication of beam pairs(s) based on beam measurements; permitted beam pairs(s); and / or reference beam pairs(s). As additional information included in the beam reporting, the IAB MT may report multiplexing mode (TDM), indication of no restrictions on beam / panel use, and / or any other indications along with beam pairs (e.g., using group-based beam reporting or beam-single-parent scenarios) based on beam measurements performed at / using the IAB MT. In one variant, the reported beam pair(s) (or beams) may be used as reference beam pairs(s) for future updates. The IAB MT can be configured to report more than one beam pair (sufficient combinations) as additional information included in the beam report, enabling the parent to have more than one beam pair that can be applied when supporting DC connections within frequencies with any multiplexing mode. The reported beam pair (or beam) can also be considered as one of the multiple reference beam pairs supported by the IAB MT. The reference beam pair (or beam) can be fixed or updated over time based on additional measurements and reports performed by / utilizing the IAB MT.

[0133] In an example embodiment, when the IAB node operates in case #B (i.e., simultaneous MT-Rx / DU-Rx), where the IABMT and DU can operate for simultaneous reception, beam reporting may consider / include indications of multiplexing modes; indications of beam / panel limitations; indications of no beam pair(s) based on beam measurements; and / or changes in beam pairs. In one variant, based on beam measurements performed at / using the IAB MT, the IAB MT may report multiplexing modes (SDM), indications of certain limitations on beam / panel usage, and / or any other indications, as additional information included in the beam reporting, regardless of whether there are beam pairs (e.g., using group-based beam reporting) (beams in a single-parent scenario). When the IAB MT reports indications of certain limitations on beam / panel usage or any other indication, the IAB MT may determine changes / limitations to beam pairs (beams) based on using the IAB DU panel to serve one or more child nodes. In another reporting variant, with or without precise beam measurements, IAB MT may report changes in the beam pair (beam) compared to previously reported beam pairs / beams or compared to (multiple) reference beam pairs / beams when using TDM mode, as additional information included in the beam report.

[0134] In the example embodiment, when the IAB node operates in case #B (i.e., simultaneously MT-Rx / DU-Rx) and serves a different child node than before, the change in beam pair (beam) can be reported again to reflect the change due to the different child node (applying the previous method).

[0135] In an example embodiment, for an in-frequency DC scenario, the aforementioned beam reporting enhancements (including additional information that enables the network to determine changes to beam pairs that can be received simultaneously at the IAB MT) can use a group-based beam measurement and reporting framework, wherein beam pairs that can be received simultaneously can be reported by the IAB MT using one or more variations of the aforementioned additional information.

[0136] In an example embodiment, in a single-parent scenario, the aforementioned beam reporting enhancements (including additional information that enables the network to determine changes to beam pairs that can be received simultaneously at the IAB MT) can use a conventional beam measurement and reporting framework, wherein beam pairs that can be received simultaneously can be reported by the IAB MT using one or more variations of the aforementioned additional information.

[0137] Now for reference Figure 5This illustrates an example scenario of Case #B (i.e., simultaneous MT-Rx / DU-Rx) and in-frequency DC operation. In this example, the IAB node is shown as having four panels: panel #1, panel #2, panel #3, and panel #4. Parent #1 can be configured to transmit to panels #1 and #4 of the IAB node. Parent #2 can be configured to transmit to panels #1 and #2 of the IAB node. Child node #1 can be configured to transmit to panel #3. Child node #2 can be configured to transmit to panel #2. Child node #3 can be configured to transmit to panel #4. In other words, the IAB node can be configured to receive transmissions from: parent #1 and parent #2 of panel #1; parent #2 and child node #2 of panel #2; child node #1 of panel #3; and parent #1 and child node #3 of panel #4.

[0138] use Figure 5 As an example, the following is a description of the beam pairs that an IAB MT can report to its parent node / network. If the IAB node is operating in TDM mode, beam measurement and reporting can indicate one or more of the following reference beam pairs: (x1, y1), (x2, y1), (x3, y1), (x3, y2), (x3, y3). The beam pairs that can be reported to the parent(s) / network(s) can be determined, at least in part, based on the child(s) that the IAB node is scheduled to receive uplink transmissions from it.

[0139] Based on IAB scheduling decisions for SDM operations with different child nodes, some reference pairs may be unsuitable. Figure 5 In the example, when the IAB-DU has no scheduled child nodes, the reference pairs can include (x1, y1), (x2, y1), (x3, y1), (x3, y2), and (x3, y3). Based on... Figure 5 In one example of the scenario shown, when child node #1 is scheduled by IAB-DU, the reference pair may include (x1, y1), (x2, y1), (x3, y1), (x3, y2), and (x3, y3). In this example, scheduling child node #1 may not result in a change to the reference pair. When child node scheduling does not result in a change to the reference pair, IAB-MT may update or not update (multiple) parent nodes. However, other scheduling by IAB-DU may result in an update to the reference pair.

[0140] Based on Figure 5 In one example of the scenario shown, when child node #2 is scheduled by IAB-DU, the reference pair can be updated to include (x3, y2) and (x3, y3). In other words, when child node #2 is scheduled by IAB-DU, the beam pairs (x1, y1), (x2, y1), and (x3, y1) may not be suitable.

[0141] Based on Figure 5 In one example of the scenario shown, when child node #3 is scheduled by IAB-DU, the reference pair can be updated to include (x1, y1) and (x2, y1). In other words, when child node #3 is scheduled by IAB-DU, the beam pairs (x3, y1), (x3, y2), and (x3, y3) may not be suitable.

[0142] Based on Figure 5 In one example of the scenario shown, when both child nodes #2 and #3 are scheduled by the IAB-DU, the reference pair can be updated to exclude any beam pairs. In other words, when child nodes #2 and #3 are scheduled by the IAB-DU, the beam pairs (x1, y1), (x2, y1), (x3, y1), (x3, y2), and (x3, y3) may not be suitable.

[0143] The aforementioned example considers in Figure 5 The scenario shown depicts an IAB node connected to both parents #1 and #2. However, an IAB node might only be connected to one of its parents. For example, an IAB node could be connected to only parent #2. For serving child #2, the reference pair could be updated to include only the beam pair using parent #2 beams y2 and y3, as shown. Figure 5 As shown, both parent #2 beam y1 and child node #2 beam are pointed at panel #2. Since these beams cannot be received simultaneously, the IAB node can include additional information in its beam report indicating that in case #B (i.e., simultaneous MT-Rx / DU-Rx), beam y1 pointing at panel #2 can be left unused so that reception from child node #2 can be achieved at the IAB node. Other combinations of scheduled reception from (multiple) parent nodes and (multiple) child nodes are also possible.

[0144] Based on Figure 5 In the above examples of the illustrated scenarios, measurements and reporting may not always be performed, thus requiring all details to be reported. In the example embodiments, beam measurements may or may not be performed when the child node is scheduled by the IAB-DU. In the example embodiments, reporting may or may not be performed when the child node is scheduled by the IAB-DU. Methods for optimizing feedback overhead are not discussed in detail in this disclosure because such mechanisms are well-known (e.g., bitmaps).

[0145] When the IAB node is stationary, the beam pairs applicable to TDM may not change significantly compared to the mobility scenario. Therefore, in the example embodiment, beam measurements and reporting can only consider assumed TDM operation (i.e., infrequent updates), and frequent updates can report changes to the reported beam pairs depending on panel usage / subnode scheduling. Since the IAB node may therefore not waste effort on frequent beam measurements and reporting, we expect efficient simultaneous operation of in-frequency DC and case #B (i.e., simultaneous MT-Rx / DU-Rx) at the IAB node.

[0146] Now for reference Figure 6 An example signaling diagram of enhanced beam reporting according to an exemplary embodiment of this disclosure is shown for SDM operation with a single parent node. It should be noted that in this diagram, the IAB nodes are shown as IAB-MT and IAB-DU, with IAB-MT communicating with the parent node and IAB-DU communicating with the child node. In this example, only one parent node is linked to the IAB nodes (IAB-MT + IAB-DU). References below... Figure 7 Describe an example where more than one parent node is linked to an IAB node (IAB-MT+IAB-DU).

[0147] Now for reference Figure 6 At 610, parent #1 can configure the IAB-MT using (multiple) Channel State Information (CSI) report configurations, which can enable beam reporting / management. Within the CSI report configuration, (multiple) associated reference signals (RS) for (multiple) beams can also be indicated. At 615, parent #1 can send associated Channel State Information Reference Signal (CSI-RS) resources (with corresponding beams) to the IAB-MT. These CSI-RSs can include non-zero power (NZP) CSI-RSs. Figure 6 In the example, the corresponding beam can include the parent beam #1-#8.

[0148] At 620, the IAB-MT can perform multiple beam measurements. For example, assuming simultaneous reception at both the IAB-MT and DU is not required, the IAB-MT can use two panels for CSI-RS measurements. Figure 6In the example, the IAB node can determine that the IAB multiplexing mode is TDM. The IAB node can determine, based on beam measurements, that beams #1, #2, and #3 can be received using panel #1; beams #4, #5, and #6 can be received using panel #2; and beams #7 and #8 may not be received by any panel. At 625, the IAB-MT can report (multiple) beam reports / measurements (e.g., via CSI reports) and additional information as described above to the network (i.e., parent #1). For example, the additional information may include an indication of the IAB node's TDM mode, and / or an indication of acceptable beams #1-#6 for transmissions from parent #1, etc.

[0149] At 630, parent #1 can activate / use(multiple) reported beams, which can be in the form of Transmission Configuration Indicator (TCI) states associated with received CRIs, for use in(multiple) control and / or data channels. Figure 6 In the example, parent #1 can activate one or more of beams #1-#6. Although in Figure 6 Not shown, but parent #1 can use one or more of the beams (i.e., beams #1-#6) reported using CSI-RS to perform data transmission to the IAB node.

[0150] In 635, IAB-DU can schedule one or more child nodes in the case of IAB-MT (i.e., simultaneously MT-Rx / DU-Rx) SDM Rx multiplexing mode, and can predetermine the panels (beams) to be used to serve the child nodes. Figure 6 In the example, the IAB-DU may decide to use panel #2 to achieve reception from the child node. Therefore, when the child node is scheduled, it may not be possible to simultaneously receive beams #4-#6 from the parent #1 using panel #2. At 640, the IAB-MT may report beams with additional information to the network (i.e., the parent #1) (e.g., via CSI reporting or any other reporting method). For example, the additional information may include limitations applied to SDM operation as described above. For example, the additional information may include an indication that beams #4, #5, and #6 may not be received by the IAB-MT. The additional information may also include an indication that the multiplexing mode is SDM. In another example, the IAB-DU may include an indication that panel #2 will be used for reception from the child node.

[0151] At 645, in the form of the TCI state to be used, parent #1 can activate / use only the reporting beam indicated by the latest update for control and data purposes. Parent #1 can activate one or more unrestricted beams, i.e., beams #1-#3. IAB-MT may or may not acquire / receive additional activation commands for the TCI state.

[0152] In 650, IAB-DU can schedule (multiple) UL transmissions, allowing IAB nodes to operate in Case #B mode (i.e., simultaneously MT-Rx / DU-Rx). IAB-DU can use Case #B operation to send UL authorizations to child nodes.

[0153] At 655, parent #1 can perform downlink transmissions to IAB-MT, and child nodes can simultaneously (i.e., within the same time slot or period) perform uplink transmissions to IAB-DU. Each transmission can be received by the IAB node because the transmissions are non-overlapping, i.e., received using different panels of the IAB node.

[0154] Now for reference Figure 7 An example signaling diagram of enhanced beam reporting according to an exemplary embodiment of this disclosure is shown for SDM operation with in-frequency DC. It should be noted that in this diagram, the IAB nodes are shown as IAB-MT and IAB-DU, with IAB-MT communicating with a parent node and IAB-DU communicating with a child node. In this example, two parent nodes are linked to the IAB nodes (IAB-MT+IAB-DU), namely parent #1 and parent #2.

[0155] At 710, parent #1 can send a CSI-RS configuration for beam management to the IAB-MT. This configuration can enable group-based beam reporting. Within the CSI reporting configuration, multiple associated reference signals (RS) for (multiple) beams can also be indicated. At 715, parent #1 can send associated Channel State Information Reference Signal (CSI-RS) resources (with corresponding beams) to the IAB-MT. These CSI-RSs can include non-zero power (NZP) CSI-RSs. Figure 7 In the example, the corresponding beams could include beams #1-#4 of parent #1. At 720, parent #2 could transmit associated CSI-RS to the IAB-MT. These CSI-RS could include non-zero power (NZP) CSI-RS. Figure 7 In the example, the corresponding beam can include the parent beam #5-#8.

[0156] At 725, the IAB-MT can perform (multiple) beam measurements. Figure 7In the example, the IAB node can determine that the IAB multiplexing mode is TDM. The IAB node can determine, based on beam measurements, that beam pairs (#1, #5), (#3, #7), and (#2, #7) are appropriate (i.e., these beam pairs will allow simultaneous reception by both parent #1 and parent #2). At 730, the IAB-MT can report (multiple) beam reports / measurements (e.g., via CSI reports) and additional information as described above to the network (i.e., parent #1). For example, the additional information may include an indication of the IAB node's TDM mode, and / or an indication of acceptable beam pairs ((#1, #5), (#3, #7), (#2, #7)) for transmissions from parent #1 and #2, etc. Parent #1 can forward this beam report, including the additional information, to parent #2 at 735.

[0157] At 740, both parent #1 and parent #2 can activate / use (multiple) reported beams, which can be in the form of Transmission Configuration Indicator (TCI) states associated with received CRIs, for use in (multiple) control and / or data channels. Figure 7 In the example, parent #1 can activate one or more of beams #1, #2, and / or #3, and parent #2 can activate one or more of beams #5 and / or #7. Although in Figure 7 Not shown, but parent #1 and / or #2 may use one or more of the beams reported using CSI-RS (i.e., beams #1-#3, #5 and / or #7) to perform data transmission to the IAB node.

[0158] In 745, IAB-DU can schedule one or more child nodes in the case of IAB-MT (i.e., simultaneously MT-Rx / DU-Rx) SDM Rx multiplexing mode, and the panels / beams to be used to serve the child nodes can be predetermined. Figure 7In the example, the IAB-DU can decide to use the panels that affect the reception of beam pairs (#3, #7) to achieve reception from the child node. Therefore, when a child node is scheduled, it may only be able to receive transmissions from the parent node using beam pairs (#1, #5) and (#2, #7). At 750, the IAB-MT can report a beam report with additional information to the network (i.e., parent #1) (e.g., via CSI reporting or any other reporting method). For example, the additional information may include restrictions applied to SDM operation as described above. For example, the additional information may include an indication that the multiplexing mode is SDM. For example, the additional information may include an indication that transmissions utilizing beam pairs (#3, #7) may not be received by the IAB-MT. In another example, the IAB-MT may include an indication of the panels to be used for reception from the child node. Parent #1 can forward this beam report (including the additional information) to parent #2. Alternatively, when additional information regarding the restricted panel at the IAB node is available at parent #1, and if beam #7 can still be used only for transmissions using parent #2, parent #1 may not forward the beam report to parent #2, but parent #1 may restrict the use of beam #1.

[0159] At 755, in the form of the TCI state to be used, both parent #1 and parent #2 can activate / use only the reporting beam indicated by the latest update for control and data purposes. Figure 7 In the example, parent #1 can activate one or more of beams #1 and / or #2, and parent #2 can activate one or more of beams #5 and / or #7. The IAB-MT may or may not acquire / receive additional activation commands for TCI status.

[0160] In version 760, the IAB-DU can schedule (multiple) UL transmissions, allowing the IAB node to operate in scenario #B mode (i.e., simultaneously MT-Rx / DU-Rx). The IAB-DU can use scenario #B operation to send UL authorizations to child nodes.

[0161] In 765, parent #1 and parent #2 can perform downlink transmissions to IAB-MT, and child nodes can simultaneously (i.e., within the same time slot or time period) perform uplink transmissions to IAB-DU. Each transmission can be received by the IAB node because the transmissions are non-overlapping, i.e., they are received using different panels of the IAB node.

[0162] The technical effect of the exemplary embodiments of this disclosure can be to ensure that the parent node does not use a beam that may interfere with the IAB node's reception of beams scheduled to be received from the child node to send to the IAB node.

[0163] Figure 8Potential steps of example method 800 are illustrated. Example method 800 may include performing beam measurement using a first node on a downlink beam received from at least one second node using the first node, 810; scheduling at least one third node using the first node for uplink transmission to the first node, 820; determining, at least in part based on the scheduling of the at least one third node and the execution of the beam measurement, using the first node one or more downlink beams that can be received simultaneously with the beam of the at least one third node, 830; and transmitting the result of the performed beam measurement using the first node, wherein the result includes an indication of one or more determined downlink beams that can be received simultaneously with the beam of the at least one third node, 840.

[0164] Figure 9 Potential steps of example method 900 are illustrated. Example method 900 may include sending to a first node an indication that a second node is configured for downlink transmission of one or more resources, 910; receiving from the first node a beam report for one or more resources, wherein the beam report includes an indication of at least one of the one or more resources that can be received using the first node, 920; activating one or more of the at least one indicated resource, 930; and performing a downlink transmission to the first node using the one or more activated resources, 940.

[0165] According to one aspect, an example method may be provided, the example method comprising: performing beam measurement on a downlink beam received from at least one second node using a first node; scheduling at least one third node using the first node for uplink transmission to the first node; determining, at least in part based on the scheduling of the at least one third node and the execution of the beam measurement, one or more downlink beams among the downlink beams that can be received simultaneously with the beams of the at least one third node; and transmitting, using the first node, the result of the performed beam measurement, wherein the result may include an indication of the one or more determined downlink beams that can be received simultaneously with the beams of the at least one third node.

[0166] The example method may further include: receiving configuration from the at least one second node using the first node, wherein the transmission of the result of the performed beam management may be at least partially based on the received configuration.

[0167] The first node may include an integrated access and backhaul node divided into mobile terminals and distributed units, wherein the transmission using the first node can be performed using the mobile terminals, and the scheduling of the at least one third node can be performed using the distributed units.

[0168] The example method may further include: utilizing the first node to simultaneously receive a downlink beam from at least one of the at least two second nodes and an uplink beam from at least one of the at least three third nodes.

[0169] The determination of the one or more downlink beams that can be received simultaneously with the beams of the at least one third node can be based at least in part on the receiver panel configuration of the first node.

[0170] The transmission of the result of the beam measurement may further include transmitting at least one of the following: the multiplexing mode of the first node, one or more restrictions on the downlink beam, an indication that there are no restrictions on the downlink beam, an indication of one or more reference beams, an indication of one or more reference beam pairs, a beam pair configured to support in-frequency dual connectivity, or an indication based on the beam measurement.

[0171] The first node can operate in either time-division multiplexing mode or space-division multiplexing mode.

[0172] The example method may further include: sending an uplink grant configuration to the at least one third node, wherein the determination of the one or more downlink beams that can be received simultaneously with the beams of the at least one third node may be based at least in part on one or more panels of the first node indicated by the uplink grant configuration.

[0173] The downlink beam and the beam of the at least one third node can be associated with overlapping frequencies.

[0174] The first node can be configured to operate in a dual-connection mode within the frequency range.

[0175] The transmission of the result of the performed beam measurement may include sending the result to at least one of the at least one second node.

[0176] The at least one second node may include at least a first parent node and a second parent node, wherein the determination of the one or more downlink beams that can be received simultaneously with the beam of the at least one third node may include: determining at least one downlink beam of the first parent node and at least one downlink beam of the second parent node that can be received simultaneously.

[0177] According to one example embodiment, an apparatus may include: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code being configured, together with the at least one processor, to cause the apparatus to: perform beam measurement on downlink beams received from at least one second node using the apparatus; schedule at least one third node for uplink transmission to the apparatus; determine one or more downlink beams that can be received simultaneously with the beams of the at least one third node, based at least in part on the scheduling of the at least one third node and the execution of the beam measurement; and transmit the results of the performed beam measurement, wherein the results may include an indication of the one or more determined downlink beams that can be received simultaneously with the beams of the at least one third node.

[0178] The example apparatus may also be configured to receive configuration from the at least one second node, wherein the transmission of the result of the performed beam management is at least in part based on the received configuration.

[0179] The example device can also be configured to simultaneously receive a downlink beam from at least one of the at least two second nodes and an uplink beam from at least one of the at least three third nodes.

[0180] The determination that one or more downlink beams capable of being received simultaneously with the beam of the at least one third node can be at least partially based on the receiver panel configuration of the device.

[0181] Sending the result of the beam measurement may further include sending at least one of the following: the multiplexing mode of the device, one or more restrictions on the downlink beam, an indication that there are no restrictions on the downlink beam, an indication of one or more reference beams, an indication of one or more reference beam pairs, a beam pair configured to support in-frequency dual connectivity, or an indication based on the beam measurement.

[0182] The example device can also be configured to operate in either time-division multiplexing mode or space-division multiplexing mode.

[0183] The example device may also be configured to send an uplink grant configuration to the at least one third node, wherein the determination of the one or more downlink beams that can be received simultaneously with the beams of the at least one third node may be based at least in part on one or more panels of the device indicated by the uplink grant configuration.

[0184] The downlink beam and the beam of the at least one third node can be associated with overlapping frequencies.

[0185] The example device can also be configured to operate in a dual-connection mode within the frequency range.

[0186] Sending the results of the performed beam measurement may include sending the results to at least one of the at least one second node.

[0187] The at least one second node may include at least a first parent node and a second parent node, wherein the determination of the one or more downlink beams that can be received simultaneously with the beam of the at least one third node may include: determining at least one downlink beam of the first parent node and at least one downlink beam of the second parent node that can be received simultaneously.

[0188] According to one example embodiment, an apparatus may include a circuit system configured to perform: performing beam measurement on a downlink beam received from at least one second node using a first node; scheduling at least one third node using the first node for uplink transmission to the first node; determining, using the first node, one or more downlink beams that can be received simultaneously with the beams of the at least one third node, based at least in part on the scheduling of the at least one third node and the execution of the beam measurement; and transmitting, using the first node, the result of the performed beam measurement, wherein the result may include an indication of the one or more determined downlink beams that can be received simultaneously with the beams of the at least one third node.

[0189] As used in this application, the term "circuit system" may refer to one or more or all of the following: (a) a hardware circuit implementation only (e.g., an implementation only in analog and / or digital circuit systems), and (b) a combination of hardware circuitry and software, such as (if applicable): (i) a combination of (multiple) analog and / or digital hardware circuitry with software / firmware, and (ii) any portion of (multiple) hardware processors having software (including (multiple) digital signal processors, software, and (multiple) memories), which work together to enable a device (such as a mobile phone or server) to perform various functions, and (c) (multiple) hardware circuitry and / or (multiple) processors, such as (multiple) microprocessors or portions of (multiple) microprocessors, which require software (e.g., firmware) to operate, but the software may be absent when operation is not required. This definition of circuit system applies to all uses of the term in this application, including in any claim. As another example, as used in this application, the term circuit system also covers an implementation of hardware circuitry or a processor (or multiple processors) or a portion of hardware circuitry or a processor and its accompanying software and / or firmware. For example, if applicable to a particular claim element, the term "circuit system" also covers baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or network devices.

[0190] According to one example embodiment, an apparatus may include components for performing: performing beam measurement on a downlink beam received from at least one second node using the apparatus; scheduling at least one third node for uplink transmission to the apparatus; determining one or more downlink beams that can be received simultaneously with the beams of the at least one third node, based at least in part on the scheduling of the at least one third node and the performance of the beam measurement; and transmitting the result of the performed beam measurement, wherein the result may include an indication of the one or more determined downlink beams that can be received simultaneously with the beams of the at least one third node.

[0191] According to one example embodiment, a non-transitory computer-readable medium includes program instructions stored thereon, which, when executed by at least one processor, cause the at least one processor to: perform beam measurement on a downlink beam received from at least one second node; schedule at least one third node for uplink transmission; determine one or more downlink beams that can be received simultaneously with the beam of the at least one third node, based at least in part on the scheduling of the at least one third node and the execution of the beam measurement; and transmit the result of the performed beam measurement, wherein the result may include an indication of the one or more determined downlink beams that can be received simultaneously with the beam of the at least one third node.

[0192] According to one aspect, an example method may be provided, the example method comprising: sending to a first node an indication of one or more resources of a second node configured for downlink transmission; receiving from the first node a beam report for the one or more resources, wherein the beam report may include an indication of at least one of the one or more resources that can be received using the first node; activating one or more of the at least one indicated resource; and performing downlink transmission to the first node using the one or more activated resources.

[0193] The example method may further include: receiving from the first node an update of the indication of at least one of the one or more resources that can be received using the first node; activating one or more of the at least one updated resource; and performing a downlink transmission to the first node using the one or more activated updated resources.

[0194] The indication that the at least one resource can be received using the first node may include at least one of the following: the multiplexing mode of the first node, one or more restrictions on downlink transmission, an indication that there are no restrictions on downlink transmission, an indication of one or more reference beams, an indication of one or more reference beam pairs, a beam pair configured to support in-frequency dual connectivity, or an indication of the execution based on the beam measurement.

[0195] The indication that the second node is configured for downlink transmission of the one or more resources may include the second node being configured for downlink transmission of one or more beams.

[0196] The example method may further include: forwarding the received beam report to at least one fourth node.

[0197] The example method may further include: receiving from at least one fourth node an indication that at least one fourth node is configured for one or more resources for downlink transmission; and sending the indication received from the at least one fourth node to the first node.

[0198] According to one example embodiment, an apparatus may include: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code are configured, together with the at least one processor, to cause the apparatus to: send to a first node an indication of one or more resources of a second node configured for downlink transmission; receive from the first node a beam report for the one or more resources, wherein the beam report may include an indication of at least one of the one or more resources that can be received using the first node; activate one or more of the at least one indicated resource; and perform a downlink transmission to the first node using the one or more activated resources.

[0199] The example apparatus may also be configured to: receive from the first node an update of the indication of at least one of the one or more resources that can be received using the first node; activate one or more of the at least one updated resource; and perform a downlink transmission to the first node using the one or more activated updated resources.

[0200] The indication of the at least one resource that can be received using the first node includes at least one of the following: the multiplexing mode of the first node, one or more restrictions on downlink transmission, an indication of no restrictions on downlink transmission, an indication of one or more reference beams, an indication of one or more reference beam pairs, a beam pair configured to support in-frequency dual connectivity, or an indication of the execution based on the beam measurement.

[0201] The indication that the second node is configured for downlink transmission of the one or more resources may include the second node being configured for downlink transmission of one or more beams.

[0202] The example device can also be configured to forward the received beam reports to at least one fourth node.

[0203] The example apparatus may also be configured to: receive from at least one fourth node an indication that at least one fourth node is configured for one or more resources for downlink transmission; and send the indication received from the at least one fourth node to the first node.

[0204] According to one example embodiment, an apparatus may include a circuit system configured to perform: sending to a first node an indication of one or more resources of a second node configured for downlink transmission; receiving from the first node a beam report for the one or more resources, wherein the beam report may include an indication of at least one of the one or more resources that can be received using the first node; activating one or more of the at least one indicated resource; and performing downlink transmission to the first node using the one or more activated resources.

[0205] According to one example embodiment, an apparatus may include components for performing the following: sending to a first node an indication that a second node is configured for downlink transmission of one or more resources; receiving from the first node a beam report for the one or more resources, wherein the beam report may include an indication of at least one of the one or more resources that can be received using the first node; activating one or more of the at least one indicated resource; and performing downlink transmission to the first node using the one or more activated resources.

[0206] According to one example embodiment, a non-transitory computer-readable medium includes program instructions stored thereon, which, when executed by at least one processor, cause the at least one processor to: send to a first node an indication that a second node is configured for downlink transmission of one or more resources; receive from the first node a beam report for the one or more resources, wherein the beam report may include an indication of at least one of the one or more resources that can be received using the first node; activate one or more of the at least one indicated resource; and perform a downlink transmission to the first node using the one or more activated resources.

[0207] It should be understood that the above description is illustrative only. Those skilled in the art can devise various alternatives and modifications. For example, the features recited in the various dependent claims can be combined with each other in any suitable combination. Furthermore, features from the different embodiments described above can be selectively combined to form new embodiments. Therefore, this specification is intended to cover all such alternatives, modifications, and variations falling within the scope of the appended claims.

Claims

1. A method for communication, comprising: Beam measurement is performed on the downlink beam received from at least one second node using the first node; The first node is used to schedule at least one third node for uplink transmission to the first node; Based at least in part on the scheduling of the at least one third node and the execution of the beam measurement, the first node determines one or more downlink beams that can be received simultaneously with the beams of the at least one third node in the downlink beams. as well as The results of the beam measurement performed are transmitted using the first node, wherein the results include an indication of one or more determined downlink beams that can be received simultaneously with the beams of the at least one third node.

2. The method according to claim 1, further comprising: The first node receives a configuration from the at least one second node, wherein the transmission of the result of the performed beam measurement is at least in part based on the received configuration.

3. The method of claim 1, wherein the first node comprises an integrated access and backhaul node divided into a mobile terminal and a distributed unit, wherein the transmission using the first node is performed using the mobile terminal, and wherein the scheduling of the at least one third node is performed using the distributed unit.

4. A device for communication, comprising: At least one processor; as well as At least one non-transitory memory and computer program code, wherein the at least one non-transitory memory and the computer program code are configured, together with the at least one processor, to cause the device to: Perform beam measurement on the downlink beam received from at least one second node using the device; Schedule at least one third node for uplink transmission to the device; Based at least in part on the scheduling of the at least one third node and the execution of the beam measurement, one or more downlink beams that can be received simultaneously with the beams of the at least one third node are determined. as well as The results of the performed beam measurement are transmitted, wherein the results include an indication of one or more determined downlink beams that can be received simultaneously with the beam of the at least one third node.

5. The apparatus of claim 4, wherein the at least one memory and the computer program code are further configured, together with the at least one processor, to cause the apparatus to: The configuration is received from the at least one second node, wherein the transmission of the result of the performed beam measurement is at least in part based on the received configuration.

6. The apparatus of claim 4, wherein the at least one memory and the computer program code are further configured, together with the at least one processor, to cause the apparatus to: Simultaneously receive downlink beams from at least one of the at least two second nodes and uplink beams from at least one of the at least three third nodes.

7. The apparatus of claim 4, wherein the determination of the one or more downlink beams capable of being received simultaneously with the beam of the at least one third node is at least partially based on the receiver panel configuration of the apparatus.

8. The apparatus of claim 4, wherein transmitting the result of the performed beam measurement further comprises transmitting at least one of the following: The reuse mode of the device Regarding one or more limitations of the downlink beam, Regarding the indication that there are no restrictions on the downlink beam, Indication of one or more reference beams, Indication of one or more reference beam pairs, Beam pairs configured to support in-frequency dual connectivity, or The instructions to be executed are based on the beam measurement.

9. The apparatus of claim 4, wherein the at least one memory and the computer program code are further configured, together with the at least one processor, to cause the apparatus to operate in one of the following ways: Time-division multiplexing mode, or Space division multiplexing mode.

10. The apparatus of claim 4, wherein the at least one memory and the computer program code are further configured, together with the at least one processor, to cause the apparatus to: Sending an uplink grant configuration to the at least one third node, wherein the determination of the one or more downlink beams that can be received simultaneously with the beams of the at least one third node is based at least in part on one or more panels of the device indicated by the uplink grant configuration.

11. The apparatus of claim 4, wherein the downlink beam and the beam of the at least one third node are associated with overlapping frequencies.

12. The apparatus of claim 4, wherein the at least one memory and the computer program code are further configured, together with the at least one processor, to enable the apparatus to operate in a frequency-interconnected dual-connection mode.

13. The apparatus of claim 4, wherein transmitting the result of the performed beam measurement comprises: The result is sent to at least one of the at least one second node.

14. The apparatus of claim 4, wherein the at least one second node comprises at least a first parent node and a second parent node, wherein the determination of the one or more downlink beams capable of being received simultaneously with the beam of the at least one third node comprises: Determine at least one downlink beam from the first parent node and at least one downlink beam from the second parent node that can be received simultaneously.

15. An apparatus for communication, comprising: At least one processor; as well as At least one non-transitory memory and computer program code, wherein the at least one non-transitory memory and the computer program code are configured, together with the at least one processor, to cause the device to: Send an indication to the first node that the second node is configured to use one or more resources for downlink transmission; Receive beam reports for the one or more resources from the first node, wherein the beam reports include: an indication of at least one of the one or more resources that can be simultaneously received using the beams of the first node and at least one third node, and the beam reports indicate the results of beam measurements by the first node. Activate one or more of the resources indicated by at least one instruction; and Downlink transmission to the first node is performed using the one or more activated resources.

16. The apparatus of claim 15, wherein the at least one memory and the computer program code are further configured, together with the at least one processor, to cause the apparatus to: Receive an update from the first node on the indication of at least one of the one or more resources that can be received using the first node; Activate one or more of the at least one updated resource; as well as Downlink transmission to the first node is performed using one or more of the activated updated resources.

17. The apparatus of claim 15, wherein the indication of the at least one resource that can be received using the first node includes at least one of the following: The reuse mode of the first node, One or more restrictions on downlink transmission, Regarding the indication that there are no restrictions on downlink transmission, Indication of one or more reference beams, Indication of one or more reference beam pairs, Beam pairs configured to support in-frequency dual connectivity, or Instructions based on the execution of the beam measurement.

18. The apparatus of claim 15, wherein the indication that the second node is configured for downlink transmission of the one or more resources includes: The second node is configured as one or more beams for downlink transmission.

19. The apparatus of claim 15, wherein the at least one memory and the computer program code are further configured, together with the at least one processor, to cause the apparatus to: The received beam report is forwarded to at least one fourth node.

20. The apparatus of claim 15, wherein the at least one memory and the computer program code are further configured, together with the at least one processor, to cause the apparatus to: Receive from at least one fourth node an indication that at least one fourth node is configured for one or more resources for downlink transmission; and Send the instruction received from the at least one fourth node to the first node.

Images