Power control using at least one power control parameter

Abstract

The present disclosure relates to power control using at least one power control parameter. Apparatuses, methods, and systems are disclosed for power control using at least one power control parameter. One method (1600) includes receiving (1602), at a first device, configuration information comprising a power offset value associated with a first plurality of resources and a first reference signal. The method (1600) includes receiving (1604) the first reference signal from a second device. The method (1600) includes performing (1606) a first measurement of the first reference signal. The method (1600) includes calculating (1608) a first expected received power value based on the first measurement and the power offset value. The method (1600) includes calculating (1610) a first target received power value. The method (1600) includes transmitting (1612) at least one downlink power control parameter to the second device based on the first target received power value and the first expected received power value.

Description

[0001] This application is a divisional application of PCT application number PCT / IB2021 / 050967, which entered the Chinese national phase on August 3, 2022; international application date February 5, 2021; Chinese application number 202180012562.6; and invention title "Power Control Using at Least One Power Control Parameter".

[0002] Cross-references to related applications

[0003] This application claims priority to U.S. Patent Application Serial No. 62 / 971,082, filed February 6, 2020, entitled “Apparatus, Methods, and Systems for Receiving Power Control in Integrated Access and Backhaul Systems,” which is incorporated herein by reference in its entirety. Technical Field

[0004] The topics disclosed in this paper generally relate to wireless communication, and more specifically to power control using at least one power control parameter. Background Technology

[0005] The following abbreviations are defined herein, and at least some of them are referenced in the following descriptions: Third Generation Partnership Project (“3GPP”), Fifth Generation (“5G”), QoS for NR V2X Communication (“5QI / PQI”), Authentication, Authorization and Accounting (“AAA”), Positive Acknowledgment (“ACK”), Aperiodic CSI (“A-CSI”), Application Function (“AF”), Authentication and Key Protocol (“AKA”), Aggregation Level (“AL”), Access and Mobility Management Function (“AMF”), Angle of Arrival (“AoA”), Angle of Departure (“AoD”), Access Point (“AP”), Application Server (“AS”), Application Service Provider (“ASP”), Autonomous Uplink (“AUL”), Authentication Server Function (“AUSF”), Authentication Token (“AUTN”), Background Data (… Background Data Transmission (“BD”), Beam Fault Detection (“BFD”), Beam Fault Recovery (“BFR”), Binary Phase Shift Keying (“BPSK”), Base Station (“BS”), Buffer State Report (“BSR”), Bandwidth (“BW”), Bandwidth Portion (“BWP”), Cell RNTI (“C-RNTI”), Carrier Aggregation (“CA”), Channel Access Priority Class (“CAPC”), Contention-Based Random Access (“CBRA”), Component Carrier (“CC”), Idle Channel Assessment (“CCA”), Common Control Channel (“CCCH”), Common Control Channel Service Data Unit (“CCCH”)SDU, Control Channel Element (“CCE”), Cyclic Delay Diversity (“CDD”), Code Division Multiple Access (“CDMA”), Control Element (“CE”), Contention-Free Random Access (“CFRA”), Configured License (“CG”), Closed Loop (“CL”), Cooperative Multipoint (“CoMP”), Channel Occupancy Time (“COT”), Cyclic Prefix (“CP”), Cyclic Redundancy Check (“CRC”), CSI-RS Resource Index (“CRI”), Channel State Information (“CSI”), Channel State Information-Reference Signal (“CSI-RS”), Common Search Space (“CSS”), Control Resource Set (“CORESET”), Central Unit (“CU”), Discrete Fourier Transform Extended (“DFTS”), Downlink Control Information (“DCI”), Downlink Feedback Information (“DFI”), Downlink Link (“DL”), Demodulation Reference Signal (“DMRS”), Data Network Name (“DNN”), Data Radio Bearer (“DRB”), Discontinuous Receive (“DRX”), Dedicated Short Range Communication (“DSRC”), Distributed Unit (“DU”), Downlink Pilot Slot (“DwPTS”), Enhanced Idle Channel Assessment (“eCCA”), Enhanced Mobile Broadband (“eMBB”), Evolved Node B (“eNB”), Extensible Authentication Protocol (“EAP”), Effective Isotropic Radiated Power (“EIRP”), European Telecommunications Standards Institute (“ETSI”), Frame-Based Equipment (“FBE”), Full Duplex (“FD”), Frequency Division Duplex (“FDD”), Frequency Division Multiplexing (“FDM”), Frequency Division Multiple Access (“FDMA”), Frequency Division Orthogonal Coverage Code (“FD-OCC”), Frequency Range 1–6 Sub-GHz bands and / or 410 MHz to 7125 MHz (“FR1”), frequency range 2–24.25 GHz to 52.6 GHz.GHz (“FR2”), General Geographic Area Description (“GAD”), Guaranteed Bit Rate (“GBR”), Group Leader (“GL”), 5G Node B or Next Generation Node B (“gNB”), Global Navigation Satellite System (“GNSS”), General Packet Radio Service (“GPRS”), Guard Period (“GP”), Global Positioning System (“GPS”), General Public Subscription Identifier (“GPSI”), Global System for Mobile Communications (“GSM”), Globally Unique Temporary UE Identifier (“GUTI”), Home AMF (“hAMF”), Hybrid Automatic Repeat Request (“HARQ”), Hybrid Automatic Repeat Request Acknowledgment (“HARQ-ACK”), Half-Duplex (“HD”), Home Location Register (“HLR”), Handover (“HO”), Home PLMN (“HPLMN”), Home Subscriber Server (“HSS”), Hash Expected Response (“HXRES”), Integrated Access and Backhaul (“IAB”), Identifier or Identifier (“ID”), Information Element (“IE”), International Mobile Equipment Identity (“IMEI”), International Mobile Subscriber Identity (“IMSI”), International Mobile Telecommunications Identity (“IMSI”), International Mobile Telecommunications System ... IMT, Internet of Things (“IoT”), Key Management Function (“KMF”), Layer 1 (“L1”), Layer 2 (“L2”), Layer 3 (“L3”), Licensed Assisted Access (“LAA”), Local Area Data Network (“LADN”), Local Area Network (“LAN”), Load-Based Device (“LBE”), Listen Before Talk (“LBT”), Logical Channel (“LCH”), Logical Channel Group (“LCG”), Logical Channel Priority (“LCP”), Log-Likelihood Ratio (“LLR”), Long Term Evolution (“LTE”), Multiple Access (“MA”), Media Access Control (“MAC”), Multimedia Broadcast Multicast Service (“MBMS”), Maximum Bit Rate (“MBR”), Primary Cell Group (“MCG”), Minimum Communication Range (“MCR”), Modulation and Coding Scheme (“MCS”), Master Information Block (“MIB”), Multimedia Internet Keying (“MIKEY”), Multiple Input Multiple Output (“MIMO”), Mobility Management (“MM”), Mobility Management Entity (“MME”), Mobile Network Operator (“MNO”), Mobile Initiation (“MO”), Massive MTC (“mMTC”), Message APUSCH Timing (“MPO”), Maximum Power Reduction (“MPR”), Multi-Panel Transmit and Receive (“MPTR”), Message A (“MsgA”), Message B (“MsgB”), Mobile Terminal (“MT”), Machine Type Communication (“MTC”), Multi-User Shared Access (“MUSA”), Non-Access Stratum (“NAS”), Narrowband (“NB”), Negative Acknowledgment (“NACK”) or (“NAK”), New Data Indicator (“NDI”), Network Entity (“NE”), Network Exposure Function (“NEF”), Network Function (“NF”), Next Generation (“NG”), NG 5G S-TMSI (“NG-5G-S-TMSI”), Non-Orthogonal Multiple Access (“NOMA”), New Radio (“NR”), Unlicensed NR (“NR-U”), Network Repository Function (“NRF”), Network Scheduling Mode (“NS Mode”) (e.g., Network Scheduling Mode for V2X Communication Resource Allocation—Mode 1 in NR V2X and LTE) V2X Mode-3), Network Slice Instance (“NSI”), Network Slice Selection Assistance Information (“NSSAI”), Network Slice Selection Function (“NSSF”), Network Slice Selection Policy (“NSSP”), Non-Supplementary Uplink (e.g., “Normal” Uplink Carrier) (“NUL”), Operation, Management and Maintenance System or Operation and Maintenance Center (“OAM”), Orthogonal Frequency Division Multiplexing (“OFDM”), Orthogonal Frequency Division Multiple Access (“OFDMA”), Open Loop (“OL”), Other System Information (“OSI”), Power Angle Spectrum (“PAS”), Physical Broadcast Channel (“PBCH”), Power Control (“PC”), UE-to-UE Interface (“PC5”), Policy and Charging Control (“PC”) C”), Primary Cell (“PCell”), Policy Control Function (“PCF”), Physical Cell Identifier (“PCI”), Power Control Resource Set (“PCRS”), Physical Downlink Control Channel (“PDCCH”), Packet Data Convergence Protocol (“PDCP”), Packet Data Network Gateway (“PGW”), Physical Downlink Shared Channel (“PDSCH”), Pattern Division Multiple Access (“PDMA”), Packet Data Unit (“PDU”), Physical Hybrid ARQ Indicator Channel (“PHICH”), Power Headroom (“PH”), Power Headroom Report (“PHR”), Physical Layer (“PHY”), Public Land Mobile Network (“PLMN”), Power Offset Resource Set (“PORS”), PC5QoS Class Identifier (“PQI”), Physical Random Access Channel (“PRACH”), Physical Resource Block (“PRB”), Proximity Service (“ProSe”), Location Reference Signal (“PRS”), Physical Sidelink Control Channel (“PSCCH”), Primary and Secondary Cell (“PSCell”), Power Spectral Density (“PSD”), Physical Sidelink Feedback Control Channel (“PSFCH”), Physical Uplink Control Channel (“PUCCH”), Physical Uplink Shared Channel (“PUSCH”), QoS Class Identifier (“QCI”), Quasi-Co-location (“QCL”), Quality of Service (“QoS”), Quadrature Phase Shift Keying (“QPSK”), Registration Area (“RA”), RARNTI (“RA-RNTI”), Radio Access Network (“RAN”), Random (“RAND”), Radio Access Technology (“RAT”), Serving RAT (“RAT-1”) (serving Uu), Other RAT (“RAT-2”) (no service for Uu), Random Access Procedure (“RACH”), Random Access Preamble Identifier (“RAPID”), Random Access Response (“RAR”), Resource Block (“RB”), Resource Block Allocation (“RBA”), Resource Element (“RE”), Resource Element Group (“REG”), Radio Frequency (“RF”), Radio Link Control (“RLC”), RLC Acknowledgment Mode (“RLC-A”) RLC Unacknowledged Mode / Transparent Mode (“RLC-UM / TM”), Radio Link Failure (“RLF”), Radio Link Monitoring (“RLM”), Radio Network Temporary Identifier (“RNTI”), Reference Signal (“RS”), Residual Minimum System Information (“RMSI”), Radio Resource Control (“RRC”), Radio Resource Management (“RRM”), Resource Extended Multiple Access (“RSMA”), Reference Signal Received Power (“RSRP”), Received Signal Strength Indicator (“RSSI”), Round Trip Time (“RTT”), Receive (“RX”), Sparse Code Multiple Access (“SCMA”), Scheduling Request (“SR”), Scheduling Request Request Indicator (“SRI”), Sounding Reference Signal (“SRS”), Single Carrier Frequency Division Multiple Access (“SC-FDMA”), Secondary Cell (“SCell”), Secondary Cell Group (“SCG”), Shared Channel (“SCH”), Sidelink Control Information (“SCI”), Subcarrier Spacing (“SCS”), Spacing Division Multiplexing (“SDM”), Serving Data Unit (“SDU”), Security Anchor Function (“SEAF”), Sidelink Feedback Content Information (“SFCI”), Serving Gateway (“SGW”), System Information Block (“SIB”), System Information Block Type 1 (“SIB1”), System Information Block Type 2 (“SIB2”), Subscriber Identifier / Identifier Module ( “SIM”, Signal-to-Interference-plus-Noise Ratio (“SINR”), Sidelink (“SL”), Service Level Agreement (“SLA”), Sidelink Synchronization Signal (“SLSS”), Session Management (“SM”), Session Management Function (“SMF”), Special Cell (“SpCell”), Semi-Persistent CSI (“SP-CSI”), Single Network Slice Selection Auxiliary Information (“S-NSSAI”), Scheduling Request (“SR”), Signaling Radio Bearer (“SRB”), SRS Resource Indicator (“SRI”), Shortened TMSI (“S-TMSI”), Shortened TTI (“sTTI”), Synchronization Signal (“SS”), Sidelink CSI RS (“S-CSI”)RS”, Sidelink PRS (“S-PRS”), Sidelink SSB (“S-SSB”), Synchronization Signal Block (“SSB”), Synchronization Signal / Physical Broadcast Channel (“SS / PBCH”), Subscription Hidden Identifier (“SUCI”), Scheduled User Equipment (“SUE”), Supplementary Uplink (“SUL”), Subscriber Permanent Identifier (“SUPI”), Tracking Area (“TA”), TA Identifier (“TAI”), TA Update (“TAU”), Timing Calibration Timer (“TAT”), Transport Block (“TB”), Transport Block Size (“TBS”), Transport Configuration Indicator (“TC”) I), Temporary Cell RNTI (“TC-RNTI”), Time Division Duplex (“TDD”), Time Division Multiplexing (“TDM”), Time Division Orthogonal Cover Code (“TD-OCC”), Temporary Mobile Subscriber Identifier (“TMSI”), Time of Flight (“ToF”), Transmit Power Control (“TPC”), Transmit Receive Point (“TRP”), Transmission Time Interval (“TTI”), Transmit (“TX”), Uplink Control Information (“UCI”), Unified Data Management Function (“UDM”), Unified Data Repository (“UDR”), User Entity / Equipment (Mobile Terminal) (“UE”) (e.g., V2X) UE), UE autonomous mode (UE autonomously selects V2X communication resources - e.g., mode 2 in NR V2X and mode 4 in LTE V2X. UE autonomous selection may or may not be based on resource sensing operation), uplink (“UL”), UL SCH (“UL-SCH”), Universal Mobile Telecommunication System (“UMTS”), user plane (“UP”), UP function (“UPF”), uplink pilot slot (“UpPTS”), ultra-reliable low-latency communication (“URLLC”), UE routing strategy (“URSP”), UE-specific search space (“USS”), vehicle-to-vehicle (“V2V”), vehicle-to-everything (“V2X”), V2X UE (e.g., a UE capable of vehicular communication using 3GPP protocols), access AMF (“vAMF”), V2X encryption key (“VEK”), V2X group key (“VGK”), V2X MIKEY key (“VMK”), visited NSSF (“vNSSF”), visited PLMN (“VPLMN”), V2X service key (“VTK”), wide area network (“WAN”), and global microwave access interoperability (“WiMAX”).

[0006] In some wireless communication networks, power control can be used. Summary of the Invention

[0007] Methods for power control using at least one power control parameter are disclosed. Apparatus and systems also perform the functions of these methods. One embodiment of the method includes receiving configuration information at a first device, including power offset values ​​associated with a first plurality of resources and a first reference signal. In some embodiments, the method includes receiving a first reference signal from a second device. In some embodiments, the method includes performing a first measurement on the first reference signal. In various embodiments, the method includes calculating a first expected received power value based on the first measurement and the power offset value. In some embodiments, the method includes calculating a first target received power value. In some embodiments, the method includes transmitting at least one downlink power control parameter to the second device based on the first target received power value and the first expected received power value.

[0008] An apparatus for power control using at least one power control parameter includes: a receiver, which receives configuration information including power offset values ​​associated with a first plurality of resources and a first reference signal; and receives the first reference signal from a second device. In various embodiments, the apparatus includes a processor, which performs a first measurement on the first reference signal; calculates a first expected received power value based on the first measurement and the power offset value; and calculates a first target received power value. In some embodiments, the apparatus includes a transmitter that transmits at least one downlink power control parameter to the second device based on the first target received power value and the first expected received power value.

[0009] Another embodiment of a method for power control using at least one power control parameter includes receiving a first reference signal from a second device at a first device. In some embodiments, the method includes performing a first measurement on the first reference signal. In some embodiments, the method includes calculating a first expected received power value associated with a first plurality of resources based on the first measurement. In various embodiments, the method includes calculating a first target received power value. In some embodiments, the method includes transmitting at least one downlink power control parameter to the second device based on the first target received power value and the first expected received power value.

[0010] Another apparatus for power control using at least one power control parameter includes a receiver that receives a first reference signal from a second device. In various embodiments, the apparatus includes a processor that: performs a first measurement on the first reference signal; calculates a first expected received power value associated with a first plurality of resources based on the first measurement; and calculates a first target received power value. In some embodiments, the apparatus includes a transmitter that transmits at least one downlink power control parameter to the second device based on the first target received power value and the first expected received power value. Attached Figure Description

[0011] A more detailed description of the embodiments briefly described above will be presented by referring to the specific embodiments illustrated in the accompanying drawings. It should be understood that these drawings depict only some embodiments and are not intended to be limiting of the scope; the embodiments will be described and explained with additional specificity and detail using the drawings, in which: Figure 1 This is a schematic block diagram illustrating an embodiment of a wireless communication system for power control using at least one power control parameter; Figure 2 This is a schematic block diagram illustrating one embodiment of a device that can be used for power control using at least one power control parameter; Figure 3 This is a schematic block diagram illustrating one embodiment of a device that can be used for power control using at least one power control parameter; Figure 4 This is a diagram illustrating one embodiment of the IAB system; Figure 5 This is a diagram illustrating another embodiment of the IAB system; Figure 6 This is a diagram illustrating yet another embodiment of the IAB system; Figure 7 This is a flowchart illustrating one embodiment of a method for transmitting and / or receiving, including a PORS configuration; Figure 8 This is a timing diagram illustrating the timing of transmit and / or receive corresponding to the PORS configuration; Figure 9 This is a flowchart illustrating one embodiment of power control; Figure 10 This is a flowchart illustrating one embodiment of issuing a DL-PC license; Figure 11 This is a flowchart illustrating one embodiment of transmitting and receiving a DL-PC license; Figure 12 This is a timing diagram illustrating the timing of DL-PC requests and DL-PC licenses; Figure 13 This is a diagram illustrating one embodiment of a system using detection; Figure 14 This is a timing diagram illustrating one embodiment of communication including probes; Figure 15 This is a flowchart illustrating one embodiment of a method for determining transmit power settings; Figure 16 This is a flowchart illustrating one embodiment of a method for power control using at least one power control parameter; and Figure 17This is a flowchart illustrating another embodiment of a method for power control using at least one power control parameter. Detailed Implementation

[0012] As those skilled in the art will understand, aspects of the embodiments can be embodied as a system, apparatus, method, or program product. Therefore, embodiments can take the form of a completely hardware embodiment, a completely software embodiment (including firmware, resident software, microcode, etc.), or an embodiment combining software and hardware aspects, which may generally be referred to herein as "circuit," "module," or "system." Furthermore, embodiments can take the form of a program product embodied in one or more computer-readable storage devices stored in machine-readable code, computer-readable code, and / or program code, hereinafter referred to as code. The storage device can be tangible, non-transitory, and / or non-transferable. The storage device may not embody signals. In one embodiment, the storage device uses only signals for accessing the code.

[0013] Certain functional units described in this specification may be designated as modules to more specifically emphasize their implementation independence. For example, modules may be implemented as hardware circuits comprising custom-designed very large-scale integration (“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. Modules may also be implemented in programmable hardware devices such as field-programmable gate arrays, programmable array logic, programmable logic devices, etc.

[0014] Modules can also be implemented in code and / or software for execution by various types of processors. The identified code modules can, for example, comprise one or more physical or logical blocks of executable code, which can be organized, for example, as objects, procedures, or functions. However, the executable files of the identified modules do not need to be physically located together, but can include entirely different instructions stored in different locations that, when logically combined, encompass the module and implement its stated purpose.

[0015] In practice, a code module can be a single instruction or many instructions, and can even be distributed across several different code segments, different programs, and across several memory devices. Similarly, in this document, operational data can be identified and illustrated within a module, and can be represented in any suitable form and organized within any suitable type of data structure. Operational data can be collected as a single dataset or can be distributed across different locations, including across different computer-readable storage devices. Where a module or part of a module is implemented in software, the software portion is stored on one or more computer-readable storage devices.

[0016] Any combination of one or more computer-readable media can be used. A computer-readable medium can be a computer-readable storage medium. A computer-readable storage medium can be a storage device for storing code. A storage device can be, for example, but not limited to, electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor systems, apparatuses, or devices, or any suitable combination thereof.

[0017] More specific examples of storage devices (a non-exhaustive list) will include the following: electrical connections having one or more cables, portable computer disks, hard disks, random access memory (“RAM”), read-only memory (“ROM”), erasable programmable read-only memory (“EPROM” or flash memory), portable optical disc read-only memory (“CD-ROM”), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium can be any tangible medium capable of containing or storing programs for use by or in conjunction with an instruction execution system, apparatus, or device.

[0018] The code used to perform the operations of the embodiments can be any number of lines and can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Python, Ruby, Java, Smalltalk, C++, and conventional procedural programming languages ​​such as the "C" programming language, and / or machine languages ​​such as assembly language. The code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer via any type of network, including a local area network ("LAN") or a wide area network ("WAN"), or can connect to an external computer (e.g., via the Internet provided by an Internet service provider).

[0019] Throughout this specification, references to "an embodiment," "embodiment," or similar language mean that a particular feature, structure, or characteristic described in connection with that embodiment is included in at least one embodiment. Therefore, unless explicitly stated otherwise, the phrases "in an embodiment," "in an embodiment," and similar language throughout this specification may, but do not necessarily all refer to the same embodiment, but rather mean "one or more, but not all, embodiments." Unless explicitly stated otherwise, the terms "comprising," "including," "having," and variations thereof mean "including, but not limited to,". Unless explicitly stated otherwise, the list of enumerated items does not imply that any or all of the items are mutually exclusive. Unless explicitly stated otherwise, the terms "a," "an," and "the" also mean "one or more".

[0020] Furthermore, the features, structures, or characteristics of the described embodiments can be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selection, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of the embodiments. However, those skilled in the art will recognize that the embodiments can be practiced without one or more specific details or using other methods, components, materials, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the embodiments.

[0021] The following description of aspects of embodiments is based on schematic flowcharts and / or schematic block diagrams of methods, apparatus, systems, and program products according to embodiments. It will be understood that each block of the schematic flowcharts and / or schematic block diagrams, and combinations of blocks in the schematic flowcharts and / or schematic block diagrams, can be implemented by code. The code can be provided to a processor of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to generate machinery, such that instructions executable via the processor of the computer or other programmable data processing apparatus create means for implementing the functions / actions specified in the blocks or blocks of the schematic flowcharts and / or schematic block diagrams.

[0022] The code can also be stored in a storage device that can instruct a computer, other programmable data processing device or other device to operate in a particular manner, such that the instructions stored in the storage device produce an article of art including instructions that implement the functions / actions specified in the schematic flowchart and / or schematic block diagram boxes or blocks.

[0023] The code may also be loaded onto a computer, other programmable data processing apparatus or other device to cause a series of operational steps to be executed on the computer, other programmable apparatus or other device to produce a computer-implemented process, such that the code executing on the computer or other programmable apparatus provides a process for implementing the function / action specified in the flowchart and / or block diagram boxes or boxes.

[0024] The schematic flowcharts and / or schematic block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of apparatus, systems, methods, and program products according to various embodiments. In this regard, each block in the schematic flowcharts and / or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions for implementing a specified logical function.

[0025] It should also be noted that in some alternative implementations, the functions indicated in the boxes may not occur in the order shown in the figures. For example, depending on the functions involved, two consecutively shown boxes may actually be executed substantially simultaneously, or these boxes may sometimes be executed in reverse order. Other steps and methods that are functionally, logically, or effectively equivalent to one or more boxes or portions thereof in the illustrated figures are conceivable.

[0026] While various arrow and line types may be employed in flowcharts and / or block diagrams, understanding them does not limit the scope of the corresponding embodiments. In fact, some arrows or other connectors may be used solely to indicate the logical flow of the depicted embodiments. For example, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of a depicted embodiment. It will also be noted that each block in a block diagram and / or flowchart, and combinations of blocks in block diagrams and / or flowcharts, can be implemented by a dedicated hardware-based system or by a combination of dedicated hardware and code that performs a specific function or action.

[0027] The description of elements in each figure may refer to elements in the figure in progress. In all figures, the same reference numerals refer to the same elements, including alternative embodiments of the same elements.

[0028] Figure 1 An embodiment of a wireless communication system 100 for power control using at least one power control parameter is depicted. In one embodiment, the wireless communication system 100 includes a remote unit 102 and a network unit 104. Although Figure 1 A specific number of remote units 102 and network units 104 are depicted, but those skilled in the art will recognize that any number of remote units 102 and network units 104 can be included in the wireless communication system 100.

[0029] In one embodiment, remote unit 102 may include computing devices such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smartphones, smart TVs (e.g., internet-connected televisions), set-top boxes, game consoles, security systems (including security cameras), in-vehicle computers, network devices (e.g., routers, switches, modems), aircraft, drones, etc. In some embodiments, remote unit 102 includes wearable devices such as smartwatches, fitness bands, optical head-mounted displays, etc. Furthermore, remote unit 102 may be referred to as a subscriber unit, mobile device, mobile station, user, terminal, mobile terminal, fixed terminal, subscriber station, UE, user terminal, device, or other terms used in the art. Remote unit 102 may communicate directly with one or more network units 104 via UL communication signals. In some embodiments, remote unit 102 may communicate directly with other remote units 102 via sidelink communication.

[0030] Network unit 104 may be distributed across a geographical area. In some embodiments, network unit 104 may also be referred to as an access point, access terminal, base station, base station, node B, eNB, gNB, home node B, relay node, device, core network, air server, wireless access node, AP, NR, network entity, AMF, UDM, UDR, UDM / UDR, PCF, RAN, NSSF, AS, NEF, key management server, KMF, or any other term used in the art. Network unit 104 is typically part of a radio access network that includes one or more controllers communicatively coupled to one or more corresponding network units 104. The radio access network is typically communicatively coupled to one or more core networks, which may be coupled to other networks such as the Internet and the public switched telephone network, etc. These and other elements of the radio access and core networks are not illustrated but are generally well known to those skilled in the art.

[0031] In one implementation, the wireless communication system 100 conforms to the standardized NR protocol in 3GPP, wherein network unit 104 transmits over DL using an OFDM modulation scheme, and remote unit 102 transmits over UL using an SC-FDMA scheme or an OFDM scheme. However, more generally, the wireless communication system 100 may implement other open or proprietary communication protocols, such as WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants, CDMA2000, Bluetooth®, ZigBee, Sigfoxx, and other protocols. This disclosure is not intended to limit implementation to any particular wireless communication system architecture or protocol.

[0032] Network unit 104 can serve multiple remote units 102 within a service area, such as a cell or cell sector, via a wireless communication link. Network unit 104 transmits DL communication signals to serve remote units 102 in the time, frequency, and / or spatial domains.

[0033] In various embodiments, remote unit 102 and / or network unit 104 may receive configuration information at a first device including power offset values ​​associated with a first plurality of resources and a first reference signal. In some embodiments, remote unit 102 and / or network unit 104 may receive a first reference signal from a second device. In some embodiments, remote unit 102 and / or network unit 104 may perform a first measurement on the first reference signal. In various embodiments, remote unit 102 and / or network unit 104 may calculate a first expected received power value based on the first measurement and the power offset value. In some embodiments, remote unit 102 and / or network unit 104 may calculate a first target received power value. In some embodiments, remote unit 102 and / or network unit 104 may transmit at least one downlink power control parameter to the second device based on the first target received power value and the first expected received power value. Therefore, remote unit 102 and / or network unit 104 may be used for power control using at least one power control parameter.

[0034] In various embodiments, remote unit 102 and / or network unit 104 may receive a first reference signal from a second device at a first device. In some embodiments, remote unit 102 and / or network unit 104 may perform a first measurement on the first reference signal. In some embodiments, remote unit 102 and / or network unit 104 may calculate a first expected received power value associated with a first plurality of resources based on the first measurement. In various embodiments, remote unit 102 and / or network unit 104 may calculate a first target received power value. In some embodiments, remote unit 102 and / or network unit 104 may transmit at least one downlink power control parameter to the second device based on the first target received power value and the first expected received power value. Therefore, remote unit 102 and / or network unit 104 may be used for power control using at least one power control parameter.

[0035] Figure 2An embodiment of a device 200 that can be used for power control using at least one power control parameter is depicted. The device 200 includes one embodiment of a remote unit 102. Furthermore, the remote unit 102 may include a processor 202, a memory 204, an input device 206, a display 208, a transmitter 210, and a receiver 212. In some embodiments, the input device 206 and the display 208 are combined into a single device, such as a touchscreen. In some embodiments, the remote unit 102 may not include any input device 206 and / or the display 208. In various embodiments, the remote unit 102 may include one or more of the processor 202, memory 204, transmitter 210, and receiver 212, and may not include the input device 206 and / or the display 208.

[0036] In one embodiment, processor 202 may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, processor 202 may be a microcontroller, microprocessor, central processing unit (“CPU”), graphics processing unit (“GPU”), auxiliary processing unit, field-programmable gate array (“FPGA”), or similar programmable controller. In some embodiments, processor 202 executes instructions stored in memory 204 to perform the methods and routines described herein. Processor 202 is communicatively coupled to memory 204, input device 206, display 208, transmitter 210, and receiver 212.

[0037] In one embodiment, memory 204 is a computer-readable storage medium. In some embodiments, memory 204 includes volatile computer storage media. For example, memory 204 may include RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and / or static RAM (“SRAM”). In some embodiments, memory 204 includes non-volatile computer storage media. For example, memory 204 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 204 includes both volatile and non-volatile computer storage media. In some embodiments, memory 204 also stores program code and associated data, such as an operating system or other controller algorithms operating on remote unit 102.

[0038] In one embodiment, input device 206 may include any known computer input device, including a touchpad, button, keyboard, stylus, microphone, etc. In some embodiments, input device 206 may be integrated with display 208, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, input device 206 includes a touchscreen, allowing text to be entered using a virtual keyboard displayed on the touchscreen and / or by handwriting on the touchscreen. In some embodiments, input device 206 includes two or more different devices such as a keyboard and a touchpad.

[0039] In one embodiment, display 208 may include any known electronically controllable display or display device. Display 208 may be designed to output visual, auditory, and / or tactile signals. In some embodiments, display 208 includes an electronic display capable of outputting visual data to a user. For example, display 208 may include, but is not limited to, LCD displays, LED displays, OLED displays, projectors, or similar display devices capable of outputting images, text, etc., to a user. As another non-limiting example, display 208 may include wearable displays such as smartwatches, smart glasses, head-up displays, etc. Furthermore, display 208 may be a component of a smartphone, personal digital assistant, television, desktop computer, laptop computer, personal computer, vehicle dashboard, etc.

[0040] In some embodiments, display 208 includes one or more speakers for generating sound. For example, display 208 may generate an audible alarm or notification (e.g., a beep or ringtone). In some embodiments, display 208 includes one or more haptic devices for generating vibration, motion, or other haptic feedback. In some embodiments, all or part of display 208 may be integrated with input device 206. For example, input device 206 and display 208 may form a touchscreen or similar touch-sensitive display. In other embodiments, display 208 may be positioned near input device 206.

[0041] In some embodiments, receiver 212 may: receive configuration information including power offset values ​​associated with a first plurality of resources and a first reference signal; and receive the first reference signal from a second device. In various embodiments, processor 202 may: perform a first measurement on the first reference signal; calculate a first expected received power value based on the first measurement and the power offset value; and calculate a first target received power value. In some embodiments, transmitter 210 may transmit at least one downlink power control parameter to the second device based on the first target received power value and the first expected received power value.

[0042] In various embodiments, receiver 212 may receive a first reference signal from the second device. In various embodiments, processor 202 may: perform a first measurement on the first reference signal; calculate a first expected received power value associated with a first plurality of resources based on the first measurement; and calculate a first target received power value. In some embodiments, transmitter 210 may transmit at least one downlink power control parameter to the second device based on the first target received power value and the first expected received power value.

[0043] Although only one transmitter 210 and one receiver 212 are illustrated, the remote unit 102 can have any suitable number of transmitters 210 and receivers 212. The transmitters 210 and receivers 212 can be of any suitable type. In one embodiment, the transmitters 210 and receivers 212 can be part of a transceiver.

[0044] Figure 3 An embodiment of a device 300 that can be used for power control using at least one power control parameter is depicted. The device 300 includes one embodiment of a network unit 104. Furthermore, the network unit 104 may include a processor 302, a memory 304, an input device 306, a display 308, a transmitter 310, and a receiver 312. As will be understood, the processor 302, memory 304, input device 306, display 308, transmitter 310, and receiver 312 may be substantially similar to the processor 202, memory 204, input device 206, display 208, transmitter 210, and receiver 212 of the remote unit 102, respectively.

[0045] In some embodiments, receiver 312 may: receive configuration information including power offset values ​​associated with a first plurality of resources and a first reference signal; and receive the first reference signal from a second device. In various embodiments, processor 302 may: perform a first measurement on the first reference signal; calculate a first expected received power value based on the first measurement and the power offset value; and calculate a first target received power value. In some embodiments, transmitter 310 may transmit at least one downlink power control parameter to the second device based on the first target received power value and the first expected received power value.

[0046] In various embodiments, receiver 312 may receive a first reference signal from the second device. In various embodiments, processor 302 may: perform a first measurement on the first reference signal; calculate a first expected received power value associated with a first plurality of resources based on the first measurement; and calculate a first target received power value. In some embodiments, transmitter 310 may transmit at least one downlink power control parameter to the second device based on the first target received power value and the first expected received power value.

[0047] In some embodiments, the IAB may not be limited to a specific multiplexing and duplex scheme, but may focus on TDM between uplink communication (e.g., uplink communication with the parent IAB node and / or the host) and downlink communication (e.g., downlink communication with the child IAB node or the UE).

[0048] In some embodiments, power control issues can arise if uplink and downlink transmissions are not always scheduled in separate time intervals, particularly when uplink and downlink communications share RF and antenna hardware. In various embodiments, the IAB node may undergo power control in the uplink, similar to uplink power control for the UE, but the IAB node may not perform power control in the downlink. If the IAB node intends to use the same RF chain and antenna panel for both uplink and downlink transmissions simultaneously, these two types of communication may suffer from imbalance. Similar problems may arise if the IAB node receives both uplink and downlink signals simultaneously. Various systems and methods for enhancing power control in IAB systems are described herein.

[0049] In some embodiments, such as uplink power control in NR, two types of uplink power control can be used: 1) closed-loop power control, which is implemented by receiving signals from a transmitter (e.g., the UE) and sending TPC feedback to the transmitter; and 2) open-loop power control, which is used for initial access. For open-loop power control, the UE receives a synchronization signal from which it can estimate path loss, and system information from which it can obtain information about the target received power. From the path loss and the target received power, the UE can calculate its transmission power for PRACH transmission.

[0050] In some embodiments, power control for transmissions on the PUSCH can be as follows:

[0051] The variables are defined in Table 1: Table 1

[0052] In addition, the following items are further defined: 1) 1) Basic open-loop power control with fractional path loss compensation; 2) ,in It is the number of information bits in the PUSCH normalized by the number of REs used for transmission (excluding DM-RS REs, etc.), and for PUSCHs containing data. However, for the Level 1 PUSCH containing control (UCI), it can be set to other values. In fact, Set the transmission power to 80% of the Shannon capacity. The value is non-zero only for single-layer transmission. It can be disabled. For example, it should be disabled when using fractional path loss compensation; 3) Beam index q , j , l Corresponding to different SRI values ​​and enabling beam-based power control: q Different values ​​of path loss are allowed for different beams. j Allow open-loop power control parameters as shown in Table 2 Different values, and l Two values ​​are allowed for use in a closed-loop process.

[0053] Table 2

[0054] For transmissions on PUCCH, α is always equal to 1 (e.g., path loss compensation for PUCCH is never a fraction).

[0055] In various embodiments, the MT, as part of the IAB node, behaves similarly to the UE, and therefore, for uplink communication with the DU of its serving cell, it can undergo a similar power control process.

[0056] Figure 4 This diagram illustrates one embodiment of an IAB system 400. The IAB system 400 includes a network 402 (e.g., a core network) that communicates with an IAB host 404 via a first communication link 406. Furthermore, the IAB system 400 includes a first UE 408 that communicates with the IAB host 404 via a second communication link 410. Further, the IAB system 400 includes a first IAB node 412 that communicates with the IAB host 404 via a third communication link 414. The IAB system 400 also includes a second UE 416 that communicates with the first IAB node 412 via a fourth communication link 418. Additionally, the IAB system 400 includes a second IAB node 420 that communicates with the first IAB node 412 via a fifth communication link 422. Further, the IAB system 400 includes a third UE 424 that communicates with the second IAB node 420 via a sixth communication link 426.

[0057] As illustrated in further detail, network 426 is connected to IAB host 404 via a backhaul link 428, which can be wired. IAB host 404 includes CU 430 and DU 432. IAB host 404 communicates with all DUs in the system via an F1 interface. Each IAB node (e.g., 412 and 420) is functionally divided into at least MTs (e.g., 434, 436) and DUs (e.g., 438, 440). The MTs of IAB nodes are connected to the DUs of a parent node, which can be another IAB node or IAB host 404.

[0058] The connection between the MT of an IAB node and the DU of its parent node (e.g., 414, 422, 426, 442, 444) is called a radio backhaul link. In a radio backhaul link, the MT is functionally similar to a UE and the DU of the parent node is similar to a base station in a conventional cellular radio link. Therefore, the link from the MT to the serving cell of the DU, which is the parent link, is called an uplink, and the link in the reverse direction is called a downlink. In this disclosure, embodiments may simply refer to uplinks or downlinks between IAB nodes, links between a node and its parent, links between a node and its child, etc., without direct reference to the MT, DU, serving cell, etc.

[0059] Each IAB host or IAB node can serve the UE (e.g., 446) via an access link (e.g., 448). IAB systems like IAB system 400 can be designed to enable multi-hop communication (e.g., the UE can connect to the core network via the access link between the IAB node and the IAB host, and multiple backhaul links). As used herein, unless otherwise stated, "IAB node" can generally refer to either an IAB node or an IAB host, provided it does not involve a connection between the CU and the core network.

[0060] Nodes and links closer to the IAB host and / or core network can be called upstream nodes and links. For example, the parent node of a master node is an upstream node of the master node, and the link to the parent node is an upstream link relative to the master node. Similarly, nodes and links farther from the IAB host and / or core network are called downstream nodes and links. For example, the child nodes of a master node are downstream nodes of the master node, and the link to the child node is a downstream link relative to the master node.

[0061] Table 3 summarizes the terminology used in this paper.

[0062] Table 3

[0063] This paper describes various systems and methods for power control in IAB systems to promote higher performance in terms of resource efficiency, multi-hop latency, complexity, and other aspects.

[0064] In some embodiments, the IAB network can be connected to the core network through one or more IAB hosts. Each IAB node can be connected to an IAB host and / or other IAB nodes via a wireless backhaul link. Each IAB host and / or node can also serve the UE.

[0065] Figure 5 This is a diagram illustrating another embodiment of IAB system 500. IAB system 500 includes an IAB network 502 and an IAB host 504 (e.g., a parent IAB node) connected via a first backhaul link 506. IAB system 500 includes a first UE 508 connected to IAB host 504 via a second backhaul link 510. Furthermore, IAB system 500 includes a first IAB node 512 (e.g., a single-panel node) connected to IAB host 504 via a third backhaul link 514. Furthermore, IAB system 500 includes a second IAB node 516 (e.g., a multi-panel node) connected to IAB host 504 via a fourth backhaul link 518. IAB system 500 includes a third IAB node 520 (e.g., a child IAB node) connected to second IAB node 516 via a fifth backhaul link 522. Furthermore, IAB system 500 includes a second UE 524 connected to second IAB node 516 via a sixth backhaul link 526. In addition, IAB system 500 includes a fourth IAB node 528 (e.g., a sub-IAB node) connected to the first IAB node 512 via a seventh backhaul link 530. IAB system 500 also includes a third UE 532 connected to the first IAB node 512 via an eighth backhaul link 534.

[0066] In some embodiments, various options may exist regarding the structure, multiplexing capabilities, and / or duplex capabilities of the IAB node. For example, each IAB node may have one or more antenna panels, each antenna panel being connected to the baseband unit via an RF chain. One or more antenna panels may be able to serve the entire area of ​​interest near the IAB node, or each antenna panel or group of antenna panels may provide partial coverage, such as within a sector. An IAB node having multiple antenna panels, each serving a separate area or sector, may be referred to as a single-panel IAB node, as it behaves similarly to a single-panel IAB node used for communication in each separate area or sector.

[0067] In some embodiments, the antenna panels of an IAB node with multiple antenna panels can be HD, meaning that the antenna panels are capable of transmitting or receiving signals in the frequency band at a certain time; or the antenna panels of an IAB node can be FD, meaning that the antenna panels are capable of both transmitting and receiving signals in the frequency band simultaneously. Unlike FD radio, HD radio can be widely implemented and used in practice, and HD radio can be assumed to be the default operating mode in wireless systems.

[0068] Table 4 lists different duplex scenarios that can be used in multiplexing scenarios that are not limited to TDM. In Table 4, IAB Node 1 (N1) is a single-panel IAB node; IAB Node 2 (N2) is a multi-panel IAB node; SDM refers to simultaneous transmission or reception on the downlink (or downstream) and uplink (or upstream); FD refers to simultaneous transmission and reception by the same antenna panel in the same frequency band; and MPTR refers to simultaneous transmission and reception by multiple antenna panels, where each antenna panel transmits or receives in the frequency band at a time.

[0069] Table 4

[0070] For example, consider scenario S1 where a single-panel IAB node N1 receives both downlink and uplink signals. The downlink signal can appear on the backhaul link from the IAB host or parent IAB node. The uplink signal can be received on the access link from UE1, on the backhaul link from child IAB node 1 (CN1), or both. The uplink signal can be power-controlled, allowing multiple UEs and / or child nodes to transmit signals to the node simultaneously. However, the downlink signal may not be power-controlled, which can create a significant power imbalance between the received power at the host node. This power imbalance can interfere with weaker signals to the point that they cannot be decoded. In various embodiments, downlink power control may be provided.

[0071] Figure 6This is a diagram illustrating yet another embodiment of IAB system 600. IAB system 600 includes an IAB network 602 and a parent node 604 connected via a first backhaul link 606. Furthermore, IAB system 600 includes a sibling node 608 connected to the parent node 604 via a second backhaul link 610. IAB system 600 includes a first UE 612 connected to the parent node 604 via a third backhaul link 614. Furthermore, IAB system 600 includes an IAB node 616 connected to the parent node 604 via a fourth backhaul link 618. IAB system 600 includes a first child node 620 connected to IAB node 616 via a fifth backhaul link 622. Furthermore, IAB system 600 includes a second child node 624 connected to IAB node 616 via a sixth backhaul link 626. Furthermore, IAB system 600 includes a second UE 628 connected to IAB node 616 via a seventh backhaul link 630. IAB system 600 includes a third UE 632 connected to IAB node 616 via an eighth backhaul link 634.

[0072] exist Figure 6 In this configuration, IAB node 616 (N) is connected to the core network via parent node 604 (PN), which can be another IAB node or an IAB host. Parent node 604 can serve other nodes, which can be referred to as sibling nodes (SN) of N (e.g., sibling node 608). IAB node 616 can serve child nodes such as first child node 620 (CN1) and second child node 624 (CN2), as well as user equipment such as third UE 632 (UE1) and second UE 628 (UE2). Each of the parent node, sibling node, and child node can serve other nodes or user equipment such as first UE 612 (UE0).

[0073] In some embodiments, the parent IAB node of the primary IAB node may adjust the transmission power used for communication on the resource set and notify the primary IAB node of the power adjustment via control signaling.

[0074] In some embodiments, the parent IAB node typically configures resource sets in the time and frequency domains in an aperiodic, semi-persistent, or periodic manner. Configuration can be sent via RRC signaling, but can also be communicated via MAC or physical layer signaling such as DCI. For example, semi-persistent configuration can be activated and / or deactivated via MAC signaling, or aperiodic configuration can be indicated via DCI messages.

[0075] In various embodiments, the information conveyed via configuration and / or other control signaling (e.g., including one or more configuration messages, referred to herein as Power Offset Resource Set (PORS) configuration) may include: 1) an ID for configuration; 2) a resource set: a) resources in time: time slots, symbols, periodicity of occurrence, etc.; b) resources in frequency: PRB, BWP, CC, etc.; 3) a power offset (e.g., relative to such as ss-PBCH-BlockPower, referenceSignalPower (which offsets powerControlOffsetSS from ss-PBCH-BlockPower), etc. (Reference power in dB), in one example, power offset can be a set of possible power offset values ​​or a series of power offset values ​​(e.g., minimum power offset, maximum power offset); 4) beam-based information (e.g., spatial QCL relative to the reference signal); and / or 5) the target received power from the parent node—the target received power at the IAB node (e.g., PSD per RE or RB in dBm can be considered similar to Po, which can be used for reference channels such as PDSCH and / or PDCCH or reference signals such as demodulated RS or CSI-RS, which can be expected for the IAB node to receive channels and / or signals within + / - X dB of the target received power level from the parent node).

[0076] In one embodiment, an IAB node may request a target receive power value for channel and / or signal reception from its parent node on a resource set or typically for any allocated resources. In such an embodiment, the IAB node may determine the target receive power based on measurements from its parent node (e.g., RSRP) and / or the target receive power settings for reception from the child node or UE to which the IAB is serving. The IAB node may transmit the requested target receive power on the PUSCH or PUCCH on the MT uplink (e.g., using higher-layer signaling such as MAC control elements). The IAB node may determine uplink power control parameters for the child node or UE based on the target receive power from its parent node.

[0077] After receiving the PORS configuration from the parent IAB node, the IAB node can schedule uplink transmissions for its own child IAB nodes and UEs based on their respective expected received power (RXP_exp).

[0078] Figure 7 This is a flowchart illustrating one embodiment of a method 700 for transmitting and / or receiving, including a PORS configuration.

[0079] Method 700 includes units 702-708 executed by a parent (e.g., upstream) node and units 710-724 executed by a principal (e.g., downstream) node.

[0080] In units 702-708 executed by the parent node, the parent node (PN) transmit 702 includes a PORS configuration of at least the time-frequency resource set T and power offset R_ofs. The PORS configuration may include indexes and / or references to reference signals such as SS / PBCH blocks or CSI-RS.

[0081] PN transmits the 704 reference signal while applying the reference power (TXP_ref). The reference signal is implicitly or explicitly associated with the PORS configuration (e.g., a relative power offset relative to the reference signal power) through higher-level parameters. This reference signal can be an SS / PBCH block or a CSI-RS. The reference signal can be transmitted periodically (e.g., transmission can occur before or after cell 702).

[0082] Next, PN transmitter 706 schedules signals and / or channels (C1) such as PDSCH on resources in resource set T.

[0083] Finally, PN transmits the 708 signal and / or channel C1 while applying transmit power TXP_ref and / or R_ofs.

[0084] In units 710-724 executed by the master node, the master node (N) receives 710 a PORS configuration including at least a time-frequency resource set T and a power offset R_ofs. The PORS configuration may include an index and / or reference to a reference signal such as an SS / PBCH block or CSI-RS.

[0085] N receives the 712 reference signal and measures the reference power (RXP_ref), which is typically equal to the transmit reference power (TXP_ref) attenuated by the communication channel. The reference signal is implicitly or explicitly associated with the PORS configuration (e.g., a relative power offset relative to the reference signal power) via higher-level parameters. This reference signal can be an SS / PBCH block or CSI-RS. The reference signal can be transmitted periodically (e.g., reception can occur before or after cell 710).

[0086] N calculates the first expected received power RXP_exp1 associated with resource set T as follows: RXP_ref / R_ofs.

[0087] Next, N receives 716 DCIs such as PDSCH signals and / or channels (C1) on resources in resource set T.

[0088] N also obtains a second expected received power RXP_exp2 associated with signals and / or channels (C2) from another node, such as a sub-node (CN) or a UE. N can obtain RXP_exp2 by performing measurements on communications from the CN and / or the UE—such as to SRS.

[0089] Then, N compares the two expected received powers RXP_exp1 and RXP_exp2 of 720.

[0090] If the ratio between these two values ​​exceeds a threshold Q, N may need to transmit 722 DCI signals to schedule signals and / or channels C2 from the CN and / or UE on resources that do not overlap with resource set T. Specifically, N may need to schedule C2 on separate time resources, resulting in a TDM approach. The threshold can depend on N's ability to handle power imbalances.

[0091] Otherwise, if the ratio does not exceed the threshold Q, N can transmit 724 DCIs to schedule C2s from the CN and / or UE on resources overlapping with the resource set. In particular, N can schedule C2s on overlapping time resources, which yields either an FDM or SDM approach.

[0092] Figure 8 This is a timing diagram 800 illustrating the timing corresponding to the transmit and / or receive times configured with respect to the PORS. Timing diagram 800 illustrates timing 802 corresponding to PN, timing 804 corresponding to N, timing 806 corresponding to the first child node (CN1), and timing 808 corresponding to the second child node (CN2). The first PORS (PORS 1) is configured with transmit opportunities 810, 814, and 818, while the second PORS (PORS 2) is configured with transmit opportunities 812 and 816. In transmit opportunity 812, PN transmits PDSCH transmission 820 to N as shown by directional transmission 822, and CN2 transmits PUSCH transmission 824 to N as shown by directional transmission 826. In transmit opportunity 814, PN transmits PDSCH transmission 828 to N as shown by directional transmission 830, and CN1 transmits PUSCH transmission 832 to N as shown by directional transmission 834.

[0093] In some embodiments, PORS 1 and PORS 2 are configured in a periodic or semi-persistent manner.

[0094] In various embodiments, PORS 1 provides a power offset from the PN to generate received power RXP1 in N. Similarly, in such embodiments, PORS 2 provides a power offset from the PN to generate received power RXP2 in N.

[0095] N expects the received power RXP_exp1 from its child IAB node CN1. The difference between RXP1 and RXP_exp1 can be less than a power imbalance threshold that N can tolerate. Similarly, N expects the received power RXP_exp2 from its child IAB node CN2. The difference between RXP2 and RXP_exp2 can be less than a power imbalance threshold that N can tolerate.

[0096] PN schedules PDSCH transmissions to N, which use resources from PORS 1 and PORS 2. After obtaining information on the power offsets of the resources applied to PORS 1 and PORS 2, N can schedule PUSCH transmissions for CN1 and CN2 in the resources associated with (or multiplexed with) PORS 1 and PORS 2, respectively.

[0097] In some embodiments, the PN may need to know which PORS configurations are relevant. If the PN does not have specific knowledge and configures generic PORS, resources may be wasted because the power offset does not match the expected power from either the CN or the UE.

[0098] In various embodiments, N can request to send a power offset request or receive a target power request, similar to a DL-PC request. However, in such embodiments, the request may not be specific to a particular transmission and may not need to be accepted immediately. Instead, after receiving a power offset request or a target power request from N and possibly its sibling IAB nodes (SN), PN can configure a new PORS or modify an existing PORS to accommodate each IAB node's need for enhanced full-duplex.

[0099] In some embodiments, N can send control signaling to PN to notify PN which PORS configurations are suitable for N. In mobile IAB systems, this information can change frequently and such updates can be sent periodically.

[0100] In some embodiments, the determination made by the principal node N may be about whether to schedule downstream communication with the child node or UE simultaneously with upstream communication with the parent node.

[0101] In various embodiments, based on DL RS measurements of the serving cell (e.g., PN), IAB node N can set uplink power control parameters for child nodes or UEs. Uplink power control parameters may include open-loop parameters and / or closed-loop parameters (e.g., P0, α, step size for TPC commands).

[0102] Figure 9 This is a flowchart 900 illustrating an embodiment of power control.

[0103] exist Figure 9In the process, IAB node N receives 902 a PORS configuration including resource set T and associated power offsets R_ofs. This configuration can be transmitted by the parent node (PN). Then, N receives 904 a reference signal such as an SS / PBCH block or CSI-RS and performs 906 a measurement M on that reference signal. After obtaining the result of measurement M, such as SSB-RSRP or CSI-RSRP, N calculates 908 the target received power RXP1 based on M and R_ofs. The calculated result can be the expected received power for communication on resource set T.

[0104] Next, N sets 910 for a second target received power RXP2 for another communication from a child node (CN) or UE. A constraint may exist whereby the ratio between RXP1 and RXP2, or the difference between RXP1 and RXP2 in decibels, must not exceed a threshold Q. This threshold may be set by a standard, configured by the network (e.g., semi-statically or dynamically indicated), or depend on the capabilities of N. The target received power can be described in terms of energy per resource element (EPRE), where a resource element (RE) is a resource cell in a time-frequency resource grid.

[0105] Finally, N sets uplink control parameters 912 to CN and / or UE. These uplink control parameters may include one or more sets of closed-loop power control parameters and / or open-loop power control parameters, such as P0, α, etc. CN and / or UE then use those parameters to communicate with N. Specifically, N may set uplink power control parameter P based on RXP2, and then N may transmit 914 P to another radio entity.

[0106] In various embodiments, uplink control parameters used by the CN and / or UE may be associated with a resource set in the downstream that overlaps with the resource set T in the upstream. In some embodiments, similar resource set configurations may be configured for both upstream and downstream links that include the same or similar resource sets but different power control parameters, such as: 1) the upstream configuration is a PORS configuration that includes power offset information; and / or 2) the downstream configuration includes uplink power control information.

[0107] In some embodiments, although the two configurations may be of different types, they may have similar relationships between parameters. For example, if the PORS configuration on resource set T1 indicates a power offset R1 relative to a reference signal, and another PORS configuration on resource set T2 indicates a power offset R2 relative to the same reference signal, then the associated uplink power control parameters (e.g., power spectral density offset) P1 and P2 for downstream communication may, for example, follow similar ratios, such as: 1) in a true measure: P1 / P2 = R1 / R2; or 2) in a dB measure: P1-P2 = R1-R2.

[0108] In some embodiments, the relationships between parameters can be maintained through implementation because the configuration is transmitted and received by different entities, but in other embodiments the relationships can be configured in a standard specification.

[0109] In one embodiment, the IAB node (N) can perform power control while receiving signals. This can occur when there is a significant imbalance between the power of the signals received from downstream nodes {CN1, CN2, UE1, UE2} and the power of the signals received from upstream node PN. The IAB node N can address this issue fully or partially by performing uplink power control together with {CN1, CN2, UE1, UE2}. However, if uplink power control alone fails to address the issue, N can send a power control request to PN to change its transmission power.

[0110] In various embodiments, N cannot tolerate power imbalances exceeding a threshold Q. For example, N can maintain P DL / P UL ≤ Q (and also P) UL / P DL ≤ Q) to decode the received signal, where P DL This represents the received power of the downlink signal received from PN, and P UL This represents the received power of the uplink signals received from {CN1, CN2, UE1, UE2}. The received power can be a normalized value such as the received power per RB or RE. A threshold Q can be applied to signals that are less than Δf apart in the frequency domain. Then, if P... DL / P UL If Q is true, then IAB node N can perform power control to increase uplink power and / or decrease downlink power.

[0111] In some embodiments, the IAB node N may be able to exert power control on the uplink signal to some extent. However, increasing the transmission power by {CN1, CN2, UE1, UE2} may be limited by node capabilities, radiation regulations, interference management considerations, etc. For example, N may be able to increase the uplink signal by a ratio R while requiring a ratio R UL , and R UL < R. Then, N may have the following options: 1) Option 1: Perform scheduling in a way that avoids FDM between the signals from PN and {CN1, CN2, UE1, UE2} in the frequency gap Δf; and 2) Option 2: Perform downlink power control to reduce the signal power from PN by at least R DL = R / R UL .

[0112] As can be understood, considering that the IAB system aims at efficient bandwidth utilization in ultra-dense deployments, Option 1 may be too restrictive. Therefore, N may send a power control request to PN to reduce the downlink power.

[0113] In various embodiments, the downlink power control (DL-PC) request may contain some or all of the following information: 1) Identification number (ID); 2) The expected value of the power change, e.g., the expected value of the power change by a ratio R DL —— this value can typically be described in decibels (dB) —— and in some embodiments, may include the maximum and minimum values of the power change; 3) The reference power if the transmission power is different for different downlink signals, e.g., if PN applies power P1 to signal and / or channel C1 and power P2 to transmit signal and / or channel C2, the DL-PC request may contain a reference to C1 or C2, examples of C1 and C2 are PDCCH, PDSCH, SS / PBCH block, CSI-RS, etc.; 4) The time information for applying the power change, e.g., the DL-PC request may contain a request to change the transmission power for a specific signal and / or channel, for a specific time interval, for the transmission until the next DL-PC signaling, etc.; 5) Frequency information, such as the sub-band of interest (e.g., the starting PRB and the number of PRBs); and / or 6) Spatial information, e.g., information about a specific beam, and the DL-PC request may refer to the beam through a beam index such as CRI or a QCL reference to signals and / or channels such as PDCCH, PDSCH, SSB / PBCH block, etc.

[0114] In some embodiments, PN serves multiple nodes simultaneously, and it can also communicate with its own parent node. Therefore, a DL-PC request may or may not be accepted. Thus, PN can send a DL-PC response to N to inform it whether the DL-PC request can be accepted and how it can be accepted. The DL-PC response may contain one or more of the following information: 1) an identifier (ID), possibly referring to the DL-PC request ID; 2) whether the DL-PC request is permitted; 3) a permitted value for power variation, such as a ratio R. DL —This value can be described in decibels (dB) and can be equal to or close to the expected value contained in the DL-PC request—In one embodiment, a value between the minimum and maximum request values ​​can be selected; 4) Timing information for applying power changes, for example, the DL-PC response may include references to a signal and / or channel, a time interval, the transmission thereafter until the next DL-PC signaling, etc.; 5) Frequency information, such as sub-bands (e.g., the starting PRB and the number of PRBs); and / or 6) Spatial information, such as information about a specific beam. The DL-PC response may reference the beam by a beam index such as CRI or by QCL references to signals and / or channels such as PDCCH, PDSCH, SSB / PBCH blocks, etc.

[0115] In some embodiments, IAB node N can schedule uplink signals based on information in the DL-PC response (or its absence). For example, N can allow downlink signals to only pass through with sufficient power—e.g., through a power level not lower than P. UL ≥ QP DL The power of the received uplink signal is the FDM between the received signals. In various embodiments, if the threshold Q is applied only to frequency gaps less than the value Δf, then N can allow a gap of at least Δf if the expected received power ratio exceeds Q.

[0116] Figure 10 This is a flowchart 1000 illustrating an embodiment of issuing a DL-PC license from a (upstream) IAB node.

[0117] The parent node (PN) transmits a 1002 signal and / or channel C1 to the IAB node N, while PN applies transmission power TXP for this transmission.

[0118] Next, PN transmits 1004 DCI to N, which is scheduling the second signal and / or channel C2.

[0119] Then, PN may optionally receive a 1006 DL-PC request from N to reduce the transmission power of C2 relative to the transmission power of C1 by (at least) a ratio R.

[0120] If a DL-PC request is received, PN can attempt to set a new transmission power TXP_new for C2 by setting 1008 TXP_new := Max {TXP / R,TXP_min}. However, other constraints such as those for other concurrent transmissions can constrain power reduction by minimizing TXP_min.

[0121] Next, PN can transmit a 1010 DL-PC response to notify N that the power reduction of R_g is permitted, where R_g:= TXP / TXP_new.

[0122] In some embodiments, the PN can emit a DL-PC response that rejects power changes.

[0123] PN sets the transmit power TXP to a new value by setting 1012 TXP := TXP_new.

[0124] Finally, PN transmits the 1014 signal and / or channel C2 while applying the transmission power TXP.

[0125] Figure 11 This is a flowchart 1100 illustrating an embodiment of a request (downstream) IAB node to transmit and receive DL-PC licenses.

[0126] IAB node N receives the 1102 signal and / or channel C1 from its parent node (PN) using the received power RXP. Received power is the transmission power attenuated by the communication channel and other losses.

[0127] Next, N receives the second scheduling signal 1104 and / or the DCI of channel C2 from PN.

[0128] Furthermore, N can receive 1106 SR and / or BSR from the UE or sub-node (CN) to obtain an uplink signal with the expected receive power RXP_exp. In some embodiments, N may want to (e.g., by employing FDM) receive the uplink signal from the UE and / or CN simultaneously with receive C2. However, the expected receive power from the UE and / or CN may be constrained by RXP_exp.

[0129] IAB node N can check whether the power imbalance obtained from 1108 exceeds a threshold Q (e.g., RXP / RXP_exp > Q). If so, N can initiate downlink power control signaling. Otherwise, N can continue to schedule C2 and uplink signals simultaneously. N can also perform uplink power control.

[0130] To perform downlink power control, N can transmit an 1110 DL-PC request to PN to reduce the transmit power of C2 relative to the transmit power of C1 by a requested power reduction ratio R (e.g., R ≥ RXP / (RXP_exp. Q)). The requested power reduction ratio can be targeted at at least a receive power ratio less than a threshold Q.

[0131] Then, N can receive a DL-PC response (e.g., DL-PC license) from PN for the power reduction ratio of 1112 license R_g.

[0132] Next, N compares the permitted power reduction R_g with the minimum value that satisfies the power ratio constraint (e.g., R_g ≥ RXP / (RXP_exp. Q))1114.

[0133] If the constraints are not met, N can schedule uplink signals on resources that do not overlap with C2 in the time domain and can receive 1116 C2 and uplink signals and / or channels in TDM.

[0134] If the constraints are met, N may have the option to schedule uplink signals on resources that overlap with C2 in the time domain and may receive 1118 C2 and uplink signals and / or channels in SDM and / or FDM.

[0135] Figure 12 This is timing diagram 1200, which illustrates the timing corresponding to DL-PC requests and DL-PC licenses. Timing diagram 1200 illustrates timing 1202 corresponding to the parent IAB node (PN), timing 1204 corresponding to the IAB node (N), and timing 1206 corresponding to the child node (CN).

[0136] First, PN uses DCI 1210 transmitted to N to schedule PDSCH 1208 transmission. Then, N sends DL-PC request 1212 to PN to obtain changes in its downlink power for transmission. PN authorizes this request by sending DL-PC license message 1214 to N. After receiving DL-PC license message 1214, N can use DCI 1218 to schedule PUSCH transmission 1216, which is frequency-domain multiplexed with PDSCH 1208, for CN.

[0137] As can be understood, the advantage of the PORS method over the DL-PC request-license method is that there is no need for signaling between the scheduling of PDSCH and PUSCH. In fact, since N has already obtained information through the PORS configuration, N can refer to the latest power measurement results from PN, the power measurement results from CN1 and / or CN2, and reference powers (e.g., ss-PBCH-BlockPower, referenceSignalPower, etc.) to schedule PUSCH that is frequency and / or spatially multiplexed with PDSCH.

[0138] However, the PORS method and the DL-PC request-license method can be similar. For example, for the PORS method, consider the following: 1) PN configures PORS in an aperiodic manner and schedules PDSCH to N in PORS; 2) N recognizes that if PORS takes a different power offset, it can be FDMed on PUSCH transmissions from CN, and then it sends a power offset request to PN; 3) PN then updates the power offset of PORS by sending control signaling to N; and 4) After the update has been received, N schedules PUSCH for CN on time resources that overlap with the time resources of PDSCH. A similar process can be followed for the DL-PC request-license method.

[0139] In various embodiments, the parent IAB node PN can exchange DL-PC control signaling with the IAB node N to adjust the downlink transmission power used for transmissions to N. Power adjustment and the information exchanged via control signaling can facilitate duplex enhancement for N.

[0140] In some embodiments, uplink signaling can be used to notify the parent node of preferred power adjustments to enable simultaneous reception of downlink and uplink signals. Uplink signaling may be referred to as a power offset request, target receive power request, and / or DL-PC request.

[0141] In some embodiments, a power offset request or DL-PC request may be generated based on the implementation (e.g., the subject node may estimate the expected received power RXP_exp from the CN and / or UE based on measurements of any signal or combination of signals from the CN and / or UE).

[0142] In various embodiments, the method for obtaining RXP_exp can be specified by the standard. For example, RXP_exp can be set to any one or a combination of the following: 1) the latest received power of PUCCH (e.g., the latest RSRP of DMRS in the latest PUCCH transmission from the CN and / or UE); 2) the latest received power of PUSCH (e.g., the latest RSRP of DMRS in the latest PUSCH transmission from the CN and / or UE); and / or 3) the RSRP of SRS from the CN and / or UE.

[0143] In some embodiments, the latest received power or RSRP can be specified as being associated with a specific beam or QCL parameter, particularly in frequency range 2 (FR2). In some embodiments, uplink signaling can be carried by RRC, MAC, and / or physical layer signaling such as UCI.

[0144] In various embodiments, a power offset request may be associated with a PORS configuration. In some embodiments, a subject node may request a power offset from a parent node without referencing a PORS configuration. The request message may include a desired power offset value or a series of power offset values ​​relative to a reference power. The reference power may be indicated implicitly or explicitly. For implicit indication, a standard or prior configuration may determine the downlink reference power of the RSRP, such as an SS / PBCH block or CSI-RS, as a reference. Another example of implicit indication may be an implicit reference to the power received from the latest downlink channel. For explicit indication, the request message may include a reference (e.g., an index) to a downlink reference signal, such as an SS / PBCH block or CSI-RS. In some embodiments, a subject node may request a change in the power offset for a specific PORS configuration. In such embodiments, the request message may include a reference (e.g., an index) to an existing PORS configuration.

[0145] In some embodiments, DL-PC requests may not refer to a specific channel or resource set. In such embodiments, any such request may be rejected (e.g., at the discretion of the parent node).

[0146] In some embodiments, downlink signaling can be used to notify the principal node of an upcoming power adjustment (e.g., in response to earlier uplink signaling). Downlink signaling can be PORS configuration or DL-PC licensing.

[0147] In various embodiments, PORS configuration updates or DL-PC licenses performed by the PN can be generated based on the implementation (e.g., depending on multiple power offset requests or DL-PC requests received by the PN, transmission power limits, regulatory constraints, etc.). In some embodiments, power control requests may not be admitted (e.g., due to conflicting requests in ultra-dense deployments), and the decision about which requests to license may depend on the implementation.

[0148] In some embodiments, the determination of which requests are accepted can be specified in standard documentation. For example, if a power control request is received in the uplink, QoS specifications, higher-layer signaling, etc., can delegate the behavior of the parent node. In another example, low-latency services and / or wireless backhaul services may be prioritized and may require acceptance of service-related power offset requests or DL-PC requests based on higher-layer specification requirements and / or higher-layer signaling.

[0149] In various embodiments, IAB nodes may be able to provide power control capabilities to the rest of the network. For example, an IAB node may send information to its parent node about its ability to receive unbalanced signals. Each piece of information may indicate, for example, the minimum frequency gap Δf in Hertz or PRB, and the associated maximum power ratio Q in decibels (dB). The IE containing the capability information may include tables, such as those similar to Table 5.

[0150] Table 5

[0151] In some embodiments, the IAB node capabilities for power control may include: 1) the number of panels; and / or 2) the maximum number of PORS configurations or the maximum number of DL-PC processes.

[0152] In various embodiments, information elements containing capability information can be transmitted via higher-level signaling—for example, via RRC messages (e.g., automatically at connection time or via request-response signaling)—with the remainder of the IAB system and / or network. Capability information can be used by implementation, configuration, or specification.

[0153] In some embodiments, downlink power control in certain time slots or symbols may be subject to power constraints allocated to the signals and / or channels scheduled in those time slots or symbols. For example, synchronization signals may be transmitted with a fixed power that cannot be dynamically changed. In another example, periodic CSI-RS may exist for RLM and RRM. In these examples, because the transmit power cannot be dynamically changed, large power adjustments to other signals and / or channels may not be accepted by the parent node.

[0154] In some embodiments, one or more of the following rules may be specified by the standard and / or otherwise implemented: 1) PORS cannot be configured on slots and / or symbols containing SS / PBCH blocks, periodic CSI-RS, etc.; 2) PORS configuration on slots and / or symbols containing SS / PBCH blocks, periodic CSI-RS, etc. may be ignored; 3) Power offset in PORS configuration on slots and / or symbols containing SS / PBCH blocks, periodic CSI-RS, etc. is constrained by a ratio Q relative to SSB-RSRP, CSI-RSRP, etc.; 4) PORS configuration on slots and / or symbols containing SS / PBCH blocks, periodic CSI-RS, etc. 5) Power offset requests can be ignored or assumed invalid by any node of interest; 6) DL-PC requests for channels on slots and / or symbols containing SS / PBCH blocks, periodic CSI-RS, etc., can be ignored or assumed invalid by any node of interest; 7) If a PORS or channel includes any slot and / or symbol containing SS / PBCH blocks, periodic CSI-RS, etc., the rule can apply to the entire PORS or channel; and / or 7) The rule can apply not only in the case where SS / PBCH blocks, periodic CSI-RS, etc. are in the current BWP and / or CC, but also in another BWP and / or CC—for example, in the case of in-band carrier aggregation.

[0155] In various embodiments, a multi-hop scenario N1-N2-N3-N4 can exist, where: N1 is the parent node of N2; N2 is the parent node of N3; N3 is the parent node of N4; and N4 can be a child node or a UE. In such embodiments, it is assumed that N2 sends a PORS configuration to N3, enabling N3 to enjoy simultaneous communication with both N2 and N4. However, N2 can be a child node of N1 and therefore it must comply with the uplink TPC commands provided by N1. Furthermore, N2 may also be subject to power constraints for transmission, such as: 1) the power ratio between simultaneous uplink and downlink transmissions to N1 and N3 respectively may not exceed a threshold that can be determined by standards or by the hardware capabilities of N2; and / or 2) hardware and / or regulatory constraints apply to the maximum transmission power of N2, which is the sum of the transmission power in the uplink (to N1) and downlink (to N3) directions. Therefore, TPC commands from N1 can cause conflicts with PORS configurations from N2.

[0156] In some embodiments, the following may apply: 1) N2 can remove the PORS configuration to avoid power imbalance conflicts—N2 can send a message to N3 to notify it that the PORS configuration is no longer valid—in one embodiment, the PORS configuration may have an expiration time, after which N3 may assume the configuration is no longer valid; 2) N2 can update the PORS configuration to avoid power imbalance conflicts—specifically, N2 can send a message to N3 to update the power offset value of the PORS or replace the PORS configuration with a new PORS configuration—the new power offset can then allow power transmission in the uplink and downlink without imposing a large imbalance at N2; 3) N2 can avoid scheduling downlink transmissions on the PORS as long as a conflict exists—therefore, if the PORS configuration is not used for a period of time, N3 may assume the configuration has expired—expiration The time period can be set by standard or configuration; 4) It can enable N2 to apply partial power compensation to avoid conflicts, for example, it can enable N2 to deviate from the transmission power in the uplink (e.g., determined by a TPC command from N1) and / or the transmission power in the downlink (e.g., determined by PORS configuration) by a certain amount; 5) N2 can send a control message to N1 notifying it of the constraints to comply with the TPC command - this control message can be, for example, a PHR - where N2 generates a PHR based on the ratio between transmit power and power constraints according to PORS configuration, hardware and regulatory restrictions, etc., the report can be a MAC layer message and can be triggered and generated according to RRC configuration; and / or 6) N2 can fully or partially share PORS configuration information with N1 and associate power constraint reports such as PHR with the PORS configuration.

[0157] It should be noted that problems may arise due to mobility or any other factors that alter the channel quality (such as path loss) of any wireless link in the system. The embodiments described herein can be applied to resolve any such problems.

[0158] In various embodiments, once the primary node (N) obtains the expected received power in the downlink and uplink, it can make scheduling decisions based on the implementation. For example, N can group its downstream nodes (e.g., UEs and child nodes) into groups that can be scheduled simultaneously with downlink channels expected to have known power offsets. This grouping can vary depending on the implementation. In some embodiments, signaling can be used to facilitate or automate the grouping process. For example, UEs or child nodes (CNs) in a group may be able to transmit only on specific resources (e.g., specific symbols or time slots) that may correspond to resources in the PORS. In this example, since the UE and / or CN may not be directly aware of the PORS configuration, N may need to notify the UE and / or CN via control signaling (e.g., dedicated packet signaling).

[0159] In some embodiments, the UE and / or CN in the group may not be limited to using resources in a resource set or resource pool, but may be limited to applying a transmission power that produces a desired value (or a range of values) of received power at the receiver.

[0160] In various embodiments, the IAB node can have greater flexibility in uplink power control (e.g., due to fewer implementation constraints and / or fewer regulatory constraints). Uplink power control can be used by adding a partial compensation element to the UL-PC, which allows power imbalances to be "half" compensated by the DL-PC and half compensated by the UL-PC. In some embodiments, uplink power control can be used based on an implementation incorporating predetermined signaling. For example, UL-PC parameters can be included in communications associated with the PORS. Then, if the UE and / or CN are scheduled on resources in the PORS, it can be expected that the UE and / or CN will apply additional UL-PC terms in the power control equation. This signaling can be combined with UE signaling and / or CN signaling.

[0161] An embodiment can be described relative to scenario S1. In scenario S1, the problem is whether IAB node N is likely to receive downlink signals from its parent IAB node (PN) and uplink signals from {UE1, UE2, ..., UEn} and / or child IAB nodes {CN1, CN2, ..., CNm}. Furthermore, there may be interference from upcoming transmissions from other nodes {N1, N2, ..., Nk}.

[0162] In scenario S1, to check whether a specific resource allocation with a particular set of transmission powers allows N to receive and decode all signals, a probe time interval (e.g., one or several symbols) can be specified through configuration. During the probe time interval, all nodes of interest transmit reference signals on their assigned PRBs, while N receives the signals and performs measurements. Based on the measurement results, N can determine whether a resource allocation with the expected power results in a decodeable combination of signals.

[0163] An example system 1300 for the detection method is illustrated in... Figure 13 In this example, IAB node (N) 1302 can be scheduled to receive PDSCH from parent node (PN) 1304, N 1302 may intend to schedule PUSCH from child node (CN) 1306, and N 1302 may be subject to interference from interfering node (N1) 1308.

[0164] In this system 1300, a probe interval can be configured before actual transmission so that N 1302 can recognize whether a PUSCH from CN 1306 can be scheduled in the presence of a scheduled PDSCH and interference. This is illustrated in... Figure 14 middle.

[0165] Figure 14 This is a timing diagram illustrating one embodiment of communication 1400 including probing. Communication 1400 occurs at time 1402. At a first time, probing 1404 may occur. Then, at a second time, PDSCH 1406 may be received from PN 1304, PUSCH 1408 may be received from CN 1306, and interference 1410 may be received from N1 1308.

[0166] It should be noted that interference measurement can be achieved through cross-link interference (CLI) management mechanisms. Alternatively, a detection method can be used to address power imbalances without the need for CLI coordination.

[0167] As described herein, it can be assumed that DCI message scheduling shares the channel and / or the data channel. In some embodiments, DCI formats 1_0 and 1_1 can be specified for scheduling PDSCH, and DCI formats 0_0 and 0_1 can be specified for scheduling PUSCH. Embodiments of this disclosure may use the same or similar DCI formats for channel scheduling.

[0168] In some embodiments, the new DCI format can be used to schedule channels, indicate parameter values ​​for a specific channel, trigger aperiodic configuration, and / or for other purposes. The same and / or similar information can be carried by RRC or MAC signaling.

[0169] As will be understood, the configurations and associated signaling described herein may be beam-based (e.g., resource, signal, or channel-related behaviors may be associated with spatial QCL). For example, if a subject node N intends to schedule a PUSCH quasi-co-located with a reference signal relative to spatial Rx parameters from a CN, N can obtain the expected received power (RXP_exp) by measuring the RSRP of the reference signal quasi-co-located with the reference signal relative to spatial Rx parameters.

[0170] The embodiments described herein can be implemented on time-frequency resources with mixed parameter sets (e.g., different values ​​for OFDM symbol duration and subcarrier spacing). Appropriate transformations of values ​​can be expected to account for the effects of the mixed parameter sets. For example, if power control is applied to the resources, all resources that completely or partially overlap with the resources in the time domain can follow the rules of the FDM signal.

[0171] In various embodiments, frequency resources in the PORS can be indicated implicitly or explicitly. Examples of implicit indication could be the BWP or the entire CC. Furthermore, in some embodiments, uplink signals from sub-IAB nodes can be distinguished from uplink signals from the UE.

[0172] In some embodiments, transmit power settings can be used to address transmit power imbalances (e.g., if the transmit power settings are required for simultaneous operation, such as between upstream and downstream links).

[0173] In some embodiments, the IAB node (N) determines the downlink transmit power to be transmitted to the child node (CN) or UE (e.g., for transmitting PDSCH) based on uplink power control parameters received from the parent node (PN). The uplink power control parameters may include open-loop power control parameters such as P0 and α. Additionally, N may receive TPC commands for closed-loop dynamic adjustment of its uplink transmit power.

[0174] In various embodiments, the IAB system can be designed to enable flexible deployment, including deployment in mobile and dynamic environments, support for different deployment densities, and / or for other purposes. In some embodiments, means may exist for IAB nodes to serve IAB nodes and UEs in situations where channel quality is highly unbalanced. In any IAB deployment where IAB node N is serving multiple child nodes and UEs, each child node or UE may require different ranges of transmit power values ​​due to varying values ​​of path loss, etc. Therefore, a setting of the transmit power value by PN could prevent N from multiplexing communication upstream and downstream for a variety of CNs and / or UEs, which could therefore lead to lower resource efficiency and higher latency.

[0175] In some embodiments, the PN can configure different uplink transmit power control parameters for different resource sets (e.g., for different symbols and / or time slots). The configuration can be semi-static to enable each IAB node served by the PN to schedule downstream communication with its CN and / or UE in a timely manner. The configuration of uplink transmit power control parameters for a resource set may be referred to herein as a Power Control Resource Set (PCRS) configuration and may include one or more messages, but can be referred to by any suitable name.

[0176] In various embodiments, the PCRS configuration can be made using an RRC Information Element (IE) that includes one or more of the following parameters: 1) an ID for configuration; 2) a set of resources: a) resources in time: time slots, symbols, periodicity of occurrence, etc., and / or b) resources in frequency: PRB, BWP, CC, etc.; 3) power control parameters (e.g., P0, α); and / or 4) beam-based information (e.g., spatial QCL relative to a reference signal).

[0177] In some embodiments, information included in the PCRS configuration may alternatively be included in another configuration such as a time slot configuration, a multipurpose resource configuration, and / or another configuration.

[0178] In some embodiments, the PCRS configuration can be used to associate power control parameters with communication in a resource set (e.g., on a time-frequency grid), allowing IAB node N to obtain upstream power control information in advance and schedule downstream communication accordingly. Furthermore, assuming the power control parameters for different resource sets cover a sufficiently wide range of upstream power values, a proportionally wide range of downstream power values ​​can be used.

[0179] Once IAB node N receives the PCRS configuration, it can continue to schedule communication with the CN and / or UE.

[0180] Figure 15 This is a flowchart illustrating one embodiment of a method 1500 for determining transmit power settings (e.g., performed at an IAB node (N)).

[0181] First, N receives the PCRS configuration 1502, which includes resource set T and power control parameters {P}. The PCRS configuration can be an RRC IE, included in an RRC IE, and / or part of another IE. The PCRS configuration can be received from the parent node (PN) and can be generated by the CU hosted by PN or IAB.

[0182] Next, N can receive 1504 TPC command {C} from PN (e.g., for resource set T).

[0183] Then, given the PCRS configuration parameters and TPC commands, N (e.g., based on {P} and {C}) calculates the intervals and / or ranges of transmit power TXP1 for uplink communication with PN and / or for possible uplink communication. When N calculates TXP1, communication may or may not yet be scheduled on resource set T.

[0184] N determines the second transmit power TXP2 used by 1508 for downlink communication and / or downstream communication D with the sub-node (CN) or UE. N may determine the value of TXP2 or a range of possible values ​​for TXP2 based on channel measurements performed by N, CN and / or UE.

[0185] Next, N can determine whether downlink and / or downstream communication D can be scheduled simultaneously with uplink and / or upstream communication with PN (e.g., whether N can schedule D while applying TXP2, where: TXP1 / Q ≤ TXP2 ≤ TXP1 x Q). For this purpose, N can compare the values ​​of TXP1 and TXP2. If the power imbalance between TDM communications does not exceed a threshold Q, N may need to ensure that the ratio between TXP1 and TXP2 does not exceed this threshold in order to schedule D on time resources overlapping with time resources in T. It should be noted that N can consider guard periods before and / or after time resources in T. N can consider the frequency domain separation value between the resources used for D and the resource set T (e.g., in units of RBs) (e.g., based on the power imbalance between TXP1 and TXP2).

[0186] exist Figure 15 In this context, it can be assumed that Q is represented by a true metric and that it is a value greater than or equal to 1. The value of Q may depend on node capabilities and / or may be determined by criteria, by semi-static configuration, and / or by dynamic indications.

[0187] If the ratio between TXP1 and TXP2 is within the threshold Q, then N can schedule 1512 D on resources that overlap with T in time.

[0188] Otherwise, N can schedule 1514 D on resources that do not overlap with T in time.

[0189] In some embodiments, the determination in step 1510 may be based on whether the ratio between TXP1 and TXP2 exceeds a threshold Q, while in other embodiments, the determination in step 1510 may include other considerations. For example, total transmit power may be constrained. Constraints may be determined by at least one of node capabilities, emission regulations, values ​​set by standards, and / or configurations and / or indications made by the IAB system. In some embodiments, if N recognizes that coordinating uplink and / or upstream communication and downlink and / or downstream communication results in exceeding the power constraint, it may not schedule D on resources that overlap with T in time.

[0190] In various embodiments, there may be systems where a power imbalance constraint Q can be determined based on an average value (e.g., energy per resource element (EPRE)) and a total power constraint can be determined by the maximum total energy across all resource elements. In such embodiments, the determination made by N in step 1510 may be whether a certain resource allocation for downlink communication and / or downstream communication D distributes a specific amount of transmission energy across the allocated set of REs in a way that satisfies both constraints. For example, an upper limit on the transmission energy for D is considered by subtracting the energy required for uplink communication and / or upstream communication from the total energy constraint. Then, if a lower limit also exists on the EPR for D based on the power imbalance constraint Q, there exists a maximum number of REs that can be allocated to D. N may consider this constraint on the resource allocation to determine whether it can proceed to step 1512 or step 1514.

[0191] In some embodiments, the IAB node transmits SS / PBCH blocks and / or CSI-RS for mobility management purposes. In such embodiments, the IAB node and the UE perform measurements on these reference signals to determine whether the current serving cell is appropriate or whether a handover to another cell would be better.

[0192] In some embodiments, if N is configured with SS / PBCH blocks or CSI-RS for mobility, these reference signals may or may not overlap with the power control resource set. If the reference signals do overlap, the power used for transmission of the reference signals may be limited by the total power minus the power that can be allocated to uplink and / or upstream communications. Therefore, N can semi-statically allocate transmit power to the reference signals based on the open-loop power control parameters configured for those resources.

[0193] In various embodiments, if a dynamic TPC command increases the share of transmit power required for uplink and / or upstream communication, a lower share is reserved for the transmission of the reference signal. Since the reference signal used for mobility is assumed to remain consistent with the stability of the system topology, N may not be able to dynamically change the transmit power of the reference signal. In some embodiments, N may reduce the transmit power used for the reference signal and maintain consistent power over a minimum time period. The minimum time period may be determined by a criterion or by system configuration. In some embodiments, N may apply an upper limit to how it dynamically follows the TPC command. In some embodiments, N may reschedule or remove the reference signal configuration to follow the TPC command.

[0194] In some embodiments, handover decisions move a UE from one cell to another. In IAB systems, the impact can be greater because handover of an IAB node (MT) can lead to topology changes. Therefore, the IAB node may need to consider criteria such as load balancing, in addition to mobility-related measurements, to make a handover decision. In such systems, consistent transmission of mobility-related reference signals can be critical. Therefore, control signaling can be provided to the IAB node to inform its parent node (PN) of limitations it has on downlink and / or downstream communications, such as those used for mobility-related reference signals.

[0195] In some embodiments, PH can be the difference between the nominal maximum transmit power of the UE and the estimated power used for transmission. The estimated power used for transmission may not be the actual power and / or power used for transmission, but rather the transmit power that would be used in the absence of an upper limit on transmit power. Therefore, the PH level can be positive or negative. A negative PH level can indicate the amount by which the transmit power for transmission is limited by the nominal maximum transmit power of the UE. For PUSCH transmissions, a negative PH level can indicate that the network has scheduled a higher data rate than the UE could support given the available transmit power. The network can then adjust the uplink data rate accordingly so that the UE is no longer power-limited. Power margin can be calculated by subtracting the power required to transmit signals on the PUSCH from the UE's maximum total transmit power. The UE can periodically report the power margin via MAC signaling based on the configuration from the serving cell.

[0196] For example, if the UE is in the serving cell c UL carrier f UL BWP b PUSCH transmission timing i If a PUSCH is transmitted, the UE calculates the actual power margin in [dB] for the Type-1 report. Therefore, if the UE determines that the Type-1 power margin report for the active serving cell is based on the actual PUSCH transmission, then for the use of an indexed... j Open-loop parameter set configuration and indexed q d Path loss references and indexes l Serving cell with PUSCH power control adjustment status c carrier f UL BWP activities b PUSCH transmission timing i The UE calculates Type-1 PHR (also known as PUSCHPHR) as follows: (Equation 1), where the power margin in Equation 1 is in [dB] and all parameters are defined in 3GPP TS 38.213. Specifically, for the serving cell... c Each uplink carrier f Determine the maximum UE output power P separately. CMAX,f,c If the UE is not in the serving cell c UL carrier f UL BWP b PUSCH transmission timing i If a PUSCH is transmitted during transmission, the UE cannot report the actual power margin. This is due to the fact that if the transmission timing... i If there is no PUCCH and / or PUSCH transmission, then it cannot be determined. The UE alternatively reports "virtual" power margin based on reference PUSCH transmissions. Therefore, if the UE determines the type-1 PHR of the serving cell to be activated is based on reference PUSCH transmissions, then for the serving cell... c carrier f UL BWP activities b PUSCH transmission timing i The UE will calculate the Type-1 power margin in dB as follows:

[0197] (Equation 2), where This is based on the assumptions that MPR=0dB, A-MPR=0dB, P-MPR=0dB, and ΔT C The values ​​are calculated at 0dB, where MPR ("Maximum Power Reduction"), A-MPR ("Additional Maximum Power Reduction"), P-MPR ("Power Management Maximum Power Reduction"), and ΔT are calculated. C These are power reduction and / or rollback items. All of these power reduction and / or rollback items are defined in 3GPP TS 38.101.

[0198] In some embodiments, the UE may determine the Type-3 Power Headroom Report for Activating the Serving Cell based on the actual SRS transmission, as described in TS 38.213, or determine the Virtual Type-3 PHR based on the reference SRS transmission.

[0199] In some embodiments, the IAB node's maximum transmit power (MT) is determined not only based on node capabilities or standard specifications but also on the power required for downlink and / or downstream communication. The PHR from the IAB node can be associated with a power control resource set, which substantially limits the range of uplink transmission power for that resource set. The IAB node can then use the resource set to transmit reference signals for mobility and / or other downlink and / or downstream signals with more stringent power requirements.

[0200] In some embodiments, if transmit power control TXP2 is assigned to a reference signal or other downlink communication D, the IAB node can consider TXP2 × Q and any total transmit power constraints to generate a power headroom report. If D overlaps temporally with a resource set T in the PCRS configuration, the PHR can be associated with T, allowing the parent node (PN) to apply the power headroom information to communications it will schedule on T.

[0201] In one embodiment, the P power control resource set for the IAB node MT can be determined or configured. CMAX,f,c In another embodiment, the IAB node MT can determine P individually or additionally based on the transmit power control TXP2 allocated to the reference signal or other downlink communication D. CMAX,f,c In some embodiments, the maximum power reduction required to multiplex downlink and / or downstream communications from the IAB node (e.g., and uplink and / or upstream communications transmitted to the PN) can be included in the P-MPR term or a new term can be defined (e.g., for multiplexing the power required to calculate P). CMAX,f,c The IAB-P-MPR of the MPR). The IAB node MT can indicate the P in the PHR to the PN. CMAX,f,c And / or IAB-P-MPR. A PHR (e.g., physical or virtual) can be associated with a power control resource set (e.g., PUSCH, PUCCH, and / or SRS transports on resources corresponding to resource set T). In one example, the ID of the power control resource set associated with PH can be reported in the PHR.

[0202] In various embodiments, the base station can be the central controller of the cell, and the UE can follow its instructions for scheduling, power control, timing alignment, etc. It is expected that the UE will strictly follow the base station and network instructions and provide feedback in the form of CSI reports, HARQ ACK feedback, PHR, etc., to help the base station control the cell. However, in an IAB system, IAB nodes can be responsible for controlling their own cells and can be provided with means to cancel communication despite instructions from the serving cell.

[0203] In some embodiments, an IAB node may cancel uplink transmissions after determining that the transmit power used for uplink communication exceeds a threshold. The IAB node may determine the threshold based on the power it has allocated to downlink signals and / or downstream signals (such as periodic reference signals for mobility). The IAB node may further notify the serving cell (e.g., via a PHR including a negative value) that the uplink and / or upstream communication has been canceled due to power control reasons.

[0204] In some embodiments, the IAB node may cancel downlink communication after determining that uplink communication requires higher transmit power than previously anticipated. The IAB node may further notify downstream nodes (e.g., CN and / or UE) of the cancellation, or the error may be handled via HARQ transmission.

[0205] In various embodiments, the IAB node can determine which communication, uplink and / or upstream or downlink and / or downstream has a higher priority. Priority can be determined by at least one of QoS parameters such as QCI, Redundancy Version (RV), signal type, etc. For example: 1) signals with stricter QoS constraints may be given higher priority; 2) transport blocks with higher RVs may be given higher priority; 3) periodic reference signals used for mobility may be given higher priority; 4) reference signals may be given higher priority compared to control or shared channels; and / or 5) control channels may be given higher priority than shared channels.

[0206] In some embodiments, if the higher priority signal is an uplink signal and / or an upstream signal, the downlink signal and / or downstream signal is canceled, while if the higher priority signal is a downlink signal and / or a downstream signal, the uplink signal and / or upstream signal can be canceled.

[0207] In some embodiments, there may be two types of resource set configurations: 1) PORS makes an association between power offsets (e.g., reference signals from blocks such as SS / PBCH) or receive target power settings for resource sets—primarily for downlink resource sets; and 2) PCRS makes an association between power control parameters for resource sets—primarily for uplink resource sets.

[0208] In various embodiments, the configuration can be made via a standalone RRC IE, can be included in other configurations, or can be made via control signaling.

[0209] In some embodiments, the IAB system can be expected to utilize flexible resource configuration that allows IAB nodes to share resources in both upstream and downstream directions. Resources can be configured as flexible (F) at the symbol level, and then indicated as DL or UL for each instance. Furthermore, resources can be configured as hard, soft, or unavailable for IAB nodes at the symbol level. If a resource is configured as hard (H), it is always available; if it is configured as soft (S), it needs to be indicated as available for each instance; and if it is configured as unavailable (NA), the IAB node cannot use the resource for scheduling communications. The combination of {DL, UL, F, H, S, NA} and the availability indication of soft resources (via DCI) can provide a high level of flexibility for scheduling in the IAB system.

[0210] In some embodiments, since upstream and downstream resources can be shared, the IAB node can receive a combination of PORS and PCRS configurations, i.e., associating power offset parameters (e.g., primarily for downlink) and power control parameters (e.g., primarily for uplink). The IAB node then considers the {DL, UL, F, H, S, NA} configuration and availability indications (e.g., via DCI) to determine which power control parameters apply to which time resources (e.g., time slots, symbols, etc.).

[0211] Furthermore, in various embodiments, the IAB node may not indicate in the signaling to the PN or CN and / or UE which time resources in the resource set are associated with the signaling. Instead, the relevant time resources can be inferred from the IAB node's knowledge of its resource configuration and availability indications. This can be feasible because the IAB node can inform other nodes of its resource configuration. For example, if a time slot in the PORS configuration and / or PCRS configuration includes both DL and UL symbols, the IAB node can inform its parent node of the time slot configuration. The PHR transmitted from the IAB node to its parent node can then cover the entire time slot without explicitly indicating which symbols in the time slot are configured as UL. However, since the parent node knows the configuration, it can infer the information and report the PHR only for the UL symbols in the time slot.

[0212] In some embodiments, power control configurations, such as PORS and PCRS configurations, can be provided by the CU of the IAB host. In such embodiments, IAB nodes in an IAB system served by the IAB host can be able to transmit power control configurations to improve coordination, control interference, etc. Therefore, signaling can be provided by a higher layer (e.g., via an F1 interface) and can be periodic, semi-persistent, non-periodic, or based on a request-response protocol.

[0213] In some embodiments, there may be details about how to apply various methods to solve power control problems in different scenarios.

[0214] In various embodiments, in scenario S2, a single-panel IAB node (N) can receive downlink signals from its parent node (PN) and can simultaneously transmit downlink signals to its child node (CN) or UE. This is an example of full-duplex (FD) wireless communication. FD wireless may be rare in practice and FD radio devices are expected to require strict power control conditions to operate. However, FD can be used in various embodiments.

[0215] Furthermore, simultaneous transmission and reception in scenario S2 can depend on the node's capabilities, which can be proactively or reported to other nodes in the system upon request. Capabilities may include constraints based on transmit and receive power under the following conditions: 1) resource overlap (e.g., the same time-frequency resources are used for transmission and reception); and / or 2) resource non-overlap (e.g., transmission and reception are FDM).

[0216] In scenario S2, the system and method may include one or more of the following: 1) N reports its capability to PN or to the CU of the IAB host; 2) N receives a PORS configuration including a resource set and / or a power offset associated with the resource set relative to a reference signal such as an SS / PBCH block or CSI-RS; 3) N receives the reference signal and performs measurements on the reference signal to obtain a reference power such as an SSB-RSRP or CSI-RSRP; 4) N calculates a target received power based on the measurement results and the power offset in the PORS configuration; and / or 5) if possible, based on channel conditions and node capabilities, N sets the transmit power for downlink communication to the CN and / or UE on resources overlapping with the resource set in the PORS configuration in either or both of the time and frequency domains.

[0217] It can be noted that the downlink transmission power information obtained by receiving PORS configuration on resource set T enables N to generate and transmit its own PORS configuration on resource set T, which can be sent to the sub-IAB node or UE served by N. In various embodiments, some or all of the PORS configurations can be generated at the CU and transmitted to the IAB node by a higher layer.

[0218] In some embodiments, the DL-PC request-license method may be extended to address scenario S2. For this purpose, N may need to assess a range of transmission power suitable for downlink transmission to CN and / or UE and send a request to PN to adjust its downlink transmission power to N on resources that overlap with downlink communication to CN and / or UE in either time or frequency.

[0219] In some embodiments, in scenario S3, a single-panel IAB node (N) transmits to both its parent node (PN) and its child node (CN) or UE. In scenario S3, the uplink transmission from N to PN can be controlled by the PN power, while the power of the downlink transmission from N to CN and / or UE can be determined by the implementation method.

[0220] In scenario S3, since only uplink transmission is power-limited, N can be implemented to balance the power between transmissions. In various embodiments, in scenario S3, the method may include: 1) signaling for power control; 2) configuration rules; 3) rules for storing transmission power for SS / PBCH, periodic CSI-RS, etc.; and / or 4) implementation methods.

[0221] In scenario S3, consider PN-N-CN and / or UE, where PN is the serving cell for N, and N is the serving cell for CN and / or UE.

[0222] In some embodiments, in scenario S3, N can simultaneously transmit signals to PN and CN and / or UE via a single antenna panel. Specifically, N transmits signals to PN on the PUSCH and to CN and / or UE on the PDSCH, where the PUSCH and PDSCH are fully or partially FDM. The method for other channels can be similar.

[0223] In various embodiments of scenario S3, power control parameters can be communicated to N in advance via configuration, which may be referred to as PCRS configuration. PCRS configuration may include the following parameters: 1) an ID for configuration; 2) a set of resources: a) resources in time (e.g., time slots, symbols, periodicity of occurrence, etc.), b) resources in frequency (e.g., PRB, BWP, CC, etc.); 3) power control parameters (e.g., P0 and α); and / or 4) beam-based information (e.g., spatial QCL relative to a reference signal).

[0224] In some embodiments, a method for an IAB node to receive a PCRS configuration may include one or more of the following: 1) N reports its capability to the PN or to the CU of the IAB host; 2) N receives a PCRS configuration including a resource set and a set of power control parameters associated with the resource set; 3) N receives a TPC command; 4) N calculates a target transmit power for an upcoming uplink transmission based on the PCRS configuration and the TPC command; and / or 5) if possible, based on channel conditions and the node's capabilities, N sets the transmit power for downlink communication to the CN and / or the UE on resources that overlap with the resource set in the PCRS configuration in either the time domain or the frequency domain.

[0225] It should be noted that the uplink transmission information obtained by receiving the PCRS configuration on resource set T enables N to generate and transmit the PORS configuration on resource set T, which can be sent to the sub-IAB node or UE served by N. In some embodiments, some or all of the PCRS and PORS configurations can be generated at the CU and transmitted to the IAB node by a higher layer.

[0226] In various embodiments, the DL-PC request-license method can be extended to address scenario S3. For this purpose, N may need to assess a range of transmission power suitable for downlink transmission to CN and / or UE and send a request to PN to adjust the uplink transmission power from N on resources that overlap with downlink communication to CN and / or UE in either time or frequency.

[0227] In some embodiments, to implement FDM between PUSCH and PDSCH transmissions, PN may transmit a first DCI (e.g., DCI1) that pre-schedules the PUSCH transmission sufficiently. Once N receives and decodes DCI1, it can evaluate whether it can schedule the PDSCH transmission on overlapping time resources such as the resources scheduled for the PUSCH transmission and / or the power required for the transmission of the PUSCH signal.

[0228] In some embodiments, if N recognizes that there are sufficient remaining resources and power for scheduling simultaneous channels, N may generate and transmit a second DCI (e.g., DCI2) to schedule PDSCH transmissions to be transmitted to CN and / or UE.

[0229] In various embodiments, the time gap between DCI1 and the scheduled PUSCH transmission can be determined via RRC IE. PUSCH-TimeDomainResourceAllocation The higher-level parameter k2 controls this. k2 can be set to the minimum time N needs to decode DCI1 plus the minimum time N needs to transmit DCI2. That is: k2_min(PN) := T_min(N) + k0_min(N).

[0230] In this equation, k0_min(PN) is the minimum value of k2 for PUSCH transmission from N to PN, T_min(N) is the minimum time required for N to decode DCI1 from PN, and k0_min(N) is the minimum value of k0 for PDSCH transmission from N to CN and / or UE. Higher-layer parameters k0 can be obtained through RRC IE. PDSCH- TimeDomainResourceAllocation To determine.

[0231] In one example, a 2-hop system PN-N-UE can exist. In this example, PN schedules PUSCH transmissions for N and N schedules PDSCH transmissions for the UE. Since N can schedule PDSCH transmissions for the UE with k0=0, k0_min(N) := 0 can be set. Then, k2_min(PN) can depend only on the minimum decoding time for N, which can be set to the constant T_min(N) := T_min.

[0232] In another example, a 3-hop system PN-N-CN-UE can exist. In this example, {PN, N, CN} can schedule {PUSCH, PDSCH, PUSCH} for {N, CN, UE} respectively. Then, the minimum value for k0 can be taken in the following recursive form: k2_min(PN):= T_min(N)+k0_min(N) k0_min(N):= T_min(CN)+k2_min(CN) Since CN can schedule PDSCH for UE even when k2=0, k2_min(CN) can be set to 0. Therefore: k0_min(N) := T_min(CN) k2_min(PN):= T_min(N)+T_min(CN) Assuming T_min(N) := T_min(CN) := T_min, we obtain: k2_min(CN) := 0 k0_min(N) := T_min k2_min(PN) := 2 × T_min This recursive rule can be extended to larger hop counts. For example, in an m-hop IAB system Nm-…-N1-N0-UE, assuming all values ​​for the minimum DCI decoding time are identical, we have: k_min(N0) := 0 k_min(N1) := T_min … k_min(Nm):= m × T_min In the above equation, k_min is either k0_min or k2_min, depending on the situation.

[0233] It should be noted that since the IAB node may not know the number of hops at the RRC layer, the minimum threshold for k0 or k2 can become configurable at higher layers.

[0234] Assume that an IAB node receives the following higher-level parameters in one or more configurations: 1) T: resource set T (e.g., time slots and PRBs) (optional); 2) k0: minimum value for k0 (optional); 3) k2: minimum value for k2 (optional); and / or 4) CN_ID: set of child IAB nodes of the IAB node (optional). Default values ​​can be set as follows: 1) If T is not set, let T be all available resources; and 2) If CN_ID is not set, let CN_ID be the set of all child IAB nodes of the IAB node.

[0235] In some embodiments, consider an IAB node as the receiver of a DCI that schedules a PUSCH transmission. If an IAB node intends to schedule a PDSCH transmission concurrently with a PUSCH transmission, it can perform the following steps: 1) receive the DCI and decode it; and 2) Does the value of k2 enable scheduling of a PDSCH transmission if k0 ≥ k0_min? a) If yes, schedule the concurrent PDSCH transmission if resource and power considerations allow; b) If no, do not schedule the concurrent PDSCH transmission.

[0236] In various embodiments, consider an IAB node as the receiver of a DCI that schedules PDSCH transmissions. If the IAB node intends to schedule a PUSCH transmission concurrently with the PDSCH transmission, it can perform the following steps: 1) receive the DCI and decode it; and 2) Does the value of k0 enable scheduling of PDSCH transmissions if k2 ≥ k2_min? a) If yes, schedule the concurrent PUSCH transmission if resource and power considerations allow; b) If no, do not schedule the concurrent PUSCH transmission. As will be understood, the elements described with respect to scenario S3 can be applied to other scenarios.

[0237] In some embodiments, N may follow power control performed by PN, provided it does not cause interference with power-limited downlink signals. N may consider transmitting a PHR based on power constraints introduced by the downlink signals. The PHR may be associated with a time slot and / or symbol that contains the power-limited downlink signal.

[0238] In some embodiments, PN may have the capability to consist of power-constrained resources for N. PN then does not schedule communication with N on those resources that would require N to violate power constraints, or PN does not expect N to follow normal power control procedures for any communication on power-constrained time slots and / or symbols.

[0239] In various embodiments, the duplex and / or multiplexing capabilities of the IAB node, as well as the node's tolerance to power imbalances, can be used in decision-making. The determination of the IAB node may affect the generation and transmission of closed-loop TPC commands, the maintenance and updating of power control configurations (e.g., PORS, PCRS, etc.).

[0240] In some embodiments, the configuration rule can be set to a minimum value of k0 and / or k2 that can be defined by a standard specification or that can depend on the implementation.

[0241] In some embodiments, the system’s collective ability to efficiently schedule communications may affect the system’s behavior at higher layers for processes such as admission control used to guarantee the required QoS.

[0242] In various embodiments, in scenario S4, a single-panel IAB node (N) can transmit uplink signals to its parent node (PN) and simultaneously receive uplink signals from its child node (CN) or UE. This is another example of full-duplex (FD) wireless communication. Similar to scenario S2, the simultaneous transmission and reception in scenario S4 can depend on the node's capabilities.

[0243] In scenario S4, the system and method may include one or more of the following: 1) N reporting capability to PN or to the CU of the IAB host; 2) N receiving a PCRS configuration including a resource set and a set of power control parameters associated with the resource set; 3) N receiving a TPC command; 4) N calculating a target transmit power for an upcoming uplink transmission based on the PCRS configuration and the TPC command; and / or 5) if possible, based on channel conditions and node capabilities, N setting power control parameters for uplink communication from the child node and / or UE on resources that overlap with the resource set in the PCRS configuration in either or both of the time and frequency domains.

[0244] It should be noted that the uplink transmit power information obtained by receiving the PCRS configuration on resource set T enables N to generate and transmit its own PCRS configuration on resource set T, which can be sent to the child IAB node or UE served by N. In some embodiments, some or all of the PCRS configurations can be generated at the CU and transmitted to the IAB node by a higher layer.

[0245] In various embodiments, the DL-PC request-license method can be extended to address scenario S4. For this purpose, N may need to assess a range of transmission power suitable for uplink transmissions from CN and / or UE and send a request to PN to adjust the uplink transmission power from N on resources that overlap with uplink communication from CN and / or UE in either time or frequency.

[0246] In some embodiments, scenarios S5, S6, S7, and S8 can be similar to scenarios S1, S2, S3, and S4, respectively, except that IAB node N uses more than one panel for communication with other entities in the spatial region. Using multiple panels can reduce the severity of power imbalance conditions. Node capability information can be transmitted proactively or on demand by the rest of the system (e.g., other IAB nodes, IAB hosts, etc.), or the node capability information can be used locally by the IAB node.

[0247] As used herein, despite the frequent references to the IAB, the embodiments described herein can be applied to wireless relay nodes and other types of wireless communication entities.

[0248] Furthermore, as used in this paper, although the entities are referred to as IAB nodes, the same approach can be applied to IAB hosts, which are IAB entities that connect the core network to the IAB network with minor or no modifications.

[0249] Furthermore, each configuration and / or embodiment described herein can be provided through one or more configurations or embodiments. For example, an earlier configuration may provide a subset of parameters, while a later configuration may provide another subset of parameters. As another example, a later configuration may override values ​​provided by an earlier configuration or pre-configuration.

[0250] In some embodiments, configuration can be provided via RRC signaling, MAC signaling, physical layer signaling such as DCI messages, combinations thereof, and / or other means. Configuration may include pre-configured or semi-static configurations provided by standards, vendors, and / or networks and / or operators. Each received parameter value can be overridden by configuring or indicating it.

[0251] Furthermore, the configurations and signaling described in the embodiments described herein can be incorporated into the standard specification by defining new IEs, new MACs, and new L1 signaling, or they can be included in existing IEs and / or signaling. For example, parameters of PORS or PCRS can be included in other system configurations such as time slot configuration.

[0252] Power and energy values ​​described herein or in standard specifications can be described in a true quantity (e.g., in mW) or in a parallel quantity (e.g., dBm). Below are examples of the relationship between true and parallel quantity values: For power, energy, etc.: P[dB] = P[dBW] = 10 log 10 (P[W]) P[dBm] = 10 log 10(P[mW]) Regarding power offset, power ratio, etc.: R[dB] = 10 log 10 (R) It should be noted that the ratio in a true measure can be equivalent to the difference in a logarithmic measure. Therefore, the words "ratio" and "difference" are used interchangeably and can be understood from the context.

[0253] As used herein, “HARQ-ACK” can refer to both a positive response (“ACK”) and a negative response (“NACK”). ACK can mean that the TB was received correctly, while NACK (or NAK) can mean that the TB was received incorrectly.

[0254] Figure 16 This is a flowchart illustrating one embodiment of a method 1600 for power control using at least one power control parameter. In some embodiments, method 1600 is performed by a device such as remote unit 102 and / or network unit 104. In some embodiments, method 1600 may be performed by a processor running program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0255] In various embodiments, method 1600 includes receiving at a first device 1602 configuration information including power offset values ​​associated with a first plurality of resources and a first reference signal. In some embodiments, method 1600 includes receiving from a second device 1604 the first reference signal. In some embodiments, method 1600 includes performing a first measurement on the first reference signal 1606. In various embodiments, method 1600 includes calculating a first expected received power value 1608 based on the first measurement and the power offset value. In some embodiments, method 1600 includes calculating a first target received power value 1610. In some embodiments, method 1600 includes transmitting at least one downlink power control parameter to the second device 1612 based on the first target received power value and the first expected received power value.

[0256] In some embodiments, the first target received power value is calculated based on a second expected received power value associated with a first plurality of resources and a power imbalance threshold. In some embodiments, the power imbalance threshold is predefined, semi-statically configured, dynamically transmitted by signaling, or some combination thereof. In various embodiments, the second expected received power value is obtained based on a second measurement of a second reference signal from a third device.

[0257] In one embodiment, the first expected received power value, the first target received power value, and the second expected received power value are calculated on a per-resource element basis. In some embodiments, method 1600 further includes: receiving an received power change value from a second device; and transmitting scheduling information for uplink channels associated with a first plurality of resources to a third device based on the received power change value, the second expected received power value, and a power imbalance threshold. In some embodiments, calculating the first target received power value includes selecting a first target received power value such that the ratio between the first target received power and the second expected received power is less than the power imbalance threshold.

[0258] In various embodiments, the second device provides a first serving cell for the first device, and the second device provides a second serving cell for the third device. In one embodiment, method 1600 further includes: receiving from the second device an indication of whether at least one downlink power control parameter is accepted; and transmitting scheduling information to the third device for an uplink channel associated with a first plurality of resources based on whether the indication is affirmative. In some embodiments, being associated with the first plurality of resources includes: being located on a subset of the first plurality of resources; being located on a second plurality of resources that overlap with the first plurality of resources in the time domain; or a combination thereof.

[0259] Figure 17 This is a flowchart illustrating another embodiment of a method 1700 for power control using at least one power control parameter. In some embodiments, method 1700 is performed by a device such as remote unit 102 and / or network unit 104. In some embodiments, method 1700 may be performed by a processor running program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0260] In various embodiments, method 1700 includes receiving a first reference signal from a second device at a first device 1702. In some embodiments, method 1700 includes performing a first measurement on the first reference signal 1704. In some embodiments, method 1700 includes calculating a first expected received power value associated with a first plurality of resources based on the first measurement 1706. In various embodiments, method 1700 includes calculating a first target received power value 1708. In some embodiments, method 1700 includes transmitting at least one downlink power control parameter to the second device 1710 based on the first target received power value and the first expected received power value.

[0261] In some embodiments, the first target received power value is calculated based on a second expected received power value associated with a first plurality of resources and a power imbalance threshold. In some embodiments, the power imbalance threshold is predefined, semi-statically configured, dynamically transmitted by signaling, or some combination thereof. In various embodiments, the second expected received power value is obtained based on a second measurement of a second reference signal from a third device.

[0262] In one embodiment, the first expected received power value, the first target received power value, and the second expected power received value are calculated on a per-resource element basis. In some embodiments, method 1700 further includes: receiving a permitted power change value from a second device; and transmitting scheduling information for uplink channels associated with a first plurality of resources to a third device based on the permitted power change value, the second expected received power value, and a power imbalance threshold. In some embodiments, calculating the first target received power value includes selecting a first target received power value such that the ratio between the first target received power and the second expected received power is less than the power imbalance threshold.

[0263] In various embodiments, the second device provides a first serving cell for the first device, and the second device provides a second serving cell for the third device. In one embodiment, method 1700 further includes: receiving from the second device an indication of whether at least one downlink power control parameter is accepted; and transmitting scheduling information to the third device for an uplink channel associated with a first plurality of resources based on whether the indication is affirmative. In some embodiments, being associated with the first plurality of resources includes: being located on a subset of the first plurality of resources; being located on a second plurality of resources that overlap with the first plurality of resources in the time domain; or a combination thereof.

[0264] In one embodiment, a method includes: receiving configuration information at a first device including power offset values ​​associated with a first plurality of resources and a first reference signal; receiving the first reference signal from a second device; performing a first measurement on the first reference signal; calculating a first expected received power value based on the first measurement and the power offset values; calculating a first target received power value; and transmitting at least one downlink power control parameter to the second device based on the first target received power value and the first expected received power value.

[0265] In some embodiments, the first target received power value is calculated based on a second expected received power value associated with a first plurality of resources and a power imbalance threshold.

[0266] In some embodiments, the power imbalance threshold is predefined, semi-statically configured, dynamically signaled, or some combination thereof.

[0267] In various embodiments, the second expected received power value is obtained based on a second measurement of a second reference signal from a third device.

[0268] In one embodiment, the first expected received power value, the first target received power value, and the second expected power received value are calculated on a per resource element basis.

[0269] In some embodiments, the method further includes: receiving an accepted power change value from a second device; and transmitting scheduling information for an uplink channel associated with a first plurality of resources to a third device based on the accepted power change value, a second expected received power value, and a power imbalance threshold.

[0270] In some embodiments, calculating the first target received power value includes selecting a first target received power value such that the ratio between the first target received power and the second expected received power is less than a power imbalance threshold.

[0271] In various embodiments, the second device provides a first serving cell for the first device, and the second device provides a second serving cell for the third device.

[0272] In one embodiment, the method further includes: receiving from a second device an indication of whether at least one downlink power control parameter is accepted; and transmitting, based on whether the indication is affirmative, scheduling information for an uplink channel associated with a first plurality of resources to a third device.

[0273] In some embodiments, being associated with the first plurality of resources includes: being located on a subset of the first plurality of resources; being located on a second plurality of resources that overlap with the first plurality of resources in the time domain; or a combination thereof.

[0274] In one embodiment, an apparatus includes a first device. The apparatus further includes: a receiver that receives configuration information including power offset values ​​associated with a first plurality of resources and a first reference signal; and receives the first reference signal from a second device; a processor that performs a first measurement on the first reference signal; calculates a first expected received power value based on the first measurement and the power offset values; and calculates a first target received power value; and a transmitter that transmits at least one downlink power control parameter to the second device based on the first target received power value and the first expected received power value.

[0275] In some embodiments, the first target received power value is calculated based on a second expected received power value associated with a first plurality of resources and a power imbalance threshold.

[0276] In some embodiments, the power imbalance threshold is predefined, semi-statically configured, dynamically signaled, or some combination thereof.

[0277] In various embodiments, the second expected received power value is obtained based on a second measurement of a second reference signal from a third device.

[0278] In one embodiment, the first expected received power value, the first target received power value, and the second expected power received value are calculated on a per resource element basis.

[0279] In some embodiments, the receiver receives the received power change value from the second device; and the transmitter transmits scheduling information for the uplink channel associated with the first plurality of resources to the third device based on the received power change value, a second expected received power value, and a power imbalance threshold.

[0280] In some embodiments, the processor calculating the first target received power value includes the processor selecting the first target received power value such that the ratio between the first target received power and the second expected received power is less than a power imbalance threshold.

[0281] In various embodiments, the second device provides a first serving cell for the first device, and the second device provides a second serving cell for the third device.

[0282] In one embodiment, the receiver receives from the second device an indication of whether at least one downlink power control parameter is accepted; and the transmitter, based on whether the indication is affirmative, transmits scheduling information for an uplink channel associated with a first plurality of resources to the third device.

[0283] In some embodiments, being associated with the first plurality of resources includes: being located on a subset of the first plurality of resources; being located on a second plurality of resources that overlap with the first plurality of resources in the time domain; or a combination thereof.

[0284] In one embodiment, a method includes: receiving a first reference signal from a second device at a first device; performing a first measurement on the first reference signal; calculating a first expected received power value associated with a first plurality of resources based on the first measurement; calculating a first target received power value; and transmitting at least one downlink power control parameter to the second device based on the first target received power value and the first expected received power value.

[0285] In some embodiments, the first target received power value is calculated based on a second expected received power value associated with a first plurality of resources and a power imbalance threshold.

[0286] In some embodiments, the power imbalance threshold is predefined, semi-statically configured, dynamically signaled, or some combination thereof.

[0287] In various embodiments, the second expected received power value is obtained based on a second measurement of a second reference signal from a third device.

[0288] In one embodiment, the first expected received power value, the first target received power value, and the second expected power received value are calculated on a per resource element basis.

[0289] In some embodiments, the method further includes: receiving a permitted power change value from a second device; and transmitting scheduling information for an uplink channel associated with a first plurality of resources to a third device based on the permitted power change value, a second expected received power value, and a power imbalance threshold.

[0290] In some embodiments, calculating the first target received power value includes selecting a first target received power value such that the ratio between the first target received power and the second expected received power is less than a power imbalance threshold.

[0291] In various embodiments, the second device provides a first serving cell for the first device, and the second device provides a second serving cell for the third device.

[0292] In one embodiment, the method further includes: receiving from a second device an indication of whether at least one downlink power control parameter is accepted; and transmitting, based on whether the indication is affirmative, scheduling information for an uplink channel associated with a first plurality of resources to a third device.

[0293] In some embodiments, being associated with the first plurality of resources includes: being located on a subset of the first plurality of resources; being located on a second plurality of resources that overlap with the first plurality of resources in the time domain; or a combination thereof.

[0294] In one embodiment, an apparatus includes a first device. The apparatus further includes: a receiver that receives a first reference signal from a second device; a processor that: performs a first measurement on the first reference signal; calculates a first expected received power value associated with a first plurality of resources based on the first measurement; calculates a first target received power value; and a transmitter that transmits at least one downlink power control parameter to the second device based on the first target received power value and the first expected received power value.

[0295] In some embodiments, the first target received power value is calculated based on a second expected received power value associated with a first plurality of resources and a power imbalance threshold.

[0296] In some embodiments, the power imbalance threshold is predefined, semi-statically configured, dynamically signaled, or some combination thereof.

[0297] In various embodiments, the second expected received power value is obtained based on a second measurement of a second reference signal from a third device.

[0298] In one embodiment, the first expected received power value, the first target received power value, and the second expected power received value are calculated on a per resource element basis.

[0299] In some embodiments, the receiver receives a permitted power change value from the second device; and the transmitter transmits scheduling information for uplink channels associated with a first plurality of resources to the third device based on the permitted power change value, a second expected received power value, and a power imbalance threshold.

[0300] In some embodiments, the processor calculating the first target received power value includes the processor selecting the first target received power value such that the ratio between the first target received power and the second expected received power is less than a power imbalance threshold.

[0301] In various embodiments, the second device provides a first serving cell for the first device, and the second device provides a second serving cell for the third device.

[0302] In one embodiment, the receiver receives from the second device an indication of whether at least one downlink power control parameter is accepted; and the transmitter, based on whether the indication is affirmative, transmits scheduling information for an uplink channel associated with a first plurality of resources to the third device.

[0303] In some embodiments, being associated with the first plurality of resources includes: being located on a subset of the first plurality of resources; being located on a second plurality of resources that overlap with the first plurality of resources in the time domain; or a combination thereof.

[0304] The embodiments may be practiced in other specific forms. The described embodiments are to be regarded in all respects as illustrative only and not restrictive. Furthermore, any embodiments described herein may be combined together. Therefore, the scope of the invention is indicated by the appended claims rather than the foregoing description. All variations within the meaning and equivalents of the claims are included within their scope.

Claims

1. An apparatus for performing network functions, the apparatus comprising: At least one memory; as well as At least one processor, coupled to the at least one memory and configured such that the device: Receive resource configuration at the first node, the resource configuration indicating: The identifier (ID) of the resource configuration; Multiple time slots; as well as Periodicity; and A first control message is received from the second node, the first control message indicating the received power of the Physical Downlink Shared Channel (PDSCH) in the time domain, frequency domain, and spatial domain, wherein the resources in the time domain are indicated by the resource configuration, and the first control message includes: The identifier of the resource configuration; The first indication of the downlink transmission power adjustment value; and The second indication of the first beam index; and Obtain the received power of the PDSCH associated with the resource and the first beam index and based on the power offset value relative to the received power of the Channel State Information Reference Signal (CSI-RS).

2. The apparatus of claim 1, wherein the first node is an Integrated Access and Backhaul (IAB) node, and the second node is the parent node of the first node.

3. The apparatus of claim 1, wherein the first control message is a first media access control (MAC) message.

4. The apparatus of claim 1, wherein the resource configuration is indicated in a Radio Resource Control (RRC) Information Element (IE).

5. The apparatus of claim 1, wherein the power adjustment value is in decibels (dB).

6. The apparatus of claim 1, wherein the first beam index comprises one or more of a synchronization signal block (SSB) index, a CSI-RS index, or a quasi-co-address (QCL) parameter.

7. The apparatus of claim 1, wherein the first node is an IAB node, and one or more of the following exist: the second node is the parent node of the first node, or the first node is the child node of the second node.

8. The apparatus of claim 1, wherein the at least one processor is configured such that the apparatus: Send a second MAC message to the second node, the second MAC message indicating one or more of the following: The identifier of the resource configuration; The fourth indication of the expected downlink transmission power adjustment value; The fifth indicator of the second beam index; or The sixth indication of the second frequency resource.

9. The apparatus of claim 8, wherein the second control message is a second media access control (MAC) message.

10. The apparatus of claim 8, wherein the desired power adjustment value is in decibels (dB).

11. The apparatus of claim 8, wherein the second beam index comprises one or more of a synchronization signal block (SSB) index, a CSI-RS index, or a quasi-co-address (QCL) parameter.

12. A method for performing network functions, the method comprising: Receive resource configuration at the first node, the resource configuration indicating: The identifier (ID) of the resource configuration; Multiple time slots; as well as Periodicity; as well as A first control message is received from the second node, the first control message indicating the received power of the Physical Downlink Shared Channel (PDSCH) in the time domain, frequency domain, and spatial domain, wherein the resources in the time domain are indicated by the resource configuration, and the first control message includes: The identifier of the resource configuration; The first indication of the downlink transmission power adjustment value; and The second indication of the first beam index; and Obtain the received power of the PDSCH associated with the resource and the first beam index and based on the power offset value relative to the received power of the Channel State Information Reference Signal (CSI-RS).

13. The method of claim 12, wherein the first node is an Integrated Access and Backhaul (IAB) node, and the second node is the parent node of the first node.

14. The method of claim 12, wherein the first control message is a first media access control (MAC) message.

15. The method of claim 12, wherein the resource configuration is indicated in a Radio Resource Control (RRC) Information Element (IE).

16. The method of claim 12, wherein the power adjustment value is in decibels (dB).

17. The method of claim 12, wherein the first beam index comprises one or more of a Synchronization Signal Block (SSB) index, a CSI-RS index, or a Quasi-Co-address (QCL) parameter.

18. An apparatus for performing network functions, the apparatus comprising: At least one memory; as well as At least one processor, coupled to the at least one memory and configured such that the device: At the Integrated Access and Backhaul (IAB) node, a resource configuration is received from a Radio Resource Control (RRC) Information Element (IE), which indicates: The identifier (ID) of the resource configuration; Multiple time slots; as well as Periodicity; A first Media Access Control (MAC) message is received from the parent node of the IAB node. This MAC message indicates the received power of the Physical Downlink Shared Channel (PDSCH) in the time, frequency, and spatial domains, wherein the resources in the time domain are indicated by the resource configuration. The MAC message includes: The identifier of the resource configuration; The first indication of the downlink transmission power adjustment value; and A second indication of a first beam index, including one or more of the first synchronization block (SSB) index, the first channel state information reference signal (CSI-RS) index, or the first quasi-co-address (QCL) parameter; The processor obtains the received power of the PDSCH associated with the resource and the first beam index, and based on the power offset value relative to the CSI-RS received power; and A second MAC message is sent to the parent node, the second MAC message indicating one or more of the following: The identifier of the resource configuration; The fourth indication of the expected downlink transmission power adjustment value; A fifth indication of the second beam index, including the second SSB index, the second CSI-RS index, the second QCL parameter, or some combination thereof; or The sixth indication of the second frequency resource; Or some combination thereof.

19. The apparatus of claim 18, wherein the resource configuration is indicated in a Radio Resource Control (RRC) Information Element (IE).

20. The apparatus of claim 18, wherein the MAC message includes a third indication of a first frequency resource.

Images